linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Havoc Pennington <hp@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: communicating with user login sessions
Date: Sat, 19 Apr 2003 01:24:58 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-105071558112166@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-104977671310586@msgid-missing>

On Fri, Apr 18, 2003 at 05:49:56PM -0700, David Brownell wrote: 
>  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?) 

Yeah it's probably post-0.9; you could grab it from anoncvs though.
 
>        Header:
>            name "org.kernel.hotplug.Kernel.Event"
>            srvc ... goes to how many listeners? ...

broadcast I think. (there will be a way in dbus for clients to
indicate which broadcasts they want, so a broadcast doesn't wake up
every process on the bus - so message senders typically don't need to
worry about who gets the message)

>            sndr ... whatever kernel authenticates itself as ...

sndr is filled in by the bus itself with the connection's base service
name, which is an automatically assigned unique ID.

>        Arguments
>            uint64 - timestamp

I need to add a 64-bit type, haven't done that yet. It's in TODO
though and trivial.

>            string - argv [0]
>            string - argv [1]

Here you probably want to use array of array of byte - using the array
type instead of variable number of args means the message can map to a
function call or callback, and using array of byte instead of string
means it's binary clean (dbus string type is UTF-8).

Havoc


-------------------------------------------------------
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

  parent reply	other threads:[~2003-04-19  1:24 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
2003-04-19  1:24 ` Havoc Pennington [this message]
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-105071558112166@msgid-missing \
    --to=hp@redhat.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).