For sure. I would say if you run a distro like Arch, using it without cow filesystem and snapshots is not a good idea… You can even integrate snapshots with pacman and bootloader.
I’ve been running nixos for so long, that I don’t really need snapshots. You can always boot to the previous state if needed.
If you write software and run tests against a database, I’d avoid having the docker volumes on btrfs pool. The performance is not great.
ZFS is still the de-facto standard of a reliable filesystem. It’s super stable, and annoyingly strict on what you can do with it. Their Raid5 and Raid6 support are the only available software raids in those levels that are guaranteed to not eat your data. I’ve run a TrueNAS server with Raid6 for years now, with absolutely no issues and tens of terabytes of data.
But, these copy on write filesystems such as ZFS or btrfs are not great for all purposes. For example running a Postgres server on any CoW filesystem will require a lot of tweaking to get reasonable speeds with the database. It’s doable, but it’s a lot of settings to change.
About the code quality of Linux filesystems, Kent Overstreet, the author of the next new CoW filesystem bcachefs, has a good write-up of the ups and downs:
- ext4, which works - mostly - but is showing its age. The codebase terrifies most filesystem developers who have had to work on it, and heavy users still run into terrifying performance and data corruption bugs with frightening regularity. The general opinion of filesystem developers is that it’s a miracle it works as well as it does, and ext4’s best feature is its fsck (which does indeed work miracles).
- xfs, which is reliable and robust but still fundamentally a classical design - it’s designed around update in place, not copy on write (COW). As someone who’s both read and written quite a bit of filesystem code, the xfs developers (and Dave Chinner in particular) routinely impress me with just how rigorous their code is - the quality of the xfs code is genuinely head and shoulders above any other upstream filesystem. Unfortunately, there is a long list of very desirable features that are not really possible in a non COW filesystem, and it is generally recognized that xfs will not be the vehicle for those features.
- btrfs, which was supposed to be Linux’s next generation COW filesystem - Linux’s answer to zfs. Unfortunately, too much code was written too quickly without focusing on getting the core design correct first, and now it has too many design mistakes baked into the on disk format and an enormous, messy codebase - bigger that xfs. It’s taken far too long to stabilize as well - poisoning the well for future filesystems because too many people were burned on btrfs, repeatedly (e.g. Fedora’s tried to switch to btrfs multiple times and had to switch at the last minute, and server vendors who years ago hoped to one day roll out btrfs are now quietly migrating to xfs instead).
- zfs, to which we all owe a debt for showing us what could be done in a COW filesystem, but is never going to be a first class citizen on Linux. Also, they made certain design compromises that I can’t fault them for - but it’s possible to better. (Primarily, zfs is block based, not extent based, whereas all other modern filesystems have been extent based for years: the reason they did this is that extents plus snapshots are really hard).
I started evaluating bcachefs in my main workstation when it arrived to the stable kernels. It can do pretty good raid-1 with encryption and compression. This combination is not really available integrated to the filesystem in anywhere else but zfs. And zfs doesn’t work with all the kernels, which prevents updating to the latest and greatest. It is already a pretty usable system, and in a few years will probably take the crown as the default filesystem in mainstream distros.
You can also very easily run the bridges yourself if you don’t trust them. I do so in my homelab, it was 10 minutes of work setting it all up. Super stable, and e2e from my side.
For me their value proposition is their new beta android app which is the best Android matrix client, and their quite fast matrix server. That might change in the future when conduit is fast enough…
This is my nix config for our brother scanner. Just run any Linux scanner utility and it just works:
https://git.sr.ht/~pimeys/nixos/tree/main/item/core/home-services.nix#L10
I borrowed an installation CD from the local library around 1998. It was RedHat 5.x, and I started messing around with it due to me being interested in alternative operating systems. Before it, I had OS/2 Warp 3.0 in our IBM Pentium 100 MHz family computer which didn’t really do it for me to be honest.
It took weeks to get anything working with Linux. I went to the library, borrowing books. In our middle school we had an internet connection, so I utilized it to learn how to configure modelines correctly to get X11 running.
When it did finally run, the default window manager was FVWM95, almost like Windows 95!
I used OSX a few years in the power PC times, just to switch back to Linux around 2008.
Edit: my real love for Linux started when I got Debian running. RedHat didn’t have anything comparable to apt those days. You needed to download RPM packages manually with all the dependencies, while apt just worked with one command.
The first 20 minutes I got transaction errors from the order, then it went through, I got charged and… a transaction error. Made my second order without PayPal, paid the second time and a 1TB model is coming for Christmas. The second payment was returned a few hours later.
This is our first Steam Deck, never tried one. Goes to Christmas wrapping immediately and we open it on the 25th.
Yep. I’m from Europe and of course this is kind of not understanding American culture enough to not compare different qualities of mac&cheese. That reminds me, we came back home from the US and had mac&cheese in a restaurant in Germany. They served us Kraft with fried onions and parmesan flakes on top. At that moment I understood Germans will never understand American cuisine…
Is there an easy way to get this version as a normal citizen? I remember needing Windows 10 in my previous job a few times a year, and we spent quite a while with our office manager to get me a license and get the LTSC version of Windows installed with the key. It worked eventually, but was definitely trickier than a normal Windows installation.
That to be said, my partner still uses that Windows version and it is definitely the right thing to use, if needing Windows.
There’s a pretty vibrant open source diabetes community in Germany. Some tools such as AndroidAPS and xDrip have been existing for a long time and work together with many pump and CGM models available through the health insurance. GPL-3.0 licensed.
At least these were very beneficial for me, A1c went down from 7.5 to 5.5% without many hypos. You have to compile AndroidAPS by yourself due to distributing binaries would not be legal. It requires some knowledge, but for my partner not needing to call an ambulance ever again when I have a nightly hypo, that is a big win.
No nightly hypos for the past five years I’ve been using these tools…
I really liked Silmarillion when I was a teenager. But, I was also an avid reader and read some really serious literature back in the days. It’s not like a manual, it’s just having so many characters and timelines going on. It’s very interesting, if you’re interested on the history of the Middle Earth and its characters.
But, not for everybody for sure. Not like Lord of the Rings, which is a real feel good sick day book to read.
Plex and plexamp are quite good. Jellyfin and finamp too.