Date: Wed, 12 Jul 2000 19:17:54 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
cc: djgpp AT delorie DOT com
Subject: Re: Filetree disk size
In-Reply-To: <Pine.LNX.4.10.10007121719030.32191-100000@acp3bf>
Message-ID: <Pine.SUN.3.91.1000712191537.4869A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 12 Jul 2000, Hans-Bernhard Broeker wrote:

> > It's a simple change, and is a useful feature to have.  `du' expects the 
> > library to return the block size, and if it does not, falls back to some 
> > simple-minded default.  
> 
> What library? What 'block size' does it read from it?

See the definition of the macro ST_NBLOCKS on src/system.h in the 
Fileutils distribution.

> According to the fileutils 4.0 docs I consulted, du only uses block size
> for displaying, not for measuring the file length.

IANL, but the code disagrees, or so it seems: the size of each file is 
run through ST_NBLOCKS.