Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site mit-eddie.UUCP Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!mit-eddie!barmar From: barmar@mit-eddie.UUCP (Barry Margolin) Newsgroups: net.unix Subject: Re: tar .vs. cpio - (nf) Message-ID: <2541@mit-eddie.UUCP> Date: Sun, 12-Aug-84 19:46:41 EDT Article-I.D.: mit-eddi.2541 Posted: Sun Aug 12 19:46:41 1984 Date-Received: Mon, 13-Aug-84 03:33:35 EDT References: <226@haddock.UUCP> Reply-To: barmar@mit-eddie.UUCP (Barry Margolin) Organization: MIT, Cambridge, MA Lines: 24 In article <226@haddock.UUCP> johnl@haddock.UUCP writes: > - reading file names from stdin is a feature, not a bug. You can use > find to enumerate just the files you want rather than having to dump > everything in a directory tree, e.g. > > $ find somedir -mtime -14 -print | cpio -oB >/dev/rmt0 > > (dump only files modified within the last two weeks.) Doing this > with tar is pretty hard. It isn't really very hard: tar`find ...` Accepting file names on the command line is the Unix convention. Note that I have no real opinion on the debate. I have only used tar so far. In response to someone's mention of "tp", the predecessor to "tar": it is still available in 4.2BSD. -- Barry Margolin ARPA: barmar@MIT-Multics UUCP: ..!genrad!mit-eddie!barmar