Changed wrong use of "resp." in docs
This commit is contained in:
@ -42,7 +42,7 @@ To build libisoburn go into its toplevel directory and execute:
|
||||
|
||||
- make
|
||||
|
||||
To make the library and the xorriso application accessible for running resp.
|
||||
To make the library and the xorriso application accessible for running and
|
||||
software development:
|
||||
|
||||
- make install
|
||||
@ -73,7 +73,7 @@ extensions. Its API is described in libisofs/libisofs.h .
|
||||
|
||||
For xorriso features see its man page xorriso/xorriso.1 or
|
||||
its GNU info document xorriso/xorriso.info.
|
||||
For the corresponding C language API see libisoburn/xorriso.h (resp.
|
||||
For the corresponding C language API see libisoburn/xorriso.h (or
|
||||
xorriso/xorriso.h in the build directory).
|
||||
The implementation this API is part of libisoburn.
|
||||
The xorriso command line tool gets installed as dynamically linked
|
||||
|
@ -22,8 +22,8 @@ extend the unclaimed area into vital blocks of the ISO image.
|
||||
Meanwhile Debian
|
||||
[http://cdimage.debian.org/cdimage/daily-builds/daily/current/ daily]
|
||||
and [http://cdimage.debian.org/cdimage/weekly-builds/ weekly] builds make
|
||||
use of this feature with their bootable ISO images for i386 and amd64. E.g.
|
||||
[http://cdimage.debian.org/cdimage/daily-builds/daily/current/i386/iso-cd/debian-testing-i386-businesscard.iso debian-testing-i386-businesscard.iso].
|
||||
use of this feature with their bootable ISO images for i386. E.g.
|
||||
[http://cdimage.debian.org/cdimage/daily-builds/daily/current/i386/iso-cd/debian-testing-i386-netinst.iso debian-testing-i386-netinst.iso].
|
||||
|
||||
According to a
|
||||
[http://syslinux.zytor.com/archives/2011-March/016201.html thread of march 2011]
|
||||
@ -51,12 +51,12 @@ with 16 * 2kB partition offset. Isohybrid MBR patching was done by xorriso.
|
||||
Details:
|
||||
|
||||
The first 32 kB of an ISO 9660 image are called System Area and may host any
|
||||
byte pattern. In the case of RIPLinux-9.3-non-X.iso only the first 512 bytes
|
||||
are non-zero. But to avoid any assumptions, all 32 kB get copied here.
|
||||
byte pattern. The first 512 bytes of RIPLinux-9.3-non-X.iso contain the
|
||||
isohybrid capable MBR, which will be re-used in this example.
|
||||
{{{
|
||||
dd if=RIPLinux-9.3-non-X.iso bs=1K count=32 of=RIPLinux-9.3-non-X.sysarea
|
||||
dd if=RIPLinux-9.3-non-X.iso bs=512 count=1 of=RIPLinux-9.3-non-X.mbr
|
||||
}}}
|
||||
Normally the System Area file with its MBR is provided by the Syslinux
|
||||
Normally the isohybrid MBR is provided by the Syslinux
|
||||
installation under the name isohdp[fp]x*.bin .
|
||||
E.g. /usr/lib/syslinux/isohdpfx.bin
|
||||
|
||||
@ -68,7 +68,7 @@ The files of the image are made accessible for reading
|
||||
A new ISO image gets composed. The first three lines of arguments are taken
|
||||
from the prescriptions of ISOLINUX wiki and adapted to the names used in
|
||||
RIPLinux-9.3-non-X.iso.
|
||||
Option -isohybrid-mbr imports the copied System Area and patches the MBR
|
||||
Option -isohybrid-mbr imports the copied MBR and patches it
|
||||
according to rules published by hpa on Syslinux mailing list.
|
||||
Option -partition_offset 16 causes the first partition to start at 2 kB block
|
||||
number 16. It also prepares the image to be mountable by this partition, too.
|
||||
@ -77,7 +77,7 @@ number 16. It also prepares the image to be mountable by this partition, too.
|
||||
-o new_image.iso \
|
||||
-b boot/isolinux/isolinux.bin -c boot/boot.cat \
|
||||
-no-emul-boot -boot-load-size 4 -boot-info-table \
|
||||
-isohybrid-mbr RIPLinux-9.3-non-X.sysarea \
|
||||
-isohybrid-mbr RIPLinux-9.3-non-X.mbr \
|
||||
-partition_offset 16 \
|
||||
/mnt
|
||||
}}}
|
||||
@ -177,7 +177,7 @@ Open questions:
|
||||
|
||||
- Shall the partition of an isohybrid image be marked bootable ?
|
||||
Currently xorriso keeps the 0x80 mark of an imported MBR
|
||||
resp. the 0x80 mark which xorriso sets by its own MBR
|
||||
and the 0x80 mark which xorriso sets by its own MBR
|
||||
preparations.
|
||||
- If not to be marked bootable:
|
||||
What equipment would the partition need to justify having the mark ?
|
||||
@ -196,7 +196,7 @@ int iso_write_opts_set_part_offset(IsoWriteOpts *opts,
|
||||
int iso_write_opts_set_system_area(IsoWriteOpts *opts, char data[32768],
|
||||
int options, int flag);
|
||||
}}}
|
||||
resp. by libisoburn calls
|
||||
or by libisoburn calls
|
||||
{{{
|
||||
int isoburn_igopt_set_part_offset(struct isoburn_imgen_opts *opts,
|
||||
uint32_t block_offset_2k,
|
||||
@ -212,7 +212,7 @@ int isoburn_igopt_set_system_area(struct isoburn_imgen_opts *o,
|
||||
int isoburn_igopt_get_system_area(struct isoburn_imgen_opts *o,
|
||||
char data[32768], int *options);
|
||||
}}}
|
||||
resp. by xorriso options
|
||||
or by xorriso options
|
||||
{{{
|
||||
-boot_image any partition_offset=(2kb_block_adr)
|
||||
-boot_image any partition_sec_hd=(number)
|
||||
|
Reference in New Issue
Block a user