On 2009-01-15 19:05, Marcel Moolenaar wrote: >> Hmm, strangely enough I have multiple systems which really do use ad0s1 >> while installed DD using sysinstall, and have been using that since years... > This is a problem with sysinstall. It looks like DD is broken. > MBR partitions are always created. Indeed, and the MBR itself is filled with /boot/boot1, plus a partition table. It is possible this was done to appease some PC BIOSes, because some of those refuse to boot, if there is no "valid" MBR with an active partition... > GEOM_PART correctly uses the > BSD disklabel that's in the 2nd sector, but GEOM_MBR claims the > MBR being unaware that the disk is DD. But how can this be, if I don't have GEOM_MBR in my kernel config? (I'm using GENERIC, in fact.) > libdisk is broken in that it should > not create MBR slices for DD configurations to begin with... As stated above, this might be on purpose; enough braindead BIOSes out there... :)Received on Thu Jan 15 2009 - 18:25:00 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:40 UTC