From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] allow non-block devices for udevinfo
Date: Wed, 25 Feb 2004 16:31:53 +0000 [thread overview]
Message-ID: <1077726712.1161.20.camel@pim> (raw)
In-Reply-To: <403CACFA.8080308@suse.de>
On Wed, 2004-02-25 at 15:11, Hannes Reinecke wrote:
> Hi all,
>
> with the attached patch to udevinfo it is possible to look also at
> devices in /class which do not provide the 'dev' attribute, e.g. net
> devices.
> Agreed, it is of limited usefulness as it stands, but with it we can
> check devices for consistency with the 'standard' or 'acceptable'
> behaviour re. sysfs. And complain loudly to the driver maintainer if
> they don't (Hi Arnd !).
I don't think, that we should print udev keys for devices that udev
can't handle. It claims that the printed keys are usable in a rule.
I agree that we should check the standard compliance as much as we can,
but I don't think that's the goal of udevinfo. Remember that all
multiline values and values containing nonprintable chars are simply
skipped in the current udevinfo device walk. So nonconformant attributes
are as well not printed.
If you really need it, please make it a separate tool or at least a
different command line option of udevinfo.
Please don't print any attribute we can't use, in the SYSFS{attribute}
format. I expect a lot of legitimate confusion otherwise.
thanks,
Kay
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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-02-25 16:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 14:11 [PATCH] allow non-block devices for udevinfo Hannes Reinecke
2004-02-25 16:31 ` Kay Sievers [this message]
2004-02-28 0:22 ` 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=1077726712.1161.20.camel@pim \
--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).