From owner-freebsd-hackers Mon May 20 14:44:42 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA20716 for hackers-outgoing; Mon, 20 May 1996 14:44:42 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA20709 for ; Mon, 20 May 1996 14:44:39 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id OAA28549; Mon, 20 May 1996 14:39:50 -0700 From: Terry Lambert Message-Id: <199605202139.OAA28549@phaeton.artisoft.com> Subject: Re: Congrats on CURRENT 5/1 SNAP... To: csdayton@midway.uchicago.edu Date: Mon, 20 May 1996 14:39:50 -0700 (MST) Cc: jehamby@lightside.com, freebsd-hackers@FreeBSD.org In-Reply-To: <199605202002.PAA03266@woodlawn.uchicago.edu> from "Soren Dayton" at May 20, 96 03:02:33 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > 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. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.