Hi Raphaël, TPG and TC
holy, how complicate it's that ! By easy kernel eth0 it is known,
where the problem is, but this, makes at all more complicate ! .. holycrap..
this is something like, it's heavy and much to learn and you mus be an
professional,
before you get there by ...
It's every become more difficulty for the end user to learn, what it is
Linux !
so much can not hold in the brain ... ant there say's ever, hold it so
easy as possible..
this so the new network equipment/establishment , it is an definitive
fail ,
because it is become to huge !
and we should look, to restoration the Drakconfiguration in direction
drakconnect in my opinion , because, the kernel it's the linux, not the
Redhat or Systemd,
so should adjust the Systemd in direction of Linux/Kernel and not other ,
because, it's Linus' Kernel, what it is Linux and not the other way
around ..
so should start the wlan before the normal network , why(?) , because it is
at moment, to be start the wlan behind the nfs.. bur the generally
network should starts
because the others it is in dependencies of the network generally ..
and wireless lan it's nothing else as the cable Lan and the 100 (i have
no 0 forgotten)mbit
on wlan it's coming also ! because we has 100mbit and at moment it's any
handy
more faster as the actually wlan from computer, but it will sure catch
up ! I'm sure !
So it would be beneficial if we adjust the system ever to our
Linuxdistriebution or setting up ever links
if exist in direction eth0-eth10 or more by setting an array for check
up if ethXXX exist
and then setting up an |enp2s0| because, what Redhat or Systemd can do,
can we longer
and use the default kernel device, because, this is the original..
in humble Opinion .. because, the eth0 its the original, but speaks
nothing again,
if we let automatic linking the systemd-thing and make our own thing,
further with eth.
In this direction can we use between enp2s0 for booting and for real
configuration eth0 (also by hand).
But therefore we need an work-arround and an work with it .... facility ...
something like systemd-omv-net-easement.service/target who work before
the network start and linking
the ethXXX and wlanXXX in this direction who system with it works, with
this it is in future possible
to work ever with systemd and update systemd in an easy way by adding
our scripts per automatism ,
because we become in any case more own scripts as we know now.
best regards
Blacky
Am 02.03.2015 um 21:05 schrieb Raphaël Jadot:
For who need more informations about consistent network naming in
systemd
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-Consistent_Network_Device_Naming.html
2015-03-02 18:36 GMT+01:00 symbianflo <[email protected]
<mailto:[email protected]>>:
Il 02/03/2015 14:17, Tomasz Gajc ha scritto:
World is moving forward and systemd guys decided to change
network device naming to help network manager and modem
manager to allow configuring network devices more easily.
Other distro are moving toward this policy so this is not a bug.
other distros already moved on new network dev. naming....
_______________________________________________
OM-Cooker mailing list
[email protected] <mailto:[email protected]>
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
