Not a sysadmin, but a programmer. My work machines have been:

• 2003-2008 Windows 7
• 2008-2011 Ubuntu
• 2011-2019 Arch
• 2019-2024 NixOS

Probably going to keep using NixOS. This is a very cool OS.

A big monitor with 100% AdobeRGB is going to be very very expensive. And if you want it to be 65", you just can’t find them…

And it is a monitor, meant to be watched from a close distance. It will not be such a great experience for movies and such.

That is correct.

https://www.phoronix.com/review/amd-ryzen-9950x-9900x

A random hacker news comment. I’m in EU, where this kind of tracking is not legal, so I cannot validate…

If it is a Samsung tv, they have been automatically connecting to any open wifi, maybe your neighbor has one. And there goes the data.

Avoid Samsung.

I run invidious at home on my proxmox server. The server is available everywhere with tailscale, so I can use it even when travelling. If Google ever blocks this, nobody at home can watch youtube anymore…

Yeah. He is pretty horrible. What surprised me though is his daughter’s film company has a pretty solid track record on quality movies and tv series:

https://en.m.wikipedia.org/wiki/Annapurna_Pictures

But yeah, Larry Elison sucks…

Very cool. When this really works, I might install Haiku to my fun and play laptop…

Does Firefox work with Haiku already?

His job is to not get the maintainers to agree, but his job definitely is to bark a bit if somebody behaves like Ted.

It might even be Rust is not meant for Linux kernel and it will never happen. Or it happens in the driver layers, but stays out from the core. We do not know yet. The concern Ted is raising is definitely valid: if the C APIs change, people who work daily in the C code cannot spent cycles fixing the Rust APIs. These people have their day jobs which pays them to maintain these subsystems, and it is at least not yet clear will these employers fund rewriting anything in Rust. There are tens of filesystems in Linux, with lifetimes passing around that are not documented and might not work in Rust.

Note: I’m a Rust dev for the past 10 years, and I follow this discussion with high interest.

Yeah. Isn’t it funny that the most popular file system in the world has such a codebase, and it is not even well documented how it works!

I have my reasons to choose XFS or bcachefs with my machines.

Yes and no. Linus can yell to people and he does, he can force his say as he has been recently doing by expecting sched_ext to land in 6.12. BUT. Linux is a bazaar, it’s so big and there are so many different factions forcing them to do anything is going to take a long time. Lots of different teams are working on Linux, with their own priorities.

The borrow checker is exactly what the kernel needs.

Ted is the maintainer of ext4 and there are not many people in the world who understand this code.

For Rust to succeed, it has to get the subsystem maintainers to agree. It is going to be many years of petting very angry bobcats…

And that is not even the worst I’ve heard, makes you a bit numb if you follow LKML.

Me neither, but the risk is there and well documented.

The point was, ZFS is not great as your normal laptop/workstation filesystem. It kind of requires a certain setup, can be slow in certain kinds of workflows, expects disks of same size and is never available immediately for the latest kernel version. Nowadays you actually can add more disks to a pool, but for a very long time you needed to build a new one. Adding a larger disk to a pool will still not resize it, untill all the disks are replaced.

It shines with steady and stable raid arrays, which are designed to a certain size and never touched after they are built. I would never use it in my workstation, and this is the point where bcachefs gets interesting.

Signal always responds to authorities when they ask for data, and they give them all they have: the day they registered, their phone number and the timestamp they last used the app.

Telegram has unencrypted channels of drug dealing, and what I heard is a lot of illegal porn too. The authorities want information on certain users there and Telegram doesn’t comply. This is directly against the law Signal is not breaking, because they always send all the data they have to the law enforcement.

But scrub is not fsck. It just goes through the checksums and corrects if needed. That’s why you need ECC ram so the checksums are always correct. If you get any other issues with the fs, like a power off when syncing a raidz2, there is a chance of an error that scrub cannot fix. Fsck does many other things to fix a filesystem…

So basically a typical zfs installation is with UPS, and I would avoid using it on my laptop just because it kind of needs ECC ram and you should always unmount it cleanly.

This is the spot where bcachefs comes into place. It will implement whatever we love about zfs, but also be kind of feasible for mobile devices. And its fsck is pretty good already, it even gets online checks in 6.11.

Don’t get me wrong, my NAS has and will have zfs because it just works and I don’t usually need to touch it. The NAS sits next to UPS…

It is only in TLS where you have to disable compression, not in HTTP.

https://security.stackexchange.com/questions/19911/crime-how-to-beat-the-beast-successor/19914#19914

Could you explain how a CRIME attack can be done to a disk?

I mean… If you have a ton of raw photos in one directory, you can enable the highest compression rate with zstd to it. Every other directory has lz4 with the fastest compression. Your pics take much less space, but the directory will be slower to read and write.

For me the reason was that I wanted encryption, raid1 and compression with a mainlined filesystem to my workstation. Btrfs doesn’t have encryption, so you need to do it with luks to an mdadm raid, and build btrfs on top of that. Luks on mdadm raid is known to be slow, and in general not a great idea.

ZFS has raid levels, encryption and compression, but doesn’t have fsck. So you better have an UPS for your workstation for electric outages. If you do not unmount a ZFS volume cleanly, there’s a risk of data loss. ZFS also has a weird license, so you will never get it with mainline Linux kernel. And if you install the module separately, you’re not able to update to the latest kernel before ZFS supports it.

Bcachefs has all of this. And it’s supposed to be faster than ZFS and btrfs. In a few years it can really be the golden Linux filesystem recommended for everybody. I sure hope Kent gets some more help and stops picking fights with Linus before that.