Because people can download and install seperate protocol modules.
DECnet for example is likely to be done this way in 2.2.
> main(){ for(;;) socket(25,0,0); }
> makes syslog work pretty hard....
If you don't have your conf.modules configured for it and modprobe set up
nicely. The syslog problem is a modprobe problem IMHO not a kernel problem
Alan
-
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/