Date: Tue, 06 May 2003 14:01:25 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: sh@planetquake.com Cc: hackers@freebsd.org Subject: Re: Bridge config in /etc/rc (patch) Message-ID: <20030506.140125.22500726.imp@bsdimp.com> In-Reply-To: <000901c31405$033a4bd0$0300000a@antalus> References: <011901c31390$7aef5730$0300000a@antalus> <20030506.062105.70173875.imp@bsdimp.com> <000901c31405$033a4bd0$0300000a@antalus>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <000901c31405$033a4bd0$0300000a@antalus>
"Sean Hamilton" <sh@planetquake.com> writes:
: M. Warner Losh wrote:
: | I think I like this syntax and have only one comment. This seems to
: | match up with ifconfig's aliases fairly well. However, I think that
: | the model here might be better served by the routes:
: |
: | bridge_names="a b c"
:
: Instead of this, why not just something like 'set' to find a list of
: variables? Then the user can create bridge0, bridgejim, bridge_bill, or
: whatever they like, and to prevent a bridge from being used, they need only
: comment it out.
Just because it is consistant with how routing is done... No other
real compelling reason.
: | I'd stick to spaces only, to match the sysctl. I don't think that it
:
: Well, the sysctl accepts both spaces and commas.
Then never mind...
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030506.140125.22500726.imp>