Slashdot Mirror
Removing Libsystemd0 From a Live-running Debian System
lkcl writes The introduction of systemd has unilaterally created a polarization of the GNU/Linux community that is remarkably similar to the monopolistic power position wielded by Microsoft in the late 1990s. Choices were stark: use Windows (with SMB/CIFS Services), or use UNIX (with NFS and NIS). Only the introduction of fully-compatible reverse-engineered NT Domains services corrected the situation. Instructions on how to remove systemd include dire warnings that "all dependent packages will be removed", rendering a normal Debian Desktop system flat-out impossible to achieve. It was therefore necessary to demonstrate that it is actually possible to run a Debian Desktop GUI system (albeit an unusual one: fvwm) with libsystemd0 removed. The reason for doing so: it doesn't matter how good systemd is believed to be or in fact actually is: the reason for removing it is, apart from the alarm at how extensive systemd is becoming (including interfering with firewall rules), it's the way that it's been introduced in a blatantly cavalier fashion as a polarized all-or-nothing option, forcing people to consider abandoning the GNU/Linux of their choice and to seriously consider using FreeBSD or any other distro that properly respects the Software Freedom principle of the right to choose what software to run. We aren't all "good at coding", or paid to work on Software Libre: that means that those people who are need to be much more responsible, and to start — finally — to listen to what people are saying. Developing a thick skin is a good way to abdicate responsibility and, as a result, place people into untenable positions.
I personally prefer to use cross-platform software. I prefer software that runs about the same regardless of the platform I'm using it on, and I prefer to have the option to use any supported platform to run the software.
can you please do me a favour and make those thoughts known on the following wine bugreport? http://bugs.winehq.org/show_bu...
the reason i ask is because there is critical functionality in wine that should never have been allowed to go so long without being implemented, and it's Named Pipes "Message Mode". the problem with message-mode is that there really is no good POSIX equivalent, and AJ - the paid-up employee - is in such a dominant and abusive position of authority that nobody may challenge his dictatorship. the only option left to implement anything remotely resembling message-mode under the extreme and fascist technically-tight conditions dictated by AJ is a non-portable hack using a little-known feature of TCP sockets that is *only* implemented in the linux kernel.
i mention this in the context of what you say to illustrate that the problem you highlight is not just restricted to one piece of software (systemd), but is a common problem across many of the critical pieces of software that we are using today. and the worst part is that *in each case* it is extremely difficult to gain sufficient technical expertise in order to engage with these people.... but even if you *do* have the technical expertise they often are so entrenched in their day-to-day mindset as absolute... "gods of their world" that even a reasonable and rational argument is completely ignored.
the long and short of it is that GNU/Linux software is getting out of hand, and is becoming so complex as well as so prevalent that the dominance and arrogance of just one person or company can have massive detrimental consequences for a *lot* of people. i'm really not sure what can be done about this, if anything.