Alt account of @Badabinski

Just a sweaty nerd interested in software, home automation, emotional issues, and polite discourse about all of the above.

  • 0 Posts
  • 14 Comments
Joined 2 months ago
cake
Cake day: June 9th, 2024

help-circle



  • The tiered storage stuff is pretty cool. You can say “I want this data on this disk, so if I get a cache miss from a faster disk/RAM it’ll come from this other disk first.”

    I believe it also has some interesting ways of handling redundancy like erasure coding, and I thiiiink it does some kind of byte-level deduplication? I don’t know if that’s implemented or is even still planned, but I remember being quite excited for it. It was supposed to be dedupe without all of the hideous drawbacks that things like ZFS dedupe have.

    EDIT: deduplication is absolutely not a thing yet. I don’t know if it’s still on the roadmap.

    EDIT: Erasure coding is deffo implemented, however.


  • Badabinski@kbin.earthtoLinux@lemmy.mlHyprland is now fully independent!
    link
    fedilink
    arrow-up
    62
    arrow-down
    4
    ·
    edit-2
    24 days ago

    What if you need to file a bug? What if you have a question on the config that’s not easily answered by the docs? If you never, ever find bugs and never, ever have questions, then sure, separate the two. There are genuinely people like that, but they’re not common. If you’re one of them, then I’m genuinely glad for you.

    My opinion is this: You use software. You don’t use people, but you sure as hell rely on them.





  • The other person may have responded with a fair amount of hostility, but they’re absolutely correct. I run Kubernetes clusters hosting millions of containers across hundreds of thousands of VMs at my job, and OOMKills are just a fact of life. Apps will leak memory, and you’re powerless to fix it unless you’re willing to debug the app and fix the leak. It’s better for the container to run out of memory and trigger a cgroup-scoped OOM kill. A system-wide OOM kill will murder the things you love, shit in your hat, and lick your face like David Tennant licked Krysten Ritter.




  • I always just derive the interface name from first principles. Like, if I want to know which interface will be used to get out to the internet in a script, I’ll just find the one that’s L2 adjacent with the default gateway. If I’m given an egress or cidr, I’ll just find the interface that has that IP. Modern iproute2 has a JSON output option which makes getting this information pretty trivial. Doing that means that it doesn’t matter what scheme your OS is using.

    I personally prefer the persistent names for Ethernet, although I don’t like them for WiFi. Luckily, it seems like my wireless adapter always just ends up as wlan0. I’m not sure why that’s the case, but it works out well in the end for me.