As per fsf only those linux distributions are 100% free:

Dragora
Dyne
Guix
Hyperbola
Parabola
PureOS
Trisquel
Ututo
libreCMC
ProteanOS

Do you agree or no?

I see a lot of people that want to switch from windows to a linux distro or a open os. But from what i see they tend to migrate to another black boxed/closed os.

What is a trully free os that doesnt included any closed code/binary blobs/closed drivers etc.

Just 100% free open code, no traps.

What are the options and what should one go with if they want fully free os that rejects any closed code?

  • utopiah@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    17 days ago

    Ah… but then that’s not enough, you need to insure that the supply chain itself is 100% free! For example if you are using an Intel CPU, how can you verify it does what it says it does?

    Enter precursor.dev ! Check this out if 100% free is not enough for you.

    PS: honestly do what makes pragmatically your world, and that of the ones around you, better. Hopefully it is toward free software but IMHO if you have more agency with usage (which yes does overlap significantly with this) then it’s a powerful step to keep on doing so.

  • HubertManne@piefed.social
    link
    fedilink
    English
    arrow-up
    0
    ·
    17 days ago

    Agree those are 100% free? I don’t know. It would take a lot of research to verify but I trust fsf as it is currently so think its likely the case. Agree to fully switch to a 100% free os? No. I need the nvidia driver. I would like to though. Believe that really any linux distro is a black box/closed os? No. Just having some binary blobs from vendors is a compromise but its not a deal breaker.

    • thingsiplay@beehaw.org
      link
      fedilink
      arrow-up
      0
      ·
      17 days ago

      Agree to fully switch to a 100% free os? No. I need the nvidia driver.

      Well, there is an Open Source Nvidia driver nowadays (not talking about Nouveau, but the new Nova). I don’t know how good it is and my old Nvidia 1070 card is not supported by Nova. So cannot do any comparisons sadly. I think in the future Open Source Nvidia drivers could be in a similar spot as AMD.

      • HubertManne@piefed.social
        link
        fedilink
        English
        arrow-up
        0
        ·
        17 days ago

        yeah and its been around for awhile but never works quite as well. I choose my os partially by it being install and work with not much more muss or fuss. That being said when buying hardware I preference amd because of the drivers.

  • pmk@lemmy.sdf.org
    link
    fedilink
    arrow-up
    0
    ·
    17 days ago

    Iirc, the list is of operating systems that the FSF recommends. You could have a system running 100% free software, but the FSF won’t recommend it if the distro makes it easy to theoretically install proprietary code. It’s fine to run such a system, but the FSF won’t recommend it.

  • chi-chan~@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    17 days ago

    Make sure they /actually work/ on your computer; not for nothing Debian started to include proprietary drivers by default.

    If you switch to <fully-free-os> and nothing works, then what?

    We would all prefer no proprietary code whatsoever, but prefer even more that stuff would work.

    If you really want to go for fully libre route, I’d consider buying –in the future or now, depends on how much do you want it right now– the correct hardware for it.

  • exu@feditown.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    17 days ago

    The FSF has an ass-backwards approach to firmware, leading to only these distros fulfilling their requirements.

    Their preference for firmware is as follows:

    1. Firmware that’s open source (fair enough)
    2. Firmware that can’t be updated (i.e. devices that are flashed once at the factory)
    3. Firmware that can be updated (CPU microcode, firmware for GPUs, SSDs, etc)

    As Linux includes patching of CPU microcode on boot (to fix security vulnerabilities and bugs) the default build of Linux doesn’t fulfill those requirements.

    • thingsiplay@beehaw.org
      link
      fedilink
      arrow-up
      0
      ·
      17 days ago

      Honestly, I am grateful that the FSF is a bit more strict in this definition. While I do not care too much about this, I think it is good that we have some ideal to follow and look forward. And its good, because anyone who wants to go that route, have a community and direction.

      • LeFantome@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        17 days ago

        Idealism is fine.

        Braindead self-denial less so.

        How is proprietary firmware that cannot be updated superior?

        The line the FSF draws between what is hardware and what is software is total nonsense

        The FSF should stick to software so they can maintain the completely hard line that you value. That can apply to actual software.

        There should maybe be a Free Hardware Foundation too (maybe a sister or sub-project). If that existed though, they would have to reject pretty much all the hardware that all of us use, including the hardware that the operating systems in this list were designed to run on. Because they are all completely proprietary regardless of their firmware update policies.

        I would love a FHF. Let’s all use open schematic, RISC-V systems with open source firmware. Yes please!

        But let’s stop doing dumb shit like refusing to update the microcode on our Intel CPU and pretending that is more free instead of just more dumb.

        The way why the FSF approaches firmware today is totally braindead (in my view).

      • suicidaleggroll@lemmy.world
        link
        fedilink
        arrow-up
        0
        ·
        17 days ago

        Disagree. Their priorities are backwards.

        Company A releases a product, it runs closed-source proprietary firmware on-board, and it can’t be updated by the user even if bugs or compatibility issues are found later on in the product’s life cycle.

        Company B releases a product, it runs closed-source proprietary firmware on-board, but it can be updated by the user if bugs or compatibility issues are found later on in the product’s life cycle.

        According to the FSF, product A gets the stamp of approval, product B doesn’t. That makes no sense.

  • ulterno@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    17 days ago

    Better get an Open Hardware RISC V system, with stuff like the graphics, sound and elt/WiFi/Bt being Open Hardware too.

    Then you can go with a fully open OS and it will actually make sense.

  • mvirts@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    17 days ago

    Bruh is your CPU even source available?

    The only option for true transparency is to build it from scratch, like at the logic gate level.

    Those distros have ethical and legal value but they don’t magically make you better off.

  • Flax@feddit.uk
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    17 days ago

    Wasn’t there something that couldn’t be classified as free because it had json or something which has a licence and it’s only stipulation is is “do not use for evil”?

  • LeFantome@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    17 days ago

    Debain and Fedora are 100% free software operating systems.

    Point at a single package in either one that is proprietary software.

    Driver firmware does not count. Why? Because that is hardware. The hardware is proprietary regardless and there is proprietary firmware in my hardware regardless of what my OS does.

    None of the operating systems listed run on “free” hardware, so arguing about how free the non-free hardware is is meaningless.

    Calling Debian and Fedora “closed source” or “black box” because they distribute firmware is madness. Hardware that cannot be updated at all is less “black box”? If that is your view, your opinions hold no weight with me at all.

    • pie@piefed.socialOP
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      17 days ago

      driver firmware does not count?
      ofc it does.
      it is just your opinion and it holds also no weight with me too

      • LeFantome@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        16 days ago

        Why does the proprietary firmware in your hardware only suck if it can be upgraded?

        You are quite happy running hardware that uses proprietary firmware as long as it does not show it to you. But if it shows it to you then it has to be free software?

        I am not saying free software would not be better. Clearly it would be. But saying that not showing the firmware to you is better than showing it to you makes no sense. Please try to make a good argument for why it is ok as long as you don’t see it?

        Given that you are willing to run proprietary firmware, why are you not willing to run proprietary firmware that can be upgraded? Got an argument for that makes your “ofc it does” even a little bit valid?

        Or are you running on 100% “free” hardware? Because that is for sure not anything based on AMD or Intel and for sure not using any GPU or network card that I have ever heard of.

        RISC-V is fighting the good fight. But even there the actual hardware being used today is proprietary, including of course the firmware (accessible or not). And I doubt you are running RISC-V anyway.

  • Una@europe.pub
    link
    fedilink
    arrow-up
    0
    ·
    17 days ago

    Aren’t these shipped without any proprietary firmware, which you can try and if it works for you it works and use it but for many people these just won’t work and using stuff like arch/Debian/fedora/opensuse to name a few will work much better. Like they are great distros if they work for you use them but they are not for everyone.

    • vapeloki@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      17 days ago

      This. No property firmware blobs, nothing that is considered non free software.

      So, no Nvidia graphics for gaming, no wifi and bt, a bunch of software not available.

      • LeFantome@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        17 days ago

        No. You don’t get it.

        You have to switch to hardware that keeps its firmware safely hidden inside so we can call it “hardware”. If you let the firmware be updated, now it is “software” and it has to be free. But you can run in whatever “hardware” you want and be totally free.

        • vapeloki@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          17 days ago

          I don’t get what?

          There is a reason for the naming hardware, firmware, software.

          HARD, FIRM, SOFT.

          No, hardware das not bekomme Software just because it has firmware.

          And yes it would love to see free firmware.

          Look at CPU microcode. It is used to fix security issues in hardware. Without it you are vulnerable. Not using the property firmware blob to update the microcode is a very very bad idea. Does that make the CPU software…

          • LeFantome@programming.dev
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            16 days ago

            Sorry buddy. It looks like I somehow replied to the wrong comment.

            You misunderstood me (no surprise given the first sentence).

            No, the CPU does not become “software” because it has firmware. Which is why it is crazy to disqualify Linux distros as “free” when they include firmware blobs.

            Based on your comment here, I would say we completely agree.

            [EDIT: Actually, I see my mistake now. I was replying to you. I just forgot to put the /s at the end of my first line. I said “You don’t get it” because “you do get it”.]

            • vapeloki@lemmy.world
              link
              fedilink
              arrow-up
              0
              ·
              16 days ago

              Sorry, I am very sensible regarding this topic. I may have overreacted too.

              I would suggest we keep those comments here for the overall content and shake hands :)

      • Anonymouse@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        17 days ago

        I thought Debian didn’t include firmware and other binaries by default. I remember having a separate firmware CD for installs on weird RAID controllers. Did that change?

        • Pika@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          0
          ·
          edit-2
          17 days ago

          It didn’t until 2022 or so, it’s had a toggle that can be turned on or off for non-free repo’s for as long as I can remember but, starting around 2022 they changed the default to allow for non-free (and also apparently made it a pain in the butt for the live install to disable it because its a boot param now instead of a toggle)

    • LeFantome@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      17 days ago

      Never upgrading your CPU firmware is a bad idea. Most of the people saying that “works for them” have no idea what they are talking about. Yea, your system runs. Congratulations.

      And they are still running on proprietary firmware. Just outdated firmware that they refuse to update.

      It is just such utter nonsense. It makes my brain hurt.

  • LeFantome@programming.dev
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    17 days ago

    The reduction in proprietary hardware that results from those systems is not meaningful in my view while the massive reduction in security and the greater inconvenience matter.

    People have no idea how their hardware works. A card from NVIDIA has not just the NVIDIA drivers but a bunch of internal systems with additional firmware. Even your CPU may have an entire OS on it.

    Hardware that allows its firmware to be updated is more open, not less, even if I currently only have proprietary firmware to load on it. And at least it can be updated. Simply not letting me upgrade the firmware does not magically make the hardware more open. Not allowing proprietary firmware for an open source operating system is just not an idea that resonates with me.

    Would I prefer fully open source hardware and firmware? Yes. I am happy to see these options are slowly developing. In the meantime, we all run our software on proprietary hardware and drawing the line between hardware and software at a less convenient or less secure point is not making me any more free.

    At least, that is my opinion man.

  • Sinfaen@beehaw.org
    link
    fedilink
    arrow-up
    0
    ·
    9 days ago

    Hard disagree. Only people that are already in linux-land should even think or talk about this, and only after they’re aware of what they depend on and whether they can even do that in the first place.

    Main reason: biggest thing holding Linux back is user-base. The more users there are, the more that companies will actually care about supporting the OS. In the meantime, newbies to Linux need an OS that is as hassle free as possible that supports what they need. Windows and macOS have their downsides, but you can’t disagree that they work out of the box. You only get a few chances to get someone to even think about switching ecosystems, and going to a straight free distro is another huge hurdle on top of that. Most closed source applications only get tested on debian/rhel based distros anyway, I wouldn’t be able to do my my day job on a distro outside of that without some serious headache.

    There are many closed source components that don’t have equivalent open source alternatives, and features are a thing that will snag many people. Most people aren’t technical.

  • ZkhqrD5o@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    17 days ago

    For that goal, really stick by the FSF recommendations, for that, they are perfect as they have strict requirements.

    But I think calling other GNU/Linux distros black box only because some drivers are proprietary is a bit too far, some people just prefer a “minimum damage” approach and that’s a compromise everyone needs to decide for themselves. If I were living in China or Iraq, however, then I would exclusively run distros like that as well.

    • vapeloki@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      17 days ago

      We ate talking about:

      • CPU Microcode
      • Firmware for network and WiFi cards

      Those are not just “some hardware will not work”. Currently, don’t using those blobs that you will have an vulnerable CPU but ad you are also offline that should be safe /sarcasm