Date: Tue, 21 May 1996 09:09:33 +0600 (ESD) From: "Serge A. Babkin" <babkin@hq.icb.chel.su> To: terry@lambert.org (Terry Lambert) Cc: csdayton@midway.uchicago.edu, jehamby@lightside.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Congrats on CURRENT 5/1 SNAP... Message-ID: <199605210309.JAA08088@hq.icb.chel.su> In-Reply-To: <199605202139.OAA28549@phaeton.artisoft.com> from "Terry Lambert" at May 20, 96 02:39:50 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > and revamp the boot scripts to support > > > SVR4-style /etc/init.d for safer package installs. > > > > I would like to see this happen. I find it much more flexible than > > one flat file. Are there compelling reasons for keeping the current > > structure for boot scripts. > > There are compelling modular installation and packaging reasons for > *not* keepingthe current structure. > > One issue that SVR4 does not address (doesn't mean we can't) is > a read-only / (and therefore /etc) and the ability to support > drop-in per system package/daemon configurations anyway. How about the HP-UX 10 approach ? They have divided their boot scripts into 2 parts: one, the fixed is in /sbin/init.d (marked as read-only) and the tunes are in /etc/rc.config (global definitions) and /etc/rc.config.d (definitions for particular scripts). This is very like FreeBSD rc and sysconfig files but splitted. May be it is a good model ? -SB
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605210309.JAA08088>