this post was submitted on 12 Sep 2025
46 points (96.0% liked)

Linux

10948 readers
639 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] just_another_person@lemmy.world -4 points 3 months ago (1 children)

Pathetic ๐Ÿคฃ

It's like you're a wannabe a troll, but you're incapable of really hammering home the pendantic nature of facile incel ricochet insults.

Whenever you want to give up and admit you're wrong, I'll be here ignoring you.

[โ€“] stephen01king@piefed.zip 2 points 3 months ago (1 children)

Unfortunately, the troll here is the one who can't be bothered to read people's comment before replying. Try again.

[โ€“] mzan@programming.dev 1 points 3 months ago

An inspirational reply of koverstreet https://lwn.net/Articles/1028572/ He is focused on solving all bug reports, and in iterating bcachefs in the faster way possible. It is a sort of implicit contract with its users base: "you are using bcachefs in production/real-world despite it is experimental, and I will support you restoring files and improving code".

So, I can understand why he doesn't like waiting too much before releasing improvements. The Linux kenernel release cycle can transform weeks in months if some bug-fixes requires new features or refactorings, like in case of a new file system. I'm sorry that him and Linux maintainers didn't find a good approach.

BTW, I used bcachefs for 1-2 years with 3 HDD and 1 SSD in cache. It supported this usage scenario better than ZFS for a desktop/workstation like mine setting.