Messages in this thread | | | Subject | Re: Reading empty file (was: Re: /dev/full) | Date | Wed, 23 Dec 1998 17:03:31 -0500 | From | "Brandon S. Allbery KF8NH" <> |
| |
In message <19981223115950.B1207@dallas.net>, Fuzzy Fox writes: +----- | > It's not strange, it's what /dev/null is for. /dev/full isn't as widespread | > as /dev/null is. | | Reading from /dev/null gives immediate EOF. Reading from /dev/full | gives the same results as reading from /dev/zero. +--->8
Reading from /dev/full gives bytes=0, error=ENOSPC, as recently reported (after I conflated it with another /dev/full I've seen somewhere). A program which gets the same result from /dev/full as /dev/null is a program without proper error checking; a program which gets the same results from /dev/full as /dev/zero has a bug.
-- brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net system administrator [WAY too many hats] allbery@ece.cmu.edu carnegie mellon / electrical and computer engineering KF8NH We are Linux. Resistance is an indication that you missed the point.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |