From: Oli Comber <ocomber@cmedltd.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev sysfs %s{filename} not working
Date: Thu, 31 Mar 2005 16:39:24 +0000 [thread overview]
Message-ID: <1112287164.3470.615.camel@localhost.localdomain> (raw)
In-Reply-To: <1111489188.24786.1183.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
On Mon, 2005-03-28 at 03:31 +0200, Kay Sievers wrote:
> On Wed, 2005-03-23 at 17:37 +0000, Oliver Comber wrote:
> > > >
> > > > 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.
>
> I've added something to my tree today. The next udev version will be
> able to do this without the "../".
>
> Kay
Excellent, Cheers Kay! I look forward to trying out the next version.
This should take a lot of load off of cups, sane etc trying to do device
discovery themselves or users struggling to have dependable
names/devices for two or more connected printers (My original
problem ;0) )
Good work! :0)
-Oli
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-03-31 16:39 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
2005-03-28 1:31 ` Kay Sievers
2005-03-31 16:39 ` Oli Comber [this message]
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=1112287164.3470.615.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 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).