linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Failed to Create Symlinks ...
Date: Mon, 30 Nov 2009 14:03:23 +0000	[thread overview]
Message-ID: <200911301503.23439.zzam@gentoo.org> (raw)
In-Reply-To: <866c8f7a0911281452g2b8d95f7q4456d4428db66490@mail.gmail.com>

On Sonntag, 29. November 2009, Kay Sievers wrote:
> On Sun, Nov 29, 2009 at 20:15, Matthias Schwarzott <zzam@gentoo.org> wrote:
> > I have a similar issue.
> > the lvm2 package on gentoo installs this udev rule:
> > KERNEL="device-mapper", SYMLINK+="mapper/control"
> >
> > Now udev-147 cries about not being able to create the symlink as
> > kernel-provided name is already set to "mapper/control".
>
> Yes, this is expected, mapper/control is the primary name, and not a
> symlink.
I suggested lvm2 maintainers to change the rule to
KERNEL="device-mapper", NAME="mapper/control"

>
> > So is the only possibility to surpress this warning to adjust the rule to
> > this?
> > KERNEL="device-mapper", NAME="mapper/control"
>
> Looks like, yes. Recent kernels/udev though should not have any rule
> for this. We removed all such rules from the udev default rule set.
>
Sure, but gentoo does aim to support at least not only the newest kernels, but 
udev for now still supports 2.6.27 or even older versions with older udev 
versions.

Is there a way to conditionalize these rules besides shell tricks at boot 
checking kernel versions and discarding some rules/rule files on some 
conditions.

Matthias

  parent reply	other threads:[~2009-11-30 14:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-28 22:52 Failed to Create Symlinks Chris Dellin
2009-11-29 19:04 ` Kay Sievers
2009-11-29 19:15 ` Matthias Schwarzott
2009-11-29 19:20 ` Kay Sievers
2009-11-30 12:37 ` Kay Sievers
2009-11-30 14:03 ` Matthias Schwarzott [this message]
2009-11-30 14:08 ` Matthias Schwarzott
2009-11-30 15:39 ` 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=200911301503.23439.zzam@gentoo.org \
    --to=zzam@gentoo.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).