Re: Path to kmods

[Christoph Egger <Christoph_Egger%gmx.de@localhost>]

Quentin Garnier wrote:
> On Wed, Nov 12, 2008 at 05:11:58PM +0100, Christoph Egger wrote:
>> Michael wrote:
>>> Hello,
>>>
>>> On Nov 12, 2008, at 10:52 AM, Hubert Feyrer wrote:
>>>
>>>> On Wed, 12 Nov 2008, Andrew Doran wrote:
>>>>>> Regarding the PR/38724, can we change the path to "/kmods/" or
>>>>>> something
>>>>>> like that? Would be good to have meaningful name before it gets used
>>>>>> widely.
>>>>> /kernel?
>>>> Prior art:
>>>>
>>>> Solaris:             /kernel,
>>>> Linux (OpenSuSE 10.2 here):     /lib/modules/$(uname -r)
>>>>
>>>> I don't know about other systems, but checking on FreeBSD and Mac OS X
>>>> may be worthwhile.
>>> /System/Library/Extensions on OSX - I doubt we want that ;)
>>>
>>>> My gut feeling tells me that to support easy switching/testing of
>>>> kernels, the kernel version should be in the path.
>>> I agree. Since we already mimic Solaris in other ways we may as well do
>>> it here too.
>> the directory structure should at least allow different kernel
>> version/types.
>>
>> I sort of dual-boot NetBSD/amd64 and NetBSD/Xen (Dom0) with the same
>> userland. Sometimes it happens, that the kernels have a different
>> uname -r.
> 
> Why do the kernel modules need to be different?  That doesn't appear
> necessary to me, but maybe I'm missing something.

For development/testing purpose.
I have two boot menu entries for native and two for xen.
Two always boot my test machine (either native or xen) independent
how much I messed up the development/testing kernels.

I want to be sure, that when I boot a stable kernel that it loads
the stable modules - a directory, where I don't mess around
unlike to the testing stuff.

Christoph