3 ms·
If you semi-trust your tool binaries enough not to do something silly like making syscalls directly, what about using the `LD_PRELOAD` equivalent to intercept `
by o11c 1y ago
If you semi-trust your tool binaries enough not to do something silly like making syscalls directly, what about using the `LD_PRELOAD` equivalent to intercept `open` etc.? (Yes there's a long tail in that "etc.")
Or does using Go ruin everything again?
(Also it seems like it should in principle be possible to keep the symlink forest around and only delete other files)
- eru 1y ago> Or does using Go ruin everything again? Go isn't the only language ecosystem that likes to make statically linked binaries. Rust, OCaml and Haskell etc also prefer this. Or am I missing something? I think dynamic linking is mainly popular in the C (and perhaps C++) world? And I guess for commonly interpreted languages like Python, more or less.
- _flux 1y agoRust, OCaml and Haskell (ghc) do dynamically links against libc by default, though. What they "statically link" is their own libraries.
- eru 1y agoYes. Though you can also make them statically link against libc. I think that's more common, if you use musl? In any case, I'm not sure all filesystem operations would come out of libc? (Especially if you use io_uring or other fancy io options.)