From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: DEVICE and usb strategy
Date: Mon, 20 Mar 2006 01:00:19 +0000 [thread overview]
Message-ID: <20060320010019.GC11927@vrfy.org> (raw)
In-Reply-To: <dvkfan$9gs$1@sea.gmane.org>
On Sun, Mar 19, 2006 at 09:36:26PM +0100, Andreas Jellinghaus wrote:
> what is the current strategy for usb and DEVICE in udev?
Ignore $DEVICE.
> for example:
> - /proc/bus/usb not mounted
> - /dev/bus/usb is present
> - what should be in DEVICE ?
>
> currently I have a situation with (k)ubuntu dapper / udev 079
> in this case: my application gets called, but with DEVICE pointing
> to /proc/bus/usb/... and that does not exist.
Sure, it didn't make sense in the first place to add an absolute path to
the kernel code.
> Sure, I can add magic code to my application. But before doing so
> I would first like to know if there is a consensus what should be
> in DEVICE and whos job it is to set it properly / handle alternative
> locations. so, what is the strategy on this?
Ignore $DEVICE and $INTERFACE entirely and use the values provided by
the kernel event and the sysfs device pointed to by $DEVPATH.
Kay
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
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:[~2006-03-20 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 20:36 DEVICE and usb strategy Andreas Jellinghaus
2006-03-20 1:00 ` Kay Sievers [this message]
2006-03-20 8:04 ` Andreas Jellinghaus
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=20060320010019.GC11927@vrfy.org \
--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;
as well as URLs for NNTP newsgroup(s).