From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] du and find
Date: Sat, 2 Jan 2010 18:31:23 -0800 [thread overview]
Message-ID: <20100103023124.7CE9C5B4D@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sat, 02 Jan 2010 20:49:39 EST." <dff576b94c27303e2d6e56152d886254@brasstown.quanstro.net>
On Sat, 02 Jan 2010 20:49:39 EST erik quanstrom <quanstro@quanstro.net> wrote:
> > And can eat up a lot of memory or even run out of it. On a
> > 2+ year old MacBookPro "find -x /" takes 4.5 minutes for 1.6M
> > files and 155MB to hold paths. My 11 old machine has 64MB
> > and over a million files on a rather slow disk. Your solution
> > would run out of space on it.
>
> modern cat wouldn't fit in core on the early pdps unix was
> developed on!
No point in gratuitously obsoleting old machines. I am
running FreeBSD-7.2 on it my 11yo machine and so far it has
stood up well enough.
> just to be fair, could you fit your 1.6m files on your 11yu machine?
> i'm guessing you couldn't.
Yes. It's on its third disk. A 6yo 80G IDE disk.
> > Basically this is just streams programming for arguments
> > instead of data.
>
> that's fine. but it's no excuse to hobble exec. not unless
> you're prepared to be replace argument lists with an argument
> fd.
Not sure how exec is hobbled. Given the way Unix programs
behave you can't replace arg list with an arg fd (I used to
carry around a libary to do just that but the problem is all
the standard programs). Anyway, I don't see how xargs can be
gotten rid of.
next prev parent reply other threads:[~2010-01-03 2:31 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<df49a7371001021043p2a990207od65457a068b7828@mail.gmail.com>
2010-01-02 19:47 ` erik quanstrom
2010-01-02 23:21 ` Bakul Shah
2010-01-03 1:49 ` erik quanstrom
2010-01-03 2:31 ` Bakul Shah [this message]
2010-01-03 2:40 ` erik quanstrom
2010-01-06 20:44 ` Akshat Kumar
[not found] <<20100102052943.GA9871@machine>
2010-01-02 17:05 ` erik quanstrom
2010-01-02 18:18 ` anonymous
[not found] <<df49a7371001011744o6687fd59l451d690ea56edea5@mail.gmail.com>
2010-01-02 2:02 ` erik quanstrom
2010-01-02 5:29 ` anonymous
2010-01-02 18:43 ` roger peppe
2010-01-03 2:28 ` Anthony Sorace
[not found] <<df49a7371001011234r3aaaf961n8ce253a6681e74b1@mail.gmail.com>
2010-01-02 0:51 ` erik quanstrom
2010-01-02 1:44 ` roger peppe
[not found] <<af7cc2a5be1668a4f2cb708f5bd96f67@yyc.orthanc.ca>
2009-12-29 1:22 ` erik quanstrom
2009-12-29 0:41 erik quanstrom
2009-12-29 1:03 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-01-01 20:34 ` roger peppe
[not found] <<68eb39920912281531jd0e4661j56adfc589a370dfc@mail.gmail.com>
2009-12-28 23:35 ` erik quanstrom
2009-12-28 23:39 ` Don Bailey
2009-12-29 1:00 ` anonymous
2009-12-29 1:13 ` Don Bailey
[not found] <<20091228230510.GA25423@machine>
2009-12-28 23:25 ` erik quanstrom
2009-12-28 23:31 ` Don Bailey
2009-12-28 23:50 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
-- strict thread matches above, loose matches on Subject: below --
2009-12-28 23:05 anonymous
2009-12-28 23:09 ` lucio
2009-12-28 23:14 ` Steve Simon
2009-12-29 17:59 ` Tim Newsham
2009-12-29 18:28 ` Don Bailey
2009-12-29 20:16 ` Rob Pike
2009-12-30 7:44 ` anonymous
2010-05-03 12:13 ` Mathieu Lonjaret
2010-05-03 12:18 ` Akshat Kumar
2010-05-03 12:26 ` Mathieu Lonjaret
2010-05-03 12:49 ` tlaronde
2010-05-03 13:10 ` Ethan Grammatikidis
2010-05-03 13:41 ` Steve Simon
2010-05-03 15:18 ` Ethan Grammatikidis
2010-05-03 15:29 ` jake
2010-05-03 15:46 ` Ethan Grammatikidis
2010-05-03 15:37 ` Steve Simon
2010-05-03 13:17 ` Rudolf Sykora
2010-05-03 14:53 ` erik quanstrom
2010-05-03 18:34 ` Jorden M
2010-05-04 10:01 ` Ethan Grammatikidis
2010-05-04 10:29 ` Robert Raschke
2010-05-04 15:38 ` Jorden M
2010-05-04 16:56 ` Gabriel Díaz
2010-05-04 18:39 ` Karljurgen Feuerherm
2010-05-03 14:03 ` 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=20100103023124.7CE9C5B4D@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.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).