MCP: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
No edit summary |
|||
| Line 1: | Line 1: | ||
{{TOCright}} | |||
<div style="background-color: black;"> | |||
A timeline of "MCP" | A timeline of "MCP" | ||
== My Early Career == | == My Early Career == | ||
| Line 32: | Line 33: | ||
== References == | == References == | ||
</div> | |||
Revision as of 18:25, 6 October 2019
A timeline of "MCP"
My Early Career
I was the systems programmer at Daytona Beach Community, now Daytona State college which was thenn 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.
In a modern context, it is the encompassing operational context for the development of DCP nodes.
4715 Story
«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 a larger OS construct, the DCP or domain control program. MCP itself has these components/layers:
- The top level which is a lisp image running a generic blackboard model of realtime operatons control.
- 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 modified linux kernel to support the above.
4716/17
Precursors marshalled, extant, then in prodtest .
4721
Intentionally blank for formatting purpose.
See also
- Current docs
