Oh, boo hoo hoo: Big Bad Blue has stolen BSDs partition number. That's really ignorant of them, and they deserve to be punished by losing sales. But for anyone who want to develop a fix, here are some ideas:
1) Patch the fsck'ing BIOS. [Dangerous on a laptop]
2) Modify the bootloader so that it re-writes the partition table on every boot using some other type. Writeback at shutdown.
3) recompile your BSD kernel to use a different filesystem type. Or really use a different type for the filesystems [but then you look one of the biggest reasons for running BSD--softupdates].
This can be gotten around. IBM has just done something stupid. They probably ought to have stolen the XENIX fs number instead!
Workarounds (Score:5)
1) Patch the fsck'ing BIOS. [Dangerous on a laptop]
2) Modify the bootloader so that it re-writes the partition table on every boot using some other type. Writeback at shutdown.
3) recompile your BSD kernel to use a different filesystem type. Or really use a different type for the filesystems [but then you look one of the biggest reasons for running BSD--softupdates].
This can be gotten around. IBM has just done something stupid. They probably ought to have stolen the XENIX fs number instead!