Date: Thu, 23 Mar 2006 13:20:34 -0800 From: Luigi Rizzo <rizzo@icir.org> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: Paul Schmehl <pauls@utdallas.edu>, freebsd-net@freebsd.org Subject: Re: lo0 not starting on boot Message-ID: <20060323132034.A73245@xorpc.icir.org> In-Reply-To: <20060323211838.GA1787@odin.ac.hmc.edu>; from brooks@one-eyed-alien.net on Thu, Mar 23, 2006 at 01:18:38PM -0800 References: <FAE07A50EBD6BB365C5FDD88@utd59514.utdallas.edu> <20060323195534.GB25560@odin.ac.hmc.edu> <3AC2CAE7FC658D8EBA589F4F@utd59514.utdallas.edu> <20060323124953.A72829@xorpc.icir.org> <20060323211838.GA1787@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 23, 2006 at 01:18:38PM -0800, Brooks Davis wrote: ... > It used to be hard coded. Today we force it to the front of the list > in the network_interfaces=auto case, but don't do anything special with > it in the other case. We could change to code to always make it the > first item in all cases if it exists at all, but I'm not particularly > thrilled by that idea. In general I don't recommend the use of > network_interfaces at all and I'm tempted to nuke it at some point in > the future. It's not really necessicary any more becuse you can use the > NOAUTO keyword in your ifconfig_<ifn> lines if you want them around, but > don't want them used at boot. the NOAUTO makes sense indeed. basically it is a documentation issue - print a warning when you parse rc.conf and find network_interfaces set, and suggest NOAUTO instead. cheers luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060323132034.A73245>