netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: Patrick McHardy <kaber@trash.net>,
	Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
	Stephen Hemminger <shemminger@vyatta.com>,
	netdev@vger.kernel.org
Subject: Re: Vlan interface nuisance
Date: Mon, 02 Mar 2009 22:53:40 -0800	[thread overview]
Message-ID: <49ACD3F4.8080700@candelatech.com> (raw)
In-Reply-To: <20090303064149.GA4154@ff.dom.local>

Jarek Poplawski wrote:
> Yes, very interesting arguments for another disussion... But if we're
> talking about naming than you seem to ignore what Lennart, Ben, Denys
> and probably Stephen said about their preferred way, and I think it
> matters, because if they had problems with understanding this change
> I can only imagine what "common users" would say without knowing all
> this technical rationale (which IMHO is disputable too - names  are
> for people).
>   
I like my own naming scheme, and I use it by specifying the name when
creating the vlan using 'ip'.  It would have been nice (IMO) to have the
dev.vid naming be default from the beginning, but since it wasn't, it would
cause more harm than good to change it now.

So, I'm NOT arguing for changing the behaviour, though anything that can
document the features of 'ip' better and make it more obvious you can set
the name upon creation should help people...

Ben

> Jarek P.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


-- 
Ben Greear <greearb@candelatech.com> 
Candela Technologies Inc  http://www.candelatech.com



      reply	other threads:[~2009-03-03  6:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02  4:47 Vlan interface nuisance Stephen Hemminger
2009-03-02  4:57 ` David Miller
2009-03-02  5:05   ` Stephen Hemminger
2009-03-02  5:28     ` David Miller
2009-03-02  9:44       ` Patrick McHardy
2009-03-02  6:50     ` Herbert Xu
2009-03-02  7:15       ` Stephen Hemminger
2009-03-02  7:39         ` Herbert Xu
2009-03-02  9:45           ` Patrick McHardy
2009-03-02  9:57             ` David Miller
2009-03-02 17:20 ` Lennart Sorensen
2009-03-02 18:51   ` Jarek Poplawski
2009-03-02 18:56     ` Ben Greear
2009-03-02 19:06       ` Jarek Poplawski
2009-03-02 19:23         ` Denys Fedoryschenko
2009-03-02 20:24           ` Jarek Poplawski
2009-03-02 21:52         ` Patrick McHardy
2009-03-02 19:36     ` Lennart Sorensen
2009-03-02 20:07       ` Jarek Poplawski
2009-03-02 21:49     ` Patrick McHardy
2009-03-02 21:51       ` Stephen Hemminger
2009-03-02 21:54         ` Patrick McHardy
2009-03-02 22:30       ` Jarek Poplawski
2009-03-02 23:35         ` Patrick McHardy
2009-03-03  6:41           ` Jarek Poplawski
2009-03-03  6:53             ` Ben Greear [this message]

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=49ACD3F4.8080700@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=jarkao2@gmail.com \
    --cc=kaber@trash.net \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /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).