netdev - Re: [PATCH] libertas: name the network device wlan%d

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090812075624.GC18186@guralp.com>
Date:	Wed, 12 Aug 2009 08:56:24 +0100
From:	Bob Dunlop <rdunlop@...alp.com>
To:	"John W. Linville" <linville@...driver.com>
Cc:	Daniel Mack <daniel@...aq.de>, netdev@...r.kernel.org,
	Roel Kluin <roel.kluin@...il.com>,
	libertas-dev@...ts.infradead.org
Subject: Re: [PATCH] libertas: name the network device wlan%d

> > 
> > 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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html