[coyotos-dev] Thoughts on (non)persistence

Marcus Sundman sundman at iki.fi
Fri Jan 21 16:15:49 EST 2005


On Friday 21 January 2005 23:04, Jonathan Adams wrote:
> On Fri, 21 Jan 2005 22:55:50 +0200, Marcus Sundman <sundman at iki.fi> wrote:
> > On Friday 21 January 2005 22:02, Jonathan S. Shapiro wrote:
> > >   1. If processes are not persistent, how can we contrive to give
> > >      them some form of unique identity that survives system restart?
> >
> > Umm.. If the only relevant difference between two instances (processes)
> > of a program is the sets of capabilities they have then I see no
> > problem. If a process dies (e.g. because of a crash) the system will
> > just create a new process and give it the capabilities of the one that
> > died, right? Why would some kind of "unique identity" be needed? What
> > am I missing here?
>
> What if two programs have capabitilities to *each other*?

Why not associate the capability with the set of capabilities that a process 
holds instead of with that process itself?


- Marcus Sundman


More information about the coyotos-dev mailing list