From owner-freebsd-questions Thu Mar 18 7:41:15 1999 Delivered-To: freebsd-questions@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id 78EF21544E for ; Thu, 18 Mar 1999 07:38:38 -0800 (PST) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.2/8.9.2) id JAA43695 for freebsd-questions@freebsd.org; Thu, 18 Mar 1999 09:42:46 -0600 (CST) (envelope-from obonilla) Date: Thu, 18 Mar 1999 09:42:45 -0600 From: Oscar Bonilla To: freebsd-questions@freebsd.org Subject: tar damaged (not related to FreeBSD :) Message-ID: <19990318094245.A43680@fisicc-ufm.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG does anyone know of any tricks to repair a file damaged by an ASCII ftp transfer? here's what happened... a new sysadmin here made some backups of some important dirs in a Solaris box (using tar and gzip) tranfered them to another server (FreeBSD) but forgot to set the tranfer mode to BINARY (Solaris ftp needs to be explicitly told to use binary mode, otherwise defaults to ASCII). Then he zaped solaris from the sunbox and installed a new version. now if we try to decompress the files using gunzip in the FreeBSD box gunzip dumps core. idem if we do it in the solaris box. is there any way to reconstruct the files? thanks, -oscar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message