Can't get mkisofs to work,manpage useless.

minr · 03-01-2012, 01:13 PM

I admit to being slow, but: trying to make a simple eltorito emulation mode bootable cd; Have a 2.88 .img image, and for now only
need an empty data dir(just want to boot the image from the cd).
The problem is 'mkisofs'. Even tried putting both the dir and the .img into /usr/bin, where the mkisofs is located. The commandline:
mkisofs -b name.img -o someiso.iso dirname will always find the
dir ok, but inevitably ends with "uh oh, cannot find 'name.img'.
Have tried absolute paths, to no avail. The manpage for mkisofs is
totally incomprehensible, saying for '-b' option that the .img file must be specified relative to "the source path specified to mkisofs".
What is that, and who or what "specified it to mkisofs"?
What on earth am I doing wrong here? -minr.

kbp · 03-01-2012, 03:59 PM

As the error says, the boot image location is relative to the directory you're putting in the iso..

If the image file and dirname are in the current directory:

Code:

mv name.img dirname/
mkisofs -b name.img -o someiso.iso dirname

or:

Code:

mkdir dirname/boot
mv name.img dirname/boot/
mkisofs -b boot/name.img -o someiso.iso dirname

.. clearer ?

Found this in another one of my posts:

Code:

mkisofs -r -N -allow-leading-dots -d -J -T -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot \
 -V $(VERSION) -boot-load-size 4 -boot-info-table  -o $(TMPISO) .

minr · 03-01-2012, 05:14 PM

kbp,
that works!. Maybe it's just me, but couldn't the manpage have said; "put the img in the
dir"? The way they said it is j-u-u-ust a bit abstruse? Oh well, tnx for the tip.