On Mon, 2008-08-11 at 18:40 +0100, Scott James Remnant wrote: > On Mon, 2008-08-11 at 19:24 +0200, Kay Sievers wrote: > > > On Mon, 2008-08-11 at 18:08 +0100, Scott James Remnant wrote: > > > On Mon, 2008-08-11 at 19:00 +0200, Kay Sievers wrote: > > > > > > > Sure, but how would we handle the bugs we create by renaming: > > > > /sys/class/input/mouse0/ > > > > to > > > > /sys/class/input/input!mouse0/ > > > > > > > Why would we have any bugs? > > > > Because we change many device names in sysfs to be different from today. > > I don't think we can do that. Current HAL, and all sorts of simpler > > stuff would just stop working. > > > Shouldn't HAL be using the DEVNAME from udev anyway? Otherwise it would > break today if someone wrote a udev rule. It's doing that, it does not guess /dev names, but classifies devices by its name, which we would change. > Is there any particular reason that the kernel couldn't include DEVNAME > in the uevent for things like mouse0? > > add /class/input/mouse0 > DEVNAME=input/mouse0 It could, possibly, but then we get all the devfs and "policy in kernel" discussions back, if we add such a thing. :) 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
