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

New -boot_image bootspecs partition_table=gpt_basdat, gpt_hfsplus, apm_hfsplus

Browse Source
This commit is contained in:
Thomas Schmitt
2014-09-30 18:18:58 +00:00
parent 78c96924e1
commit 8b326cbb91
5 changed files with 121 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
libisoburn/trunk/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, Jun 28, 2014"
@c man .TH XORRISO 1 "Version 1.3.9, Sep 28, 2014"
@c man .\" Please adjust this date whenever revising the manpage.
@c man .\"
@c man .\" Some roff macros, for reference:
@ -3498,8 +3498,8 @@ 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.:
In that case it suffices to use as bootspec the text "@strong{dir=/isolinux}"
or "dir=/boot/isolinux". E.g.:
@*
-boot_image isolinux dir=/boot/isolinux
@*
@ -3579,10 +3579,22 @@ 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.
@*
Other than a El Torito boot image, the file disk_path needs not to be added
Other than an El Torito boot image, the file disk_path needs not to be added
to the ISO image.
@*
-boot_image isolinux system_area= implies "partition_table=on".
@strong{-boot_image isolinux system_area=} implies "partition_table=on".
In this case, the disk path should lead to one of the SYSLINUX files
isohdp[fp]x*.bin or to a file which was derived from one of those files.
E.g. to the first 512 bytes from an ISOLINUX isohybrid ISO image.
@*
In this case, El Torito boot images (dir=, bin_path=, efi_path=)
may be augmented by
@strong{isolinux partition_entry=gpt_basdat}
or @strong{isolinux partition_entry=gpt_hfsplus},
and by @strong{isolinux partition_entry=apm_hfsplus}.
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.
@*
@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