[rescue] Linux wet paint, was Re: Spark10 CPU question (must fix - SPARC damnit :-) )

Dave McGuire mcguire at neurotica.com
Fri Dec 23 01:15:52 CST 2016

On 12/22/2016 02:27 PM, Liam Proven wrote:
> On 18 December 2016 at 14:05, Rich Kulawiec <rsk at gsp.org> wrote:
>> Yes.  I use it as part of the interview process: those who have achieved
>> sufficient technical maturity and understand the Software Tools approach
>> as well as the fundamentals of the Unix philosophy can evaluate -- and
>> dismiss -- systemd in just a few minutes.  It is obvious on inspection.
> Could you spell it out for me? I am trying to fully understand this.

  Just to jump in here...Lumping everything into one process and
(presumably, I haven't looked at the source code) letting the threading
system handle it is just moving the multitasking to another level.  It's
all in-process, and unless they've implemented some sort of
inter-subsystem protection, if their sntp implementation screws up and
stomps on memory, it can barf all over the PAM subsystem's address space.

  Further, it's fundamentally changing what Linux is, moving it farther
away from UNIX.  I think it's reasonable to take that as being
self-evidently a bad thing.

> It *must* by simple deductive logic have strong arguments going for it
> or not everyone would be leaping aboard the boat.

  It's new and fresh, and therefore an improvement over what came before it.

> And yet, almost all I read and hear is hate hate hate, with few actual
> specifics.

  Those kids know not where the dragons lie.

  But now I actually have to agree with Ian...while there is historical
content in this thread, it's getting to be just a bit off-topic.


Dave McGuire, AK4HZ
New Kensington, PA

More information about the rescue mailing list