Here's a proposal for a small improvement that might benefit many ...
Slitaz is among the few GNU/Linux distributions that runs entirely in RAM, not only because it is small but because it is designed that way. The advantages of this are obvious: Run from a Live CD, Slitaz is very fast and practically incorruptible, as a simple re-boot will sort out even the biggest mess (ideal for wild experiments one wouldn't dare otherwise). I guess, most of those who do not install Slitaz but run it from a customized Live CD, do so for these reasons.
The downside to all of this is of course a lack in flexibility. One has to make a new CD whenever there's an update for an important application (browser, flash player etc.). But this doesn't happen too often and a script that adds/removes packages, copies/deletes stuff, runs Tazlito and re-boots, usually doesn't take longer than 15-20 minutes including burning.
But there's still something missing in this setup: persistence! It is possible to mount a drive and restore stuff during boot-up in /etc/init.d/local.sh. But for a backup function there seems to be nothing like this. I'm using two hooks in the re-boot and the shut-down sections of /urs/bin/desktopbox (thanks, kultex) to run a backup script. But I think this is rather inelegant. It also has the disadvantage to run in the user space. A mount/unmount command in the backup script will prompt for a password, and who wants to type a password when shutting down the computer?
So, here's my proposal: why not have something like "local_up.sh" and "local_dn.sh", sitting peacefully next to each other in /etc/init.d, doing exactly what their names suggest? ("local_dn" should obviously be executed very late so there's no prompt for a password).
