From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Greg KH <greg@kroah.com>
Cc: Nuno Silva <nuno.silva@vgertech.com>,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 013 release
Date: Wed, 14 Jan 2004 17:46:46 +0000 [thread overview]
Message-ID: <40058086.5000106@nortelnetworks.com> (raw)
In-Reply-To: 20040114171527.GB5472@kroah.com
Greg KH wrote:
> On Wed, Jan 14, 2004 at 05:15:48AM +0000, Nuno Silva wrote:
>>A sugestion and a question:
>>
>>- Make udev print a /etc/udev/udev.rules line every time a device is
>>found because default behaviour is too silent and "make DEBUG=true" is
>>too noisy.
> Yeah, but what exactly would udev print out? All of the sysfs files in
> the device it found? Would it print it out for every device that comes
> through? Or just for ones that no rule applied to?
Maybe for ones with a matching rule, you could print something like:
udev[1234]: new device found matching rule <blah>, creating device node
<nodename>
For ones that don't match any rules, you could dump out all the info:
udev[1234]: new device found with no matching rules, device info: blah blah
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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
WARNING: multiple messages have this Message-ID (diff)
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Greg KH <greg@kroah.com>
Cc: Nuno Silva <nuno.silva@vgertech.com>,
linux-hotplug-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 013 release
Date: Wed, 14 Jan 2004 12:46:46 -0500 [thread overview]
Message-ID: <40058086.5000106@nortelnetworks.com> (raw)
In-Reply-To: 20040114171527.GB5472@kroah.com
Greg KH wrote:
> On Wed, Jan 14, 2004 at 05:15:48AM +0000, Nuno Silva wrote:
>>A sugestion and a question:
>>
>>- Make udev print a /etc/udev/udev.rules line every time a device is
>>found because default behaviour is too silent and "make DEBUG=true" is
>>too noisy.
> Yeah, but what exactly would udev print out? All of the sysfs files in
> the device it found? Would it print it out for every device that comes
> through? Or just for ones that no rule applied to?
Maybe for ones with a matching rule, you could print something like:
udev[1234]: new device found matching rule <blah>, creating device node
<nodename>
For ones that don't match any rules, you could dump out all the info:
udev[1234]: new device found with no matching rules, device info: blah blah
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2004-01-14 17:46 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 23:52 [ANNOUNCE] udev 013 release Greg KH
2004-01-13 23:52 ` Greg KH
2004-01-14 1:38 ` Frédéric L. W. Meunier
2004-01-14 2:14 ` Jon Smirl
2004-01-14 5:15 ` Nuno Silva
2004-01-14 17:15 ` Greg KH
2004-01-14 17:15 ` Greg KH
2004-01-14 17:46 ` Chris Friesen [this message]
2004-01-14 17:46 ` Chris Friesen
2004-01-14 19:23 ` Nuno Silva
2004-01-14 19:23 ` Nuno Silva
2004-01-14 21:14 ` Greg KH
2004-01-14 21:14 ` Greg KH
2004-01-15 7:48 ` Nuno Silva
2004-01-15 23:03 ` Greg KH
2004-01-15 23:03 ` Greg KH
2004-01-14 20:34 ` Clay Haapala
2004-01-14 20:34 ` Clay Haapala
2004-01-14 20:47 ` Chris Friesen
2004-01-14 20:47 ` Chris Friesen
2004-01-14 21:12 ` Greg KH
2004-01-14 21:12 ` Greg KH
2004-01-14 21:10 ` Greg KH
2004-01-14 21:10 ` Greg KH
2004-01-14 17:27 ` Greg KH
2004-01-15 4:14 ` Kay Sievers
2004-01-15 14:32 ` Kay Sievers
2004-01-15 22:40 ` Greg KH
2004-01-16 2:25 ` Nuno Silva
2004-01-16 3:24 ` Kay Sievers
2004-01-16 3:45 ` Nuno Silva
2004-01-19 20:29 ` Olaf Hering
2004-01-19 20:40 ` Greg KH
2004-01-19 20:44 ` Olaf Hering
2004-01-19 20:50 ` 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=40058086.5000106@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=greg@kroah.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.silva@vgertech.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.