netdev - Re: network interface *name* alias support?

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: <1211569893.11907.39.camel@perihelion>
Date:	Fri, 23 May 2008 15:11:33 -0400
From:	Jon Masters <jonathan@...masters.org>
To:	Rick Jones <rick.jones2@...com>
Cc:	"Kok, Auke" <auke-jan.h.kok@...el.com>,
	Jan Engelhardt <jengelh@...ozas.de>, johnathan@...masters.org,
	netdev@...r.kernel.org, dwmw2@...radead.org
Subject: Re: network interface *name* alias support?

On Fri, 2008-05-23 at 15:06 -0400, Jon Masters wrote:

> My intention is to also allow for:
> 
> ifcfg-slot_<whatever>
> 
> Where the configuration is based entirely upon what vendor <XYZ> says is
> the first, second, or third card. Then, those who want to use the older
> names can continue to do so, but those who prefer to base their
> configuration upon the order the vendor states, can do so.

I'm aware there are other ways to achieve this than having udev assign
an alias on boot, but I think the alias approach is particularly clean.

Jon.


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