[SOLVED] Trouble interpreting instructions for Live Slackware usb
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Trouble interpreting instructions for Live Slackware usb
Hi!
I am afraid I may be asking a pretty dumb question, but unfortunately I can't avoid it, as I need a persistent Live Slackware USB. I have made a couple in the past but I never cared whether they were persistent or not, before.
Will the following command produce a persistent USB?
Create a version of Slackware Live, where the stick is known to the system as '/dev/sdX. Note - the value for the output parameter is the device name of the stick and not one of its partitions!
# ./iso2usb.sh -i ~/download/slackware64-live-14.2.iso -o /dev/sdX
Create a Live with an encrypted /home (allocating 30% of the stick's free space for /home) and where the persistent data will be stored in a container file instead of a directory:
# ./iso2usb.sh -i slackware64-live-current.iso -o /dev/sdX -c 30% -P
You might have noticed that the “-P” parameter does not accept a size parameter. This is because the unencrypted container file is created as a 'sparse' file that starts at zero size and is allowed to grow dynamically to a maximum of 90% of the initial free space on the Linux partition of the stick.
-P --persistfile Use an unencrypted 'persistence' file insteadof a directory
(for use on FAT filesystem).
-p|--persistence <name> Custom name of the 'persistence' directory/file.
If it does not exist yet, create it manually.
The CD/DVD versions (and the USB stick if you configure it accordingly) operate without persistence, which means that all the changes you make to the OS are lost when you reboot.
as how to achieve it, but as stated previously, just a matter of curiosity, as I don't remember how I did it in the past.
-p|--persistence <name> Custom name of the 'persistence' directory/file.
If it does not exist yet, create it manually.
-P|--persistfile Use an unencrypted 'persistence' file instead
of a directory (for use on FAT filesystem).
Examples:
What/Who 'create it manually': the script,
or must the user, before running the script?
-P toggles from a persistent directory to a persistent file. -p <name> changes the name of the persistence directory/file from the default name persistence.
To disable persistence add nop to the boot loader config files on the usb or use dd/copy to put iso onto usb (will make usb read only).
Last edited by colorpurple21859; 10-07-2022 at 09:59 AM.
nop is one of the boot parameters for liveslak mentioned about the middle section of the liveslak documentation
Add nop as a kernel boot parameter to the linux line of the EFI/BOOT/grub.cfg file on the efi partition of the usb for uefi mode and the append line of boot/extlinux/menu/vesamenu.cfg on the liveslak partition for legacy mode
Or add nop as a boot option to the boot menu at start-up as a temporary fix.
Last edited by colorpurple21859; 10-07-2022 at 04:29 PM.
Is it OK to ask here what is the concrete, practical difference between using a file and using a directory for persistence?
The liveslak persistence directory is readily accessible when liveslak is auto-mounted with a file manager, whereas a persistence file requires an extra step of mounting to access the persistence files.
On a side note I think deleting the persistence directory/file will disable persistence, not sure if there is any downside to this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.