Date: Thu, 16 Jun 2005 14:04:04 -0700 From: David Wolfskill <david@catwhisker.org> To: current@freebsd.org Subject: Re: HEADSUP: OpenBSD dhclient incoming Message-ID: <20050616210404.GM33118@bunrab.catwhisker.org> In-Reply-To: <20050616205033.GF13900@odin.ac.hmc.edu> References: <20050615061009.GA11914@odin.ac.hmc.edu> <001501c5720b$aceb84d0$0b2a15ac@SMILEY> <20050616164747.GB21733@odin.ac.hmc.edu> <20050616.142507.85367515.imp@bsdimp.com> <20050616205033.GF13900@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 16, 2005 at 01:50:33PM -0700, Brooks Davis wrote:
> ...
> Agreed. There's actually some demand for a default for wired interfaces
> as well. If nothing else I know the EmuLab people would like one
> so they didn't have to use their own scripts to configure all the
> interfaces. I've thought about it a bit. I'm leaning towards a
> default_ifconfig variable plus a new magic ifconfig_<if> option NONE to
> cause the default option not to be used.
>From the perspective that NIC-specific variables are of the form
"ifconfig_${NIC}" (e.g., ifconfig_lo0; ifconfig_ed0; ifconfig_xl0),
might it make at least as much sense to call it "ifconfig_default" (or
something similar)?
Peace,
david
--
David H. Wolfskill david@catwhisker.org
Any given sequence of letters is a misspelling of a great many English words.
See http://www.catwhisker.org/~david/publickey.gpg for public key.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050616210404.GM33118>