Re: where to install additional kernel modules?

[Tollef Fog Heen]

* Christoph Hellwig 

| > No need to Cc me, BTW.
| 
| Then setup your headers properly..

What's wrong with his headers?  The default on Debian mailing lists is
to not Cc posters.  Please read the mailing list docs on lists.d.o if
you haven't already.

-- 
Tollef Fog Heen,''`.
UNIX is user friendly, it's just picky about who its friends are  : :' :
  `. `' 
`-  

Re: where to install additional kernel modules?

[Manoj Srivastava]

On Mon, 25 Aug 2003 21:51:57 +0200, martin f krafft <[EMAIL PROTECTED]> said: 

> also sprach Manoj Srivastava <[EMAIL PROTECTED]> [2003.08.25.1652
> +0200]:
>> If there is a single sane approach,

> Well, what's the single sane approach then? So far I've heard four,
> and they are all possible.

A) I said "if".

 B)
> also sprach David Schleef <[EMAIL PROTECTED]> [2003.08.25.0330 +0200]:
>> In reality, it doesn't matter what directory you put modules in,
>> since they all share the same namespace.  You can't have two module
>> files called module_x.o and expect it to work.  Users, however,
>> appreciate the separation.

So /lib/modules/$kvers/$package/ is as good as anything we
 have seen. It is not as it any single machine is likely to have
 hundreds of third party modules to so clutter up /lib/modules/$kvers/
 that finer grained subdirs would be required.

manoj
-- 
The sun never sets on those who ride into it. RKO
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: where to install additional kernel modules?

[martin f krafft]

also sprach Manoj Srivastava <[EMAIL PROTECTED]> [2003.08.25.1652 +0200]:
>   If there is a single sane approach,

Well, what's the single sane approach then? So far I've heard four,
and they are all possible.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpjjrbjHVg4r.pgp
Description: PGP signature

Re: where to install additional kernel modules?

[Manoj Srivastava]

On Mon, 25 Aug 2003 10:30:18 +0200, martin f krafft
<[EMAIL PROTECTED]> said:

> also sprach David Schleef <[EMAIL PROTECTED]> [2003.08.25.0330 +0200]:
>> In reality, it doesn't matter what directory you put modules in,
>> since they all share the same namespace.  You can't have two module
>> files called module_x.o and expect it to work.  Users, however,
>> appreciate the separation.

> I am aware of that, and I favour the approach taken by comedi.
> However, I simply wanted to know if this is guided by policy or just
> sane decision.

> Should there be a policy entry about it?

If there is a single sane approach, policy should not enter
 into it. Policy is not here to tell people not to create bugs -- we
 should know that all by our own selves.

manoj
-- 
The world wants to be deceived. Sebastian Brant
Manoj Srivastava   <[EMAIL PROTECTED]>  
1024R/C7261095 print CB D9 F4 12 68 07 E4 05  CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Re: where to install additional kernel modules?

[martin f krafft]

also sprach David Schleef <[EMAIL PROTECTED]> [2003.08.25.0330 +0200]:
> In reality, it doesn't matter what directory you put modules in,
> since they all share the same namespace.  You can't have two
> module files called module_x.o and expect it to work.  Users,
> however, appreciate the separation.

I am aware of that, and I favour the approach taken by comedi.
However, I simply wanted to know if this is guided by policy or just
sane decision.

Should there be a policy entry about it?

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgp6e2SNoCxWp.pgp
Description: PGP signature

Re: where to install additional kernel modules?

[David Schleef]

On Sun, Aug 24, 2003 at 06:19:16PM +0200, martin f krafft wrote:
> also sprach Christoph Hellwig <[EMAIL PROTECTED]> [2003.08.24.1806 +0200]:
> > the right place is /lib/modules/${kver}/${package}
> 
> says who?

It's always been this way.  However, before 2.4, modutils had a set
list of directories that it looked at in /lib/moduiles/${kvers},
which included pcmcia, mtd, and rtai, all of which were for non-kernel
source module packages.  Other packages (including Comedi) put their
modules in misc/, rather than bother asking for another directory.  I
eventually asked David Hinds to add comedi to the list of search
directories, and mentioned something about searching all directories.
The next release searched all directories.

In reality, it doesn't matter what directory you put modules in,
since they all share the same namespace.  You can't have two module
files called module_x.o and expect it to work.  Users, however,
appreciate the separation.



dave...

Re: where to install additional kernel modules?

[martin f krafft]

also sprach Christoph Hellwig <[EMAIL PROTECTED]> [2003.08.24.1806 +0200]:
> the right place is /lib/modules/${kver}/${package}

says who?

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpTkg3v8wwFy.pgp
Description: PGP signature

Re: where to install additional kernel modules?

[Eduard Bloch]

Moin Christoph!
Christoph Hellwig schrieb am Sunday, den 24. August 2003:

> > > Where then should comedi install itself? comedi drivers are for data
> > > acquisition cards.
> > 
> > /lib/modules/VERSION/misc?
> 
> no.  that's wrong for 2.4+ kernels.

Any evidence? AFAICS modutils don't have problems with it.

MfG,
Eduard.
-- 
Wer ist hier idle?
-- Kester Habermann

Re: where to install additional kernel modules?

[Aaron M. Ucko]

Christoph Hellwig <[EMAIL PROTECTED]> writes:

> no.  that's wrong for 2.4+ kernels.

Interesting, as it seems to be the status quo; I have a bunch of
modules in /lib/modules/2.4.21/misc (from four different modules
packages produced via make-kpkg), which incidentally all seem to load
fine.

No need to Cc me, BTW.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info.

Re: where to install additional kernel modules?

[Christoph Hellwig]

On Sun, Aug 24, 2003 at 12:13:03PM -0400, Aaron M. Ucko wrote:
> Christoph Hellwig <[EMAIL PROTECTED]> writes:
> 
> > no.  that's wrong for 2.4+ kernels.
> 
> Interesting, as it seems to be the status quo; I have a bunch of
> modules in /lib/modules/2.4.21/misc (from four different modules
> packages produced via make-kpkg), which incidentally all seem to load
> fine.

They will of course still load fine, but one of the reasons for
the module directory layout change is that each package gets its
own directory under /lib/modules/${kver}/


> No need to Cc me, BTW.

Then setup your headers properly..

Re: where to install additional kernel modules?

[Christoph Hellwig]

On Sun, Aug 24, 2003 at 12:03:23PM -0400, Aaron M. Ucko wrote:
> martin f krafft <[EMAIL PROTECTED]> writes:
> 
> > Where then should comedi install itself? comedi drivers are for data
> > acquisition cards.
> 
> /lib/modules/VERSION/misc?

no.  that's wrong for 2.4+ kernels.

Re: where to install additional kernel modules?

[Christoph Hellwig]

On Sun, Aug 24, 2003 at 01:00:47PM +0200, martin f krafft wrote:
> i see pcmcia-source and comedi-source installing the modules into
> /lib/modules/`uname -r`/pcmcia and /lib/modules/`uname -r`/comedi.
> my bcm4400-source and bcm5700-source packages install into
> /lib/modules/`uname -r`/kernel/drivers/net/bcm.
> 
> Thinking about it, I argue that it would be better to install them
> into /lib/modules/`uname -r`/bcm since
> /lib/modules/`uname -r`/kernel is the hierarchy used by the
> kernel-image and should not be touched by additional modules that
> are not part of the kernel image.
> 
> is there a policy item that covers this? what do people think?

the right place is /lib/modules/${kver}/${package}

Re: where to install additional kernel modules?

[Aaron M. Ucko]

martin f krafft <[EMAIL PROTECTED]> writes:

> Where then should comedi install itself? comedi drivers are for data
> acquisition cards.

/lib/modules/VERSION/misc?

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info.

Re: where to install additional kernel modules?

[martin f krafft]

also sprach Eduard Bloch <[EMAIL PROTECTED]> [2003.08.24.1353 +0200]:
> IMHO the right location is /lib/modules/`uname -r`/net.

So what about Bug#189297?

Where then should comedi install itself? comedi drivers are for data
acquisition cards.

-- 
Please do not CC me when replying to lists; I read them!
 
 .''`. martin f. krafft <[EMAIL PROTECTED]>
: :'  :proud Debian developer, admin, and user
`. `'`
  `-  Debian - when you have better things to do than fixing a system
 
Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver!


pgpa3oe1i0ZCW.pgp
Description: PGP signature

Re: where to install additional kernel modules?

[Eduard Bloch]

#include 
* martin f krafft [Sun, Aug 24 2003, 01:00:47PM]:

> Thinking about it, I argue that it would be better to install them
> into /lib/modules/`uname -r`/bcm since
> /lib/modules/`uname -r`/kernel is the hierarchy used by the
> kernel-image and should not be touched by additional modules that
> are not part of the kernel image.
> 
> is there a policy item that covers this? what do people think?

IMHO the right location is /lib/modules/`uname -r`/net.  .../bcm is
wrong since it is not a new device/driver group.

MfG,
Eduard.
-- 
Hier wird zwar nicht viel gemacht, aber was gemacht wird, ist nicht zu
gebrauchen.


pgpjKuFmoqpfF.pgp
Description: PGP signature