All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Moore <dcm@MIT.EDU>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev rules for new firewire driver stack
Date: Thu, 21 Aug 2008 18:57:05 +0000	[thread overview]
Message-ID: <1219345025.20119.1.camel@dmoore.corp.google.com> (raw)
In-Reply-To: <tkrat.3253e0826700753e@s5r6.in-berlin.de>

On Thu, 2008-08-21 at 20:32 +0200, Stefan Richter wrote:
> David Moore wrote:
> > Yes, I think it was me who originally came up with this symlink script.
> > See here:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id$0770
> > 
> So, to summarize the need of symlink rules:
> 
>    - We don't need symlinks (aliases) for application support,
>      neither type-oriented aliases, nor persistently named aliases.
> 
>    - Symlinks may be needed to fit the firewire device files into a
>      distro's file permissions scheme though.  (This was actually the
>      intent behind redhat/40-redhat.rules, which wasn't apparent to
>      me when I read the rules files out of context.)
> 
> Ergo, there may be distro-specific symlinks but applications/libraries 
> will not rely on any of those.  (Right?)

Yes, exactly right.

-David


      parent reply	other threads:[~2008-08-21 18:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-20 19:39 udev rules for new firewire driver stack Stefan Richter
2008-08-20 20:31 ` David Moore
2008-08-20 20:57 ` Stefan Richter
2008-08-20 21:23 ` David Moore
2008-08-20 22:52 ` Stefan Richter
2008-08-21 18:32 ` Stefan Richter
2008-08-21 18:57 ` David Moore [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=1219345025.20119.1.camel@dmoore.corp.google.com \
    --to=dcm@mit.edu \
    --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.