*BSD News Article 34077


Return to BSD News archive

Xref: sserve comp.os.386bsd.questions:12192 comp.os.386bsd.misc:3096
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!convex!convex!news.duke.edu!news-feed-1.peachnet.edu!emory!cherry.atlanta.com!nntp.mindspring.com!usenet
From: rsanders@mindspring.com (Robert Sanders)
Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.misc
Subject: Re: Whats wrong with Linux networking ???
Date: 10 Aug 1994 05:42:22 GMT
Organization: MindSpring Enterprises, Inc.
Lines: 35
Message-ID: <RSANDERS.94Aug10014226@hrothgar.mindspring.com>
References: <Cu107E.Mz3@curia.ucc.ie> <325760$rc9@ra.nrl.navy.mil>
	<Cu8CBr.Fx@calcite.rhyolite.com>
	<RSANDERS.94Aug9003813@hrothgar.mindspring.com>
	<329joi$eul@Starbase.NeoSoft.COM>
NNTP-Posting-Host: hrothgar.mindspring.com
In-reply-to: peter@Starbase.NeoSoft.COM's message of 9 Aug 1994 23:06:42 -0500

On 9 Aug 1994 23:06:42 -0500, peter@Starbase.NeoSoft.COM (Peter da Silva) said:

> 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

Well, at least the NetBSD folks seem to think it's important enough to
spend time on.  Remember, the main topic of this discussion now is NIH
and re-implementation, not whether the cases in point should be
implemented at all.

> OK, OK, I can see why you'd have it as a portability hack, but stick
> it off in /usr/lib/libcruft.so...

Are you suggesting a user-level implementation (ick), or are you
saying that you don't want space in libc taken up, or are you saying
that these IPC mechanisms should be deprecated by additional link-time
pains?  The first is sheer lunacy, the second would be silly (syscall
stubs are tiny, and ftok() trivial), and the third sort of ruins the
point of backwards compatibility.

Most of today's Unix is baggage that should be discarded for better
(and, as you say, sometimes older) solutions.  I'm not sure there's
any baby left to separate from the bathwater.  But this is all old
news and not worth discussing; please don't pollute this noise with
irrelevent noise or I'll have to drop the whole thing and do something
useful.

  -- Robert