Also found in: Wikipedia.
MOSIXMulticomputer Operating System for Unix
References in periodicals archive ?
At the traditional operating system level, SSI typically consists of a distributed file system and distributed process management, such as in MOSIX [Barak and Litman, 1985], Sprite [Ousterhout et al., 1988] and OSF/1 AD TNC [Zajcew et al., 1993].
One way to remove communication residual dependencies is to deploy locating techniques, such as multicasting (as used in V kernel [Theimer et al., 1985), reliance on the home node (as used in Sprite [Douglis and Ousterhout, 1991], and MOSIX [Barak and Litman, 1985]), or on a forwarding name server (as used in most distributed name services, such as DCE, as well as in mobile agents, such as MOA [Milojicic et al., 1999]).
One is to provide for distribution at the lower levels of a system, as in MOSIX or Sprite, and the other is by providing distribution at a higher-level, as in Locus and its derivatives.
The MOSIX distributed operating system is an ongoing project that began in 1981.
This section presents four case studies of process migration: MOSIX, Sprite, Mach, and LSF.
MOSIX is a distributed operating system from the Hebrew University of Jerusalem.
Various versions of MOSIX have been in active use at the Hebrew University since 1983.
At context switch time, a MOSIX node may elect to migrate any process to another node.
MOSIX presents a process with a uniform view of the file system, devices and networking facilities regardless of the process's current location.
Each node in the system is independent of all other nodes and may selectively participate in the MOSIX cluster or deny services to other nodes.
MOSIX nodes may join or leave a MOSIX cluster at any time.
The MOSIX Distributed Operating System: Load Balancing for UNIX.