From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: how to notify blindly created 'all_partitions' to dbus, HAL, gvm
Date: Sun, 11 Apr 2004 12:11:29 +0000 [thread overview]
Message-ID: <20040411121129.GA5590@vrfy.org> (raw)
We have a feature in udev to create all 15 partitions for a removable
media device without looking at it. It's needed cause most of the devices
never notify about a media change and with a fully dynamic /dev we need
to access one partition to force the kernel to revalidate the device.
This all couldn't be avoided without polling :(
Now as we create nodes, should we execute the /etc/dev.d/ programs for
the "blind" partition nodes? What are the implications for HAL, gvm?
And should we fake the DEVPATH for it, huhh...?
thanks,
Kay
-------------------------------------------------------
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=click
_______________________________________________
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:[~2004-04-11 12:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-11 12:11 Kay Sievers [this message]
2004-04-11 13:57 ` how to notify blindly created 'all_partitions' to dbus, HAL, David Zeuthen
2004-04-11 14:42 ` how to notify blindly created 'all_partitions' to dbus, HAL, gvm 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=20040411121129.GA5590@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).