Updated documentation about MBR
This commit is contained in:
@ -337,7 +337,11 @@ Most bootable GNU/Linux CDs are equipped with ISOLINUX or GRUB boot
|
||||
images. xorriso is able to create or maintain an El Torito object
|
||||
which makes such an image bootable. For details see option -boot_image.
|
||||
It is possible to make ISO images bootable from USB stick or other
|
||||
hard-disk-like media by -boot_image argument system_area= .
|
||||
hard-disk-like media by -boot_image argument system_area= . This
|
||||
installs a Master Boot Record which may get adjusted according to the
|
||||
needs of GRUB resp. ISOLINUX. An *MBR* 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 only on overwriteable media.
|
||||
Emulation -as mkisofs supports the example options out of the ISOLINUX
|
||||
wiki. It also supports the options used in GRUB script grub-mkrescue.
|
||||
The support for other boot image types is sparse.
|
||||
@ -2004,20 +2008,27 @@ of the existing sessions, unless one can assume overwriteable media.
|
||||
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.
|
||||
Special disk_path "/dev/zero" causes 32k of NUL-bytes. Use this
|
||||
to discard an MBR which eventually was loaded with the ISO image.
|
||||
Other than a 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".
|
||||
"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 boot image LBA to be written into the MBR. This
|
||||
works only if also "system_area=" and "bin_path=" or "dir=" is
|
||||
given.
|
||||
and it causes the boot image LBA to be written into the MBR. For
|
||||
the first session this works only if also "system_area=" and
|
||||
"bin_path=" or "dir=" is given.
|
||||
With types "any" and "grub" it shows a single partiton which
|
||||
starts at byte 512 and ends where the ISO image ends. This works
|
||||
with or without system_area= or boot image.
|
||||
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 and sizes as if it had been processed by
|
||||
"partition_table=on". If so, 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 eventually was loaded with the ISO image.
|
||||
|
||||
|
||||
File: xorriso.info, Node: Charset, Next: Exception, Prev: Bootable, Up: Options
|
||||
@ -2806,7 +2817,7 @@ programs trigger comparable actions.
|
||||
xorriso options with the same name and hardcoded argument "on",
|
||||
e.g. -acl "on". Explicit arguments are expected by --stdio_sync
|
||||
and --scdbackup_tag.
|
||||
--sort-weight gets as argument a number and an iso_rr_path. The
|
||||
--sort-weight gets as arguments a number and an iso_rr_path. The
|
||||
number becomes the LBA sorting weight of regular file iso_rr_path
|
||||
or of all regular files underneath directory iso_rr_path. (See
|
||||
-find -exec sort_weight).
|
||||
@ -3787,7 +3798,7 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
|
||||
|