>I dont understand. Why can't the capability device be put directly
>into 9vx? Doesn't the 9vx "kernel" have its own notion of
>user id for each of the processes it hosts independant of the
>underlying unix user id? I thought only select parts of the
>system such as the unix file server cared about
of cpu.c makes use of the kernel cap device via a call to the
auth_chuid function, and the cap device is not available in 9vx,
probably due to the single-user nature of it as a hosted environment.
I dont understand. Why can't the capability device be put directly
into 9vx? Doesn't the 9vx "kerne
A brief note on 9vx and cpu, which might also be relevant for a few
other things. Using 9vx as a cpu server has been mentioned a few
times, but my attempts to actually get this working met with failure
initially. I believe I have tracked down the issue - the remoteside()
of cpu.c makes use of the k