public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hancockr@shaw.ca
Cc: linux-kernel@vger.kernel.org, lunz@falooley.org
Subject: Re: [PATCH] keep track of network interface renaming
Date: Sun, 11 Feb 2007 13:41:45 -0800 (PST)	[thread overview]
Message-ID: <20070211.134145.48809485.davem@davemloft.net> (raw)
In-Reply-To: <45CF6C6A.1090506@shaw.ca>

From: Robert Hancock <hancockr@shaw.ca>
Date: Sun, 11 Feb 2007 13:20:10 -0600

> 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.

Perhaps you have a point, I'll think about this some more.

But on the other hand note that kernel log messages can scroll away
and get lost, so you cannot really rely upon them for gathering
information which is necessary for properly detecting devices
in userspace or anything like that.

  reply	other threads:[~2007-02-11 21:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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
2007-02-11 22:35         ` Tilman Schmidt

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.134145.48809485.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lunz@falooley.org \
    /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