The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: Oliver Xymoron <oxymoron@waste.org>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
	David Lang <dlang@diginsite.com>,
	Manfred Spraul <manfred@colorfullife.com>,
	"Albert D. Cahalan" <acahalan@cs.uml.edu>,
	lm@bitmover.com, linux-kernel@vger.kernel.org
Subject: Re: bug database braindump from the kernel summit
Date: Mon, 02 Apr 2001 19:04:47 -0400	[thread overview]
Message-ID: <3AC9058F.580E268B@mountain.net> (raw)
In-Reply-To: <Pine.LNX.4.30.0104021436110.24812-100000@waste.org>

Oliver Xymoron wrote:
> 
> On Sun, 1 Apr 2001, Jeff Garzik wrote:
> 
> > On Sun, 1 Apr 2001, David Lang wrote:
> > > if we want to get the .config as part of the report then we need to make
> > > it part of the kernel in some standard way (the old /proc/config flamewar)
> > > it's difficult enough sometimes for the sysadmin of a box to know what
> > > kernel is running on it, let alone a bug reporting script.
> >
> > Let's hope it's not a flamewar, but here goes :)
> >
> > We -need- .config, but /proc/config seems like pure bloat.
> 
> As a former proponent of /proc/config (I wrote one of the much-debated
> patches), I tend to agree. Debian's make-kpkg does the right thing, namely
> treating .config the same way it treats System-map, putting it in the
> package and eventually installing it in /boot/config-x.y.z. If Redhat's
> kernel-install script did the same it would rapidly become a non-issue.

How about /lib/modules/$(uname -r)/build/.config ? It's already there.

Tom

-- 
The Daemons lurk and are dumb. -- Emerson

  parent reply	other threads:[~2001-04-02 23:06 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-01 19:32 bug database braindump from the kernel summit Manfred Spraul
2001-04-01 20:17 ` Albert D. Cahalan
2001-04-01 21:07   ` Jeff Garzik
2001-04-01 21:48     ` Manfred Spraul
2001-04-01 22:48       ` Jeff Garzik
2001-04-01 23:01         ` David Lang
2001-04-01 23:21           ` Jeff Garzik
2001-04-01 23:25             ` David Lang
2001-04-01 23:34               ` Jeff Garzik
2001-04-01 23:32                 ` David Lang
2001-04-01 23:44                   ` Jeff Garzik
2001-04-01 23:43                     ` David Lang
2001-04-02  0:26                       ` Ben Ford
2001-04-02 18:57                         ` Kai Henningsen
2001-04-05 12:55                         ` Petr Baudis
2001-04-02  5:26             ` Richard Russon
2001-04-02 21:35               ` Steven Walter
2001-04-02 19:39             ` Oliver Xymoron
2001-04-02 21:40               ` J . A . Magallon
2001-04-02 22:09                 ` Jeff Garzik
2001-04-02 22:24                   ` David Lang
2001-04-02 22:38                   ` J . A . Magallon
2001-04-02 23:04               ` Tom Leete [this message]
2001-04-02 23:12                 ` Oliver Xymoron
2001-04-02 23:24                   ` Jeff Garzik
2001-04-02 23:31                     ` Oliver Xymoron
2001-04-03 16:05                   ` Miles Lane
2001-04-02  1:49     ` Miles Lane
2001-04-01 20:59 ` Jeff Garzik
  -- strict thread matches above, loose matches on Subject: below --
2001-04-01 22:34 Stephen Satchell
2001-04-02  8:00 ` Olaf Titz
2001-04-01 17:54 Larry McVoy
2001-04-01 19:43 ` Albert D. Cahalan
2001-04-01 20:21   ` Gregory Maxwell
2001-04-01 20:38     ` Albert D. Cahalan
2001-04-01 21:16 ` David Lang
2001-04-01 21:18   ` David Lang
2001-04-02  1:57   ` Miles Lane
2001-04-02  5:07     ` David Lang
2001-04-01 23:14 ` Jeff Garzik
2001-04-02 13:31 ` Rogier Wolff

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=3AC9058F.580E268B@mountain.net \
    --to=tleete@mountain.net \
    --cc=acahalan@cs.uml.edu \
    --cc=dlang@diginsite.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=manfred@colorfullife.com \
    --cc=oxymoron@waste.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