Re: End of hypocrisy ?

[Steve Litt <slitt@troubleshooters.com>]

On Mon, 4 Aug 2014 14:03:35 +0200
Raffaele Morelli <raffaele.morelli@gmail.com> wrote:

> 2014-08-04 12:37 GMT+02:00 Andrew McGlashan <
> andrew.mcglashan@affinityvision.com.au>:
> 
> > My own view is "why systemd" .... fix sysinit instead, where it is
> > broken or rather the packages [whatever they are] that don't work
> > properly.
> >
> > systemd gives faster boot times, so what!  I prefer to boot less
> > often and run with what works until I /have/ to do a reboot, so it
> > wouldn't matter if it took 10 times as long to boot.  Improving
> > boot times is just like overclocking for games, it is largely
> > irrelevant and something to boast about ... ie, no real benefit.
> >
> > IOW systemd is a great big waste of time and resources.
> >
> > I don't want to know anything more about systemd, unless I am
> > forced to deal with it, I won't be.
> >
> > Cheers
> > A.
> >
> 
> ​I've seen tons of posts sent to this list about systemd... bla bla
> bla... and did not understand what's the matter with it.​
> 
> ​I wonder what are you all doing with your init scripts which doesn't
> work with systemd. So what?
> 
> /r

I can answer that with two reasons:

1) Binary log files. If you can't see what a radical departure that is
   from the world of Unix, look again.

2) Gratuitous interdependency. Part of the Unix Philosophy is that
   programs should "do one thing and do it well." The user assembles a
   functionality from many such small programs. Up to now, init was
   just init. It started the computer, the /dev and /proc stuff, the
   TTY's and the daemons, then pretty much got out of the way. Now here
   comes systemd, requiring or encouraging even desktop environments to
   require or suggest it.

   Imagine if they replaced grep, cut, cat, diff, awk, sed, head, tail,
   ls, and find with ks (stands for Kitchen Sink). You can do anything
   you want with ks, but you need to know all its options and config
   settings, and its myriad of idiosyncracies. And if it has bugs or
   departures from documented behavior, as any program of its size is
   likely to have at one time or another, everything breaks.

So whether stuff works with systemd isn't the main problem, it's just
icing on the cake when it *doesn't* work.

SteveT

Steve Litt                *  http://www.troubleshooters.com/
Troubleshooting Training  *  Human Performance