From: Clemens Ladisch <clemens@ladisch.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: persistent FireWire device names
Date: Wed, 04 Jul 2012 19:48:04 +0000 [thread overview]
Message-ID: <4FF49DF4.4080208@ladisch.de> (raw)
In-Reply-To: <4FF47870.3020509@ladisch.de>
Kay Sievers wrote:
> On Wed, Jul 4, 2012 at 7:08 PM, Clemens Ladisch <clemens@ladisch.de> wrote:
>> Makefile.am | 1 +
>> rules/60-persistent-firewire.rules | 26 ++++++++++++++++++++++++++
>> 2 files changed, 27 insertions(+), 0 deletions(-)
>
> What is this useful for? Firewire is by definiton a hotplug bus, and
> application dealing with raw firewire nodes, need to manage that
> anyway.
Most normal applications indeed do this.
> what kind of problem would that solve, that isn't better solved at
> the application level?
There are several testing and debugging tools where devices are
selected not by their capabilities but by their identity.
It would certainly be possible to add code to lookup devices by
their GUID or name, but having udev create a bunch of symlinks
is much simpler.
Regards,
Clemens
prev parent reply other threads:[~2012-07-04 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 17:08 [PATCH] udev: persistent FireWire device names Clemens Ladisch
2012-07-04 17:22 ` Kay Sievers
2012-07-04 19:48 ` Clemens Ladisch [this message]
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=4FF49DF4.4080208@ladisch.de \
--to=clemens@ladisch.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).