Date: Wed, 7 May 2003 00:50:31 -0700 (PDT) From: Doug Barton <DougB@FreeBSD.org> To: Terry Lambert <tlambert2@mindspring.com> Cc: hackers@freebsd.org Subject: Re: Bridge config in /etc/rc (patch) Message-ID: <20030507004857.I5620@znfgre.qbhto.arg> In-Reply-To: <3EB8B7FD.AFBE8EC4@mindspring.com> References: <011901c31390$7aef5730$0300000a@antalus> <20030505225826.G666@znfgre.qbhto.arg> <1052215193.41902.130.camel@watchtower.office.parksmediagroup.com> <3EB8B7FD.AFBE8EC4@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 7 May 2003, Terry Lambert wrote:
> Doug Barton wrote:
> > On Tue, 6 May 2003, Benjamin F. Burke wrote:
> > Experienced users can fend for themselves regarding edge cases like bridge
> > configurations. That's what rc.local is for. I'm worried about not
> > overwhelming new users.
>
> As an idea here, is it possible to have a large list of rc files
> in a particular location in directories that would automatically
> be run in their own directory, and automatically get their defaults
> sourced in, and have their own rc.conf's that get sourced in, etc.?
>
> If there were a subdirectory traversal for (currently non-existant)
> subdirectories in /usr/local somewhere, then each one of these
> "fend for yourself" cases could be implemented as ports.
>
> /usr/ports/rc/* anyone?
/usr/local/etc/rc.d has already been suggested, and it's a direction I'd
like to see us move in. Because the ordering of dependencies is
non-trivial, I'm not sure having more than one such directory is a
realistic target atm, but at least having one is definitely doable.
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030507004857.I5620>