Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!brutus.cs.uiuc.edu!wuarchive!texbell!sugar!peter
From: peter@sugar.hackercorp.com (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Minix, Unix on the Amiga, and flames on AmigaDOS braindamage...
Message-ID: <4118@sugar.hackercorp.com>
Date: 16 Aug 89 11:37:25 GMT
References: <1610@uw-entropy.ms.washington.edu> <195@VAX1.CC.UAKRON.EDU> <4148@cps3xx.UUCP>
Organization: Sugar Land Unix - Houston
Lines: 23

In article <4148@cps3xx.UUCP>, usenet@cps3xx.UUCP (Usenet file owner) writes:
> Most UNIX programs *do not* ever check this. UNIX programmers assume
> a blissful computer with plenty enough VM to get by.

This is pure garbage. I don't think I've seen any ordinary UNIX programs
that do this. Now things might be different in the X-windows world, where
they have a rather cavalier attitude towards resource usage. You did
mention that you're using a Sun...

(speaking of Suns, we just got one at work. *This* is supposed to be a
better product than System V? It's sure got more bells and whistles,
but the amount of integration and productizing is virtually nil)

If you want to point a finger at UNIX programs, there is a problem with the
assumption that disk space is effectively infinite... but I've not seen too
many Amiga programs that check for this, either. A few, yes, so it shows a bit
more care... but most still ignore error returns from Write.

Now Amiga programmers, on the other hand, do tend to leave dead file locks
lying around...
-- 
Peter "Have you hugged your wolf today" da Silva      `-_-'
...texbell!sugar!peter, or peter@sugar.hackercorp.com  'U`