Re: The Tragedy Of systemd

Lars Poulsen <lars@cleo.beagle-ears.com> wrote:

But redhat has funding from and obligations to groups that run large
datacenters that need to be managed from control desks based on
parameterized templates, and to support these needs, they built
something that works for that crowd.

And still those server people complain that systemd feels more like
its geared for desktop machines. Noone cares how long it takes to boot
a server, and many server jockeys would love the possibility to turn
off the parallelism of systemd when booting (for reproducibility,
sacrificing speed).

Where is the per-network-device data that used to be in
/etc/sysconfig/network-scripts now? I know I am supposed to use
network-manager, but how does it play with ifconfig and "ip addr" and
"ip route"?

systemd-networkd is an optional alternative to NetworkManager. It does
that job very well for the server and it is very nice to configuration
management. It can do VLANs and Bonding which is important in the
datacenter, but it doesn't do Wifi, which is important for the desktop
case, and it - as far as I know - doesn't do 802.1x which is important
for Wifi and also some corporate networks.

Greetings
Marc
--
----------------------------------------------------------------------------
Marc Haber         |   " Questions are the         | Mailadresse im Header
Rhein-Neckar, DE   |     Beginning of Wisdom "     |
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 6224 1600402