From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <a560a5d01001220929x50d560f9yfa27be5f8ba176c6@mail.gmail.com>
References: <a560a5d01001220929x50d560f9yfa27be5f8ba176c6@mail.gmail.com>
Date: Fri, 22 Jan 2010 17:44:23 +0000
Message-ID: <6a3ae47e1001220944v34a952ebv23388e2aaab247a1@mail.gmail.com>
From: Robert Raschke <rtrlists@googlemail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: multipart/alternative; boundary=00032555843abcd21d047dc45eda
Subject: Re: [9fans] find command reloaded
Topicbox-Message-UUID: c288b364-ead5-11e9-9d60-3106f5b1d025

--00032555843abcd21d047dc45eda
Content-Type: text/plain; charset=UTF-8

On Fri, Jan 22, 2010 at 5:29 PM, Rudolf Sykora <rudolf.sykora@gmail.com>wrote:

> Hello,
>
> I've been wondering.
> The plan9 'replacement' for the (linux/unix-like) find command, according
> to the faq, is, in a way,
>
> grep foo `{du -a . | awk '{print $2}'}
>
> Now I want to find all files containing foo.
> Is it so that `{ ... } produces the full list first and only afterwards
> this is used?
> If so (and as I understand it really is so), the number of arguments may be
> enormous, e.g. millions of names...
> I don't feel this is the way to go...
>
> How do you carry out such a search?
>
> Thanks
> Ruda
>
>

Have you come across a situation where it doesn't work or it's too slow for
your needs?

Robby

--00032555843abcd21d047dc45eda
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Fri, Jan 22, 2010 at 5:29 PM, Rudolf Syko=
ra <span dir=3D"ltr">&lt;<a href=3D"mailto:rudolf.sykora@gmail.com">rudolf.=
sykora@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.=
8ex; padding-left: 1ex;">
<div>Hello,<br></div><div><br></div><div>I&#39;ve been wondering.</div><div=
>The plan9 &#39;replacement&#39; for the (linux/unix-like) find command, ac=
cording to the faq, is, in a way,</div><div><br></div><div>grep foo `{du -a=
 . | awk &#39;{print $2}&#39;}</div>


<div><br></div><div>Now I want to find all files containing foo.</div><div>=
Is it so that `{ ... } produces the full list first and only afterwards thi=
s is used? </div><div>If so (and as I understand it really is so), the numb=
er of arguments may be enormous, e.g. millions of names...</div>

<div>I don&#39;t feel this is the way to go...</div><div><br></div><div>How=
 do you carry out such a search?</div><div><br></div><div>Thanks</div><div>=
Ruda=C2=A0</div><div>=C2=A0</div>
</blockquote></div><br>Have you come across a situation where it doesn&#39;=
t work or it&#39;s too slow for your needs?<br><br>Robby<br><br>

--00032555843abcd21d047dc45eda--