From: Mike Fedyk <mfedyk@matchmail.com>
To: Dave O <cxreg@pobox.com>
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-hfsplus-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] new HFS(+) driver
Date: Thu, 2 Oct 2003 17:26:08 -0700 [thread overview]
Message-ID: <20031003002608.GC13051@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0310021359140.31213@narbuckle.genericorp.net>
On Thu, Oct 02, 2003 at 02:00:25PM -0500, Dave O wrote:
> This works, however du(1) seems to get the block size wrong:
>
> meatloop:/cdrom# ls -l
> total 393244
> -rwxr-xr-x 1 501 dialout 341952833 Sep 22 17:24 else.zip
> -rwxr-xr-x 1 501 dialout 450701627 Sep 22 20:07 outlook.zip
> -rwxr-xr-x 1 501 dialout 607534655 Sep 22 17:26 quick1.zip
> -rwxr-xr-x 1 501 dialout 431279243 Sep 22 17:26 quick2.zip
> -rwxr-xr-x 1 501 dialout 605501959 Sep 22 17:27 quick3.zip
> -rwxr-xr-x 1 501 dialout 403836898 Sep 22 17:28 quick4.zip
> -rwxr-xr-x 1 501 dialout 380636073 Sep 22 17:28 quick5.zip
>
> meatloop:/cdrom# du -sh
> 385M .
Are you sure? I haven't done the math, but you are comparing base 1000 to
base 1024 numbers. Try comparing:
du -sh .
ls -lh
next prev parent reply other threads:[~2003-10-03 0:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 8:37 [ANNOUNCE] new HFS(+) driver Roman Zippel
2003-10-02 18:02 ` Dave O
2003-10-02 18:30 ` Roman Zippel
2003-10-02 19:00 ` Dave O
2003-10-03 0:26 ` Mike Fedyk [this message]
2003-10-03 2:43 ` Dave O
2003-10-02 18:06 ` viro
2003-10-02 18:24 ` Roman Zippel
2003-10-02 18:52 ` Brad Boyer
2003-10-06 19:38 ` Mike Fedyk
2003-10-06 19:47 ` Brad Boyer
2003-10-03 7:04 ` J.A. Magallon
2003-10-03 10:30 ` Roman Zippel
2003-10-03 22:39 ` J.A. Magallon
2003-10-04 3:00 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031003002608.GC13051@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=cxreg@pobox.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-hfsplus-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox