From: John Haxby <john.haxby@oracle.com>
To: net-tools@lina.inka.de
Cc: Bernd Eckenfels <be-mail2010@lina.inka.de>,
Narendra_K@Dell.com, jengelh@medozas.de,
shemminger@linux-foundation.org, netfilter-devel@vger.kernel.org,
jgarzik@users.sourceforge.net, Charles_Rose@Dell.com,
Matt_Domsch@Dell.com, Shyam_Iyer@Dell.com,
Jordan_Hargrave@Dell.com, Sandeep_K_Shandilya@Dell.com
Subject: Re: [PROPOSAL]: Alias names for network interfaces
Date: Wed, 13 Jan 2010 17:22:32 +0000 [thread overview]
Message-ID: <4B4E0158.4050102@oracle.com> (raw)
In-Reply-To: <20100113110425.GA5095@lina.inka.de>
On 13/01/10 11:04, Bernd Eckenfels wrote:
> Hello,
>
> On Wed, Jan 13, 2010 at 12:17:16PM +0530, Narendra_K@Dell.com wrote:
>
>> The implementation is for char device node solution we proposed earlier.
>> It would be extended to handle the current proposal if it is acceptable.
>>
> For the record: I still dont like the idea to add another namespace (besides
> interface index number and kernel names (possibly renamed)) to network
> devices (especially in usermode), however if nobody else objects I will keep
> quiet and accept the patches.
>
I am less than enthusiastic about the idea as well. I've come across
numerous userspace scripts and whatnot that have enough trouble with the
default route not being through "eth0" let alone anything more
complex. Aliases are going to cause a lot of problems for a lot of
people for little actual gain.
jch
next prev parent reply other threads:[~2010-01-13 17:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDA0A4495861324DA2618B4C45DCB3EE5899AC@blrx3m08.blr.amer.dell.com>
2010-01-12 19:49 ` Re:[PROPOSAL]: Alias names for network interfaces Narendra K
2010-01-13 0:11 ` Jan Engelhardt
2010-01-13 6:47 ` [PROPOSAL]: " Narendra_K
2010-01-13 11:04 ` Bernd Eckenfels
2010-01-13 17:22 ` John Haxby [this message]
2010-01-13 17:46 ` Domsch, Matt
2010-01-13 18:11 ` Bernd Eckenfels
2010-01-13 18:21 ` Jan Engelhardt
2010-01-14 8:44 ` Patrick McHardy
2010-01-14 9:35 ` Jan Engelhardt
2010-01-15 19:14 ` Narendra_K
2010-01-18 17:07 ` Marco Innocenti
2010-01-19 17:32 ` Narendra_K
2010-01-19 22:31 ` Stephen Hemminger
2010-01-20 1:02 ` Bernd Eckenfels
2010-01-20 16:42 ` Narendra_K
2010-01-13 17:54 ` Stephen Hemminger
2010-01-13 13:24 ` Patrick McHardy
2010-01-13 13:43 ` Jan Engelhardt
2010-01-13 16:27 ` Stephen Hemminger
2010-01-13 17:00 ` Narendra_K
2010-01-14 8:41 ` Patrick McHardy
2009-12-17 13:54 Narendra_K
2009-12-17 14:48 ` Jan Engelhardt
2009-12-18 2:02 ` Bernd Eckenfels
2009-12-18 13:19 ` Narendra_K
2009-12-18 13:42 ` Jan Engelhardt
2009-12-18 14:02 ` Domsch, Matt
2009-12-18 14:08 ` Domsch, Matt
2009-12-18 14:15 ` Jan Engelhardt
2009-12-20 0:12 ` Jordan_Hargrave
2009-12-18 17:38 ` Stephen Hemminger
2009-12-21 17:28 ` Narendra_K
2009-12-21 17:36 ` Stephen Hemminger
2009-12-23 17:11 ` Narendra_K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B4E0158.4050102@oracle.com \
--to=john.haxby@oracle.com \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=Sandeep_K_Shandilya@Dell.com \
--cc=Shyam_Iyer@Dell.com \
--cc=be-mail2010@lina.inka.de \
--cc=jengelh@medozas.de \
--cc=jgarzik@users.sourceforge.net \
--cc=net-tools@lina.inka.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).