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 12:46:18 +0100	[thread overview]
Message-ID: <20120116114618.GA618@polynum.com> (raw)
In-Reply-To: <d4aaeac9019d72d94f2bb7c6af6ab1a1@chula.quanstro.net>

On Sun, Jan 15, 2012 at 04:17:43PM -0500, erik quanstrom wrote:
> > 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?
>
> plan 9 ls does not have a -R option.

It seems what I'm trying to say is not clear. I know that shipping Plan9
has no '-R'. What I mean is, since find(1) and others are not here
because they are duplicating other utils, and can be recreated with
other "primitives", why du(1) was kept and not simply ls(1) extended
with a '-R'? Since ls(1) already displays the size of a file (in bytes).

--
        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 11:46 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 [this message]
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=20120116114618.GA618@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).