From: Christian Zoz <zoz@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: New hotplug interface is not working right for me
Date: Fri, 11 Mar 2005 18:58:03 +0000 [thread overview]
Message-ID: <20050311185803.GH8247@suse.de> (raw)
In-Reply-To: <20050311060405.GA16141@thyrsus.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 1684 bytes --]
On Fri, Mar 11, Kay Sievers wrote:
> On Fri, 2005-03-11 at 08:38 -0500, Eric S. Raymond wrote:
> > Kay Sievers <kay.sievers@vrfy.org>:
> > > Yeah, I'm all for doing this with udev rules. It is already working on
> > > my box. We just need to agree if and how we should do that. The plan is
> > > to add hotplug scripts with udev rules and execute scripts based on the
> > > same rule logic we use to name the device node.
> > >
> > > Your hook into hotplug with a udev rule would look like this:
> > > ACTION="add", SYSFS{vendor}="GPS", SYSFS{product}="0815", NAME="gps", HOTPLUG="/usr/bin/gps-something"
> >
> > Hmm, this looks interesting. I'm looking at the udev man page, and it looks
> > as though rules like this might work:
>
> No, not today, not with the current version. We are just thought about
> adding rule based program execution, cause it is similar to all the
> match logic to name a device and it would be more elegant than the
> current directory searching.
Kay, your ideas are very good. Go on and make this happen. I like
this way much more then the current multiplexer.
--
ciao, christian
ç¡ç ä¸è¶³ã¯ããä»äºã®æµã ã
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&opÌk
_______________________________________________
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:[~2005-03-11 18:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 6:04 New hotplug interface is not working right for me Eric S. Raymond
2005-03-11 6:45 ` Greg KH
2005-03-11 8:54 ` Kay Sievers
2005-03-11 13:38 ` Eric S. Raymond
2005-03-11 14:16 ` Kay Sievers
2005-03-11 15:38 ` Hannes Reinecke
2005-03-11 15:40 ` Eric S. Raymond
2005-03-11 16:05 ` Kay Sievers
2005-03-11 17:03 ` Eric S. Raymond
2005-03-11 17:32 ` Kay Sievers
2005-03-11 18:58 ` Christian Zoz [this message]
2005-03-11 19:07 ` Eric S. Raymond
2005-03-11 20:35 ` Kay Sievers
2005-03-11 20:48 ` Eric S. Raymond
2005-03-14 17:06 ` Darren Salt
2005-03-14 18:16 ` Marco d'Itri
2005-03-14 18:25 ` Kay Sievers
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=20050311185803.GH8247@suse.de \
--to=zoz@suse.de \
--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.