nixCraft š§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
Siim OÅ”ur@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.
Norman Wilson@oclsc @nixCraft yes you can declare dependencies and yes they do start in order. However now that you mentioned it I did have one issue. But ai dont know if systemd wouldāve faired better here and that is. A case of a PCI device enumerating too long. On one of my firewalls I have 2 X520 adapters and the second one takes long to ābootā. OpenRC is so fast in coming up that the startup scripts that configure its interfaces time out before the device appears for userspace..
@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?
@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.