* 2.4 and 2.6 kernel module
@ 2005-08-17 2:05 Fong Vang
2005-08-17 2:17 ` Fong Vang
0 siblings, 1 reply; 2+ messages in thread
From: Fong Vang @ 2005-08-17 2:05 UTC (permalink / raw)
To: linux-kernel
In the 2.4 kernel, modules contain the "kernel_version" identification
in the module itself. This is an example from the 2.4.18 reiserfs
kernel module:
kernel_version=2.4.18-27.7.xbigmem
using_checksums=1
description=ReiserFS journaled filesystem
author=Hans Reiser <reiser@namesys.com>
license=GPL
kernel_version=2.4.18-27.7.xbigmem
using_checksums=1
This ID doesn't seem to exist anymore in the 2.6 kernel. How does a
2.6 kernel know if a module is compatible?
Thanks for any help.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: 2.4 and 2.6 kernel module
2005-08-17 2:05 2.4 and 2.6 kernel module Fong Vang
@ 2005-08-17 2:17 ` Fong Vang
0 siblings, 0 replies; 2+ messages in thread
From: Fong Vang @ 2005-08-17 2:17 UTC (permalink / raw)
To: linux-kernel
Found the answer by googling further. It's been renamed to vermagic.
strings reiserfs.ko|grep vermagic
vermagic=2.6.9-11.EL 586 REGPARM 4KSTACKS gcc-3.4
On 8/16/05, Fong Vang <sudoyang@gmail.com> wrote:
> In the 2.4 kernel, modules contain the "kernel_version" identification
> in the module itself. This is an example from the 2.4.18 reiserfs
> kernel module:
>
> kernel_version=2.4.18-27.7.xbigmem
> using_checksums=1
> description=ReiserFS journaled filesystem
> author=Hans Reiser <reiser@namesys.com>
> license=GPL
> kernel_version=2.4.18-27.7.xbigmem
> using_checksums=1
>
>
> This ID doesn't seem to exist anymore in the 2.6 kernel. How does a
> 2.6 kernel know if a module is compatible?
>
> Thanks for any help.
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-08-17 2:17 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-08-17 2:05 2.4 and 2.6 kernel module Fong Vang
2005-08-17 2:17 ` Fong Vang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox