David Bustos wrote: > Quoth Zhenghui Xie on Fri, May 12, 2006 at 12:04:05PM -0700: >> netprofd is the NWAM daemon to manipulate network links and interfaces. >> network/profiled is the SMF service for this daemon and its start method >> starts netprofd. This service should be started fairly early at boot, so >> it only depends on network/pfil. (Basically, network/profiled can be >> considered as the replacement of current network/physical) >> >> It makes netprofd running early in boot, before i_ddi_io_initialized has >> been called. But one of the first things netprofd does is 'ifconfig -a >> plumb', which causes the problem. log file messages in [1]. > > Doesn't network/physical also plumb interfaces? Why does > network/physical work, but netprofd's ifconfig -a plumb fail? >
network/physical does specific plumbs based on what hostname.* files exist, which doesn't require walking the device tree. Whereas "ifconfig -a plumb" does, and is the point at which it's failing for Jan. At installation, we use an "ifconfig -a plumb" to find all the network devices and attempt to configure them, but the miniroot ordering ensures that the device tree is built before that happens. The correct fix is clearly to rearrange the ordering here; the root problem is identity:node depending on the this service, which really isn't necessary for the prototype - we've clearly proven over the years that client systems can work just fine when their nodename doesn't relate to their network presence. That's why netprof & inetmenu tell you to configure your system as "standalone", because it effectively breaks this dependency. Dave
