Transporting a portable operating system: UNIX to an IBM minicomputer
Communications of the ACM
Communications of the ACM
ACM SIGAda Ada Letters
| Hi-index | 0.02 |
This paper discusses the strategies for KAPSE implementations by defining the KAPSE that must be supported from the users' point of view and by providing hardware and software criteria against which any KAPSE implementation strategy must be judged. The users' view of the KAPSE is really their view of the MAPSE (or APSE) which is supported by the KAPSE. Any KAPSE implementation strategy can be described as either an implementation of the KAPSE on a bare machine or an implementation of the KAPSE in conjunction with the host machine's operating system. The concerns for the bare machine KAPSE implementation strategy are centered around the hardware criteria of the bare machine's Instruction Set Architecture and hardware configuraton for the bare machine. Examples from the ALS and AIE are supplied in this discussion.The operating systems KAPSE implementation strategies address the situations where the KAPSE is implemented on top of or beside the host machine's operating system. The concerns for the operating system KAPSE implementation strategy are centered around the software criteria of program execution, I/O support, and the KAPSE database for the KAPSE software. Program execution, I/O support, and the KAPSE database includes: process execution and communication: Ada I/O support and virtual terminals; and the KAPSE database access software, respectively. As before, examples from the ALS, AIE, and UNIX are supplied in this discussion. Finally, the KAPSE implementation strategies are summarized in terms of the users' view of the KAPSE, the hardware criteria of the bare machine's ISA and hardware configuration, and the software criteria of program execution, I/O support, and the KAPSE database.