On Fri, Jan 30, 2009 at 06:35, Soh Kam Yung <sohkamyung@xxxxxxxxx> wrote: > On Fri, Jan 30, 2009 at 11:03 AM, Kay Sievers <kay.sievers@xxxxxxxx> wrote: >> On Fri, Jan 30, 2009 at 01:43, Soh Kam Yung <sohkamyung@xxxxxxxxx> wrote: >>> >>> I did try NAME="", but that also didn't seem to work. >>> >>> BTW, I'm using udev-135. >>> >> >> Oh, I think you've found a bug in recent udev versions, since we use >> the new rules engine. >> >> I fixed it in the git repo: >> http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=647f7c49e8ddfbbe2afd9545484a3ad936f438e9 >> >> It will be part of udev version 138. > > That's good news for udev. > > Unfortunately, it may not be good news to me. I'm 'stuck' with using > kernel 2.6.21.1 on my embedded system. The README for udev-136 says > that 2.6.22 is required for reliable operation (which is why I'm using > udev-135). > > Can I safely used udev-138 (when released) or should I try to apply > the patch to udev-135? You can do either way. Creating device nodes and running programs works with much older kernels. Only "advanced" operations are not supported with older kernels, like libudev's DEVTYPE support, and some rather special wildcard device lookups. It sounds, you will not use that "advanced" stuff anyway. :) 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
