> I don't see a problem. Let the kernel read the partition table, > iterate over the partitions, extract properties from each partition, > try to match a dk to each partition by properties (e.g., guid(dk3) > == guid(partition 7 at sd0)). If there is a match, take the dk unit > number from the matching property list (e.g., dk3). If there is no > match, choose a unit number that is used by neither a device_t or a > configuration properties list.
That way you teach lots of knowledge into dk(4). That's what I don't like to do. Now you pass GUID from kernel config, what is the point to have the predefined unit number 3? Masao -- Masao Uebayashi / Tombi Inc. / Tel: +81-90-9141-4635