Re: /lib/modules/kabi-4.0-0*

[Björn Augustsson <august chalmers se>]

On Thu, Mar 16, 2006 at 11:05:27AM -0500, Jason Baron wrote:
> On Thu, 16 Mar 2006, Björn Augustsson wrote:
> 
> > I haven't found any docs on this, and as far as I can deduce from a
> > running system, neither module-init-tools not mkinitrd knows anything
> > about the kabi directories.
> > 
> > Anyone?
> 
> 3rd party modules that are compiled against any of the kernel-devel pkgs 
> should continue to work fine against any later kernels without having to 
> re-compile. If this is not the case for, we want to know about it. We have 
> a number of practices in place to make sure that this works.

I'm sorry, I don't get it.

But normally a module will end up somewhere in /lib/modules/`uname -r`
and the next kernel will not look there. So what am I supposed to do? 

* Move it to the /lib/modules/kabi-xyz dir?
* Move it to the /lib/modules/<new-kernel> dir?

or what?

Is the module supposed to know about this, and install itself to 
the kabi dir? What if it doesn't?

/August, man of many questions.
-- 
Björn Augustsson      Sysadmin     IT Systems & Services
Chalmers tekniska högskola     Chalmers University of Technology
         "Damn spooky analog crap." -- John Carmack.