From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 013 release
Date: Thu, 15 Jan 2004 22:40:58 +0000 [thread overview]
Message-ID: <20040115224058.GK22433@kroah.com> (raw)
In-Reply-To: <20040113235213.GA7659@kroah.com>
On Thu, Jan 15, 2004 at 03:32:26PM +0100, Kay Sievers wrote:
> On Thu, Jan 15, 2004 at 05:14:16AM +0100, Kay Sievers wrote:
> > On Wed, Jan 14, 2004 at 01:10:43PM -0800, Greg KH wrote:
> > > On Wed, Jan 14, 2004 at 02:34:26PM -0600, Clay Haapala wrote:
> > > > On Wed, 14 Jan 2004, Chris Friesen spake thusly:
> > > > >
> > > > > Maybe for ones with a matching rule, you could print something like:
> > > > >
> > > > >
> > > > Is the act of printing/syslogging a rule in an of itself?
> > >
> > > No, as currently the only way stuff ends up in the syslog is if
> > > DEBUG=true is used on the build line.
> > >
> > > But it's sounding like we might want to change that... :)
> >
> > How about this in the syslog after connect/disconnect?
> >
> > Jan 15 05:07:45 pim udev[28007]: configured rule in '/etc/udev/udev.rules' at line 17 applied, 'video*' becomes 'video/webcam%n'
> > Jan 15 05:07:45 pim udev[28007]: creating device node '/udev/video/webcam0'
> > Jan 15 05:07:47 pim udev[28015]: removing device node '/udev/video/webcam0'
>
> Here is a slightly better version. I've created a logging.h file and
> moved the debug macros from udev.h in there.
Nice, I've applied this, and made a few tweaks to the build stuff to
make it more like the other build options (USE_LOG instead of just LOG).
thanks,
greg k-h
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-01-15 22:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 23:52 [ANNOUNCE] udev 013 release 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:46 ` Chris Friesen
2004-01-14 19:23 ` Nuno Silva
2004-01-14 21:14 ` Greg KH
2004-01-15 7:48 ` Nuno Silva
2004-01-15 23:03 ` Greg KH
2004-01-14 20:34 ` Clay Haapala
2004-01-14 20:47 ` Chris Friesen
2004-01-14 21:12 ` 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 [this message]
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=20040115224058.GK22433@kroah.com \
--to=greg@kroah.com \
--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).