delorie.com/archives/browse.cgi | search |
Date: | Tue, 26 Dec 2000 17:52:51 -0500 |
Message-Id: | <200012262252.RAA24612@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 <dj AT delorie DOT com> |
To: | djgpp-workers AT delorie DOT com |
In-reply-to: | <3A489766.349B3C71@bigfoot.com> (message from Richard Dawe on |
Tue, 26 Dec 2000 13:04:38 +0000) | |
Subject: | Re: An implementation of /dev/zero for DJGPP |
References: | <Pine DOT SUN DOT 3 DOT 91 DOT 1001225105646 DOT 18547E-100000 AT is> <3A489766 DOT 349B3C71 AT bigfoot DOT com> |
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 |
> BTW there's a device call /dev/full on Linux, which returns zeroes when > read, but returns ENOSPC when written to. This could easily be added to > the /dev/zero framework. If there are any good uses for /dev/full, then > I'll add this. Otherwise I'll just add a note to the /dev/zero sources. I can see this being useful for testing handling of disk full errors.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |