From owner-freebsd-current Mon Oct 23 14: 7:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 6F50337B4D7; Mon, 23 Oct 2000 14:07:18 -0700 (PDT) Received: from localhost (bandix@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id RAA66506; Mon, 23 Oct 2000 17:07:42 -0400 (EDT) (envelope-from bandix@looksharp.net) Date: Mon, 23 Oct 2000 17:07:42 -0400 (EDT) From: "Brandon D. Valentine" To: "Brian O'Shea" Cc: "David O'Brien" , bv@wjv.com, freebsd-current@FreeBSD.ORG Subject: Re: new rc.network6 and rc.firewall6 In-Reply-To: <20001023134843.Y622@beastie.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Oct 2000, Brian O'Shea wrote: >Sounds interesting. To add a new rc script to the system, do you have >to add an entry to an "rc order list" somewhere (in addition to adding >the new script)? How is that handled? The nice (or clumsy, depending >on your point of view) part about the SysV way is that the order in >which the rc scripts are executed is implicit in the scripts' names. >Of course, they have added a symlink maze (worse, hard links on HP-UX) >on top of that, making it tedious to maintain rc scripts by hand >(maybe that was by design). Hmm I don't have any NetBSD machines running the later 1.5 revisions yet, so I've not seen the new scripts, but I would say that adding a new script to a list of rc files would be much less hassle than adding an entry in a monolithic /etc/rc to process that new file. -- Brandon D. Valentine "Few things are harder to put up with than the annoyance of a good example." -- Mark Twain, Pudd'nhead Wilson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message