On Fri, Feb 25, 2011 at 18:01, Steffen Sledz <sledz@xxxxxxxxxxxx> wrote: > Am 25.02.2011 17:57, schrieb Kay Sievers: >> On Fri, Feb 25, 2011 at 16:55, Steffen Sledz <sledz@xxxxxxxxxxxx> wrote: >>> inotify_init1 first appeared in Linux 2.6.27 >> >> We depend on that or a more recent kernel for a few other reasons too. >> .27 might be the first on where this udev version compiles, but all >> below .32 is pretty much untested and known to fail during runtime in >> some areas. Let's not fix such compile failures, it is unlikely that >> udev will run properly for other reasons than inotify. > > Hmmm? > > Is there an overview of these reasons? We like/need to use udev-151 (or newer) together with linux 2.6.24. Not really. It's all a moving target in one direction only. We only really support compatibility for newer kernels with old userspace. Old kernels with new userspace are usually not even tested. Support for kernels with the deprecated sysfs layout (CONFIG_SYSFS_DEPRECATED) has been removed a while ago. Some lookup/enumeration features in libudev relies on information in /sys only available in kernels >= .31. Some stuff relies on DEVNAME set by the kernel, which was part of the devtmpfs changes. Udev should run fine on plain tmpfs, but it is also not tested anymore. Also races that happen only with tmpfs don't get fixed anymore. Some changes are visible in the compat rules files: http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=rules/misc/30-kernel-compat.rules;hb=HEAD The same rules applie here, we already dropped stuff here for kernels older than .27. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
