From owner-freebsd-stable Tue Jun 23 19:21:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01821 for freebsd-stable-outgoing; Tue, 23 Jun 1998 19:21:19 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from osprey.grizzly.com (med.sc.scruznet.com [165.227.115.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01814 for ; Tue, 23 Jun 1998 19:21:14 -0700 (PDT) (envelope-from markd@Grizzly.COM) Received: (from markd@localhost) by osprey.grizzly.com (8.8.8/8.8.5) id TAA23225; Tue, 23 Jun 1998 19:22:32 -0700 (PDT) Date: Tue, 23 Jun 1998 19:22:32 -0700 (PDT) Message-Id: <199806240222.TAA23225@osprey.grizzly.com> From: Mark Diekhans To: tom@uniserve.com CC: blapp@attic.ch, freebsd-stable@FreeBSD.ORG, hoek@hwcn.org In-reply-to: (message from Tom on Tue, 23 Jun 1998 17:26:01 -0700 (PDT)) Subject: Re: GNU-Tar should be updated References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: Tom > pax is also a nice tar replacement. On BSDI, tar is just a link to pax. >I'm pretty sure pax can backup up /dev I worked on some distribution software about 5 years ago that look at incorporating the pax code to read tar files. We ended up finding some serious bugs and dropped the idea. I don't remember the nature of the bugs, but they were reproduced on every system that had a vendor copy of pax that I could find. Attempts to contact the author failed. Unless someone has done some major work on pax, I would recommend staying away from it. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message