Functional specialization in distributed operating systems

ABSTRACT

A distributed operating system provides the same functionality and interface as a monolithic operating system. That is, for both systems the goal is to make the computing and storage facilities as provided by the hardware available to the users of the system. In distributed operating system new hardware can be added to the system to increase the storage or computing power, or to increase the availability of the storage and computing services. During and after this addition, the interface to the system remains unchanged. Transparency of access is a key concept.The top-level interface consists of sophisticated command interpreters and editors, supported by a high-resolution graphical window system. This software is run by workstations. Workstations are powerful computer units, consisting of a CPU, memory, a bitmap display, keyboard, a pointing device such as a mouse, and a network interface. In addition, workstations are often equipped with a disk. The CPU is at least as powerful as those used in traditional computer systems, and the amount of memory is equivalent or even larger.A workstation is dedicated to one individual. Consequently, the workstation is idle most of the time. It is therefore tempting to use it as the main computing resource for the owner and perhaps others as well. It could also be used autonomously from the rest of the system in case of a failure. We are opposed to these uses of workstations, since we believe that workstations should only provide the top-level interface. In this paper we will outline our reasons for this, and show how this principle has been applied in the Amoeba distributed operating system.

REFERENCES

• 1: Andrew S. Tanenbaum , Robbert Van Renesse, Distributed operating systems, ACM Computing Surveys (CSUR), v.17 n.4, p.419-470, Dec. 1985 [doi>10.1145/6041.6074]
• 2: Pike, R., "The Blit: a Multiplexed Graphics Terminal," AT&T Bell Laboratories Technical Journal 63(8), pp. 1607-1631 (October 1984).
• 3: Renesse, R. van, Tanenbaum, A. S., and Sharp, G. J., "The Workstation: Computing Resource or just a Terminal?," Proc. of the Workshop on Workstation Operating Systems, Cambridge, Ma. (November 1987).
• 4: D. L. Parnas, On the criteria to be used in decomposing systems into modules, Communications of the ACM, v.15 n.12, p.1053-1058, Dec. 1972 [doi>10.1145/361598.361623]
• 5: Zimmermann, H., "OSI Reference Model--The ISO Model of Architecture for Open Systems Interconnection," IEEE Trans. Comm. COM-28, pp. 425-432 (April 1980).
• 6: Mullender, S. J. and Tanenbaum, A. S., "The Design of a Capability-Based Distributed Operating System," The Computer Journal 29(4), pp. 289-299 (1986).
• 7: Mullender, S. J. and Tanenbaum, A. S., "Protection and Resource Control in Distributed Operating Systems," Computer Networks 8, pp. 412-432 (October 1984).
• 8: Renesse, R. van, Tanenbaum, A. S., Staveren, J. M. van, and Hall, J., "Connecting R.PC-Based Distributed Systems Using Wide-Area Networks," Proc. of the 7th Int. Conf. on Distributed Computing Systems, Berlin (West), pp. 28-34 (September 1987).
• 9: Renesse, R. van et al, "Mandis/Amoeba: A Widely Dispersed Object-Oriented Operating System," Proc. of the EUTECO 88 Conf., Vienna, Austria (April 1988).
• 10: Tanenbaum, A. S., Mullender, S. J., and Renesse, R. van, "Using Sparse Capabilities in a Distributed Operating System," Proc. of the 6th Int. Conf. on Distributed Computing Systems, Cambridge, Mass., pp. 558-563 (May 1986).