On Tue, Dec 23, 2008 at 03:32:55PM -0500, James Carlson wrote: > Renee Danson writes: > > > It's that last line that worries me. There's a lot of grunginess required > > to install a location (which, incidentally, will disappear when locations > > can be instances of enhanced smf profiles), and that grunginess mostly > > lives in nwamd. Replicating it in network/location's start method feels > > even more grungy. > > If you were to go with a split service as you previously suggested, > you'd have to have duplicated grunge as well, right?
No, it could just be in nwamd; the first service would load up the default locations, and then network/location wouldn't run until nwamd had selected and done most of the installation of the chosen location (which it would be able to do because the first service took care of loading in the minimally required locations). > > I suppose, though, that it (the location installation grunginess) doesn't > > have to live in nwamd. Especially considering that we hope it will be > > going away soon. We could write a script or c program that does it, and > > then that could be called from either nwamd or network/location's start or > > refresh method. That script or c program could then be replaced once we > > have smf infrastructure to activate an enhanced profile. > > > > Does that sound reasonable? Simple enough? > > Yes, that does sound like a good way out. Great. I like it better than the extra-service idea. thanks, renee
