Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
I've always liked systemd.
I'm learning FreeBSD and the training wheels are off having to learn RC. I should've done this years ago.
On that, anyone know how to pull core temps off a 20 year old Celeron D in OpenBSD? That and my internal PC speaker are the only things I don't have working yet.
OP when systemd successfully wipes his ass
It's almost as if people think systemd is one massive executable rather than a suite of tools
Nah, it's a single executable, like GNU.
Yes, GNU.exe, I know it well.
All that happens at boot is that linux.exe calls systemd.exe, uses all your system resources making your machine unusable bloat.
when you first boot Systemd calls back to Redhat HQ: "Mr Pottering, we got him"
None of this stuff for me. I prefer one tool doing one thing, like busybox
Well it is also a massive executable in the mix there
Did you accidentally forget A) the .so files these binaries link against and B) the actual systemd daemon binary?
We're still not clearing 10 megs
[XXX@YYY]$ ls -lh /usr/lib/libsystemd.so.0.40.0 /usr/lib/systemd/libsystemd-core-257.7-1.so /usr/lib/systemd/libsystemd-shared-257.7-1.so
-rwxr-xr-x 1 root root 1.2M Jun 25 14:42 /usr/lib/libsystemd.so.0.40.0
-rwxr-xr-x 1 root root 2.4M Jun 25 14:42 /usr/lib/systemd/libsystemd-core-257.7-1.so
-rwxr-xr-x 1 root root 4.5M Jun 25 14:42 /usr/lib/systemd/libsystemd-shared-257.7-1.so
Are you intentionally misrepresenting this or are you actually missing these? Also: This isn't about diskspace. Obviously every halfway modern PC can provide the disk space to house the systemd binaries. Disk is cheap but crucially not necessarily tied to complexity. A simple application can take Gigs and still be simple if it includes a lot of resources (graphical, audio, whatever). And a very complex thing can "only" take a few megabytes if it only includes code. Like systemd does.
Note that I am a (mostly) happy user of systemd. I am just annoyed at people misrepresenting facts to fight anti-systemd-bullshit.
It's weird ldd didn't find libssytemd.so ! I have an old system, apparently libsystemd-core and libsystemd-shared weren't a thing back in 2021 on ... ubuntu focal
Sorry but there is a libsystemd-shared listed in your screenshot
I like systemd
Awaiting the guillotine...
You're not alone. For most of my career, I've only used Linux to develop software and deploy that software to production. That usually means webservers, databases, iptables/netfilter, and all the other backend processes that glue that together.
Before systemd, I was using sysVInit. Let me say that systemd has been head-and-shoulders above the previous experience in a variety of ways, with a host of built-in features:
systemctl status <service> shows you exactly what files are loaded)Bottom line: it's dead simple to add your own stuff, and just as simple to read what packaged software is doing. I also think that using a CLI (instead of poking around /var/run and ps output) is a step up in terms of system administration, given how complex all this can get.
My only contention is the forced use of journald, where my preference would be to use the standard /var/log paradigm for all this, rather than have a doorman to a binary logging database. You can configure it to emit text logs, but that's not the system of record for logging - just a feed.
All that said, container-based solutions have rendered both init systems irrelevant a lot of the time, with tools like Kubernetes providing just about all of the same features. Moreover, cloud solutions tend to lean into cloud-init for host startup configuration and management anyway.
I am more of a hobbyist when it comes to running software on Linux. That said, I usually end up being the guy who installs and manages software on work Linux servers, writes Ansible scripts to standardize configs, and troubleshoot when things dont work. Im not as advanced as you are, but got my fair share of pre-systemd headaches... so yeah, I completely agree with you.
I appreciate that. And don't count yourself as less advanced - a lot of folks would consider using a CM tool like Ansible to be pretty wizardly stuff.
I love it as well it makes everything way easier. You can even run containers with it if you install quadlet. I just recreated most of my homelab containers using it.
Been using Linux as my main system for about 8 years now. I know nothing but systemd. I have never tried other init systems, so I genuinely don't know what I'm missing out on (if there is any). I don't mind systemd and I really really like services and timers. I use them all the time to automate things, but that doesn't mean I don't hate some things about systemd. One of the things that I'd love to burn to charcoal is that "a stop job for UID 1000..... 1:45 minutes", bitch? I don't have that much time on my hands, reboot right now. What are the things that other init systems have that make them better than systemd?
a stop job for UID 1000..... 1:45 minutes
oh oh and then it changes to 3 minutes something when 1:45 passes! where was that configured mr poettering??
Yay another thread where a bunch of script kiddies running a homelab come shitting on a toolset that saved the professionals from the init mess. But they of course know that systemd is bloated and prefer running their node servers in dokker containers on something more lightweight
This, so much this. Although it's equally old grumpy farts as well as script kiddies. You'll be able to identify the former by their trademark quote "Systemd is the end of / nail in the coffin for Linux".
I still stand by my assumption that anyone complaining about systemd has never tried to configure SysVInit scripts before
Honestly buttctl has some nice features once you get used to it.
I like how you can pipe anything into it.