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

A first attempt on making bootable ISO images

Browse Source
This commit is contained in:
Thomas Schmitt
2008-09-26 16:14:21 +00:00
parent 1a0346a1a1
commit b2984efc9f
6 changed files with 344 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
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 19, 2008"
.TH XORRISO 1 "Sep 26, 2008"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -861,7 +861,7 @@ iso_rr_path.
-type type_letter
.br
matches only files files of the given type:
"block", "char", "dir", "pipe", "file", "link", "socket",
"block", "char", "dir", "pipe", "file", "link", "socket", "eltorito",
"Xotic" which eventually matches what is not matched by the other types.
.br
Only the first letter is interpreted. E.g.: -find / -type d
@ -1352,25 +1352,51 @@ xorriso adds the traditional 300k of padding by default to all images.
.br
For images which will never get to a CD it is safe to use -padding 0 .
.TP
\fB\-boot_image\fR "any"|"isolinux" "discard"|"keep"|"patch"
Defines the handling of an eventual boot image (El-Torito) which has been read
from an existing ISO image. All types ("any") can be discarded or kept
unaltered. The latter makes only sense if the format of the boot image is
\fB\-boot_image\fR "any"|"isolinux" "discard"|"keep"|"patch"|bootspec
Defines the handling of an eventual boot image (El-Torito) which has
been read from an existing ISO image or defines how to make a prepared
ISOLINUX file set bootable.
.br
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
The boot image type "isolinux" can be kept unaltered (not advisable), or
discarded, or it can be patched to match its relocation. In the latter case
the resulting ISO image is bootable if the boot image was really complying
to the isolinux standard.
.br
Creation of new boot images is not yet possible.
An existing boot image of type "isolinux" can be
kept unaltered (not advisable), or be discarded, or it can be patched
to match its relocation. In the latter case the resulting ISO image is
bootable if the boot image was really produced by ISOLINUX.
.br
CAUTION:
This is an expert option. xorriso is not an expert yet.
It cannot recognize the inner form of boot images.
This is an expert option.
xorriso cannot recognize the inner form of boot images.
So the user has already to know about the particular needs of the
bootimage which is present on the input media.
.br
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 (-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
-boot_image isolinux dir=/boot/isolinux
.br
It is possible to make several individual settings. E.g.
.br
-boot_image isolinux bin_path=/boot/isolinux/isolinux.bin
.br
-boot_image isolinux cat_path=/boot/isolinux/boot.cat
.br
-boot_image isolinux load_size=2048
.br
But that should hardly be necessary.
.br
CAUTION: xorriso only connects some ISOLINUX files to the El-Torito mechanism.
If the ISOLINUX setup was incorrect or if the given files are not by ISOLINUX
at all, then anything may happen when booting is attempted.
.TP
.B Exception processing:
.PP