• 3 Posts
  • 53 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle

  • 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.


  • F04118F@feddit.nltoLinux@lemmy.mlAnother help me choose a distro
    link
    fedilink
    arrow-up
    16
    arrow-down
    1
    ·
    19 days ago

    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!


  • 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.


  • F04118F@feddit.nltoSelfhosted@lemmy.worldKubernetes storage backends
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 month ago

    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.








  • The way I understand it, there’s 2 use cases for a VPN, with different concerns and providers:

    • having access to your private home network from anywhere, through an encrypted tunnel (Tailscale, Wireguard on the router, etc)
    • having your outgoing traffic to the internet go through an anonymized exit node so that your ISP can not watch or sell what you are doing (ProtonVPN, Mullvad VPN, etc)

    Is Tailscale fit for the second? I thought not, as the exit node is not an anonymized VPN server but one of your own machines.