l4-hurd
[Top][All Lists]
Advanced

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

Re: Part 2: System Structure


From: Bas Wijnen
Subject: Re: Part 2: System Structure
Date: Thu, 18 May 2006 13:28:31 +0200
User-agent: Mutt/1.5.11+cvs20060403

On Thu, May 18, 2006 at 01:14:15PM +0200, Pierre THIERRY wrote:
> > I think for your examples there may have been some misunderstanding
> > about what a parent and a child was, though.
> 
> BTW, how do you define childness?

Oh, I thought this was clear by now.  Thanks for letting me know that it
wasn't. :-)

The parent is the process which puts the binary image into the memory and
makes the system call which turns it into a process (called exec() or
similar).  It is in the position to do anything it wants to the child just
before making that system call.  The constructor is simply trusted not to do
anything.

> I don't see how you end up saying the process is the child of the
> constructor... Except some authority, every resource given to the yield by
> the constructor comes from the requestor.  Which should then be considered
> the parent naturally.

Who pays for the resources is a different question.  Childness is for me
defined by who performs the system call.

Thanks,
Bas

-- 
I encourage people to send encrypted e-mail (see http://www.gnupg.org).
If you have problems reading my e-mail, use a better reader.
Please send the central message of e-mails as plain text
   in the message body, not as HTML and definitely not as MS Word.
Please do not use the MS Word format for attachments either.
For more information, see http://129.125.47.90/e-mail.html

Attachment: signature.asc
Description: Digital signature


reply via email to

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