| Keykos | Eros | Coyotos | Comments
|
| Key | Capability
|
| Domain | Process
|
| Available | Open Wait | | (a domain state) Will accept messages via a start key.
|
| Waiting | Closed Wait | | (a domain state) Will accept messages only via a resume key.
|
| Domain tool | Process tool | Fault Handler
|
| Meter | SchedClass | Schedule | Same Problem, Different Solution
|
| Segment | Address Space | GPT
|
| Data Key | Number Capability | | Later KK docs use “number key”.
|
| Kernel | Virtual Machine
|
| Jump | IPC
|
| Fork | Send
|
| Page | Data Page
|
| Node | CapPage
|
| Sense key | weak RO cappage capability
|
| Sensory | Weak
|
| Segment Key | Opaque Capability | | “Opaque” better describes a discovered patterns for segment keys.
|
| trap code | fault code
|
| process | thread of control |
| The Keykos process is an emergent concept.
The Eros thread is a real kernel construct.
|
| data byte (of key) | key data or key info, (“Facet ID” for start keys)
|
| Return keys | Reply ports
|
| lss | blss
|
| Factory | Constructor
|
| Swap Area | Log
|
| Dry Run | Setup | | Portion of kernel code that establishes or verifies preconditions necessary for kernel object invocation.
|
| Involved - Don’t read | Read Hazard | | Kernel logic
|
| Involved - Don’t write | Write Hazard | | Kernel logic
|
| Device Allocation Object | Device Creator | | Differences due Differences due to
hardware platforms.
|
| Page Range | PhysRange
|
| DIB (Derivative Information Block) | PCB(Process Control Block)
| | Kernel logic
|
| Entry block | ExitBlock | | Keykos terminology from perspective of domain code, EROS from perspective of kernel.
|
| Exit block | EntryBlock
|
| KK | EROS
|
| Front end | Wrapper (both good and newly conventional)
|
Please suggest additions.