From owner-freebsd-hackers Fri Jul 11 15:09:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA05992 for hackers-outgoing; Fri, 11 Jul 1997 15:09:02 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA05985 for ; Fri, 11 Jul 1997 15:08:59 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA25774; Fri, 11 Jul 1997 15:01:31 -0700 From: Terry Lambert Message-Id: <199707112201.PAA25774@phaeton.artisoft.com> Subject: Re: /etc/init.d/ To: aflundi@lundin.abq.nm.us (Alan Lundin) Date: Fri, 11 Jul 1997 15:01:31 -0700 (MST) Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199707111120.FAA01337@lundin.abq.nm.us.> from "Alan Lundin" at Jul 11, 97 05:20:40 am 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 > I guess I don't see what the problem with the > current system is. Currently you can have one > script (assuming you have NFS mounting it amoung > N machines) that says: > > case `hostname` in > $SERVER) > ;; > esac > > where if it is moved to /etc/rc.d, then you must > maintain N scripts, AND you stand more of a chance > that those scripts will get clobbered on the next > OS upgrade. What if I *want* to clobber the scripts for upgraded facilities when I upgrade the facility? What if I want to upgrade some facilities, but not others? I guess you'd have me editing up my rc file so that I couldn't upgrade without editing it again (big hassle). The other side of the coin is, when I install the HTTP server, I want startup and shutdown sequences placed in my startup and shutdown sequences, automatically, without me having to edit an rc file there, either. Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.