[ale] Why systemd vs sysvinit really doesn't matter to me

[Damon L. Chesser]

I hate to nit pick (I really do) but your statement is actually a false 
dilemma.  The OP stated "why systemd vs sysvinit really doesn't matter 
to me", not "systemd vs sysvinit".  The OP says he can't find the time, 
he just wants to use the OS.  The OP never said "this or that".

I am with him.  I just don't care.  That is an opinion, not a dilemma.  
I also don't like watermelon.  Nothing to argue about here.  If you like 
watermelon, eat it.  If you want init $FOO use it.  I just don't want it 
(particularly, I mean, you need some sort of init) or really even care 
about it (which init is used), as long as I can us the Linux (GNU or 
otherwise) when it it booted.


On 02/17/2018 08:02 PM, Steve Litt via Ale wrote:
> On Sat, 17 Feb 2018 13:42:58 -0500
> James Taylor via Ale <ale at ale.org> wrote an email with this subject.
>
> Steve Litt replies:
>
> The very subject of this thread is a false dilemma
> (https://en.wikipedia.org/wiki/False_dilemma).
>
> And it's a false dilemma the systemd cabal employs endlessly, so as not
> to compete with modern simple and efficient inits like runit and s6,
> or, if you like a 100% single file startup, Epoch.
>
>
> SteveT
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo

-- 
Damon at damtek.com
404-271-8699