Date: Fri, 28 Apr 1995 23:50:47 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: jkh@time.cdrom.com (Jordan K. Hubbard) Cc: hackers@FreeBSD.org Subject: Re: What I'd *really like* for 2.0.5 Message-ID: <199504290650.XAA08734@gndrsh.aac.dev.com> In-Reply-To: <11052.799132602@time.cdrom.com> from "Jordan K. Hubbard" at Apr 28, 95 10:16:42 pm
next in thread | previous in thread | raw e-mail | index | archive | help
[CC: trimmed] ... > > You're not alone.. :-) These should be going away soon. > > > - The SCSI disk probe messages also irritate the hell out of me: > > 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 the "fnob0: not found" messages just obscure > the messages I'm really looking for (or cause them to scroll off the > screen). Unfortunately, I seem to be in the minority here as a number > of other folks say that they like all that "extra diagnostic information." > > I say fiddlesticks, and it's time to make the -v flag earn its keep. > FreeBSD should either shut up entirely or spew loads of stuff at you > if you boot with -v. > > Anyone of a mind to go on a little boot message reform rampage? At FreeBSD 1.1 I went through every probe message generated by the GENERIC system and made them consistent. Since then people have pulled in all sorts of directions and we are now seriously inconsistent. I had it down to close to 1 line, and rarely more than 2 lines per device. We have now gone to 3 to 4 lines per device :-(. The ``not found'' messages issue was debated and decided shortly after it was implemented. The major reason for keeping it around is that you know the kernel looked for the device, you know at what address it tried to find it, and you know that the probe returned 0 for some reason. This has always helped with debugging peoples problems with misconfigured systems. It also acts as a big reminder you have cruft in your kernel that you should probably remove from it. I do mind to some extent if you go on a ``message reform rampage'' with out a clear statement of just what it is you are going to do. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504290650.XAA08734>