Subject: Re: More verbose SCSI errors...
To: None <firstname.lastname@example.org>
From: John Kohl <email@example.com>
Date: 08/19/1997 12:06:32
>>>>> "MJ" == Matthew Jacob <firstname.lastname@example.org> writes:
MJ> What you suggest though, does raise a tough call question. I really
MJ> am torn between taking the BSDI approach (requiring more userland work,
MJ> but that's okay) and getting instant functionality.
My take on this: provide a kernel option with full string decoding, and
another option (maybe make this the default?) to spit out ASC/ASCQ
numeric pairs. Keep the existing full details available too (maybe
under an option?).
Once the kernel stuff is in shape, step back and relax, then consider a
user-level interpretation tool.