Linux Hotplug development
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Starting with udev
Date: Fri, 12 Mar 2010 15:53:08 +0000	[thread overview]
Message-ID: <ac3eb2511003120753v608bf8c1jfe73594565d9c78c@mail.gmail.com> (raw)
In-Reply-To: <20100311095534.637ab0a7@tosh-l20.laptop>

On Fri, Mar 12, 2010 at 16:39, Salvatore De Paolis <iwkse@claws-mail.org> wrote:
> On Thu, 11 Mar 2010 10:33:49 +0100
> Kay Sievers <kay.sievers@vrfy.org> wrote:
>
>> Udev runs at the system-level as root, it can not talk to your user
>> session where the notification would appear. You have to subscribe to
>> events from your user session, and not put system-wide rules into
>> udev, to get events in your session.

> Thank's it's clear now the logic under it. By the way I didn't find a lot of
> documentation about it. Writing udev rules [1] doesn't help from this side.
> I'll get the source and build the doc.
> Otherwise do you have other useful links?

This is maybe the closest to what you are looking for. Ignore all the
HAL bits, that all has changed, but the model is almost the same. Look
at the diagram at page 17 for the flow of events in a more complicated
example:
  http://people.freedesktop.org/~david/talks/dynamic-device-handling-OLS-2006.pdf

Less pretty diagrams, but pretty much up-to-date:
  http://people.freedesktop.org/~david/talks/Plumbers-2009-Sievers-Zeuthen-Replugging-The-Modern-Desktop.pdf

Kay

  parent reply	other threads:[~2010-03-12 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11  8:55 Starting with udev Salvatore De Paolis
2010-03-11  9:33 ` Kay Sievers
2010-03-12 15:39 ` Salvatore De Paolis
2010-03-12 15:53 ` Kay Sievers [this message]
2010-03-12 16:57 ` Salvatore De Paolis

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=ac3eb2511003120753v608bf8c1jfe73594565d9c78c@mail.gmail.com \
    --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