public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Bradford <john@grabjohn.com>
To: davidsen@tmr.com (Bill Davidsen)
Cc: rddunlap@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix os release detection in module-init-tools-0.9.6
Date: Wed, 1 Jan 2003 16:23:08 +0000 (GMT)	[thread overview]
Message-ID: <200301011623.h01GN8Lw001696@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1030101104259.14470A-100000@gatekeeper.tmr.com> from "Bill Davidsen" at Jan 01, 2003 10:51:14 AM

> > | Um, you read the .config, which hopefully is stored somewhere.
> > | (Although you could resurrect the /proc/config patch which goes around
> > | every so often).  There are many things you can't tell by reading
> > | /proc/ksyms.
> > 
> > Right, the .config file is the answer.  And there are at least 2
> > patch solutions for it, the /proc/config that Rusty mentioned, or
> > the in-kernel config that Khalid Aziz and others from HP did along
> > with me, and it's in 2.4.recent-ac or 2.5.recent-dcl or 2.5.recent-cgl.
> 
> It would be useful to have a few global options perhaps included in /proc
> (or wherever) on all kernels. By global I mean those which affect the
> entire kernel, like preempt or smp, rather than driver options. We already
> note 'tainted,' so this is not a totally new idea. It would seem that most
> of the processor options could fall in this class, MCE, IOAPIC, etc.
> 
> If the aim is to speed stability, putting any of the "whole config"
> options in and defaulted on might be a step toward that.

Having all of the config options in a /proc/config file would be a
great help for people using my new bug database, because it would
allow them to upload the .config for their current kernel even if it
is not one they have compiled themselves.

At the moment, the facility to search for bugs via the config options
that cause them is only useful for people who are compiling their own
kernel.

John.

  reply	other threads:[~2003-01-01 16:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-28 10:38 [PATCH] fix os release detection in module-init-tools-0.9.6 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2002-12-28  5:49 Zhuang, Louis
2002-12-28  6:12 ` Rusty Russell

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=200301011623.h01GN8Lw001696@darkstar.example.net \
    --to=john@grabjohn.com \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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