Re: Avoiding SystemD isn't hard
I agree that a fork is too radical, hard to maintain without money and
blah blah blah...
We just need "uselessd + new udev" to kick systemd entirely.
Then, if a problem appear, lets fix it. And if a new software
appearing depending on systemd as PID1, I'll not use it, simple as
that.
Again, I do not want systemd as PID1 AND I do not want to go back to
sysvinit either.
So, uselessd seems the way to go. Mostly because it is, what I was
thinking systemd was (but it is not slim/tiny), in first place. So,
"systemd is a liar". It comes talking about a new init, then, you're
dead. I feel betrayed because I was thinking about a new init, not
this thing.
Now, that I know that systemd is much more than an "init replacement",
I don't want it, neither its engulfed udev.
I'll have "peace of mind" when I see no systemd sources at all.
Maybe in the end of the day, Debian will be forked.
Hope not!
On 21 October 2014 13:19, Liam Proven <lproven@gmail.com> wrote:
> A blog post explaining why it isn't mandatory, the utter futility of
> the fork and more besides, clearly and simply.
>
> http://www.vitavonni.de/blog/201410/2014102101-avoiding-systemd.html
>
> --
> Liam Proven • Profile: http://lproven.livejournal.com/profile
> Email: lproven@cix.co.uk • GMail/G+/Twitter/Flickr/Facebook: lproven
> MSN: lproven@hotmail.com • Skype/AIM/Yahoo/LinkedIn: liamproven
> Cell/Mobiles: +44 7939-087884 (UK) • +420 702 829 053 (ČR)
>
>
> --
> To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> Archive: https://lists.debian.org/CAMTenCHWZi76oZ74EfTkiJX0G9ifd0pv0sFLE2aUyVKQSEnw@mail.gmail.com
>
Reply to: