From: Fong Vang <sudoyang@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 and 2.6 kernel module
Date: Tue, 16 Aug 2005 19:17:15 -0700 [thread overview]
Message-ID: <4f52331f05081619176c9fd472@mail.gmail.com> (raw)
In-Reply-To: <4f52331f050816190542249721@mail.gmail.com>
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.
>
prev parent reply other threads:[~2005-08-17 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 2:05 2.4 and 2.6 kernel module Fong Vang
2005-08-17 2:17 ` Fong Vang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f52331f05081619176c9fd472@mail.gmail.com \
--to=sudoyang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox