Re: HEADSUP: OpenBSD dhclient incoming

In message: <001501c5720b$aceb84d0$0b2a15ac_at_SMILEY>
            "Darren Pilgrim" <dmp_at_bitfreak.org> 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