Cocoa Hoto in real life (nprofile…k9rm) Yes. 99% of my init needs are met by running daemon[1] from rc.local at boot; the default method on Slackware. With three lines of shell script I get a named daemon, with PID file tracking, executed by its own user, optionally in a chroot, and with stdout and stderr redirected to log files.
And for the 1% when I want something crazy, like running multiple network namespaces for different services hosted in them, connecting over specific Wireguard networks each, and isolated from seeing the actual network hardware directly, I can modify the simple networking init scripts, and make it happen myself in a couple of hours. I don't even want to imagine what it would be like to try to modify systemd and NetworkManager code to add such a feature.
My experience with systemd was very buggy, in production, causing extended down-times, from bugs left unfixed for years. My experience with OpenRC was alright, but does not spark joy. Only caused production downtime once, due to a buggy interaction with consolekit2, but that's a track record roughly %600 times better than systemd already.
[1]: https://libslack.org/daemon/
Red Rozenglass /
npub1aj…94pgc
2025-03-26 06:30:46
in reply to nevent1q…8trh
Author Public Key
npub1aj05n6h74ys35hfujyddczfcmr4drhs79xtrfdxw8sutdq2gnw9q994pgcPublished at
2025-03-26 06:30:46Event JSON
{
"id": "19a5e309863932adc7498d527b8cdb0203bf6ba4212081e97406976d6640a2c5",
"pubkey": "ec9f49eafea9211a5d3c911adc0938d8ead1de1e299634b4ce3c38b681489b8a",
"created_at": 1742970646,
"kind": 1,
"tags": [
[
"p",
"0a93edbc7e77bd5da46055e51d8192ce20cdb5d9cfd88010f67f7d46684cf827",
"wss://relay.mostr.pub"
],
[
"e",
"74ad5533e8b5ae78a1eae45ba56c4d0fef8bf542f737a23c329264194a28c1e3",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fedi.dreamscape.link/rozenglass/p/1742970646.369383",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqp2f7m0r7w774mfrq2hj3mqvjecsvmdweelvgqy8k0a75v6zvlqns0yk9rm Yes. 99% of my init needs are met by running daemon[1] from rc.local at boot; the default method on Slackware. With three lines of shell script I get a named daemon, with PID file tracking, executed by its own user, optionally in a chroot, and with stdout and stderr redirected to log files.\n\nAnd for the 1% when I want something crazy, like running multiple network namespaces for different services hosted in them, connecting over specific Wireguard networks each, and isolated from seeing the actual network hardware directly, I can modify the simple networking init scripts, and make it happen myself in a couple of hours. I don't even want to imagine what it would be like to try to modify systemd and NetworkManager code to add such a feature.\n\nMy experience with systemd was very buggy, in production, causing extended down-times, from bugs left unfixed for years. My experience with OpenRC was alright, but does not spark joy. Only caused production downtime once, due to a buggy interaction with consolekit2, but that's a track record roughly %600 times better than systemd already.\n\n[1]: https://libslack.org/daemon/\n\n",
"sig": "638513462f2d3770d76876317119af72a3acb0da68e138b906fffc0e9dbd7cae3610cd7061f7ceeda41ef098104f2995e0650e11513ff58a22a047e751227a48"
}