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

[Björn Augustsson <august chalmers se>]

On Thu, Mar 16, 2006 at 12:02:51PM -0500, Jason Baron wrote:
> 
> as you noticed, i avoided that part of your question :) 

Heh.

> We've really left 
> this procedure up to 3rd party vendors, to decide where, and how they want 
> to manage their own modules. To me, this is almost to a fault....i think 
> the orginal idea behind the /lib/modules/kabi* directory was in fact that 
> modules should be stuck in there so that they could be treated in a 
> generic way. The kernel could export its own 'kabi' version and then all 
> the tools, 'depmod', 'mkinitrd', etc. could know about that path. However, 
> as you pointed out that work was really never fleshed out. ie the tools 
> don't know about the path. I'd be interested in making this happen, if 
> people think its a good idea...

Well, it would be useful to me, if it could be made to actually work.
(Mr van de Ven's mail seem to indicate he thinks otherwise.)

I realize the potential issue that having a kabi can be seen to be
helping proprietary modules.  (Which it reasonably would, as well as
normal, GPLed third-party modules.)

OTOH, if it doesn't work, I think the kabi dirs should be removed,
because right now they only confuse folks (read: me).

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