> > On Fri, Apr 20, 2001 at 07:26:18PM -0700, Rodney W. Grimes wrote:
> >
> > > > (cat bigfilelist; echo destdir) | xargs cp
> > >
> > > I like this version of the patch!! It's much much cleaner than
> > > hacking up cp or xargs, it even follows the unix principle of
> > > using simple tools and glueing them togeather to do bigger
> > > jobs, is unix implementation independent, and is very clear
> > > in what it does.
> >
> > It's clean, simple, and unfortunately, totally bogus.
> >
> > Try:
> >
> > echo 1 2 3 4 5 6 7 8 9 | xargs -n 4 echo
> >
> > Now consider what would happen with the above suggested construct with
> > a very long file list.
>
> bleck... try this for your sample:
> $ (echo 1 2 3 4 5 6 7 8 9 | xargs -n 4) | while read x; do
> > echo -n $x; echo " dst"
> > done
> 1 2 3 4 dst
> 5 6 7 8 dst
> 9 dst
> $
>
> >
> > I don't see a problem with adding an option to cp to treat the first
> > argument as the target instead of the last argument. It's a simple
> > solution, the code change is simple, and it produces the exact desired
> > result. What's the problem?
>
> It's yet another non-portable option.
I hate to appear rude, but has anybody in this discussion actually used
xargs for what it's meant to be used ?
How do you do this in a script:
cd /topdir; find . -type f | xargs -i {} cp {} /otherdir/.
Before anyone starts writing scripts, consider that {} will be
replaced by xargs with (roughly) ARG_MAX - 10 characters worth of the
stuff coming off the pipe. If your combined arguments plus
environment exceeds ARG_MAX execve(2) will give you E2BIG.
> --
> Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
--
Brian <[EMAIL PROTECTED]> <brian@[uk.]FreeBSD.org>
<http://www.Awfulhak.org> <brian@[uk.]OpenBSD.org>
Don't _EVER_ lose your sense of humour !
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
