Date: Sat, 24 Dec 2011 13:50:13 -0800 From: Doug Barton <dougb@FreeBSD.org> To: Warner Losh <imp@bsdimp.com> Cc: Maxim Ignatenko <gelraen.ua@gmail.com>, freebsd-rc@FreeBSD.org Subject: Re: conf/163508: [rc.subr] [patch] Add " enable" and " disable" commands to rc.subr Message-ID: <4EF64915.4030006@FreeBSD.org> In-Reply-To: <D9E8E12B-7E7F-4164-802F-4F6FE7DFB397@bsdimp.com> References: <201112241230.pBOCUF3h064098@freefall.freebsd.org> <D9E8E12B-7E7F-4164-802F-4F6FE7DFB397@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/24/2011 08:46, Warner Losh wrote: > Also, let's not reject it before it is done. Let's reject it when it actually doesn't handle the cases that are interesting. No sense in cutting off a good feature because of some theoretical problem. It is a problem we have sometimes in the project... Warner, You seemed to have missed the bit where I said, "We've already been down this path once before, and it turns out to be way harder to do this right than it looks at first glance." Just as an example of potential problems, imagine a scenario where the user has foo_enable=NO in rc.conf, but the service keeps starting up anyway. For better or worse rc.d offers a lot of flexibility in how services are enabled. We've already heard from users who use those various mechanisms, and don't want them removed/broken. Absent an overhaul of the underlying structure of configuration files (which would violate one or both of remove/break existing functionality) there is no way to add this feature in a thorough manner. Adding it in a less-than-thorough manner will cause more problems than it solves. Which returns me to my original point, how hard is it to edit rc.conf anyway? Doug -- [^L] Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EF64915.4030006>