Updated documentation about MBR

This commit is contained in:
2010-04-18 15:46:12 +00:00
parent cc6a26b917
commit 04c5aa191c
3 changed files with 111 additions and 87 deletions

View File

@ -378,7 +378,12 @@ xorriso is able to create or maintain an El Torito object which makes such
an image bootable. For details see option -boot_image.
.br
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 \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
only on overwriteable media.
.br
Emulation -as mkisofs supports the example options out of the ISOLINUX wiki.
It also supports the options used in GRUB script grub-mkrescue.
@ -2245,9 +2250,6 @@ 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.
.br
Special disk_path "/dev/zero" causes 32k of NUL-bytes.
Use this to discard an MBR which eventually was loaded with the ISO image.
.br
Other than a El Torito boot image, the file disk_path needs not to be added
to the ISO image.
.br
@ -2257,13 +2259,23 @@ to the ISO image.
446 to 511 of the System Area.
.br
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.
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.
.br
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.
.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
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.
.br
Special "system_area=/dev/zero" causes 32k of NUL-bytes.
Use this to discard an MBR which eventually was loaded with the ISO image.
.br
.TP
.B Character sets:
.PP
@ -3131,7 +3143,7 @@ same name and hardcoded argument "on", e.g. -acl "on".
Explicit arguments are expected by --stdio_sync
and --scdbackup_tag.
.br
--sort-weight gets as argument a number and an iso_rr_path.
--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).