Article View: comp.std.unix
Article #594Re: Standards Update, IEEE 1003.4: Real-time Extensions
From: Chip Salzenberg
Date: Thu, 04 Oct 1990 20:39
Date: Thu, 04 Oct 1990 20:39
16 lines
1217 bytes
1217 bytes
Submitted-by: chip@tct.uucp (Chip Salzenberg) According to fouts@bozeman.bozeman.ingr (Martin Fouts): >One reason to not treat every IPC facility as part of the file system: >Shared memory IPC mechanisms which don't need to be visible to processes >not participating in the IPC. Yes, it is obviously desirable to have IPC entities without names. This feature is a simple extension of the present ability to keep a plain file open after its link count falls to zero. Of course, the committee could botch the job by making it an error to completely unlink a live IPC. -- Chip Salzenberg at Teltronics/TCT <chip@tct.uucp>, <uunet!pdn!tct!chip> Volume-Number: Volume 21, Number 186
Technical Details
Message-ID:
<13219@cs.utexas.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!jsqReferences:
<540@usenix.ORG> <553@usenix.ORG> <13132@cs.utexas.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!jsq From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.std.unix Subject: Re: Standards Update, IEEE 1003.4: Real-time Extensions Message-ID: <13219@cs.utexas.edu> Date: 4 Oct 90 20:39:37 GMT References: <540@usenix.ORG> <553@usenix.ORG> <13132@cs.utexas.edu> Sender: jsq@cs.utexas.edu Organization: Teltronics/TCT, Sarasota, FL Lines: 16 Approved: jsq@cs.utexas.edu (Moderator, John S. Quarterman) X-Submissions: std-unix@uunet.uu.net