1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
|
.\" Copyright (c) 1986 The Regents of the University of California.
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice, this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\" 3. Neither the name of the University nor the names of its contributors
.\" may be used to endorse or promote products derived from this software
.\" without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\" @(#)1.t 5.1 (Berkeley) 4/16/91
.\"
.NH
The Role of Research in Maintaining System Vitality
.PP
Since the divestiture of AT&T, UNIX has become the focus of
a massive marketing effort.
To succeed, this effort must convince
potential customers that the product is supported,
that future versions will continue to be developed,
and that these versions will be upwardly
compatible with all past applications.
.PP
AT&T's size alone ensures that it will be around in years to come.
Because the company has allocated increasing research, development,
and support resources to UNIX over the past 10 years
it provides an assurance of its commitment.
Its massive advertising campaign for System V,
its presence on the /usr/group UNIX standards committee,
and the publication of the \fISystem V Interface Definition\fR
testify to the company's intention
to remain compatible with past systems.
.PP
Although repeal of the law of entropy is a necessary step
along the road to a
viable commercial product, this runs counter to
orderly system evolution.
Be that as it may, AT&T's major UNIX
commercialization effort has succeeded in making the system
available to a much broader audience than was previously possible.
.PP
The freezing of what previously had been
an ever-changing UNIX interface
represented a major departure from the pattern that the
small but highly skilled UNIX community had come to expect.
Most early users had accounts
at sites that had the source to the programs they ran.
Thus, as the system interface evolved to reflect more current technology,
software could be changed to keep pace.
Users simply updated their programs
to account for the new interface,
recompiled them, and continued to use them as before.
Although this required a large effort,
it allowed the system --
and the tools that ran on it -- to reflect
changes in software technology.
.PP
At the forefront of the technological wave
was AT&T's own Bell Laboratories [Ritchie74].
It was there that the UNIX system was born and nurtured,
and it was there that its evolution was controlled --
up through the release
of the 7th Edition.
Universities also were involved with the
system almost from its inception.
The University of California at
Berkeley was among the first participants,
playing host to several researchers on sabbatical from the Labs.
This cooperation typified the harmony
that was characteristic of the early UNIX community.
Work that was contributed to the Labs by
different members of the community helped
produce a rapidly expanding set of tools and facilities.
.PP
With the release of the 7th Edition, though,
the usefulness of UNIX already had been
clearly established, and other organizations within AT&T began
to handle the public releases of the system.
These groups took far less input from the community
as they began to freeze the system interface
in preparation for entry into the commercial marketplace.
.PP
As the research community continued to modify the UNIX system,
it found that it needed an organization that could produce releases.
Berkeley quickly stepped into the role.
Before the final public release of UNIX from the Labs,
Berkeley's work had been focused on the development of
tools designed to be added to
existing UNIX systems.
After the AT&T freeze, though,
a group of researchers at
the university found that they could easily
expand their role to include the coalescing function
previously provided by the Labs.
Out of this came the first full Berkeley distribution of UNIX
(3.0BSD),
complete with virtual memory --
a first for UNIX users.
The idea was so successful that System V eventually adopted it
six years later.
.NH 2
Motivations for Change
.PP
At the same time that AT&T was beginning
to put the brakes on further
change in UNIX, local area networks and bitmapped workstations
were just beginning to emerge from
Xerox PARC and other research centers.
Users in the academic and research community realized
that there were no production-quality operating systems
capable of using such hardware.
They also saw that networking unquestionably would be
an indispensable facility in future systems research.
Though it was not clear that UNIX
was the correct base on which to build a networked system,
it was clear that UNIX offered the most expedient means by which
to build such a system.
.PP
This posed the Berkeley group with an interesting challenge:
how to meet the needs of the community of users
without adding needless complexity to existing applications.
Their efforts were aided by the presence of a large and diverse
local group of users who were teaching introductory programming,
typesetting documents, developing software systems, and
trying to build huge Lisp-based systems capable
of solving differential equations.
In addition, they were able to discuss current problems
and hash out potential solutions at semi-annual
technical conferences run by the Usenix organization.
.PP
The assistance of a steering committee composed of academics,
commercial vendors, DARPA researchers, and people from the Labs
made it possible for
the architecture of a networking-based UNIX system to be developed.
By keeping with the UNIX tradition of integrating work done by
others in preference to writing everything from scratch,
4.2BSD was released less than two years later [Joy83].
|
