LargeSystem: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
(T) |
No edit summary |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
At the time of initial exposure, Burroughs had distinct architectures/divisions, Large Systems (B 6 and 7000 then A series) and Medium Systems (B 17 and 1900, then B series?). | At the time of our initial working exposure, [[Burroughs]] had distinct architectures/divisions, Large Systems (B 6 and 7000 then A series) and Medium Systems (B 17 and 1900, then B series?). | ||
<br><br> | |||
Here, by LargeSystem we mean the conceptual VM implemented by the current [[DMS III]] core domain control program. | |||
<br><br> | |||
Each host participating in the DCP is considered to be a processor under control of the | Each host participating in the DCP is considered to be a processor under control of the PVM and it's file system and | ||
IO capabilities are modelled using an amalgam of the Large Systems library and [[Algol68]] <i>transput</i> definitions | IO capabilities are modelled using an amalgam of the Large Systems library and [[Algol68]] <i>transput</i> definitions | ||
where a library is simply a collection of Books as defined in the Revised Report. | where a library is simply a collection of Books as defined in the Revised Report. | ||
Latest revision as of 08:18, 3 October 2006
At the time of our initial working exposure, Burroughs had distinct architectures/divisions, Large Systems (B 6 and 7000 then A series) and Medium Systems (B 17 and 1900, then B series?).
Here, by LargeSystem we mean the conceptual VM implemented by the current DMS III core domain control program.
Each host participating in the DCP is considered to be a processor under control of the PVM and it's file system and
IO capabilities are modelled using an amalgam of the Large Systems library and Algol68 transput definitions
where a library is simply a collection of Books as defined in the Revised Report.
