Date: Sat, 6 Jan 2001 16:41:42 -0500 Message-Id: <200101062141.QAA18992@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: djgpp-workers AT delorie DOT com In-reply-to: <8632-Sat06Jan2001203659+0200-eliz@is.elta.co.il> Subject: Re: /dev/zero & /dev/full FSEXTs References: <8632-Sat06Jan2001203659+0200-eliz AT is DOT elta DOT co DOT il> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Shouldn't /dev/full be NOT ready for writing? What does `select' > return on Unix systems for the /dev/full device in this case? It needs to be ready, so that the app will try to write to it and see that it's full. If it's never ready, the program will wait forever.