• 3 Posts
  • 33 Comments
Joined 1 year ago
Cake day: July 11th, 2023
  • jyoskykidOPtoLinux@lemmy.ml•A solution to the GNU/Linux naming problem
    23·
    1 month ago

    Given the label is meant to classify related operating systems, the label should provide an accurate description of the basis of the system.

    Which is one of the reasons why specified GNU/Linux separately from just Linux for Alpine, instead of calling it Musl/Linux.

    If a software is written for just Linux, it will work on either system. But if it is written for GLIBC, it work work on Musl LIBC based systems.

    Programs linked dynamically with Musl LIBC won’t work on GLIBC based systems too, but considering the trend of everyone using GLIBC, those who build for Musl LIBC would state it explicitly, compared to programs released for GLIBC, which ambiguously only say that it is built for Linux.

  • jyoskykidOPtoLinux@lemmy.ml•A solution to the GNU/Linux naming problem
    23·
    1 month ago

    software written for “Linux” usually works on any POSIX operating system, and sometimes even Windows. Unless you’re talking about binary compatibility, which is meaningless in the Linux space anyway.

    In practice, as a person who uses Musl LIBC and the Runit init system, most “Linux programs” don’t even work on it, often even if I try to build it from source because of their dependencies on GLIBC. GLIBC is a very hard dependency that most people overlook when writing software.

    And many programs even have a hard dependency on systemd, to a lesser extent. Even that too only works on systems with GLIBC, and cannot be used with any other LIBC.

  • jyoskykidOPtoLinux@lemmy.ml•A solution to the GNU/Linux naming problem
    24·
    1 month ago

    Yes, GNU is not a complete OS, but neither is Linux, but we call it as such.

    Hell why are we not raising pitchforks at GNU for being a all encompassing project that wants to consume everything like everyone complains systemd is trying to do?

    The reason is ultimately the actions of the Linux community from the beginning itself. Had they been fair, we would’ve referred to the project as GNU/Linux from the beginning itself.

    There’s no point in going back to change any contemporary label for accuracy, we only have to do so if there is a sense of unfairness in the label. That is the case here.

    It is a pointless distinction created by a guy that was pissy that his pet project was not getting the attention he thought it deserved.

    If Stallman was like AT&T who filed a copyright on BSD/386 for using their work, he wouldn’t have caused this. The entire principle of trademarking exists for this reason. It’s only when a person tries to help other people that they get sidelined. It is our responsibility to give the original developers the due respect.

    As for systemd, it was always created as an init system for the GNU/Linux OS. I use Void Linux musl edition with Runit init system, and it could not be replaced with systemd because it depends on GLIBC.

  • jyoskykidOPtoLinux@lemmy.ml•A solution to the GNU/Linux naming problem
    26·
    1 month ago

    That’s where the history matters. If you applied patches to the GNU project to make it work with Linux, how does the resulting OS become Linux in the end? Linux holds a special place in that regard because it makes the kernel layer, but it doesn’t completely invalidate GNU.

    Even this commented asked the question of how we call OSs not approved by FSF as GNU/Linux distributions, showing how he does not understand what the idea even implies. GNU is not a political movement, FSF is.

  • jyoskykidOPtoLinux@lemmy.ml•A solution to the GNU/Linux naming problem
    51·
    1 month ago

    Chrome OS would be a Proprietary Community/Linux OS, and Chromium OS would be a Community/Linux OS. Chromium is a community project that’s added to the Gentoo base.

    By Community, I’m referring to the free community projects, not just any contributions.

    Windows for example is an Proprietary NT OS, but all Windows are NT based, so we can just skip the NT part.

  • jyoskykidOPtoLinux@lemmy.ml•A solution to the GNU/Linux naming problem
    27·
    1 month ago

    Just read the post dude. I made it easy to read first, then others asked what the problem was, so I had to add it. I guess I’ll put it at the end instead.

    Musl, systemd, Freedesktop, etc. were never OS projects. GNU and Linux are OSes.

    Also, most “Linux programs” don’t run on Musl LIBC based distros like Void Linux musl edition, which I’m using, and I’m considering returning to the GLIBC edition for my sanity.

  • jyoskykidOPtoLinux@lemmy.ml•A solution to the GNU/Linux naming problem
    26·
    1 month ago

    LiGNUx is unpronounceable. It’s kind of like xbwhfr.

    Linux is pronounceable, but the recognition of one of the founders who chose to market it while the other who fought for freedom gets unrecognised is unfair, and people can notice that.

    I mentioned *BSD because I’m solving this problem from an ontological level to address systems. If someone categorizes FreeBSD as a BSD OS vs BSD fork, there’s still a small debate that can arise from it. Calling it a Community/BSD OS gives attribution to the core team as well as the original BSD team. And all of it remains easily pronounceable as well.

    You wouldn’t call it GNU slash Linux, but a “community developed GNU and Linux based OS” and just Linux for referring to the Kernel. Most apps for example run only on GLIBC, and therefore calling them Linux apps doesn’t make it inclusive of Musl LIBC based systems.

Moderates