Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!pprg.unm.edu!topgun.dspo.gov!lanl!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.unix.wizards
Subject: Re: Look!  An xargs!!
Message-ID: <10933@smoke.BRL.MIL>
Date: 4 Sep 89 05:47:04 GMT
References: <666@lakart.UUCP> <1641@cbnewsl.ATT.COM> <7774@cbmvax.UUCP> <4026@buengc.BU.EDU> <1122@virtech.UUCP> <16816@pasteur.Berkeley.EDU>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 9

In article <16816@pasteur.Berkeley.EDU> deboor@buddy.Berkeley.EDU.UUCP (Adam R de Boor) writes:
-Shell scripts 201 (Graduate level :)
-While the lecturer in SS101 was wrong in his solution of the problem (or
-perhaps misunderstood the problem itself), his contention that xargs can
-be solved with a rudimentary shell script is correct, q.e.d. (or some
-similar abbreviation, hee hee)

The first solution was actually better, because it didn't bump into
the exec args limit that is the main reason for xargs's existence.