From owner-freebsd-stable Sat May 18 14:47:45 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.noos.fr (racine.noos.net [212.198.2.71]) by hub.freebsd.org (Postfix) with ESMTP id 7A2BA37B40C for ; Sat, 18 May 2002 14:47:39 -0700 (PDT) Received: (qmail 27605605 invoked by uid 0); 18 May 2002 21:47:37 -0000 Received: from unknown (HELO gits.gits.dyndns.org) ([212.198.230.194]) (envelope-sender ) by 212.198.2.71 (qmail-ldap-1.03) with SMTP for ; 18 May 2002 21:47:37 -0000 Received: from gits.gits.dyndns.org (on0jz53tzdd4xkpw@localhost [127.0.0.1]) by gits.gits.dyndns.org (8.12.3/8.12.3) with ESMTP id g4ILlai2002081; Sat, 18 May 2002 23:47:36 +0200 (CEST) (envelope-from root@gits.dyndns.org) Received: (from root@localhost) by gits.gits.dyndns.org (8.12.3/8.12.3/Submit) id g4ILlYrC002080; Sat, 18 May 2002 23:47:34 +0200 (CEST) (envelope-from root) Message-Id: <200205182147.g4ILlYrC002080@gits.gits.dyndns.org> Subject: Re: Tar broken for large files? In-Reply-To: <20020517232616.GC60644@no-support.loc> To: Bjoern Fischer Date: Sat, 18 May 2002 23:47:34 +0200 (CEST) From: Cyrille Lefevre Cc: Lou Katz , freebsd-stable@FreeBSD.ORG Reply-To: cyrille.lefevre@laposte.net X-Face: V|+c;4!|B?E%BE^{E6);aI.[< List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On May 18, 2002 01:26:16 am +0200, Bjoern Fischer wrote: > On Fri, May 17, 2002 at 05:56:21AM +0200, Cyrille Lefevre wrote: > > also, how about using pax ? > > > > FYI, for writting, use pax -w -x ustar -f /dev/sa0 > > and for reading, use pax -r -pp -f /dev/sa0 > > IMHO pax(1) is one of the most underestimated archivers in the > UNIX environment. well, some advantages/disavantage of tar/cpio/pax : pax : handle sparse files natively may read broken archives (I did it recently using -E where cpio fail :) pax as tar : handle sparse files natively don't know about broken archives ? pax as cpio : handle sparse files natively unable to read broken archives :( gnu tar : need --spare to handle sparse files well may read broken archives using --ignore-failed-read (-i on older tar :) gnu cpio : need --spare to handle sparse files well unable to read broken archives :( > What about propagating pax(1) and wrap the tar(1) command line > interface into pax for compatibility. Then get rid of the old > hacked up GNU tar version in the base system. If one needs the > features of a decent GNU tar, the port is the proper way in > any event. tar and cpio are already wrapper into pax depending how it is called (pax, cpio and/or tar). so, there is noting to do except to install the required links. see PR #38256 for details : http://www.FreeBSD.org/cgi/query-pr.cgi?pr=bin/38256 > All in all there are these 3 options to choose from: > > 1.) Fix the tar(1) in the base system. > 2.) Import a new fresh GNU tar version into the base system. > 3.) Push pax(1) and wrap the tar(1) CLI into it. in order, I prefer 3, 2, 1 :) Cyrille. -- Cyrille Lefevre mailto:cyrille.lefevre@laposte.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message