Date: Wed, 07 May 2003 00:38:37 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Doug Barton <DougB@FreeBSD.org> Cc: hackers@freebsd.org Subject: Re: Bridge config in /etc/rc (patch) Message-ID: <3EB8B7FD.AFBE8EC4@mindspring.com> References: <011901c31390$7aef5730$0300000a@antalus> <20030505225826.G666@znfgre.qbhto.arg> <20030506002824.G666@znfgre.qbhto.arg> <20030506214845.X5620@znfgre.qbhto.arg>
next in thread | previous in thread | raw e-mail | index | archive | help
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? -- Terry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EB8B7FD.AFBE8EC4>