Date: Mon, 18 May 1998 11:20:04 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Dan Janowski <danj@3skel.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: system config database... Message-ID: <28331.895515604@time.cdrom.com> In-Reply-To: Your message of "Mon, 18 May 1998 14:09:29 EDT." <Pine.BSF.3.96.980518140136.22495F-100000@fnur.3skel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> in a configuration. There are a few things that are > too arbitrary, mostly cleanup stuff like ptmp, and vi -r. > Those things seem better in their own scripts, no? No. :) If you're going to offer one-stop shopping then you need to just toss an umbrella over it all. The proliferation of little scripts which "just don't quite fit" into the overall framework is what makes debugging a system startup failure such a bear on the more complex rc.d-using systems and what we want to avoid. You want to think of the entire startup process, from init's first gasp to the very last "rc.local" type of action, as a single system with a decent API for adding, deleting and editing the objects it manages. Anything less ambitious just isn't worth accepting all the transition shock hassles for, IMHO, and that's speaking as someone who's inflicted fairly major transition shock on the user base not just once but _twice_ (/etc/sysconfig followed by /etc/rc.conf) for what, in hindsight, wasn't that much of a gain. If I had it to do over, I'd have either just left the pre-sysconfig mechnanisms completely alone or gone for broke and fixed it once and for all in a far more elegant fashion. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28331.895515604>