netdev - Re: Network Device Naming mechanism and policy

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: <20090324231448.GA21479@kroah.com>
Date:	Tue, 24 Mar 2009 16:14:48 -0700
From:	Greg KH <greg@...ah.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	david@...g.hm, Dan Williams <dcbw@...hat.com>,
	Patrick McHardy <kaber@...sh.net>,
	Matt Domsch <Matt_Domsch@...l.com>, netdev@...r.kernel.org,
	linux-hotplug@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Network Device Naming mechanism and policy

On Tue, Mar 24, 2009 at 09:02:14PM +0000, Alan Cox wrote:
> > this is convienient for some things, but not for others.
> > 
> > what's unique and reproducable is the discovery order
> 
> Not in the case of things like USB...

Or even PCI.

/me pats his laptop that reassigns PCI device ids randomly every 3rd or so boot.
--
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