From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: communication between applications and hotplugd
Date: Mon, 01 Jul 2002 20:47:27 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-102555659026763@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102555289922428@msgid-missing>
> Is there a way an application can communicate directly with the hotplugd,
> instead of just a bunch of scripts ?
/sbin/hotplug is invoked by the kernel as the way it
reports hotplug events ... there is no "hotplugd".
What you could do is have /sbin/hotplug forward those
events to some application using named pipes or sockets.
That's been discussed as one of the mechanisms by which
the X11 server, for one example, would learn about new
input devices. Clearly it could work for any kind of
hotplug event.
As for notification about new /dev nodes (char/block
major and minor) ... you might be able to make "devfsd"
do it. Remember that there's no linkage within the
kernel between the device ids it uses (c/b major/minor)
and the filenames assigned to them in /dev, except for
systems that use devfs. Until "driverfs" gets more
functional (in 2.5) I suspect some of what you want
is going to be difficult.
- Dave
-------------------------------------------------------
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
next prev parent reply other threads:[~2002-07-01 20:47 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 [this message]
2002-07-02 4:55 ` 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-102555659026763@msgid-missing \
--to=david-b@pacbell.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).