From owner-freebsd-hackers Sun Apr 27 19:06:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA12661 for hackers-outgoing; Sun, 27 Apr 1997 19:06:47 -0700 (PDT) Received: from kalypso.cybercom.net (kalypso.cybercom.net [206.28.134.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA12653 for ; Sun, 27 Apr 1997 19:06:41 -0700 (PDT) Received: from atlanta (mfd-dial1-18.cybercom.net [206.28.134.50]) by kalypso.cybercom.net (8.8.5/8.8.5) with SMTP id WAA04684; Sun, 27 Apr 1997 22:03:40 -0400 (EDT) Message-Id: <1.5.4.32.19970428020340.007096ac@cybercom.net> X-Sender: ksmm@cybercom.net X-Mailer: Windows Eudora Light Version 1.5.4 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 27 Apr 1997 22:03:40 -0400 To: Brandon Gillespie , Terry Lambert From: The Classiest Man Alive Subject: Re: /etc/netstart bogons.. Cc: jkh@time.cdrom.com, hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 03:23 PM 4/27/97 -0600, Brandon Gillespie wrote: >> > I think it is more a case of functionality, rather than personal >> > preference. With the rc.d/init.d approach you have more modularity, >> > and the ability to start/stop random packages in a consistent way. >> > There is also a single standard place that a vendor can throw a >> > startup script in--this is a good thing. >> >I definitely agree, I abhore the rc?.d stuff--I can never remember what is >what (especially since it has some variance depending upon the O/S). What What is it that ties us to those arcane eight-dot-three names anyway? Why can't we just have a master rc script that launches others, like network.d or filesystems.d? Sure would beat hunting through rc* files to change the startup options on your daemons. K.S.