To install click the Add extension button. That's it.

The source code for the WIKI 2 extension is being checked by specialists of the Mozilla Foundation, Google, and Apple. You could also do it yourself at any point in time.

4,5
Kelly Slayton
Congratulations on this excellent venture… what a great idea!
Alexander Grigorievskiy
I use WIKI 2 every day and almost forgot how the original Wikipedia looks like.
Live Statistics
English Articles
Improved in 24 Hours
Added in 24 Hours
Languages
Recent
Show all languages
What we do. Every page goes through several hundred of perfecting techniques; in live mode. Quite the same Wikipedia. Just better.
.
Leo
Newton
Brights
Milds

V (operating system)

From Wikipedia, the free encyclopedia

V
DeveloperDavid Cheriton
Written inC
OS familyDistributed operating system
Working stateDiscontinued
Initial release1981; 43 years ago (1981)
Latest releaseFinal / 1988; 36 years ago (1988)
Marketing targetResearch
Available inEnglish
Update methodCompile from source code
PlatformsWorkstations:
SUN, MicroVAX, DEC Firefly
Kernel typeMicrokernel
Default
user interface
VGTS
LicenseStanford University
Preceded byThoth, Verex

The V operating system (sometimes written V-System) is a discontinued microkernel distributed 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 operating system and Verex kernel that Cheriton had developed in the 1970s.[2][3] Despite similar names and close development dates, it is unrelated to UNIX System V.

YouTube Encyclopedic

  • 1/3
    Views:
    261 210
    154 350
    183 794
  • The operating system of life - George Zaidan and Charles Morton
  • Operating Systems 2 - Memory Manager
  • Operating System Basics

Transcription

Every chicken was once an egg, every oak tree an acorn, every frog a tadpole. The patch of mold on that old piece of bread in the back of your fridge, not so long ago that was one, solitary cell. Even you were once but a gleam in your parents' eyes. All these organisms share the same basic goal: to perpetuate their own existence. All lifeforms that we've discovered so far stay alive by using basically the same rules, materials, and machinery. Imagine a factory full of robots. These robots have two missions: one, keep the factory running, and two, when the time is right, set up an entirely new factory. To do those things, they need assembly instructions, raw materials, plenty of energy, a few rules about when to work normally, when to work quickly, or when to stop, and some exchange currencies because even robots need to get paid. Each factory has a high security office with blueprints for all the possible factory configurations and complete sets of instructions to make all the different types of robots a factory could ever need. Special robots photocopy these instructions and send them off to help make the building blocks of more robots. Their colleagues assemble those parts into still more robots, which are transported to the right location in the factory and given the tools they need to start working. Every robot draws energy from the central power plant, a giant furnace that can burn regular fuel but also scrap materials if not enough regular fuel is available. Certain zones in the factory have harsher working conditions, so these areas are walled off. But the robots inside can at least communicate with the rest of the factory through specialized portals embedded directly into the walls. And as you've probably figured out, what we're describing here is a cell. The high security office is the nucleus. It stores the blueprints and instructions as deoxyribonucleic acid, or DNA. The photocopied instructions are RNA. The robots themselves are mostly proteins built from amino acids, but they'll often use special tools that are, or are derived from, vitamins and minerals. The walls between factory zones and around the factory itself are mostly made up of lipids, a.k.a. fats. In most organisms, the primary fuel source are sugars, but in a pinch, fats and proteins can be broken down and burned in the furnace as well. The portals are membrane proteins which allow very specific materials and information to pass through the walls at the right times. Many interactions between robot proteins require some kind of push, think robot minimum wage. A few small but crucial forms of money are transferred between proteins to provide this push. Electrons, protons, oxygen, and phosphate groups are the main chemical currencies, and they're kept in small molecular wallets or larger tote bags to keep them safe. This is biochemistry, the study of how every part of the factory interacts to keep your life running smoothly in the face of extreme challenges. Maybe there's too much fuel; your body will store the excess as glycogen or fat. Maybe there's not enough; your body will use up those energy reserves. Maybe a virus or bacteria tries to invade; your body will mobilize the immune system. Maybe you touched something hot or sharp; your nerves will let you know so you can stop. Maybe it's time to create a new cell or a new person. Amazingly, oak trees, chickens, frogs, and, yes, even you share so many of the same basic robot and factory designs that biochemists can learn a lot about all of them all at the same time.

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 a remote 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 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, 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 one computer, 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 (GUI) 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.[9] V also spawned another pure microkernel effort at Apple Computer known as Vanguard, which added a number of improvements to the basic system.[10] 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.

Commands

The following is a list of workstation commands that are supported by the V operating system version 6.0 command-line interface.[11]

References

  1. ^ a b "Past Research in the DSG". Distributed Systems Group. 20 July 1995. Archived from the original on 27 July 2012. Retrieved 14 September 2020.
  2. ^ Cheriton, David R. (1982). The Thoth system: multi-process structuring and portability. North-Holland. ISBN 0-444-00701-6.
  3. ^ Cheriton, David R. (1981). "The design of a distributed kernel". Proceedings of the ACM '81 conference on - ACM 81. pp. 46–52. doi:10.1145/800175.809831. ISBN 0-89791-049-4. S2CID 14212831.{{cite book}}: CS1 maint: date and year (link)
  4. ^ Cheriton, David R. (March 1988). "The V Distributed System" (PDF). Communications of the ACM. 31 (3): 314–333. doi:10.1145/42392.42400. S2CID 7523994. Archived from the original (PDF) on August 12, 2017. Retrieved June 25, 2011. Reprinted in Innovations in Internetworking ISBN 0-89006-337-0
  5. ^ Cheriton, David R. (February 1988). "Versatile Message Transaction Protocol". RFC 1045. doi:10.17487/RFC1045. Retrieved June 25, 2011.
  6. ^ Cheriton, David R. (1986). "VMTP: A transport protocol for the next generation of communication systems". ACM SIGCOMM Computer Communication Review. 16 (3): 406–415. doi:10.1145/1013812.18217. ISBN 0-89791-201-2.
  7. ^ Deering, Steve (August 1989). "Host Extensions for IP Multicasting". RFC 1112. doi:10.17487/RFC1112. Retrieved September 4, 2013.
  8. ^ Nowicki, William I. (March 1985). Partitioning of Function in a Distributed Graphics System (PDF). Stanford University. Technical Report CSL-85-282
  9. ^ Hahn, Harley (1995). The Unix Companion. Osborne McGraw-Hill. p. 45. ISBN 0-07-882149-5.
  10. ^ Finlayson, Ross S.; Hennecke, Mark D.; Goldberg, Steven L. (1993). "From V to Vanguard: the evolution of a distributed, object-oriented microkernel interface". USENIX Symposium on Microkernels and Other Kernel Architectures: 3.
  11. ^ V-System 6.0 Reference Manual

External links

This page was last edited on 28 April 2024, at 23:24
Basis of this page is in Wikipedia. Text is available under the CC BY-SA 3.0 Unported License. Non-text media are available under their specified licenses. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc. WIKI 2 is an independent company and has no affiliation with Wikimedia Foundation.