BSD 4_4 release

[unix-history] / usr / src / share / doc / psd / 21.ipc / 1.t

diff --git a/usr/src/share/doc/psd/21.ipc/1.t b/usr/src/share/doc/psd/21.ipc/1.t
index 5f1d0ba..f4e48ff 100644 (file)
--- a/usr/src/share/doc/psd/21.ipc/1.t
+++ b/usr/src/share/doc/psd/21.ipc/1.t
@@ -1,11 +1,37 @@
-.\" Copyright (c) 1986 The Regents of the University of California.
-.\" All rights reserved.
+.\" Copyright (c) 1986, 1993
+.\"    The Regents of the University of California.  All rights reserved.

 .\"
 .\"

-.\" %sccs.include.redist.roff%
+.\" 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. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"    This product includes software developed by the University of
+.\"    California, Berkeley and its contributors.
+.\" 4. 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.

 .\"
 .\"

-.\"    @(#)1.t 5.1 (Berkeley) %G%
+.\" 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.

 .\"
 .\"

-.\".ds LH "4.3BSD IPC Primer
+.\"    @(#)1.t 8.1 (Berkeley) 8/14/93
+.\"
+.\".ds LH "4.4BSD IPC Primer

 .\".ds RH Introduction
 .\".ds RF "Leffler/Fabry/Joy
 .\".ds LF "\*(DY
 .\".ds RH Introduction
 .\".ds RF "Leffler/Fabry/Joy
 .\".ds LF "\*(DY


@@ -27,14 +53,12 @@ more than two years of discussion and research.  The facilities
 provided in 4.2BSD incorporated many of the ideas from current
 research, while trying to maintain the UNIX philosophy of
 simplicity and conciseness.
 provided in 4.2BSD incorporated many of the ideas from current
 research, while trying to maintain the UNIX philosophy of
 simplicity and conciseness.

-The current release of Berkeley UNIX, 4.3BSD,
-completes some of the IPC facilities
-and provides an upward-compatible interface.
-It is hoped that the interprocess communication
-facilities included in 4.3BSD will establish a
-standard for UNIX.  From the response to the design,
-it appears many organizations carrying out
-work with UNIX are adopting it.
+The 4.3BSD release of Berkeley UNIX
+improved upon some of the IPC facilities
+while providing an upward-compatible interface.
+4.4BSD adds support for ISO protocols and IP multicasting.
+The BSD interprocess communication
+facilities have become a defacto standard for UNIX.

 .PP
 UNIX has previously been very weak in the area of interprocess
 communication.  Prior to the 4BSD facilities, the only
 .PP
 UNIX has previously been very weak in the area of interprocess
 communication.  Prior to the 4BSD facilities, the only


@@ -51,8 +75,8 @@ Earlier attempts at extending the IPC facilities of UNIX have
 met with mixed reaction.  The majority of the problems have
 been related to the fact that these facilities have been tied to
 the UNIX file system, either through naming or implementation.
 met with mixed reaction.  The majority of the problems have
 been related to the fact that these facilities have been tied to
 the UNIX file system, either through naming or implementation.

-Consequently, the IPC facilities provided in 4.3BSD have been
-designed as a totally independent subsystem.  The 4.3BSD IPC
+Consequently, the IPC facilities provided in 4.2BSD were
+designed as a totally independent subsystem.  The BSD IPC

 allows processes to rendezvous in many ways. 
 Processes may rendezvous through a UNIX file system-like
 name space (a space where all names are path names)
 allows processes to rendezvous in many ways. 
 Processes may rendezvous through a UNIX file system-like
 name space (a space where all names are path names)


@@ -68,7 +92,7 @@ more use is made of these facilities they will be refined;
 only time will tell.
 .PP
 This document provides a high-level description
 only time will tell.
 .PP
 This document provides a high-level description

-of the IPC facilities in 4.3BSD and their use.
+of the IPC facilities in 4.4BSD and their use.

 It is designed to complement the manual pages for the IPC primitives
 by examples of their use.
 The remainder of this document is organized in four sections.  
 It is designed to complement the manual pages for the IPC primitives
 by examples of their use.
 The remainder of this document is organized in four sections.