Renee Danson writes: > - nwamd, when ready to install a location, will place the needed > files in /etc/svc/volatile/nwam-loc/. > > - nwamd will disable/re-enable network/location, which will cause > it to re-evaluate its dependencies, and see the required files > under /etc/svc/volatile/nwam-loc/. [...] > I'm thinking the creation of the default locations should be split > off into a separate transient service, which would be inserted between > filesystem/usr and network/location in the dependency chain. That > feels a little heavy-weight; but I haven't yet come up with anything > better. Any ideas?
Isn't network/location enabled by default on the first boot? If it is, then this problem shouldn't occur: nwamd will start, but be unable to do anything until network/location runs. Once it does run, it'll set up the default locations, and nwamd can then choose one and restart network/location. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
