On Jan 16, Lionel Elie Mamane <[EMAIL PROTECTED]> wrote: > - the udev package could ship a different > z45_persistent-net-generator.rules, that does not assume uniqueness > of MAC addresses (as suggested by Ard) _and_ leaves vlan interfaces > alone. (If they are renamed at all, the ifupdown plugin in the vlan > package gets confused in all cases.) Stupid idea, as usual the people who know nothing about how udev works are the ones trying to "fix" it.
> Any other idea? udev willing to do that, maybe after a wider > discussion on debian-devel or something like that? Not going to happen. This idea has been shot down multiple times in other contexts, so please do not waste my and your time by advocating it. > - the udev package ships a different > z45_persistent-net-generator.rules, that does not assume uniqueness > of MAC addresses, but does not treat vlan interfaces interfaces > specially either. See above. > - the vlan package could ship a z19_vlan that would preempt > z20_persistent-net.rules by specifying that vlan interfaces should > keep their kernel name. This wold be stupid too, but I could not prevent it. > and then I realised that "true" interfaces have PHYSDEVPATH, > PHYSDEVBUS and PHYSDEVDRIVER in their environment. So we can use: This is what DRIVERS=="?*" is for. I have a better idea: what about finding out why on some systems DRIVERS has a value even for VLAN interfaces and then fixing the reason which causes this (the kernel, I suppose)? > In all cases, it would be good if vlan mentioned this situation in its > README.Debian. Maybe it's better to spend time fixing the bug instead of documenting it. -- ciao, Marco
signature.asc
Description: Digital signature
