this post was submitted on 30 Sep 2025
203 points (99.0% liked)
Linux
58904 readers
746 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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?
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/
...
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-ToolsYou certainly don’t have to use bcachefs. I love it but several of my systems will come off it Joe that it is out of the kernel. But not for technical reasons.
It is not that he changes were scary. Nobody had a problem with the changes. It was entirely process. It was “when” the changes were being submitted.
Kent always sent stuff in after the merge window. And when Linus rejected them, due to timing, Jent would throw a massive fit and start insulting everybody. Ironically he would complain about having to put up with “drama” from Linus.
So, Linus kicked him out.
Nothing to do with the code.