Tiny Core Base > Release Candidate Testing
Core v4.2rc2
roberts:
"I eat my own dog food", i.e, standard extensions are used to create the isos.
The syslinux extension according to the .info file has not changed since:
--- Code: ---Current: 2010/07/14
--- End code ---
What did change during this RC cycle was the added isohybrid code on the TinyCore iso.
The latest posting of TinyCore-4.2rc2.iso has the isohybrid feature removed.
I am waiting to hear if the removal of the isohybrid solves the reported issue.
roberts:
--- Quote from: coreplayer2 on December 19, 2011, 03:21:20 AM ---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.
--- End quote ---
Obviously a virtual machine is not a real machine. I suspect that hdparm -z is not being supported by your vm. hdparm -z is required to re-read an in session change to a drive partition table.
bmarkus:
--- Quote from: roberts on December 19, 2011, 11:41:46 AM ---"I am waiting to hear if the removal of the isohybrid solves the reported issue.
--- End quote ---
Just downloaded Tiny Core and Core Plus. Same as before, doesn't work. If iso hybrid removed, it is something else.
roberts:
With TinyCore being only an example and CorePlus only a convenience installlation build.
Nothing should preclude you from proceeding with Core-4.2.iso with your desired collection of X/GUI extensions residing on your tcedir.
bmarkus:
--- Quote from: roberts on December 19, 2011, 03:02:36 PM ---With TinyCore being only an example and CorePlus only a convenience installlation build.
Nothing should preclude you from proceeding with Core-4.2.iso with your desired collection of X/GUI extensions residing on your tcedir.
--- End quote ---
There are no reason to use 4.rc2, I will stay with stable 4.1 which runs smoothly on all machines here. Testing was done, result reported.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version