On Thu, Nov 13, 2014 at 12:44:12PM +0100, Justus Winter wrote:
> Well, the proc server registers for these notifications. I'll add
> this RPC to the process protocol:
This looks good to me. I like that it relies on the kernel for
security, but that it's also minimalist.
--
Richard Braun
Quoting Richard Braun (2014-11-13 12:25:14)
> On Thu, Nov 13, 2014 at 12:09:03PM +0100, Justus Winter wrote:
> > Possession of the privileged host control port, and it is only
> > possible to register for these notifications once.
>
> How does this recurse in the subhurd ?
Well, the proc server r
On Thu, Nov 13, 2014 at 12:09:03PM +0100, Justus Winter wrote:
> Possession of the privileged host control port, and it is only
> possible to register for these notifications once.
How does this recurse in the subhurd ?
--
Richard Braun
Quoting Richard Braun (2014-11-13 11:30:20)
> On Wed, Nov 12, 2014 at 04:49:07PM +0100, Justus Winter wrote:
> > Overall it's looking good, time to get the discussion going.
>
> What privilege is required to request these notifications ?
Possession of the privileged host control port, and it is o
On Wed, Nov 12, 2014 at 04:49:07PM +0100, Justus Winter wrote:
> Overall it's looking good, time to get the discussion going.
What privilege is required to request these notifications ?
--
Richard Braun
Hello,
I'm trying to get unprivileged Subhurds to work. The first part of
the puzzle is in fact a tiny kernel patch to provide a robust parental
relationship of tasks to userspace. Currently, /hurd/proc relies on
posixesque processes to call proc_child to form a process hierarchy.
I'
