Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 2 Apr 2001 19:14:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 2 Apr 2001 19:14:04 -0400 Received: from waste.org ([209.173.204.2]:5733 "EHLO waste.org") by vger.kernel.org with ESMTP id ; Mon, 2 Apr 2001 19:13:45 -0400 Date: Mon, 2 Apr 2001 18:12:25 -0500 (CDT) From: Oliver Xymoron To: Tom Leete cc: Jeff Garzik , David Lang , Manfred Spraul , "Albert D. Cahalan" , , Subject: Re: bug database braindump from the kernel summit In-Reply-To: <3AC9058F.580E268B@mountain.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2 Apr 2001, Tom Leete wrote: > 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. It'd be great if we got away from the config being hidden too. -- "Love the dolphins," she advised him. "Write by W.A.S.T.E.." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/