> We don't need a second mechanism to handle dk(4), do we? If dk3 should > attach to the volume with GUID 60708090-a0b0-c0d0-e0f0-01020304050, let > the device properties say so: > > <plist version="1.0"> > <dict> > <key>device-driver</key> > <string>dk</string> > <key>device-unit</key> > <integer>0x3</integer> > <key>guid</key> > <string>60708090-a0b0-c0d0-e0f0-01020304050</string> > </dict> > </plist>
Usually GUID is recorded in partition table. You're viewing things in reverse order... Masao -- Masao Uebayashi / Tombi Inc. / Tel: +81-90-9141-4635
