Lines Matching full:unix
54 Berkeley UNIX\(dg 4.4BSD offers several choices for interprocess communication.
66 \(dg\|UNIX is a trademark of AT&T Bell Laboratories.
73 were a major addition to UNIX in the Berkeley UNIX 4.2BSD release.
77 In UNIX a process has a set of I/O descriptors, from which one reads
90 Pipes are another form of descriptor that have been used in UNIX
97 provided by UNIX.
106 The identification of IPC with I/O is quite longstanding in UNIX and
108 processes communicating within a single machine. With Berkeley UNIX
120 available. These new possibilities are allowed in the Berkeley UNIX IPC
123 Thus Berkeley UNIX 4.4BSD offers several choices for IPC.
128 but not necessarily with the system calls of the UNIX system or with
131 communication that are supported by Berkeley UNIX 4.4BSD.
152 In UNIX these lines can never join again. A call to the system routine
173 (devices are also treated as files in UNIX), the child's input will
183 Most users of UNIX know that they can pipe the output of a
277 Berkeley UNIX 4.4BSD provides a slight generalization of pipes. A pipe is a
298 domain, called the UNIX domain.
299 The UNIX domain uses UNIX path names for naming sockets.
333 Neither standard UNIX pipes nor socketpairs are
340 In Berkeley UNIX 4.4BSD one can create individual sockets, give them names and
348 Two that will be used in the examples here are the UNIX domain (or AF_UNIX,
349 for Address Format UNIX) and the Internet domain (or AF_INET).
350 UNIX domain IPC is an experimental facility in 4.2BSD and 4.3BSD.
351 In the UNIX domain, a socket is given a path name within the file system
355 UNIX domain names, therefore, allow communication between any two processes
357 The Internet domain is the UNIX implementation of the DARPA Internet
416 in the UNIX domain.
418 .sh 1 "Datagrams in the UNIX Domain"
425 Figure 5a\ \ Reading UNIX domain datagrams
431 The structure used to name UNIX domain sockets is defined
436 These sockets are in the UNIX domain.
450 Figure 5b\ \ Sending a UNIX domain datagrams
453 Names in the UNIX domain are path names. Like file path names they may
465 Names in the UNIX domain are only used for rendezvous. They are not used
496 Unlike UNIX domain names, Internet socket names are not entered into
558 will not work for names in the UNIX domain.
678 in the UNIX domain. Streams in the UNIX domain can be used for this sort
690 Figure 9a\ \ Initiating a UNIX domain stream connection
696 Figure 9b\ \ Accepting a UNIX domain stream connection
702 UNIX 4.4BSD has several system calls for reading and writing information.
764 including, in the UNIX domain, the transmission of a file descriptor from one
827 Berkeley UNIX 4.4BSD. These have been presented in an order chosen for
832 UNIX systems. They also are relatively
838 The two communication domains, UNIX and Internet, allow processes with no common
868 An introduction to the UNIX system and programming using UNIX system calls
870 Further documentation of the Berkeley UNIX 4.4BSD IPC mechanisms can be
875 UNIX Programmer's Manual [CSRG 1986].
912 .i "The UNIX Programming Environment."
929 .i "UNIX Programmer's Manual, 4.4 Berkeley Software Distribution."