Olaf Hering wrote:
> Keep track about which network interface names were renamed after the
> network device driver printed its banner. Previous kernel names will
> be reused when new interfaces get registerd.
> Recent udev scripts implement a stable kernel device name for network
> interfaces.
> Th
Keep track about which network interface names were renamed after the
network device driver printed its banner. Previous kernel names will
be reused when new interfaces get registerd.
Recent udev scripts implement a stable kernel device name for network
interfaces.
This printk avoids confusion abo
Christoph Hellwig <[EMAIL PROTECTED]> :
[...]
> the about to rename part is really noisy.
Yes.
@@ -730,7 +731,11 @@ int dev_change_name(struct net_device *d
else if (__dev_get_by_name(newname))
return -EEXIST;
else
+ {
-> a cleanup patch may be avoided if th
On Sat, Feb 18, Jeff Garzik wrote:
> Fix Xen network support not to do such stupid stuff...
No Xen due to lack of A20 gates.
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-
On Sun, Feb 19, 2006 at 12:21:20AM +0100, Olaf Hering wrote:
>
> Keep track about which network interface names were renamed after the
> network device driver printed its banner. Example insanity:
>
> honeydew:~ # dmesg| grep -Ew '(eth[0-9]|rename|renamed)'
> e1000: eth0: e1000_probe: Intel(R) PR
On Sun, Feb 19, 2006 at 12:21:20AM +0100, Olaf Hering wrote:
>
> Keep track about which network interface names were renamed after the
> network device driver printed its banner. Example insanity:
>
> honeydew:~ # dmesg| grep -Ew '(eth[0-9]|rename|renamed)'
> e1000: eth0: e1000_probe: Intel(R) PR
On Sat, Feb 18, Andrew Morton wrote:
> What caused all that renaming? If it was userspace-initiated then perhaps
> we should display current->comm too?
Its udev, or nameif. Some apps (and worse: lusers!) expect stable
network device names. They cant be bothered to name them foo and bar and
be d
Olaf Hering <[EMAIL PROTECTED]> wrote:
>
> honeydew:~ # dmesg| grep -Ew '(eth[0-9]|rename|renamed)'
> e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection
> e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection
>
Keep track about which network interface names were renamed after the
network device driver printed its banner. Example insanity:
honeydew:~ # dmesg| grep -Ew '(eth[0-9]|rename|renamed)'
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
e1000: eth1: e1000_probe: Intel(R) PRO/1000 Net
