Date: Wed, 15 Jun 2005 23:02:28 -0700 From: "Darren Pilgrim" <dmp@bitfreak.org> To: "'M. Warner Losh'" <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: RE: HEADSUP: OpenBSD dhclient incoming Message-ID: <000e01c57238$fa215270$0b2a15ac@SMILEY> In-Reply-To: <20050615.212659.86621150.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
From: M. Warner Losh [mailto:imp@bsdimp.com] > In message: <001501c5720b$aceb84d0$0b2a15ac@SMILEY> > "Darren Pilgrim" <dmp@bitfreak.org> writes: > : 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... *takes crash course in network.subr, pccard_ether and netif* Yeah, ok. Shame on me for not keeping up on the reading. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000e01c57238$fa215270$0b2a15ac>