Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750913AbXBKVlr (ORCPT ); Sun, 11 Feb 2007 16:41:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750917AbXBKVlr (ORCPT ); Sun, 11 Feb 2007 16:41:47 -0500 Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:52274 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1750913AbXBKVlq (ORCPT ); Sun, 11 Feb 2007 16:41:46 -0500 Date: Sun, 11 Feb 2007 13:41:45 -0800 (PST) Message-Id: <20070211.134145.48809485.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 From: David Miller In-Reply-To: <45CF6C6A.1090506@shaw.ca> References: <45CF6C6A.1090506@shaw.ca> X-Mailer: Mew version 5.1.52 on Emacs 21.4 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 790 Lines: 18 From: Robert Hancock 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/