From: Ian Soboroff <ian@cs.umbc.edu>
To: linux-kernel@vger.kernel.org
Subject: /proc/config idea
Date: 02 Apr 2001 09:25:55 -0400 [thread overview]
Message-ID: <877l13whzw.fsf@danube.cs.umbc.edu> (raw)
[sorry this doesn't have proper References: headers, i read the list
off the hypermail archive.]
there was some discussion of whether the kernel should emit a
/proc/config or some such for purposes of bug reporting, but that
seems to be a lot of bloat.
instead, why not try to point to a canonical location for a config
copy (we already basically do this with ksymoops and System.map), and
instead have a /proc/config-hash which emits a (precomputed) MD5 hash
of the .config file it was compiled with?
this way, you could check possible configs (Debian for example likes
to stash a copy in /boot, like System.map) and also know if they were
the right ones.
the one problem that comes to mind right now is modules, which needn't
correspond to a full kernel .config.
anyway, my $0.02.
ian
--
----
Ian Soboroff ian@cs.umbc.edu
University of MD Baltimore County http://www.cs.umbc.edu/~ian
next reply other threads:[~2001-04-02 13:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 13:25 Ian Soboroff [this message]
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
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=877l13whzw.fsf@danube.cs.umbc.edu \
--to=ian@cs.umbc.edu \
--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
all inboxes | Powered by JetHome®