3 ms·
Doesn't sound like this fixes systemd, unless your problem is that you depend on systemd + kubernetes. That is, I read this as a Redhat/Gnome/Freedesktop proble
by denton-scratch 4y ago
Doesn't sound like this fixes systemd, unless your problem is that you depend on systemd + kubernetes. That is, I read this as a Redhat/Gnome/Freedesktop problem; I'd love a fix for systemd, but I don't think this one solves my problems.
- kris-nova 4y agoCare to elaborate on your problems? Or maybe a more fundamental question would be -- would you be interested in a project like this solving whatever your particular gripes with systemd might be?
- denton-scratch 4y agoThanks for a constructive response! I don't code any more, and I was never an OS-level programmer. And the systemd debate has been argued, and my champions lost. So I concede; I don't want to argue about systemd. The problems are still there though, and I'm interested in ideas that propose to solve them. This article was scratching different itches than the ones that bother me. I'm not interested in Kubernetes, or any other enterprise cloud stuff for that matter. I don't need orchestration, my hardware never changes (so I don't need anything like UDEV), and if there ever is an ad-hoc change I can ad-hoc configure it.
- majewsky 4y ago> my hardware never changes (so I don't need anything like UDEV) You don't own any USB peripherals?
- denton-scratch 4y agoOf course. But I'm not constantly plugging them in and out. These are a couple of headless, domestic NUC-type boxes, providing simple local services. They don't have GUIs, so notifications are irrelevant.