From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bob Dunlop Subject: Re: [PATCH] libertas: name the network device wlan%d Date: Wed, 12 Aug 2009 08:56:24 +0100 Message-ID: <20090812075624.GC18186@guralp.com> References: <1250000012-25673-1-git-send-email-daniel@caiaq.de> <20090811143401.GD2684@tuxdriver.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Daniel Mack , netdev@vger.kernel.org, Roel Kluin , libertas-dev@lists.infradead.org To: "John W. Linville" Return-path: Received: from b.painless.aaisp.net.uk ([81.187.30.52]:35810 "EHLO b.painless.aaisp.net.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754953AbZHLISx (ORCPT ); Wed, 12 Aug 2009 04:18:53 -0400 Content-Disposition: inline In-Reply-To: <20090811143401.GD2684@tuxdriver.com> Sender: netdev-owner@vger.kernel.org List-ID: > > > > Fix this by calling it wlan%d. > > > I'm fine with changing it, but it isn't really wrong either -- it's > just a name, and afterall in most cases all the user will see is > ethernet frames. > > Comments from the libertas driver crew? Well I've been applying the equivalent of this patch privately since we started using the libertas driver. We build systems with one or two wired Ethernets and then an optional wireless module. A fixed name wlan0 is a lot easier than explaining to a user that the interface might be eth1 or eth2 depending on which model they have, or that eth1 might be wired or wireless. It also simplifies scripts and configuration file handling. I'm sure there are many other solutions for big systems but this is really simple for small boys. -- Bob Dunlop Guralp Systems Limited http://www.guralp.com