- cross-posted to:
- [email protected]
- selfhosted
- cross-posted to:
- [email protected]
- selfhosted
After a few conversations with people on Lemmy and other places it became clear to me that most aren’t aware of what it can do and how much more robust it is compared to the usual “jankiness” we’re used to. In this article I highlight less known features and give out a few practice examples on how to leverage Systemd to remove tons of redundant packages and processes.
Especially for homelab owners:
Have you ever felt like there might be something wrong with your current approach to installing and managing your services? Have you figured out how massively bloated systems are becoming with Docker and tons of little “helpers” that at the end of the day have dependency issues, are hard to understand and modify? Maybe you just want to squeeze a few extra miles out of a memory-tight system such as a Raspberry Pi. Deep learning Systemd will give you an edge and a better understanding about how your systems work and improve your workflows.
And yes, Systemd does containers. :)
Can you elaborate on that?
Sure
1st place to look at comparison of features (IMHO 😉) is the Arch Linux Wiki
And there’s also a good list on the Chrony site
But my brief list is:
ntpd
.systemd-timesyncd
is “better”, but, this doesn’t (yet?) use a DHCP NTP option and always writes to a file - not good for read-only filesystems / SD cards (source)chrony
(Note: on LinuxMint, installing this removessystemd-timesyncd
)fake-hwclock
So, I go with the general theme of your article - keep it simple, don’t install multiple tools to do the same thing - but as you can see, there are use cases where I personally wish we could remove the systemd component(s) and keep the others.
I never had issues with
systemd-timesyncd
in laptops / intermittent network connections. It works as expected…