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  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]
Date:	Fri, 23 May 2008 14:07:50 +0100
From:	David Woodhouse <>
To:	Jon Masters <>
Cc:	netdev <>
Subject: Re: network interface *name* alias support?

On Wed, 2008-05-21 at 18:47 -0400, Jon Masters wrote:
> I would like to add support for network interface name aliases to the
> kernel. For example, rather than simply "eth0", one might have:
> eth0 -> eth_slot_0_0
> And use either name for device configuration, etc. This should be pretty
> easy, but I would like some comments - in particular, has this been done
> already and I'm missing something?
> Why is this useful? Say, for example that your a manufacturer building
> machines using the latest DMI extension to SMBIOS that allows you to
> specify what the physical ordering of interfaces is. Then, a
> distribution might choose to configure based on the physical slot
> ordering specified by the vendor - allowing for "rip and replace".

Why do you need a given interface to have more than one name? Why not
just assign names according to whatever criteria you care about?
That's entirely a udev problem, surely?


To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists