Date: Wed, 30 Sep 1998 21:20:36 +0800 From: Peter Wemm <peter@netplex.com.au> To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Cc: Kenneth Merry <ken@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/cam/scsi scsi_all.c scsi_all.h Message-ID: <199809301320.VAA12170@spinner.netplex.com.au> In-Reply-To: Your message of "30 Sep 1998 14:40:57 %2B0200." <xzpk92lixie.fsf@grjottunagard.ifi.uio.no>
index | next in thread | previous in thread | raw e-mail
Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= wrote:
> Kenneth Merry <ken@FreeBSD.ORG> writes:
> > Log:
> > In the bootverbose case, print out error messages for all errors that wil
l
> > not be retried again, even if the SF_NO_PRINT flag is set.
>
> Could the bootverbose flag be made accessible through sysctl? This way
> you could boot verbose to get detailed probe messages, and switch it
> off later to avoid "unintersting" messages such as "tagged openings"
> etc. I'm willing to do the deed if somebody more clueful than me okays
> it and reviews the patch...
Perhaps it should be a second variable, eg: scsi_verbose.. and a
corresponding sysctl hw.scsi_verbose (or hw.scsi.verbose if there is
potential for more hw.scsi.* variables).
Then, the code can do a 'scsi_verbose = bootverbose' once at first startup
time, and references to bootverbose can be changed to scsi_verbose in the
cam code.
At the moment this would pretty much have the same effect, but the prospect
of twiddling bootverbose itself on the fly at runtime sends a chill down my
spine..
Cheers,
-Peter
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199809301320.VAA12170>