Path: csiph.com!1.us.feeder.erje.net!feeder.erje.net!1.eu.feeder.erje.net!weretis.net!feeder4.news.weretis.net!news.unit0.net!news.panservice.it!bofh.it!news.nic.it!robomod
From: Brian <ad44@cityscape.co.uk>
Newsgroups: linux.debian.user
Subject: Re: network setup
Date: Tue, 13 Dec 2016 22:10:03 +0100
Message-ID: <sO2uJ-683-11@gated-at.bofh.it>
References: <sNgT7-2oS-1@gated-at.bofh.it> <sNi8y-35w-3@gated-at.bofh.it> <sNmYx-5V3-3@gated-at.bofh.it> <sNV9U-1DV-25@gated-at.bofh.it> <sNVtg-1Kh-15@gated-at.bofh.it> <sNVCW-1NI-33@gated-at.bofh.it> <sO1fk-5cf-17@gated-at.bofh.it> <sO1p0-5fY-41@gated-at.bofh.it>
X-Mailbox-Line: From debian-user-request@lists.debian.org  Tue Dec 13 21:03:02 2016
Old-Return-Path: <brian@copernicus.org.uk>
X-Amavis-Spam-Status: No, score=-6.999 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
X-Policyd-Weight: using cached result; rate:hard: -7
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-Backscatter: 123456789
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Mailing-List: <debian-user@lists.debian.org> archive/latest/715260
List-ID: <debian-user.lists.debian.org>
List-URL: <https://lists.debian.org/debian-user/>
List-Archive: https://lists.debian.org/msgid-search/13122016205017.42d4ac69f090@desktop.copernicus.org.uk
Approved: robomod@news.nic.it
Lines: 41
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
X-Original-Date: Tue, 13 Dec 2016 21:02:45 +0000
X-Original-Message-ID: <13122016205017.42d4ac69f090@desktop.copernicus.org.uk>
X-Original-References: <alpine.NEB.2.20.1612111309400.26410@panix1.panix.com> <20161211104708.158cd71a@whynot.keepingdreams.org> <alpine.NEB.2.20.1612111936470.22392@panix1.panix.com> <20161213131811.GA22537@tuxteam.de> <20161213133604.5ysx2lgsgmzqo337@darac.org.uk> <20161213134047.GA23378@tuxteam.de> <20161213194439.GN12628@copernicus.org.uk> <912d6151-2dbf-6ae3-e959-e7b4274530e4@rail.eu.org>
Xref: csiph.com linux.debian.user:175688

On Tue 13 Dec 2016 at 20:48:46 +0100, Erwan David wrote:

> Le 12/13/2016 à 20:44, Brian a écrit :
> > On Tue 13 Dec 2016 at 14:40:47 +0100, tomas@tuxteam.de wrote:
> > 
> >> On Tue, Dec 13, 2016 at 01:36:05PM +0000, Darac Marjal wrote:
> >>
> >> [...]
> >>
> >>> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
> >>> lists three options:
> >>
> >> Thanks!
> > 
> > For someone who has been using Debian for many years the position you
> > expound is understandable and viable to support. Someone who is used to
> > eth0 and wlan0 for interface names is bound to sit up and take notice
> > when they change to something which is strange and doesn't exactly stick
> > in the memory.
> > 
> > But remember new users; does it really matter to them? They have no
> > personal history to point to. As you point out, the engineering
> > advantages are unarguable. And after all, there are three options which
> > can be employed to get something you are not given. That's not bad as
> > things go.
> > 
> 
> Do you think eno167778 will be more useful than eth0 to a new user ?
> (yes I've seen the name for the only NIC of a machine)

It is no more nor more less useful than eth0 in the sense that
networking works for them. Do you think a new user is going to
react in horror to one rather than the other?

My God, why must I  use eno167778, he will say? I must change
this to something I like. connection0 looks good.

And so he can. So where's the problem?

-- 
Brian.