On Sun, Apr 18, 2010 at 23:08, Marco d'Itri <m...@linux.it> wrote: >> On Apr 18, Mario 'BitKoenig' Holbe <mario.ho...@tu-ilmenau.de> wrote: >> > KERNEL=="audio", NAME="%k0", SYMLINK+="%k" >> Nowadays this is considered bad, accordingly to the upstream maintainer >> you should not change the kernel name of a device. > > $ grep -rl 'NAME=[^=]' /etc/udev/rules.d /lib/udev/rules.d > /etc/udev/rules.d/70-persistent-net.rules
NAME for network devices is fine. They also rename the kernel device. > /etc/udev/rules.d/00-local.rules If this specifies a name different than the kernel device name, it is something that should be fixed. > /lib/udev/rules.d/75-persistent-net-generator.rules NAME for network devices is fine, as mentioned. > /lib/udev/rules.d/55-dm.rules Device-mapper is work-in-progress, and probably just uses NAME="" which is ok. (should still not be done that way, but it does not matter here). > /lib/udev/rules.d/50-udev-default.rules It's probably just for support of older kernels, or for deprecated subsystems drivers like "ieee1394", which need to be replaced by "firewire". There should be no rule that specifies a name that is different from the kernel device name. > Apart from my own rules this seems to be quite a common behaviour. Swapping plain kernel-defined names with symlinks is not supported. It may work, but the behavior is undefined. Recent kernels provide *all* device node names, and with devtmpfs they also manage their creation and deletion. On recent systems, udev is only expected to manage additional symlinks and the permissions of the kernel-created device node. > Well, I think moving device nodes forth and back in the /dev tree is > quite common behavior Upstream udev does not really support this. Kernel device names are defined (and optionally created and deleted) by the kernel these days. Thanks, Kay -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
