netdev - Re: extended netdevice naming proposal

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: <20101118185225.GB4952@auslistsprd01.us.dell.com>
Date:	Thu, 18 Nov 2010 12:52:25 -0600
From:	Matt Domsch <Matt_Domsch@...l.com>
To:	Rick Jones <rick.jones2@...com>
Cc:	linux-hotplug@...r.kernel.org, netdev@...r.kernel.org,
	narendra_k@...l.com, jcm@...hat.com, notting@...hat.com
Subject: Re: extended netdevice naming proposal

On Thu, Nov 18, 2010 at 10:34:29AM -0800, Rick Jones wrote:
> With the presence of the pci_slot driver to allow association of the PCI 
> address with a "slot name" is encoding such information into the interface 
> name really necessary?

I think so.  1) Dell systems seem not to be able to put information
into pci_slot.  That needs investigation.  2) if it's not in the name,
the user must do the correlation themselves manually.

Thanks,
Matt

-- 
Matt Domsch
Technology Strategist
Dell | Office of the CTO
--
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