From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: communication between applications and hotplugd
Date: Tue, 02 Jul 2002 04:55:34 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102558584513926@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102555289922428@msgid-missing>
On Mon, Jul 01, 2002 at 09:47:09PM +0000, Joseph Wenninger wrote:
>
> I'm implementing an application for KDE, which would need information about
> plugging/unplugging devices, device types and if possibly major/minor device
> numbers (or device node names corresponding with the newly added/removed
> devices).
driverfs combined with /sbin/hotplug will provide this information to
you in 2.5 soon. Pat Mochel and I just presented how this will be done
at the 2002 Ottawa Linux Symposium. I don't know if the talks are
online yet, but later this week, we'll have something written down
and post it to lkml for how it will all work.
Basically driverfs will export the major/minor number for the device,
and /sbin/hotplug will be called when the device shows up or disappears.
With this, devfs is no longer needed, and all of the naming policy can
move to userspace. More details later, I'm supposed to be on vacation
right now :)
thanks,
greg k-h
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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
prev parent reply other threads:[~2002-07-02 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 19:48 communication between applications and hotplugd Joseph Wenninger
2002-07-01 20:47 ` David Brownell
2002-07-02 4:55 ` Greg KH [this message]
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-102558584513926@msgid-missing \
--to=greg@kroah.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).