I don't agree with /u/red-crayon-scribbles ' approach to memory safety, but what you're saying isn't entirely true either.
It is possible to manipulate memory in ways that do not conform to Rust's lifecycle/ownership model. In theory, this can even be done correctly.
The problem is that in practice, this leads to the following, many of which were committed by some of the most highly skilled C developers alive, including major kernel contributors:
I just finished Crysis and Crysis: Warhead. Crysis took the c1launcher mod to start, Warhead just needed the env vars.
Hope I'll have the energy to dive back into Death Stranding soon. If not, I'll have another shot at MGS1. Last time I got to the sniper duel (on my phone with RetroArch and an old Xbox controller) and then when I got my Deck, the save refused to load. Been long enough that I wouldn't mind starting over.
I never played the original MGS series, first I got into it was MGS: Peace Walker on PSP, absolutely loved it, got hundreds of hours in it, then did a bit of MGS V but never finished that either.
If selfhosting the family chat is not a goal in itself and it's about privacy or being independent from big tech, just take the loss and go to Signal. Much smoother experience than any self-hosted messenger can provide for now.
If Mint works for you, just stick with it. No need to try a different distribution to compare. You'll know when you need it.
I would only go to Fedora if you need it. For example newer drivers (kernel, mesa). Don't go change the kernel and/or mesa on a distribution, probably better to switch at that point. Or if you need KDE or GNOME for some reason. Wayland is disabled in Mint by default, but can be enabled. It's been over a year IIRC since they added experimental Wayland support so it may be fine by now.
Differences between Linux distributions are exaggerated.
Mint is a great choice, it is very stable, and it really holds your hand via the Software Center.
However, stable also means old: it does not support the latest hardware.
If you have hardware that released after (rough estimate) April 2024, consider something based on Fedora, such as Bazzite, instead. It comes with modern drivers and should support modern hardware much better.
keep it on cache since I do a lot of code compilation, but I will usually switch it to frequency for gaming and stuff.
Isn't gaming the most cache-heavy CPU workload there is? The X3D CPUs have consistently topped gaming benchmarks, even outperforming much more modern CPUs that lack 3D cache.
I'd sooner do it the other way around: frequency for compiling, rendering, transcoding, etc. Cache for gaming!
Yep, and then there's probably a good number of people who have no idea of threat modelling who just copy those actions to say they have "good privacy".
The problem with non-PLP drives is that Rook-Ceph will insist that its writes get done in a way that is safe wrt power loss.
For regular consumer drives, that means it has to wait for the cache to be flushed, which takes aaaages (milliseconds!!) and that can cause all kinds of issues.
PLP drives have a cache that is safe in the event of power loss, and thus Rook-Ceph is happy to write to cache and consider the operation done.
Again, 1Gb network is not a big deal, not using PLP drives could cause issues.
If you don't need volsync and don't need ReadWriteMany, just use Longhorn with its builtin backup system and call it a day.
I tried Longhorn, and ended up concluding that it would not work reliably with Volsync. Volsync (for automatic volume restore on cluster rebuild) is a must for me.
I plan on installing Rook-Ceph. I'm also on 1Gb/s network, so it won't be fast, but many fellow K8s home opsers are confident it will work.
Rook-ceph does need SSDs with Power Loss Protection (PLP), or it will get extremelly slow (latency). Bandwidth is not as much of an issue.
Find some used Samsung PM or SM models, they aren't expensive.
Longhorn isn't fussy about consumer SSDs and has its own built-in backup system. It's not good at ReadWriteMany volumes, but it sounds like you won't need ReadWriteMany. I suggest you don't bother with Rook-Ceph yet, as it's very complex.
Also, join the Home Operations community if you have a Discord account, it's full of k8s homelabbers.
There will be tougher usecases to migrate. Which, depends on how you use Google.
For example, I've never read Google News but am having trouble replacing Keep for synced, widgeted notes (groceries etc) on phone, as well as GSheets for synced, collaborative excel-like sheets with good mobile UX.
Also, I would bundle mail and calendar in one (it's a single button to import both in Proton and those services are tightly coupled) and check your duplicate browser/chrome mentions
/etc/systemd/system/mnt-nfs.mount
[Unit] Description=Mount NFS Share [Mount] What=server:exported_path Where=/mnt/nfs_share Type=nfs Options=_netdev,auto,rw [Install] WantedBy=multi-user.target