LinuxQuestions.org - [SOLVED] Trouble interpreting instructions for Live Slackware usb

- Slackware - Installation (https://www.linuxquestions.org/questions/slackware-installation-40/)

- - Trouble interpreting instructions for Live Slackware usb (https://www.linuxquestions.org/questions/slackware-installation-40/trouble-interpreting-instructions-for-live-slackware-usb-4175717501/)

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?

Code:

# ./iso2usb.sh -i ~/download/slackware64-live-daw-current.iso -o /dev/sdX

And if so how does one produce a non persistent one? (this one is just a matter of curiosity).

It might help provide some context if you were to provide a link the instructions you are trying to follow.

My Bad ! I apologize.

I edited what had become a too long post, and in the process I eliminated the link:
https://docs.slackware.com/slackware:liveslak

and the parts I was not sure of how to interpret:

Quote:

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.

Thanks for caring.

This also is not clear to me:

Quote:

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.

I think it's just the presence or absence of the -p
(like the presence or absence of -l on ls gives you a long listing or not)

You can't write on a typical CD.
I think 'accordingly' meant without the -p

I'm learning too! Slackware is amazing! You'll get there!

But I always mind!!! :confused:

Code:

-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?

Why doesn't the -P (uppercase) take a file name?

-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).

Thanks guys. I guess I understand it now.

Is it OK to ask here what is the concrete, practical difference between using a file and using a directory for persistence?

...And is the nop parameter valid for different bootloaders, or is it limited to some preferred ones?

Pardon me if I am too curious.

Quote:

nop

must be a typo here. It is a CPU instruction operation code!!!
https://en.m.wikipedia.org/wiki/Opcode

Quote:

Originally Posted by colorpurple21859 (Post 6384888)

... To disable persistence
add nop
to the boot loader config files on the usb ...

What do all of you mean by: bootloader?
grub? loadlin? (I couldn't find the three character token ' nop ' in any documentation)
https://en.m.wikipedia.org/wiki/Bootloader
https://en.m.wikipedia.org/wiki/Comp...of_bootloaders

I don't think you mean a kernel boot parameter:
https://www.kernel.org/doc/html/v6.0...arameters.html

:confused: :banghead: :newbie:S :cry: wanna know :study: :scratch:
In words: :confused: :banghead: :newbie:S :cry: wanna know :study: :scratch:

Added: while desperately googling, I did find something that mentions

Quote:

'nopersistent'

https://askubuntu.com/questions/1181...h-ubuntu-19-10

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.

Quote:

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.

@colorpurple21859: thanks for once again clarifying.

Marking as solved.