From e7cc0c839f29250ebfc15cc9d5acf1af6d4e0689 Mon Sep 17 00:00:00 2001 From: Peter Pentchev Date: Fri, 5 Nov 2004 19:11:17 +0000 Subject: [PATCH] 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 Based on: patch by Sebastian Schulze Struchtrup --- en_US.ISO8859-1/books/handbook/disks/chapter.sgml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/disks/chapter.sgml b/en_US.ISO8859-1/books/handbook/disks/chapter.sgml index 72ffbb468d..61e1fd3c39 100644 --- a/en_US.ISO8859-1/books/handbook/disks/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/disks/chapter.sgml @@ -1031,14 +1031,19 @@ umass0: detached used to specify the location of the boot image for use in producing an El Torito 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 floppy disk emulation mode, + and thus expects the boot image to be exactly 1200, 1440 or + 2880 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 should be used. So, if /tmp/myboot holds a bootable FreeBSD system with the boot image in /tmp/myboot/boot/cdboot, you could produce the image of an ISO 9660 file system in /tmp/bootable.iso like so: - &prompt.root; mkisofs -U -R -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot + &prompt.root; mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot Having done that, if you have vn (FreeBSD 4.X), or md