From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott James Remnant Date: Mon, 11 Aug 2008 17:40:31 +0000 Subject: Re: default udev rules Message-Id: <1218476431.14932.49.camel@quest> MIME-Version: 1 Content-Type: multipart/mixed; boundary="=-v73VILFqKeTZRk9CYMiG" List-Id: References: <1218277281.31266.32.camel@lgn.site> In-Reply-To: <1218277281.31266.32.camel@lgn.site> To: linux-hotplug@vger.kernel.org --=-v73VILFqKeTZRk9CYMiG Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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: > >=20 > > > Sure, but how would we handle the bugs we create by renaming: > > > /sys/class/input/mouse0/ > > > to > > > /sys/class/input/input!mouse0/ > > >=20 > > Why would we have any bugs? >=20 > 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. >=20 Shouldn't HAL be using the DEVNAME from udev anyway? Otherwise it would break today if someone wrote a udev rule. Is there any particular reason that the kernel couldn't include DEVNAME in the uevent for things like mouse0? add /class/input/mouse0 DEVNAME=3Dinput/mouse0 Scott --=20 Scott James Remnant scott@canonical.com --=-v73VILFqKeTZRk9CYMiG Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBIoHmPSnQiFMl4yK4RAgT2AKCbOkSIGrzHH0yd69qU/+XvtU3hpACcCwDG m8BYLBHR7dHwABVJWukGmX0= =RroI -----END PGP SIGNATURE----- --=-v73VILFqKeTZRk9CYMiG--