• geneva_convenience@lemmy.ml
        link
        fedilink
        arrow-up
        10
        arrow-down
        2
        ·
        1 day ago

        Oracle funding doesn’t sound like a good thing at all since they’re basically CIA cloud ran by one of the most influential Zionists. But an unstable filesystem sounds even worse.

        • fmstrat@lemmy.nowsci.com
          link
          fedilink
          English
          arrow-up
          6
          arrow-down
          1
          ·
          17 hours ago

          Everyone always says “Companies should fund FOSS instead of spending money on big corpos!”, yet then this.

          It’s FOSS. It’s auditable. Funding is a good thing.

          • HiddenLayer555@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            31 minutes ago

            Google managed to backdoor Linux and Firefox with their “FOSS” libWebp. Took literally years until some security researcher not affiliated with any of them found the bug by chance and made a public report, and by then it had already been explited by NSO for ages. If they had worked for Google (or Apple/Microsoft/Amazon/any of the other corporations that just imported Google’s libWebp code without looking at it) they would have gotten silenced and the exploit would still be there as a gift to Israel. Turns out just because it’s auditable doesn’t mean it gets audited before it’s too late.

          • geneva_convenience@lemmy.ml
            link
            fedilink
            arrow-up
            2
            arrow-down
            1
            ·
            17 hours ago

            That’s true, but we also know that funding can come with stipulations. Oracle is an especially sketchy company.

            But that counts for all big tech I guess.

            • Auli@lemmy.ca
              link
              fedilink
              English
              arrow-up
              1
              ·
              7 hours ago

              So not using Linux at all then? Most of the development is paid for by big tech.

            • fmstrat@lemmy.nowsci.com
              link
              fedilink
              English
              arrow-up
              4
              ·
              14 hours ago

              In this situation it works well, IMO. For some more context, ZFS was created by Sun (FOSS). Oacle bought them and built Oracle ZFS out of it. OpenZFS forked at that point from Sun code, and that’s what we use in Linux/etc. The Oracle variant supplies support to the FOSS variant. So Oracle has no control over OpenZFS.

      • LeFantome@programming.dev
        link
        fedilink
        arrow-up
        3
        arrow-down
        4
        ·
        1 day ago

        “Major stability problems”. Hilarious. Get one person that actually uses bcachefs to confirm that. Good luck.

        Kent has stability problems and drives me crazy but that is a baseless hit piece. Bcachefs is a solid fs.

        Linus has not pushed back on the quality of bcachefs other than to say it is too unproven to rely on (too new). What Linus objected to was the process violations and the attitude of the lead developer.

        Given how much Linus and the other LKML devs wanted to get rid of Kent, the fact that it took so long to dump him tells us that they really wanted to keep bcachefs (the technology).

        There may have been more data loss bugs in btrfs and even OpenZFS than bcachefs since it was added to the kernel. I have many bcachefs systems. I have one btrfs system. Guess which one has caused me problems.

        • fmstrat@lemmy.nowsci.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          17 hours ago

          Fair enough on “major”. Edited that. But it has stability issues that aren’t handled well enough for RCs, so it’s not a hit piece to state that fact. Those stability issues may come from it being new, but it’s still an issue. Saying it’s because they want to “get rid of Kent” is just as much of a hit piece, too.

          • LeFantome@programming.dev
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            9 hours ago

            The dev is unstable. And he made the kernel process chaotic. But the filesystem itself is pretty solid. Do you have a link to stability issues?

            • fmstrat@lemmy.nowsci.com
              link
              fedilink
              English
              arrow-up
              1
              ·
              8 hours ago

              My understanding is the stability risks come from active development additions vs “fixes” during that stage of the development cycle.

              https://linuxiac.com/torvalds-expresses-regret-over-merging-bcachefs-into-kernel/

              Simply put, only small bug fixes are allowed after the post-merge phase to integrate changes into the current kernel cycle. However, Overstreet’s PR included more than just fixes; it continued to develop new features, which always carry risks. That’s why Torvalds was unhappy with it. As a result, the changes were rejected.

              Currently, the file system is being actively developed. Although it shows great potential with impressive features and strong data reliability, it’s not yet stable enough to be adopted by major Linux distributions as a proven and reliable solution.

              YMMV, but my production systems will stick with ZFS since it’s kernel release updates are clear when there are “upgrades” vs “updates”, as you do those manually when it alerts you.

              “Stable” in this context doesnt mean “your PC will definately crash and you will lose data!”, bcachefs is well past that. It means that the development is too active to be considered production ready since the code changes are too large to confirm the scary bit won’t happen (as much as can be).

              Even JC threw in the towel on bcachefs-tools due to this: https://www.phoronix.com/news/Debian-Orphans-Bcachefs-Tools

    • wurstgulasch3000@feddit.org
      link
      fedilink
      arrow-up
      14
      arrow-down
      2
      ·
      2 days ago

      Yes I’m asking for the reason why you think this development is good. It seemed to me like it could have worked out if they talked it out and could have added something of value to the OS

        • patatahooligan@lemmy.world
          link
          fedilink
          arrow-up
          15
          arrow-down
          1
          ·
          2 days ago

          There’s no reason to be rude and insulting. It doesn’t make the other person look lazy; it just makes you look bad, especially when you end up being wrong because you didn’t do any research either. The article is garbage. It’s obviously written by someone who wants to talk about why they don’t like bcachefs, which would be fine, but they make it look like that’s why Linus wanted to remove bcachefs, which is a blatant lie.

          Despite this, it has become clear that BcacheFS is rather unstable, with frequent and extensive patches being submitted to the point where [Linus Torvalds] in August of last year pushed back against it, as well as expressing regret for merging BcacheFS into mainline Linux.

          But if we click on the article’s own source in the quote we see the message (emphasis mine):

          Yeah, no, enough is enough. The last pull was already big.

          This is too big, it touches non-bcachefs stuff, and it’s not even remotely some kind of regression.

          At some point “fix something” just turns into development, and this is that point.

          Nobody sane uses bcachefs and expects it to be stable, so every single user is an experimental site.

          The bcachefs patches have become these kinds of "lots of development during the release cycles rather than before it", to the point where I’m starting to regret merging bcachefs.

          If bcachefs can’t work sanely within the normal upstream kernel release schedule, maybe it shouldn’t be in the normal upstream kernel.

          This is getting beyond ridiculous.

          Stability has absolutely nothing to do with it. On the contrary, bcachefs is explicitly expected to be unstable. The entire thing is about the developer, Kent Overstreet, refusing to follow the linux development schedule and pushing features during a period where strictly bug fixes are allowed. This point is reiterated in the rest of the thread if anyone is having doubts about whether it is stated clearly enough in the above message alone.

        • nixon@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          52
          arrow-down
          3
          ·
          2 days ago

          It’s not lazy to ask someone who seems to know something about the topic within a discussion thread about said topic. You know more than I do on this.

          I understand how you may not want to take the time to answer someone’s question but also you could have replied with the link you eventually did instead of saying “Seriously?” Within the context of calling others lazy you could also qualify under the same term since you took the time to respond but not with the answer.

          With search being what it is nowadays I wouldn’t know if I am getting a good result to find out the answer since it is of a technical and specific nature I may or may not even know if I am familiar with to begin with. It could take me much longer to figure it out, or I will give up and not be interested in finding out more about a field you seem to have an interest and knowledge about and I am demonstrating I want to know more about.

          I think it is fair to ask for more information from someone who shows more expertise in the topic before searching.

        • wurstgulasch3000@feddit.org
          link
          fedilink
          arrow-up
          18
          arrow-down
          3
          ·
          edit-2
          2 days ago

          I’ve heard about this and wanted to hear your opinion on it because you seemed to have gotten to another conclusion than I have. But it seems that you’re not interested in discussing so I’m no longer interested