Tiny Core Base > Release Candidate Testing
Core v4.2rc2
gerald_clark:
That's even better.
Shows there is more than one way to skin a cat.
roberts:
--- Quote from: gerald_clark on December 18, 2011, 01:06:25 PM ---Running "tce-load -i Xprogs' from an aterm does not update wbar or desktop menus.
X must be stopped and restarted.
--- End quote ---
Done! :)
coreplayer2:
Awesome work here thanks
meanwhile i'm experiencing a few inconveniences, initially one appeared an issue with the windows managers of coreplus. I figured I'd sample these window managers, with a fresh frugal install between each. Soon after sampling two or three wm's I began experiencing system lockups, resolved by forcing a shutdown to clear each time, pulling the plug deal.
I found that despite the installer reporting to write zeros to the disk, create a new partition, format etc etc. the old installed extensions are loaded each time, ie: the old partition was not being zero'd or partitioned and formatted as indicated. On a clean new drive the installer performed the partitioning and formatting as expected, however a drives partition structure is never again touched once created.
I've performed the install procedure many times, boot to coreplus cd - tc-install - using frugal - whole disk - select disk - install boot loader - format with ext2 - boot options for persistence etc etc.. then watch as the installer writes zero's to the beginning of /dev/sda, create new partition and format it etc etc then reboot to the drive and all old extensions are still present and loaded.
So far have used gparted to wiped the drive and create a new partition, after which the installer from coreplus cd works as advertised.
I found this anomaly can be reliably reproduced using a VM
Also would be grateful for some consistency in the use of the install buttons, like an "exit" button next to the grayed out "proceed" button on install completion, as it is i'm always suspicious if the install fully completed.
bmarkus:
Just a small cosmetic. Running from CD an eject before shutting down would be convenient.
yoshi314:
--- Quote from: bmarkus on December 18, 2011, 05:11:13 PM ---4.1 works, 4.2 doesn'. Therefore it is a 4.2 bug >:(
--- End quote ---
or it's a syslinux issue. did its version change in the meantime ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version