On Tue, 20 Jul 1999, Julian Gilbey wrote: > > You started this proposal, so why don't you simply bring it to a > > good end? I'll support your intension...
> So I'd like some advice. The whole policy about /etc/rc?.d fails > immediately when file-rc is being used. So should I actually propose > a rewriting which talks only about runlevels and starting/stopping > services at various runlevels which has no dependency on the > /etc/rc?.d directories? I think that is the correct way forward. It may be the "correct" way to rewrite especially 3.3.1 (where the idea of the SysV init concept with symlinks is explained), but the explanation with symlinks makes this concept easily understandable. At the moment I don't see how to describe this concept independently from the symlinks and runlevel.conf (which is a textual representation of the symlinks in one file). So maybe we should stay on the explanation of the concept with symlinks in 3.3.1 and add some text, which explains that the symlinks doesn't have to be real symlinks but can have some other representation (e.g. one single file runlevel.conf). And than 3.3.3 "Managing the links" has to be changed to put stress on the fact, that update-rc.d MUST be used to create the "symlinks" (at the moment, 3.3.3 only says, that you must not include the links in the package, and you _can_ (this should be changed to "must") use update-rc.d for creating/removing the "links". I fear that a complete rewrite of this section makes it much harder to understand the essentials of this, so we may stay on this "picture" of symlinks, which describes the idea of the functionality. Ciao Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ * PGP: 1024/DD08DD6D 2D E7 CC DE D5 8D 78 BE 3C A0 A4 F1 4B 09 CE AF