Date: Mon, 23 Oct 2000 14:18:15 -0700 From: "Brian O'Shea" <boshea@ricochet.net> To: "Brandon D. Valentine" <bandix@looksharp.net> Cc: "Brian O'Shea" <boshea@ricochet.net>, "David O'Brien" <obrien@FreeBSD.ORG>, bv@wjv.com, freebsd-current@FreeBSD.ORG Subject: Re: new rc.network6 and rc.firewall6 Message-ID: <20001023141815.A622@beastie.localdomain> In-Reply-To: <Pine.BSF.4.21.0010231706190.65525-100000@turtle.looksharp.net>; from Brandon D. Valentine on Mon, Oct 23, 2000 at 05:07:42PM -0400 References: <20001023134843.Y622@beastie.localdomain> <Pine.BSF.4.21.0010231706190.65525-100000@turtle.looksharp.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 23, 2000 at 05:07:42PM -0400, Brandon D. Valentine wrote: > 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. > I agree. However, I was comparing it to the SysV rc script format, not to the existing BSD rc scripts. -brian -- Brian O'Shea boshea@ricochet.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001023141815.A622>