Weblog entry #9 for Utumno

kernel-package
Posted by Utumno on Wed 24 May 2006 at 08:48
Tags: none.
Maybe I am missing something, but after an honest shot at reading kernel-package's man page I still have no idea about what seems to be an obvious piece of functionality in it: adding a single module to an already compiled kernel.

Suppose I have an already compiled kernel , and suddenly I realize I need one more option (let's say, 'nat') in my ip_tables module. Currently, I know of no other way to do it than

1) make {menu,g,x}config and mark the option
2) re-compile the whole new kernel and install.

It should be possible to mark the new option, and (if said ip_tables is really compiled as a module) be able to only re-compile this module, obtain a small .deb which would just install a new iptable_nat.ko to /lib/modules/`uname -r`/kernel/net/ipv4/netfilter/ .

This not only would save us 20 minutes of compilation, but would also ease the pain with proprietary drivers ( say, NVidia ) which have to be recompiled each time one installs a new kernel.

So, the question: is the above possible with kernel-package or not?

 

Comments on this Entry

Posted by simonw (84.45.xx.xx) on Wed 24 May 2006 at 18:26
[ Send Message | View Weblogs ]
Have you looked at the module-assistant package? Probably not as flexible as you want, but might do the job.

It isn't that good for random source code modules, but a lot of common source packages are already in Debian.

Most common iptables modules are already in the stock kernel, certainly I've done complex firewall installs without building a bespoke kernel.

As regards proprietary modules, don't go there.

Steve will no doubt be along shortly to fill the gaps in.

[ Parent | Reply to this comment ]

Posted by Utumno (211.22.xx.xx) on Fri 26 May 2006 at 20:37
[ Send Message | View Utumno's Scratchpad | View Weblogs ]
Thanks, m-a looks good :)

[ Parent | Reply to this comment ]

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search