1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking Benchmarking Platform
Phoromatic Test Orchestration

Systemd's Network Support Frustrating Some Users

systemd

Published on 21 February 2014 11:30 AM EST
Written by Michael Larabel in systemd
87 Comments

The latest controversy within the systemd camp is the new networkd support that appeared in this week's systemd 209 release. It seems the new systemd-networkd is forced upon users by default and not everyone likes this approach.

The systemd 209 release is a major release that brings many new features, including a new systemd-networkd component for configuring and bringing up your network. It appears that in systemd there isn't an easy way to disable this feature if you don't want it: it's enabled by default and instead of issuing a command to disable it, it needs to be hard-masked out of the service file.

A Phoronix reader pointed out this approach to handling systemd-networkd and forcing it on by default (rather than making it an option to be enabled) was discouraging. Additionally, with it being enabled by default, systemd-networkd will be a daemon that still runs even if it was not configured. The systemd-networkd will just run and remain a running daemon without doing anything until it's configured.

In going through the latest Git code, there was a change to not statically enable systemd-networkd but then the next commit to systemd just minutes later enabled networkd by default. At least with the latest work, it's possible to run systemd disable systemd-networkd to disable this service if you don't wish to have systemd managing network functionality, but it will still be on by default.

This networkd component has been frustrating some early adopters of systemd 209 so we'll see if any further changes are made in time for systemd 210.

About The Author
Michael Larabel is the principal author of Phoronix.com and founded the web-site in 2004 with a focus on enriching the Linux hardware experience and being the largest web-site devoted to Linux hardware reviews, particularly for products relevant to Linux gamers and enthusiasts but also commonly reviewing servers/workstations and embedded Linux devices. Michael has written more than 10,000 articles covering the state of Linux hardware support, Linux performance, graphics hardware drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and OpenBenchmarking.org automated testing software. He can be followed via and or contacted via .
Latest Linux News
  1. Phoronix Test Suite 5.8 Milestone 5 Brings Near Final "Belev" Experience
  2. For AMD Users, Linux 4.2 Will Bring The New AMDGPU Driver & VCE1 For Radeon
  3. Atomic Mode-Setting Still Baking For Samsung's Exynos DRM Driver
  4. Ubuntu Phone Update This Month Brings Many Improvements
  5. Fedora's "Fedup" To Be Replaced In Fedora 23
  6. Android M Should Bring Greater Performance & Efficiency
  7. AMD Teases Upcoming Radeon "Fiji" GPU Launch
  8. Dell Makes An Ubuntu Installation Guide, Suggests Users Try It Out
  9. Running Linux On The Intel Compute Stick
  10. AMD Launches The A10-7870K "Godavari" APU
Latest Articles & Reviews
  1. Opening The Gates To Our Daily Open-Source Linux Benchmark Results
  2. The Latest Features For Linux Performance Management + Benchmark Monitoring
  3. Noctua NH-U12DX i4 + NF-F12
  4. Btrfs RAID 0/1 Benchmarks On The Linux 4.1 Kernel
Most Viewed News This Week
  1. NVIDIA's Proprietary Driver Is Moving Closer With Kernel Mode-Setting
  2. Zapcc Claims To Be A "Much Faster C++ Compiler"
  3. OpenWRT 15.05 Preparing Improved Security & Better Networking
  4. Features Added To Mesa 10.6 For Open-Source GPU Drivers
  5. Ubuntu's LXD vs. KVM For The Linux Cloud
  6. The Latest Linux Kernel Git Code Fixes The EXT4 RAID0 Corruption Problem
  7. Fedora 22 Is Being Released Next Tuesday
  8. Friction Building Around An Ubuntu Community Council Decision