linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Mansfield <patman@aracnet.com>
To: Chris Paulson-Ellis <chris@edesix.com>
Cc: dougg@torque.net, Bill Nottingham <notting@redhat.com>,
	linux-hotplug-devel@lists.sourceforge.net,
	linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
	jgarzik@pobox.com
Subject: Re: [PATCH] /dev/disk/by-id incomplete and unhelpful for SATA drives
Date: Fri, 06 Jan 2006 18:58:12 +0000	[thread overview]
Message-ID: <20060106185812.GA6404@aracnet.com> (raw)
In-Reply-To: <43BE7203.8060404@edesix.com>

On Fri, Jan 06, 2006 at 01:34:59PM +0000, Chris Paulson-Ellis wrote:

> Note that it is still a bit different to the page 0x80 output, but I 
> don't think this matters (unless that '0' or '1' is a bug not a 
> feature). For my purposes, it just needs to be unique.
> 
> # ( scsi_id -p 0x80 -g -x -s /block/sda ; \
>     scsi_id -p 0x83 -g -x -s /block/sda ) | grep ID_SERIAL
> ID_SERIAL=SATA_Maxtor_6Y160M0_Y4DCTR3E
> ID_SERIAL\x1aTA_Maxtor_6Y160M0_Y4DCTR3E

Yes, the above is a feature. The SATA in the above is actually S + ATA,
the 'S' is added to guarantee no overlap with page 83 names.

For page 80 the output is concatenation of 'S', vendor, model, and page 80
result, 

For page 83 the output puts the id type as a prefix, so the name spaces
for page 83 can't collide - they are mostly unique across a given id type,
but not for vendor specific, hence we also add model + vendor for vendor
specific.

And for '-x', extra spaces are removed and then spaces converted to '_'.

-- Patrick Mansfield


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&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

  reply	other threads:[~2006-01-06 18:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 18:05 /dev/disk/by-id incomplete and unhelpful for SATA drives Chris Paulson-Ellis
2005-12-21 18:55 ` Kay Sievers
2005-12-21 21:57 ` Chris Paulson-Ellis
2005-12-22  4:35 ` Kay Sievers
2005-12-22 11:24 ` Chris Paulson-Ellis
2005-12-22 18:35 ` Bill Nottingham
2005-12-22 21:08 ` David Liontooth
2005-12-22 22:48 ` Chris Paulson-Ellis
2005-12-23  0:12 ` Chris Paulson-Ellis
2006-01-06  1:36   ` patman
2006-01-06  2:57     ` Douglas Gilbert
2006-01-06 12:39       ` [PATCH] " Douglas Gilbert
2006-01-06 13:34         ` Chris Paulson-Ellis
2006-01-06 18:58           ` Patrick Mansfield [this message]
2006-01-06 19:46         ` Patrick Mansfield
2006-01-06 23:44           ` Douglas Gilbert
2006-03-06 20:08         ` Jeff Garzik
2006-03-07 17:05           ` Douglas Gilbert

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=20060106185812.GA6404@aracnet.com \
    --to=patman@aracnet.com \
    --cc=chris@edesix.com \
    --cc=dougg@torque.net \
    --cc=jgarzik@pobox.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=notting@redhat.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 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).