On Mon, 6 Dec 2004, Simon 'corecode' Schubert wrote:
> i had a look at loader, and it seemed to me that there is logic for extended
> slices...
When you asked for volunteers to patch loader I started looking at the code
also -- and I'm still looking ;o) Can you point out for me which file(s)
contain the relevant code?
> could you please post your fdisk output for the original
> dfly-in-extended slice setup? i suspect the new FAT32 extended slice ids not
> working correctly.
Note that partition 4 is *not* (of course) the logical partition I referred to
earlier -- it is my gcc34 install of DFly which boots perfectly. My logical
partition containing DFly is ad1s8 which I can mount okay but can't boot from.
# fdisk -v ad1
******* Working on device /dev/ad1 *******
parameters extracted from in-core disklabel are:
cylinders=14946 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=14946 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 169,(NetBSD)
start 16065, size 7373835 (3600 Meg), flag 80 (active)
beg: cyl 1/ head 0/ sector 1;
end: cyl 459/ head 254/ sector 63
The data for partition 2 is:
sysid 5,(Extended DOS)
start 7389900, size 57014685 (27839 Meg), flag 0
beg: cyl 460/ head 0/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 166,(OpenBSD)
start 13703445, size 12884130 (6291 Meg), flag 0
beg: cyl 853/ head 0/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
sysid 165,(DragonFly/FreeBSD/NetBSD/386BSD)
start 219399705, size 12321855 (6016 Meg), flag 0
beg: cyl 1023/ head 0/ sector 1;
end: cyl 1023/ head 254/ sector 63