From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev sysfs %s{filename} not working
Date: Tue, 22 Mar 2005 11:08:26 +0000 [thread overview]
Message-ID: <1111489706.6050.38.camel@localhost.localdomain> (raw)
In-Reply-To: <1111489188.24786.1183.camel@localhost.localdomain>
On Tue, 2005-03-22 at 10:59 +0000, Oliver Comber wrote:
> Hi List,
>
> I'm having a problem creating symbolic links with udev using the %
> s{filename} construct.
>
> I'm using Ubuntu Warty, kernel 2.6.8.1-4-386, udev 0.026-1ubuntu5.
Is that udev version 026?
> I want to name USB devices, specifically printers, according to
> manufacturer and possibly (eventually) serial number.
>
> The rule I'm trying to use is:
> BUS="usb", KERNEL="lp[0-9]*", NAME="usb/%k", SYMLINK="usbdev-%
> s{product}"
>
> The symlink which gets created is:
> lrwxrwxrwx 1 root root 7 Mar 22 10:36 /dev/usbdev- ->
> usb/lp0
>
> My %s{product} bit seems to resolve to an empty string.
What does:
udevinfo -a -p /class/usb/lp0
You can use only the attributes that show up here.
Good luck,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&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 prev parent reply other threads:[~2005-03-22 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 10:59 udev sysfs %s{filename} not working Oliver Comber
2005-03-22 11:08 ` Kay Sievers [this message]
2005-03-22 11:20 ` Oliver Comber
2005-03-22 11:52 ` Kay Sievers
2005-03-22 14:41 ` Oliver Comber
2005-03-23 17:37 ` Oliver Comber
2005-03-28 1:31 ` Kay Sievers
2005-03-31 16:39 ` Oli Comber
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=1111489706.6050.38.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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.