From: Yan Seiner <yan@seiner.com>
To: linux-hotplug@vger.kernel.org
Subject: SYMLINK+="xxx" can only be used once
Date: Tue, 27 Feb 2007 16:39:43 +0000 [thread overview]
Message-ID: <45E45ECF.7070103@seiner.com> (raw)
I'd like to know if this is a bug or a feature. I know it's driving me
nuts.
I have a system with 3 sound cards. I need to assign fixed device names
to these cards. I've tried various combinations of module parameters
and I've found the most reliable way is to use udev to symlink the
device names using udev.
Here's the rule I am using:
#Yamaha Corporation YMF-724F
SYSFS{device}="0x000d", SYSFS{vendor}="0x1073", MODE="0660",
NAME="snd/%k", SYMLINK+="soundcard/Yamaha_YMF_724F", SYMLINK+="dsp01"
What happens is that only the last SYMLINK is created. This is
reproducilble; I can turn the order around and the soundcard link will
be created but not the dsp one.
I can't find any examples of multiple SYMLINK creation, so I suspect
this may be a feature, but I don't quite understand why it would be so.
Can anyone shed some light on this?
Thanks,
--Yan
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
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
next reply other threads:[~2007-02-27 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 16:39 Yan Seiner [this message]
2007-02-27 16:50 ` SYMLINK+="xxx" can only be used once Alexander E. Patrakov
2007-02-27 17:11 ` Yan Seiner
2007-02-27 17:54 ` Bryan Kadzban
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=45E45ECF.7070103@seiner.com \
--to=yan@seiner.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 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).