From: Oliver Comber <ocomber@cmedltd.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev sysfs %s{filename} not working
Date: Wed, 23 Mar 2005 17:37:39 +0000 [thread overview]
Message-ID: <1111599459.8826.35.camel@localhost.localdomain> (raw)
In-Reply-To: <1111489188.24786.1183.camel@localhost.localdomain>
> >
> > Yeah, we just look at the class device itself and physical device, but
> > do not walk up the all physical devices while searching for the sysfs
> > attribute to apply with a format char. I will see what I can do for a
> > one of the next udev versions.
> > In the meantime this dirty trick may work: "%s{../product}". :)
Excuse the bad form posting over myself, but I've just managed to get
your hack above to work with the latest released sources (056) :
BUS="usb", KERNEL="lp[0-9]*", NAME="usb/%k", SYMLINK="myprinters/%
s{../product}"
gives me free, (almost) unique device naming, without having to write
any device specific udev rules!
The version shipped in Ubuntu Warty - 028 - doesn't support this hack.
Thanks very much!
-Oli
-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register
by 3/29 & save $300 http://ads.osdn.com/?ad_idh83&alloc_id\x15149&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-23 17:37 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
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 [this message]
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=1111599459.8826.35.camel@localhost.localdomain \
--to=ocomber@cmedltd.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.