From: Matthew Wilcox <matthew@wil.cx>
To: "Philip R. Auld" <pauld@egenera.com>
Cc: "Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
dougg@torque.net, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Print SCSI Inquiry data more compactly
Date: Wed, 21 Jun 2006 10:50:57 -0600 [thread overview]
Message-ID: <20060621165057.GW1630@parisc-linux.org> (raw)
In-Reply-To: <20060621164150.GM31472@vienna.egenera.com>
On Wed, Jun 21, 2006 at 12:41:50PM -0400, Philip R. Auld wrote:
> > scsi 2:0:1:0: Device: DASD HP 18.2G ATLAS10K3_18_SCA HP05 ANSI ver: 02
>
> Parsing this, (and the Matt's earlier version), there are 5 tokens
> there in the middle for 4 fields. How does one know what the vendor
> string is for example?
1) This is not for parsing, it's informational for users. Do tools
really still parse through /var/log/dmesg?
2) This information is available other ways, such as through sysfs and
procfs.
3) I know it's not obvious from the above example (damn HP firmware),
but these are actually fixed-size fields. The first is 8 bytes, "HP 18.2G"
the second 16 bytes are "ATLAS10K3_18_SCA", the third is "HP05" and then
the ANSI ver is at the end.
next prev parent reply other threads:[~2006-06-21 16:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 15:42 [PATCH] Print SCSI Inquiry data more compactly Salyzyn, Mark
2006-06-21 16:41 ` Philip R. Auld
2006-06-21 16:50 ` Matthew Wilcox [this message]
2006-06-21 17:02 ` Eddie Williams
2006-06-21 17:18 ` James Smart
2006-06-21 17:33 ` Matthew Wilcox
2006-06-21 18:04 ` Stefan Richter
2006-06-21 19:03 ` Matthew Wilcox
2006-06-21 22:36 ` Stefan Richter
2006-06-22 2:55 ` Douglas Gilbert
2006-06-21 17:47 ` Philip R. Auld
2006-06-21 22:14 ` Stefan Richter
2006-06-21 22:23 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2006-06-20 22:27 Matthew Wilcox
2006-06-21 14:50 ` Douglas Gilbert
2006-06-21 15:47 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060621165057.GW1630@parisc-linux.org \
--to=matthew@wil.cx \
--cc=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=mark_salyzyn@adaptec.com \
--cc=pauld@egenera.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.