Hi vinceASPECT and RICH ..
This is a note mostly for lurkers really new to the concept about question 2 .... and might need just a slight head-start before delving into the very fine book and wiki's.
As delivered, TC assumes a read-only CD environment where nothing by default is saved after reboot. It uses the "cde" directory and contents to get the desired extensions and so forth.
To actually SAVE changes, we need to tell TC that it is no longer a cd type of environment.
The simplest way to do that is to manually create a "tce" directory in the root of a drive. Tinycore will search for it, and use that directory structure for persistent changes and optional extensions.
But, by manually creating that tce directory, you'll be missing the extensions that were part of the cd distribution itself in the cde directory. Some new users to Tinycore find themselves at the commandline after reboot, rather than the say the gui interface.
An easy solution to this is instead of manually creating the "tce" directory in the root of a drive, COPY the existing fully populated cde directory to the root of a drive, and RENAME it to tce. Or simply rename it to tce if the cde directory is already in the root depending on how you built it.
That's the magic part, but there can be issues with this simplicity. For example, the magic starts to break if there are multiple tce directories hanging around. This can happen if in a pique of excitement about TC, you start experimenting and forget you've already made one!
This is where specifying the location and drive of where the tce directory is located can come into play.
To be very specific about it, one changes their variable in the kernel boot line by either specifying a LABEL or UUID. These can also include more specific paths.
One common example would be to see something like this in the kernel boot line if you have a drive with a label you created with say "MYLINUX"
tce=LABEL=MYLINUXAgain, instead of using a LABEL, the use of UUID's is even more exacting. Like what if you have two drives with the same label? Yeah, UUID's for you!
When you reboot, even if you have other tce directories hanging around for testing purposes, etc, this will direct your current TC session to use the tce directory on THIS drive. Instead of temporarily changing the boot line all the time, one can manually edit their sylinux/extlinux or grub bootloader's line to make this permanent.
Is this the best or only way to do it? Not necessarily - refinement comes with experience, but this will at least get one off the ground and see the aha moment as described in the book or wiki.
That's my take on it - not being a technical writer ...
Welcome
FAQ
Downloads
Wiki
