mvaralar

5 ms·

1. 1.▲
   by mvaralar 9mo ago

   Feel free to submit a PR I will happily accept it.
2. 2.▲
   by mvaralar 9mo ago

   Toro started in 2006 more or less. I lost the .org domain so I had to move to the .io.
3. 3.▲
   by mvaralar 9mo ago

   As far as you provide the bindings, you can compile it with an application built in any language. There are in the repo a few examples with C programs.
4. 4.▲
   by mvaralar 9mo ago

   > Both those "separations" is not something Toro provides on its own; the Toro unikernel would totally be under the control of the host, from what I can tell. That said, what Toro (or any unikernel, really) does is reduce the a
5. 5.▲
   by mvaralar 9mo ago

   I can add that. Thanks!
6. 6.▲
   by mvaralar 9mo ago

   Toro is just a library OS that allows you to build an application and deploy it as a VM without the OS. Toro acts as the OS. Different that other unikernels, Toro is not meant to be POSIX compliant. The idea is to provide an API that suits
7. 7.▲
   by mvaralar 9mo ago

   > Suppose you control the entire stack though, from the bare metal up. (Correct me if I'm wrong, but) Toro doesn't seem to run on real hardware, you have to run it atop QEMU or Firecracker. In that case, what difference does it