From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Friesen Date: Wed, 14 Jan 2004 17:46:46 +0000 Subject: Re: [ANNOUNCE] udev 013 release Message-Id: <40058086.5000106@nortelnetworks.com> List-Id: References: <20040113235213.GA7659@kroah.com> <4004D084.1050106@vgertech.com> <20040114171527.GB5472@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Greg KH Cc: Nuno Silva , linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org 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 , creating device node 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