Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!think!ames!pasteur!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Fork--impossible, and here's why
Message-ID: <8805151800.AA08332@cory.Berkeley.EDU>
Date: 15 May 88 18:00:43 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 14

>Fork() has one side effect that most people miss--ALL things are duplicated.
>In particular, both people have file handles to the same files, but
>AmigaDos will not let you get multiple writers to the same file no matter
>what you do (a BIG limit, in my opinion).
>
>Worse, in unix, a fork gives you dup'd file descriptors--i.e., if either
>process does a read, both have their next read address incremented.

	Actually, it does.  When you Open() a file 1005, it obtains a 
shared lock and you can still write to the file...  But, as you said,
doesn't give the duplicity or even have a Dup() call.  AmigaDos really
does need a Dup() call!

				-Matt