• 5 Posts
  • 236 Comments
Joined 2 years ago
cake
Cake day: June 24th, 2023

help-circle

  • 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















  • Honestly, I’ve had access to tons of Nvidia cards (1050, 1060, 1080, 3070, etc). All of them worked great for gaming whenever I tried in Debian or Ubuntu, using whatever drivers were latest at the time.

    The ONLY place I had issue was specific settings (HDR + 120hz over HDMI) in Bazzite. I wanted a new card back then anyway so I got an AMD. But I’ve heard their Nvidia image is great, now.



  • Pretend your running a live OS off a read-only USB, yet any changes (app installs, config changes, etc) you make are saved to the HD. A new version of the OS comes out, so you write a new ISO to your USB, and upon booting it, all you changes are applied on top.

    This is a simplistic view of immutable distros, but thwy wrk more like snapshots. It allows for rollback. So you install v1, then v2 is a newer snapshot of the base OS, v3 is another, always building.

    The catch is they often require apps to run under things like flatpak so you don’t have to alter the OS packages. Personally, I’m not a fan for a daily driver, but it’s great for distros like Bazzite.