this post was submitted on 28 Aug 2023
62 points (84.4% liked)
Linux
47369 readers
847 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That list of "features" never needed to be replaced by systemd and for the most part are provided by the other init offerings.
As for logging you may find yourself one with a system using systemd that has faced an error and cannot boot good luck reading the binary journal it makes, yes these entries can be pushed out to text file or syslog but if systemd falls over hard it will log to the default binary journal and you'll need to use another install with systemd to run journalctl --file /path/to/mounted/journal which in an emergency is a true PITA.
It is not an outlet for those who you choose to espouse as "People who don't want linux to evolve" far from it most of them just want systemd to stop trying to replace things that are not broken and for other projects to stop having it as a hard dependency. Yes it is modular, yes these can be disabled but it has so many tentacles that it is clear the intentions are wider than just being an init.
What's wrong with ip, iproute2, iptables/nftables, ufw, firewalld, ntp, dnscrypt, privoxy, dnsmasq, openresolve, crond, sudo, mount, syslog-ng?
Are they somehow obsolete now?
If you want a basic bootloader your UEFI has one built in and/or you can boot the kernel directly with efistub, systemd-boot is so basic it's pointless to the point that an unconfigured install of refind is a truckload better.
I get that this is a hot topic but waaay too many people are just adding pointless opinion and toxic opinion into this debate that doesn't help anyone make what they want is a decent informed choice and tbh when I see Gnome make a hard dependency of systemd it makes me think either systemd is doing too much, is not modular enough, devs got lazy or all of the above.
And a final FYI I use systemd and have disabled much of it but can't uninstall the parts I don't need/want.
This is plain wrong. Init wasn't able to properly start things in parallel and monitor them. With systemd you can even create a visual representation graph of your boot services that you can use to identify what is taking more time and when things are happening.
What's wrong? Too many tools, way too fragmented and poorly integrated. It is very, very easy to get into trouble if you simply setup a dual stack system with IPv6-PD with those tools. With systemd it all works of the box with simples configuration files and its way more intuitive. For eg. cron is a mess, systemd timers share the unit config format which is way better and more scalable.
So you are saying you could just have a very small footprint and have a very lightweight system that is very solid but instead of choose to go with a bunch of different tools? I've leveraged systemd to be able to have fully working system on devices with 256MB of RAM while still having RAM for other important applications.
Here's a handy chart for you
https://wiki.gentoo.org/wiki/Comparison_of_init_systems
As you can see many have the ability to start services in parallel. Some script magic with graphviz will also do similar to analyse blame.
What's wrong? Too many tools, way too fragmented and poorly integrated. It is very, very easy to get into trouble if you simply setup a dual stack system with IPv6-PD with those tools. With systemd it all works of the box with simples configuration files and its way more intuitive. For eg. cron is a mess, systemd timers share the unit config format which is way better and more scalable.
Do you honestly beloved thie mental gymnastics your getting into just to prove your point, go back to windows. Lol
Well done on using systemd how you wish, now move on and let others use it how they wish or remove it.
It's not gymnastics, it's years and years of init bullshit and fragmentation / lack of integration related issues that were solved by systemd.
Keep telling yourself that, meanwhile we'll all see your obvious dislike of of general userland tools.
I don’t dislike them, I never disliked them… I simply came to like systemd’s efficiency more.
Yup, windows is calling you.
Bye