Re: Kernel module package depending on kernel-headers.
>>"Ian" == Ian Zimmerman <email@example.com> writes:
Manoj> And you can set up your module postinst to install the module
Manoj> in any directory you want -- /lib/modules/2.4/foo, for example,
Manoj> and copy files at will.
Ian> But what is the point of having them in a package, then?
Heh. I have 2.4.17 installed, and I install module_foo. Where
do the module files go?
I now install 2.4.18. Now, either the module search path is
changed, or boom! no more module foo with new kernel.
That is why the packaged module foo should copy files to 2.4.18
Ian> Okay, I didn't know about the first part, thanks for pointing it out.
Ian> But it would only be of any import if the rigid dependencies were
The rigid dependencies are created by people who package
modules. They are there since it is a hassle to implement the hooked
file copy stuff that is needed in order for packaged modules to work
There really are reasons for the rigid dependendcies. We are
not quite all morons here, you know. Even if we can't spell.
I'm a lucky guy, and I'm happy to be with the Yankees. And I want to
thank everyone for making this night necessary. Yogi Berra at a
dinner in his honor
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
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