Re: [PATCH] udev: persistent FireWire device names

Kay Sievers <[email protected]>
Newsgroups gmane.linux.hotplug.devel,gmane.linux.kernel.firewire.devel
Message-ID <CAPXgP12EniM+jpMZQ74S=o+74SdugUOUbEfH5Sv1_w+dNvMTCw@mail.gmail.com>
On Wed, Jul 4, 2012 at 7:08 PM, Clemens Ladisch <[email protected]> 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. It's very much like USB, we don't do anything like that for
USB either, because we require the apps to cope with the nature of the
bus, and don't want them to expect predictable device nodes for the
raw access.

There is no legacy to support for firewire, like we need to do for
most other of the persistent stuff. So, what kind of problem would
that solve, that isn't better solved at the application level?

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.