Date: Sat, 29 Apr 1995 04:35:13 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Bruce Evans <bde@zeta.org.au> Cc: phk@ref.tfs.com, rgrimes@gndrsh.aac.dev.com, hackers@FreeBSD.org, nate@trout.sri.MT.net Subject: Re: What I'd *really like* for 2.0.5 Message-ID: <13796.799155313@time.cdrom.com> In-Reply-To: Your message of "Sat, 29 Apr 1995 17:37:24 %2B1000." <199504290737.RAA15373@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> The drivers should be removed, not their messages. You can use userconfig > or the (unimplemented) driver-disable flag in your config file to disable > drivers without completely removing them.. This assumes the average user is competent enough to play with userconfig's disable or compile a kernel. Judging by the tech support calls I get, the average user isn't. > I agree. The messages are for putting in /var/log/messages to look > at later and quote in bug reports. `bootverbose' should not affect the > amount of output that is logged to disk. There should probably be > more boot messages, but less printed on the console. The message > buffer currently limits the number of boot messages too much. Then this should be fixed. The entire idea of bootverbose was, to me, to be able to REALLY diagnose user problems with the increased level of debugging information supplied. I don't know about you, but "bt0: not found at 0x330" has NEVER been that helpful to me in diagnosing these user problems that people seem to be arguing so vehemently (and needlessly) that we need to be able to solve. I never disagreed with any of that. I don't, however, think that the current output is helpful enough to qualify as anything but noise. You guys are fighting the good fight, but on entirely the wrong battlefield. An entirely common syndrome among UNIX die-hards and exactly why we lost the war to Microsoft. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13796.799155313>