• 0 Posts
  • 25 Comments
Joined 3 years ago
cake
Cake day: August 6th, 2023

help-circle



  • Memory leaks are more than possible in rust. Rust type system prevents things like free being called on an already free resource. It very much also allows not calling free even when nothing references things. It also makes things like arena allocation a fun endeavor compared to other systems languages. It’s not impossible just trickier. Rust isn’t a panacea, you would need something more like idris with its type system to programmatically enforce resources are freed at runtime during the compilation phase. But a fully dependent type system is very much a bleeding edge thing.









  • As a recently former hpc/supercomputer dork nfs scales really well. All this talk of encryption etc is weird you normally just do that at the link layer if you’re worried about security between systems. That and v4 to reduce some metadata chattiness and gtg. I’ve tried scaling ceph and s3 for latency on 100/200g links. By far NFS is easier than all the rest to scale. For a homelab? NFS and call it a day, all the clustering file systems will make you do a lot more work than just throwing hard into your nfs mount options and letting clients block io while you reboot. Which for home is probably easiest.




  • That’s rpm, suse Linux 1.0 was never built off the same source or installer that Redhat Linux was.

    Do you have a historical example where any suse distribution used redhat based source? As opensuse as I said only used the rpm package manager, it never used any other components of a redhat derived install.

    Source: I work there and can find zero redhat strings in any old source code from that era, the old greybeards took offense to the implication that suse was ever based on redhat other than using rpm which at the time was about it for packaging.

    All they did was start to use rpm instead of tar for packaging.