From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Requirement to customize Linux Network Interface naming Convention
Date: Tue, 4 Aug 2015 21:04:30 -0700 [thread overview]
Message-ID: <20150805040430.GA25360@kroah.com> (raw)
In-Reply-To: <CAJqwu=8rA-1CiBm4snx81c=hJs_V0R0gVuFjUDrHV0Fs2Ddyew@mail.gmail.com>
On Wed, Aug 05, 2015 at 09:24:41AM +0530, Akash Bhatnagar wrote:
> Hi,
>
> We have a requirement to tweak the Linux Network Interface Naming
> conventions so that, it can support names of interfaces with "/" character.
Who is "we"?
And why do you want such a thing?
> For example, ip tuntap add dev fe/1/1 mode tap
>
> With iproute2 it simply shows error as INVALID Argument. What are the
> changes we supposed to do inside Kernel and iproute2 package?
Lots, good luck :)
But first, push back, you should never care what the network interface
name is, that never matters.
greg k-h
next prev parent reply other threads:[~2015-08-05 4:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-05 3:54 Requirement to customize Linux Network Interface naming Convention Akash Bhatnagar
2015-08-05 4:04 ` Greg KH [this message]
2015-08-05 14:39 ` Akash Bhatnagar
2015-08-05 14:50 ` Greg KH
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=20150805040430.GA25360@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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).