Pilot: An Operating System for a Personal Computer

  • David D. Redell
  • Yogen K. Dalal
  • Thomas R. Horsley
  • Hugh C. Lauer
  • William C. Lynch
  • Paul R. McJones
  • Hal G. Murray
  • Stephen C. Purcell


The Pilot operating system provides a single-user, single language environment for higher level software on a powerful personal computer. Its features include virtual memory, a large “flat” file system, streams, network communication facilities, and concurrent programming support. Pilot thus provides rather more powerful facilities than are normally associated with personal computers. The exact facilities provided display interesting similarities to and differences from corresponding facilities provided in large multi-user systems. Pilot is implemented entirely in Mesa, a high-level system programming language. The modularization of the implementation displays some interesting aspects in terms of both the static structure and dynamic interactions of the various components.


Transmission Control Protocol File System Network Stream Information Processing Technique Primary Memory 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Brinch-Hansen, P. The nucleus of a multiprogramming system. Comm. ACM 13, 4 (April 1970), 238–241.Google Scholar
  2. 2.
    Boggs, D.R., Shoch, J.F., Taft, E., and Metcalfe, R.M. Pup: An internetwork architecture. To appear in IEEE Trans. Commun. (Special Issue on Computer Network Architecture and Protocols).Google Scholar
  3. 3.
    Cerf, V.G., and Kahn, R.E. A protocol for packet network interconnection. IEEE Trans. Commun. COM-22, 5 (May 1974), 637–641.CrossRefGoogle Scholar
  4. 4.
    Cerf, V.G., and Kirstein, P.T. Issues in packet-network interconnection. Proc. IEEE 66, 11 (Nov. 1978), 1386–1408.CrossRefGoogle Scholar
  5. 5.
    Farber, D.J. and Heinrich, F.R. The structure of a distributed computer system: The distributed file system. In Proc. 1st Int. Conf. Computer Communication, 1972, 364–370.Google Scholar
  6. 6.
    Habermann, A.N., Flon, L., and Cooprider, L. Modularization and hierarchy in a family of operating systems. Comm. ACM 19, 5 (May 1976), 266–272.CrossRefGoogle Scholar
  7. 7.
    Horsley, T.R., and Lynch, W.C. Pilot: A software engineering case history. In Proc. 4th Int. Conf. Software Engineering, Munich, Germany, Sept. 1979, 999.Google Scholar
  8. 8.
    Internet Datagram Protocol Version 4. Prepared by USC/Information Sciences Institute, for the Defense Advanced Research Projects Agency, Information Processing Techniques Office, Feb. 1979Google Scholar
  9. 9.
    Lampson, B.W. Redundancy and robustness in memory protection. Proc. IFIP 1974, North Holland, Amsterdam, 128–132.Google Scholar
  10. 10.
    Lampson, B.W., Mitchell, J.G., and Satterthwaite, E.H. On the transfer of control between contexts. In Lecture Notes in Computer Science 19, Springer-Verlag, New York, 1974, 181–203.Google Scholar
  11. 11.
    Lampson, B.W., and Redell, D.D. Experience with processes and monitors in Mesa. Comm. ACM 23, 2 (Feb. 1980), 105–117.CrossRefGoogle Scholar
  12. 12.
    Lampson, B.W., and Sproull, R.F. An open operating system for a single user machine. Presented at the ACM 7th Symp. Operating System Principles (Operating Syst. Rev. 13, 5), Dec. 1979, 98–105.Google Scholar
  13. 13.
    Lauer, H.C., and Satterthwaite, E.H. The impact of Mesa on system design. In Proc. 4th Int. Conf. Software Engineering, Munich, Germany, Sept. 1979, 174–182.Google Scholar
  14. 14.
    Lockemann, P.C., and Knutsen, W.D. Recovery of disk contents after system failure. Comm. ACM 11, 8 (Aug. 1968), 542.CrossRefGoogle Scholar
  15. 15.
    Metcalfe, R.M., and Boggs, D.R. Ethernet: Distributed packet switching for local computer networks. Comm. ACM 19, 7 (July 1976), 395–404.CrossRefGoogle Scholar
  16. 16.
    Mitchell, J.G., Maybury, W., and Sweet, R. Mesa Language Manual. Tech. Rep., Xerox Palo Alto Res. Ctr., 1979.Google Scholar
  17. 17.
    Pouzin, L. Virtual circuits vs. datagrams—technical and political problems. Proc. 1976 NCC, AFIPS Press, Arlington, Va., 483–494.Google Scholar
  18. 18.
    Ritchie, D.M., and Thompson, K. The UNIX time-sharing system. Comm. ACM 17, 7 (July 1974), 365–375.CrossRefGoogle Scholar
  19. 19.
    Ross, D.T. The AED free storage package. Comm. ACM 10, 8 (Aug. 1967), 481–492.zbMATHCrossRefGoogle Scholar
  20. 20.
    Rotenberg, Leo J. Making computers keep secrets. Tech. Rep. MAC-TR-115, MIT Lab. for Computer Science.Google Scholar
  21. 21.
    Stern, J.A. Backup and recovery of on-line information in a computer utility. Tech. Rep. MAC-TR-116 (thesis), MIT Lab. for Computer Science, 1974.Google Scholar
  22. 22.
    Sunshine, C.A., and Dalai, Y.K. Connection management in transport protocol. Comput. Networks 2, 6 (Dec. 1978), 454–473.CrossRefGoogle Scholar
  23. 23.
    Stoy, J.E., and Strachey, C. OS 6—An experimental operating system for a small computer. Comput. J. 15,2 and 3 (May, Aug. 1972).Google Scholar
  24. 24.
    Transmission Control Protocol, TCP, Version 4. Prepared by USC/lnformation Sciences Institute, for the Defense Advanced Research Projects Agency, Information Processing Techniques Office, Feb. 1979.Google Scholar
  25. 25.
    Wulf, W., et. al. HYDRA: The kernel of a multiprocessor operating system. Comm. ACM 17, 6 (June 1974), 337–345.CrossRefGoogle Scholar

Copyright information

© Springer Science+Business Media New York 2001

Authors and Affiliations

  • David D. Redell
  • Yogen K. Dalal
  • Thomas R. Horsley
  • Hugh C. Lauer
  • William C. Lynch
  • Paul R. McJones
  • Hal G. Murray
  • Stephen C. Purcell

There are no affiliations available

Personalised recommendations