Date: Sat, 21 May 2005 14:03:09 -0700 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Mark Murray <markm@FreeBSD.ORG> Cc: freebsd-standards@FreeBSD.ORG Subject: Re: Read /dev/null differs from POSIX Message-ID: <20050521210309.GA60844@troutmask.apl.washington.edu> In-Reply-To: <200505212042.j4LKgk8i071299@grovel.grondar.org> References: <20050521203209.GA60647@troutmask.apl.washington.edu> <200505212042.j4LKgk8i071299@grovel.grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 21, 2005 at 09:42:46PM +0100, Mark Murray wrote: > Steve Kargl writes: > > Sorry for the noise. I remembered feof() about 15 minutes > > ago. FreeBSD's null(4) man page, although quite short, is > > somewhat confusing in its vagueness. > > NP. If the docs don't work, I guess we need to fix them. Given that > I've had my grimy paws in null(4), it seems fair that I fix the docs. > > I'll give them a general looking over, but if you have any suggestions > you'd like to see put in there, I'd be happy to oblige. > I have to run to a little league baseball game, so I think about there. Something along the lines: The null device has permission 666. Upon writing to /dev/null, the data is thrown away. Upon reading /dev/null, it will always return EOF. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050521210309.GA60844>