Date: Fri, 20 Apr 2001 21:00:56 -0700 (PDT) From: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net> To: bsd@bsdhome.com (Brian Dean) Cc: schweikh@schweikhardt.net (Jens Schweikhardt), freebsd-current@FreeBSD.ORG Subject: Re: cp -d dir patch for review (or 'xargs'?) Message-ID: <200104210400.VAA69212@gndrsh.dnsmgr.net> In-Reply-To: <20010420223943.A59039@vger.bsdhome.com> from Brian Dean at "Apr 20, 2001 10:39:43 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104210400.VAA69212>