Re: Still learning! (kernel help)

On Sat, Dec 31, 2005 at 11:55:32AM -1000, dhull <dhull@digitaloverload.net> wrote:
> If there is no magic how do I know what modules etc...
> to place in the kernel?

This is where initimate knowledge of your system comes in handy. You
need to have code in your kernel for every device and every piece of
functionality you want to use.

You're not completely on your own, though. I use the text-based
'make config' rather than 'make xconfig', and for most questions
it asks you, there's help available that explains what it is and
helps you decide if you need it. Play around with 'make xconfig'
and see if you can find the help for each option.

Whether you compile something into the kernel itself or leave it
as a module is usually not that important. As Jim mentioned,
modules are easier to configure, so for example, if you have a
temperamental sound card, and need to play around with the I/O
address, it's easier to unload and reload the module until you get
it right, rather than reboot each time. On the other hand, as
Greg alluded to, you need to be able to boot with what's in the
kernel itself. So if your system exists on Reiser filesystems
on an IDE disk, make darn sure you have reiser and ide drivers
compiled directly into the kernel, not left as modules. Other
than that, in-kernel vs. module is a personal choice.

There's plenty of documentation out there on compiling a kernel.
If you haven't already, be sure to read /usr/src/linux/README.
And here are a couple relevant HOWTOs:
http://www.digitalhermit.com/linux/Kernel-Build-HOWTO.html
http://tldp.org/HOWTO/Module-HOWTO/index.html

Good luck, and have fun.

--
Bryan Medsker
bryanm@acsalaska.net
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.