* What does CONFIG_NETDEVICES *really* mean ?
@ 2001-12-13 23:53 Peter Cleve
0 siblings, 0 replies; only message in thread
From: Peter Cleve @ 2001-12-13 23:53 UTC (permalink / raw)
To: linux-kernel
Hi!
CONFIG_NETDEVICES is referenced only at 2 files in the kernel source:
- net/core/sock.c
- drivers/isdn/isdn_common.c
In net/core/sock.c it's used as an #ifdef around the SO_BINDTODEVICE code
in sock_setsockopt().
This is the interesting part from net/core/sock.c :
[ ... ]
case SO_SNDTIMEO:
ret = sock_set_timeout(&sk->sndtimeo, optval, optlen);
break;
#ifdef CONFIG_NETDEVICES
case SO_BINDTODEVICE:
{
char devname[IFNAMSIZ];
[ ... ]
IMHO it's completly legal to bind a socket to the loopback interface if you
have an machine with CONFIG_INET=y and unset CONFIG_NETDEVICES. I'm not a
kernel hacker and think the surrounding #ifdef should be removed.
In drivers/isdn/isdn_common.c it is used as an #ifdef about some cmd's
in isdn_ioctl(). Some cmd's which are surrounded by CONFIG_NETDEVICES are:
case IIOCNETGPN: /* Get peer phone number of a connected isdn network interface */
case IIOCNETAIF: /* Add a network-interface */
case IIOCNETASL: /* Add a slave to a network-interface */
..... many follows .......
Consider a kernel with no additional Network interfase except isdn interfaces,
these ioctl's cannot work, but IMHO these are needed to set up the isdn interfaces.
IMHO CONFIG_INET fit's better.
Maybe somebody with more knowledge about the kernel can comment about these topics.
Greetings
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2001-12-13 23:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-13 23:53 What does CONFIG_NETDEVICES *really* mean ? Peter Cleve
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).