Date: Fri, 18 Feb 2005 10:35:03 +0100 From: Bernd Walter <ticso@cicely12.cicely.de> To: Stijn Hoop <stijn@win.tue.nl> Cc: Steve Kargl <sgk@troutmask.apl.washington.edu> Subject: Re: Change tar to GNU Message-ID: <20050218093502.GS753@cicely12.cicely.de> In-Reply-To: <20050218092709.GM8471@pcwin002.win.tue.nl> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050218093502.GS753>