On Tue, 04 Feb 2003 17:20, Daniel Pittman wrote: > As a rule I use kernels without module support built in for my kernels. > It's not that I care that deeply about the issue -- it's just that > having everything I use built in means that I don't have to administer > module configuration or anything like that.
Watch out. Some kernel modules (eg, most PCMCIA drivers) don't even work when hard compiled in. This might just be the momma's boy modules who rely heavily on userspace programs. But it also makes it more difficult to set driver options; you need to do it on the kernel command line. What's better - having to configure a modules.conf, or having to deal with the side effects of dozens of buggy Linux kernel drivers misinitialising on bootup? The answer, of course, depends on the variety of systems you have - and hence the number of drivers you need to compile in. -- Sam Vilain, [EMAIL PROTECTED] Real Programmers don't write in LISP. Only faggot programs contain more parenthesis than actual code.
