Date: Mon, 25 Dec 2000 13:05:42 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
cc: djgpp-workers AT delorie DOT com
Subject: RE: An implementation of /dev/zero for DJGPP
In-Reply-To: <NEBBIOJNGMKPNOBKHCGHOEAMCAAA.tim.van.holder@pandora.be>
Message-ID: <Pine.SUN.3.91.1001225130436.19455A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Mon, 25 Dec 2000, Tim Van Holder wrote:

> Or you could have some bitmask (_djgpp_fsext_devices?) that is checked
> in the startup code and will call the necessary init functions:
> 
> extern int _djgpp_fsext_devices;
> int _djgpp_fsext_devices = __FSEXT_DEV_ZERO | __FSEXT_DEV_RANDOM;

This will always link in the /dev/zero support.  We are trying to avoid 
bloating each program with code and data it will never use.