From: Kay Sievers <kay.sievers@vrfy.org>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Jiri Pirko <jpirko@redhat.com>,
linux1394-devel@lists.sourceforge.net,
linux-hotplug@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Jay Fenlason <fenlason@redhat.com>
Subject: Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
Date: Thu, 21 May 2009 18:43:01 +0200 [thread overview]
Message-ID: <ac3eb2510905210943h109e6cc6o76e9978fe47a6eac@mail.gmail.com> (raw)
In-Reply-To: <4A1565B6.10907@s5r6.in-berlin.de>
On Thu, May 21, 2009 at 16:31, Stefan Richter <stefanr@s5r6.in-berlin.de> wrote:
> Usually I prefer brevity too. Alas, it may not be clear to many people what
> "fw" is supposed to mean. People might associate it with, let's say,
> "firewall" before "firewire" when they deal with networking. However, more
> opinions on this are welcome.
Yeah, common one is also "firmware". I think "firewire" is fine.
> As for practical length restrictions: The kernel's networking core requires
> that these names fit into 15 characters plus trailing \0. I don't have an
> idea whether there are userland components which have even tighter
> restrictions.
>
> Does anybody know of potential trouble in networking tools if interface
> names are 9 or 10 characters long?
I don't think so, stuff at the tools level usually works flawlessly
with "eth0_rename_ren" devices, when things went wrong with renaming
the devices. :)
Kay
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-05-21 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 13:29 [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name Stefan Richter
2009-05-21 13:48 ` Jiri Pirko
2009-05-21 14:31 ` Stefan Richter
2009-05-21 16:43 ` Kay Sievers [this message]
[not found] ` <alpine.DEB.2.01.0905232309400.7424@bogon>
2009-05-24 9:47 ` Stefan Richter
2009-05-25 8:33 ` Matthias Schwarzott
2009-05-25 10:43 ` Stefan Richter
2009-05-25 10:57 ` Kay Sievers
2009-05-21 19:34 ` David Miller
2009-05-21 20:13 ` Stefan Richter
2009-05-21 20:33 ` David Miller
2009-05-21 21:35 ` Stefan Richter
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=ac3eb2510905210943h109e6cc6o76e9978fe47a6eac@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=fenlason@redhat.com \
--cc=jpirko@redhat.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
/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).