Re: udev naming problems for eth*

2006-01-19 Thread Davide Natalini
Md wrote: udev now can rename the interfaces, because they haven't a name yet. udev still loads the modules, you just have been lucky. This is not a solution in any way. maybe I miss something, but for what I see we don't need udev not to load the modules: we just need they are not loaded *be

Re: udev naming problems for eth*

2006-01-19 Thread Davide Natalini
Md wrote: This reminds me that there should be a list of modules which MUST NOT be added to the initramfs because loading them too early is both useless and as in this case actively harmful. I'm testing this solution: I added a blacklist file in /etc/mkinitramfs/, put "blacklist net-module" lin

Re: udev naming problems for eth*

2006-01-18 Thread Davide Natalini
Philipp Matthias Hahn wrote: udevd uses ioctl(SIOCSIFNAME) to rename the devices. If you drivers are compiled in, the get assigned eth[01] during init, but udev is called much later. Renaming eth0 to eth1 will fail, because there already is an eth1 and vis versa. Consider using another name syste

udev naming problems for eth*

2006-01-18 Thread Davide Natalini
Hi all I'm trying to get static naming for my network interfaces with udev, without success. the system is debian sarge based, with udev version 0.076-6 and kernel 2.6.14-7-686-smp on a P4. the network interfaces are a realtek 8139 integrated in the motherboard (eth0) and a 3com pci (eth1)