Mailinglist Archive: opensuse (1239 mails)

< Previous Next >
Re: [opensuse] ssytemd and openSUSE
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
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.

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!

At that level does it really matter what the nomenclature is?
"ethX" is nice but the alternative aren't show stoppers.

We succeed only as we identify in life, or in war, or in anything else, a single overriding objective, and make all other considerations bend to that one objective.
Dwight D. Eisenhower, speech, April 2, 1957
How long did the whining go on when KDE2 went on KDE3?

The only universal constant is change. If a species can not adapt it
goes extinct. That's the law of the universe, adapt or die.
-- Billie Walsh, May 18 2013
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >