This hasn't been a problem up to 2.1.125. Mainly, linux boots, recognize
these as extended partitions, and accept to mount them when I want.
Amidst these special partitions, most are 44bsd, apart from one ext2fs
partition. Why ? My network card does not work under openbsd, I have some
cvs-updated stuff on that partition, and bsd ext2fs is more reliable than
linux ufs these days...
Enter 2.1.126. The bsd partitions still mount ok, apart from that specific
ext2fs partition. I get a message from drivers/ll_rw_blk.c:
"attempt to access beyond end of device".
I think I can figure out what that message means, as this ext2fs disklabel
partition isn't part of the partition it's supposed to.
The weird part is, after scanning patch-2.1.126 carefully, I can't figure
out what changed to trigger that check. Help ?!?
The other point being that I believe that a bsd disklabel may have to label
more than a dos partition, in which case that check is actually out of order.
-- Marc Espie |anime, sf, juggling, unicycle, acrobatics, comics... |AmigaOS, OpenBSD, C++, perl, Icon, PostScript... | `real programmers don't die, they just get out of beta'- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/