From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udevinfo query
Date: Tue, 27 Jan 2004 07:12:41 +0000 [thread overview]
Message-ID: <20040127071241.GA12286@vrfy.org> (raw)
In-Reply-To: <20040127030511.18446.qmail@web14914.mail.yahoo.com>
On Mon, Jan 26, 2004 at 07:05:11PM -0800, Jon Smirl wrote:
> It would be nice to be able to query for the full path to the node. This would
> make it easier to script things. Instead of "udevinfo -r" and "udevinfo -p
> /class/dri/card0 -q name", I could just do something like "udevinfo -p
> /class/dri/card0 -q fullname" and get back /udev/dri/card0
You don't like man pages, or do you?
-r Print the the udev_root directory. When used
in conjunction with a query for the node name, the
udev_root will be prepended.
/sbin/udevinfo -r -p /sys/class/video4linux/video0 -q name
/udev/video/webcam0
> I tried "udevinfo -p /class/dri/card0 -q name" without udev running. It gives
> the error "device not found in database". udevinfo -r returns "/udev/".
> Shouldn't these messages be changed to indicate that udev is not mounted and
> running?
What do you mean with 'running'?
If you have a database we query it, if you don't have it, we will fail
with "unable to open udev database". That's perfectly ok, I think.
Kay
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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
prev parent reply other threads:[~2004-01-27 7:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 3:05 udevinfo query Jon Smirl
2004-01-27 7:12 ` Kay Sievers [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=20040127071241.GA12286@vrfy.org \
--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 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).