From owner-freebsd-hackers Fri Apr 28 22:33:23 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA08761 for hackers-outgoing; Fri, 28 Apr 1995 22:33:23 -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 WAA08754 for ; Fri, 28 Apr 1995 22:33:19 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.11/8.6.11) id XAA06209; Fri, 28 Apr 1995 23:37:33 -0600 Date: Fri, 28 Apr 1995 23:37:33 -0600 From: Nate Williams Message-Id: <199504290537.XAA06209@trout.sri.MT.net> To: Poul-Henning Kamp Cc: jkh@time.cdrom.com (Jordan K. Hubbard), hackers@FreeBSD.org Subject: Re: What I'd *really like* for 2.0.5 In-Reply-To: <199504290525.WAA23948@ref.tfs.com> References: <11052.799132602@time.cdrom.com> <199504290525.WAA23948@ref.tfs.com> Sender: hackers-owner@FreeBSD.org Precedence: bulk > > All the probe messages irritate the hell out of me. The style is > > inconsistent in many places and I still maintain that I do *NOT* want > > to know about all the things it didn't find, I want to know about only > > the things it did since.... > With the advent of userconfig, I'm for removing them. Now you can use > userconfig to see what drivers you have in your kernel. > > Lets kill them now. 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. > > Anyone of a mind to go on a little boot message reform rampage? > yes please. Please don't until we get other folks who have an opinion on this to speak their mind. Nate