[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: kernel command line

From: Thomas Bushnell, BSG
Subject: Re: kernel command line
Date: 18 May 2001 10:54:50 -0700
User-agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7

Roland McGrath <roland@gnu.org> writes:

> I have been assuming that in your proposal task_create completes without
> waiting for this notification to be received and processed.  If the
> notification is a message containing the task port of the creator task,
> then this will arrive as MACH_PORT_DEAD if the creator task dies first, no?

Ah, yes.  I see my error now.

Then I think an inheritance scheme is probably best.

How about the following:

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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]