From owner-freebsd-current@FreeBSD.ORG Thu Jun 16 03:30:22 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 4409216A423 for ; Thu, 16 Jun 2005 03:30:22 +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 AD74143D58 for ; Thu, 16 Jun 2005 03:30:11 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j5G3PnIl031661; Wed, 15 Jun 2005 21:25:49 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Wed, 15 Jun 2005 21:26:59 -0600 (MDT) Message-Id: <20050615.212659.86621150.imp@bsdimp.com> To: dmp@bitfreak.org From: "M. Warner Losh" In-Reply-To: <001501c5720b$aceb84d0$0b2a15ac@SMILEY> References: <20050615061009.GA11914@odin.ac.hmc.edu> <001501c5720b$aceb84d0$0b2a15ac@SMILEY> 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, freebsd-current@freebsd.org, matt@gsicomp.on.ca 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 03:30:22 -0000 In message: <001501c5720b$aceb84d0$0b2a15ac@SMILEY> "Darren Pilgrim" writes: : 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. This can be good. I have ifconfig_fxp1 lines in my rc scripts for when I setup temprary networks as a reminder to what to use. I specifically set network_interfaces to exclude them from being run. : 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. This is really not an issue. If I insert my network card, I want it configured in the manner that it would have been configured on boot. devd and /etc/pccard_ether (poorly named, I know) already takes care of that situation... Warner