Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!sdcsvax!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Transparent Asynchronous I/O.
Message-ID: <8708310745.AA01722@cory.Berkeley.EDU>
Date: Mon, 31-Aug-87 03:45:32 EDT
Article-I.D.: cory.8708310745.AA01722
Posted: Mon Aug 31 03:45:32 1987
Date-Received: Tue, 1-Sep-87 01:16:23 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 12

>In article <4160003@hpspdla.HP.COM> paulz@hpspdla.HP.COM (Paul Zander) writes:
>>Having once used a computer which buffers all I/O, I can
>>say that it can be a real pain in the a**.  [ ... ]  It would send the
>>write to the buffer, then proceed to the fatal error, leaving
>>some of the diagnostics still in the buffer!  
>> 
>Leo L. Schwab:
>	That is why God invented kprintf().				:-)

	And why STDERR is always unbuffered (or supposed to be).

					-Matt