From owner-freebsd-questions Thu Dec 26 10:59:31 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA03416 for questions-outgoing; Thu, 26 Dec 1996 10:59:31 -0800 (PST) Received: from seabass.progroup.com (catfish.progroup.com [206.24.122.2]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA03410 for ; Thu, 26 Dec 1996 10:59:28 -0800 (PST) Received: (from craig@localhost) by seabass.progroup.com (8.7.5/8.6.12) id LAA13305 for questions@FreeBSD.ORG; Thu, 26 Dec 1996 11:00:27 -0800 (PST) Message-Id: <199612261900.LAA13305@seabass.progroup.com> Subject: Re: cpio truncating inode numbers? To: questions@FreeBSD.ORG Date: Thu, 26 Dec 1996 11:00:27 -0800 (PST) From: "Craig Shaver" In-Reply-To: from "Christian Weisgerber" at Dec 26, 96 01:54:15 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Greg Lehey writes: > > > > cpio: xxxxx filename being backed up : truncating inode number > > > > It's not a disaster, it's a historical quirk. The cpio format has > > only 2 bytes for the inode number (the inode is the real file del ... > > > You're probably better off using tar. > > What's the maximum path length GNU tar can handle? 100 characters? 250? > POSIX says 256 bytes. -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088