9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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: Mon, 16 Jan 2012 18:43:18 +0100	[thread overview]
Message-ID: <20120116174318.GA382@polynum.com> (raw)
In-Reply-To: <4F144CBD.2000208@gmail.com>

On Mon, Jan 16, 2012 at 11:13:49AM -0500, Joel C. Salomon wrote:
> 
> My guess would be that this discussion illustrates exactly why: ls(1) is
> a gadget that pretty-prints the directory entry.  Extending it with '-R'
>  would require it to learn about possibly-circular mount points; yuck.
> On the other hand, du(1) has this sort of feature as its raison d'être.

And as my blunders have shown, du(1) tries but does not succeed.

And Disk Usage has only a meaning on a file server for the file locally
served. 

But the thread will be going nowhere, since, if I'm convinced that du(1)
is special, I'm not convinced it makes really sense as a "general" tool
in a Plan9 environment.

But let this thread dies. I have some job to do on fdisk.
-- 
        Thierry Laronde <tlaronde +AT+ polynum +dot+ com>
                      http://www.kergis.com/
Key fingerprint = 0FF7 E906 FBAF FE95 FD89  250D 52B1 AE95 6006 F40C



  reply	other threads:[~2012-01-16 17:43 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 [this message]
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=20120116174318.GA382@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).