All of lore.kernel.org
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: Re: fully udev-based hotplug system
Date: Fri, 24 Jun 2005 12:35:38 +0000	[thread overview]
Message-ID: <20050624123538.GA11206@wonderland.linux.it> (raw)
In-Reply-To: <20050623215418.GA16536@wonderland.linux.it>

[-- Attachment #1: Type: text/plain, Size: 754 bytes --]

On Jun 24, Kay Sievers <kay.sievers@vrfy.org> wrote:

> > ACTION=="add", SUBSYSTEM=="input", BUS=="serio", \
> > 	RUN+="/etc/hotplug/serio.agent"
>
> The input subsystem is still broken and calls /sbin/hotplug directly.
> The SUSE kernels introduced a "input_device"-class to solve that, but during
> the last months the input-maintainers just _talk_ about ideas instead of
> fixing that mess. :( The patch we use is attached.
I understand that even if /proc/sys/kernel/hotplug is udevsend its
events will be ignored anyway as soon as a netlink message is received,
is this correct?
If it is, then I will have to disable netlink events processing in udev,
I cannot require Debian/unstable users to patch their kernels.

-- 
ciao,
Marco

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-06-24 12:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 21:54 fully udev-based hotplug system Marco d'Itri
2005-06-24  3:04 ` Bill Nottingham
2005-06-24  5:00 ` Greg KH
2005-06-24  5:02 ` Greg KH
2005-06-24 12:27 ` Kay Sievers
2005-06-24 12:35 ` Marco d'Itri [this message]
2005-06-24 12:43 ` Kay Sievers
2005-06-24 18:33 ` Bill Nottingham
2005-06-24 18:50 ` 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=20050624123538.GA11206@wonderland.linux.it \
    --to=md@linux.it \
    --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.