On Fri, Dec 10, 2010 at 06:26:36PM +0100, frantisek holop wrote:
quoted text
> hmm, on Fri, Dec 10, 2010 at 05:38:19PM +0200, Antoine Jacoutot said that
> > On Fri, 10 Dec 2010 16:25:40 +0100, frantisek holop
> > <minusf@obiit.org> wrote:
> > >why not reuse the /etc/rc.conf style "set these to "NO" to turn
> > >them off.
> > >otherwise, they're used as flags" approach?
> > 
> > It's not how it works, it won't start anything unless you add it to
> > the rc_scripts variable.
> 
> thanks for pointing that out, now i see.
> what confused me was that there was no default $rc_scripts
> 
> was there a reason not to be consistent with /etc/rc.conf services?
> 

Yes, the principle of least surprise !

We're not debian, so some packages include several components. Ditto
for dependencies.
Let's say you install a bunch of things in a hurry.

Then you find out, when you reboot a machine, that you're suddenly blessed
with five new daemons that you did not *explicitly request*.

Good luck systematically checking /etc/rc.d for those surprises after
a new package install...