kernel modules

[Bill Davidson]

On Thu, 20 Jun 2002 21:36:56 -0500
"David A. Bandel" <david at pananix.com> wrote:

> On Thu, 20 Jun 2002 17:51:39 -0400
> begin  Bill Davidson <harley7 at mnsi.net> spewed forth:
> 
> > I've compiled a kernel and I realize I want to compile 2 more modules.
> > If I run make menuconfig, without make mrproper, will all the
> > selections that I had previouly chosen stay that way? Is that the way I
> > should do it? Then I could run make modules and make modules_install.
> > And if that's the way it's done, I don't think I need to reboot, but do
> > I need to do anything else? depmod maybe?
> 
> All you need to do is:
> make menuconfig (choose the new modules)
> make modules;make modules_install
> 
> modprobe <module>
> 
> no need for a reboot or anything.

Thanks. That's the answer I was hoping for

> Note:  the above _only_ works on modules, and on modules in areas where
> you already have modules (i.e., there's no change to the kernel itself).
> e.g., suppose you chose CONFIG_NETFILTER=y, then made some netfilter
> modules.  You later decided to remake iptables, only wanted to add a few
> new modules using make most-of-pom.  You could then go to the kernel
> tree, and do:
> make oldconfig (select as modules the new netfilter modules)
> make modules;make modules_install
> 
> begin writing rules for the new modules.

Thanks. I'll be saving this one.

> However, if you originally said NO to CONFIG_NETFILTER, but now decided
> you wanted to try some netfilter modules, you'd have to remake the entire
> kernel (make menuconfig;make bzImage;make modules;make modules_install;cp
> System.map /boot/System.map;cp arch/i386/boot/bzImage
> /boot/bzImage;lilo;shutdown -r now)
> Note that, as long as this is just a kernel _remake_, you don't need
> `make mrproper`, `make dep`, `make clean`.  I only use the mrproper
> target the_very_ first time (not after only a patch-up) or if I change
> from uni- to multi- processor.  I only use the dep and clean targets
> first time around after I patch up. 
> 
> The above is based on my experience and may not be best practice, but it
> works (as it has hundreds of times over the years).  I _hate_ waiting for
> compile steps I don't need to run, so I take every known shortcut.
> 
> Crystal?

Very. Thanks. That was excellent.