All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennart Poettering <lennart@poettering.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks
Date: Thu, 13 May 2010 14:06:09 +0000	[thread overview]
Message-ID: <20100513140607.GB12639@tango.0pointer.de> (raw)
In-Reply-To: <20100513134742.GB1768@piware.de>

On Thu, 13.05.10 15:47, Martin Pitt (martin.pitt@ubuntu.com) wrote:

> Hello Kay,
> 
> Kay Sievers [2010-05-13 15:29 +0200]:
> > >  (2) I hear that udevd will eventually go away, and its probers will
> > >     be fanned out to the subsystem daemons, therefore leaving the
> > >     udev package as a relatively stable library only.
> > 
> > Oh, that's interesting news. :) What makes you think of that? 
> 
> Scott just gave a presentation about the plumbing layer, and mentioned
> that. It came as quite a surprise to me, too, and that's why I wrote "I
> hear", not "it is" :) I'll ask him about this.
> 
> > What would match on and deliver all the kernel events to subcribers?
> 
> As far as I understood it, libudev would stay for client-side programs
> (reading events from netlink and enumerate from /sys), and the udev
> database would stay for the properties, but the udev daemon
> would/could go away.

OMG! Ubuntu is forking udev! This is ... funny...

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4

  reply	other threads:[~2010-05-13 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-13 13:47 udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks rules Martin Pitt
2010-05-13 14:06 ` Lennart Poettering [this message]
2010-05-16 11:22 ` udevd [was: Re: [RFC/PATCH] input_id: add touchpad quirks Scott James Remnant
2010-05-16 16:04 ` Greg KH
2010-05-17 11:10 ` Scott James Remnant
2010-05-17 16:14 ` 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=20100513140607.GB12639@tango.0pointer.de \
    --to=lennart@poettering.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.