ArticleslgStudy

computer science

History of the Berkeley Software Distribution

History of the Berkeley Software Distribution is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand History of the Berkeley Software Distribution rather than just read about it. In short: The history of the Berkeley Software Distribution began in the 1970s when University of California, Berkeley received a copy of Unix. Professors and students at the university began adding software to the operating system and released it as BSD to select universities.

History of the Berkeley Software Distribution — main illustration
History of the Berkeley Software Distribution — illustration

Key takeaways

  • History of the Berkeley Software Distribution belongs to computer science; place it in that map before memorising details.
  • Learn the definition first, then one example that makes the definition concrete.
  • Connect History of the Berkeley Software Distribution to a quantity you can measure, compute or draw — that is where exam questions come from.
  • Reproduce the core statement of History of the Berkeley Software Distribution from memory before moving on to harder problems.

Reference excerpt

The history of the Berkeley Software Distribution began in the 1970s when University of California, Berkeley received a copy of Unix. Professors and students at the university began adding software to the operating system and released it as BSD to select universities. Since it contained proprietary Unix code, it originally had to be distributed subject to AT&T licenses. The bundled software from AT&T was then rewritten and released as free software under the BSD license. However, this resulted in a lawsuit with Unix System Laboratories, the AT&T subsidiary responsible for Unix. Eventually, in the 1990s, the final versions of BSD were publicly released without any proprietary licenses, which led to many descendants of the operating system that are still maintained today.

1BSD (PDP-11) The earliest distributions of Unix from Bell Labs in the 1970s included the source code to the operating system, allowing researchers at universities to modify and extend Unix. The operating system arrived at Berkeley in 1974, at the request of computer science professor Bob Fabry who had been on the program committee for the Symposium on Operating Systems Principles where Unix was first presented. A PDP-11/45 was bought to run the system, but for budgetary reasons, this machine was shared with the mathematics and statistics groups at Berkeley, who used RSTS, so that Unix only ran on the machine eight hours per day (sometimes during the day, sometimes during the night). A larger PDP-11/70 was installed at Berkeley the following year, using money from the Ingres database project. Also in 1975, Ken Thompson took a sabbatical from Bell Labs and came to Berkeley as a visiting professor. He helped to install Version 6 Unix and started working on a Pascal implementation for the system. Graduate students Chuck Haley and Bill Joy improved Thompson's Pascal and implemented an improved text editor, ex. Other universities became interested in the software at Berkeley, and so in 1977 Joy started compiling the first Berkeley Software Distribution (1BSD), which was released on March 9, 1978. 1BSD was an add-on to Version 6 Unix rather than a complete operating system in its own right. Some thirty copies were sent out.

2BSD (PDP-11) The Second Berkeley Software Distribution (2BSD), released in May 1979, included updated versions of the 1BSD software as well as two new programs by Joy that persist on Unix systems to this day: the vi text editor (a visual version of ex) and the C shell. Some 75 copies of 2BSD were sent out by Bill Joy. A further feature was a networking package called Berknet, developed by Eric Schmidt as part of his master's thesis work, that could connect up to twenty-six computers and provided email and file transfer. After 3BSD (see below) had come out for the VAX line of computers, new releases of 2BSD for the PDP-11 were still issued and distributed through USENIX; for example, 1982's 2.8.1BSD included a collection of fixes for performance problems in Version 7 Unix, and later releases contained ports of changes from the VAX-based releases of BSD back to the PDP-11 architecture. 2.9BSD from 1983 included code from 4.1cBSD, and was the first release that was a full OS (a modified V7 Unix) rather than a set of applications and patches. The most recent release, 2.11BSD, was first issued in 1991. Unlike the previous releases, it required split instruction/data space, to accommodate the ever-increasing size of its utility programs. In the 21st century, maintenance updates from volunteers continued: patch #499 was released on January 2, 2026.

3BSD

A DEC VAX computer was installed at Berkeley in 1978. The port of Version 7 Unix to the VAX architecture, UNIX/32V, did not take advantage of the VAX's virtual memory capabilities, which were necessary to run large programs such as Franz Lisp. The kernel of 32V was largely rewritten by Berkeley graduate student Özalp Babaoğlu to include a virtual memory implementation, and a complete operating system including the new kernel, ports of the 2BSD utilities to the VAX, and the utilities from 32V was released as 3BSD at the end of 1979. 3BSD was also alternatively called Virtual VAX/UNIX or VMUNIX (for Virtual Memory Unix), and BSD kernel images were normally called /vmunix until 4.4BSD. The success of 3BSD was a major factor in the Defense Advanced Research Projects Agency's (DARPA) decision to fund Berkeley's Computer Systems Research Group (CSRG), which would develop a standard Unix platform for future DARPA research in the VLSI Project.

4BSD 4BSD (November 1980) offered a number of enhancements over 3BSD, notably job control in the previously released csh, delivermail (the ancestor of sendmail), "reliable" signals, and the Curses programming library. In a 1985 review of BSD releases, John Quarterman et al., wrote:

4BSD was the operating system of choice for VAXs from the beginning until the release of System III (1979–1982) [...] Most organizations would buy a 32V license and order 4BSD from Berkeley without ever bothering to get a 32V tape. Many installations inside the Bell System ran 4.1BSD (many still do, and many others run 4.2BSD).

4.1BSD 4.1BSD (June 1981) was a response to criticisms of BSD's performance relative to the dominant VAX operating system, VMS. The 4.1BSD kernel was systematically tuned up by Bill Joy until it could perform as well as VMS on several benchmarks. The release would have been called 5BSD, but after objections from AT&T the name was changed; AT&T feared confusion with AT&T's UNIX System V. Several tapes have turned up, all with a label that says 4.1BSD, yet differences between the tapes are present. The software development that would lead from 4.1BSD to 4.2BSD was funded from sources including ARPA, Order Number 4031, Contract N00039-82-C-0235 which was in effect at least from November 15, 1981 through September 30, 1983.

… excerpt ends here. Continue reading the full article.

Illustrations

History of the Berkeley Software Distribution: VAX-11/780 internals
VAX-11/780 internals
History of the Berkeley Software Distribution: "4.3 BSD UNIX" from the University of Wisconsin circa 1987. System startup and login.
"4.3 BSD UNIX" from the University of Wisconsin circa 1987. System startup and login.
History of the Berkeley Software Distribution: 4.3 BSD from the University of Wisconsin. Browsing "/usr/ucb" and "/usr/games"
4.3 BSD from the University of Wisconsin. Browsing "/usr/ucb" and "/usr/games"
History of the Berkeley Software Distribution: Installation of 386BSD. 386BSD was an early port of BSD to the Intel 80386 architecture.
Installation of 386BSD. 386BSD was an early port of BSD to the Intel 80386 architecture.
History of the Berkeley Software Distribution: Simplified evolution of Unix systems
Simplified evolution of Unix systems

Worked examples

Example 1 — a first encounter with History of the Berkeley Software Distribution

Start with the simplest possible case. Write down what History of the Berkeley Software Distribution claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to History of the Berkeley Software Distribution before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about History of the Berkeley Software Distribution ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of History of the Berkeley Software Distribution

In research
History of the Berkeley Software Distribution appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry
Engineering practice reuses History of the Berkeley Software Distribution in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom
History of the Berkeley Software Distribution is common in secondary-school and first-year university syllabi. It links to neighbouring topics Berkeley Software Distribution, History of free and open-source software, History of software, so understanding it makes those chapters shorter.
In everyday life
Look for History of the Berkeley Software Distribution outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study History of the Berkeley Software Distribution in 20 minutes

  1. Read the reference excerpt below once, without taking notes.
  2. Close the page and write down what History of the Berkeley Software Distribution means in your own words.
  3. Compare your version with the excerpt and mark what you missed.
  4. Work through the three examples above with pen and paper.
  5. Explain History of the Berkeley Software Distribution out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is History of the Berkeley Software Distribution in simple terms?

The history of the Berkeley Software Distribution began in the 1970s when University of California, Berkeley received a copy of Unix. Professors and students at the university began adding software to the operating system and released it as BSD to select universities.

Why does History of the Berkeley Software Distribution matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study History of the Berkeley Software Distribution?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on History of the Berkeley Software Distribution.

Tags

  • Berkeley Software Distribution
  • History of free and open-source software
  • History of software

Keep exploring