Make GNU/Linux Great Again?

When I escaped from Windows to GNU/Linux I felt that the GNU/Linux ecosystem is like a remote, secluded beach. A place of tranquility, solitude and retreat from the outside world. Only the initiated ones could come, so that the beach remained well-kept and untainted. Unfortunately, this is no longer the case to me. Some came and thought ‘Oh, what a lovely place! Let’s build a resort here so that many more may flock and enjoy it!’. On paper this sounded great. Unfortunately, with people arrived noise, odor and litter…

As a GNU/Linux user I am a proponent of the ‘tried and tested’. I like simple setups with a minimal number of components and services that are mandatory for my PC to achieve the intended functionalities. I loath stacks of UIs/APIs and infinite towers of front-ends. Understandably, there is a need to separate the user from the hardware to prevent inadvertent damage. However, going several levels deep is a choice, not an obligation.

As many know and most should know, Linux is merely the kernel. The components that sit on top of it are interchangeable and as a whole, the GNU/Linux operating system can be built in various ways. There are several init architectures, including the legacy upstart, sysVinit, systemd, epoch and openRC. Same goes for the bootloader – LILO (now defunct), GRUB2, syslinux, etc. Why then do we only hear of systemd nowadays?

In short, it’s a lobby/agenda of companies that financially support GNU/Linux development. Systemd was spawned by Red Hat as an alternative to the old and ugly Unix ways of the past, which in their opinion are old and ugly, because they require more effort to maintain. Dubious logic, followed by dubious assurance of increased performance and simplified maintenance. Per reference, shell-based init scripts are so simple to write that even a high-schooler would easily be able to handle them.

However, for the resort builders it doesn’t matter. They see opportunity, invest and make profit. Freedom is a financially unsustainable luxury they have no need for. They want a new beach where they can sell their ice cream and pop. This money-driven cancer infests the whole GNU/Linux ecosystem and finds no satiation. The biggest problem is that it kills GNU/Linux’s modularity, the biggest selling point! If desktop environments start to depend on service management utilities, we have a problem…

Fortunately, there are ways and means I have been exploring recently. For instance, one doesn’t need the Gnome Network Manager for wireless network management, as wpa_supplicant’s GTK-based GUI does it perfectly well. In addition, there are GNU/Linux distributions that still appreciate the Unix ways, like Void Linux, CRUX and Gentoo Linux. We can and definitely should make GNU/Linux great again. The place of freedom and tranquility it used to be.

Per my contribution I decided to thoroughly explore CRUX and see how well one can build a GNU/Linux distribution on top of it.


2 thoughts on “Make GNU/Linux Great Again?

  1. i think youre right. whats more, red hat seems to thrive on this.

    red hat ceo brian stevens:

    “Red Hat’s model works because of the complexity of the technology we work with. An operating platform has a lot of moving parts, and customers are willing to pay to be insulated from that complexity. I don’t think you can take one finite element – like Apache – and make a business out of it [using our model]. You need product complexity.”

    systemd author (and red hat employee) lennart poettering on how to get there:

    (awful, isnt it?)

    just for fun:


    • I think it’s absolutely sad and one of the reasons I fight so much to migrate to BSDs. Red Hat has the horse-power to create a product based on GNU/Linux, much like companies build services based on FreeBSD and OpenBSD. Let them have those products. Let them have their own desktop (GNOME3) and GNU/Linux distribution (Red Hat / Fedora). However, why in the actual f*ck do they have to change GNU/Linux entirely? How does infesting the whole ecosystem help GNU/Linux? It kills the diversity, it kills everything that GNU/Linux stood for…

      …though of course it’s irrelevant, because all they care about is making money. I read through the blog post by Lennart Poettering. Yes, there is a ton of problems in terms of software consistency, but that’s mostly down to distribution maintainers, who decide to put binaries (/sbin, /bin, /usr/bin, /usr/sbin, /usr/local/sbin, /usr/local/bin, etc.) and libraries in random places. Same goes for the kernel. This can be addressed by providing proper documentation and finally understanding why it’s necessary to adhere to some sane standards, which somehow almost no one does. However, systemd does NOT fix this problem at all. It creates the Nth+1 approach, which deepens the problem, not solves it. However, as one can gather from OpenRC’s popularity among Manjaro users, almost no one seems to really care.

      Liked by 1 person

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s