On 04/20/2018 10:45 AM, Denys Vlasenko wrote:
On Fri, Apr 20, 2018 at 1:08 AM, Laurent Bercot <ska-skaw...@skarnet.org> wrote:
Since no one had time/inspiration to create runit/daemontools
style servie supervision in Fedora, I'll going to create
something homegrown.
I don't understand this.
Why should there be a specific runit/daemontools style service
supervision *in Fedora* ?
I meant, there could be a package ready to be installed.
IIRC there is not.
In the rest of your mail, it looks like you're trying to change the
*init system*.
Yeah, right. Good luck with that. Getting a distro that has embraced
systemd to function right without systemd is a lost cause at this point.
Sure, you can always *boot* on your chosen init system. It's not hard.
The difficult part is the service management: if your chosen init
system is not natively supported by the distro, and in particular by
the package manager, it means you have to rewrite the way every
single daemon starts.
Sure.
The thing is, I don't need that many daemons.
In fact, one thing which was pissing me off is that there were like
3 times more daemons running than I needed. What is that
"systemd-logind" thing and since when login requires a _daemon_???
accounts-daemon? polkitd? rsyslogd? irqbalance? upowerd?
What _are_ all these programs and why they are in my memory?
Then, even if you do that, further down the road, you'll find that
some packages don't work, because they're silently relying on an
obscure feature of systemd. And then it's headaches all the way down.
Don't change the chosen init system of a distro without having support
from the distro itself. If you want to use your own process supervisor
instead of the distro's chosen supervisor, then do that - but run the
supervisor *on top of* the distro's init system. It will make your life
a lot simpler.
Running one of the much leaner and less intrusive init systems (let's
call it again like that before systemd changed the language)? That
sounds like putting a bicycle on top of a train to me.
But this will not allow me to have a webpage with a public description
how I eradicated canc^W systemd - and survived, no probs.
That would be so much less fun.
Thank you very much for this! I also had to un-systemd a Debian system
for as Rasperry Pi, which was a bit easier, as debian still provides an
escape route from system. Otherwise I just switched away from systemd
distros, but it is still a very good thing to show any Linux distro user
any possible way out of the systemd trap.
Bye
Tim
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
