Some documentation updates

This commit is contained in:
2010-04-26 17:56:06 +00:00
parent 37ca34038e
commit e79ee34d6c
6 changed files with 102 additions and 98 deletions

View File

@ -2173,7 +2173,8 @@ Each -boot_image command has two arguments: type and setting. More than one
-boot_image command may be used to define the handling of one or more boot
images. Sequence matters.
.br
Types "isolinux" and "grub" care for known peculiarities. Type "any" makes
Types \fBisolinux\fR and \fBgrub\fR care for known peculiarities.
Type \fBany\fR makes
no assumptions about the origin of the boot images.
.br
@ -2187,10 +2188,10 @@ 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".
.br
"show_status" will print what is known about the loaded image
\fBshow_status\fR will print what is known about the loaded image
and its designated fate.
.br
"next" ends the definition of a boot image and starts a new one.
\fBnext\fR ends the definition of a boot image and starts a new one.
Any following -bootimage bootspecs will affect the new image.
The first "next" discards eventually loaded boot images and their
catalog.
@ -2202,8 +2203,8 @@ boot images which are present on the input media.
Most safe is the default: -boot_image "any" "discard".
.br
A bootspec is a word of the form name=value and is used to describe the
parameters of a boot image by an El Torito record and eventually a MBR.
A \fBbootspec\fR is a word of the form name=value and is used to describe
the parameters of a boot image by an El Torito record and eventually a MBR.
The names "dir", "bin_path", "efi_path" lead to El Torito bootable images.
Name "system_area" activates a given file as MBR.
.br
@ -2229,48 +2230,48 @@ which bundles these individual settings:
.br
-boot_image any boot_info_table=on
.br
"bin_path=" depicts the boot image file, a binary program which is to be
\fBbin_path=\fR depicts the boot image file, a binary program which is to be
started by the hardware boot facility (e.g. the BIOS) at boot time.
.br
"efi_path=" depicts a boot image file that is ready for EFI booting.
\fBefi_path=\fR depicts a boot image file that is ready for EFI booting.
Its load_size is determined automatically, no boot info table gets
written, platform_id is 0xef.
.br
An El Torito boot catalog file gets inserted into the ISO image with address
"cat_path=" at -commit time.
\fBcat_path=\fR at -commit time.
It is subject to normal -overwrite and -reassure processing if there is already
a file with the same name.
The catalog lists the boot images and is read by the boot facility to choose
one of the boot images.
.br
"load_size=" is a value which depends on the boot image. Default 2048 should
be overridden only if a better value is known.
\fBload_size=\fR is a value which depends on the boot image.
Default 2048 should be overridden only if a better value is known.
.br
"boot_info_table=on" may be used to apply patching to a boot image which
\fBboot_info_table=on\fR may be used to apply patching to a boot image which
is given by "any" "bin_path=". "boot_info_table=off" disables patching.
.br
"platform_id=" defines by two hex digits the Platform ID of the boot image.
"00" is 80x86 PC-BIOS, "01" is PowerPC, "02" is Mac, "ef" is EFI.
\fBplatform_id=\fR defines by two hex digits the Platform ID of the
boot image. "00" is 80x86 PC-BIOS, "01" is PowerPC, "02" is Mac, "ef" is EFI.
.br
"id_string="text|56_hexdigits defines the ID string of the boot catalog
\fBid_string=\fRtext|56_hexdigits defines the ID string of the boot catalog
section where the boot image will be listed. If the value consists of 56
characters [0-9A-Fa-f] then it is converted into 28 bytes, else the first
28 characters become the ID string.
The ID string of the first boot image becomes the overall catalog ID.
It is limited to 24 characters. Other id_strings become section IDs.
.br
"sel_crit="hexdigits defines the Selection Criteria of the boot image.
\fBsel_crit=\fRhexdigits defines the Selection Criteria of the boot image.
Up to 20 bytes get read from the given characters [0-9A-Fa-f].
They get attributed to the boot image entry in the catalog.
.br
"discard" gives up an existing boot catalog and its boot images.
\fBdiscard\fR gives up an existing boot catalog and its boot images.
.br
"keep" keeps or copies boot images unaltered and writes a new catalog.
\fBkeep\fR keeps or copies boot images unaltered and writes a new catalog.
.br
"patch" applies boot info table patching of existing boot images.
\fBpatch\fR applies boot info table patching to existing boot images.
.br
"system_area="disk_path copies at most 32768 bytes from the given disk file to
the very start of the ISO image.
\fBsystem_area=\fRdisk_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.
.br
@ -2279,8 +2280,8 @@ to the ISO image.
.br
-boot_image isolinux system_area= implies "partition_table=on".
.br
"partition_table=on" causes a simple partition table to be written into bytes
446 to 511 of the System Area.
\fBpartition_table=on\fR causes a simple partition table to be written
into bytes 446 to 511 of the System Area.
.br
With type "isolinux" it shows a partition that begins at byte 0 and it causes
the LBA of the first boot image to be written into the MBR. For the first