| 2 |
- |
1 |
<html>
|
|
|
2 |
<title>
|
|
|
3 |
preface
|
|
|
4 |
</title>
|
|
|
5 |
<body BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#330088" ALINK="#FF0044">
|
|
|
6 |
<H1>Preface to the Second (1995) Edition
|
|
|
7 |
</H1>
|
|
|
8 |
<P>
|
|
|
9 |
Plan 9 was born in the same lab where Unix began.
|
|
|
10 |
Old Unix hands will recognize the cultural heritage in this manual,
|
|
|
11 |
where venerable Unix commands live on,
|
|
|
12 |
described in the classic Unix style. Underneath, though, lies
|
|
|
13 |
a new kind of system, organized around communication and
|
|
|
14 |
naming rather than files and processes.
|
|
|
15 |
</P>
|
|
|
16 |
<P>
|
|
|
17 |
In Plan 9, distributed computing is a central premise,
|
|
|
18 |
not an evolutionary add-on. The system relies on a
|
|
|
19 |
uniform protocol to refer to and communicate
|
|
|
20 |
with objects, whether they be data or processes, and whether or
|
|
|
21 |
not they live on the same machine or even similar machines.
|
|
|
22 |
A single paradigm (writing to named places) unifies
|
|
|
23 |
all kinds of control and interprocess signaling.
|
|
|
24 |
</P>
|
|
|
25 |
<P>
|
|
|
26 |
Name spaces can be built arbitrarily. In particular all
|
|
|
27 |
programs available to a given user are customarily united
|
|
|
28 |
in a single logical directory.
|
|
|
29 |
Temporary files and
|
|
|
30 |
untrusted activities can be confined in isolated spaces.
|
|
|
31 |
When a portable machine connects to the
|
|
|
32 |
central, archival file system, the machine's local
|
|
|
33 |
name space is joined smoothly to that of the archival file system.
|
|
|
34 |
The architecture affords other unusual abilities, including:
|
|
|
35 |
</P>
|
|
|
36 |
<DL>
|
|
|
37 |
<DT><DT> <DD>
|
|
|
38 |
Objects in name spaces imported from other machines (even from
|
|
|
39 |
foreign systems such as MS-DOS) are transparently accessible.
|
|
|
40 |
<DT><DT> <DD>
|
|
|
41 |
Windows appear in name spaces on a par with files and processes.
|
|
|
42 |
<DT><DT> <DD>
|
|
|
43 |
A historical file system allows one to navigate
|
|
|
44 |
the archival file system in time as well as in space;
|
|
|
45 |
backup files are always at hand.
|
|
|
46 |
<DT><DT> <DD>
|
|
|
47 |
A debugger can handle simultaneously active processes
|
|
|
48 |
on disparate kinds of hardware.
|
|
|
49 |
</dl>
|
|
|
50 |
<P>
|
|
|
51 |
The character set of Plan 9 is Unicode, which
|
|
|
52 |
covers most of the world's major scripts.
|
|
|
53 |
The system has its own programming languages:
|
|
|
54 |
a dialect of C with simple inheritance, a simplified shell,
|
|
|
55 |
and a CSP-like concurrent language, Alef.
|
|
|
56 |
An ANSI-POSIX emulator (APE) admits unreconstructed Unix code.
|
|
|
57 |
</P>
|
|
|
58 |
<P>
|
|
|
59 |
Plan 9 is the work of many people.
|
|
|
60 |
The protocol was begun by Ken Thompson; naming
|
|
|
61 |
was integrated by Rob Pike and networking by Dave Presotto.
|
|
|
62 |
Phil Winterbottom simplified the management of name spaces
|
|
|
63 |
and re-engineered the system.
|
|
|
64 |
They were joined by Tom Killian, Jim McKie, and Howard Trickey in
|
|
|
65 |
bringing the system up on various machines and making
|
|
|
66 |
device drivers.
|
|
|
67 |
Thompson made the C compiler;
|
|
|
68 |
Pike, window systems;
|
|
|
69 |
Tom Duff, the shell and raster graphics;
|
|
|
70 |
Winterbottom, Alef;
|
|
|
71 |
Trickey, Duff, and Andrew Hume, APE.
|
|
|
72 |
Bob Flandrena ported a myriad of
|
|
|
73 |
programs to Plan 9.
|
|
|
74 |
Other contributors include
|
|
|
75 |
Alan Berenbaum,
|
|
|
76 |
Lorinda Cherry,
|
|
|
77 |
Bill Cheswick,
|
|
|
78 |
Sean Dorward,
|
|
|
79 |
David Gay,
|
|
|
80 |
Paul Glick,
|
|
|
81 |
Eric Grosse,
|
|
|
82 |
John Hobby,
|
|
|
83 |
Gerard Holzmann,
|
|
|
84 |
Brian Kernighan,
|
|
|
85 |
Bart Locanthi,
|
|
|
86 |
Doug McIlroy,
|
|
|
87 |
Judy Paone,
|
|
|
88 |
Sean Quinlan,
|
|
|
89 |
Bob Restrick,
|
|
|
90 |
Dennis Ritchie,
|
|
|
91 |
Bjarne Stroustrup,
|
|
|
92 |
and
|
|
|
93 |
Cliff Young.
|
|
|
94 |
</P>
|
|
|
95 |
<P>
|
|
|
96 |
Plan 9 is made available as is, without formal support, but
|
|
|
97 |
substantial comments or contributions may be communicated to
|
|
|
98 |
the authors.
|
|
|
99 |
<br> <br>
|
|
|
100 |
<DL><DT><DD>
|
|
|
101 |
<DL><DT><DD>
|
|
|
102 |
<DL><DT><DD>
|
|
|
103 |
<DL><DT><DD>
|
|
|
104 |
<DL><DT><DD>
|
|
|
105 |
<DL><DT><DD>
|
|
|
106 |
<DL><DT><DD>
|
|
|
107 |
<DL><DT><DD>
|
|
|
108 |
Doug McIlroy
|
|
|
109 |
<br>
|
|
|
110 |
March, 1995
|
|
|
111 |
|
|
|
112 |
</P>
|
|
|
113 |
<br> <br>
|
|
|
114 |
<A href=http://www.lucent.com/copyright.html>
|
|
|
115 |
Copyright</A> © 2000 Lucent Technologies Inc. All rights reserved.
|
|
|
116 |
</body></html>
|