From: "Thomas Bartosik" <thomas.bartosik@gmx.at>
To: linux-hotplug@vger.kernel.org
Subject: udevadm - argument order question
Date: Mon, 06 Jul 2009 13:20:26 +0000 [thread overview]
Message-ID: <20090706132026.9190@gmx.net> (raw)
consider the following two commands:
udevadm info --attribute-walk --query=all --path=$(udevadm info --query=path --name=/dev/sdb1)
udevadm info --query=all --attribute-walk --path=$(udevadm info --query=path --name=/dev/sdb1)
They produce different results. I don't think this is as expected (at least I did not expect it, tried aome time and thought all the ATTRS fields do not exist anymore since the conversion from udevinfo to udevadm info.. until I found this out!)
Maybe I am wrong, but I think this is a bug or at least an undocumented feature.
Please advise whether I should create a bug report and where.
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
next reply other threads:[~2009-07-06 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 13:20 Thomas Bartosik [this message]
2009-07-06 13:27 ` udevadm - argument order question Kay Sievers
2009-07-06 16:52 ` Dan Nicholson
2009-07-06 22:57 ` 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=20090706132026.9190@gmx.net \
--to=thomas.bartosik@gmx.at \
--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).