Hi,
I've been going trough the slitaz documentation to learn how to add persistence/modify the splash screen. I've found that there wasn't good info at the handbook yet, so I added a page there:
http://doc.slitaz.org/en:guides:persistence_splash
Anyway, I was hoping someone could go over what I write to ensure I didn't wrote down any mistakes (I got all info from forum posts, so there shouldn't be any major ones in there but I did make some assumptions here and there).
I also still remain to have some questions about the persistence adding/splashscreen altering:
* first of all, was I right that persistence can be kept out simply by removing the home=UUID line at the extlinux.conf or syslinux.cfg file ? Is syslinux indeed located at /home/boot/syslinux ?
* next, can both a root and a user account (each with or without persistence, so 4 accounts in total) be made ? I assume persistence can be added/removed by adding or leaving out the home=UUID, however I didn't find how exactly a user and a root account can be made at the boot screen (not at the slim login manager !). The idea is to be able to remove slim alltogether and just use the boot screen instead (similar as in Antix Linux). An added advantage would be that new linux users might not need to format the drive to ext3 anymore, and can just format it to fat32 in windows and then use a windows usb stick maker (like LinuxLive usb creator, ...)
* another question is whether it is indeed possible to remove slim, and also delete all programs that tap into slim (for example the logout/switch user button in the logout box), ... If possible, what files do I need to change to delete all references to slim
* finally, is it possible to have changes saved in an allready existing rootfs.gz file ? I might need to do changes on slitaz during the course of many days, so would need to log out/shut off the computer many times, and I don't want to make a distro/flavour that uses a huge amount of rootfs.gz files (I assume one will be created every time I make changes during a particular day). Alternatively, if not possible, can I make a recipe, cook list or flavor file (not sure what the difference is between these) or just a basic shell script that would execute all the changes in one go ? That way, I can just modify the recipe/cook list/flavor file/shell script during the course of many days, and then execute it the last day, and immediately make the rootfs.gz file that same day.
