From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-kernel@vger.kernel.org
Subject: Re: udev: Inconsistency between %b and %p?
Date: Thu, 06 Sep 2007 23:59:10 +0200 [thread overview]
Message-ID: <fbpsso$6bh$1@sea.gmane.org> (raw)
In-Reply-To: <jelkbjfovn.fsf@sykes.suse.de>
Andreas Schwab wrote:
> Manuel Reimer <Manuel.Spam@nurfuerspam.de> writes:
>
>> For me, this looks like a bug, or am I wrong?
>
> It's a feature. It's documented.
man udev says:
| The name of the device matched while searching the devpath upwards
| for SUBSYSTEMS, KERNELS, DRIVERS and ATTRS.
What exactly does this mean?
Why should anyone need the name of a device, he didn't search for?
Could someone give me an example, where someone may be interested in an
device name of an device, he just used, to narrow his rule to the one
device, he is looking for.
Yours
Manuel
next prev parent reply other threads:[~2007-09-06 21:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 15:33 udev: Inconsistency between %b and %p? Manuel Reimer
2007-09-06 15:57 ` Andreas Schwab
2007-09-06 21:05 ` Manuel Reimer
2007-09-06 21:46 ` Andreas Schwab
2007-09-06 21:59 ` Manuel Reimer [this message]
2007-09-07 1:03 ` Kay Sievers
2007-09-11 14:11 ` Manuel Reimer
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='fbpsso$6bh$1@sea.gmane.org' \
--to=manuel.spam@nurfuerspam.de \
--cc=linux-kernel@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