> [Melvin needs a hand-tailored kernel for a crappy webserver. Source is
> _long_ gone]
Melvin is a html-only geek, but not stupid. He knows where he can get the
sources for the distribution's kernel, and he knows very well that it is
advisable to stick to the distribution's software. He understands enough of
the process so he can tailor a kernel for _webserving_, not optimal use of
all hardware on Ye Olde Coffepot. He leaves out sound, serial support, and
acceleration support for the video card (What for in a webserver?),
configures floppy and CD as modules (to save the odd byte), just ext3 as
builtin filesystem (no need for all the others, iso9660 is module for some
savings). He includes iptables support, but no connection tracking or NAT
modules. All things an autoconfigurator wouldn't dream of doing on its own.
[Again, building a tailored kernel for a specific application on a crappy
machine is no place for automatism; for everything else an Aunt Tillie
might need a "get nearest size" is enough]
> "Crap." Melvin thinks. "I don't remember what kind of network card I
> compiled in. Am I going to have to open this puppy up just to eyeball
> the hardware?" Doing that would take time Melvin was planning to spend
> chatting up a girl geek he's noticed over at the computer lab.
If Melvin did compile the kernel in the first place, he is smart enough to
keep .configure around. If not, he doesn't deserve getting laid.
For terminally stupid Melvins, keep .configure around somewhere.
-- Horst von Brand http://counter.li.org # 22616 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/