Bug 372371 – sys-fs/udev can be installed on a system running a kernel that does not meet upstream requirements

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Dmitri Bogomolov 2011-06-20 14:05:35 UTC]

I have installed =sys-fs/udev-171-r1 in system with kernel 2.6.31.

Reproducible: Always




This messages are in /var/log/syslog after booting:

Jun 20 09:03:38 smb /etc/init.d/udev-mount[3407]: Your kernel is too old to work with this version of udev.
Jun 20 09:03:38 smb /etc/init.d/udev-mount[3413]: Current udev only supports Linux kernel 2.6.32 and newer.
Jun 20 09:03:38 smb /etc/init.d/udev-mount[3310]: ERROR: udev-mount failed to start
Jun 20 09:03:38 smb /etc/init.d/udev[3311]: ERROR: cannot start udev as udev-mount would not start

[Comment 1 William Hubbs 2011-06-20 18:39:01 UTC]

The requirement for linux-2.6.32 is from upstream, so I recommend
that you upgrade your kernel.

[Comment 2 Dmitri Bogomolov 2011-06-20 19:30:04 UTC]

(In reply to comment #1)
> The requirement for linux-2.6.32 is from upstream, so I recommend
> that you upgrade your kernel.

I have upgraded. The question is why ebuild doesn't die when trying to emerge on system with older kernel?

[Comment 3 William Hubbs 2011-06-20 20:37:27 UTC]

(In reply to comment #2)
> I have upgraded. The question is why ebuild doesn't die when trying to emerge
> on system with older kernel?

This is actually a good question.

Zzam, why do we not die when the version of udev being merged requires a kernel that is newer than the running kernel?

[Comment 4 William Hubbs 2012-03-22 01:16:57 UTC]

The answer for this is that it is possible to build udev on a machine
that is different from the one where it will run.
Think of a build host building binary packages for multiple machines for
example.