Date:	Tue, 2 Jan 2001 11:23:49 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc:	DJGPP workers <djgpp-workers AT delorie DOT com>
Subject:	Re: An implementation of /dev/zero for DJGPP
In-Reply-To:	<3A50E72B.2B422C95@phekda.freeserve.co.uk>
Message-ID:	<Pine.SUN.3.91.1010102112330.18307G-100000@is>
MIME-Version:	1.0
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

On Mon, 1 Jan 2001, Richard Dawe wrote:

> > I'm not sure this is a grave limitation, but it at least should be
> > documented somewhere.
> 
> I don't think this is a grave limitation either, since child programs will
> be still be able to use /dev/zero, /dev/full.
> 
> Where do you think the best place to document this limitation is? In the
> source code or in the library documentation?

In the docs of __dev_zero_init, I guess.  You want to say that the
/dev/zero emulation will not work in a debugger.

It is probably a good idea to add to the general FSEXT docs a comment
which says that _any_ FSEXT will probably not work in a debugger.

> Actually, this leads to me to another question - why is
> the section containing the FIONBIO ioctl #if 0'd out in sys/ioctl.h? Is
> this to prevent some Unixy programs from thinking that we support, e.g.
> terminal ioctls?

Yes.  Actually, the entire Unixy part of ioctl.h is ifdef'ed away,
since that functionality is not supported.  FIONBIO is just one of the
bits which got the axe...

- Raw text -