Jump to content

V (operating system)

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by AnomieBOT (talk | contribs) at 19:35, 6 December 2014 (Dating maintenance tags: {{Cn}}). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

For the Unix variant, see UNIX System V.
V
DeveloperDavid Cheriton
Written inC
Working stateHistoric
Kernel typeMicrokernel
Default
user interface		VGTS
LicenseStanford University

The V operating system (sometimes written V-System) is a microkernel operating system that was developed by faculty and students in the distributed systems group at Stanford University from 1981 to 1988, led by Professors David Cheriton and Keith A. Lantz.[1] V was the successor to the Thoth and Verex operating systems that Cheriton had developed in the 1970s.[2][3] Despite very similar names and close development dates, it is not related to the UNIX System V.

Features

The key concepts in V are multithreading and synchronous message passing. The original V terminology uses "process" for what is now commonly called a "thread", and "team" for what is now commonly called a "process" consisting of multiple threads sharing an address space. Communication between threads in V uses synchronous message passing, with short, fixed-length messages that can include access rights for the receiver to read or write part of the sender's address space before replying. The same message-passing interface is used both between threads within one process, between threads of different processes within one machine, and between threads on different machines connected by a local Ethernet.[4] A thread receiving a message is not required to reply to it before receiving other messages; this distinguished the model from Ada rendezvous.

One common pattern for using the messaging facility is for clients to send messages to a server requesting some form of service. From the client side, this looks much like RPC (remote procedure call). The convenience of an automatic stub generator was lacking, but on the other hand, the client can pass one parameter by reference, which is not possible with other RPC implementations. From the server side the model differs more from RPC, since by default all client requests are multiplexed onto one server thread. The server is free to explicitly fork threads to handle client requests in parallel, however; if this is done, the server-side model is much like RPC too.

V was never an end in itself for the Stanford group; rather, it was used as a vehicle for many different research projects in distributed operating systems and networking. Much like other operating system efforts of its day (such as Sprite), V was a complete system that was mostly self hosting. Many students ran V as the only operating system on their diskless SUN workstations or MicroVAX workstations. Compiles could be done either on V itself or on VAX Unix machines that provided file service in a more stable environment than the ever-changing research system.

V did have some notable impacts. After the initial implementation on a single computer, protocol called the Versatile Message Transaction Protocol (VMTP) was developed to extend the send-receive-reply system call semantics over a local area network.[5][6] The protocol included multicast support developed by Steve Deering as a graduate student in the group. The Internet Protocol layer to support this evolved into the IP multicast standard.[1][7]

The V system was used for graphical user interface research. The Virtual Graphics Terminal Service (VGTS) provided a modular windowing system for both local and remote applications.[8] The little-known W Window System got its name because it was first hosted on the V operating system, and the better-known X Window System in turn got its name because its first version was based partly on W.[citation needed] V also spawned another pure microkernel effort at Apple Computer known as Vanguard, which added a number of improvements to the basic system.[9] Vanguard later disappeared in a reorganization. The Tektronix VM700 television measurement instrument was developed in a networked V environment in the late 1980s and ran a lightly modified version of the V operating system; this device was manufactured and sold for many years.

References

  1. ^ a b "Past Research in the DSG". official web site. July 20, 1995. Retrieved June 25, 2011.
  2. ^ David R. Cheriton (1982). The Thoth system: multi-process structuring and portability. North-Holland. ISBN 0-444-00701-6.
  3. ^ David R. Cheriton (1981). "The design of a distributed kernel". Proceedings of the ACM '81 conference: 46–52. doi:10.1145/800175.809831. ISBN 0-89791-049-4.
  4. ^ David R. Cheriton (March 1988). "The V Distributed System" (PDF). Communications of the ACM. 31 (3): 314–333. doi:10.1145/42392.42400. Retrieved June 25, 2011. Reprinted in Innovations in Internetworking ISBN 0-89006-337-0
  5. ^ David Cheriton (February 1988). "Versatile Message Transaction Protocol". RFC 1045. Retrieved June 25, 2011.
  6. ^ David R. Cheriton (1986). "The VMTP: a transport protocol for the next generation of communication systems". Proceedings of the ACM SIGCOMM conference on Communications architectures & protocols. 16 (3): 406–415. doi:10.1145/1013812.18217. ISBN 0-89791-201-2.
  7. ^ Steve Deering (August 1989). "Host Extensions for IP Multicasting". RFC 1112. Retrieved September 4, 2013.
  8. ^ William I. Nowicki (March 1985). Partitioning of Function in a Distributed Graphics System (PDF). Stanford University. Technical Report CSL-85-282
  9. ^ Ross S. Finlayson; Mark D. Hennecke; Steven L. Goldberg (1993). "From V to Vanguard: the evolution of a distributed, object-oriented microkernel interface". USENIX Symposium on Microkernels and Other Kernel Architectures.
Retrieved from "https://en.wikipedia.org/w/index.php?title=V_(operating_system)&oldid=636921067"