From owner-freebsd-standards@FreeBSD.ORG Sat May 21 20:32:09 2005 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCF4516A4CE; Sat, 21 May 2005 20:32:09 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C3F343D49; Sat, 21 May 2005 20:32:09 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j4LKW9Di060685; Sat, 21 May 2005 13:32:09 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j4LKW9Hu060684; Sat, 21 May 2005 13:32:09 -0700 (PDT) (envelope-from sgk) Date: Sat, 21 May 2005 13:32:09 -0700 From: Steve Kargl To: Mark Murray Message-ID: <20050521203209.GA60647@troutmask.apl.washington.edu> References: <20050521193605.GB51782@troutmask.apl.washington.edu> <200505212013.j4LKDTMC070728@grovel.grondar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200505212013.j4LKDTMC070728@grovel.grondar.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-standards@FreeBSD.ORG Subject: Re: Read /dev/null differs from POSIX X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 May 2005 20:32:10 -0000 On Sat, May 21, 2005 at 09:13:29PM +0100, Mark Murray wrote: > Steve Kargl writes: > > >From http://www.opengroup.org/onlinepubs/009695399/toc.htm > > > > /dev/null -- An infinite data source and data sink. Data > > written to /dev/null shall be discarded. Reads from > > /dev/null shall always return end-of-file (EOF). > > > > This program > > ... abuses fread(3) return values. > 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. -- Steve