Also found in: Encyclopedia.
DACNOSDistributed Academic Computing Network Operating System
References in periodicals archive ?
Two operating-system related services were developed partly in parallel with the DACNOS kernel: Remote File Access and Remote Execution.
The DACNOS Remote Execution Service (RES) [19] enables the sharing of programs located on remote computers.
File access of a remote program is handled by the DACNOS RFA component.
In both cases, most of the design and all of the implementation was done by the students who had some programming experience but no DACNOS knowledge.
In both cases the client components were ported to all DACNOS systems.
The design and implementation of DACNOS was a joint effort of researchers at the University of Karlsruhe and IBM.
A few numbers on the amount of code produced for the NOS kernel (excluding the DACNOS System Services) shall illustrate the development work: the KSC component (for VM/CMS) has about 7,000 lines of code, half C and half assembly language.
For DACNOS on VM/CMS, each virtual machine (VM) is a "logical node" and represents an independent RSC entity with several internal and potentially many user-defined processes.
Though we succeeded to port DACNOS to PC DOS and implemented the transparent Remote File Access client in the PC file system, the applicability of DACNOS on a PC is rather limited due to the severe lack of memory.
Given the DACNOS constraints and network environment our design could not exploit some of the mechanisms and techniques that have frequently been used in other projects on distributed operating systems.
We were also very much interested in the overhead introduced by the DACNOS kernel compared to the basic, unenhanced inter-process communication facilities of the host system.
In this section we restrict our discussion to related work that concentrates like DACNOS on adding solutions for heterogeneity and distribution to existing computing environments.