From: Oliver Neukum <oliver@neukum.name>
To: linux-hotplug@vger.kernel.org
Subject: Re: Hotplug events for block devices?
Date: Thu, 13 Mar 2003 00:08:03 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-104751416505361@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-104751085302189@msgid-missing>
> > However, I'd like to be able to receive hotplug events for _all_ block
> > devices, regardless of connection type or anything else. In fact, I'd
> > like to receive hotplug events for all block device _minors_ as well, so
> > when the kernel scans (or receives) partition information that would
> > generate events as well. The event would only have to indicate
> > add/remove, "block", and the DEVPATH to the device node in sysfs.
>
> Yes, that would be very good, and has been on my list of things to do
> for quite some time.
How do you construct a sensible DEVPATH for iSCSI or nbd ?
How do you notify about the loss or gain of an IO path as opposed
to a whole device?
Regards
Oliver
-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open!
Get cracking and register here for some mind boggling fun and
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
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 prev parent reply other threads:[~2003-03-13 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 23:09 Hotplug events for block devices? Kevin P. Fleming
2003-03-12 23:36 ` Greg KH
2003-03-13 0:08 ` Oliver Neukum [this message]
2003-03-13 0:10 ` Greg KH
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=marc-linux-hotplug-104751416505361@msgid-missing \
--to=oliver@neukum.name \
--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.