Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Subject: Re: any chance of... Message-ID: <1993Mar31.031615.5064@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: CS References: <1p84lbINN1j1@iskut.ucs.ubc.ca> <JKH.93Mar30023319@whisker.lotus.ie> <1993Mar30.041706.28158@coe.montana.edu> <1pauv5INN771@iskut.ucs.ubc.ca> Date: Wed, 31 Mar 1993 03:16:15 GMT Lines: 28 In article <1pauv5INN771@iskut.ucs.ubc.ca> felawka@sitka.triumf.ca (Larry Felawka) writes: > >Gee Nate, the only argument you give is one AGAINST using TAR. What's >wrong with cpio? (let the cpio flame war commence ...) > Reason for tar: I never used cpio until this distribution. Tar is a very well known format in the *nix world. How many sites do you see with progname.cpio.Z archives. Not many. However, there are tons of progname.tar.Z files laying around. Most *nix people know how to use tar. Reason against cpio: Byte header problems. At least on a couple platforms I know of, you can't un-cpio the distribution files on the machine, to check things out before putting them onto floppies for installation purposes. Me, the main reason I like tar is because I know tar. I don't know cpio. Nate -- osynw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, work #: (406) 994-4836 | I don't think they'll catch on - home #: (406) 586-0579 | Don Hammerstrom