From: linux-hotplug-devel@digitalride.net
To: linux-hotplug@vger.kernel.org
Subject: can udev SYMLINK{all_partitions} ?
Date: Wed, 08 Sep 2004 19:36:24 +0000 [thread overview]
Message-ID: <20040908193625.26490.h64.wm@smtp.sc0.cp.net> (raw)
I've been using the NAME{all_partitions} syntax successfully for a usb card reader, but I also need a symlink created for each partition as
well. For example, I would like both the normal /dev/sda1,/dev/sda2, etc. AND /dev/usb/cf1,/dev/usb/cf2, etc. accessible. The goal is to
use udev to maintain all the normal kernel names while creating symlinks to more intuitive spots that may be automounted for other users who
don't want to mess with /dev/sdX.
Going out on a limb, I tried the syntax SYMLINK{all_partitions} with several variations (which didn't work) including:
BUS="scsi", KERNEL="sd*", SYSFS{model}="*HS-CF*" ,SYSFS{vendor}="*IN-WIN*", NAME{all_partitions}="%k", SYMLINK{all_partitions}="usb/cf"
BUS="scsi", KERNEL="sd*", SYSFS{model}="*HS-CF*" ,SYSFS{vendor}="*IN-WIN*", NAME{all_partitions}="%k", SYMLINK{all_partitions}="usb/cf%n"
Am I missing an easy way to achieve this, or is someone already working on a SYMLINK{all_partitions} syntax?
Thanks,
Mike
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_idP47&alloc_id\x10808&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
next reply other threads:[~2004-09-08 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 19:36 linux-hotplug-devel [this message]
2004-09-08 22:40 ` can udev SYMLINK{all_partitions} ? 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=20040908193625.26490.h64.wm@smtp.sc0.cp.net \
--to=linux-hotplug-devel@digitalride.net \
--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).