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

help-circle



  • mitchtytoPeople Mastodon@quokk.austay woke
    link
    fedilink
    arrow-up
    1
    ·
    8 days ago

    So cite which documents support the claim. If it’s so easy it shouldn’t be hard to do. You’re basically replying to a statement of that’s illegal and being asked to cite what is illegal by saying reference all of the legal caselaw. It may be technically correct but it’s useless. There is a reason academics and legal scholars say reference paragraph x of book y etc. if you can’t provide easy examples why would I buy your claim?

    Put up or shut up.




  • mitchtytolinuxmemes@lemmy.worldKiller
    link
    fedilink
    arrow-up
    2
    ·
    29 days ago

    Doesn’t do much if the process is in uninterruptible I/o. Kill can’t do much against syscalls that aren’t returning, you’ll be rebooting. You can try this https://github.com/mitchty/nix/blob/shenanigans/src/evilkill.sh but it’s not guaranteed to work. It’s just trying to force the process to exit(), but it doesn’t always work and can’t. All that script amounts to is attaching a debugger and executing assembly to mimic exit. I’ll say 60% of the time it works 100% of the time when kill doesn’t.











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