From: Patrick Mansfield <patmans@us.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: %c option does not handle LF as a seperator
Date: Thu, 04 Mar 2004 22:51:17 +0000 [thread overview]
Message-ID: <20040304145117.A29031@beaverton.ibm.com> (raw)
In-Reply-To: <2F75A5CCEF1E6A4C8CA2E75CF7F529E902036598@orsmsx409.jf.intel.com>
On Thu, Mar 04, 2004 at 01:05:27PM +0100, Hannes Reinecke wrote:
> Patrick Mansfield wrote:
> > On Tue, Mar 02, 2004 at 04:42:43PM -0800, Greg KH wrote:
> >
> >>On Tue, Mar 02, 2004 at 04:36:57PM -0800, Sabharwal, Atul wrote:
> >>>>
> >>>>BUS="scsi", PROGRAM="/sbin/scsi_id", RESULT="SSEAGATE ST318436LW
> >>>>3BM07NKA000070456Z6B",
> >>>> NAME="disk-sda-%c{3}"
> >>>>
> > I haven't ever seen a LF in the SCSI vendor, model, or page 0x80. I am not
> > sure if it is allowed by the standards.
> >
> It's not. At least not for page 0x80:
>
> ASCII data fields shall contain only ASCII graphic codes (i.e., code
> values 20h through 7Eh) (from SPC-3).
>
> But actually it's not page 0x80 which is the culprit (0x80 returns only
> the serial number, which seems to be ok), but rather the model name
> (from INQUIRY or page 0x83).
>
> What does the device say at initialisation?
> There should be boot messages from the SCSI layer; if something's dodgy
> with the data it should show up there, too.
>
> Care to send me the output of dmesg?
In working to debug the problem, I got offlist email from Atul (using od,
so the mind numbing line wrapping was not an issue) showing no linefeeds
or such in the model, vendor, or scsi_id output.
-- Patrick Mansfield
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-03-04 22:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 0:36 %c option does not handle LF as a seperator Sabharwal, Atul
2004-03-03 0:42 ` Greg KH
2004-03-03 0:46 ` Kay Sievers
2004-03-03 0:51 ` Sabharwal, Atul
2004-03-03 1:02 ` Kay Sievers
2004-03-03 1:06 ` Sabharwal, Atul
2004-03-03 1:14 ` Patrick Mansfield
2004-03-03 1:23 ` Sabharwal, Atul
2004-03-03 1:32 ` Sabharwal, Atul
2004-03-03 1:59 ` Kay Sievers
2004-03-03 2:28 ` Sabharwal, Atul
2004-03-04 12:05 ` Hannes Reinecke
2004-03-04 22:51 ` Patrick Mansfield [this message]
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=20040304145117.A29031@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=linux-hotplug@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).