Date: Sat, 29 Apr 1995 00:00:57 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: phk@ref.tfs.com (Poul-Henning Kamp) Cc: nate@trout.sri.MT.net, jkh@time.cdrom.com, hackers@FreeBSD.org Subject: Re: What I'd *really like* for 2.0.5 Message-ID: <199504290700.AAA08761@gndrsh.aac.dev.com> In-Reply-To: <199504290539.WAA24041@ref.tfs.com> from "Poul-Henning Kamp" at Apr 28, 95 10:39:25 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > > 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. > > Nate are you sleeping ? > Have you tried "boot: /kernel -c" lately ??? > userconfig IS ONLY available at booup ! Then I counter with the opposite argument, I can't see what did not get found after boot if you remove the not found messages. Right now I can use dmesg or look in /var/log/messages and see it, but if you remove those I would have no way to find out what I told it to probe for but it did not find :-(. -- 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?199504290700.AAA08761>