Jim Newsome

> Is there a way to tell Cargo to enforce this? For example if you (or a dependency) do extern crate std, I'm assuming it will automatically link in libc?...

[cargo nono](https://github.com/hobofan/cargo-nono) is the tool I was thinking of for validating `std` wasn't pulled in: ``` $ cargo nono check cnostd: SUCCESS linux-syscall: SUCCESS ``` [cargo tree](https://doc.rust-lang.org/cargo/commands/cargo-tree.html) is also helpful,...

Making the shim statically linked would also simplify injecting it into an executable without `LD_PRELOAD`; i.e. [supporting statically linked executables](https://github.com/shadow/shadow/issues/1839)

> might also allow us to remove the Docker [requirements](https://shadow.github.io/docs/guide/supported_platforms.html#docker) for increasing the size of the /dev/shm mount (these errors have been confusing and difficult to debug in the past)....

Good point. I suppose we could add a header in the file itself with a unique ID that's also included in the serialized handle.

Unassigned myself since @RWails is working on a Rust rewrite of this code

Do we want to make it easier to specify "end time - x" before adding `kill` to our examples? Or is that too much scope creep? e.g. ``` processes: -...

To be clear; I'm filing this to capture the results of discussion and investigation into what it would take to support this. I think we will eventually want to do...

We've made some headway: > Fix shadow's TCP implementation to be compatible with onionmasq's (e.g. per-byte sequence numbers; correct checksums...) I think this is fixed in the new (experimental) rust...

> @sporksmith The unwrap here is panicking from ESRCH, so the thread must not exist anymore. Should this loop and try other threads instead of panicking? Maybe, but I'd like...