Some documentation updates
This commit is contained in:
@ -2621,7 +2621,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.
|
||||
@*
|
||||
Types "isolinux" and "grub" care for known peculiarities. Type "any" makes
|
||||
Types @strong{isolinux} and @strong{grub} care for known peculiarities.
|
||||
Type @strong{any} makes
|
||||
no assumptions about the origin of the boot images.
|
||||
@*
|
||||
@sp 1
|
||||
@ -2636,10 +2637,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".
|
||||
@*
|
||||
"show_status" will print what is known about the loaded image
|
||||
@strong{show_status} will print what is known about the loaded image
|
||||
and its designated fate.
|
||||
@*
|
||||
"next" ends the definition of a boot image and starts a new one.
|
||||
@strong{next} 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.
|
||||
@ -2652,8 +2653,8 @@ Most safe is the default: -boot_image "any" "discard".
|
||||
@*
|
||||
@sp 1
|
||||
|
||||
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 @strong{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.
|
||||
The names "dir", "bin_path", "efi_path" lead to El Torito bootable images.
|
||||
Name "system_area" activates a given file as MBR.
|
||||
@*
|
||||
@ -2679,50 +2680,50 @@ which bundles these individual settings:
|
||||
@*
|
||||
-boot_image any boot_info_table=on
|
||||
@*
|
||||
"bin_path=" depicts the boot image file, a binary program which is to be
|
||||
@strong{bin_path=} 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.
|
||||
@*
|
||||
"efi_path=" depicts a boot image file that is ready for EFI booting.
|
||||
@strong{efi_path=} 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.
|
||||
@*
|
||||
An El Torito boot catalog file gets inserted into the ISO image with address
|
||||
"cat_path=" at -commit time.
|
||||
@strong{cat_path=} 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.
|
||||
@*
|
||||
"load_size=" is a value which depends on the boot image. Default 2048 should
|
||||
be overridden only if a better value is known.
|
||||
@strong{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
|
||||
@strong{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.
|
||||
@*
|
||||
"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.
|
||||
@strong{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.
|
||||
@*
|
||||
"id_string="text|56_hexdigits defines the ID string of the boot catalog
|
||||
@strong{id_string=}text|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.
|
||||
@*
|
||||
"sel_crit="hexdigits defines the Selection Criteria of the boot image.
|
||||
@strong{sel_crit=}hexdigits 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.
|
||||
@*
|
||||
"discard" gives up an existing boot catalog and its boot images.
|
||||
@strong{discard} gives up an existing boot catalog and its boot images.
|
||||
@*
|
||||
"keep" keeps or copies boot images unaltered and writes a new catalog.
|
||||
@strong{keep} keeps or copies boot images unaltered and writes a new catalog.
|
||||
@*
|
||||
"patch" applies boot info table patching to existing boot images.
|
||||
@strong{patch} applies boot info table patching to existing boot images.
|
||||
@*
|
||||
@cindex System area, _definiton
|
||||
@cindex MBR, set, -boot_image system_area=
|
||||
"system_area="disk_path copies at most 32768 bytes from the given disk file to
|
||||
the very start of the ISO image.
|
||||
@strong{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.
|
||||
@*
|
||||
@ -2732,8 +2733,8 @@ to the ISO image.
|
||||
-boot_image isolinux system_area= implies "partition_table=on".
|
||||
@*
|
||||
@cindex Partition table, _definiton
|
||||
"partition_table=on" causes a simple partition table to be written into bytes
|
||||
446 to 511 of the System Area.
|
||||
@strong{partition_table=on} causes a simple partition table to be written
|
||||
into bytes 446 to 511 of the System Area.
|
||||
@*
|
||||
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
|
||||
|
Reference in New Issue
Block a user