Date: Tue, 29 Apr 2008 16:59:34 -0500 From: Brooks Davis <brooks@freebsd.org> To: David Naylor <naylor.b.david@gmail.com> Cc: sam@freebsd.org, freebsd-current@freebsd.org Subject: Re: [REGRESSION] Vap and ifconfig on boot Message-ID: <20080429215934.GA88339@lor.one-eyed-alien.net> Resent-Message-ID: <20080430161350.GA78754@lor.one-eyed-alien.net> In-Reply-To: <200804292335.13340.naylor.b.david@gmail.com> References: <200804292335.13340.naylor.b.david@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Tue, Apr 29, 2008 at 11:35:09PM +0200, David Naylor wrote: > Hi, > > Before vap if someone specified ifconfig_iwn0 then if_iwn.ko would be kldload > on boot should the interface not be found, and the driver not already active > (built into the kernel or loaded). However now it appears that with > wlans_iwn0="wlan0" does not result in if_iwn.ko being kldloaded. > > Thought your should know. Apologies if this is a false positive. Unless you were setting the network_interfaces variable manually (a deprecated configuration), I'd be pretty surprised if this were the case. The rc system has not way of knowing what ifconfig_<ifn> variables are set so it wouldn't call ifconfig and trigger an autoload. I'm willing to be proved wrong, but I don't think I am... -- Brooks [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFIF5pFXY6L6fI4GtQRAi3FAKCwFbUk//8JP6a4Zog72AaF6To30QCaAvKi y1IMBcE4sVfhPBdsadetahk= =jKbJ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080429215934.GA88339>