diff --git a/libisoburn/trunk/xorriso/convert_man_to_html.sh b/libisoburn/trunk/xorriso/convert_man_to_html.sh index a87749f9..98e0668f 100755 --- a/libisoburn/trunk/xorriso/convert_man_to_html.sh +++ b/libisoburn/trunk/xorriso/convert_man_to_html.sh @@ -51,7 +51,7 @@ then -e 's/Libburn drives:<\/b>/\ 
Libburn drives:<\/b>/' \ -e 's/^-dev /\ \ -dev /' \ -e 's/^-devices /\ \ -devices /' \ - -e 's/Rock Ridge, POSIX, X\/Open:<\/b>/\ 
Rock Ridge, POSIX, X\/Open:<\/b>/' \ + -e 's/Rock Ridge, POSIX, X\/Open, and El Torito:<\/b>/\ 
Rock Ridge, POSIX, X\/Open, and El Torito:<\/b>/' \ -e 's/Command processing:<\/b>/\ 
Command processing:<\/b>/' \ -e 's/Dialog, Readline, Result pager:<\/b>/\ 
Dialog, Readline, Result pager:<\/b>/' \ -e 's/Aquiring source and target drive:<\/b>/\ 
Aquiring source and target drive:<\/b>
\ 
/' \ diff --git a/libisoburn/trunk/xorriso/xorriso.1 b/libisoburn/trunk/xorriso/xorriso.1 index 3fe2a231..8611efa4 100644 --- a/libisoburn/trunk/xorriso/xorriso.1 +++ b/libisoburn/trunk/xorriso/xorriso.1 @@ -2,7 +2,7 @@ .\" First parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" other parameters are allowed: see man(7), man(1) -.TH XORRISO 1 "Sep 30, 2008" +.TH XORRISO 1 "Oct 02, 2008" .\" Please adjust this date whenever revising the manpage. .\" .\" Some roff macros, for reference: @@ -79,7 +79,7 @@ Creating, Growing, Modifying, Blind Growing .br Libburn drives .br -Rock Ridge, POSIX, X/Open +Rock Ridge, POSIX, X/Open, and El Torito .br Command processing .br @@ -327,7 +327,7 @@ One may use option .B -ban_stdio_write to surely prevent this risk and to allow only MMC drives. .SS -.B Rock Ridge, POSIX, X/Open: +.B Rock Ridge, POSIX, X/Open, and El Torito: .br .B Rock Ridge is the name of a set of additional informations which enhance @@ -342,6 +342,20 @@ xorriso is not named "porriso" because POSIX only guarantees 14 characters of filename length. It is the X/Open System Interface standard XSI which demands a file name length of up to 255 characters and paths of up to 1024 characters. Rock Ridge fulfills this demand. +.PP +An +.B El Torito +boot record connects a boot image, which is a binary program plus some +other files stored in the ISO image, with the bootstrapping facility of +contemporary computers. +The content of the boot image files is not in the scope of El Torito. +.br +Most bootable Linux CDs are equipped with ISOLINUX boot images. xorriso is +able to create or maintain an El Torito object which makes such an image +bootable. Emulation -as mkisofs supports the example options out of the +ISOLINUX wiki. +.br +The support for other boot image types is sparse. .SS .B Command processing: .br @@ -397,7 +411,7 @@ to make dialog more comfortable. .PP Readline is an enhancement for the input line. You may know it already from the bash shell. Whether it is available in xorriso depends on the availability -of package readline-dev at the time when xorriso was built from its sourcecode. +package readline-dev at the time when xorriso was built from its sourcecode. .br It allows to move the cursor over the text in the line by help of the Leftward and the Rightward arrow key. @@ -1356,28 +1370,15 @@ For images which will never get to a CD it is safe to use -padding 0 . .TP .B El Torito bootable ISO images: .PP -An El Torito file object connects a boot image, which is a set of binaries -and other files in the ISO image, with the bootstrapping facility of -contemporary computers. -The content of the boot image files is not in the scope of El Torito. -.br -Most bootable Linux CDs are equipped with ISOLINUX boot images. xorriso is -able to create or maintain an El Torito object which makes such an image -bootable. Emulation -as mkisofs supports the example options out of the -ISOLINUX wiki. -.br -The support for other boot image types is sparse. -.br - Contrary to published specifications many BIOSes will load an El Torito object from the first session on media and not from the last one, which gets mounted by default. This makes no problems with overwriteable media, because they appear to inadverted readers as one single session. .br -With multi-session media CD-R[W], DVD-R[W], DVD+R, this implies that the whole -bootable system has to reside already in the first session and that the last -session still has to bear all files which the booted system expects after -eventually mounting the ISO image. +But with multi-session media CD-R[W], DVD-R[W], DVD+R, it implies that the +whole bootable system has to reside already in the first session and that +the last session still has to bear all files which the booted system expects +after eventually mounting the ISO image. .br If ISOLINUX is known to be present on media then it is advised to patch it when a follow-up session gets written. But one should not rely on the @@ -1420,7 +1421,7 @@ In that case it suffices to use as bootspec the text "dir=/isolinux" or .br -boot_image isolinux dir=/boot/isolinux .br -It is possible to do this by several individual settings. E.g. +which bundles these individual settings: .br -boot_image isolinux bin_path=/boot/isolinux/isolinux.bin .br @@ -1428,10 +1429,11 @@ It is possible to do this by several individual settings. E.g. .br -boot_image isolinux load_size=2048 .br -But that should hardly be necessary. +bin_path depicts the binary program which is to be started by the BIOS at +boot time. It is among the files produced by ISOLINUX. .br -A El Torito boot catalog file gets inserted into the ISO image at -commit time. -Its location is the effective cat_path= . +An El Torito boot catalog file gets inserted into the ISO image with address +cat_path at -commit time. It is subject to normal -overwrite and -reassure processing if there is already a file with the same name. .br