Xref: utzoo comp.arch:8125 comp.unix.questions:11526
Path: utzoo!attcan!uunet!mcvax!dik
From: dik@cwi.nl (Dik T. Winter)
Newsgroups: comp.arch,comp.unix.questions
Subject: Re: Endian wars - really 386 questi
Message-ID: <7877@boring.cwi.nl>
Date: 5 Feb 89 02:48:35 GMT
References: <30@microsoft.UUCP> <28200266@mcdurb> <24318@amdcad.AMD.COM>
Followup-To: comp.unix.questions
Organization: CWI, Amsterdam
Lines: 24

In article <24318@amdcad.AMD.COM> rpw3@amdcad.UUCP (Rob Warnock) writes:
 > +---------------
 > | (Quick: who's run into Unix's 10K command-line limit?)
 > +---------------
 > 
 > Yes, all of us, until we [most of us?] started using the standard utility
 > program "xargs" (used to be System-V only, until a p-d source for a useful
 > subset for 4.x BSD was posted several years ago). With "xargs", that 10k limit
 > becomes a non-issue. Instead of, for example:
 > 
 > 	$ some_cmd -options `find <selection> -print`
 > try:
 > 	$ find <selection> -print | xargs some_cmd -options
 > 
But of course the two are equivalent only if "some_cmd -options" uses only
one input file at a time.  Try:
	cc -o aap `find <selection> -print`
And if they are equivalent you could already do:
	find <selection> -exec some_cmd -options {} \;
(although you have a lot more processes).
-- 
dik t. winter, cwi, amsterdam, nederland
INTERNET   : dik@cwi.nl
BITNET/EARN: dik@mcvax