Mailinglist Archive: opensuse (1239 mails)

< Previous Next >
Re: [opensuse] ssytemd and openSUSE
  • From: Per Jessen <per@xxxxxxxxxxxx>
  • Date: Wed, 19 Jun 2013 08:02:36 +0200
  • Message-id: <kprhht$q9k$>
Anton Aylward wrote:

Per Jessen said the following on 06/18/2013 03:55 PM:
Anton Aylward wrote:

We've been though this before , such as when we made /dev/
generated'. It didn't fit everyone's needs right away. (I'm not
sure it does even now.)

Right now all I see in in
which uses ifup/ifdown and
which maps an Ethernet address to eth0

YMMV - it probably does :-)

Don't hold your breath, in 13.1 we're headed toward
socalled "PredictableNetworkInterfaceNames", such as enp13s0,
enp14s0, enp3s1f0, enp3s1f1, enp6s2 ...

I agree with Cristian.
a) this is a udev issue not a systemd issue

Apologies, I don't how I could have mistaken the two. :-(

b) we don't want special 'suse' hacks on this.

As far as I can make out we can still have deterministic mapping of a
specific ethernet port (card, slot, whatever you want to call it) to
"ethX' for whatever value of X. Deterministic meaning the same on
every boot.

If that is the case, I have no case :-), but as far as I have understood
that is not correct. If you're certain a user can maintain the current
deterministic enumeration of eth0, eth1, eth2 with a minimum of effort,
we can close that report as invalid.

That is a fundamental requirement of a system running as a firewall,
isn't it? That WAN, DMZ, LAN and WLAN wiring match what the ports are
named - every time!

Sure, that's how it works today. See

At that level does it really matter what the nomenclature is?

Yes it does. The network interface names are used for loads of things
outside the system - monitoring, measurement etc. Inside the system
the new naming would mean amending scripts etc. (ref. YaST2 in 13.1M2),
whereas keeping the naming would mean being able to move stuff from one
box to another without having to think about the network naming scheme.

"ethX" is nice but the alternative aren't show stoppers.

I beg to differ. In a working environment of more than one system,
having a mix of ethX and enp13s0, enp14s0, enp3s1f0, enp3s1f1 and
enp6s2 will not work without a significant effort in adapting the rest
of the environment.

Like I said in the bugreport:

The current enumeration of network interfaces ...

1) overall works very well
2) is integrated into everything else
3) corresponds to the style of enumeration we're used to working with
in linux
3a) corresponds to the style of enumeration used by the manufacturer
4) is easy to pronounce
5) is consistent when one is dealing with multiple systems.

We really ought to retain the option for the user to use the existing
scheme of renaming at start up.

Per Jessen, Zürich (22.6°C) - free DNS hosting, made in Switzerland.

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >