No subject

[bogus@does.not.exist.com ()]

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!).<BR>
&nbsp=3B<BR>
So then i tried to bypass this and:<BR>
&nbsp=3B<BR>
I mount the debian live image with:<BR>
mount -o loop=2Coffset=3D512 binary.img /mnt/deblive/<BR>
&nbsp=3B<BR>
Load the bootsector of syslinux:<BR>
dd if=3D/usr/lib/syslinux/mbr.bin of=3D/dev/sdb bs=3D512 count=3D1<BR><BR>M=
ake a 128MB&nbsp=3Bfat16 parition (made with parted) on sdb1=2C set it boot=
able<BR>
&nbsp=3B<BR>
I then mount /dev/sdb1 and copy all files recursively:<BR>
mnt /dev/sdb1 /mnt/cf<BR>
cp -r /mnt/deblive/* /mnt/cf/<BR>
umount /dev/sdb1<BR>
&nbsp=3B<BR>
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?<BR>
&nbsp=3B<BR>
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.<BR>
&nbsp=3B<BR>
Many thanks in advance=2C<BR>
&nbsp=3B<BR>
Chris<BR><br /><hr />Make a mini you on Windows Live Messenger! <a href=3D'=
http://clk.atdmt.com/UKM/go/107571437/direct/01/' target=3D'_new'>Try it No=
w!</a></body>
</html>=

--_2e5ab1cf-35cd-42fd-a1cd-c39042b8fdbe_--