New -as mkisofs options -G and --protective-msdos-label for GRUB
This commit is contained in:
@ -1,5 +1,5 @@
|
||||
This is xorriso.info, produced by makeinfo version 4.8 from
|
||||
./xorriso.texi.
|
||||
This is xorriso/xorriso.info, produced by makeinfo version 4.8 from
|
||||
./xorriso/xorriso.texi.
|
||||
|
||||
INFO-DIR-SECTION Archiving
|
||||
START-INFO-DIR-ENTRY
|
||||
@ -68,7 +68,7 @@ Changes file properties in the ISO image.
|
||||
Updates ISO subtrees incrementally to match given disk subtrees.
|
||||
Writes result either as completely new image or as add-on session to
|
||||
optical media or filesystem objects.
|
||||
Can activate ISOLINUX boot images via El Torito.
|
||||
Can activate ISOLINUX and GRUB boot images via El Torito.
|
||||
Can perform multi-session tasks as emulation of mkisofs and cdrecord.
|
||||
Can record and restore hard links and ACL.
|
||||
Content may get zisofs compressed or filtered by external processes.
|
||||
@ -333,10 +333,13 @@ and paths of up to 1024 characters. Rock Ridge fulfills this demand.
|
||||
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.
|
||||
Most bootable GNU/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. For details see option -boot_image. Emulation
|
||||
-as mkisofs supports the example options out of the ISOLINUX wiki.
|
||||
Most bootable GNU/Linux CDs are equipped with ISOLINUX or GRUB boot
|
||||
images. xorriso is able to create or maintain an El Torito object
|
||||
which makes such an image bootable. For details see option -boot_image.
|
||||
It is possible to make ISO images bootable from USB stick or other
|
||||
hard-disk-like media by -boot_image argument system_area= .
|
||||
Emulation -as mkisofs supports the example options out of the ISOLINUX
|
||||
wiki. It also supports the options used in GRUB script grub-mkrescue.
|
||||
The support for other boot image types is sparse.
|
||||
|
||||
*ACL* are an advanced way of controlling access permissions to file
|
||||
@ -569,7 +572,7 @@ image by aquiring an input drive. In rare cases it is desirable to
|
||||
activate them only after image loading.
|
||||
|
||||
-load entity id
|
||||
Load a particular (possibly outdated) ISO image from -dev or
|
||||
Load a particular (possibly outdated) ISO session from -dev or
|
||||
-indev. Usually all available sessions are shown with option -toc.
|
||||
entity depicts the kind of addressing. id depicts the particular
|
||||
address. The following entities are defined:
|
||||
@ -1889,26 +1892,35 @@ 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.
|
||||
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
|
||||
capability to influence the bootability of the existing sessions,
|
||||
unless one can assume overwriteable media.
|
||||
If a boot image from ISOLINUX or GRUB 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 capability to influence the bootability
|
||||
of the existing sessions, unless one can assume overwriteable media.
|
||||
|
||||
-boot_image "any"|"isolinux"
|
||||
-boot_image "any"|"isolinux"|"grub"
|
||||
"discard"|"keep"|"patch"|"show_status"|bootspec
|
||||
Define the handling of an eventual El Torito object which has been
|
||||
read from an existing ISO image or define how to make a prepared
|
||||
ISOLINUX file set bootable.
|
||||
|
||||
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.
|
||||
With any type, "show_status" will print what is known about the
|
||||
loaded image and its designated fate.
|
||||
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.
|
||||
Define the handling of an eventual El Torito boot image object
|
||||
which has been read from an existing ISO image or define how to
|
||||
make a prepared boot image file set bootable. Such file sets get
|
||||
produced by ISOLINUX or GRUB.
|
||||
Each -boot_image command has two arguments: type and setting. More
|
||||
than one -boot_image command may be used to define the handling.
|
||||
Sequence matters.
|
||||
Types "isolinux" and "grub" care for known peculiarities. Type
|
||||
"any" makes no assumptions about the origin of the boot image.
|
||||
|
||||
El Torito boot images of any type can be newly inserted, or
|
||||
discarded, or patched, or kept unaltered. The latter is only safe
|
||||
if the format of the boot image is relocatable without content
|
||||
changes.
|
||||
Some boot images contain a boot info table, which needs to be
|
||||
patched when the boot image gets newly introduced into the ISO
|
||||
image or if an existing image gets relocated. This is
|
||||
automatically done if type "isolinux" or "grub" is given, but not
|
||||
with "any".
|
||||
"show_status" will print what is known about the loaded image and
|
||||
its designated fate.
|
||||
CAUTION: 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 boot image which is present on the
|
||||
@ -1916,29 +1928,51 @@ unless one can assume overwriteable media.
|
||||
Most safe is the default: -boot_image "any" "discard".
|
||||
|
||||
A bootspec is a word of the form name=value and is used to
|
||||
describe the activation of a ISOLINUX boot image by an El Torito
|
||||
record. The names "dir" and "bin_path" lead to boot image
|
||||
activation.
|
||||
describe the activation of a boot image by an El Torito record and
|
||||
eventually a MBR. The names "dir" and "bin_path" lead to El
|
||||
Torito boot image activation. Name "system_area" activates the
|
||||
given file as MBR.
|
||||
On all media types this is possible 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.
|
||||
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 in /boot/isolinux . In that case
|
||||
it suffices to use as bootspec the text "dir=/isolinux" or
|
||||
The boot image and its supporting files have to be added to the
|
||||
ISO image by normal means (image loading, -map, -add, ...). In
|
||||
case of ISOLINUX the files should reside either in ISO image
|
||||
directory /isolinux or in /boot/isolinux . In that case it
|
||||
suffices to use as bootspec the text "dir=/isolinux" or
|
||||
"dir=/boot/isolinux". E.g.:
|
||||
-boot_image isolinux dir=/boot/isolinux
|
||||
which bundles these individual settings:
|
||||
-boot_image isolinux bin_path=/boot/isolinux/isolinux.bin
|
||||
-boot_image isolinux cat_path=/boot/isolinux/boot.cat
|
||||
-boot_image isolinux load_size=2048
|
||||
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.
|
||||
-boot_image any boot_info_table=on
|
||||
"bin_path=" depicts the binary program which is to be started by
|
||||
the BIOS at boot time.
|
||||
An El Torito boot catalog file gets inserted into the ISO image
|
||||
with address cat_path at -commit time. It is subject to normal
|
||||
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.
|
||||
"load_size=" is a value which depends on the boot image. Default
|
||||
2048 should be overridden only if a better value is known.
|
||||
"boot_info_table=on" may be used to apply patching to a boot image
|
||||
which is given by "any" "bin_path=". "boot_info_table=off"
|
||||
disables patching.
|
||||
"discard" gives up an existing boot image.
|
||||
"keep" keeps or copies an existing boot image unaltered.
|
||||
"patch" applies boot info table patching if an existing boot image
|
||||
gets copied to a new location.
|
||||
"system_area="disk_path copies at most 32768 bytes from the given
|
||||
disk file to the very start of the ISO image. This System Area is
|
||||
reserved for system dependent boot software, e.g. an MBR which can
|
||||
be used to boot from USB stick or hard disk.
|
||||
Other than a El Torito boot image, the file disk_path needs not to
|
||||
be added to the ISO image.
|
||||
"partition_table=on" causes a simple partition table to be written
|
||||
into bytes 446 to 511 of the System Area. It shows a single
|
||||
partiton which starts at byte 512 and ends where the ISO image
|
||||
ends.
|
||||
|
||||
|
||||
File: xorriso.info, Node: Charset, Next: Exception, Prev: Bootable, Up: Options
|
||||
@ -3683,7 +3717,7 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
|
||||
|