On Wed, 2008-04-23 at 14:59 -0700, Cathy Zhou wrote: > Sebastien Roy wrote: > > The dlmgmt_create_common() function currently requires a link name, and > > dlmgmt_upcall_create() always calls this function with the devname to > > ensure that the linkname matches the underlying device name. We could > > change those semantics such that dlmgmtd_create_common() could take a > > NULL link name. If passed in a NULL link name, it could come up with a > > link name based on the algorithm specified in the service property > > loaded above. > > > We still need the devname, as the daemon needs to know the devname associated > to a link, so that it maps to the same link name when the device instance > detaches and reattaches.
True; the devname could be passed in as a separate argument. > > > > One hole in this approach exists when dlmgmtd isn't running and network > > devices attach (does this happen during reconfigure boot?). What do we > > do for that case? Perhaps we need to re-think whether links are created > > at all if devices attach and dlmgmtd isn't running... > > > dlmgmtd is usually running before network attaches, except during the > netinstall or netboot, that a primary device is usually plumbed by the kernel > at very early phase before any daemon can be run. Note that a link cannot be > renamed when it is plumbed. How to rename this primary device to a vanity > name > is another problem that we need to resolve. Do we care about what datalinks are called during a netboot/netinstall? -Seb
