Date: Wed, 15 Jun 2005 17:38:10 -0700 From: "Darren Pilgrim" <dmp@bitfreak.org> To: "'Brooks Davis'" <brooks@one-eyed-alien.net>, "'Vladimir Grebenschikov'" <vova@fbsd.ru> Cc: freebsd-current@freebsd.org, 'Matthew Emmerton' <matt@gsicomp.on.ca> Subject: RE: HEADSUP: OpenBSD dhclient incoming Message-ID: <001501c5720b$aceb84d0$0b2a15ac@SMILEY> In-Reply-To: <20050615061009.GA11914@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001501c5720b$aceb84d0$0b2a15ac>