[ANNOUNCE] udev 167 release

[ANNOUNCE] udev 167 release

[Kay Sievers]

Here comes a new udev version. Thanks to all who have contributed to
this release.

The tarball can be found here:
 ftp://ftp.kernel.org/pub/linux/utils/kernel/hotplug/

The development repository can be found here:
 http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=summary

The ChangeLog can be found here:
 http://www.kernel.org/git/?p=linux/hotplug/udev.git;a=blob;hb=HEAD;f=ChangeLog

udev 167
====
Bugfixes.

The udev runtime data moved from /dev/.udev/ to /run/udev/. The
/run mountpoint is supposed to be a tmpfs mounted during early boot,
available and writable to for all tools at any time during bootup,
it replaces /var/run/, which should become a symlink some day.

If /run does not exist, or is not writable, udev will fall back using
/dev/.udev/.

On systemd systems with initramfs and LVM used, packagers must
make sure, that the systemd and initramfs versions match. The initramfs
needs to create the /run mountpoint for udev to store the data, and
mount this tmpfs to /run in the rootfs, so the that the udev database
is preserved for the udev version started in the rootfs.

The command 'udevadm info --convert-db' is gone. The udev daemon
itself, at startup, converts any old database version if necessary.

The systemd services files have been reorganized. The udev control
socket is bound by systemd and passed to the started udev daemon.
The udev-settle.service is no longer active by default. Services which
can not handle hotplug setups properly need to actively pull it in, to
act like a barrier. Alternatively the settle service can be unconditionally
'systemctl'enabled, and act like a barrier for basic.target.

The fstab_import callout is no longer built or installed. Udev
should not be used to mount, does not watch changes to fstab, and
should not mirror fstab values in the udev database.

udev 166
====
Bugfixes.

New and updated keymaps.

Re: [ANNOUNCE] udev 167 release

[Gabor Z. Papp]

* 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]?

Re: [ANNOUNCE] udev 167 release

[Kay Sievers]

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]?

Seems your dmesg needs to be fixed to recognize full syslog prefixes.

Userspace uses proper facility values now, for dmesg, syslog, the
admin, to be able to properly distinguish kernel messages from
userspace-injected ones.

Udev, and a few other common early-boot tools which write to the
kernel buffer added such facility value. For udev it's LOG_DAEMON
which is 3, the log level is 6, so the prefix <30> is (3*8)+6.

The kernel pretty-print part is here:
  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;hù90c8d9cde929cbc575098e825d7c29d9f45054

Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [ANNOUNCE] udev 167 release

[Karel Zak]

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

Re: [ANNOUNCE] udev 167 release

[Gabor Z. Papp]

* Karel Zak <kzak@redhat.com>:

| > > what is/mean <30> before udev[1589]?

| I'm not able reproduce this problem on Fedora-15.

$ dmesg -r | grep udev
<4><30>udev[1144]: starting version 167

In this case my syslog-ng 2.1.4 is the ancient/too old?

Thanks and sorry for the noise.

Re: [ANNOUNCE] udev 167 release

[Kay Sievers]

On Tue, Apr 5, 2011 at 20:45, Gabor Z. Papp <gzp@papp.hu> wrote:
> * Karel Zak <kzak@redhat.com>:
>
> | > > what is/mean <30> before udev[1589]?
>
> | I'm not able reproduce this problem on Fedora-15.
>
> $ dmesg -r | grep udev
> <4><30>udev[1144]: starting version 167
>
> In this case my syslog-ng 2.1.4 is the ancient/too old?

No, that looks fine, missed that because I'm used to see timestamps
the kernel adds. They are in-between the two prefixes then.

It's expected behavior for old kernels. Older kernels do not recognize
the multi-digit prefix, and adds another default prefix, it's just
some noise to ignore.

We patched the kernel already to do the right thing now. See the link
in the earlier mail.

Kay