HEADSUP: OpenBSD dhclient incoming
Warner Losh
imp at bsdimp.com
Thu Jun 16 20:26:30 GMT 2005
From: Brooks Davis <brooks at one-eyed-alien.net>
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
More information about the freebsd-current
mailing list