> > [...]
> > > The 2.1 socket code is modular enough that CONFIG_<type>=m is equivalent
> > > to CONFIG_<type>=n. I don't think that it would be worth the additional
> > > code and complexeties just to make it distingush between these two states
> > > for a protocol. It would be much better to just fix net-tools to check
> > > for the appropiate /proc/net files first before opening these sockets.
> > Just too bad they won't appear until after you modprobe(8) for them ;-)
> Good point. Then they should only open the sockets if the user requested
> information from them.
I.e., when /etc/rc.d/* ifconfig(8) or whatever is appropiate for the
module. Done as requested ;-)
-- Dr. Horst H. von Brand mailto:vonbrand@inf.utfsm.cl Departamento de Informatica Fono: +56 32 654431 Universidad Tecnica Federico Santa Maria +56 32 654239 Casilla 110-V, Valparaiso, Chile Fax: +56 32 797513- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/