On Wed, Jan 16, 2008 at 04:16:32PM +0100, Marco d'Itri wrote:
> On Jan 16, Lionel Elie Mamane <[EMAIL PROTECTED]> wrote:
>> 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.

Ah well, yes. Then a solution would be for the automatically generated
/etc/udev/rules.d/z25_persistent-net.rules to have a DRIVERS=="?*"
condition in every line. On some of my machines, it has them, on some
machines it has not. When I add them to the machines that have them
not, it fixes the problem. So a good solution would be for the
automatically generated rules always to have a DRIVERS=="?*"
condition. Why is it not the case that they always have it?

Maybe older versions of udev did not put this condition and the file
is not converted on upgrade?

> 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)?

I am not aware of any system where DRIVERS has a value for VLAN
interfaces.

>> 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.

Sure, if udev will make it so that
/etc/udev/rules.d/z25_persistent-net.rules is always such as it works
out of the box (even if upgrading from older udev versions), then no
documentation necessary. But if there are scenarios (such as upgrades
from sarge or etch) where it will not work out of the box, for example
because udev will not convert an existing
/etc/udev/rules.d/z25_persistent-net.rules (because it would be
afraid of loosing local administrator customisations, for example),
then some documentation is necessary, because the administrator needs
to update /etc/udev/rules.d/z25_persistent-net.rules by hand. Will you
update it automatically on upgrades?

-- 
Lionel



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to