Re: If Not Systemd, then What?
On Tue, 21 Oct 2014 18:41:21 -0700
Patrick Bartek <nemommxiv@gmail.com> wrote:
> On Mon, 20 Oct 2014, Steve Litt wrote:
>
> > On Mon, 20 Oct 2014 12:45:11 -0700
> > Patrick Bartek <nemommxiv@gmail.com> wrote:
> >
> > > After much vitriolic gnashing of teeth from those opposed to
> > > systemd, I wonder... What is a better alternative?
> >
> > * Nosh
> > * Runit
> > * Upstart
> > * S6
> > * Probably more I don't know about.
>
> OpenRC, God, and another one -- I can't recall the name -- come to
> mind. Been studying them all. Runit as a partial or full "drop-in"
> replacement for sysvinit seems promising.
>
> > > And it can't be sysvinit.
> > >
> > > Yes. Syvinit still works, but it is after all 20 years old. It's
> > > been patched and bolted onto and jury-rigged
> >
> > Nobody's arguing for sysvinit as a long term solution, for the exact
> > reasons you post above. Those of us who appeared to favor sysvinit
> > were saying "let's wait until we have something good." We also
> > pointed out the false choice of prematurely narrowing it to systemd,
> > Upstart or sysvinit.
>
> This I realize, but for some "something good" is never ever good
> enough to replace the old, the familiar, the comfortable.
I spoze. But there's little good about systemd, and a whole lot of bad.
Like I listed near the beginning of this thread, there are plenty of
"something good"s that I'd gladly replace sysvinit with. But systemd is
a catastrophe if you want a computer controlled by you and not
Red Hat.
SteveT
Steve Litt * http://www.troubleshooters.com/
Troubleshooting Training * Human Performance
Reply to: