From owner-freebsd-hackers Tue Feb 2 06:41:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21673 for freebsd-hackers-outgoing; Tue, 2 Feb 1999 06:41:53 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21668 for ; Tue, 2 Feb 1999 06:41:50 -0800 (PST) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id JAA13206; Tue, 2 Feb 1999 09:45:41 -0500 (EST) (envelope-from witr@rwwa.com) Message-Id: <199902021445.JAA13206@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Richard Wackerbarth cc: Wes Peters , hackers@FreeBSD.ORG Subject: Re: more modular rc/init/uninit system... In-reply-to: Your message of "Mon, 01 Feb 1999 05:59:35 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Feb 1999 09:45:41 -0500 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rkw@dataplex.net said: :- Actually, more than "on startup". You should be able to move from one :- environment to another at any time by changing the target. (eg run :- level) I think it is important to avoid conflating "configuration management" with "startup/shutdown" management. The SYSV run-levels do that and I think that is a great flaw. I'd like to separate these two things. So, for example, deciding whether to start PPP over your ISP or Ethernet over your office LAN would be a "configuration management" issue. Actually starting the system, given a particular configuration, would be a "startup/shutdown management" issue. That is not to say that the one wouldn't draw on the features of the other. For example, should you decide to switch from one configuration to another without restarting the system (by sleeping your laptop at the office and waking it up at home) you would presumably use the "startup/shutdown management" features to stop/start/restart the appropriate services to effect the switch to the new configuration. Keeping a strict demarcation between these two entities will result in a much simpler and thus understandable/maintainable implementation than a mongo-ronco-Makefile-prolog-rule-based-config-rewriting does-everyting tool. IMO. My proposal carefully addressed only the startup/shutdown management issues, leaving the configuration management issues to some other to-be-designed-in-the-future tool. --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message