Cathy Zhou wrote: > Consider the old configuration: an aggr1 and /etc/hostname.aggr1 > > During the first boot of system upgrade, network/physical would try to plumb > aggr1, but aggr1 cannot be created because the physical link (say bge1) is > not known to the daemon yet (it will not be known until devices/local).
Ah, right. I wonder if this can be worked around by having the link name to link id function attempt to cause a device to attach when a lookup fails. I like your idea of moving device enumeration up in the SMF dependency tree better, however. > My latest proposal can solve this problem. We could not choose to prompt a > warning only when none of the interfaces are plumbed successfully), but that > changes the today's behavior and I don't know whether that is acceptable. > > This makes me wonder another problem: the network-nwam service will not be > able to walk datalinks either at that point. How does that work? How it used > to work? The nwam daemon periodically scans for devices, so maybe the first scan fails, but subsequent attempts succeed.(?) > Can we move the iteration of network devices in or before > network/physical? I will try it out. Sounds like a promising idea, I hope strange SMF service dependencies don't get in the way. -Seb
