:: Re: [DNG] Linux-related critique [R…
Top Page
Delete this message
Reply to this message
Author: James Powell
Date:  
To: dng@lists.dyne.org
Subject: Re: [DNG] Linux-related critique [Rant]


> Date: Wed, 19 Aug 2015 00:07:36 +0200
> From: philnx@???
> To: dng@???
> Subject: Re: [DNG] Linux-related critique [Rant]
>
> Rainer, I'm sorry for posting the wrong quote header in my previous
> message. Of course I was quoting "DStoicheff", not you.
>
> Best,
> Philip
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Anyone that feels systemd is a forward thinking idea, go read the UNIX documentation by Doug Mcllroy and the rest of the guru's who developed and founded not just UNIX but the underlying principles of UNIX and UNIX-like systems.

Now please do yourself a favor, if you still think systemd is the next best thing since sliced bread. Go down to Wal-Mart, Best Buy, or some other humdrum name-brand store, buy a copy of Windows 10, and please, for the love of all that is sacred, holy, sane, and just in this universe, DO NOT COME BACK.

systemd is not launchd, busybox, or SMF.

systemd is a complete shell-less hypervisor that is more akin to the PlayStation 3 operating system (XBM) which was about as GNU friendly as Bill Gates or Steve Jobs. It is not an alternative, nor is it a drop-in sysvinit replacement. It is a completely new middleware that has about as much usage and business in GNU/Linux as svchost would have. Entire systems must be rebuilt around it. Services must be rebuild to use it. It is not just "an init system". It is a hypervisor. Here's the definition for the stupidly clueless:

"A hypervisor or virtual machine monitor (VMM) is a piece of computer software, firmware or hardware that creates and runs virtual machines.
A computer on which a hypervisor is running one or more virtual machines is defined as a host machine. Each virtual machine is called a guest machine. The hypervisor presents the guest operating systems with a virtual operating platform
and manages the execution of the guest operating systems. Multiple
instances of a variety of operating systems may share the virtualized
hardware resources."


Each virtual terminal to the shell is a virtual machine in which everything is a guest of the host. Yes, bash is no longer the default access point of the system. systemd is the host, it is the access point. It supplies it's own networking manager, kernel command line interface, boot manager, session manager, device manager, and a host of other things which all run independent of the shell system, unlike a traditional UNIX or UNIX-like system. In short, your "root" access is not really and truly root. It's a root accessible shell session with root permissions.


In traditional GNU/Linux, bash is the base of the system. Everything run as an off-shoot of bash as a daemonized forked executable.


systemd is technically thinking exactly like Windows 9x/ME all over again. A system running on top of another system. It was a flawed design then, and it's a flawed design now.


I hope this has been enlightening for the clueless as to what systemd is and how un-progressive and backwards thinking it truly is.


If you want forward thinking stuff, look at s6, OpenRC, Runit, and others. Things that are aimed at helping UNIX, not turning GNU/Linux into another half-assed, piss-poor, wanna-be copy of Windows 9x.


Good day sir!


-Jim