implementation of a resource manager for distributed minix  minix is an operating system written by andrew s. tanenbaum and is very much like unix version 7. it uses the same system calls and even the shell is functionally identical to that of unix. it is written in c language and intel 8088 assembly language. minix has all the functionalities of an operating system namely, process manager, i/o manager, device driver, state saver, inter-process communication, memory manager and file manager, user interface, utilities and timing service.  minix, being a modular operating system, is easy to understand and modify and it is distributed with source code. thus, minix can be identified as a suitable candidate for transforming it into a distributed operating system (dos).  to transform minix into a dos, a kernel process called net is proposed to be added. this will be logically located at the same hierarchical level as the memory manager and the file system. net will be composed of a communication manager (cm), a network manager(nm), a resource manager (rm) and extended ipc. these managers will be transparent to users but will offer functionality of a dos. at present, ipc in minix takes place using messages stored in shared buffers. this is due to the restricted address space of the intel 8088 microprocessor. user requests are carried out by sending messages either to the memory manager or the file system which in turn send messages to the system and device driver processes and upon successful completion of the task, return a message to the user via the same route.  the resource manager is an essential component of a dos. as the name suggests, it manages the resources of a system. it maintains an up to date version of the system's resources and also keeps track of the status of other systems in the network. this is achieved by maintaining a global kernel data structure called the system state table (sst). entries in the sst include logical unit number of the various hosts, their logical names, physical station addresses, number of processes running, percent of idle time, available memory, number of users, number of open virtual circuits and an 'altruism' factor indicating willingness to accept remote processes for running. the sst may be accessed by the nm to map logical host names to numbers or physical addresses. the resource manager may be accessed by higher level components such as the user interface, linking loader or by advanced programmers by making resource manager service calls. in this way, the user interface and parallel loader query the rm to discover the number of available processors, willingness to accept remote requests, etc.  the resource manager employs two types of messages: 1) messages are sent at boot time to all hosts announcing the present status of the local system including the boot version, and 2) a message is sent after each time-out interval. if a message is not received from a remote host after two time-out intervals, the remote node is presumed to be dead.  the cm interacts with rm concerning the status information. this status information, piggy-backed onto message frames, is attached to incoming and outgoing frames.  on incoming frames, the status information is placed in a temporary buffer for analysis by the rm. the rm also places local host status information in a second temporary buffer area so that the cm may piggyback the status data onto outgoing frames.  devendra naniwadekar