IMHO, #SystemD is pretty good, but I'm not a fan of using dbus and I think a lot of people aren't either, and if they'd just make that one aspect of systemd more unix-like, i.e, create files in /dev/ and /sys/ etc to actually control the state of systemd rather than forcing everything to use some IPC API, then I think basically every complaint about systemd magically goes away
DBus is a fine idea, but just not very POSIX-y, more along the lines of how Windows and Mac work. Which is not Linux-y🤷
If you’ve ever navigated any form of forum or online community focused on #Linux, you probably saw someone mentioning #SystemD as either an advantage, or, more likely, a problem. While it’s used by virtually every major Linux distro, it seems like there’s a strong core of people who dislike this system,so I thought I’d give a look at what systemd is, and at why some people seem to really hate it:
# cat /var/log/README
You are looking for the traditional text log files in /var/log, and they are
gone?
Here's an explanation on what's going on:
You are running a systemd-based OS where traditional syslog has been replaced
with the Journal. The journal stores the same (and more) information as classic
syslog. To make use of the journal and access the collected log data simply
invoke "journalctl", which will output the logs in the identical text-based
format the syslog files in /var/log used to be. For further details, please
refer to journalctl(1).
Alternatively, consider installing one of the traditional syslog
implementations available for your distribution, which will generate the
classic log files for you. Syslog implementations such as syslog-ng or rsyslog
may be installed side-by-side with the journal and will continue to function
the way they always did.
Thank you!
Further reading:
man:journalctl(1)
man:systemd-journald.service(8)
man:journald.conf(5)
https://0pointer.de/blog/projects/the-journal.html
From gratuitous use of superfluous language features (a cleanup handler, for a single fd, srsly?) to inappropriate use of standard POSIX APIs (using connect+write on a socket that only sends one message and then gets closed, really?) Older compilers don't even support a cleanup attribute, and this code is used as a model of portability??
for a full-feature build, down 5 libs which are now dlopened on demand. Last one, libcap, will need to be swapped for some ioctls which won't happen for this release.
The Linux systemd Controversy: A Beginner’s Guide to Understanding the Debate
In the world of Linux, few debates have stirred as much controversy as the battle between the traditional System V init system, often known as SysVinit, and the newer systemd.
systemd is a system and service manager, first introduced in 2010 to replace the traditional System V init system. It was designed to improve boot-up speeds and manage sy ...continues
I think that #systemd should do package management. I hate when I have to install some software, but it only has a .deb package. I think that a unified packaging format for Linux would be good.
#Flatpak takes a lot of space and doesn't work well with CLI software. #Snap relies on a closed backend and is not very fast.
I love how Go and Rust programs just compile down to a single binary you can do whatever you want with. Sprinkle a systemd definition and voila, you’ve got yourself a long running service with superpowers 🥰.
Fucking #gnome sometimes (most of the time). I've got a fairly intricate op to run tonight and under #kde I would be able to re-title all the shells I need to have open to run it but in Gnome? "Derrr, we removed that option... it was 2 hard 4 luzers to understand!"
I swear to all that matters, the UX experimentation perpetrated by Gnome is a pestilence rivaled only by that of #systemd
finally have my #irc server running about the way I want. next thing will be linking it up to another server to create a tiny little irc network.
it really isn't hard to set up either this ircd (ngircd) or one of the alternatives in debian, the only thing I have issues with is how it interacts with #systemd when you try to restart it. but that's a systemd thing. and maybe I'm just bad at that.
otherwise you can just install the package and have a working irc server just like that.
#systemd v256~rc1 is out! You know the drill, download it, run it, find all the bugs and report them - possibly to somebody else, I'll be at the nearest pub
I'm trying to have a Target get disabled by a Condition, and then not pull in its dependencies, but the systemd documentation says it's not possible - but doesn't suggest an alternative
I know people love hating on #systemd but there are so many things that are great about it. The journal is among the best (and the one that people seem to hate the most for reasons I find hard to relate to). Building a service with good logging is literally free, no code required, STDOUT/STDERR goes to the journal, you're done. Ingesting those logs into something like Loki is also free. #linux