Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:12259 comp.os.386bsd.misc:3146 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!news.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!henson!reuter.cse.ogi.edu!hp-cv!hp-pcd!sdd.hp.com!spool.mu.edu!howland.reston.ans.net!swrinde!news.uh.edu!uuneo.neosoft.com!Starbase.NeoSoft.COM!nobody From: peter@Starbase.NeoSoft.COM (Peter da Silva) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc Subject: Re: Whats wrong with Linux networking ??? Date: 9 Aug 1994 23:06:42 -0500 Organization: NeoSoft Internet Services +1 713 684 5969 Lines: 19 Message-ID: <329joi$eul@Starbase.NeoSoft.COM> References: <Cu107E.Mz3@curia.ucc.ie> <325760$rc9@ra.nrl.navy.mil> <Cu8CBr.Fx@calcite.rhyolite.com> <RSANDERS.94Aug9003813@hrothgar.mindspring.com> NNTP-Posting-Host: starbase.neosoft.com In article <RSANDERS.94Aug9003813@hrothgar.mindspring.com>, Robert Sanders <rsanders@mindspring.com> wrote: >Or the Linux SYSV IPC implementation? (smiles) Why, captain bones, I would hope they'd not import *any* SysV IPC mechanism, seing as it's fundamentally broken as designed since it creates Yet Another name space for no good reason at all, especially when they had named pipes, multiplexed files, Unix domain sockets and the Xenix special-file-based IPC mechanisms as models to start with. IPC has been in the file system, using the file system protection mechanisms, namespace management, and so on since at least *1979*. OK, OK, I can see why you'd have it as a portability hack, but stick it off in /usr/lib/libcruft.so... (and I'm as much a System V bigot as anyone)