From: "Andreas Jellinghaus [c]" <aj@ciphirelabs.com>
To: linux-hotplug@vger.kernel.org
Subject: rule for scsi tape changers? [u]
Date: Tue, 28 Aug 2007 06:31:17 +0000 [thread overview]
Message-ID: <200708280831.17841.aj@ciphirelabs.com> (raw)
before re-inventing the wheel: does anyone have a rule for scsi device
changers? the typical name would be /dev/changer and the devices are usualy
sg* devices. kernel dmesg tells me:
TID 513 Vendor: HP M Device: MSL6000 Seri Rev: 0507
Vendor: HP Model: MSL6000 Series Rev: 0507
Type: Medium Changer ANSI SCSI revision: 02
0:0:0:0: Attached scsi generic sg0 type 8
udevinfo:
BUS="scsi"
ID="0:0:0:0"
DRIVER="unknown"
SYSFS{device_blocked}="0"
SYSFS{iocounterbits}="32"
SYSFS{iodone_cnt}="0x9f9"
SYSFS{ioerr_cnt}="0xd"
SYSFS{iorequest_cnt}="0x9f9"
SYSFS{model}="MSL6000 Series "
SYSFS{queue_depth}="1"
SYSFS{queue_type}="none"
SYSFS{rev}="0507"
SYSFS{scsi_level}="3"
SYSFS{state}="running"
SYSFS{timeout}="0"
SYSFS{type}="8"
SYSFS{vendor}="HP "
I see the rules on my ubuntu systems use ENV{ID_CDROM} and friends for cdrom
devices. what creates these? is there a simialr ID_CHANGER information?
Thanks, Andreas
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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
next reply other threads:[~2007-08-28 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-28 6:31 Andreas Jellinghaus [c] [this message]
2007-08-28 13:41 ` rule for scsi tape changers? [u] Jamie Wellnitz
2007-08-28 14:49 ` Kay Sievers
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=200708280831.17841.aj@ciphirelabs.com \
--to=aj@ciphirelabs.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).