Renee Danson writes: > On Tue, Dec 23, 2008 at 02:29:13PM -0500, James Carlson wrote: > > If nwamd hasn't chosen something, shouldn't network/location just go > > ahead with some default, such as "no network?" > > > > Or is that too simple? > > Oh, way too simple, of course. :-)
;-} > Independently, network/location will be started when filesystem/usr is > online. The first thing it will do is create the default locations, if > needed. It will then check for a location that nwamd wants to be installed, > and finish installing and activate if that's present. If not, it will > install and activate the No-Net location. Yes, that's the idea. > 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? > 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. -- 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
