Re: kernel command line

[Roland McGrath]

> Ah, yes.  I see my error now.

But just the one, eh?  I guess we'll have to keep working on you to attain
full repetence.

> Every task gets associated with it a "restricted name".  (Alternative
> name suggestions welcome.)  This is a send right, and I don't envision
> anyone ever sending messages on it.
> 
> Anyone who has the task port can fetch the restricted name port.  But
> only a privileged task can set the restricted name port.  A new task
> gets its restricted name port copied from its parent in task_create.
> 
> That seems sufficient for proc to do what it wants, and pretty simple.

What I proposed was nearly identical to this, but in my plan you need
host-priv to fetch the right as well as to set it.  I can't think off hand
of a reason it really matters, but it might be useful for proc to know that
the send rights it uses in this way are private capabilities that noone but
proc could ever have.