On Tue, Mar 01, 2011 at 09:50:27AM +0100, Christian Pohl wrote: > Marc Haber wrote: > > On Mon, 28 Feb 2011 22:26:56 +0100, Arthur de Jong > > <adejong@debian.org> wrote: > >>On Sat, 2011-02-26 at 21:44 +0100, Tollef Fog Heen wrote: > >>> Personally, I'd rather we didn't have them, as this is supposed to be > >>> controlled by the rcN.d links and if that interface is too hard for > >>> people we should fix that rather than invent multiple ways of disabling > >>> daemons, but the current mess is, well, a mess. > >>I would also love to have a way to easily configure which daemons should > >>be started at boot time. I don't know whether switching to insserv made > >>things simpler in that regard though. > Isn't update-rc.d the way to configure the rc.d scripts? No, it's a way for *maintainer scripts* to manage init scripts. > Or am I old-fashioned. You are using an interface that was never meant for administrator use. Nowadays there's an 'update-rc.d enable/disable', but even that, I think, was intended to be a backend for the 'service' command. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slangasek@ubuntu.com vorlon@debian.org
Attachment:
signature.asc
Description: Digital signature