On Wed, Jun 03, 2009 at 07:57:37AM -0400, John Baldwin wrote: > On Wednesday 03 June 2009 5:31:10 am Dag-Erling Sm??rgrav wrote: > > John Baldwin <j...@freebsd.org> writes: > > > [...] Given that, there really isn't a good reason to customize > > > network_interfaces anymore. > > > > Listing e.g. bge0 in network_interfaces will (indirectly) cause if_bge > > to be loaded if it wasn't already. If network_interfaces is left blank, > > only interfaces that already have a driver attached to them will be > > configured.
Ugh, I thought I'd killed that off. I'm solidly in the camp of people who think the autoloading is a mistake. If you're going to hardcode a list of module you want to load, /boot/loader.conf is the place, not this indirect hack that bites people on the ass because it works for real interfaces, but not all sorts of other types due to the impossibilty of generalizing support. For extra fun, making a typo on your ifconfig command line can lead to loading a random module. > That is a good argument. Someone noted it on -stable as well as something > they use. Also, I wonder if ipv6_network_interfaces should actually default > to whatever the value of 'network_interfaces' is so that if someone does use > a customized 'network_interfaces' line it affects IPv6 configuration as well. > > (Maybe have it default to an empty value and have an empty value get replaced > with 'network_interfaces'?). That's probably a good solution for ipv6_network_interfaces. -- Brooks
pgpi2Z7rgpP1J.pgp
Description: PGP signature
