Miguel Barão wrote:
> This not a bug but rather an inconsistent output between these two du
> options,
> which is not documented in the manpages.
>
> Suppose 'somefile' is a file containing a lot of zeros.
>
> Then I get:
> $ du -k somefile
> 12
> $ du somefile
> 12
> $ du -b somefile
> 4194432
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Miguel Barão on 10/19/2006 9:47 AM:
> This not a bug but rather an inconsistent output between these two du
> options,
> which is not documented in the manpages.
Read the info documentation instead, where it talks about sparse files.
>
Miguel Barão <[EMAIL PROTECTED]> writes:
> It seems that du -b is returning the size of the file, and not the "disk
> usage" of that file.
Yes, that's how it is documented.
--apparent-size print apparent sizes, rather than disk usage; although
the apparent size
Miguel Barão <[EMAIL PROTECTED]> writes:
> This not a bug but rather an inconsistent output between these two du
> options,
> which is not documented in the manpages.
Maybe you're using an old version of the man pages? The current
version says this:
-b, --bytes
equivalent
Miguel Barão wrote:
This not a bug but rather an inconsistent output between these two du
options, which is not documented in the manpages.
Suppose 'somefile' is a file containing a lot of zeros.
Then I get:
$ du -k somefile
12
$ du somefile
12
$ du -b somefile
4194432
It seems that du -b is
This not a bug but rather an inconsistent output between these two du options,
which is not documented in the manpages.
Suppose 'somefile' is a file containing a lot of zeros.
Then I get:
$ du -k somefile
12
$ du somefile
12
$ du -b somefile
4194432
It seems that du -b is returning the size of
