It’s initial bcachefs anyway, which doesn’t support all features yet and still needs a lot of work. I wouldn’t run bcachefs yet on any system where an LTS kernel is necessary.
Firefox now supports a setting (in Preferences → Privacy & Security) to enable Global Privacy Control. With this opt-in feature, Firefox informs the websites that the user doesn’t want their data to be shared or sold.
This sounds like Do Not Track revisited. The only difference that I can find (only skimmed the website) is, that there seems to be some legal support for this in the state of California.
Now you can exercise your legal privacy rights in one step via Global Privacy Control (GPC), required under the California Consumer Protection Act (CCPA).
I wonder:
How does this differ from DNT?
Does this this have any real chance to take off? From what I’ve heard, DNT has been rather counterproductive as it can be used to fingerprint users.
Features include caching,[4] full file-system encryption using the ChaCha20 and Poly1305 algorithms,[5] native compression[4] via LZ4, gzip[6] and Zstandard,[7] snapshots,[4] CRC-32C and 64-bit checksumming.[3] It can span block devices, including in RAID configurations.
The main takeaway from the article is that the developer’s name is Kent Overstreet, who beat his bitter rival Surrey Underpath, who are both canonically related to famed developer Cornwall Midroad.
As someone else said, it’s similar to btrfs. bcachefs has a lot of functional overlap with btrfs, which is great. There have also been a few benchmarks showing that bcachesfs is faster for some situations (cold-cache warming, IIRC). One of the big advantages over btrfs is that bcachefs’s RAID is more robust - several of btrfs’s RAID levels have been marked as experimental and prone to data loss, for years. There’s been improvement in btrfs RAID lately; the skeptic in me believes this is directly a result of pressure from bcachefs, which is in a position to become a favored fs in Linux.
I really hope it would be a working one, not like xfs where your files may just disappear with no trace (never on Irix, never on any other fs) or like btrfs which may just suddenly go read only and be dead on reboot with no fsck and all data unreachable.
How hard is it to get the basics right? Doesn’t matter how much rice there is if it keeps blowing up.
Me too. I’ve run 30 years with ext and bsd filesystems with no failure. Many years with various UNIX native fs as well. But Linux xfs, reiserfs, btrfs all have resulted in catastrophic failure within a year on several machines. They’re permanently off my list, but I have some hope that someone will get a new fs right.
A lot of the time it obviously takes a little while for userland tools to catch up and for distros to include both the new kernel and userland tools for it into their latest versions but once that is done average users certainly do notice differences. Literally all the features that are talked about a lot like BPF or io_uring or all the features that make containers possible were introduced in a kernel release at some point.
While I don’t know how, I do know that there is a way to have mesa for most things while having AMF encoder for encoding. Nobara has this set up out of the box so there is some way. Maybe you could search for it using a search engine
Does it really? I know when I looked into it a bit ago the main dev for nobara had a video about how to install it and use it but it didn’t let you split that out. You could quickly change back and forth between mesa and amdgpu but if you tried to run amf with mesa it would hard lock and crash
It has been some time since I tried out Nobara so I might be wrong. I just remember that Nobara page lists having amf encoder support out of the box as a feature
9to5linux.com
Active