From d8c8b92069933173c582babd200abf2b047baae9 Mon Sep 17 00:00:00 2001 From: Thomas Schmitt Date: Wed, 9 Mar 2011 11:01:48 +0000 Subject: [PATCH] Updated partition offset wiki --- libisoburn/trunk/doc/partition_offset.wiki | 16 +++++----------- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/libisoburn/trunk/doc/partition_offset.wiki b/libisoburn/trunk/doc/partition_offset.wiki index c370c071..ff35e7a9 100644 --- a/libisoburn/trunk/doc/partition_offset.wiki +++ b/libisoburn/trunk/doc/partition_offset.wiki @@ -46,6 +46,10 @@ are non-zero. But to avoid any assumptions, all 32 kB get copied here. {{{ dd if=RIPLinux-9.3-non-X.iso bs=1K count=32 of=RIPLinux-9.3-non-X.sysarea }}} +Normally the System Area file with its MBR is provided by the Syslinux +installation under the name isohdp[fp]x*.bin . +E.g. /usr/lib/syslinux/isohdpfx.bin + The files of the image are made accessible for reading {{{ mount -o loop RIPLinux-9.3-non-X.iso /mnt @@ -78,7 +82,7 @@ and plugged into a Debian system. yields {{{ Device Boot Start End Blocks Id System -/dev/sdb1 * 64 119215 59576 17 Hidden HPFS/NTFS +/dev/sdb1 * 64 120831 60384 17 Hidden HPFS/NTFS }}} I can mount /dev/sdb and /dev/sdb1 alike: @@ -154,16 +158,6 @@ preparations. - If not to be marked bootable: What equipment would the partition need to justify having the mark ? -- I am still puzzled by the cylinder-head-sector ambiguity. How does a reader -of the partition table determine the numbers for heads/cylinder and -sectors/head ? -fdisk tells about my /dev/sdb -{{{ - 105 heads, 17 sectors/track, 2193 cylinders, total 3915776 sectors -}}} -My partiton table rather was computed with 255 heads/cylinder, 63 sectors/head -Debian does not mind the difference. (It uses the 32 bit LBAs, i assume.) - ------------------------------------------------------------------------ Application: