mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: lunz@falooley.org
Cc: olaf@aepfle.de, rol@witbe.net, akpm@osdl.org,
	linux-kernel@vger.kernel.org, rol@as2917.net
Subject: Re: [PATCH] keep track of network interface renaming
Date: Sun, 11 Feb 2007 10:28:52 -0800 (PST)	[thread overview]
Message-ID: <20070211.102852.45510952.davem@davemloft.net> (raw)
In-Reply-To: <20070211182704.GA14021@avocado.homenet>

From: Jason Lunz <lunz@falooley.org>
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.

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

  parent reply	other threads:[~2007-02-11 18:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-11 11:28 2.6.20/2.6.20-rc7 : ethX renumbered Paul Rolland
2007-02-11 12:54 ` [PATCH] keep track of network interface renaming Olaf Hering
2007-02-11 13:29   ` Paul Rolland
2007-02-11 17:55   ` David Miller
     [not found]     ` <20070211182704.GA14021@avocado.homenet>
2007-02-11 18:28       ` David Miller [this message]
2007-02-11 22:35         ` Tilman Schmidt
2007-02-11 13:04 ` 2.6.20/2.6.20-rc7 : ethX renumbered Benoit Boissinot
2007-02-11 13:14   ` Paul Rolland
2007-02-11 13:35     ` Paul Rolland
     [not found] <fa.vON9rghc4zb2B4B1Ub/ZAaRY2v8@ifi.uio.no>
     [not found] ` <fa.EIATc7QlHJ5coYaEARiq54/4h6A@ifi.uio.no>
     [not found]   ` <fa.rECiNcG8qmgC5L7se1aXLWosf4E@ifi.uio.no>
     [not found]     ` <fa./pMesnnnb80P5K2iQYUkxeYCpXA@ifi.uio.no>
2007-02-11 19:20       ` [PATCH] keep track of network interface renaming Robert Hancock
2007-02-11 21:41         ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070211.102852.45510952.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lunz@falooley.org \
    --cc=olaf@aepfle.de \
    --cc=rol@as2917.net \
    --cc=rol@witbe.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome