Comment by nine_k 18 hours ago So it's basically like tini (keep a single executable running), but in Rust? 2 comments nine_k Reply lrvick 17 hours ago Yep. The less C code in production the better. lrvick 14 hours ago Of note, it also will handle platform specific bring-up system calls, basic filesystem setup, etc, so it is much more suitable for embedded, server, or enclave use cases than tini, imo. It is mostly used for Nitro enclaves today.
lrvick 17 hours ago Yep. The less C code in production the better. lrvick 14 hours ago Of note, it also will handle platform specific bring-up system calls, basic filesystem setup, etc, so it is much more suitable for embedded, server, or enclave use cases than tini, imo. It is mostly used for Nitro enclaves today.
lrvick 14 hours ago Of note, it also will handle platform specific bring-up system calls, basic filesystem setup, etc, so it is much more suitable for embedded, server, or enclave use cases than tini, imo. It is mostly used for Nitro enclaves today.
Yep. The less C code in production the better.
Of note, it also will handle platform specific bring-up system calls, basic filesystem setup, etc, so it is much more suitable for embedded, server, or enclave use cases than tini, imo. It is mostly used for Nitro enclaves today.