Core v4.2rc2

[gerald_clark]

That's even better.
Shows there is more than one way to skin a cat.

[roberts]

Running "tce-load -i Xprogs' from an aterm does not update wbar or desktop menus.
X must be stopped and restarted.

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]

4.1 works, 4.2 doesn'. Therefore it is a 4.2 bug 

or it's a syslinux issue. did its version change in the meantime ?

[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: [Select]

Current:        2010/07/14
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]

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.

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]

"I am waiting to hear if the removal of the isohybrid solves the reported issue.

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]

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.

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.

[coreplayer2]

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.

Didn't notice hdparm in the list of installed extensions Am assuming  some features of hdparm are included with the installer? 
Many methods exist to write new partition tables I use gparted  successfully on all VM's and real hardware included.  Havent experience any negative issues using hdparm before but will investigate if you feel this is the cause of this issue.

I really like the installer, pity grub4dos has been depreciated, I still use it on older hardware which Syslinux v 4.x hasn't supported. 
edit: syslinux has not changed (is still v4.01)

[Rich]

Hi coreplayer2
hdparm is provided by busybox through a link in /sbin.

[coreplayer2]

thanks, although is busy box always installed with coreplus? ...?

[maro]

BusyBox has been from day one at the very core of each "Core" release. In it's many "incarnations" (i.e. the so called applets) it provides the equivalent of ca. 225 different executables, whilst not even using up 500 kBytes. It is one of the main reasons why Core can be as small as it is.

The fact that someone with 300+ posts in this forum here is not even aware of such IMHO "basic fact about Core" makes me really wonder why people are seemingly not even reading the first line of the Welcome page.

BTW that page probably needs some refresh to adjust to the fact that kernel v2.6 is now history, and possibly some more due to the change of focus from TC to Core.

[Rich]

Hi coreplayer2
Open a terminal an enter   ls -l /bin
You will see that the majority of the commands listed (including ls) are really links to busybox.
Now enter   ls -l /sbin
You will find that a lot of those commands are just links to /bin/busybox.