Subject: Re: On the proposal to augment NetBSD startup (/etc/rc*/*/*...) system
To: Luke Mewburn <email@example.com>
From: Julian Assange <firstname.lastname@example.org>
Date: 12/05/1999 17:38:48
Luke Mewburn <email@example.com> writes:
> Michael Graff writes:
> > One thing the init.d method doesn't fix, however, is the problem of
> > options. Or is there a /etc/config.d associated with these things?
> What doesn't rc.conf provide in this case? I.e, rc.conf provides this!
> PS: I have considered an /etc/config/ (a la IRIX), but that's
> orthogonal to this issue.
ps. one further suggestion to /etc/rc hackers. please. please. please,
support full logging of rc output to the disk. Remote debugging of rc
sequences is nigh-impossible as rc currently stands.
Stefan Kahrs in [Kah96] discusses the
notion of completeness--programs which never go wrong can be
type-checked--which complements Milner's notion of
soundness--type-checked programs never go wrong [Mil78].