Announcement

Collapse
No announcement yet.

OpenZFS 2.1.10 Released - Adds Linux 6.2 Support, Finally Drops Python 2 Compatibility

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

  • OpenZFS 2.1.10 Released - Adds Linux 6.2 Support, Finally Drops Python 2 Compatibility

    Phoronix: OpenZFS 2.1.10 Released - Adds Linux 6.2 Support, Finally Drops Python 2 Compatibility

    OpenZFS 2.1.10 is out as the latest update to this open-source ZFS file-system implementation currently supported on Linux and FreeBSD 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
    you just deserve a better licence buddy

    Comment


    • #3
      Why does file system utilities need Python? I certainly don't want fsck or mkfs to depend on Python. Seems brittle... Or is it just a build system/dev tooling thing?

      Comment


      • #4
        Originally posted by Vorpal View Post
        Why does file system utilities need Python? I certainly don't want fsck or mkfs to depend on Python. Seems brittle... Or is it just a build system/dev tooling thing?
        The python requirement is for if you want to build the optional python bindings. OpenZFS itself doesn't require python, and happily builds without it.

        Comment


        • #5
          "for Linux and FreeBSD" - What about Illumos?

          Comment


          • #6
            Originally posted by horizonbrave View Post
            you just deserve a better licence buddy
            Sigh...Because that works both ways.

            The CDDL is technically a more free license than the GPL. The only reason those licenses don't jive are two reasons: neither allow re-licensing code, that's the main biggie, and their ownership models.

            The Linux Foundation could always grant either OpenZFS or CDDL a special exception. That's not unprecedented. That would cover the re-licensing part. No big deal, should be an easy decision to make. However,

            The other issue is the ownership model. The GPL allows every commit to be owned by the individual contributor. The CDDL allows every commit to be owned by the organization. The ownership issue is why we're starting to see a lot of GPL+CLA or dual licensed GPL+BSD/MIT projects. Projects where you agree to the GPL while at the same time agree to give the code to the organization.

            Long term, the GPL ownership model will stifle things. Death+70 years of every single contributor is damn stupid. I think that's what the GPL to Public Domain is in the USA. If Disney had their way it'd be even longer. They really need to nip that in the bud down to like 20 years after public commit or public pull request (to remove the loophole of calling it an experiential pull request and not officially committed code for 45 years).

            Comment


            • #7
              Originally posted by Estranged1906 View Post
              "for Linux and FreeBSD" - What about Illumos?
              NetBSD and Illumos distros use the original Solaris implementation from OpenSolaris to the best of my knowledge. FreeBSD did too in versions prior to 13.0. Illumos's case makes sense to maintain bug for bug compatibility with Solaris, NetBSD I don't understand their model, also they have a really wonky ZFS on root setup. It is not as streamlined as FreeBSD. NetBSD is also cool because it isn't hedging the bet on just ZFS, they have a port in progress (read only last time I heard) of HAMMER 2 from DragonFlyBSD!

              Comment


              • #8
                Originally posted by kylew77 View Post

                NetBSD and Illumos distros use the original Solaris implementation from OpenSolaris to the best of my knowledge. FreeBSD did too in versions prior to 13.0. Illumos's case makes sense to maintain bug for bug compatibility with Solaris, NetBSD I don't understand their model, also they have a really wonky ZFS on root setup. It is not as streamlined as FreeBSD. NetBSD is also cool because it isn't hedging the bet on just ZFS, they have a port in progress (read only last time I heard) of HAMMER 2 from DragonFlyBSD!
                Thanks for the explanation. So there's OpenZFS for FreeBSD and Linux and Solaris ZFS for Solaris, Illumos and NetBSD.
                Because the Wikipedia article is a bit confusing (https://en.wikipedia.org/wiki/OpenZFS) and seems to imply that Illumos and NetBSD also use OpenZFS.

                Comment


                • #9
                  Originally posted by Estranged1906 View Post
                  Because the Wikipedia article is a bit confusing (https://en.wikipedia.org/wiki/OpenZFS) and seems to imply that Illumos and NetBSD also use OpenZFS.
                  I'm for sure that Illumos does not use OpenZFS., and I am 90%+ fore sure NetBSD doesn't either.

                  Comment


                  • #10
                    Originally posted by kylew77 View Post

                    I'm for sure that Illumos does not use OpenZFS., and I am 90%+ fore sure NetBSD doesn't either.


                    Originally posted by illumos.org
                    The illumos project is part of the community of operating system projects that ships OpenZFS.


                    Originally posted by wiki.netbsd.org
                    • FreeBSD more or less imports code from openzfs and pushes back fixes. \todo Verify this.
                    • NetBSD has imported code from FreeBSD.

                    Comment

                    Working...
                    X