jmc@root44.UUCP (06/22/83)
When I first heard of FIFOs (as in System III et al) I thought "what a good idea". We've been running System III for a year now, and the curious fact is that we haven't actually used them.... I was just wondering if anyone regularly did....... John Collins .....!vax135!ukc!root44!jmc
ken@turtleva.UUCP (06/25/83)
What makes a FIFO (I assume that you are talking about software FIFOs)
different than a pipe?
Ken Turkowski
{decwrl,amd70}!turtlevax!kengwyn%brl-vld@sri-unix.UUCP (06/27/83)
From: Doug Gwyn (VLD/VMB) <gwyn@brl-vld> A FIFO is a "named pipe". I.e., it acts like a pipe but can be opened by its name in the file system rather than having to be passed as an open fd created by a parent process. The additional kernel code to support FIFOs was minimal, which may have something to do with this facility being there; it integrates nicely with the existing pipe and file facilities. This idea was tried by RAND Corp. several years ago but wasn't implemented as cleanly. One could use a FIFO for any server daemon; the known file name would serve as a port to send requests to. Berkeley sockets could also be used this way.