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  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:	Sat, 24 May 2008 06:53:17 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...ozas.de>
To:	Jon Masters <jonathan@...masters.org>
cc:	Thomas Graf <tgraf@...g.ch>, Rick Jones <rick.jones2@...com>,
	"Kok, Auke" <auke-jan.h.kok@...el.com>, johnathan@...masters.org,
	netdev@...r.kernel.org, dwmw2@...radead.org
Subject: Re: network interface *name* alias support?


On Saturday 2008-05-24 06:25, Jon Masters wrote:
>
>I guess that would also work quite nicely for what I want to do, but the
>problem is that this will require either:
>
>*). The kernel decodes the DMI extension directly.
>*). We can first inform each device which slot it is in (set the slot).
>
>My intention is to implement whatever seems reasonable, and my reason
>for asking is that I am not a networking maintainer, so I want to know
>what seems reasonable :)

Why are we even looking at slot numbers? I do not think there is any
guarantee that the order of slots as a human would recognize them on
the board must always correspond to a monotonically increasing linear
function.
--
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

Powered by blists - more mailing lists