Matthew Martin enlightened us with:
> OK I chose to do the 2.6 Kernel Manualy. What is the diference
> between * built-in and M module

Modules are parts of the kernel that are stored in files that live in
/lib/modules/<kernel version>/. They can be loaded on demand, and thus
prevent your kernel from taking up more memory than you need. It's
also easier to pass them options, etc.

You need some modules compiled into your kernel (*) instead of as an
external module. Think of this: if your harddisk has the XFS
filesystem, but you compiled XFS support as a module, your kernel
wouldn't be able to find the module in the first place to load XFS
support. See the problem? You also need to compile in support for your
IDE chipset, and some other things, for the same reason.

Sybren
--
The problem with the world is stupidity. Not saying there should be a
capital punishment for stupidity, but why don't we just take the
safety labels off of everything and let the problem solve itself?