netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: stefanr@s5r6.in-berlin.de
Cc: linux1394-devel@lists.sourceforge.net,
	linux-hotplug@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, fenlason@redhat.com
Subject: Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as interface name
Date: Thu, 21 May 2009 12:34:03 -0700 (PDT)	[thread overview]
Message-ID: <20090521.123403.13286908.davem@davemloft.net> (raw)
In-Reply-To: <tkrat.21c425cc195510c9@s5r6.in-berlin.de>

From: Stefan Richter <stefanr@s5r6.in-berlin.de>
Date: Thu, 21 May 2009 15:29:10 +0200 (CEST)

> Change the initial name of IP-over-1394 networking interfaces from
> "eth[0-9]+" to "firewire[0-9]+".
> 
> This should have been done years ago for the reason mentioned in the
> inline comment.  The naming issue basically prevented acceptance of
> IP networking over 1394 on Linux.
> 
> The future IP-over1394 driver in the newer alternative firewire driver
> stack will use the "firewire%d" format from the start while "eth%d" will
> no longer be used in the new driver.
> 
> Necessary changes in userland:
> 
> People who use the eth1394 driver either have to update their network
> configuration (or instead perhaps respecpective udev interface renaming
> rules) to the new names, or add
> 
>     options eth1394 firewire_interface_name=N
> 
> to /etc/modprobe.conf or /etc/modprobe.d/whatever if they really prefer
> the old names.
> 
> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>

I think the basis for this patch is completely bogus.

Device names are just that, names.  If you want to know "what it is"
or "where it is" you use tools to determine that information.

If you make ethtool's get info command return something useful,
then the user can see that it's a firewire interface and act
accordingly, as can sophisticated confiruation applications.

I am completely against this patch.

  parent reply	other threads:[~2009-05-21 19:34 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
     [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 [this message]
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=20090521.123403.13286908.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=fenlason@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).