You should maybe read about the use cases for deduplication before using it. Here’s one recent article:
https://despairlabs.com/blog/posts/2024-10-27-openzfs-dedup-is-good-dont-use-it/
If you mostly store legit Blu-ray rips, the answer is probably no, you should not use zfs deduplication.
Yeah… So I’m in Berlin, and in Germany the internet operators finally are building fiber everywhere. The provider who lays the fiber to our street is Deutsche Telekom, and they promise to pay everything: laying the fiber, bringing it to our house and bringing the fiber to every apartment for a two year monopoly on fiber internet after which it’s up for competition using their cables. What needs to happen next is our landlord (a Swiss company) and house management company to agree on these guys to come in, put little fiber dividers to every floor and drill a hole to the walls so we get the fiber cable to our apartment.
Of course this being Germany, they are very slow on agreeing on that, we might need to go to court and for sure we need to talk to our neighbors who own their apartments to push them a bit. I’d expect us to get the connection maybe before end of 2025. But eventually it will happen…
I am doing exactly the same as what the OP is doing. In addition to that, I will unify my beelink mini PC proxmox server and our old Intel atom NAS into one rack server with AMD EPYC, proxmox and truenas in a VM.
I sure hope our landlord and the Internet operator can agree on the operator finally bringing fiber cables to all apartments. Then I would have fast enough uplink to my homelab.
Graphene only works on Pixel phones. Graphene is more private and secure, but might be too many issues for people who do not care about such things that much. Lineage has better support for different phone models, and you can make it just like a normal Android OS, that just happens to provide updates for your phone years after the manufacturer stops sending them.
Neither of them is better than the other, it’s just about your priorities. Get Graphene if you have a Pixel and you value privacy and are willing to tinker with it a bit if some apps don’t work.
Add that China theme to the mix.
You’re welcome.
Not a sysadmin, but a programmer. My work machines have been:
Probably going to keep using NixOS. This is a very cool OS.
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…
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.
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 one of the most addictive games I’ve played. The good thing is that it is cheap and doesn’t have any microtransactions. And a lot of fun.
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?
Have you considered other distros? I’ve had lots of success with the immutable fedora variants, which offer great stability and NVIDIA drivers in the base system. If you need apt, you create a new Debian container in the box buddy and make that container be your default when opening a terminal.
Gnome variant: https://projectbluefin.io/
KDE variant: https://getaurora.dev/
Gaming variant: https://bazzite.gg/
They are all the same distro with different desktop setup and default apps. You can install one of them and seamlessly switch to another one without losing any data.