Rumor has it that on Wed, Jun 21, 2006 at 10:50:57AM -0600 Matthew Wilcox said: > 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? > You don't read var/log/dmesgs when you are looking at a scsi issue? I really meant eye ball parsing mostly. > 2) This information is available other ways, such as through sysfs and > procfs. Why put it here at all then? ;) > > 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. I know they're fixed size fields. I'm not good at counting spaces that's why I offered the suggestion of some sort of field sep character. I wouldn't have thought about it if you didn't use an example with white spaces :) Cheers, Phil -- Philip R. Auld, Ph.D. Egenera, Inc. Software Architect 165 Forest St. (508) 858-2628 Marlboro, MA 01752 - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
