Date: Sun, 24 Dec 2000 15:03:42 -0500
Message-Id: <200012242003.PAA29486@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <2110-Sun24Dec2000202824+0200-eliz@is.elta.co.il>
Subject: Re: An implementation of /dev/zero for DJGPP
References: <3A460B93 DOT 2347528B AT bigfoot DOT com> <2110-Sun24Dec2000202824+0200-eliz AT is DOT elta DOT co DOT il>
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
Precedence: bulk


> This actually raises a more serious problem: how does an application
> requests that /dev/zero support to be linked in?

One way is via command line:

	gcc -Wl,-u,__use_dev_zero ...

Or, in main,

	__use_dev_zero();

I think very few programs actually need /dev/zero; dd is the only one
(aside from programs that mmap() it for shared memory, which we don't
support (yet?)) that I can think of that really benefits from it.

I guess it depends on how big the handler is, and if we want to carry
that kind of load in *every* program, and how big such a load can get
as we add more and more handlers.

I would think that making it the default would be wrong in general.