Re: [PATCH] keep track of network interface renaming

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



David Miller wrote:
From: Jason Lunz <[email protected]>
Date: Sun, 11 Feb 2007 13:27:05 -0500

On Sun, Feb 11, 2007 at 09:55:52AM -0800, David Miller wrote:
This is kernel log clutter.

You can ask the kernel for the list of interfaces, and
use even ethtool to ask what driver each interface is
associated with.

The patch wasn't applied because it really is not necessary.
I disagree completely. I'm working right now on a udev-based system that
does ethernet device renaming. It's quite difficult when working with
udev to tell exactly when and why each interface was renamed, since it's
typically done within initramfs where it's difficult to enable debug
messages. This printk helps immensely.

You can listen on a netlink socket for these events if you
want to see when they occur.

Unfortunately that's not very practical if, as in this case, the renaming is being done from an initramfs. Hiding this information as we do now is rather user-hostile.


There is no need for this log message, it is superfluous.

I think the minimal extra output from this is well worth it. If we care so much about limiting dmesg output, how about getting rid of all those hundreds of "PM: Adding info for" messages in recent kernels..

--
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux