From owner-freebsd-current@FreeBSD.ORG Thu Jun 16 23:32:26 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5807616A41C for ; Thu, 16 Jun 2005 23:32:26 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 287DB43D5D for ; Thu, 16 Jun 2005 23:32:26 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from localhost.localdomain (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id F361F7C for ; Thu, 16 Jun 2005 19:32:24 -0400 (EDT) From: "Brandon S. Allbery KF8NH" To: freebsd-current@freebsd.org In-Reply-To: <20050616220515.GC20431@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> <20050616210404.GM33118@bunrab.catwhisker.org> <20050616220515.GC20431@odin.ac.hmc.edu> Content-Type: text/plain Date: Thu, 16 Jun 2005 19:32:57 -0400 Message-Id: <1118964777.21992.0.camel@rushlight.kf8nh.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Subject: Re: HEADSUP: OpenBSD dhclient incoming X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 23:32:26 -0000 On Thu, 2005-06-16 at 15:05 -0700, Brooks Davis wrote: > On Thu, Jun 16, 2005 at 02:04:04PM -0700, David Wolfskill wrote: > > >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. ifconfig_="...defaults..." -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH