From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] du vs. ls: duplication or not?
Date: Sat, 14 Jan 2012 09:20:51 +0000 [thread overview]
Message-ID: <CAOw7k5iApz8mkb1kaBQe+4rG-TTC1oOLu1kYJQDmrFCx7QCC_Q@mail.gmail.com> (raw)
In-Reply-To: <20120114080106.GA807@polynum.com>
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
Du answers the question: (roughly) how big are these files (the files in
these directories)?
It still does that reasonably well in Plan 9 (I'm not ruling out possible
improvements, but "it works for me!").
It doesn't answer questions about physical storage. On my Linux machines, I
do use it as a guide to
"which of my or the system's directories is exhausting the space on my
SSD", with du -s * | sort +0nr
[in rc on Linux: with sh you'd need to account for the stupid dotfile
convention]. On Plan 9, I more often
use it to see roughly how much data I'm going to move to a remote machine,
or whether I've left temporary
objects and executables, or whether to tar | gzip something. I sometimes
use du -a to list the names in a
hierarchy, but then I do the same on Linux (or I use find). On Linux, I
never use ls -R, partly because I'm
running p9p's ls, but mainly because the default format of /bin/ls -R is
amazingly useless (even worse than I remembered).
[-- Attachment #2: Type: text/html, Size: 1125 bytes --]
next prev parent reply other threads:[~2012-01-14 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-14 8:01 tlaronde
2012-01-14 9:20 ` Charles Forsyth [this message]
2012-01-15 16:18 ` tlaronde
2012-01-15 21:17 ` erik quanstrom
2012-01-16 11:46 ` tlaronde
2012-01-16 16:13 ` Joel C. Salomon
2012-01-16 17:43 ` tlaronde
2012-01-16 18:06 ` erik quanstrom
2012-01-14 9:45 ` David du Colombier
2012-01-14 13:23 ` erik quanstrom
2012-01-16 7:39 arnold
2012-01-16 11:55 ` tlaronde
2012-01-16 13:21 ` erik quanstrom
2012-01-16 13:24 ` erik quanstrom
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=CAOw7k5iApz8mkb1kaBQe+4rG-TTC1oOLu1kYJQDmrFCx7QCC_Q@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).