Messages in this thread | | | Date | Wed, 18 Mar 1998 14:46:51 +1000 (EST) | From | David Burrows <> | Subject | Re: syslogd [modularity] |
| |
On Tue, 17 Mar 1998, Kirk Petersen wrote:
> > At some point, Unix-domain sockets were made modular. Double-check your > > configuration, making sure that you enable these. Can anyone explain the > > rationale behind making sockets optional? It is churning up a lot of > > support questions.. > > Sure, I made unix domain sockets optional because a) it was easy > and b) optional is good.
Agreed.. It isn't mandatory to have unix domain sockets.. for example a stripped kernel for a rescue disk doesn't need it.
Here's what prompted me to post in the first place... I noticed tcp/ip cannot be built as a module. I had a scratch of the old head wondering 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 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.
Just my $2E-2 worth.. :)
Dave.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |