systemd lost the plot a long time ago. they stopped following the Unix philosophy and now they're busy adding nonsense like age verification. Just like Firefox, systemd doesn't understand its core user base. There are plenty of distros without systemd
@nixCraft There’s little wrong with openRC, I don’t get the hate. Every system I have and there’s about 30 of them, run openrc. Except one. These are hypervisors, firewall/routers, vms and servers. I put systemd on the desktop variant only because.. and there’s really no reason for it other than curiosity. My laptop runs openrc and it’s problem free.
@siim @nixCraft #lazyweb question: does OpenRC use declared dependencies between services, so things automatically start in the right order?
@oclsc @nixCraft .. so I had to basically start its services manually with a delay of a second or two added in.
@oclsc @nixCraft and by manually I mean had to create a startup script in local.d with a sleep timer that basically runs rc-service <name> start after the sleep and all is good. Didn’t find a nicer eay to add a sleep to the service itself and it works so why bother changing something that works. .. yes this does mean that the linear startup gets delayed by a second or 2 before you get the login terminal on the console but does one really care?
@siim @nixCraft I ran into a problem like that on a systemd system; not with PCI probing but with link coming up on a network interface. I added a service that polled for that to happen before declaring successful start, and made some appropriate thing depend on it.
@oclsc @nixCraft I just remembered and have to correct myself again. My problem wasn't the scripts timing out. What happened was, the PCI device wasn't ready/renamed to it's appropriate name for userspace, and thus the startup script that was supposed to configure its interface, couldn't find the device, errored out and reported back a failure for starting. That was the real reason I needed that 1 second delay.