From: Ray Olszewski <ray@comarre.com>
To: Mike Dresser <mdresser_l@windsormachine.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: how to assess occupied space
Date: Sun, 15 Sep 2002 12:07:36 -0700 [thread overview]
Message-ID: <5.1.0.14.1.20020915120612.0228fd90@celine> (raw)
In-Reply-To: <Pine.LNX.4.33.0209151447040.23713-100000@router.windsormac hine.com>
At 02:51 PM 9/15/02 -0400, Mike Dresser wrote:
>On 15 Sep 2002, Heimo Claasen wrote:
>
> > Thanks for the hints; I didn't know some of the 'du' subtelties.
> > (BTW, is 'du' for _disk_ or for _directory_ use ?)
> >
>
>Disk usage, according to the man pages. But in a way, directory use is
>accurate too.
Where did you find this? It's not in my man page for du. (Just curious.)
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA ray@comarre.com
-------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2002-09-15 19:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-15 0:00 how to assess occupied space Heimo Claasen
2002-09-15 18:51 ` Mike Dresser
2002-09-15 19:05 ` Ray Olszewski
[not found] ` <Pine.LNX.4.33.0209151447040.23713-100000@router.windsormac hine.com>
2002-09-15 19:07 ` Ray Olszewski [this message]
2002-09-15 19:16 ` Mike Dresser
[not found] ` <Pine.LNX.4.33.0209151515110.2321-100000@router.windsormach ine.com>
2002-09-15 19:21 ` Ray Olszewski
-- strict thread matches above, loose matches on Subject: below --
2002-09-15 0:00 Revobild / Heimo Claasen
2002-09-15 4:40 ` Mike Dresser
2002-09-15 12:12 ` Haines Brown
2002-09-15 5:13 ` Ray Olszewski
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=5.1.0.14.1.20020915120612.0228fd90@celine \
--to=ray@comarre.com \
--cc=linux-newbie@vger.kernel.org \
--cc=mdresser_l@windsormachine.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.