From: Jeremy Jackson <jerj@coplanar.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: David Lang <dlang@diginsite.com>,
Jeff Garzik <jgarzik@mandrakesoft.com>,
Ian Soboroff <ian@cs.umbc.edu>,
linux-kernel@vger.kernel.org
Subject: Re: /proc/config idea
Date: Tue, 03 Apr 2001 08:43:36 -0400 [thread overview]
Message-ID: <3AC9C577.920036CD@coplanar.net> (raw)
In-Reply-To: <E14kPuE-0007xK-00@the-village.bc.nu>
Alan Cox wrote:
> > a module for 2.4.3 will work for any 2.4.3 kernel that supports modules
> > at all (except for the SMP vs UP issue) so it's not the same thing as
> > trying to figure out which if the 2.4.3 kernels matches what you are
> > running.
>
> Nope. The 2.4 kernel ABI depends upon a mixture of config options including the
> cpu type, as well as the compiler version being used. The API is intended to
> be constant throughout 2.4 (but isnt yet totally solid due to bug fixing
> activity). We don't care about the ABI because we are source code based
>
Is it possible to identify *all* the dependencies and include symbols (or by some
other
method) have these dependencies checked by insmod? It would be simply
smashing to have it all inherently bullet proof. (i know never say never, but
lower maintenance then or simpler for users or something)
next prev parent reply other threads:[~2001-04-03 12:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 13:25 /proc/config idea Ian Soboroff
2001-04-02 14:58 ` Jeremy Jackson
2001-04-02 15:19 ` Brian Gerst
2001-04-02 15:28 ` Bart Trojanowski
2001-04-03 0:23 ` Jeff Garzik
2001-04-03 0:37 ` Jeremy Jackson
2001-04-03 0:49 ` Jeff Garzik
2001-04-03 2:52 ` David Lang
2001-04-03 11:18 ` Olaf Titz
2001-04-03 12:27 ` Alan Cox
2001-04-03 12:43 ` Jeremy Jackson [this message]
2001-04-03 14:32 ` Alan Cox
2001-04-03 0:39 ` David Lang
2001-04-03 5:56 ` Michal Jaegermann
2001-04-03 14:13 ` J . A . Magallon
2001-04-03 18:46 ` Ben Ford
2001-04-03 19:11 ` Alan Cox
2001-04-03 19:12 ` J . A . Magallon
2001-04-03 19:30 ` Mike Castle
2001-04-04 11:56 ` GOMBAS Gabor
2001-04-03 20:57 ` Ben Ford
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=3AC9C577.920036CD@coplanar.net \
--to=jerj@coplanar.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dlang@diginsite.com \
--cc=ian@cs.umbc.edu \
--cc=jgarzik@mandrakesoft.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