From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] du vs. ls: duplication or not?
Date: Mon, 16 Jan 2012 08:21:47 -0500 [thread overview]
Message-ID: <0a0ca940937f390bd435a89a8604dd06@brasstown.quanstro.net> (raw)
In-Reply-To: <20120116115545.GB618@polynum.com>
> That's indeed a reason, showing that ls(1) is more on the abstract level
> (whatever the implementation, ls(1) shows ownership and permissions
> ---that can have no real relationship in the actual store) while du(1)
> tries to show effective story and needs to know more about effective
> storage.
>
> And it can work only with some filesystems. (Think ftpfs etc. and think
> sharing of blocks)
du works the same with all file servers.
i think the problem here is applying semantics to the output. du
performance a specified operation (adding up the d->size in the
stat output.) as is plan 9 tradition, what that /means/ is up to the
file server you're talking to.
- erik
next prev parent reply other threads:[~2012-01-16 13:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 7:39 arnold
2012-01-16 11:55 ` tlaronde
2012-01-16 13:21 ` erik quanstrom [this message]
2012-01-16 13:24 ` erik quanstrom
-- strict thread matches above, loose matches on Subject: below --
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
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=0a0ca940937f390bd435a89a8604dd06@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).