From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id 8167d4d3 for ; Fri, 6 Mar 2020 23:06:11 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 7E1289D779; Sat, 7 Mar 2020 09:06:09 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id D6E819D777; Sat, 7 Mar 2020 09:05:42 +1000 (AEST) Received: by minnie.tuhs.org (Postfix, from userid 112) id 873BF9D777; Sat, 7 Mar 2020 09:05:40 +1000 (AEST) X-Greylist: delayed 1267 seconds by postgrey-1.36 at minnie.tuhs.org; Sat, 07 Mar 2020 09:05:39 AEST Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by minnie.tuhs.org (Postfix) with ESMTPS id F07B69D698 for ; Sat, 7 Mar 2020 09:05:39 +1000 (AEST) Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id D226C18C080; Fri, 6 Mar 2020 17:44:31 -0500 (EST) To: tuhs@minnie.tuhs.org Message-Id: <20200306224431.D226C18C080@mercury.lcs.mit.edu> Date: Fri, 6 Mar 2020 17:44:31 -0500 (EST) From: jnc@mercury.lcs.mit.edu (Noel Chiappa) Subject: Re: [TUHS] First appearance of named pipes X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: jnc@mercury.lcs.mit.edu Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" > From: Paul Ruizendaal > The paper is from late 1981. ... When did FIFO's become a > standard Unix feature? Err, V4? :-) At least, that's when pipes arrived (I think - we don't have V4 sources, but there are indications that's when they appeared), and a pipe is a FIFO. RAND ports just allowed (effectively) a pipe to have a name in the file system. The implementation of both is pretty straight-forward. A pipe is just a file which has a maximum length, after which the writer is blocked. A port is just a pipe (it uses the pipe code) whose inode appears in the file system. > From: Clem Cole > I think the code is on one of the 'USENIX' tapes in Warren's archives. Doc is here: https://minnie.tuhs.org//cgi-bin/utree.pl?file=BBN-V6/doc/ipc and sources for all that are here: https://minnie.tuhs.org//cgi-bin/utree.pl?file=BBN-V6/dmr https://minnie.tuhs.org//cgi-bin/utree.pl?file=BBN-V6/ken (port.c is in 'dmr', not 'ken'where it should be). Noel