Comment by gf000
10 months ago
What requirements does it impose?
Also, feel free to "rob that feeling back" by learning how systemd works
10 months ago
What requirements does it impose?
Also, feel free to "rob that feeling back" by learning how systemd works
Ok, try to go off the well trodden path of a default systemd setup.
Eg. make your system "login interactive" before networking and other unneeded services (database, web server, whatever) are even attempted to be set up/started.
Use just drop-in configuration fragments (*.service.d/override.conf) without making an unmaintainable mess (ie. without making your own copies of whole, OS installed unit files).
That should get you the feel. :) And it's not something crazy, it's just basic re-ordering of dependencies.
Its not that hard, just a matter of reading the systemd documentation and learning about default dependencies: https://github.com/lukasstraub2/systemd-delay-services
Indeed, nothing crazy.
But all I want is to not have login prompt processes (getty) wait for seemingly unrelated things, and start as soon as possible.
In a friendly system, I'd just edit the getty service config and change After/Before/whatnot and be reasonably confident I didn't break anything. But
1) it's not possible, you can't just override After/Before alone.
2) systemd doesn't make it easy to inspect existing relationships in a simple to understand, localized manner in the first place. So unless you're the one that wrote all units in the system, getting a concept of what you'll possibly break by changing things is almost impossible, without just rebooting and seeing if the system will start up.
You can create a massive SVG of dependencies from systemd-analyze, but that's really not that helpful. It's a picture that has at least 10 meters on one side. :D
> What requirements does it impose?
Numerous kernel features, reliance generally on it by itself and by third party programs (running ceph w/ openrc is hard bc it assumes systemd is present). I’m buying the full car when I use it, when what I really want is a kit that I can optimize for purpose. Honestly though, this close integration is worth it. My main OS build at the moment is pretty much just systemd and podman on top of linux.
> Also, feel free to "rob that feeling back" by learning how systemd works
I really want to! I just don’t know any good resources that can help get me familiar with all it’s doing for me in the background. All I know about it is what I have gleaned from tutorials, I don’t yet feel I know what’s possible with it yet.
>learning how systemd works
Waste of time. It's easier to get used to a systemd-free distro
That's a really negative comment with little to no contribution to the discussion. Care to elaborate more on that, so that we can discuss detailed points instead of blanket statements?