From owner-freebsd-current@FreeBSD.ORG Thu Jun 16 20:26:30 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 5275416A41C for ; Thu, 16 Jun 2005 20:26:30 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-66.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EC5343D1F for ; Thu, 16 Jun 2005 20:26:29 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j5GKP78K044502; Thu, 16 Jun 2005 14:25:07 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 16 Jun 2005 14:25:07 -0600 (MDT) Message-Id: <20050616.142507.85367515.imp@bsdimp.com> To: brooks@one-eyed-alien.net From: Warner Losh In-Reply-To: <20050616164747.GB21733@odin.ac.hmc.edu> References: <20050615061009.GA11914@odin.ac.hmc.edu> <001501c5720b$aceb84d0$0b2a15ac@SMILEY> <20050616164747.GB21733@odin.ac.hmc.edu> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: vova@fbsd.ru, dmp@bitfreak.org, matt@gsicomp.on.ca, freebsd-current@freebsd.org 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 20:26:30 -0000 From: Brooks Davis Subject: Re: HEADSUP: OpenBSD dhclient incoming Date: Thu, 16 Jun 2005 09:47:47 -0700 > On Wed, Jun 15, 2005 at 05:38:10PM -0700, Darren Pilgrim wrote: > > From: Brooks Davis > > > There are two issues here. First, if we're going to keep > > > network_interfaces around, /etc/rc.d/dhclient should honor > > > it and not start dhclient on interfaces not in either > > > network_interfaces or removable interfaces. > > > > I think network_interfaces should be gotten rid of entirely for two > > reasons: > > > > 1: It creates a synchronization issue between it and the ifconfig_* > > lines and duplicates functionality. IIRC, rc.conf being out of sync in > > this way has tripped up users in the past. > > > > 2: There are real configurations in which some interfaces are not > > available when netif is run at boot. One example is the many newer > > mini-PCI wireless NICs that require a firmware upload. Devd is the > > accepted tool for performing such tasks, but rcordering puts devd after > > NETWORKING. The actions taken by devd must therefore include steps > > taken by netif. Calling the rc.d scripts directly from devd avoids > > local scripts that duplicate rc.d functionality. A similar situation > > occurs for removable interfaces. > > I'm seriously considering removing the following variables: > > network_interfaces > removable_interfaces > pccard_ether pccard_ifconfig you mean? > If I do that I'll probably add a pair of new start/stop targets to > /etc/rc.d/netif to replicate the remaining functions of pccard_ether > and nuke /etc/pccard_ether. I invented pccard_ifconfig to be done whenever a new device appeared on the system. I test about 20 different drivers these days, and having that many different ifconfig_foo= lines was burdonsome. I'd love to see the fallback functionality that this provided retained somehow. Warner