From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 047 release [u]
Date: Tue, 14 Dec 2004 00:46:03 +0000 [thread overview]
Message-ID: <1102985163.14134.25.camel@localhost.localdomain> (raw)
In-Reply-To: <1102783489.12795.20.camel@nosferatu.lan>
On Mon, 2004-12-13 at 21:18 +0200, Martin Schlemmer [c] wrote:
> On Mon, 2004-12-13 at 18:08 +0100, Kay Sievers wrote:
> > On Mon, 2004-12-13 at 18:44 +0200, Martin Schlemmer [c] wrote:
> > > Another quick question ... why was the '-d' switch to udevinfo
> > > removed?
> >
> > The udev db is plaintext now. The -d option was for the binary tdb file,
> > to get an idea whats in there.
> > A dump is just a "cat /dev/.udevdb/*" now. :)
> >
>
> Ah, ok, thanks. Btw, using udevsend as hotplug agent seem to work
> fine, although hal still do not recognise a flash drive if I have
> udev renave the node to /dev/usbfd* ...
>
> PS: you might need something like:
>
> -----
> --- udevinfo.c.orig 2004-12-13 21:15:49.000000000 +0200
> +++ udevinfo.c 2004-12-13 21:16:59.000000000 +0200
> @@ -242,7 +242,7 @@
>
> static int process_options(int argc, char *argv[])
> {
> - static const char short_options[] = "adn:p:q:rsVh";
> + static const char short_options[] = "an:p:q:rsVh";
> int option;
> int retval = 1;
> struct udevice udev;
> @@ -439,7 +439,7 @@
> }
>
> help:
> - printf("Usage: udevinfo [-anpqrdVh]\n"
> + printf("Usage: udevinfo [-anpqrVh]\n"
> " -q TYPE query database for the specified value:\n"
> " 'name' name of device node\n"
> " 'symlink' pointing to node\n"
Thanks, I've applied it to my tree and it will show up with the next
sync.
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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:[~2004-12-14 0:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 18:58 [ANNOUNCE] udev 047 release Greg KH
2004-12-08 19:28 ` Greg KH
2004-12-08 19:46 ` [ANNOUNCE] udev 048 release Greg KH
2004-12-08 21:56 ` Tomasz Kłoczko
2004-12-08 22:05 ` Greg KH
2004-12-08 22:15 ` Kay Sievers
2004-12-08 23:25 ` Tomasz Kłoczko
2004-12-08 22:22 ` Marco d'Itri
2004-12-08 23:56 ` Marco d'Itri
2004-12-09 0:08 ` Mike Frysinger
2004-12-09 21:47 ` Andrew Walrond
2004-12-09 23:25 ` Greg KH
2004-12-10 8:46 ` Andrew Walrond
2004-12-09 21:56 ` Kay Sievers
2004-12-09 22:07 ` Andrew Walrond
2004-12-09 22:18 ` Kay Sievers
2004-12-09 22:24 ` Andrew Walrond
2004-12-09 22:27 ` Kay Sievers
2004-12-09 22:33 ` Andrew Walrond
2004-12-11 16:44 ` [ANNOUNCE] udev 047 release [u] Martin Schlemmer [c]
2004-12-11 17:46 ` Kay Sievers
2004-12-11 17:59 ` Martin Schlemmer [c]
2004-12-13 16:44 ` Martin Schlemmer [c]
2004-12-13 17:08 ` Kay Sievers
2004-12-13 19:18 ` Martin Schlemmer [c]
2004-12-14 0:46 ` Kay Sievers [this message]
2004-12-17 0:08 ` Greg KH
2004-12-17 17:11 ` Martin Schlemmer [c]
2004-12-17 23:32 ` Greg KH
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=1102985163.14134.25.camel@localhost.localdomain \
--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).