Announcement

Collapse
No announcement yet.

GNU Linux-libre 6.11 Makes Adaptations For Rust, Warns Of Hidden Binary Bits In v6.11

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • GNU Linux-libre 6.11 Makes Adaptations For Rust, Warns Of Hidden Binary Bits In v6.11

    Phoronix: GNU Linux-libre 6.11 Makes Adaptations For Rust, Warns Of Hidden Binary Bits In v6.11

    Building off yesterday's Linux 6.11 release, the GNU Linux-libre 6.11-gnu kernel is now available that is the downstream stripping out driver support/features depending upon closed-source microcode/firmware and other modifications in the name of software freedom and ensuring no closed-source bits are used on Linux-libre-enabled systems...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Back when upstream started adding binary blobs to Linux, they were argued to be separate programs, under different licenses. But this new one was contributed explicitly under the GNU GPL, so, as long as its source code remained unavailable, it could not be distributed at all.
    I hope a legal spat emerges over this (just so the practice of embedding closed-source binaries in open-source source code is discouraged), but it probably won't.

    Comment


    • #3
      So which driver/commit is it that is supposedly in breach of GPL??

      Comment


      • #4
        Will this fork die? It's probably the most tin foil hat thing I've seen the GNU do. All this "cleaned up" nonsense should just call a spade a spade, and just say "regressed".

        Comment


        • #5
          Originally posted by pierce View Post
          Will this fork die? It's probably the most tin foil hat thing I've seen the GNU do. All this "cleaned up" nonsense should just call a spade a spade, and just say "regressed".
          So you would wish to force your will onto others and kill off something they use because you don't like it even though you have the ability to simply not use it ? Says a lot about you.

          Comment


          • #6
            Hmm, why can't Linux just include OpenZFS as a compiled binary? The CDDL, sections 2.1A and 2.2A, grants the ability to change the license of the compiled binary so the OpenZFS kernel binary could be MIT or BSD licensed and included in the kernel that way.

            Comment


            • #7
              With this distro you can be FREE ... free to run it on any ancient unsupported hardware that does not require firmware blobs to bring it up.

              Comment


              • #8
                Originally posted by NotMine999 View Post
                With this distro you can be FREE ... free to run it on any ancient unsupported hardware that does not require firmware blobs to bring it up.
                it depends on what you value more. freedom or bell and whistles?

                Comment


                • #9
                  Originally posted by pierce View Post
                  Will this fork die? It's probably the most tin foil hat thing I've seen the GNU do. All this "cleaned up" nonsense should just call a spade a spade, and just say "regressed".
                  Wait so I have to go tell everyone I know that separating your dark from light clothes are tin foil activities?!

                  IMO if someone wanted a real tin foil hat setup they would just custom ISA with airgap protection running a custom or simpler (BSD) kernel not Linux.

                  For me Linux-libre for me is much more an ongoing effort that makes sure the separation between light and dark licensing is tested practically, which is clearly shown in this article. In many cases these days with all the CPU vulnerabilities... having new CPU microcode makes your system "more secure".

                  Ref: https://www.spinellis.gr/pubs/conf/2...ml/Spi08b.html

                  Originally posted by kurkosdr View Post

                  I hope a legal spat emerges over this (just so the practice of embedding closed-source binaries in open-source source code is discouraged), but it probably won't.
                  I agree with you it's very easy to spot who's doing this and prevent it. Additionally I hoped that legal teams could have made it easier to get modified GPL code from companies like Mikrotik who have made it intentionally difficult to obtain modified code for decades now.

                  Comment


                  • #10
                    Originally posted by PublicNuisance View Post

                    So you would wish to force your will onto others and kill off something they use because you don't like it even though you have the ability to simply not use it ? Says a lot about you.
                    No will was forced. It's not a matter of like, but a matter of pointlessness. It's beyond cultishness.

                    Comment

                    Working...
                    X