From owner-freebsd-current@FreeBSD.ORG Thu Jun 16 00:38:14 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 16D5B16A41C for ; Thu, 16 Jun 2005 00:38:13 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA4B443D1D for ; Thu, 16 Jun 2005 00:38:13 +0000 (GMT) (envelope-from dmp@bitfreak.org) Received: from SMILEY (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 9160E19F3B; Wed, 15 Jun 2005 17:39:41 -0700 (PDT) From: "Darren Pilgrim" To: "'Brooks Davis'" , "'Vladimir Grebenschikov'" Date: Wed, 15 Jun 2005 17:38:10 -0700 Message-ID: <001501c5720b$aceb84d0$0b2a15ac@SMILEY> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 In-Reply-To: <20050615061009.GA11914@odin.ac.hmc.edu> Importance: Normal Cc: freebsd-current@freebsd.org, 'Matthew Emmerton' 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 00:38:14 -0000 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.