All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin P. Fleming" <kpfleming@backtobasicsmgmt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Clarification on /etc/udev/rules.d processing
Date: Wed, 21 Apr 2004 14:20:39 +0000	[thread overview]
Message-ID: <40868337.1070107@backtobasicsmgmt.com> (raw)
In-Reply-To: <4085F187.2070003@backtobasicsmgmt.com>

Kay Sievers wrote:

> No, if NAME is set by a rule, the processing is stopped. No later
> "symlink only" rule will be applied.

Any chance that behavior could be changed? For example, the current udev 
default rules file creates

/dev/device-mapper

for the device mapper control device. However, the recent standard 
location for that is

/dev/mapper/control

It is simple enough to create a SYMLINK rule to create this node, and it 
works fine. However, when using multiple rules files (in 
/etc/udev/rules.d), I'll have to ensure that the file containing my 
SYMLINK rule always gets processed before the one containing the NAME 
rule. I can do that, but it seems an unnecessary restriction.


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id\x1470&alloc_id638&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2004-04-21 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21  3:59 Clarification on /etc/udev/rules.d processing Kevin P. Fleming
2004-04-21 10:09 ` Kay Sievers
2004-04-21 14:20 ` Kevin P. Fleming [this message]
2004-04-21 16:08 ` Marco d'Itri

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=40868337.1070107@backtobasicsmgmt.com \
    --to=kpfleming@backtobasicsmgmt.com \
    --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.