cde & unetbootin

[jls]

Hi
I think 1 of the most common ways tc is used is via unetbootin,
Maybe not used but tried.
and here it comes the problem.
If the cde dir on the tc iso would be renamed to tce, then unetobootin made tc usb would work well like the usb which tc-install makes.
At the moment using unetbotin made usb, system loads properly but when u open apps u see at the bottom

Code: [Select]

/tmp/tce(if my memory works well)
where this could be instead the tce dir on the usb since is writable and is also the one the system used to load the tc extensions.
cde bootcode could maybe remains to look for (pseudo) cd extensions and so kept as bootcode on the tc iso.
Of course the new cde bootcode will search for dirs called tce.
So I propose to change the cde dir name to tce on the tc iso.

PS cde was introduced before the iso bootcode, so now if the user needs extensions from other sources he can use an iso to place them.

[roberts]

Allowing tce directory in an iso it effectively breaks the system.
Typically one would expect an iso image to be written to a cdrom and should therefore work.
It will not.

unetbootin is specifically discussed in the faq:
http://distro.ibiblio.org/tinycorelinux/faq.html#pendrives

[jls]

I have modified tce-setup changing al the cde occurrencies to tce and then I rebuilt the tc iso with ezremaster.
Then I tested with qemu passing the iso with the -cdrom parameter.
To me it seems to work, tc loads, apps says /tmp/tce/optional and I also tried installing some tczs without problems.
dependencies & onboot also works