MaulingMonkey

I'd lean towards allowing it to be nondeterministic. Multiple syscalls to emulate POSIX semantics sounds slow - especially in the case of network attached storage - and perhaps inconsistently implemented...

That would have the effect of allowing self-imposed `unveil`-lite like behavior, by simply closing all FDs to root/parent directories outside of the chroot.

https://doc.rust-lang.org/nightly/cargo/commands/cargo-install.html has some misleading documentation under "Manifest Options" for `--frozen` / `--locked`: > The --frozen flag also prevents Cargo from attempting to access the network to determine if it is...

(I also suspect I landed on the "Manifest Options" section by searching the cargo install docs page for "--frozen", which caused me to skip over the earlier/better explaination of locking...

> likely most critically: -none-eabi arm platforms ARM [defers enum ABI choice to platform ABI](https://github.com/ARM-software/abi-aa/blob/05abf4f78dd7837774c4880fc0e6c01ce9e41ba8/aapcs32/aapcs32.rst#enumerated-types), but of course `*-none-*` has no platform ABI. As @geeklint discovered (see: [godbolt](https://godbolt.org/z/MajYq4o68) & [Rust...