From owner-freebsd-hackers Fri Apr 28 22:43:09 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08912 for hackers-outgoing; Fri, 28 Apr 1995 22:43:09 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA08906 for ; Fri, 28 Apr 1995 22:43:05 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id XAA06260; Fri, 28 Apr 1995 23:47:16 -0600 Date: Fri, 28 Apr 1995 23:47:16 -0600 From: Nate Williams Message-Id: <199504290547.XAA06260@trout.sri.MT.net> To: Poul-Henning Kamp Cc: nate@trout.sri.MT.net (Nate Williams), jkh@time.cdrom.com, hackers@FreeBSD.org Subject: Re: What I'd *really like* for 2.0.5 In-Reply-To: <199504290539.WAA24041@ref.tfs.com> References: <199504290537.XAA06209@trout.sri.MT.net> <199504290539.WAA24041@ref.tfs.com> Sender: hackers-owner@FreeBSD.org Precedence: bulk > > I disagree. On bootup you don't have access to userconfig, and it's a > > very useful debugging tool to find out what's a kernel's been compiled > > with to see if you're it's a driver bug or a hardware misconfiguration. > > Have you tried "boot: /kernel -c" lately ??? > userconfig IS ONLY available at booup ! What I meant was that userconfig assumes the user has knowlege on how it works, so for normal people they don't have 'access' to it. Access was probably a poor choice of word to use. *IF* we are going to use it for all of the kernel device debugging, then it should be better documented before we remove the only useful form we have now. Nate