All of lore.kernel.org
 help / color / mirror / Atom feed
From: Treeve Jelbert <treeve01@pi.be>
To: linux-hotplug@vger.kernel.org
Subject: scsi cdrom
Date: Thu, 04 Mar 2004 10:15:54 +0000	[thread overview]
Message-ID: <200403041115.58030.treeve01@pi.be> (raw)
In-Reply-To: <1078395247.1172.1.camel@pim>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm trying to make udev create a symlink cdrw for my scsi cdrom

at the moment my rule matches for both sr0 and sg0 and the symlink is created 
twice, finally pointing to sg0


BUS="scsi", SYSFS{vendor}="PLEXTOR ", NAME="%k", SYMLINK="cdrw%n"

I tried using scsi_id, but that fails

# /sbin/scsi_id -s /block/sr0
0:0:4:0: sg_io failed status 0x0 0x0 0x0 0x2
0:0:4:0: sense key 0x5 ASC 0x24 ASCQ 0x0


Can anyone advise me how to check for a block device, rather than a generic 
device?


Regards,  Treeve 

- -- 
PGP Key ID: AB929B24
PGP Key Fingerprint:31D9 D22F 42E6 F545 662E  AB6F 9697 34C5 AB92 9B24 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFARwHalpc0xauSmyQRAk7zAJ9KprWf+XOK8Gu4rMBiteJwyZISpQCfe+a6
LRngClk10Qpjz7dR+8tLJLA=1yvZ
-----END PGP SIGNATURE-----


-------------------------------------------------------
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Ìk
_______________________________________________
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:[~2004-03-04 10:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-04 10:14 scsi cdrom Kay Sievers
2004-03-04 10:15 ` Treeve Jelbert [this message]
2004-03-04 10:47 ` [hotplug] " Treeve Jelbert

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=200403041115.58030.treeve01@pi.be \
    --to=treeve01@pi.be \
    --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 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.