| V | |
|---|---|
| Developer | David Cheriton |
| Written in | C |
| OS family | Distributed operating system |
| Working state | Discontinued |
| Initial release | 1981; 44 years ago (1981) |
| Latest release | Final / 1988; 37 years ago (1988) |
| Marketing target | Research |
| Available in | English |
| Update method | Compile fromsource code |
| Supported platforms | Workstations: SUN,MicroVAX,DEC Firefly |
| Kernel type | Microkernel |
| Default user interface | VGTS |
| License | Stanford University |
| Preceded by | Thoth, Verex |
TheV operating system (sometimes writtenV-System) is a discontinuedmicrokerneldistributedoperating system that was developed by faculty and students in theDistributed Systems Group atStanford University from 1981 to 1988, led by ProfessorsDavid Cheriton and Keith A. Lantz.[1] V was the successor to theThoth operating system and Verexkernel that Cheriton had developed in the 1970s.[2][3] Despite similar names and close development dates, it is unrelated toUNIX System V.
The key concepts in V aremultithreading andsynchronousmessage passing. The original V terminology usesprocess for what is now commonly called athread, andteam for what is now commonly called aprocess 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 localEthernet.[4] A thread receiving a message is not required to reply to it before receiving other messages; this distinguished the model fromAda 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 aremote procedure call (RPC). The convenience of an automatic stub generator was lacking, but in contrast, 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 asSprite), V was a complete system that was mostly self hosting. Many students ran V as the only operating system on their disklessSUN workstations orMicroVAX workstations. Compiles could be done either on V, or onVAXUnix 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 one computer, the Versatile Message Transaction Protocol (VMTP) was developed to extend the send-receive-reply system call semantics over alocal area network.[5][6] The protocol included multicast support developed bySteve Deering as a graduate student in the group. TheInternet Protocol layer to support this evolved into theIP multicast standard.[1][7]
The V-System was used forgraphical user interface (GUI) research. The Virtual Graphics Terminal Service (VGTS) provided a modularwindowing system for both local and remote applications.[8] The little-knownW Window System got its name because it was first hosted on the V operating system, and the better-knownX Window System in turn got its name because its first version was based partly on W.[9]
V also spawned another pure microkernel effort atApple Computer known asVanguard, which added a number of improvements to the basic system.[10] Vanguard later disappeared in a reorganization.
TheTektronix 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.
Ridge Computers' Ridge Operating System (ROS) was a commercial system based on Stanford's V-System.[11]
The following is a list of workstationcommands that are supported by the V operating system version 6.0command-line interface.[12]