9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Wolfgang Helbig <helbig@mailbox.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Replacement for find
Date: Wed, 30 Sep 2015 11:33:30 +0200	[thread overview]
Message-ID: <5F9B8349-6B7F-4213-84FF-50D65B5159E6@mailbox.org> (raw)
In-Reply-To: <CAFSF3XNtzVucb7xup_0WNA_tBz2Ln=4cU6fLX8hGd6T+=XvgLA@mail.gmail.com>

In Plan 9 a command is needed, that lists recursively all files. Not more and not less. The du(1) command offers too much. I do not want to list the disk usage!

The command du(1) from the second edition of plan9 only has two command line options (-a and -b size),
whereas du(1) from
	http://github.com/0intro/plan9
offers twelve options
and from 
	http://github.com/9fans/plan9port (aka Plan 9 from User Space)
eight options.
All three distributions come w/o the man page.
The Second Edition seems closest to what is needed — A du -a without the disk usage. Lets call it recurse(1). Its man page reads:
NAME:
	recurse - list recursively the file names
SYNOPSIS:
	recurse name …
DESCRIPTION
	For each directory argument print recursively the filenames in the directory, for each filename argument,
	repeat the filename.

SEE ALSO:
	ls(1)

What do you think of it?

With this, du(1) can be simplified by printing the disk usage of its arguments only.

Greetings,
Wolfgang

The sizes of the three sources differ tremendously from 
> Am 30.09.2015 um 10:23 schrieb hiro <23hiro@gmail.com>:
> 
> I'm surprised you can even remember find's command line options.
> If you need to optimize this cause you have a jillion files and think
> du takes too long i'd suggest creating an index of all files you have,
> sorted into a text file.
> Then you only have to use grep filename index.
> 




  parent reply	other threads:[~2015-09-30  9:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30  8:01 Wolfgang Helbig
2015-09-30  8:09 ` lucio
2015-09-30  8:11 ` Charles Forsyth
2015-09-30  8:23   ` hiro
2015-09-30  8:27     ` lucio
2015-09-30 10:34       ` hiro
2015-09-30  9:33     ` Wolfgang Helbig [this message]
2015-09-30  9:58       ` Aram Hăvărneanu
2015-09-30 10:41         ` Wolfgang Helbig
2015-09-30 10:45           ` hiro
2015-09-30 10:07       ` Steve Simon
2015-09-30 10:55         ` Mark van Atten
2015-09-30 11:25           ` Wolfgang Helbig
2015-09-30 13:20   ` erik quanstrom
2015-09-30 14:32     ` arnold
2015-10-01  0:06       ` sl
2015-09-30 14:57     ` Steven Stallion
2015-09-30 10:31 ` Brantley Coile
  -- strict thread matches above, loose matches on Subject: below --
2015-09-30  6:26 Wolfgang Helbig
2015-09-30  6:39 ` Alexander Kapshuk
2015-09-30  6:54 ` Mark van Atten
2015-09-30  7:39   ` hiro

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=5F9B8349-6B7F-4213-84FF-50D65B5159E6@mailbox.org \
    --to=helbig@mailbox.org \
    --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).