Cathy Zhou wrote: > Hi Dave, > > We are currently testing netinstall based on the Clearview UV bits. As you > might know, UV introduces a daemon linkmgmtd that manages link names and > linkids of all network data-links. This daemon is required by "ifconfig -a > plumb" because ifconfig needs to query into the daemon to know the link > names of all physical links on the system. > > As part of the install-discovery service, it runs "ifconfig -a plumb" to > discover all network data-links on the client system. Therefore, in order > for the install-discovery service to succeed, we make the install-discovery > service depend on the linkmgmtd service. The test shows a problem with this > change. Sometimes during netinstall, it prompts warnings like: > > "Could not log for svc:/network/linkmgmtd:default: > open(/var/svc/log//network-linkmgmtd:default.log) failed with > No such file or directory." > > Investigation shows the problem is due to a short period of unavailability > of "tmp/root", between the install-discovery script mounts tmpfs and unpacks > all the writable files into /tmp. > > One way to fix this is to split the current install-discovery service into > two services. The first one does the /tmp mount and /tmp/root > initialization, and the second one does the "ifconfig -a plumb" network > data-link discovery. linkmgmtd needs to depend on the first service and be > dependent of the second service. > > What do you think of this fix? As installation is a separate consolidation > from ON, please let us know how to proceed. >
This is probably a reasonable fix for now, though I'm surprised that you don't need the devfsadm invocations first, too? I've cc'ed install-discuss in case anyone else sees an issue. We'll be completely refactoring the miniroot and these services in the near future anyway, but that's not something you want to be waiting on. Dave
