From: "'Patrick Mansfield'" <patmans@us.ibm.com>
To: "Mukker, Atul" <Atulm@lsil.com>
Cc: 'Greg KH' <greg@kroah.com>,
'James Bottomley' <James.Bottomley@steeleye.com>,
'Linux Kernel' <linux-kernel@vger.kernel.org>,
'SCSI Mailing List' <linux-scsi@vger.kernel.org>,
linux-hotplug-devel@lists.sourceforge.net
Subject: Re: How to add/drop SCSI drives from within the driver?
Date: Thu, 27 Jan 2005 07:05:50 +0000 [thread overview]
Message-ID: <20050127070550.GA18632@us.ibm.com> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E5705B83A31@exa-atlanta>
[moving to hotplug list ...]
On Wed, Jan 26, 2005 at 06:23:16PM -0500, Mukker, Atul wrote:
> Or more likely, by placing our agent in /etc/dev.d directory. Unfortunately,
> there seems be not a consensus here as well. On system has "default" and
> "net" directories and other has "block", "input", "net", "tty"?
Those are all kernel subsystem names, and as such all are supported
directory structures for udev, the part that is distro specific is that
they supply different scripts.
There won't be any "scsi" devices since they have no dev (the upper level
drivers have them); sg shows up as scsi_generic. sd is block.
You will still have to figure out via sysfs if you want to run your agent
even for subsystem block (i.e. figure out the host/driver type, I assume
you don't want to run it on hd or standard scsi disk drives).
I don't know why this is an issue for "new" devices, this should be a
problem for you when they first show up; existing and new devs should be
handled the same way.
-- Patrick Mansfield
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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
parent reply other threads:[~2005-01-27 7:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <0E3FA95632D6D047BA649F95DAB60E5705B83A31@exa-atlanta>]
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=20050127070550.GA18632@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=Atulm@lsil.com \
--cc=James.Bottomley@steeleye.com \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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).