On Tue, Mar 07, 2006 at 05:59:15PM -0500, Dave Miner wrote: > Nicolas Williams wrote: > >/etc/system has the one benfit of being a single place to look. And > >some such settings can be changed at runtime (though mdb is not a sysadmin- > >friendly tool for doing so). > > > > And the drawback of being a free-for-all dump of random things that > wouldn't necessarily occur to anyone who's not a serious Solaris expert > as being the obvious place to configure anything. Not that a driver > .conf file is entirely free of those attributes...
Yes, which leaves us... wanting something else entirely, no? > >I suspect this struggle will continue until a project comes along to > >rationalize and replace/clean-up/integrate ndd and /etc/system settings > >into a sysadmin-friendly framework that properly supports presistence > >(but also temporary settings). > > > > I'm skeptical such a project will occur anytime soon, at least on Sun's > dime, because these are not in the class of tasks that most admins > should have to be doing and so it's easy to find uses of our money which > will give more demonstrable returns. I don't think the two solutions > Darren suggested are the only ones possible for this case, but what do I > know? ;-) I have no idea how likely such a project is, but sysadmins certainly have had to set /etc/system, driver .conf and ndd settings, and they've had to write rc files for it, and now SMF services. So I do think that this state of affairs cries out for a better solution. _______________________________________________ networking-discuss mailing list [email protected]
