Berknet

From Wikipedia, the free encyclopedia

The Berkeley Network, or Berknet, was an early wide area network, developed at the University of California, Berkeley in 1978, primarily by Eric Schmidt as part of his master's thesis work.[1] The network continuously connected about a dozen computers running BSD[2] and provided email, file transfer, printing and remote command execution services to its users, and it connected to the two other major networks in use at the time, the ARPANET and UUCPNET.[3]

The network operated using what were then high-speed serial links, 1200 bps in the initial system. Its software implementation shipped with the Berkeley Software Distribution from version 2.0 onwards.[1] It consisted of a line discipline within the Unix kernel,[4] a set of daemons that managed queues of commands to be sent across machines, and a set of user-level programs that enqueued the actual commands. The Berkeley Network introduced the .netrc file.

The release of UUCP as part of Version 7 Unix in 1979 led to little external interest in the system; Mary Ann Horton noted in 1984 that "Berknets are gone now".[5] Support for Berknet's custom email addressing scheme was provided in the Sendmail program until 1993.[4]

History[]

The development of what became Berknet began with an initial concept developed by Bob Fabry, Eric Schmidt's advisor. Schmidt developed the system until leaving for a break in May. The system was initially designed to connect only two machines, known as A and Q, both PDP-11 machines running Unix.[6] Development ran until the end of term in May. By 1 May the initial system, connecting two machines, A and Q, was operational. As development took place mostly on the A machine, the system was also used to distribute the code to Q. The menial task of moving the code to Q led to early efforts to automate the system.[6]

As the code began to become functional it also began to see use by other users, and this led to A being connected to a new machine, C. This presented the new problem that the original implementation required the same user login on both machines, and trying to keep this in sync between several machines led to A's password file growing too large. Dealing with this problem was initially handled by having dedicated "free" accounts on both machines that was used by Berknet, along with using the .netrc file to automatically log into them when needed.[6]

A third machine, Cory, was then added.[6] To deal with the account issue, and handle physical routing, A became a hub responsible for storing and forwarding any messages between C and Cory. A table-based routing map was introduced to control this. It was in this state when Schmidt completed the first version in May. While he was away, the Computing Center made several changes to the system, and this led to several incompatible versions of Berknet emerging, and periodic breakage of the system, including the sendmail system not working.[7]

By the time Schmidt returned to the system in October, a VAX 11/780 machine had been added, bringing the total to three different versions of Unix being supported. make was then used to build and distribute the code to the machines, including using the older version of the code to bootstrap the Cory machine, which ran Unix Version 6 while the others ran 7. Further changes led to a stable version and documentation began, and several additional sites were added. Performance became a problem, especially for the machines tasked with forwarding, and required hand maintenance to keep the system working.[8]

Description[]

The system had some resemblance to UUCP in that it used a batch mode file transfer system based on a Unix daemon that performed the actual transfers, as well as defining a suitable simple network protocol to move the data over the telephone-based links. The protocol is built into the net application, which watches for new files to appear a series of defined locations representing queues.[8] When a file appears, net starts a terminal connection to the selected remote machine, issues commands and performs file transfers, and then disconnects and deletes the local file if it was a success.[9]

From a user's perspective, there are a number of separate applications that make up the system, ones for reading and writing mail, one for moving files between machines, etc. These all work by placing files in the proper queues which then automatically move the data to the target machine where it is reassembled and moved back into user directories for use.[8] The most-used application was netcp, which copied files over the network. This was supplied with two filenames, the first the path to the existing file, and the second the path to the desired final location. Paths were a combination of a machine name followed by a colon, and then a normal Unix slash-separated path. For instance: 

  netcp testfile.txt Cory:/usr/pascal/sh

would copy the file testfile.txt to the path /usr/pascal/sh on the Cory machine.[9]

Likewise, the existing mail application was modified to understand the same addressing scheme, and supported by the mmail utility which automatically added headers to indicate where the message originated. On the receive side, the new application netmail uses net to log into a named remote machine and read any mail found there. When this completes, prmail then copies the messages into the user's local mail where it can be read and replied to as normal. Automation of these separate tasks was quickly introduced.[10]

Protocol[]

The underlying transfer protocol was arranged in three layers. The uppermost was the command protocol, which defined the overall file structure, below this was the stream protocol, which broke the file into multiple packets, and at the bottom was the hardware layer using the serial ports.[11]

The command layer consisted primarily of a file format that started with a length indicator, followed by a header, a command to run on the remote machine, and then any required data. The net command assembled the files, prepends the length indicator, and then places the resulting file in the proper queue. The header contains the origin and destination machine names, the login names to use on both, a version number, time stamps, and then the "pseudo-command". The header data is written as normal ASCII text with the fields separated by colons.[11]

During a transfer, the file is broken into packets for error correction purposes. The packets have a header consisting of a length byte that allows up to 255 bytes in a packet, followed by a two-byte packet number, a one-byte type indicator, a one-byte checksum, and then the data.[11] The checksum is placed at the front because the packets are variable length, and this simplified the code. There are several packet types, which contain command information or data. Among these is the "reset" packet, which indicates the start of a new transfer from a remote machine. The protocol was very similar to XMODEM in complexity, lacking sliding windows or streaming acknowledgement, features that were considered important to add to future versions.[12]

At the hardware level, the system was simply a serial port connecting two machines. However, the existing Unix systems could not directly process 8-bit ASCII data without considerable overhead, so the data being sent is encoded with three 8-bit bytes packaged into four 6-bit characters in the printable range. This introduces an overhead of 33%, which was also considered an important area for possible improvement.[12]

References[]

Citations[]

  1. ^ a b Shacklette, Mark (2004). "Unix Operating System". The Internet Encyclopedia. Wiley. p. 497. ISBN 9780471222019. Retrieved April 28, 2020.
  2. ^ Lerner, Josh; Tirole, Jean (2000). "Some simple economics of open source" (PDF). NATIONAL BUREAU OF ECONOMIC RESEARCH. Retrieved April 30, 2020. Cite journal requires |journal= (help)
  3. ^ Hauben, Michael; Hauben, Ronda (1997). Netizens: On the History and Impact of Usenet and the Internet. p. 170. ISBN 978-0-8186-7706-9.
  4. ^ a b Vixie, Paul A.; Avolio, Frederick M. (2002). Sendmail: Theory and Practice. Elsevier. p. 3. ISBN 9781555582296.
  5. ^ Horton, Mark R. (1986). What is a Domain?. Software Tools Users Group [Sof84]. pp. 368–372. Retrieved April 28, 2020.
  6. ^ a b c d Schmidt 1979, p. 2.
  7. ^ Schmidt 1979, p. 3.
  8. ^ a b c Schmidt 1979, p. 5.
  9. ^ a b Schmidt 1979, p. 6.
  10. ^ Schmidt 1979, p. 7.
  11. ^ a b c Schmidt 1979, p. 8.
  12. ^ a b Schmidt 1979, p. 9.

Bibliography[]

Retrieved from ""