[cap-talk] "Same" key
Norman Hardy
norm at cap-lore.com
Sat Feb 10 21:26:13 CST 2007
On Feb 3, 2007, at 7:39 AM, Charles Landau wrote:
> At 11:43 PM -0800 2/1/07, Norman Hardy wrote:
>> The operation on a page key to produce a RO page key, issued to the
>> same page key, always produces the same RO key.
>> There is only one RO page key to that page.
>
> I think we all know what Norm is saying, but this terminology is
> inconsistent with where we seem to be going.
> If two processes perform the operation to produce a RO page
> capability to the same page, they will have two capabilities, one in
> each process. Those two capabilities satisfy the EQ relationship, and
> are distinguished only in where they are stored. Rather than say they
> are "the same" capability, it would be more precise to say they are
> capabilities to the same object (using MarkM's precise definition of
> object).
I would like to talk as if the two processes come to hold the same
key, each in their own slot.
One key --- two slots.
Before I started talking this way I read thru much Keykos literature
and discovered a few places where I said 'key' where I should have
said 'slot'.
Making this change made things clearer for me and, in so far as I can
imagine being a new-comer, for him too.
I started talking this way in time to be captured in the Augment
version of the manual.
In this page (http://agorics.com/Library/KeyKos/Gnosis/68.html) I say
'There are four keys to a factory: the builder's key, requestor's
key, fetcher key and copy key. "Factory key" elsewhere in this manual
means "requestor's key".'
I think this thread has migrated to another interesting and important
subject.
I don't understand how the new subject bears on the point I make here
and thus I finally respond to this old mail.
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk
More information about the cap-talk
mailing list