lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ac3eb2510905210943h109e6cc6o76e9978fe47a6eac@mail.gmail.com>
Date:	Thu, 21 May 2009 18:43:01 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	Jiri Pirko <jpirko@...hat.com>,
	linux1394-devel@...ts.sourceforge.net,
	linux-hotplug@...r.kernel.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, Jay Fenlason <fenlason@...hat.com>
Subject: Re: [PATCH] ieee1394: eth1394: use "firewire%d" instead of "eth%d" as 
	interface name

On Thu, May 21, 2009 at 16:31, Stefan Richter <stefanr@...6.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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ