libburnia/legacy
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Adjustments about -boot_image after testing with various media types

Browse Source
This commit is contained in:
Thomas Schmitt
2008-09-30 10:28:46 +00:00
parent a7a60d4e4d
commit 85b45fce95
4 changed files with 36 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

36
libisoburn/trunk/xorriso/xorriso.1
View File

@ -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 26, 2008"
.TH XORRISO 1 "Sep 30, 2008"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -1367,6 +1367,22 @@ bootable. Emulation -as mkisofs supports the example options out of the
ISOLINUX wiki.
.br
The support for other boot image types is sparse.
.br
Typically a BIOS 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.
.br
If ISOLINUX is known to be present on appendable media then it is advised
to patch it when a new session gets written. But one should not rely on the
capability to influence the bootability of the existing sessions, unless one
can assume overwriteable media.
.TP
\fB\-boot_image\fR "any"|"isolinux" "discard"|"keep"|"patch"|bootspec
Defines the handling of an eventual El Torito object which has
@ -1378,7 +1394,7 @@ All types ("any") of El Torito boot images can be discarded or kept unaltered.
The latter makes only sense if the format of the boot image is
relocatable without content changes.
.br
An existing boot image of type "isolinux" can be discarded, or it can be
An existing boot image of type "isolinux" can be discarded or it can be
patched to match its relocation. In the latter case the resulting ISO image
stays bootable if the boot image was really produced by ISOLINUX.
.br
@ -1391,12 +1407,14 @@ boot image which is present on the input media.
Most safe is the default: "any" "discard".
.br
Regardless whether an El Torito boot image was detected or not, it is possible
to activate a set of ISOLINUX files for booting. An existing boot image gets
discarded, then.
The files have to be added to the ISO image by normal means (image loading,
-map, -add, ...) and should reside either in ISO image directory /isolinux or
/boot/isolinux .
On all media types it is possible to activate a set of ISOLINUX files
for booting within the first session. In further sessions an existing boot
image can get replaced by a new one, but depending on the media type
this may have few effect at boot time. See above.
.br
The ISOLINUX files have to be added to the ISO image by normal means
(image loading, -map, -add, ...) and should reside either in ISO image
directory /isolinux or /boot/isolinux .
In that case it suffices to use as bootspec the text "dir=/isolinux" or
"dir=/boot/isolinux". E.g.:
.br
@ -2637,7 +2655,7 @@ to read and execute lines from the following files:
.br
The files are read in the sequence given above, but none of them is required
for xorriso to function properly.
.TP
.SS
.B Runtime control files:
.br
The default setting of -check_media abort_file= is: