Argument "." for system area import commands
This commit is contained in:
@ -50,7 +50,7 @@
|
||||
@c man .\" First parameter, NAME, should be all caps
|
||||
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
@c man .\" other parameters are allowed: see man(7), man(1)
|
||||
@c man .TH XORRISO 1 "Version 1.3.9, Sep 28, 2014"
|
||||
@c man .TH XORRISO 1 "Version 1.3.9, Oct 28, 2014"
|
||||
@c man .\" Please adjust this date whenever revising the manpage.
|
||||
@c man .\"
|
||||
@c man .\" Some roff macros, for reference:
|
||||
@ -3427,13 +3427,12 @@ capability to influence the bootability of the existing sessions, unless one
|
||||
can assume overwriteable media.
|
||||
@*
|
||||
There are booting mechanisms which do not use an El Torito record but rather
|
||||
start at the first bytes of the image: PC-BIOS MBR for hard-disk-like devices,
|
||||
start at the first bytes of the image: PC-BIOS MBR or EFI GPT for
|
||||
hard-disk-like devices,
|
||||
APM partition entries for Macs which expect HFS+ boot images,
|
||||
MIPS Volume Header for old SGI computers, DEC Boot Block for old DECstation,
|
||||
SUN Disk Label for SPARC machines, HP-PA boot sector for HP PA-RISC machines.
|
||||
@*
|
||||
The boot firmware EFI may use programs which are located in a FAT filesystem
|
||||
and announced by an MBR partition table entry.
|
||||
@*
|
||||
@table @asis
|
||||
@sp 1
|
||||
@c man .TP
|
||||
@ -3445,10 +3444,15 @@ and announced by an MBR partition table entry.
|
||||
"discard"|"keep"|"patch"|"show_status"|bootspec|"next"
|
||||
@*
|
||||
@sp 1
|
||||
Define the handling of a set of El Torito boot images 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.
|
||||
Define the equipment of the emerging filesystem with boot entry points.
|
||||
@*
|
||||
With systems which boot via BIOS or EFI this is a set of El Torito
|
||||
boot images, possibly MBR boot code, and possibly partition tables of
|
||||
type MBR, GPT, or APM.
|
||||
Such file sets get produced by boot loader systems like ISOLINUX or GRUB.
|
||||
@*
|
||||
@sp 1
|
||||
|
||||
Each -boot_image command has two parameters: type and setting. More than one
|
||||
-boot_image command may be used to define the handling of one or more boot
|
||||
images. Sequence matters.
|
||||
@ -3459,10 +3463,22 @@ no assumptions about the origin of the boot images.
|
||||
@*
|
||||
@sp 1
|
||||
|
||||
El Torito boot images of any type can be newly inserted, or discarded,
|
||||
or patched, or kept unaltered.
|
||||
Whether to patch or to keep depends on whether
|
||||
the boot images contain boot info tables.
|
||||
When loading an ISO filesystem, system area and El Torito boot images get
|
||||
loaded, too. The default behavior is not to write loaded El Torito boot images
|
||||
and to write the loaded system area content without alterations.
|
||||
@*
|
||||
@strong{discard} gives up the El Torito boot catalog and its boot images.
|
||||
regardless whether loaded from an ISO filesystem or defined by commands.
|
||||
Any BIOS or EFI related boot options get revoked.
|
||||
Nevertheless, loaded system area data stay valid. If desired, they have to be
|
||||
erased by
|
||||
@*
|
||||
-boot_image any system_area=/dev/zero
|
||||
@*
|
||||
@strong{keep} keeps or copies El Torito boot images unaltered and writes a new catalog.
|
||||
@*
|
||||
@strong{patch} applies patching to existing El Torito boot images
|
||||
if they seem to bear a boot info table.
|
||||
@*
|
||||
A boot info table needs to be patched when the boot image gets newly
|
||||
introduced into the ISO image or if an existing image gets relocated.
|
||||
@ -3487,15 +3503,15 @@ and their designated fate.
|
||||
@sp 1
|
||||
|
||||
A @strong{bootspec} is a word of the form name=value. It is used to describe
|
||||
the parameters of a boot image by an El Torito record or a MBR.
|
||||
the parameters of a boot feature.
|
||||
The names "dir", "bin_path", "efi_path" lead to El Torito bootable images.
|
||||
Name "system_area" activates a given file as MBR.
|
||||
Name "system_area" activates a given file as MBR or other disk header.
|
||||
@*
|
||||
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 boot image and its supporting files have to be added to the ISO image by
|
||||
El Torito boot images 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 "@strong{dir=/isolinux}"
|
||||
@ -3522,10 +3538,13 @@ one of the boot images. But it is not necessary that it appears in the
|
||||
directory tree at all. One may hide it in all trees by @strong{cat_hidden=on}.
|
||||
Other possible values are "iso_rr", "joliet", "hfsplus", and the default "off".
|
||||
@*
|
||||
@strong{bin_path=} depicts a boot image file, a binary program which is to be
|
||||
started by the hardware boot facility (e.g. the BIOS) at boot time.
|
||||
@strong{bin_path=} depicts an El Torito boot image file, a binary program
|
||||
which is to be started by the hardware boot facility (e.g. the BIOS)
|
||||
at boot time.
|
||||
@*
|
||||
@strong{efi_path=} depicts a boot image file that is ready for EFI booting.
|
||||
@strong{efi_path=} depicts an El Torito boot image file that is ready for
|
||||
EFI booting. This is normally a FAT filesystem image not larger than
|
||||
65535 blocks of 512 bytes (= 32 MiB - 512).
|
||||
Its load_size is determined automatically, no boot info table gets
|
||||
written, no boot medium gets emulated, platform_id is 0xef.
|
||||
@*
|
||||
@ -3547,8 +3566,9 @@ The address is written as 64 bit little-endian number. It is the
|
||||
and then incremented by 5.
|
||||
"grub2_boot_info=off" disables this patching.
|
||||
@*
|
||||
@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.
|
||||
@strong{platform_id=} defines by a hexadecimal or decimal number
|
||||
the Platform ID of the boot image. "0x00" is 80x86 PC-BIOS, "0x01" is PowerPC,
|
||||
"0x02" is Mac, "0xef" is EFI (decimal "239").
|
||||
@*
|
||||
@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
|
||||
@ -3565,13 +3585,6 @@ They get attributed to the boot image entry in the catalog.
|
||||
Any following -bootimage bootspecs will affect the new image.
|
||||
The first "next" discards loaded boot images and their catalog.
|
||||
@*
|
||||
@strong{discard} gives up an existing boot catalog and its boot images.
|
||||
@*
|
||||
@strong{keep} keeps or copies boot images unaltered and writes a new catalog.
|
||||
@*
|
||||
@strong{patch} applies patching to existing boot images
|
||||
if they seem to bear a boot info table.
|
||||
@*
|
||||
@cindex System area, _definition
|
||||
@cindex MBR, set, -boot_image system_area=
|
||||
@strong{system_area=}disk_path copies at most 32768 bytes from the given
|
||||
@ -3596,6 +3609,12 @@ The boot image will then be mentioned in GPT as Basic Data
|
||||
or GPT HFS+ partition, and in APM as HFS+ partition.
|
||||
The first three GPT partitions will also be marked by MBR partitions.
|
||||
@*
|
||||
In multi-session situations the existing System Area is preserved by default.
|
||||
In in this case, the special disk_path "." prevents reading of
|
||||
a disk file but nevertheless causes adjustments in the
|
||||
loaded system area data. Such adjustments may get ordered by -boot_image
|
||||
commands.
|
||||
@*
|
||||
@strong{grub2_mbr=}disk_path works like "any" system_area= with additional
|
||||
patching for modern GRUB MBRs. The content start address of the first boot
|
||||
image is converted to a count of 512 byte blocks, and an offset of 4 is added.
|
||||
@ -3620,7 +3639,6 @@ This works with or without system_area= or boot image.
|
||||
Bootspecs chrp_boot_part=, prep_boot_part=, and efi_boot_part= overwrite
|
||||
this entry in the MBR partition table.
|
||||
@*
|
||||
In follow-up sessions the existing System Area is preserved by default.
|
||||
If types "isolinux" or "grub" are set to "patch", then "partition_table=on"
|
||||
is activated without new boot image.
|
||||
In this case the existing System Area gets checked whether it bears addresses
|
||||
@ -3742,8 +3760,8 @@ RAM disk file.
|
||||
and version 4.
|
||||
For the appropriate value see in PALO source code: PALOHDRVERSION.
|
||||
@*
|
||||
@strong{mips_discard} and @strong{sparc_discard}
|
||||
revoke any boot file declarations made for mips or mipsel resp. sparc.
|
||||
@strong{mips_discard}, @strong{sparc_discard}, and @strong{hppa_discard}
|
||||
revoke any boot file declarations made for mips, mipsel, sparc resp. hppa.
|
||||
This removes the ban on production of other boot blocks.
|
||||
@*
|
||||
@cindex HFS+ serial number
|
||||
|
||||
Reference in New Issue
Block a user