From owner-freebsd-emulation  Wed Nov 19 17:00:41 1997
Return-Path: <owner-freebsd-emulation>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id RAA19527
          for emulation-outgoing; Wed, 19 Nov 1997 17:00:41 -0800 (PST)
          (envelope-from owner-freebsd-emulation)
Received: from hoser (root@in221.inetnebr.com [199.184.119.221])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA19513
          for <freebsd-emulation@FreeBSD.ORG>; Wed, 19 Nov 1997 17:00:31 -0800 (PST)
          (envelope-from cradek@in221.inetnebr.com)
To: freebsd-emulation@FreeBSD.ORG
Subject: Re: Running Linux FlagShip under FreeBSD-current
References: <28090.879284476@time.cdrom.com>
Mime-Version: 1.0 (generated by tm-edit 7.94)
Content-Type: text/plain; charset=US-ASCII
From: Chris Radek <cradek@in221.inetnebr.com>
Date: 19 Nov 1997 19:00:14 -0600
In-Reply-To: "Jordan K. Hubbard"'s message of "Tue, 11 Nov 1997 13:41:16 -0800"
Message-ID: <oaiutov0pt.fsf@hoser.inetnebr.com>
Lines: 17
X-Mailer: Gnus v5.4.66/XEmacs 19.14
Sender: owner-freebsd-emulation@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

"Jordan K. Hubbard" <jkh@time.cdrom.com> writes:

> > Can anyone tell me what /dev/full is?  If I can get around that, it looks
> > like FlagShip should work.
> 
> I believe it's like /dev/zero but generates all 1s instead of all 0s.

I've seen a few guesses but none of them are correct so far; I hope
there aren't a hundred people answering this by the time I do.

The point of /dev/full is that a write() fails (returns -1) and sets
errno to ENOSPC.  On Linux, it looks like reading /dev/full is the same
as reading /dev/zero.

(from src/linux/drivers/char/mem.c)

-Chris