How to create 4MLinux Live USB *without* unetbootin?

jaimet · 04-19-2020, 06:32 PM

Hi.

I can't run unetbootin (all my machines run current debian stable, buster, and debian dropped unetbootin some time ago) and I would like to create a 4MLinux Live USB.

Is there another way that I can create a 4MLinux Live USB *without* using unetbootin?

(I know how to use dd, but apparently the iso files can not be hybridised so dd can not be used).

TIA

BW-userx · 04-19-2020, 06:56 PM

you can try installing it directly onto a USB stick, then you'll have a full blown OS on a stick. yes, it is doable.

jaimet · 04-20-2020, 03:28 AM

Quote:

Originally Posted by BW-userx

you can try installing it directly onto a USB stick, then you'll have a full blown OS on a stick. yes, it is doable.

I don't understand what installing it "directly" means. Do you know how I would do this?

shruggy · 04-20-2020, 06:54 AM

Try MultiBootUSB or just download UNetbootin binary from their website. You also may try balenaEtcher (AppImage)

Directly probably means using dd from the command line.

fatmac · 04-20-2020, 08:34 AM

Quote:

(I know how to use dd, but apparently the iso files can not be hybridised so dd can not be used).

Are you sure, have you tried running isohybrid against the .iso file(?).

(I always use dd to create my pendrives.)

BW-userx · 04-20-2020, 09:12 AM

you got two usb ports, one computer, plug in the boot install usb stick into one usb port, then the blank usb stick into the other usb port, then just use the computer to install it onto the blank usb stick.

Quote:

usb Stick1 <------ PC --------> usb Stick2

then you'll have a full blown OS on a stick instead of a PC.

jaimet · 04-22-2020, 04:58 AM

Quote:

Originally Posted by fatmac

Are you sure

Not entirely, no, but then I'm never really sure of anything so I'm not going to let that put me off.

Quote:

Originally Posted by fatmac

have you tried running isohybrid against the .iso file(?).

Yes:

Code:

$ isohybrid 4MLinux-32.1-64bit.iso
isohybrid: 4MLinux-32.1-64bit.iso: unexpected boot catalogue parameters

Quote:

Originally Posted by fatmac

(I always use dd to create my pendrives.)

You may well, but if the iso file has no boot sector, then there's not a lot of point because a classic bios will never be able to boot off it (chain-loading and other forms of magic notwithstanding). Note that the word "bootable" in the following output really means "bootable, but only when you burn this iso file to optical media" (note to self: do people still use optical media?):

Code:

$ file 4MLinux-32.1-64bit.iso
4MLinux-32.1-64bit.iso: ISO 9660 CD-ROM filesystem data 'disks' (bootable)

cf.

Code:

$ file grml96-full_2018.12.iso 
grml96-full_2018.12.iso: DOS/MBR boot sector; ...

With the help of the following links, repacking/fixing the 4MLinux isos "is left as an exercise for the reader"

Why is it impossible to hybridise 4mlinux? (It isn't impossible - you just can't use "isohybrid image.iso" to do it. See next link for more info...)
A superb DIY "how to build from Linux an ISO hybrid image"
This script may help - I don't have the time to work through it properly, but it looks like it might be useful.
"The BIOS/MBR Boot Process" in the "NeoSmart Knowledgebase"
And, of course, perl source, c source and documentation.