From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] du
Date: Thu, 21 Mar 2002 08:37:26 -0500 [thread overview]
Message-ID: <9ac634e947eb39000123f84271f9c74e@plan9.bell-labs.com> (raw)
> Plan 9 du(1) is inconsistent with BSD's: du -s walks down one
> directory in Plan 9 before the summary. I believe that I can achieve
> that effect, should I want it, by entering du -s *, whereas I can't
> achieve the same effect as NetBSD's du -s / using Plan 9's semantics.
>
> Do I need a new du of my own or would the community accept a modified
> du(1) with BSD semantics? Is there a reason for the Plan 9 semantics
> that I am unaware of?
This seems reasonable. I'm not sure why du works this way; it could
be I was trying to reproduce the behavior of the old `research Unix'
version, or I might have thought it was a good idea at the time, or I
might just have screwed up. The code goes out of its way to behave
like this.
In any case, it's trivial to change. Just eliminate the variable
'top' altogether from the function du() in /sys/src/cmd/du.c. I've
made the change on our system.
-rob
next reply other threads:[~2002-03-21 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 13:37 rob pike, esq. [this message]
2002-03-21 13:44 ` Lucio De Re
2002-03-21 13:47 ` Lucio De Re
2002-03-22 10:21 ` bs
-- strict thread matches above, loose matches on Subject: below --
2002-03-21 7:48 Lucio De Re
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=9ac634e947eb39000123f84271f9c74e@plan9.bell-labs.com \
--to=rob@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).