Re: aklug Digest V4 #256

Make oldconfig is useful when you apply an upgrade patch to a kernel
source (upgrading from 2.5.12 to 2.6.13, for instance). It reads your
existing .config, and asks you for values for any NEW parameters
introduced in the new version.

There are two thoughts on a monolithic kernel (one with all the modules
in it). It is more secure, since one usually does not enable module
loading in such a beast. Good for a server, etc. On the other hand, what
you see is what you get, and adding new hardware means a new kernel. It
is sometimes more difficult to configure, since you cannot pass
parameters in /etc/modprobe.conf. It will be bigger, not really a
consideration anymore, since none of em will fit on a floppy!

If I have a server with a fixed configuration, I will usually take the
time to build a kernel without loadable modules. On a workstation or
laptop, I am usually happy to run a stock kernel.

Jim

>-------------------------------
>
>From: "=?iso-8859-1?Q?dhull?=" <dhull@digitaloverload.net>
>Subject: Still learning! (kernel help)
>Date: Sat, 31 Dec 2005 11:55:32 -1000
>
>Learned something new at the meetig last night. I was trying to compile a kernel.
>
>Here's how I do it.
>1. make oldconfig
>2. make xconfig ( select modules etc... )
>3. make
>4. make modules
>5. make install
>6. make modules_install
>
>I've never had a problem in Fedora or CentOS. However, this new guy ( sorry, can't remember his name) tells me that "make oldconfig" just brings in a preset .config. I allways thought there was some magic going on here. That "make oldconfig" would grab some info from the running kernel.
>
>There is no magic!
>
>If there is no magic how do I know what modules etc... to place in the kernel?
>
>This new guy suggested looking at "lsmod" and making sure all the modules listed are in the kernel. If anyone has any other suggestions send them my way.
>
>There is also "mkinitrd" to think about. Do I need to run this after compiling a kernel? I don't but maybe I should.
>
>If all else fails I could make everything a module.
>
>------------------------------
>
>End of aklug Digest V4 #256
>***************************
>---------
>To unsubscribe, send email to <aklug-request@aklug.org>
>with 'unsubscribe' in the message body.
>
>
>

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Sat Dec 31 13:47:19 2005