Module paths [Re: CVS commit: src]

[Andrew Doran <ad%netbsd.org@localhost>]

On Sat, May 03, 2008 at 12:05:18PM +1000, matthew green wrote:

>    Log Message:
>    Build and install modules into /kernel/modules. Each module gets a
>    directory for properties, blobs, etc. It's not fixed in stone and
>    can easily be changed if there are issues with the location/layout.
> 
> 
> cool.  i've been waiting for his :-)
> 
> could it be not a new top-level dir?  i've used dirs called
> "/kernel" before (i think that's what freebsd uses for a while
> now, too?) and i'm generally upset when the OS starts using
> more files/subdirs in / on me, and i've been using the previous
> one before.  /lib/modules works for me, but i'm not really
> attached to it.

Do you use /stand? :-)
 
> i think we also need some version number in here.  kernel number
> changes matches when the kernel ABI has changed so, it seems
> a valid choice to make.  it means having a lot more to clean
> up if you use modules but i don't know of any other way that
> is actually safe.

/foo/modules/5.0/cd9660/cd9660.kmod

I'm tempted to say that the minor version shouldn't matter for releases but
it might be hard to stick to that kind of policy.

/foo/modules/4.99.62/cd9660/cd9660.kmod

For -current the entire version would need to be significant. One problem I
see is getting those into the set lists, but that's a SMOP a think.

Sound reasonable?

Thanks,
Andrew