From: jacky.fong@utoronto.ca
To: linux-hotplug@vger.kernel.org
Subject: SYMLINK assignment in udev rules file
Date: Wed, 21 Dec 2011 18:47:48 +0000 [thread overview]
Message-ID: <20111221134748.0ef205924g080k8g@webmail.utoronto.ca> (raw)
Hi,
I need some help with udev rule writing. I am having difficulty
understanding the description for the SYMLINK assignment key
(http://manpages.ubuntu.com/manpages/oneiric/man7/udev.7.html). The
manpage
says,
"In case multiple devices claim the same name, the link always
points to the device with the highest link_priority."
How can you have multiple devices that claim the same name? It is said
in the description section of the manpage that "the kernel usually
just assigns unpredictable device names based on the order of
discovery." E.g. sda, sdb,...
The only situation I could think of where multiple devices claiming
the same name is when the user decides to do NAME="sda", which is not
recommended, as noted in the manpage.
Btw, none of the device file nodes are created in the filesystem
(/dev) at this
point right? Since filenames must be unique under a directory, I just
don't see the case where "multiple devices claim the same name".
Thanks,
Jacky
reply other threads:[~2011-12-21 18:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111221134748.0ef205924g080k8g@webmail.utoronto.ca \
--to=jacky.fong@utoronto.ca \
--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