Slashdot Mirror
SystemD Gains New Networking Features
jones_supa writes A lot of development work is happening on systemd with just the recent couple of weeks seeing over 200 commits. With the most recent work that has landed, the networkd component has been improved with new features. Among the additions are IP forwarding and masquerading support (patch). This is the minimal support needed and these settings get turned on by default for container network interfaces. Also added was minimal firewall manipulation helpers for systemd's networkd. The firewall manipulation helpers (patch) are used for establishing NAT rules. This support in systemd is provided by libiptc, the library used for communicating with the Linux kernel's Netfilter and changing iptables firewall rulesets. Those wishing to follow systemd development on a daily basis and see what is actually happening under the hood, can keep tabs via the systemd Git viewer.
systemd seems dead set on becoming an alternative operative system.
Which wouldn't be a bad thing if it wasn't ruining perfectly good operating systems like Debian while it grows.
I've stuck with Debian for a pretty long time (since around 2000) mostly because I know how everything works. But in the last year running testing, more and more frequently I'll find that something has been yanked out and replaced by something harder to use and understand. Maybe it's finally time to switch to BSD instead.
How can we continue to believe in a just universe and freedom to eat crackers if we have no ale?
I'm sure they do. But FreeBSD doesn't have a massive init system intruding itself into every single aspect of the operating system.
Just what the fuck is SystemD supposed to be?
The world's burning. Moped Jesus spotted on I50. Details at 11.
Where do you get that idea? There's no IP forwarding and masquerading in the init process. That all happens in the networkd process.
I think they intend to bring stability and unity to Linux by eliminating modularity and choice.
Or the echo chamber could be wrong about PID 1.
Like all great lies, it includes a bit of truth:
1. More lines of code equals more bugs.
2. The systemd project has lots of lines of code.
3. PID 1 must be super reliable or bad things will happen.
So far so good right? Stay tuned for the lie:
4. All of systemd is in PID 1. Therefore systend's PID 1 must be buggy and dangerous.
It's about as right as including Bash's line count in a discussion about sysvinit PID1. But don't take my word for it. Echo on bro.