From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] du vs. ls: duplication or not?
Date: Sat, 14 Jan 2012 08:23:20 -0500 [thread overview]
Message-ID: <5941c916c707fbedadd115ad48b662ee@brasstown.quanstro.net> (raw)
In-Reply-To: <20120114080106.GA807@polynum.com>
> du(1) stands for Disk Usage. But does this, with the "historical" use,
> has any real sense now, with a namespace that can be, not only built by
> presenting a same file via different paths, but a combination of local
> storage (including memory one...) and remote storage?
i agree with charles. while one may need to take into account what
you're du'ing, du works as advertized. -s adds up all the directly-used
storage under the given path. now if one points it at something that
might include things one is not interested in, i would say the way to
correct that is by changing the path handed to du.
i think another way to state what you're getting at might be, why
doesn't du have some ai to figure out the exact on-disk footprint
under some path? clearly du can't do that since it's a 9p program,
and won't know a thing about the file server(s) it's talking to.
sort of reminds me of the holy grail, there's no way for du to be
the 1st soldier:
1st soldier: Who goes there?
King Arthur: It is I, Arthur, son of Uther Pendragon, from the castle of Camelot.
King of the Britons, defeater of the Saxons, Sovereign of all England!
1st soldier: Pull the other one!
King Arthur: I am, and this is my trusty servant Patsy. We have ridden the length and breadth
of the land in search of knights who will join me in my court at Camelot.
I must speak with your lord and master.
1st soldier: What? Ridden on a horse?
King Arthur: Yes!
1st soldier: You're using coconuts!
- erik
next prev parent reply other threads:[~2012-01-14 13:23 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
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 [this message]
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=5941c916c707fbedadd115ad48b662ee@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--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).