Gabriel Parmer

@RobertGiff You should likely have a look at the build system stuff to see if it is compatible with the RK stuff.

An important way to look a this problem is with respect to access rights. For example, for Option 3, if a component has a thread capability, then it would (without...

I've been thinking about this a lot recently, but from a different direction: How can we consolidate the control-flow operations of the kernel into the smallest number of orthogonal abstractions,...

Some side-effects of doing this that *might* make kernel code simpler: - `asnd`s are almost just `thd` caps, but they include two `thd` caps, the second to address the `tcap`....

@Others: this is awesome. We've been iterating on these types of issues for a long time, and this is a good forcing function to continue with that. > - make...

Suggested new format: ``` . ├── docs └── src ├── components │   ├── apps │   │   ├── f │   │   ├── g │   │   └── h │   ├── extern │  ...

To add more detail: The three-step protocol for capability activation is meant to address races between two capability activations in the same slot. Currently, the code in the repo simply...

Rephrasing this: We should remove the thread id and naming logic from the kernel.

@hjaensch7 Can you reproduce this, and see if `make config` was not run?h

I worry about using apt-get to install cargo as it seems like much of the rust world uses rustup to install and update. (See https://doc.rust-lang.org/cargo/getting-started/installation.html). I can only imagine this...