From: Karel Zak <kzak@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [ANNOUNCE] udev 167 release
Date: Tue, 05 Apr 2011 13:30:31 +0000 [thread overview]
Message-ID: <20110405133031.GB26986@nb.net.home> (raw)
In-Reply-To: <AANLkTi=Ff2rrxHeObMMtasxpHPDkET+UneDr8-n6F89h@mail.gmail.com>
On Thu, Mar 31, 2011 at 12:08:40PM +0200, Kay Sievers wrote:
> On Thu, Mar 31, 2011 at 10:03, Gabor Z. Papp <gzp@papp.hu> wrote:
> > * Kay Sievers <kay.sievers@vrfy.org>:
> >
> > | Here comes a new udev version. Thanks to all who have contributed to
> > | this release.
> >
> > $ dmesg
> > <30>udev[1589]: converting old udev database
> > <30>udev[1590]: starting version 167
> >
> > what is/mean <30> before udev[1589]?
I'm not able reproduce this problem on Fedora-15.
After update to udev-167:
# dmesg -r | grep udev
<6>[ 2.061910] udev[92]: starting version 166
<6>[ 10.884330] udev[362]: starting version 166
<30>[ 3154.877757] udev[1780]: converting old udev database
<30>[ 3154.975428] udev[1780]: starting version 167
'-r' means raw, so <30> prefix is there. Normal dmesg:
# dmesg | grep udev
[ 2.061910] udev[92]: starting version 166
[ 10.884330] udev[362]: starting version 166
[ 3154.877757] udev[1780]: converting old udev database
[ 3154.975428] udev[1780]: starting version 167
# rpm -qf /bin/dmesg
util-linux-2.19-3.fc15.i686
> Userspace uses proper facility values now, for dmesg, syslog, the
> admin, to be able to properly distinguish kernel messages from
> userspace-injected ones.
The dmesg from util-linux supports arbitrary number of digits between
'<' and '>' in the kernel messages.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2011-04-05 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 16:28 [ANNOUNCE] udev 167 release Kay Sievers
2011-03-31 8:03 ` Gabor Z. Papp
2011-03-31 10:08 ` Kay Sievers
2011-04-05 13:30 ` Karel Zak [this message]
2011-04-05 18:45 ` Gabor Z. Papp
2011-04-05 18:54 ` Kay Sievers
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=20110405133031.GB26986@nb.net.home \
--to=kzak@redhat.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).