[SOLVED] Slackware Live script

business_kid · 01-13-2022, 12:04 PM

Maybe I'm having delusions of competence, but I'm getting this error after trying all the obvious stuff

Code:

bash-5.1$ cd Downloads/liveslak-1.5.0
bash-5.1$ sudo ./iso2usb.sh -d
#
# Removable devices detected on this computer:
# /dev/sdc : USB      SG Flash        : 30000 MB
# /dev/sr0 : TSSTcorp CDDVDW SN-208BB : 1023 MB
#
bash-5.1$ sudo ./iso2usb.sh -i /home/dec/Downloads/slackware-live-xfce-current.iso -p -o /dev/sdc
*** Unknown parameter '/dev/sdc'!

I have deleted my liveslak directory and untarred it afresh, checked for the device nodes (present & correct) and udev (running). I'm running Slackware-15-Current-RC1. I've tried it as sdb, and sdc, powered off the box, and both in X and from an agetty console. I've even tried with '-o' & '--outdev'

EDIT: I've even ran 'wipefs -a' to provide a clean sweep of filesystems, but the problem persists

camorri · 01-13-2022, 12:29 PM

This is my best guess.

I suspect the use of -p requires a name of the persistent file or directory. I would guess the -o is assumed to be the name. Hence, /dev/sdc is looked at as a parameter.

If your intention is to not specify a name for a file, the -P should word. ( thats capitial P ).

Hope this helps.

marav · 01-13-2022, 12:37 PM

You just need to specify the name of the directory

Code:

iso2usb.sh -i slackware64-live-lean-current.iso -p persist -o /dev/sda

Code:

blackstar :: ~ » ls /mnt/alien*
mnt/alienusb.8ZCM2M:
boot  liveslak  lost+found  persist

Windu · 01-13-2022, 01:44 PM

Quote:

Originally Posted by marav

You just need to specify the name of the directory

... or leave out that "-p" parameter completely. Then the script will use a baked-in name for the persistence directory.
There's a "-h" help function to the script.

Code:

#   -p|--persistence <name>    Custom path to the 'persistence' directory
#                              or containerfile (persistence by default).

business_kid · 01-14-2022, 06:33 AM

Yep. leaving out the '-p' sorted it. I evidently was having delusions of competence

.

business_kid · 01-15-2022, 11:31 AM

This threw up something interesting so I thought I'd add it.

Having a Raspberry Pi 4B , I've been doing a lot of block copying of media recently. Most distributions are offered as binary images, which I have been installing with

Code:

dd if=/path/to/Some_Image of=/dev/sdX bs=whatever status=progress OR
dd if=/path/to/Some_Image of=/dev/mmcblk0 bs=whatever status=progress

and for the RazPi, that's fine. It doesn't need anything fancy to boot a RazPi. But it somehow compromises the disk's ability to be used as a boot disk in a pc. SD cards aren't bootable anyhow, but usb disks copied in this fashion work fine as data disks, but won't boot the pc. They show as a valid option in the live usb boot menu, but no option works.

If anyone has the magic to reverse this, of course, I'd welcome it.

business_kid · 01-16-2022, 12:50 PM

I went one stage further with this:

All the partition tables start at sector 2048, skipping the 1st Meg. So I put in a compromised usb disk as sdb, and a known good liveslak usb drive as sdc. Then I ran

Code:

dd if=/dev/sdc of=/dev/sdb bs=512 count=2048

to rewrite sectors 0-2047. Again, it's seen as a bootable drive, but is not bootable.