From: "Kevin P. Fleming" <kpfleming@cox.net>
To: linux-hotplug@vger.kernel.org
Subject: Hotplug events for block devices?
Date: Wed, 12 Mar 2003 23:09:52 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-104751085302189@msgid-missing> (raw)
In looking at the boot process of a 2.5.64 kernel (with DEBUG defined in
drivers/base/hotplug.c), I can see hotplug events for each of my ATA disks as
they are added to the "ide" bus in sysfs. So far so good.
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.
Currently, the "whole disk" block devices appear in /sys/block, but the
partitions don't seem to appear anywhere in sysfs. However, it appears that the
"block" directory is a sysfs "subsystem", not a class, so no hotplug events are
generated when the block subsystem adds/removes devices.
How should this be accomplished? Should the "block" subsystem really be a sysfs
"class"?
-------------------------------------------------------
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 reply other threads:[~2003-03-12 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 23:09 Kevin P. Fleming [this message]
2003-03-12 23:36 ` Hotplug events for block devices? Greg KH
2003-03-13 0:08 ` Oliver Neukum
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-104751085302189@msgid-missing \
--to=kpfleming@cox.net \
--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).