y dd the image to the flash the partition table would have been overwritten=
which in turn would be incorrect for my compact flash as it would have dif=
ferent block sizes. I am going out on a limb and will no doubt get shot dow=
n in flames=2C so please excuse me ignorance if the above is wrong (i suspe=
ct it is!).
So then i tried to bypass this and:
I mount the debian live image with:
mount -o loop=2Coffset=3D512 binary.img /mnt/deblive/
Load the bootsector of syslinux:
dd if=3D/usr/lib/syslinux/mbr.bin of=3D/dev/sdb bs=3D512 count=3D1Make a 12=
8MB fat16 parition (made with parted) on sdb1=2C set it bootable
I then mount /dev/sdb1 and copy all files recursively:
mnt /dev/sdb1 /mnt/cf
cp -r /mnt/deblive/* /mnt/cf/
Is there any way that the device can be given to the lh_build scripts or in=
configuration to use a physical device ad write to it direct rather than c=
reating the image file?
Please excuse me if its in the FAQ i have looked but my head isnt quite thi=
nking straight after playing with this all day.
Many thanks in advance=2C
Make a mini you on Windows Live Messenger!
Content-Type: text/html; charset="iso-8859-1"
<body class=3D'hmmessage'>Hi=2C i have built the Debian Live binary.img usi=
ng lh_build and as per the Wiki =3BI 'dd' it to /dev/sdb. All is well a=
nd the compact flash boots=2C however it soon starts chucking up a load of =
errors of file seeks outside of the physical dimensions of the disk in /var=
Aug =3B 9 08:11:55 debian40server kernel: attempt to access beyond end =
of device<BR>Aug =3B 9 08:11:55 debian40server kernel: sdb1: rw=3D0=2C =