From owner-freebsd-questions@FreeBSD.ORG Sun Jul 27 21:22:42 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C5D57C6 for ; Sun, 27 Jul 2014 21:22:42 +0000 (UTC) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3D3529CF for ; Sun, 27 Jul 2014 21:22:41 +0000 (UTC) Received: from r56.edvax.de (port-92-195-69-249.dynamic.qsc.de [92.195.69.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id 15DCF3CBDD; Sun, 27 Jul 2014 23:22:37 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id s6RLMbeH003396; Sun, 27 Jul 2014 23:22:37 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 27 Jul 2014 23:22:37 +0200 From: Polytropon To: "Ronald F. Guilmette" Subject: Re: cpio and hard links Message-Id: <20140727232237.71735292.freebsd@edvax.de> In-Reply-To: <13472.1406495024@server1.tristatelogic.com> References: <13472.1406495024@server1.tristatelogic.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2014 21:22:42 -0000 On Sun, 27 Jul 2014 14:03:44 -0700, Ronald F. Guilmette wrote: > For the the cpio program that is part of FreeBSD, is there any option > which would have the effect of causing cpio to only archive a single > instance of the data associated with each unique inode... as tar apparently > does, by default? >From reading "man cpio", I don't see that option mentioned. The only related option is -L, but it is to be used for symbolic links (and turns them into regular files). If you need this functionality, you'll probably be better off with tar, or you put tar archives into a cpio pipeline... Keep in mind not all archiving, compressing and transmission tools share the same amount of dedication toward the file system features (links, modes, user:group, permissions, attributes and so on). In case of cpio, I just think the requested feature simply is not part of what cpio can do (unlike tar, as you've correctly mentioned). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...