Notes for release candidate 1.3rx2
Tiny Core now supports UUID and LABELS. This is most helpful when using pendrives on different machines and you want to "anchor" your Tiny Core boot codes to a specific device.
To find the UUID of a device use the command blkid
blkid -s UUID /dev/sda1
You can mount devices by UUID with the mount command, e.g,
# mount -U 4773-DFE2
The UUID tend to be long, so best to cut and paste into your menu.lst boot options.
You can now specify the device to be used by UUID as follows
tce=UUID=4773-DFE2 home=UUID=4773-DFE2 opt=UUID=4773-DFE2 restore=UUID=4773-DFE2
Typically this is helpful when using pendrives, be sure to add the waitusb=5 option.
You can now also use LABELS. This too is optional.
To write a label on the partition of a pendrive, use the command tune2fs
# tune2fs -L tinycore /dev/sda1
You can check your results with
blkid -s LABEL /dev/sda1
Then you can specify devices by LABEL, e.g.
# mount -L tinycore
For Tiny Core boot options use:
tce=LABEL=tinycore home=LABEL=tinycore opt=LABEL=tinycore restore=LABEL=tinycore
--------------------------------------------------------------------------------------
Also in this cut:
udevtrigger for dymamic support of loaded modules in tc-config and tce-load will eliminate the need to have to manually modprobe many device modules.
---------------------------------------------------------------------------------------
New xsetup.sh. The new concept, is to better support Xservers.
When booting tinycore, if Xfbdev is in your tce dir then xsetup will apply to that X server.
This greatly simplifies framebuffer setup, typically needed by older laptops.
These changes also allows you to rerun xsetup to change Xserver, resolution, or mouse and still retain changes you might have made to your /home/tc/.xsession.
I also emliniated the loop you can get into by booting with xsetup, then wanting to make additional changes via another run of xsetup.sh.
The boot code xsetup will now only trigger a single run through of xsetup.sh via startx.
Xorg server is only slightly supported in the new xsetup.sh, in that it will only update .xsession if it finds an /etc/X11/xorg.conf file. Still it eliminates having to manually edit .xsession.