reassign 412348 udev
severity 412348 important
stop

        Hi,

On Sun, Feb 25, 2007, Christian Hammers wrote:
> Apparently udev, probably due to the infamous
> /etc/udev/rules.d/z25persistent-net renames the interface and thus
> ifupdown can no longer find it. 

 My understanding is that the persistent net rules are about getting a
 fixed name for interfaces when the module loading or detection order
 might result in misnamed interfaces.  I've seen this part of udev
 causing trouble in other cases where multiple interfaces avec the same
 MAC (e.g. madwifi's ath0 / wlan0), and I think this is another case of
 this.  However, VLAN interfaces names are controlled by /proc
 parameters, and hence probably don't need this help from udev.

 Hence, I'm reassigning to udev; @Marco: do you confirm this looks like
 an udev bug and it should not attempt to rename VLAN interfaces?  Or
 perhaps it tries to rename them to the wrong name and could rename them
 properly?

 (You're welcome to reassign it back to vlan if you think it can
 implement a better fix.)

 I expect this to break vlan support during upgrades after the first
 reboot, so this bug might be serious, but since it's the first one and
 I don't completely understand how udev is supposed to handle this, I'm
 leaving this at severity "important".

   Bye,
-- 
Loïc Minier <[EMAIL PROTECTED]>

Reply via email to