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

New boot_specs efi_boot_part, prep_boot_part, chrp_boot_part

Browse Source
This commit is contained in:
Thomas Schmitt
2012-06-18 11:20:31 +00:00
parent 4e733f082a
commit 56308c81e4
8 changed files with 261 additions and 91 deletions
Download Patch File Download Diff File Expand all files Collapse all files

57
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.2.3, Jun 07, 2012"
.TH XORRISO 1 "Version 1.2.3, Jun 18, 2012"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -391,19 +391,35 @@ Most bootable GNU/Linux CDs are equipped with ISOLINUX or GRUB boot images.
makes such an image bootable. For details see command \-boot_image.
.br
It is possible to make ISO images bootable from USB stick or other
hard\-disk\-like media by \-boot_image parameter system_area= . This installs
a Master Boot Record which may get adjusted according to the needs
of GRUB resp. ISOLINUX.
An \fBMBR\fR contains boot code and a partition table. It does not hamper
CDROM booting. The new MBR of a follow\-up session can get in effect
hard\-disk\-like media. Several options install a \fBMBR\fR
(Master Boot Record), It may get adjusted according to the needs of the
intended boot firmware and the involved boot loaders, e.g. GRUB2 or ISOLINUX.
A MBR contains boot code and a partition table.
The new MBR of a follow\-up session can get in effect
only on overwriteable media.
.br
MBR is read by PC\-BIOS when booting from USB stick or hard disk,
and by PowerPC CHRP or PReP when booting.
An MBR partiton with type 0xee indicates the presence of GPT.
.br
Emulation \-as mkisofs supports the example options out of the ISOLINUX wiki,
the options used in GRUB script grub\-mkrescue, and the example in the
FreeBSD AvgLiveCD wiki.
.br
There is support for boot facilities other than PC BIOS:
EFI, MIPS Big Endian (SGI), MIPS Little Endian (DEC), SUN SPARC.
A \fBGPT\fR (GUID Partition Table) marks partitions in a more modern way.
It is read by EFI when booting from USB stick or hard disk, and may be used
for finding and mounting a HFS+ partition inside the ISO image.
.br
An \fBAPM\fR (Apple Partition Map) marks the HFS+ partition.
It is read by Macs for booting and for mounting.
.br
MBR, GPT and APM are combinable. APM occupies the first 8 bytes of
MBR boot code. All three do not hamper El Torito booting from CDROM.
.br
There is support for further facilities:
MIPS Big Endian (SGI), MIPS Little Endian (DEC), SUN SPARC.
Those are mutually not combinable and also not combinable with MBR, GPT,
or APM.
.br
.PP
\fBACL\fR
@ -2805,9 +2821,12 @@ session this works only if also "system_area=" and "bin_path=" or "dir="
is given.
.br
With types "any" and "grub" it shows a single
partiton which starts at byte 512 and ends where the ISO image ends.
partition which starts at byte 512 and ends where the ISO image ends.
This works with or without system_area= or boot image.
.br
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.
@ -2818,6 +2837,26 @@ then those parameters get updated when the new System Area is written.
Special "system_area=/dev/zero" causes 32k of NUL\-bytes.
Use this to discard an MBR which was loaded with the ISO image.
.br
\fBchrp_boot_part=on\fR causes a single partition in MBR which covers
the whole ISO image and has type 0x41. This is not compatible with any
other feature that produces MBR partition entries. It makes GPT unrecognizable.
.br
\fBprep_boot_part=\fR inserts the content of a data file into the image and
marks it by an MBR partition of type 0x96. The parts of the ISO image before
and after this partition will be covered by further MBR partitions.
The data file is supposed to contain ELF executable code.
.br
\fBefi_boot_part=\fR inserts the content of a data file into the image and
marks it by a GPT partition. If not chrp_boot_part=on, then the first partition
in MBR will have type 0xee to announce the presence of GPT.
The data file is supposed to contain a FAT filesystem.
.br
Instead of a disk_path, the word \-\-efi\-boot\-image may be given.
It exposes in GPT the content of the first El Torito EFI boot image as
EFI system partition. EFI boot images are introduced by bootspec efi_path=.
The affected EFI boot image cannot show up in HFS+ because it is stored
outside the HFS+ partition.
.br
\fBpartition_offset=\fR2kb_block_adr causes a partition table with a single
partition that begins at the given block address. This is counted in 2048 byte
blocks, not in 512 byte blocks. If the block address is non\-zero then it must