Bug#398837: Also, persistent naming for interfaces...

2007-01-03 Thread Andreas Henriksson
On Sun, Dec 31, 2006 at 05:41:05PM +0100, Loïc Minier wrote: > There's already something, which is the IF_VLAN_RAW_DEVICE > (vlan_raw_device in /e/n/interfaces) setting. Ah! Thanks for pointing this out. Even though I have poked at ifupdown internals the way to pass environment variables to the

Bug#398837: Also, persistent naming for interfaces...

2006-12-31 Thread Loïc Minier
On Thu, Dec 28, 2006, Andreas Henriksson wrote: > It would be nice if there where some way that the if-pre-up.d/vlan > script could catch the setup rather then relying on the eth-name (when > using that vlan layout). Btw, I haven't tested if this even works with > the vconfig utility. There's alr

Bug#398837: Also, persistent naming for interfaces...

2006-12-28 Thread Andreas Henriksson
The reported "wlan" problem (which I personally don't agree with since mainline wlan drivers use the eth namespace, and out of tree drivers aren't something I care about) is also a problem when you use persistent naming for devices (via udev, nameif, ifrename, ...). Usually you want to stay away fr