• vivendi@programming.dev
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    10
    ·
    2 days ago

    Except, they are. Pottering is the front man who does the dirty work for IBM and Microsoft to take over Linux by forcing distros to adopt systemd.

    Those of us old enough to remember the “vote” that resulted in Debian going to Systemd remember it was almost at gunpoint.

    Death to systemd, long live FOSS culture

    • Magiilaro@feddit.org
      link
      fedilink
      arrow-up
      7
      arrow-down
      2
      ·
      2 days ago

      I am not seeing how IBM and/or Microsoft are winning anything here or how systemd enables them to take over Linux. But maybe I am missing something.

      Last time I checked (60 seconds ago) systemd was using FOSS licences for all it’s code. So it seems to be living the FOSS culture, or not?

      I am always open to learn and correct my view on things under new information, so if you can provide them I am open to read it.

      • vivendi@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        1
        ·
        1 day ago

        Ah but you see, you have to understand the FOSS community a little more than just “using a license that FSF and OSI endorsed”.

        In terms of inter-project politics, systemd is almost wholly owned by IBM. They can override any will they want, they can change anything they want, all while fucking the community over. In short, IBM, using systemd as a massive octopus growing it’s tentacles all over mainstream Linux distros, is gaining considerable weight to pull in the Linux world.

        They can essentially dictate matters to everyone they want, because you don’t want your distro to stop being supported, do you? And now, another IBM-majority project, GNOME, is almost dependent on systemd (despite the very good word of both gnome and systemd that this wouldn’t happen, IT HAS) and KDE is also being slowly pulled in that direction, with DrKonqi becoming systemd only in it’s latest update.

        Essentially, we are handing over 30 years of work in FOSS to IBM, literally the caricature of evil tech company, and now they control the mainstream and can dictate their will.

        Allow me to remind you that this same IBM almost immediately after taking over RedHat, started closing down the source sharing of RHEL, which is it’s own whole thing so I digress.

        Let my final word be this, R.M.S as much of a problematic piece of shit he is, correctly predicted we being fucked over by DRM and subscription services 20 years ago and was ridiculed for it.

        Don’t you think it’s time to take a fucking hint? You don’t have to be an anarchist to see where this is going.

        • Magiilaro@feddit.org
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          edit-2
          5 hours ago

          I have seen with Oracle Java and OpenOffice (as two examples) that the open source community is very good in just leaving and forking a project if the current owners fuck up.

          The same will happen with systemd if needed. Red Hat may be the primary source behind systemd now, but they don’t own it. All the code is fully open source, none of your ramblings have any hint of facts or any real foreseeable danger behind it. I asked for facts, for anything with some kind of real information behind it.

          There is nothing that powers the claim that RedHat or IBM could take over Linux with systemd. How would they do it? They can’t, because even if IBM would tomorrow change the license to a closed one and would want money. Who cares, everyone will just fork the version before the license change and good is.

          Just as it happened back then with Xorg (I mean the change 15 or so years ago, not the current strange fork), like it happened a short while ago with Redis, and there are so many examples more.