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

Argument "." for system area import commands

Browse Source
This commit is contained in:
Thomas Schmitt 2014-10-28 14:07:32 +00:00
parent 8e4a7482f3
commit 2446c08e16
9 changed files with 330 additions and 240 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
xorriso/emulators.c
View File

@ -1183,7 +1183,7 @@ int Xorriso_genisofs(struct XorrisO *xorriso, char *whom,
char *old_root= NULL, *argpt, *hargv[1];
char *boot_path, partno_text[8], *iso_rr_pt, *disk_pt, *rpt, *wpt;
char *rm_merge_args[3], *rr_reloc_dir_pt= NULL;
char *sort_weight_args[4], *bless_args[6];
char *sort_weight_args[4], *bless_args[6], *sa_path;
struct stat stbuf;
@ -2384,7 +2384,11 @@ problem_handler_2:;
if(i+1>=argc)
goto not_enough_args;
i++;
ret= Xorriso_set_system_area_path(xorriso, argv[i], 0);
if(strcmp(argv[i], ".") == 0)
sa_path= "";
else
sa_path= argv[i];
ret= Xorriso_set_system_area_path(xorriso, sa_path, 0);
if(ret <= 0)
goto problem_handler_boot;
if(strcmp(argpt, "-isohybrid-mbr")==0)

13
xorriso/opts_a_c.c
View File

@ -965,7 +965,11 @@ treatment_patch:;
if(ret <= 0)
goto ex;
}
ret= Xorriso_set_system_area_path(xorriso, treatpt + 12, 0);
if(strcmp(treatpt + 12, ".") == 0) {
ret= Xorriso_set_system_area_path(xorriso, "", 0);
} else {
ret= Xorriso_set_system_area_path(xorriso, treatpt + 12, 0);
}
if(ret <= 0)
goto ex;
xorriso->system_area_options&= ~0x4000;
@ -1059,6 +1063,7 @@ treatment_patch:;
}
} else if(strncmp(treatpt, "platform_id=", 12)==0) {
u= 256; /* intentionally too large */
if(strncmp(treatpt + 12, "0x", 2) == 0)
sscanf(treatpt + 14, "%x", &u);
else
@ -1200,7 +1205,11 @@ treatment_patch:;
ret= Xorriso_coordinate_system_area(xorriso, 0, (1 << 14), eff_path, 1 | 2);
if(ret <= 0)
goto ex;
ret= Xorriso_set_system_area_path(xorriso, treatpt + 10, 0);
if(strcmp(treatpt + 10, ".") == 0) {
ret= Xorriso_set_system_area_path(xorriso, "", 0);
} else {
ret= Xorriso_set_system_area_path(xorriso, treatpt + 10, 0);
}
if(ret <= 0)
goto ex;
if(treatpt [10] == 0)

77
xorriso/xorriso.1
View File

@ -9,7 +9,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 "Version 1.3.9, Sep 28, 2014"
.TH XORRISO 1 "Version 1.3.9, Oct 28, 2014"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -2914,22 +2914,25 @@ capability to influence the bootability of the existing sessions, unless one
can assume overwriteable media.
.br
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.
.br
The boot firmware EFI may use programs which are located in a FAT filesystem
and announced by an MBR partition table entry.
.br
.TP
\fB\-boot_image\fR "any"|"isolinux"|"grub"
.br
"discard"|"keep"|"patch"|"show_status"|bootspec|"next"
.br
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.
.br
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.
.br
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.
@ -2939,10 +2942,22 @@ Type \fBany\fR makes
no assumptions about the origin of the boot images.
.br
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.
.br
\fBdiscard\fR 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
.br
\-boot_image any system_area=/dev/zero
.br
\fBkeep\fR keeps or copies El Torito boot images unaltered and writes a new catalog.
.br
\fBpatch\fR applies patching to existing El Torito boot images
if they seem to bear a boot info table.
.br
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.
@ -2966,15 +2981,15 @@ and their designated fate.
.br
A \fBbootspec\fR 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.
.br
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.
.br
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 "\fBdir=/isolinux\fR"
@ -3001,10 +3016,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 \fBcat_hidden=on\fR.
Other possible values are "iso_rr", "joliet", "hfsplus", and the default "off".
.br
\fBbin_path=\fR 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.
\fBbin_path=\fR 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.
.br
\fBefi_path=\fR depicts a boot image file that is ready for EFI booting.
\fBefi_path=\fR 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.
.br
@ -3026,8 +3044,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.
.br
\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.
\fBplatform_id=\fR 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").
.br
\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
@ -3044,13 +3063,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.
.br
\fBdiscard\fR gives up an existing boot catalog and its boot images.
.br
\fBkeep\fR keeps or copies boot images unaltered and writes a new catalog.
.br
\fBpatch\fR applies patching to existing boot images
if they seem to bear a boot info table.
.br
\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
@ -3073,6 +3085,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.
.br
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.
.br
\fBgrub2_mbr=\fRdisk_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.
@ -3096,7 +3114,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.
.br
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
@ -3209,8 +3226,8 @@ RAM disk file.
and version 4.
For the appropriate value see in PALO source code: PALOHDRVERSION.
.br
\fBmips_discard\fR and \fBsparc_discard\fR
revoke any boot file declarations made for mips or mipsel resp. sparc.
\fBmips_discard\fR, \fBsparc_discard\fR, and \fBhppa_discard\fR
revoke any boot file declarations made for mips, mipsel, sparc resp. hppa.
This removes the ban on production of other boot blocks.
.br
\fBhfsplus_serial=\fRhexstring sets a string of 16 digits "0" to "9"

206
xorriso/xorriso.info
View File

@ -2574,29 +2574,42 @@ 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.
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, 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.
rather 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.
-boot_image "any"|"isolinux"|"grub"
"discard"|"keep"|"patch"|"show_status"|bootspec|"next"
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.
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.
Types *isolinux* and *grub* care for known peculiarities. Type
*any* makes no assumptions about the origin of the boot images.
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.
*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
*keep* keeps or copies El Torito boot images unaltered and writes
a new catalog.
*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. This is automatically done if type "isolinux" or "grub"
@ -2613,19 +2626,18 @@ filesystem and announced by an MBR partition table entry.
and their designated fate.
A *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 names "dir", "bin_path", "efi_path" lead to El Torito
bootable images. Name "system_area" activates a given file as MBR.
describe 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 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 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.:
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 "*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
@ -2640,13 +2652,14 @@ filesystem and announced by an MBR partition table entry.
not necessary that it appears in the directory tree at all. One
may hide it in all trees by *cat_hidden=on*. Other possible
values are "iso_rr", "joliet", "hfsplus", and the default "off".
*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.
*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, no boot medium gets emulated, platform_id is
0xef.
*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.
*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.
*emul_type=* can be one of "no_emulation", "hard_disk", "diskette".
It controls the boot medium emulation code of a boot image. The
default "no_emulation" is suitable for ISOLINUX, GRUB, FreeBSD
@ -2661,9 +2674,9 @@ filesystem and announced by an MBR partition table entry.
written as 64 bit little-endian number. It is the 2KB block
address of the boot image content, multiplied by 4, and then
incremented by 5. "grub2_boot_info=off" disables this 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.
*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").
*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
@ -2677,11 +2690,6 @@ filesystem and announced by an MBR partition table entry.
*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 loaded boot images and their catalog.
*discard* gives up an existing boot catalog and its boot images.
*keep* keeps or copies boot images unaltered and writes a new
catalog.
*patch* applies patching to existing boot images if they seem to
bear a boot info table.
*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
@ -2700,6 +2708,11 @@ filesystem and announced by an MBR partition table entry.
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.
*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
@ -2718,8 +2731,7 @@ filesystem and announced by an MBR partition table entry.
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
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 and sizes as if it had been processed by
@ -2816,9 +2828,9 @@ filesystem and announced by an MBR partition table entry.
*hppa_hdrversion=*number chooses between PALO header version 5
(default) and version 4. For the appropriate value see in PALO
source code: PALOHDRVERSION.
*mips_discard* and *sparc_discard* revoke any boot file
declarations made for mips or mipsel resp. sparc. This removes
the ban on production of other boot blocks.
*mips_discard*, *sparc_discard*, and *hppa_discard* revoke any
boot file declarations made for mips, mipsel, sparc resp. hppa.
This removes the ban on production of other boot blocks.
*hfsplus_serial=*hexstring sets a string of 16 digits "0" to "9"
and letters "a" to "f", which will be used as unique serial number
of an emerging HFS+ filesystem.
@ -5017,7 +5029,7 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top
* -alter_date sets timestamps in ISO image: Manip. (line 154)
* -alter_date_r sets timestamps in ISO image: Manip. (line 187)
* -append_partition adds arbitrary file after image end: Bootable.
(line 279)
(line 291)
* -application_id sets application id: SetWrite. (line 196)
* -application_use sets application use field: SetWrite. (line 262)
* -as emulates mkisofs or cdrecord: Emulation. (line 13)
@ -5027,7 +5039,7 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top
* -ban_stdio_write demands real drive: Loading. (line 278)
* -biblio_file sets biblio file name: SetWrite. (line 244)
* -blank erases media: Writing. (line 61)
* -boot_image controls bootability: Bootable. (line 27)
* -boot_image controls bootability: Bootable. (line 26)
* -calm_drive reduces drive activity: Loading. (line 267)
* -cd sets working directory in ISO: Navigate. (line 7)
* -cdx sets working directory on disk: Navigate. (line 16)
@ -5255,10 +5267,10 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* ACL, set in ISO image, -setfacl_r: Manip. (line 105)
* ACL, show in ISO image, -getfacl: Navigate. (line 70)
* ACL, show in ISO image, -getfacl_r: Navigate. (line 77)
* APM block size: Bootable. (line 270)
* APM block size: Bootable. (line 282)
* APM, _definition: Extras. (line 41)
* Appendable media, _definition: Media. (line 38)
* Appended Filesystem Image, -append_partition: Bootable. (line 279)
* Appended Filesystem Image, -append_partition: Bootable. (line 291)
* Automatic execution order, of arguments, -x: ArgSort. (line 16)
* Backslash Interpretation, _definition: Processing. (line 52)
* Backup, enable fast incremental, -disk_dev_ino: Loading. (line 217)
@ -5266,7 +5278,7 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Backup, scdbackup checksum tag, -scdbackup: Emulation. (line 179)
* Blank media, _definition: Media. (line 29)
* Blind growing, _definition: Methods. (line 40)
* Bootability, control, -boot_image: Bootable. (line 27)
* Bootability, control, -boot_image: Bootable. (line 26)
* Bugs, reporting: Bugreport. (line 6)
* cdrecord, Emulation: Emulation. (line 118)
* Character Set, _definition: Charset. (line 6)
@ -5275,13 +5287,13 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Character Set, for output, -out_charset: SetWrite. (line 276)
* Character set, learn from image, -auto_charset: Loading. (line 122)
* Character Set, of terminal, -local_charset: Charset. (line 58)
* CHRP partition, _definition: Bootable. (line 172)
* CHRP partition, _definition: Bootable. (line 184)
* Closed media, _definition: Media. (line 43)
* Comment, #: Scripting. (line 173)
* Control, signal handling, -signal_handling: Exception. (line 69)
* Create, new ISO image, _definition: Methods. (line 6)
* Cylinder alignment, _definition: Bootable. (line 212)
* Cylinder size, _definition: Bootable. (line 201)
* Cylinder alignment, _definition: Bootable. (line 224)
* Cylinder size, _definition: Bootable. (line 213)
* Damaged track and session, close, -close_damaged: Writing. (line 170)
* Delete, from ISO image, -rm: Manip. (line 21)
* Delete, from ISO image, -rm_r: Manip. (line 28)
@ -5313,7 +5325,7 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Drive, write and eject, -commit_eject: Writing. (line 56)
* EA, _definition: Extras. (line 65)
* ECMA-119, _definition: Model. (line 6)
* EFI system partition, _definition: Bootable. (line 181)
* EFI system partition, _definition: Bootable. (line 193)
* El Torito, _definition: Extras. (line 19)
* Emulation, -as: Emulation. (line 13)
* Emulation, .mkisofsrc, -read_mkisofsrc: Emulation. (line 153)
@ -5340,10 +5352,10 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Group, in ISO image, -chgrp_r: Manip. (line 62)
* Growing, _definition: Methods. (line 19)
* Hard links, control handling, -hardlinks: Loading. (line 134)
* HFS+ allocation block size: Bootable. (line 267)
* HFS+ serial number: Bootable. (line 264)
* HFS+ allocation block size: Bootable. (line 279)
* HFS+ serial number: Bootable. (line 276)
* hidden, set in ISO image, -hide: Manip. (line 191)
* HP-PA boot sector, production: Bootable. (line 244)
* HP-PA boot sector, production: Bootable. (line 256)
* Image reading, cache size, -data_cache_size: Loading. (line 296)
* Image, _definition: Model. (line 9)
* Image, demand volume ID, -assert_volid: Loading. (line 108)
@ -5395,13 +5407,13 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* List delimiter, _definition: Processing. (line 9)
* Local Character Set, _definition: Charset. (line 11)
* MBR, _definition: Extras. (line 26)
* MBR, set, -boot_image system_area=: Bootable. (line 127)
* MBR, set, -boot_image system_area=: Bootable. (line 135)
* MD5, control handling, -md5: Loading. (line 183)
* Media, erase, -blank: Writing. (line 61)
* Media, format, -format: Writing. (line 91)
* Media, list formats, -list_formats: Writing. (line 134)
* Media, list write speeds, -list_speeds: Writing. (line 146)
* MIPS boot file, activation: Bootable. (line 223)
* MIPS boot file, activation: Bootable. (line 235)
* mkisofs, Emulation: Emulation. (line 16)
* Modifying, _definition: Methods. (line 27)
* Multi-session media, _definition: Media. (line 7)
@ -5428,15 +5440,15 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Ownership, global in ISO image, -uid: SetWrite. (line 282)
* Ownership, in ISO image, -chown: Manip. (line 49)
* Ownership, in ISO image, -chown_r: Manip. (line 54)
* Partition offset, _definition: Bootable. (line 191)
* Partition table, _definition: Bootable. (line 152)
* Partition offset, _definition: Bootable. (line 203)
* Partition table, _definition: Bootable. (line 165)
* Pathspec, _definition: SetInsert. (line 124)
* Pattern expansion, _definition: Processing. (line 24)
* Pattern expansion, for disk paths, -disk_pattern: Insert. (line 36)
* Pattern expansion, for ISO paths, -iso_rr_pattern: Manip. (line 10)
* Permissions, in ISO image, -chmod: Manip. (line 65)
* Permissions, in ISO image, -chmod_r: Manip. (line 77)
* PReP partition, _definition: Bootable. (line 176)
* PReP partition, _definition: Bootable. (line 188)
* Problems, reporting: Bugreport. (line 6)
* Process, consolidate text output, -pkt_output: Frontend. (line 7)
* Process, control abort on error, -abort_on: Exception. (line 27)
@ -5495,10 +5507,10 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Session, mount parameters, -mount_opts: Inquiry. (line 68)
* Session, select as input, -load: Loading. (line 35)
* Sorting order, for -x, -list_arg_sorting: ArgSort. (line 27)
* SUN Disk Label, production: Bootable. (line 234)
* SUN SPARC boot images, activation: Bootable. (line 300)
* SUN Disk Label, production: Bootable. (line 246)
* SUN SPARC boot images, activation: Bootable. (line 312)
* Symbolic link, create, -lns: Insert. (line 176)
* System area, _definition: Bootable. (line 127)
* System area, _definition: Bootable. (line 135)
* Table-of-content, search sessions, -rom_toc_scan: Loading. (line 238)
* Table-of-content, show, -toc: Inquiry. (line 28)
* Timestamps, set in ISO image, -alter_date: Manip. (line 154)
@ -5514,7 +5526,7 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Verify, file tree checksums, -check_md5_r: Verify. (line 182)
* Verify, preset -check_media, -check_media_defaults: Verify. (line 41)
* Write, block size, -dvd_obs: SetWrite. (line 333)
* Write, bootability, -boot_image: Bootable. (line 27)
* Write, bootability, -boot_image: Bootable. (line 26)
* Write, buffer syncing, -stdio_sync: SetWrite. (line 340)
* Write, close media, -close: SetWrite. (line 359)
* Write, compliance to specs, -compliance: SetWrite. (line 58)
@ -5564,39 +5576,39 @@ Node: Filter94263
Node: Writing98885
Node: SetWrite109016
Node: Bootable129722
Node: Jigdo147755
Node: Charset152002
Node: Exception155317
Node: DialogCtl161437
Node: Inquiry164035
Node: Navigate171466
Node: Verify179764
Node: Restore189591
Node: Emulation198195
Node: Scripting208583
Node: Frontend216354
Node: Examples225961
Node: ExDevices227139
Node: ExCreate227805
Node: ExDialog229090
Node: ExGrowing230355
Node: ExModifying231160
Node: ExBootable231664
Node: ExCharset232216
Node: ExPseudo233108
Node: ExCdrecord234006
Node: ExMkisofs234323
Node: ExGrowisofs235663
Node: ExException236798
Node: ExTime237252
Node: ExIncBackup237711
Node: ExRestore241701
Node: ExRecovery242634
Node: Files243204
Node: Seealso244503
Node: Bugreport245226
Node: Legal245807
Node: CommandIdx246818
Node: ConceptIdx263699
Node: Jigdo148520
Node: Charset152767
Node: Exception156082
Node: DialogCtl162202
Node: Inquiry164800
Node: Navigate172231
Node: Verify180529
Node: Restore190356
Node: Emulation198960
Node: Scripting209348
Node: Frontend217119
Node: Examples226726
Node: ExDevices227904
Node: ExCreate228570
Node: ExDialog229855
Node: ExGrowing231120
Node: ExModifying231925
Node: ExBootable232429
Node: ExCharset232981
Node: ExPseudo233873
Node: ExCdrecord234771
Node: ExMkisofs235088
Node: ExGrowisofs236428
Node: ExException237563
Node: ExTime238017
Node: ExIncBackup238476
Node: ExRestore242466
Node: ExRecovery243399
Node: Files243969
Node: Seealso245268
Node: Bugreport245991
Node: Legal246572
Node: CommandIdx247583
Node: ConceptIdx264464

End Tag Table

78
xorriso/xorriso.texi
View File

@ -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

2
xorriso/xorriso_timestamp.h
View File

@ -1 +1 @@
#define Xorriso_timestamP "2014.10.28.140313"
#define Xorriso_timestamP "2014.10.28.140609"

16
xorriso/xorrisofs.1
View File

@ -9,7 +9,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 XORRISOFS 1 "Version 1.3.9, Sep 26, 2014"
.TH XORRISOFS 1 "Version 1.3.9, Oct 28, 2014"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -1030,6 +1030,10 @@ the ISO image.
.br
Other than a El Torito boot image, the file disk_path needs not to be added
to the ISO image. It will not show up as file in the directory trees.
.br
In multi\-session situations, the special disk_path "." prevents reading of
a disk file but nevertheless causes the adjustments in the
existing MBR, which were ordered by other options.
.TP
\fB\-generic-boot\fR disk_path
Alias of \-G.
@ -1053,6 +1057,8 @@ The disk path should lead to one of the Syslinux files isohdp[fp]x*.bin .
The MBR gets patched according to isohybrid needs. The first partition
describes the range of the ISO image. Its start is at block 0 by default,
but may be set to 64 disk blocks by option \-partition_offset 16.
.br
For the meaning of special disk_path "." see option \-G.
.TP
\fB\-isohybrid-gpt-basdat\fR
Mark the current El Torito boot image (see options \-b and \-e) in GPT as
@ -1165,8 +1171,12 @@ Mark the block range of the whole emerging ISO image as MBR partition of type
0x96. This is not compatible with any other feature that produces MBR
partition entries. It makes GPT unrecognizable.
.br
CHRP is used in conjunction with HFS. It is not yet tested whether HFS+
filesystems produced with option \-hfsplus would boot on any CHRP capable machine.
CHRP is often used in conjunction with HFS. It is not yet tested whether HFS+
filesystems produced with option \-hfsplus would boot on any
CHRP capable machine which does not boot pure ISO 9660 as well.
.TP
\fB\-chrp-boot\fR
Alias of \-chrp\-boot\-part.
.TP
\fB\-prep-boot-part\fR disk_path
Copy a file from disk into the emerging ISO image and mark it by a MBR

153
xorriso/xorrisofs.info
View File

@ -1009,6 +1009,9 @@ combinable and also not combinable with MBR, GPT, or APM.
Other than a El Torito boot image, the file disk_path needs not to
be added to the ISO image. It will not show up as file in the
directory trees.
In multi-session situations, the special disk_path "." prevents
reading of a disk file but nevertheless causes the adjustments in
the existing MBR, which were ordered by other options.
-generic-boot disk_path
Alias of -G.
@ -1033,6 +1036,7 @@ combinable and also not combinable with MBR, GPT, or APM.
needs. The first partition describes the range of the ISO image.
Its start is at block 0 by default, but may be set to 64 disk
blocks by option -partition_offset 16.
For the meaning of special disk_path "." see option -G.
-isohybrid-gpt-basdat
Mark the current El Torito boot image (see options -b and -e) in
@ -1139,9 +1143,13 @@ combinable and also not combinable with MBR, GPT, or APM.
partition of type 0x96. This is not compatible with any other
feature that produces MBR partition entries. It makes GPT
unrecognizable.
CHRP is used in conjunction with HFS. It is not yet tested whether
HFS+ filesystems produced with option -hfsplus would boot on any
CHRP capable machine.
CHRP is often used in conjunction with HFS. It is not yet tested
whether HFS+ filesystems produced with option -hfsplus would boot
on any CHRP capable machine which does not boot pure ISO 9660 as
well.
-chrp-boot
Alias of -chrp-boot-part.
-prep-boot-part disk_path
Copy a file from disk into the emerging ISO image and mark it by a
@ -1817,12 +1825,12 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
* --boot-catalog-hide Hide El Torito boot catalog: Bootable.
(line 116)
* --efi-boot El Torito EFI boot image: Bootable. (line 58)
* --embedded-boot Fill System Area e.g. by MBR: SystemArea. (line 35)
* --embedded-boot Fill System Area e.g. by MBR: SystemArea. (line 38)
* --emul-toc enable table-of-content emulation: SetProduct. (line 37)
* --for_backup Enable backup fidelity: SetExtras. (line 67)
* --grub2-boot-info Patch El Torito boot image: Bootable. (line 101)
* --grub2-mbr Install modern GRUB2 MBR: SystemArea. (line 38)
* --grub2-sparc-core SUN SPARC core file: SystemArea. (line 202)
* --grub2-mbr Install modern GRUB2 MBR: SystemArea. (line 41)
* --grub2-sparc-core SUN SPARC core file: SystemArea. (line 210)
* --hardlinks Recording of hardlink relations: SetExtras. (line 92)
* --md5 Recording of MD5 checksums: SetExtras. (line 84)
* --modification-date set ISO image timestamps: ImageId. (line 82)
@ -1837,7 +1845,7 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
(line 84)
* --old-root-no-md5 disable MD5 with -old-root: SetInsert. (line 105)
* --protective-msdos-label Patch System Area partition table: SystemArea.
(line 82)
(line 86)
* --quoted_path_list read pathspecs from disk file: SetInsert.
(line 13)
* --scdbackup_tag Recording of MD5 checksum: SetExtras. (line 101)
@ -1854,10 +1862,10 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
* -abstract set Abstract File path: ImageId. (line 66)
* -allow-lowercase lowercase in ISO file names: SetCompl. (line 46)
* -append_partition Append MBR partition after image: SystemArea.
(line 128)
(line 132)
* -appid set Application Id: ImageId. (line 46)
* -b El Torito PC-BIOS boot image: Bootable. (line 32)
* -B SUN SPARC boot images: SystemArea. (line 184)
* -B SUN SPARC boot images: SystemArea. (line 192)
* -biblio set Biblio File path: ImageId. (line 72)
* -boot-info-table Patch El Torito boot image: Bootable. (line 95)
* -boot-load-size El Torito boot image load size: Bootable. (line 63)
@ -1868,7 +1876,8 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
* -checksum_algorithm_iso choose .jigdo checksums: Jigdo. (line 80)
* -checksum_algorithm_template choose .template checksums: Jigdo.
(line 87)
* -chrp-boot-part CHRP partition: SystemArea. (line 156)
* -chrp-boot CHRP partition: SystemArea. (line 170)
* -chrp-boot-part CHRP partition: SystemArea. (line 160)
* -copyright set Copyright File path: ImageId. (line 77)
* -D allow deep directory hierachies: SetExtras. (line 31)
* -d omit trailing dot in ISO file names: SetCompl. (line 56)
@ -1879,7 +1888,7 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
* -disallow_dir_id_ext enforce ISO level 1 directory names: SetCompl.
(line 24)
* -e El Torito EFI boot image: Bootable. (line 50)
* -efi-boot-part EFI boot partition: SystemArea. (line 145)
* -efi-boot-part EFI boot partition: SystemArea. (line 149)
* -eltorito-alt-boot begin next boot catalog entry: Bootable.
(line 43)
* -eltorito-boot El Torito PC-BIOS boot image: Bootable. (line 40)
@ -1896,7 +1905,7 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
* -full-iso9660-filenames allow 31 characters in ISO file names: SetCompl.
(line 66)
* -G Fill System Area e.g. by MBR: SystemArea. (line 25)
* -generic-boot Fill System Area e.g. by MBR: SystemArea. (line 32)
* -generic-boot Fill System Area e.g. by MBR: SystemArea. (line 35)
* -graft-points enable target=source pathspecs: SetInsert. (line 31)
* -gui increase frequency of pacifier messages: Miscellaneous.
(line 31)
@ -1924,22 +1933,22 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
(line 16)
* -hide-rr-moved set deep directory relocation target: SetExtras.
(line 64)
* -hppa-bootloader HP-PA bootloader file: SystemArea. (line 216)
* -hppa-cmdline HP-PA PALO command line: SystemArea. (line 209)
* -hppa-hdrversion HP-PA PALO header version: SystemArea. (line 228)
* -hppa-kernel_32 HP-PA kernel_32 file: SystemArea. (line 219)
* -hppa-kernel_64 HP-PA kernel_64 file: SystemArea. (line 222)
* -hppa-ramdisk HP-PA ramdisk file: SystemArea. (line 225)
* -hppa-bootloader HP-PA bootloader file: SystemArea. (line 224)
* -hppa-cmdline HP-PA PALO command line: SystemArea. (line 217)
* -hppa-hdrversion HP-PA PALO header version: SystemArea. (line 236)
* -hppa-kernel_32 HP-PA kernel_32 file: SystemArea. (line 227)
* -hppa-kernel_64 HP-PA kernel_64 file: SystemArea. (line 230)
* -hppa-ramdisk HP-PA ramdisk file: SystemArea. (line 233)
* -input-charset set character set of disk file names: Charset.
(line 17)
* -iso-level define ISO 9660 limitations: SetCompl. (line 7)
* -isohybrid-apm-hfsplus Mark boot image in APM: SystemArea.
(line 73)
* -isohybrid-gpt-basdat Mark boot image in GPT: SystemArea. (line 56)
(line 77)
* -isohybrid-gpt-basdat Mark boot image in GPT: SystemArea. (line 60)
* -isohybrid-gpt-hfsplus Mark boot image in GPT: SystemArea.
(line 68)
(line 72)
* -isohybrid-mbr Install ISOLINUX isohybrid MBR: SystemArea.
(line 45)
(line 48)
* -J enable production of Joliet directory tree: SetExtras. (line 110)
* -jigdo-exclude add exclusion pattern for .md5: Jigdo. (line 59)
* -jigdo-force-md5 add check pattern for .md5: Jigdo. (line 52)
@ -1960,8 +1969,8 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
* -max-iso9660-filenames allow 37 characters in ISO file names: SetCompl.
(line 69)
* -md5-list set path of readable .md5: Jigdo. (line 73)
* -mips-boot MIPS Big Endian boot image: SystemArea. (line 171)
* -mipsel-boot MIPS Little Endian boot image: SystemArea. (line 178)
* -mips-boot MIPS Big Endian boot image: SystemArea. (line 179)
* -mipsel-boot MIPS Little Endian boot image: SystemArea. (line 186)
* -N omit version number in ISO file names: SetCompl. (line 73)
* -no-emul-boot El Torito boot image emulation: Bootable. (line 74)
* -no-pad do not add zeros to ISO tree: SetProduct. (line 104)
@ -1979,13 +1988,13 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
* -p set Preparer Id: ImageId. (line 54)
* -P set Publisher Id: ImageId. (line 30)
* -pad add 300 KiB of zeros to ISO tree: SetProduct. (line 97)
* -partition_cyl_align Image size alignment: SystemArea. (line 116)
* -partition_hd_cyl MBR heads per cylinder: SystemArea. (line 99)
* -partition_cyl_align Image size alignment: SystemArea. (line 120)
* -partition_hd_cyl MBR heads per cylinder: SystemArea. (line 103)
* -partition_offset Make mountable by partition 1: SystemArea.
(line 87)
* -partition_sec_hd MBR sectors per head: SystemArea. (line 103)
(line 91)
* -partition_sec_hd MBR sectors per head: SystemArea. (line 107)
* -path-list read pathspecs from disk file: SetInsert. (line 8)
* -prep-boot-part PReP partition: SystemArea. (line 165)
* -prep-boot-part PReP partition: SystemArea. (line 173)
* -preparer set Preparer Id: ImageId. (line 63)
* -prev-session set path for loading existing ISO image: Loading.
(line 22)
@ -2003,8 +2012,8 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T
* -root redirect ISO root directory: SetInsert. (line 64)
* -rr_reloc_dir set deep directory relocation target: SetExtras.
(line 47)
* -sparc-boot SUN SPARC boot images: SystemArea. (line 196)
* -sparc-label SUN Disk Label text: SystemArea. (line 199)
* -sparc-boot SUN SPARC boot images: SystemArea. (line 204)
* -sparc-label SUN Disk Label text: SystemArea. (line 207)
* -sysid set System Id: ImageId. (line 49)
* -transparent-compression enable recognition of zisofs files: SetInsert.
(line 61)
@ -2054,44 +2063,44 @@ File: xorrisofs.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
(line 101)
* Bootability, boot image patching, -boot-info-table: Bootable.
(line 95)
* Bootability, control, --grub2-sparc-core: SystemArea. (line 202)
* Bootability, control, --grub2-sparc-core: SystemArea. (line 210)
* Bootability, control, --efi-boot: Bootable. (line 58)
* Bootability, control, -b, -eltorito-boot: Bootable. (line 32)
* Bootability, control, -B, -sparc-boot: SystemArea. (line 184)
* Bootability, control, -B, -sparc-boot: SystemArea. (line 192)
* Bootability, control, -e: Bootable. (line 50)
* Bootability, control, -hppa-bootloader: SystemArea. (line 216)
* Bootability, control, -hppa-cmdline: SystemArea. (line 209)
* Bootability, control, -hppa-hdrversion: SystemArea. (line 228)
* Bootability, control, -hppa-kernel_32: SystemArea. (line 219)
* Bootability, control, -hppa-kernel_64: SystemArea. (line 222)
* Bootability, control, -hppa-ramdisk: SystemArea. (line 225)
* Bootability, control, -mips-boot: SystemArea. (line 171)
* Bootability, control, -mipsel-boot: SystemArea. (line 178)
* Bootability, control, -hppa-bootloader: SystemArea. (line 224)
* Bootability, control, -hppa-cmdline: SystemArea. (line 217)
* Bootability, control, -hppa-hdrversion: SystemArea. (line 236)
* Bootability, control, -hppa-kernel_32: SystemArea. (line 227)
* Bootability, control, -hppa-kernel_64: SystemArea. (line 230)
* Bootability, control, -hppa-ramdisk: SystemArea. (line 233)
* Bootability, control, -mips-boot: SystemArea. (line 179)
* Bootability, control, -mipsel-boot: SystemArea. (line 186)
* Bootability, El Torito section id string, -eltorito-id: Bootable.
(line 82)
* Bootability, El Torito selection criteria, -eltorito-selcrit: Bootable.
(line 90)
* Bootability, fill System Area e.g. by MBR, -G, --embedded-boot, -generic-boot: SystemArea.
(line 25)
* Bootability, for CHRP, -chrp-boot-part: SystemArea. (line 156)
* Bootability, for EFI, -efi-boot-part: SystemArea. (line 145)
* Bootability, for PReP, -prep-boot-part: SystemArea. (line 165)
* Bootability, for CHRP, -chrp-boot-part: SystemArea. (line 160)
* Bootability, for EFI, -efi-boot-part: SystemArea. (line 149)
* Bootability, for PReP, -prep-boot-part: SystemArea. (line 173)
* Bootability, install ISOLINUX isohybrid MBR, -isohybrid-mbr: SystemArea.
(line 45)
(line 48)
* Bootability, install modern GRUB2 MBR, --grub2-mbr: SystemArea.
(line 38)
(line 41)
* Bootability, mark boot image in APM, -isohybrid-apm-hfsplus: SystemArea.
(line 73)
(line 77)
* Bootability, mark boot image in GPT, -isohybrid-gpt-basdat: SystemArea.
(line 56)
(line 60)
* Bootability, mark boot image in GPT, -isohybrid-gpt-hfsplus: SystemArea.
(line 68)
(line 72)
* Bootability, next entry, -eltorito-alt-boot: Bootable. (line 43)
* Bootability, no boot image emulation, -no-emul-boot: Bootable.
(line 74)
* Bootability, patch System Area partition table, --protective-msdos-label: SystemArea.
(line 82)
* Bootability, SUN Disk Label text, -sparc-label: SystemArea. (line 199)
(line 86)
* Bootability, SUN Disk Label text, -sparc-label: SystemArea. (line 207)
* Bugs, reporting: Bugreport. (line 6)
* Character Set, for disk file names, -input-charset: Charset.
(line 17)
@ -2129,7 +2138,7 @@ File: xorrisofs.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Hiding, from ISO and Rock Ridge, -hide-list: SetHide. (line 16)
* Hiding, from Joliet, -hide-joliet: SetHide. (line 20)
* Hiding, from Joliet, -hide-joliet-list: SetHide. (line 25)
* Image size, alignment, -partition_cyl_align: SystemArea. (line 116)
* Image size, alignment, -partition_cyl_align: SystemArea. (line 120)
* Incremental insertion, disable disk ino, --old-root-no-ino: SetInsert.
(line 84)
* Incremental insertion, disable MD5, --old-root-no-md5: SetInsert.
@ -2182,14 +2191,14 @@ File: xorrisofs.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Links, follow on disk, -f, -follow-links: SetInsert. (line 24)
* Links, record and load hard links, --hardlinks: SetExtras. (line 92)
* MBR, _definition: SystemArea. (line 9)
* MBR, append partition, -append_partition: SystemArea. (line 128)
* MBR, sectors per head, -partition_sec_hd: SystemArea. (line 99)
* MBR, append partition, -append_partition: SystemArea. (line 132)
* MBR, sectors per head, -partition_sec_hd: SystemArea. (line 103)
* MD5, record and load, --md5: SetExtras. (line 84)
* Message output, increase frequency, -gui: Miscellaneous. (line 31)
* Message output, redirect stderr, -log-file: Miscellaneous. (line 35)
* Message output, suppress, -quiet: Miscellaneous. (line 27)
* Mountability, by non-trivial partition 1, -partition_offset: SystemArea.
(line 87)
(line 91)
* Options, list, -help: Miscellaneous. (line 23)
* Output file, set address, -o, -output: SetProduct. (line 8)
* Padding, 300 KiB, -pad: SetProduct. (line 97)
@ -2247,22 +2256,22 @@ Node: SetHide30591
Node: ImageId31899
Node: Bootable36067
Node: SystemArea41247
Node: Charset52378
Node: Jigdo53404
Node: Miscellaneous57671
Node: Examples59315
Node: ExSimple59801
Node: ExGraft60280
Node: ExMkisofs61527
Node: ExGrowisofs62780
Node: ExIncBackup63952
Node: ExIncBckAcc67070
Node: ExBootable68746
Node: Files70838
Node: Seealso71912
Node: Bugreport72568
Node: Legal73149
Node: CommandIdx74044
Node: ConceptIdx89184
Node: Charset52735
Node: Jigdo53761
Node: Miscellaneous58028
Node: Examples59672
Node: ExSimple60158
Node: ExGraft60637
Node: ExMkisofs61884
Node: ExGrowisofs63137
Node: ExIncBackup64309
Node: ExIncBckAcc67427
Node: ExBootable69103
Node: Files71195
Node: Seealso72269
Node: Bugreport72925
Node: Legal73506
Node: CommandIdx74401
Node: ConceptIdx89614

End Tag Table

17
xorriso/xorrisofs.texi
View File

@ -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 XORRISOFS 1 "Version 1.3.9, Sep 26, 2014"
@c man .TH XORRISOFS 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:
@ -1406,6 +1406,10 @@ the ISO image.
@*
Other than a El Torito boot image, the file disk_path needs not to be added
to the ISO image. It will not show up as file in the directory trees.
@*
In multi-session situations, the special disk_path "." prevents reading of
a disk file but nevertheless causes the adjustments in the
existing MBR, which were ordered by other options.
@c man .TP
@item -generic-boot disk_path
@kindex -generic-boot Fill System Area e.g. by MBR
@ -1435,6 +1439,8 @@ The disk path should lead to one of the Syslinux files isohdp[fp]x*.bin .
The MBR gets patched according to isohybrid needs. The first partition
describes the range of the ISO image. Its start is at block 0 by default,
but may be set to 64 disk blocks by option -partition_offset 16.
@*
For the meaning of special disk_path "." see option -G.
@c man .TP
@item -isohybrid-gpt-basdat
@kindex -isohybrid-gpt-basdat Mark boot image in GPT
@ -1569,8 +1575,13 @@ Mark the block range of the whole emerging ISO image as MBR partition of type
0x96. This is not compatible with any other feature that produces MBR
partition entries. It makes GPT unrecognizable.
@*
CHRP is used in conjunction with HFS. It is not yet tested whether HFS+
filesystems produced with option -hfsplus would boot on any CHRP capable machine.
CHRP is often used in conjunction with HFS. It is not yet tested whether HFS+
filesystems produced with option -hfsplus would boot on any
CHRP capable machine which does not boot pure ISO 9660 as well.
@c man .TP
@item -chrp-boot
@kindex -chrp-boot CHRP partition
Alias of -chrp-boot-part.
@c man .TP
@item -prep-boot-part disk_path
@kindex -prep-boot-part PReP partition