Date: Thu, 16 Jun 2005 15:05:15 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: David Wolfskill <david@bunrab.catwhisker.org>, current@freebsd.org Subject: Re: HEADSUP: OpenBSD dhclient incoming Message-ID: <20050616220515.GC20431@odin.ac.hmc.edu> In-Reply-To: <20050616210404.GM33118@bunrab.catwhisker.org> 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> <20050616210404.GM33118@bunrab.catwhisker.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--qtZFehHsKgwS5rPz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jun 16, 2005 at 02:04:04PM -0700, David Wolfskill wrote:
> On Thu, Jun 16, 2005 at 01:50:33PM -0700, Brooks Davis wrote:
> > ...
> =20
> > 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.
>=20
> >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)?
I'm divided on that one. The problem is that users may want to name an
interface "default" and this would break that. I like the symetry and
the sort order of ifconfig_default, but I'm concerned about exceptions
to the namespace as well. I'm somewhat tempted by ifconfig_DEFAULT.
-- Brooks
--=20
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
--qtZFehHsKgwS5rPz
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFCsfeaXY6L6fI4GtQRArExAJ9TRVJg/rfysRTlH1VPACiiRkd9mgCggDHg
GksEJYB1ByxC7T9WmNPBaWo=
=twXL
-----END PGP SIGNATURE-----
--qtZFehHsKgwS5rPz--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050616220515.GC20431>