On Tue, Dec 23, 2008 at 01:47:04PM -0500, James Carlson wrote: > 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.
The problem is that we had to make things a little more complex. A couple components of the location are files that must reside in well- known locations in the filesystem, and thus a location cannot be installed until we have a writable filesystem (after nwam starts), allowing those files to be copied into place. So the plan was for nwamd to put the files in a relay directory (under /etc/svc/volatile, which is writable very early, when nwam starts) as soon as it has selected a location to install/activate. network/location depends on filesystem/usr (so it will have the writable filesystem) and on nwamd having placed files under /etc/svc/volatile. So network/location can't run until nwamd has chosen a location, but on that first boot, nwamd can't choose a location until network/location has run (assuming that the user has not yet created any locations, which seems likely). -renee
