From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: devfs is dead, let's move on
Date: Thu, 07 Jul 2005 12:44:07 -0700 [thread overview]
Message-ID: <pan.2005.07.07.19.44.05.481038@cox.net> (raw)
In-Reply-To: 1120744545.6560.18.camel@lycan.lan
Martin Schlemmer posted <1120744545.6560.18.camel@lycan.lan>, excerpted
below, on Thu, 07 Jul 2005 15:55:45 +0200:
> Lastly on an unrelated note ... I have a rule:
>
> -----
> # cat /etc/udev/rules.d/40-dm.rules
> KERNEL="dm-[0-9]*", PROGRAM="/sbin/devmap_name %M %m", NAME="mapper/%c", SYMLINK="%c"
> -----
>
> And in theory it should be the last rule to set the name ... however the
> default one in 50-udev.rules overrides it, and I have to add
> OPTIONS="last_rule"
Why would a rule applied in 40-x.rules be expected to stick when
50-x.rules runs after it and has a conflicting rule?
Change the 40- to 60- and it should work. Of course, you are already
using another alternative, the last_rule option.
There's a third option that /might/ work, as well, according to the
documentation (which is fresh in my mind due to bug 98175, udev-061's
user/group mixups, today). You could try replacing the NAME= with NAME:=.
According to the documentation, the := assignment cannot be overwritten,
so that should make your name stick, with newer udevs, anyway. I think
that functionality is rather new, tho, and may not be in stable versions.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-07 19:50 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 22:46 [gentoo-dev] devfs is dead, let's move on Greg KH
2005-07-06 23:04 ` Greg KH
2005-07-06 23:06 ` Roy Marples
2005-07-06 23:16 ` Greg KH
2005-07-07 0:35 ` Mike Frysinger
2005-07-07 9:34 ` Henrik Brix Andersen
2005-07-07 13:55 ` Martin Schlemmer
2005-07-07 19:44 ` Duncan [this message]
2005-07-07 20:06 ` [gentoo-dev] " Martin Schlemmer
2005-07-07 20:19 ` [gentoo-dev] " Duncan
2005-07-07 20:52 ` [gentoo-dev] " Greg KH
2005-07-07 23:22 ` Martin Schlemmer
2005-07-08 17:06 ` Greg KH
2005-07-08 18:16 ` Stephen Bennett
2005-07-08 18:36 ` Martin Schlemmer
2005-07-08 18:43 ` Martin Schlemmer
2005-07-07 14:18 ` Chris Gianelloni
2005-07-08 17:12 ` Greg KH
2005-07-09 1:00 ` Georgi Georgiev
2005-07-09 2:31 ` Greg KH
2005-08-01 22:14 ` Greg KH
2005-08-01 23:23 ` Kumba
2005-08-01 23:32 ` Greg KH
2005-08-01 23:40 ` Kumba
2005-08-01 23:56 ` Greg KH
2005-07-07 17:39 ` Georgi Georgiev
2005-07-08 17:15 ` Greg KH
2005-07-07 19:52 ` John Mylchreest
2005-07-07 20:49 ` Greg KH
2005-07-09 3:56 ` Kumba
2005-07-09 4:42 ` Greg KH
2005-07-09 5:22 ` Kumba
2005-07-08 17:49 ` Michiel de Bruijne
2005-07-08 22:25 ` Greg KH
2005-07-08 22:46 ` Michiel de Bruijne
2005-07-08 23:35 ` Martin Schlemmer
2005-07-09 0:44 ` Michiel de Bruijne
2005-07-09 0:58 ` Martin Schlemmer
2005-07-09 2:28 ` Greg KH
2005-07-09 18:34 ` Richard Fish
2005-07-09 18:50 ` Philippe Trottier
2005-07-11 7:47 ` Martin Schlemmer
2005-07-12 22:08 ` Mike Frysinger
2005-07-13 9:00 ` Martin Schlemmer
2005-07-13 12:55 ` Mike Frysinger
2005-07-13 14:44 ` Richard Fish
2005-07-15 23:37 ` Carlos Silva
2005-07-17 13:24 ` Greg KH
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=pan.2005.07.07.19.44.05.481038@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.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