From: tlaronde@polynum.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] du vs. ls: duplication or not?
Date: Sun, 15 Jan 2012 17:18:31 +0100 [thread overview]
Message-ID: <20120115161831.GA624@polynum.com> (raw)
In-Reply-To: <CAOw7k5iApz8mkb1kaBQe+4rG-TTC1oOLu1kYJQDmrFCx7QCC_Q@mail.gmail.com>
On Sat, Jan 14, 2012 at 09:20:51AM +0000, Charles Forsyth wrote:
>[...] 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).
I wasn't refering to whatever implementation (I don't use ls -R either
since the output is simply not parsable). I was simply using -R, since
-r is already taken.
What I meant was the size of the file is already given via ls(1). So
a recursive output that make sense and fit a manipulation via join(1)
(to combine a srv/qid) and sort and uniq etc. could do the trick.
Since ls(1) gives the size of the file; since du(1) can not really or at
least not always in an arbitrary context tells the "real" occupation of
disk size, is not ls(1) enough?
--
Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
next prev parent reply other threads:[~2012-01-15 16:18 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
2012-01-15 16:18 ` tlaronde [this message]
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=20120115161831.GA624@polynum.com \
--to=tlaronde@polynum.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).