Date: Fri, 18 Feb 2005 11:39:54 +0200 From: Maxim Sobolev <sobomax@portaone.com> To: ticso@cicely.de Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Subject: Re: Change tar to GNU Message-ID: <4215B7EA.5000004@portaone.com> In-Reply-To: <20050218093502.GS753@cicely12.cicely.de> References: <Pine.NEB.3.96L.1050217192913.38170c-100000@fledge.watson.org> <4214F3C2.4020102@alumni.rice.edu> <20050217195547.GA33893@troutmask.apl.washington.edu> <86is4qfenb.fsf@xps.des.no> <20050218092709.GM8471@pcwin002.win.tue.nl> <20050218093502.GS753@cicely12.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernd Walter wrote: > On Fri, Feb 18, 2005 at 10:27:09AM +0100, Stijn Hoop wrote: > >>On Fri, Feb 18, 2005 at 09:36:40AM +0100, Dag-Erling Smørgrav wrote: >> >>>Steve Kargl <sgk@troutmask.apl.washington.edu> writes: >>> >>>>find $PATH -newermt 20050214 | xargs tar cf new.tar >>> >>>Bad idea, for a number of different reasons (including file names >>>containing spaces or other special characters, and command line length >>>limits). The following is slightly better, but will still fail if you >>>have files with newlines in them: >>> >>>find $PATH -newermt 2005-02-14 | tar -c -f new.tar -T/dev/stdin >> >>Won't find -print0 | xargs -0 ... work in all cases? > > > xargs possibly starts tar several times and tar overwrites the archive > every time. > Even if you get tar to append to an existing archive it can't know > about hardlinked files spanning multiple calls. That's a valid point. I think kientzle is likely to be interested in adding that functionality. -Maxim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4215B7EA.5000004>