X-Authentication-Warning:	acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date:	Wed, 12 Jul 2000 12:55:33 +0200 (MET DST)
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender:	broeker AT acp3bf
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp AT delorie DOT com
Subject:	Re: Filetree disk size
In-Reply-To:	<Pine.SUN.3.91.1000712074743.759B-100000@is>
Message-ID:	<Pine.LNX.4.10.10007121229440.32191-100000@acp3bf>
MIME-Version:	1.0
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

On Wed, 12 Jul 2000, Eli Zaretskii wrote:

Speaking about 'du':

> Unfortunately, it also doesn't take the exact cluster size into account, 
> so the size it prints is always less than the actual size.
> 
> Perhaps a future port of Fileutils could take care of this.

I'm not too sure. That had better be introduced not in the DJGPP port, but
as a new feature to the FSF version, and then implemented for all ports
using FAT filesystems, simultaneously.

'du' is traditionally defined to disregard any filesystem chunkyness. So
it works in terms of bytes, and only displays the result as sector counts
(512 bytes per sector, says POSIX). Printing sizes in units of clusters
(or whatever the equivalent thing is called is called) would be useful for
other platforms, too, but is not (yet) a part of the job description of
'du'.

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -