| Mullender, S. J., et al. "Amoeba - A Distributed Operating System for the 1990's." IEEE Computer (May 1990): 45-54. |
....the problems with GUIDs and why we chose not to rely on them, and then we will describe the solution in the Spring operating system that simultaneously answers all three questions. 5. 1 Problems with Global Unique Identifiers Some existing systems use GUIDs for objects (e.g. CHORUS [8] and Amoeba [16]) that can be used to determine object equivalency. If each object has a GUID, then two objects can be considered equivalent if the GUIDs of the two objects are equal. However, we believe that this approach to object equivalency is flawed. There are many cases where the flaws in GUIDs show up, but ....
Mullender, S. J., et al. "Amoeba - A Distributed Operating System for the 1990's." IEEE Computer (May 1990): 45-54.
....operating systems share two main features: a micro kernel implementation in which all possible operating system services have been moved out of the kernel into userlevel processes, and the provision of (lightweight) threads to implement these servers efficiently. Typical examples are Amoeba [4], Mach [5] Chorus [6] and also Meshix. In these systems the term process is used to define a domain of protection, where inter process communication (IPC) generally occurs using message passing, while a process may be composed of many threads sharing the same address space and communicating ....
S. Mullender, G. van Rossum, A. Tanenbaum, R. van Renesse, and H. van Staveren, "Amoeba: a distributed operating system for the 1990's," IEEE Computer, pp. 44--53, June 1990.
.... developed a message passing, UNIX compliant kernel (Meshix [1] for our scalable distributed memory architecture (Topsy [2] This kernel is a microkernel based, message passing operating system, relatively typical in structure to many current systems such as MACH [3] Chorus [4] and Amoeba [5]. Over the last two years we have been examining its structure and performance in a critical manner. This has demonstrated a number of issues that have not yet been addressed by most current microkernel architectures. Additionally, we believe that a POSIX centred architecture [6] does not provided ....
S. Mullender, G. van Rossum, A. Tanenbaum, R. van Renesse, and H. van Staveren, "Amoeba: A distributed operating system for the 1990's," IEEE Computer, pp. 44-- 53, June 1990.
....objects uses hints with chain forwarding to locate objects. ffl Drawbacks program tied to network topology; number of nodes compiled into program. requires existing applications to be rewritten using their programming model Amoeba ffl Operating system built from specialized components. [3], 4] 5] 6] ffl Model system built from a pool of processors, specialized servers (ie, file server) and workstations for graphics and editing; all non graphical tasks executed remotely on pool of processors developed programming language Orca to write distributed applications. ....
Mullender, S., G. van Rossum, A. Tanenbaum, R. van Renesse, and H. van Staveren, "Amoeba: A Distributed Operating System for the 1990's," IEEE Computer, May 1990.
....Unix, System V and more recently Sprite[11] to smaller, simpler and more portable kernels. By layering the operating system in this way, the kernel can be kept fast and efficient with the more complex tasks being provided by servers. Other implementations of this model are Chorus mix[5] Amoeba[12] and Mach[13] Amoeba, Chorus mix and Mach all aim to provide a clean programming paradigm by designing the operating system and its interface in an object oriented manner. They are oriented towards parallel and distributed programming applications. In contrast, Sprite and Meshix aim to provide ....
S. Mullender, G. van Rossum, A. Tanenbaum, R. van Renesse, and H. van Staveren, "Amoeba: a distributed operating system for the 1990's," IEEE Computer, pp. 44--53, June 1990.
....paper (see [5] instead this paper concentrates on how these services are provided to external servers and how they support effective client server communications. Particular attention is paid to the security aspects of this system which are significantly simpler and faster than other systems [6, 7]. In the remainder of this paper, section 2 provides an overview of the Angel operating system which form the basis of this work, section 3 describes the problems associated with providing efficient and secure client server kernel interaction, section 4 describes the adopted solution, and section ....
S. Mullender, G. van Rossum, A. Tanenbaum, R. van Renesse, and H. van Staveren, "Amoeba: A distributed operating system for the 1990's," IEEE Computer, pp. 44--53, June 1990.
No context found.
S. Mullender, G. van Rossum, A. Tanenbaum, R. van Renesse, and H. van Staveren. "Amoeba: A distributed operating system for the 1990's,". IEEE Computer, pages 44--53, June 1990.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC