Date: Sat, 21 Apr 2001 13:18:57 +0200 From: Jens Schweikhardt <schweikh@schweikhardt.net> To: Mike Smith <msmith@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: cp -d dir patch for review (or 'xargs'?) Message-ID: <20010421131857.B4574@schweikhardt.net> In-Reply-To: <200104202214.f3KMEAf06331@mass.dis.org>; from msmith@freebsd.org on Fri, Apr 20, 2001 at 03:14:10PM -0700 References: <20010420235419.B1276@schweikhardt.net> <200104202214.f3KMEAf06331@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 20, 2001 at 03:14:10PM -0700, Mike Smith wrote: # > # > Folks, # > # > although there was much rejoicing, I think there's no need for a # > new option to cp. Just use the toolbox, it's not too hard: # > # > (cat bigfilelist; echo destdir) | xargs cp # > # > Or even # > # > echo destdir >>bigfilelist # > xargs cp < bigfilelist # > # > should do the trick. # # No, it won't. Consider a list of files a, b, c, d. You create input to # xargs 'a b c d destdir', which it then splits into 'a b c' and 'd # destdir'. The first time cp is run, it will probably fail; the second # time only 'd' ends up where you expect it. You mean if bigfilelist list exceeds the -n limit of xargs (default 5000)? Yes, you'll be surprised then. It was a bit of POLA violation for me when I found xargs would by default use 5000 arg chunks and not all in one go. I'd rather get rid of kern.argmax and the limitations of the exec familiy. Yes, I'm dreaming :-) Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) 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?20010421131857.B4574>