From: Rusty Russell <rusty@rustcorp.com.au>
To: "Zhuang, Louis" <louis.zhuang@intel.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix os release detection in module-init-tools-0.9.6
Date: Sat, 28 Dec 2002 17:12:56 +1100 [thread overview]
Message-ID: <20021228062644.83BF62C06B@lists.samba.org> (raw)
In-Reply-To: Your message of "Sat, 28 Dec 2002 13:49:49 +0800." <957BD1C2BF3CD411B6C500A0C944CA2601AA1377@pdsmsx32.pd.intel.com>
In message <957BD1C2BF3CD411B6C500A0C944CA2601AA1377@pdsmsx32.pd.intel.com> you
write:
> Dear Rusty,
> IMHO, try_old_version can tell kernel release better with this
> patch, don't you? ;->
> - Louis
I prefer, in principle, to test for features, not kernel versions.
What about 2.1, for example?
I've changed the check to sys_create_module(NULL, 0) != -ENOSYS,
instead, which should cover everything.
Now, why do you want /proc/ksyms exactly? I'm not hugely opposed to
it, but it's rarely what people actually want, since it contains only
exported symbols.
My plan was to change the format of /proc/modules slightly to make it
extensible (patch on my page), then add the "start of module"
parameter, which should allow ksymoops and oprofile to handle modules
cleanly again (although ksymoops is less urgent since CONFIG_KALLSYMS
does such a nice job for most things).
Hope that clarifies,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2002-12-28 6:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 5:49 Zhuang, Louis
2002-12-28 6:12 ` Rusty Russell [this message]
2002-12-28 10:38 Zhuang, Louis
2002-12-29 5:54 ` Rusty Russell
2002-12-29 18:33 ` Randy.Dunlap
2003-01-01 15:51 ` Bill Davidsen
2003-01-01 16:23 ` John Bradford
2003-01-01 18:53 ` Randy.Dunlap
2003-01-02 12:47 ` Bill Davidsen
2003-01-02 13:07 ` John Bradford
2003-01-02 16:22 ` Randy.Dunlap
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=20021228062644.83BF62C06B@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.zhuang@intel.com \
/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
Powered by JetHome