Subject: Re: PROPOSAL: /etc/rc, /etc/init.d/*, ...
To: Luke Mewburn <email@example.com>
From: Hubert Feyrer <firstname.lastname@example.org>
Date: 12/01/1999 05:02:56
On Wed, 1 Dec 1999, Luke Mewburn wrote:
- It's nice that you support both generating SysV (rc?.d) and BSD (rc)
environments, but I think we should decide for one system to use.
- I wouldn't mind see the rc.sh replace the /etc/rc we have now
- I feel uneasy with the idea that there is a possibility to get my
system in a non-booting state by touching /etc/rc
- Most important: what does it need to drop in a "classical" SysV script,
as distributed with various pkgs? The examples you show use a lot of
variables which usual SysV scripts don't use. They're usually just
shell scripts that know what to do with 'start' and 'stop', are the
lacking options (or the errors caused by using them) caught?
- Is there a way to drop in init-scripts in some other place than
/etc/init.d (e.g. /usr/pkg/etc/init.d, /usr/local/etc/init.d, ...), and
get them picked up?
NetBSD - Better for your uptime than Viagra