Felix thanks for the links, excellent reading and very informative but
again personal opinion is rife in the first one. The second one is much
better and does discuss some technical issues of systemd. The problem for
me is if systemd is a problem why is Linus allowing it? Why are greater
technical minds letting it take over if it is the problem people say it is?
I remember the kernel crashing issue and I, still to this day, believe
systemd highlighted a problem with the kernel itself. T Ts'o even suggested
in the kernel mailing list that the kernel has a problem in that it could
not do what it was supposed to do and systemd highlighted it. Yes systemd
caused a problem and yes the Lennart and Co should have acknowledged it and
fixed it but everyone involved (not just T Ts'o) should have recognised the
kernel had a problem as well. The reason I remember that issue is the
discussion surrounding it on LQ was where I was told to "choose sides and
be judged". Everyone bar a few who didn't get emotional recognised the
kernel had a bug and systemd highlighted it, everyone bar a few who didn't
get emotional failed to see that both sides in that problem refused to fix
a bug in their code.
On 18 September 2014 14:18, Curt Howland <Howland(a)priss.com> wrote:
On Thu, Sep 18, 2014 at 12:15 AM, Felix Miata
<mrmazda(a)stanis.net> wrote:
with the perspective reading
http://ewontfix.com/14/ had upon me.
Thank you Felix. That is an excellent article.
Curt-
--
The secret of happiness is freedom,
and the secret of freedom is courage.
- Thucydides
---------------------------------------------------------------------
To unsubscribe, e-mail:
trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail:
trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive:
http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting