netdev - Re: [PATCH] Rename "virtual ethernet device" to "virtual ethernet pair device".

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: <20071106.191906.127144742.davem@davemloft.net>
Date:	Tue, 06 Nov 2007 19:19:06 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	rusty@...tcorp.com.au
Cc:	netdev@...r.kernel.org, xemul@...nvz.org, ebiederm@...ssion.com
Subject: Re: [PATCH] Rename "virtual ethernet device" to "virtual ethernet
 pair device".

From: Rusty Russell <rusty@...tcorp.com.au>
Date: Wed, 7 Nov 2007 14:09:00 +1100

> There are already iSeries and pSeries virtual ethernet drivers called
> veth; calling a local tunnel device "veth" is confusing.
> 
> I didn't rename the module nor the header, to avoid breaking
> documentation and userspace programs respectively.  But I'd really
> like to.  It'd also be nice to mention "containers" somewhere in the
> help text (I'm assuming that's what it's for?).
> 
> Signed-off-by: Rusty Russell <rusty@...tcorp.com.au>

We had a lengthy discussion about the name on netdev.  I'm sorry that
you missed it, and are bringing this back up again so that we have to
discuss it once more.

If anything, the veth naming makes more sense than the IBM device
cases.

And that's why I decreed that last time this came up that the naming
for veth was just fine.
-
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