From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: communicating with user login sessions
Date: Sat, 19 Apr 2003 00:49:56 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105071271010592@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-104977671310586@msgid-missing>
Havoc Pennington wrote:
>
> How the events get to D-BUS is something I'd defer to kernel hackers
> on - I can't say I have an informed opinion. Basically I gather
> there's some minimal hook to get the event to a userspace process, and
> that process connects to D-BUS and sends the event.
Yes, /sbin/hotplug is that minimal hook for now; though
nothing prevents faster event delivery schemes, should they
ever really be needed. (*)
From what you say, it seems that someone could whip up a
shell script giving us a hotplug-to-DBus gateway, by using
that "dbus-send" program (not in dbus-0.9?) to deliver a
hotplug event like:
Header:
name "org.kernel.hotplug.Kernel.Event"
srvc ... goes to how many listeners? ...
sndr ... whatever kernel authenticates itself as ...
Arguments
uint64 - timestamp
string - argv [0]
string - argv [1]
...
nil
string - envp [0]
string - envp [1]
...
nil
I'd really like to see someone send by such a script, perhaps
an "/etc/hotplug/input.agent" to forward input hotplug events
so that an X11-ish component can at least monitor keyboards,
wheels, drum kits, and such as they appear/disappear.
Eventually of course, that component should make many of those
devices available as X11 input devices... :)
- Dave
(*) I can imagine some kernel switch controlling how the hotplug
event gets formatted and delivered. One option would be
to spawn a process, as we've done so far. Another would be
to queue the events so some process could read them out in
the appropriate format. I'd not be surprised to find people
needing that second option by the time 2.7 starts.
-------------------------------------------------------
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:[~2003-04-19 0:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 4:37 communicating with user login sessions Havoc Pennington
2003-04-08 5:20 ` Greg KH
2003-04-17 23:50 ` David Brownell
2003-04-18 0:13 ` David Brownell
2003-04-18 5:39 ` Havoc Pennington
2003-04-18 5:51 ` Havoc Pennington
2003-04-18 22:40 ` Greg KH
2003-04-18 23:45 ` David Brownell
2003-04-19 0:49 ` David Brownell [this message]
2003-04-19 1:24 ` Havoc Pennington
2003-04-19 1:30 ` Havoc Pennington
2003-04-19 1:43 ` Havoc Pennington
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-105071271010592@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).