Messages in this thread | | | Date | Tue, 17 Mar 1998 21:58:17 -0800 | From | Kirk Petersen <> | Subject | Re: syslogd [modularity] |
| |
> why not. In my eyes its perfectly feasable.. For example, if a tcp/ip > bug is found or whatever, you could simply recompile tcp/ip and reinsert > it into the running kernel. :)
I tried this shortly after doing unix domain sockets. It wasn't too hard to make ipv4 compile as a module. It even could be inserted. But there were *lots* of bugs. Shortly after this, the first code freeze was announced, so I figured it could wait until 2.3.
> I suppose there are those out there who believe modules are evil, and > maybe they're right.. But to me it seems logical to have all features > there if you want them, and only load the ones you need IF you need them > and when you need them.
No arguments here.
For those of you curious about kmod's problems, I've been trying hundreds of different fixes. I think I'm close to a fix, so don't get too anxious to go back to kerneld!
-- Kirk Petersen speakeasy.org/~kirk/
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |