The newcastle connection or UNIXes of the world unite!

@article{Brownbridge1982TheNC,
  title={The newcastle connection or UNIXes of the world unite!},
  author={David R. Brownbridge and Lindsay F. Marshall and Brian Randell},
  journal={Software: Practice and Experience},
  year={1982},
  volume={12}
}
In this paper we describe a software subsystem that can be added to each of a set of physically interconnected UNIX or UNIX look‐alike systems, so as to construct a distributed system which is functionally indistinguishable at both the user and the program level from a conventional single‐processor UNIX system. The techniques used are applicable to a variety and multiplicity of both local and wide area networks, and enable all issues of inter‐processor communication, network protocols, etc., to… 
View on Wiley
homepages.cs.ncl.ac.uk
204 Citations
Highly Influential Citations
1
Background Citations
18
Methods Citations
6

204 Citations

Citation Type

Citation Type

An experiment with the newcastle connection protocol
TLDR
The experiment demonstrates that the Newcastle Connection technique can be used to connect together operating systems with differing structures and philosophies, and suggests that increasing the range of services offered would be possible, despite the substantial differences in structure between Nimrod and Unix.
Primitives for Distributed Computing in a Heterogeneous Local Area Network Environment
TLDR
A set of high-level communication primitives has been designed and implemented to provide the programmer with an interface independent of the operating system and of the underlying interprocess communications facilities.
VAXcluster: a closely-coupled distributed system
TLDR
A VAXcluster is a highly available and extensible configuration of VAX computers that operate as a single system that uses a distributed version of the VAX/VMS operating system to achieve performance in a multicomputer environment.
The architecture of UNIX united
TLDR
A description of the basic semantics of UNIX United is followed by that of the architecture implied by the protocol between components in a UNix United system, and of a software structure appropriate to the architecture and the protocol.
GUY BERNARD, ANDRZEJ DUDA, YORAM HADDAD, MEMBER, IEEE, AND GILBERT HARRUS
TLDR
A set of high- level communication primitives provides the programmer with an interface independent of the operating system and of the underlying interprocess communications facilities, and is complemented by three user-written functions.
Approaches to Distributed UNIX Systems
TLDR
This paper examines several approaches to developing a distributed version of the UNIX! operating system and the issue of transparency is central to both, and is examined in some detail.
Design considerations for the transformation of MINIX into a distributed operating system
TLDR
Design considerations include a definition of Distributed Operating Systems (DOSs), a description of existing DOSs, a descriptions of operating system architectural components which add DOS functionality, a plan for the placement of these components within the MINIX environment, and an explanation of the types of DOS communication.
Naming in the distributed operating system ZGL
TLDR
It is believed that the partitioning of the name space into many local name spaces and one global shared name space allows the ZGL system to satisfy each workstation's demand for local autonomy and still be able to facilitate transparent resource sharing.
The Design of the Saguaro Distributed Operating System
TLDR
The design of the Saguaro operating system for computers connected by a local-area network is described, which makes extensive use of a type system to describe user data and to specify the types of arguments to commands and procedures.
A programmable interface language for heterogeneous distributed systems
TLDR
This paper proposes a distributed system architecture in which communication follows a programming paradigm, and a programming language provides remote service interfaces for the heterogeneous distributed system environment.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 32 REFERENCES
The network Unix system
TLDR
This paper discusses the organization of the NIP currently being used with the Unix operating system on the ARPA network, and the Network Unix system is noteworthy because of the natural way that network and local functions are merged.
The UNIX time-sharing system
TLDR
The nature and implementation of the file system and of the user command interface are discussed, including the ability to initiate asynchronous processes and over 100 subsystems including a dozen languages.
A Local Network Based on the UNIX Operating System
  • L. Rowe, K. Birman
  • Computer Science
    IEEE Transactions on Software Engineering
  • 1982
TLDR
An efficient message-oriented interprocess communication mechanism and asynchronous I/O were added to the system to support the development of distributed applications and to make it easier to connect the local network to packet-switched networks.
A distributed UNIX system based on a virtual circuit switch
TLDR
This paper reports on the design and implementation of a distributed UNIX system that consists of two components: the S-UNIX subsystem provides a complete UNIX process environment enhanced by access to remote files; the F-UNix subsystem is specialized to offer remote file service.
A Unix-Based Local Computer Network with Load Balancing
TLDR
Comparisons of the Purdue ECN with other Unix networks in terms of network configurations, protocols, and capabilities are compared to shed light on the load-balancing strategies embedded in its system software.
The architecture of the Eden system
TLDR
The philosophy and goals of Eden are stated, the programming methodology that is chosen to support, and the hardware and kernel architecture of the system are discussed.
The Cambridge Model Distributed System
TLDR
The Cambridge Model Distributed System sets out to provide, by means of a number of interconnected miniand microcomputers, facilities that are similar to those provided by a time-sharing system.
The National Software Works: A distributed processing system
TLDR
The National Software Works (NSW) is an ambitious project to link a set of geographically distributed and diverse hosts with an operating system which appears as a single entity to a prospective user.
Accent: A communication oriented network operating system kernel
TLDR
This paper focuses on system supplied facilities which support transparent network access and fault-tolerant behavior under a modified version of VAX/UNIX.
The Design of a Reliable Remote Procedure Call Mechanism
TLDR
This correspondence describes the design of a reliable Remote Procedure Call mechanism intended for use in local area networks and discusses various design issues involved, including the choice of a message passing system over which the remote call mechanism is to be constructed.
...
1
2
3
4
...