MCP: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
Line 32: | Line 32: | ||
* Current docs | * Current docs | ||
== | == Footnote == | ||
<div style="background-color: white;"> | <div style="background-color: white;"> | ||
<references/> | <references/> |
Revision as of 00:32, 7 October 2019
A timeline of "MCP" in my life course.
MCP 4 Era
I was the systems programmer at Daytona Beach Community, now Daytona State college which was then a Burroughs shop as my second job out of college. [1]
The first referent of the acronym is the operating system of the same name, which was at release 18 in 2017.
4715 Story
In a my domain space concept, it is the designation for nodes of a Domain Control Program (DCP).
«MCP» is the operating system abstraction on a single node of a cluster, or cloud of computers with fast interconnectivity, miniminally 1 gigabit per second. The MCPs operate as the nodes of the larger OS construct, the DCP. MCP itself has these components/layers:
- The top level which is a lisp image running a generic blackboard model of realtime operations control and knowledge base management.
- The workflow level which is implemented by the Work Flow Language, another Burroughs inspiration, reimagined as a context for literate programming and revival of the job control concept based on a generalization of the algol wiffle.
- A base layer close to machine level using the c++ actor framework and optionally a custom debian kernel.
4716-18
Precursors marshalled, extant, then in prodtest .
CP 4721
Blank for formatting purpose.
See also
- Current docs
Footnote