| Both sides previous revisionPrevious revision | |
| en:guides:persistence_splash [2014/11/26 15:14] – added my second remark; I hope someone reads it and corrects this manual accordingly brianperry | en:guides:persistence_splash [2026/10/14 23:55] (current) – external edit 127.0.0.1 |
|---|
| |
| ==Method 1== | ==Method 1== |
| By typing "slitaz home = sdxx" or "slitaz home=UUID" at the command line at the splash/boot screen. See [[http://doc.slitaz.org/en:handbook:livecd#Slitaz parameters|here]]. This option hence involves typing in this line every time you want persistence. It's also only useful when keeping the slim login manager in place, as you can't specify to (immediately) log in as user or root (either with or without persistence). | By typing "slitaz home = sdxx" or "slitaz home=UUID" at the command line at the splash/boot screen. See [[https://doc.slitaz.org/handbook/live.html parameters|here]]. This option hence involves typing in this line every time you want persistence. It's also only useful when keeping the slim login manager in place, as you can't specify to (immediately) log in as user or root (either with or without persistence). |
| |
| The "home=sdxx" or "home=UUID" basically just tells slitaz which disk it is where it needs to write the system changes to (which are being written away as a rootfs.gz file, see below). It should btw be noted here that "home=UUID" is preferred over "home=sdxx" or even "home=usb (the latter is the same as "home=sda1"). This, as depending on which drives you connect at any given time, your drive name may change, which will give problems (this happens as depending on the access speed of the drive (speed depending on the type of drives connected/inserted, i.e. SATA drive, USB drive, ...), linux will assign a different drive name). Then, to effectively write away the changes, you need to type in "#tazusb writefs gzip (for fast compression, average filesize), "#tazusb writefs lzma" (for slow compression, smaller filesize) or "#tazusb writefs none" (for no compression, larger filesize). Each of these will write everything to a 'rootfs.gz' archive to be loaded the next time you boot. | The "home=sdxx" or "home=UUID" basically just tells slitaz which disk it is where it needs to write the system changes to (which are being written away as a rootfs.gz file, see below). It should btw be noted here that "home=UUID" is preferred over "home=sdxx" or even "home=usb (the latter is the same as "home=sda1"). This, as depending on which drives you connect at any given time, your drive name may change, which will give problems (this happens as depending on the access speed of the drive (speed depending on the type of drives connected/inserted, i.e. SATA drive, USB drive, ...), linux will assign a different drive name). Then, to effectively write away the changes, you need to type in "#tazusb writefs gzip (for fast compression, average filesize), "#tazusb writefs lzma" (for slow compression, smaller filesize) or "#tazusb writefs none" (for no compression, larger filesize). Each of these will write everything to a 'rootfs.gz' archive to be loaded the next time you boot. |
| |
| ==Method 2== | ==Method 2== |
| Another way to tell slitaz the disk it needs to write to is by simply modifying or adding an entry to the extlinux.conf file (which is located at /home/boot/extlinux). See also [[http://forum.slitaz.org/topic/how-to-make-changes-persistent-on-a-usb-key-live-installation|here]]. This method is the only method that doesn't require typing in commands every time you boot and require persistence (more automated). Note that the same method can also be followed when you have a FAT32/non-slim login manager setup, however, you will then need to do the changes in the syslinux.cfg file (located at /home/boot/syslinux), see [[https://superuser.com/questions/123399/how-to-make-slitaz-usb-persistent|here]], and not extlinux.conf. To change the extlinux.conf or syslinux.cfg (which one you need to alter will depend on the filesystem you use), you need to pick one of the slitaz entries you're currently not using at the boot screen (i.e. base, justx, ... entry), and then modify it. Alternatively, you can make an entirely new label as well (see [[http://forum.slitaz.org/topic/how-to-make-changes-persistent-on-a-usb-key-live-installation|here]]. Make it look like this: | Another way to tell slitaz the disk it needs to write to is by simply modifying or adding an entry to the extlinux.conf file (which is located at /home/boot/extlinux). See also [[https://maille.slitaz.org/|here]]. This method is the only method that doesn't require typing in commands every time you boot and require persistence (more automated). Note that the same method can also be followed when you have a FAT32/non-slim login manager setup, however, you will then need to do the changes in the syslinux.cfg file (located at /home/boot/syslinux), see [[https://superuser.com/questions/123399/how-to-make-slitaz-usb-persistent|here]], and not extlinux.conf. To change the extlinux.conf or syslinux.cfg (which one you need to alter will depend on the filesystem you use), you need to pick one of the slitaz entries you're currently not using at the boot screen (i.e. base, justx, ... entry), and then modify it. Alternatively, you can make an entirely new label as well (see [[https://maille.slitaz.org/|here]]. Make it look like this: |
| |
| LABEL my slitaz\\ | LABEL my slitaz\\ |
| |
| ==Method 3== | ==Method 3== |
| The last method is done by simply typing in some commands at the terminal (see [[http://forum.slitaz.org/topic/slitaz-on-usb-persistent|here]]. | The last method is done by simply typing in some commands at the terminal (see [[https://maille.slitaz.org/|here]]. |
| So, after booting into slitaz, just bring up the terminal, log in as root, and then type: | So, after booting into slitaz, just bring up the terminal, log in as root, and then type: |
| |
| vga=normal autologin home=2c55c420-760a-4fa3-871b-64191dcc338a BOOT_IMAGE=/boot/bzImage | vga=normal autologin home=2c55c420-760a-4fa3-871b-64191dcc338a BOOT_IMAGE=/boot/bzImage |
| |
| <note important>Having read the "http://doc.slitaz.org/en:handbook:hacklivecd#modify-the-isolinux-configuration" page, I seem to understand that what was the "main boot loader" was actually the isolinux boot loader, which in turn starts syslinux (with FAT32 usb sticks). With ext-formatted drives, syslinux itself then also starts extlinux before that boot loader can load slitaz. | <note important>Having read the "https://doc.slitaz.org/handbook/build.html page, I seem to understand that what was the "main boot loader" was actually the isolinux boot loader, which in turn starts syslinux (with FAT32 usb sticks). With ext-formatted drives, syslinux itself then also starts extlinux before that boot loader can load slitaz. |
| |
| Is this correct ? If so, update the text accordingly above. One really need to now this to know what files to edit. Also, is it possible to leave out booting the syslinux boot loader completely when booting a slitaz liveUSB stick formatted in ext3 ? If possible, I suppose one can just alter the isolinux files to accomplish this, and then make 2 versions of the customised slitaz distro if one wants to; knowlingly | Is this correct ? If so, update the text accordingly above. One really need to now this to know what files to edit. Also, is it possible to leave out booting the syslinux boot loader completely when booting a slitaz liveUSB stick formatted in ext3 ? If possible, I suppose one can just alter the isolinux files to accomplish this, and then make 2 versions of the customised slitaz distro if one wants to; knowlingly |
| |
| ==See also== | ==See also== |
| * [[en:handbook:hacklivecd#modify-the-isolinux-configuration|Modifying isolinux]] (isolinux appearantly being the "main boot loader" which starts syslinux -syslinux itself starting extlinux if you have an ext-formatted USB drive with slitaz on it | * [[https://doc.slitaz.org/handbook/build.html|Modifying]]solinux]] (isolinux appearantly being the "main boot loader" which starts syslinux -syslinux itself starting extlinux if you have an ext-formatted USB drive with slitaz on it |
| |
| ==Additional links/references== | ==Additional links/references== |
| * http://forum.slitaz.org/topic/slitaz-40-liveusb-writefs | * https://maille.slitaz.org/ |
| * http://forum.slitaz.org/topic/a-couple-of-newbie-questions | * https://maille.slitaz.org/ |
SliTaz Wiki