Describe the -no-emul-boot mkisofs(8) option and use it in the example.

Also remove the -U option from the example, since it could create ISO
images that some systems could not boot from (besides, it is not used in
the FreeBSD src/release/i386/mkisoimages.sh script, and there probably
is a reason for that ;)

PR:		70952
Submitted by:	Jon Wallace <jon@whoweb.com>
Based on:	patch by Sebastian Schulze Struchtrup <seb@struchtrup.com>
This commit is contained in:
Peter Pentchev 2004-11-05 19:11:17 +00:00
parent ea0f10f559
commit e7cc0c839f
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=22794

View file

@ -1031,14 +1031,19 @@ umass0: detached</screen>
used to specify the location of the boot image for use in producing an
<quote>El Torito</quote> bootable CD. This option takes an
argument which is the path to a boot image from the top of the
tree being written to the CD. So, given that
tree being written to the CD. By default, &man.mkisofs.8; creates an
ISO image in the so-called <quote>floppy disk emulation</quote> mode,
and thus expects the boot image to be exactly 1200, 1440 or
2880&nbsp;KB in size. Some boot loaders, like the one used by the
FreeBSD distribution disks, do not use emulation mode; in this case,
the <option>-no-emul-boot</option> option should be used. So, if
<filename>/tmp/myboot</filename> holds a bootable FreeBSD system
with the boot image in
<filename>/tmp/myboot/boot/cdboot</filename>, you could produce the
image of an ISO 9660 file system in
<filename>/tmp/bootable.iso</filename> like so:</para>
<screen>&prompt.root; <userinput>mkisofs -U -R -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot</userinput></screen>
<screen>&prompt.root; <userinput>mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot</userinput></screen>
<para>Having done that, if you have <devicename>vn</devicename>
(FreeBSD&nbsp;4.X), or <devicename>md</devicename>