From owner-freebsd-questions@FreeBSD.ORG Thu May 11 17:54:40 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D13E916A4F3 for ; Thu, 11 May 2006 17:54:40 +0000 (UTC) (envelope-from kdk@daleco.biz) Received: from ezekiel.daleco.biz (southernuniform.com [66.76.92.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0E4F43D78 for ; Thu, 11 May 2006 17:54:39 +0000 (GMT) (envelope-from kdk@daleco.biz) Received: from [192.168.2.2] ([69.27.149.254]) by ezekiel.daleco.biz (8.13.4/8.13.1) with ESMTP id k4BHsFJx054640; Thu, 11 May 2006 12:54:17 -0500 (CDT) (envelope-from kdk@daleco.biz) Message-ID: <44637A42.8030209@daleco.biz> Date: Thu, 11 May 2006 12:54:10 -0500 From: Kevin Kinsey User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.0.2) Gecko/20060509 SeaMonkey/1.0.1 MIME-Version: 1.0 To: Olivier Nicole References: <005a01c67498$a54a2a70$0300020a@mickey> <200605110227.k4B2RItS085960@banyan.cs.ait.ac.th> In-Reply-To: <200605110227.k4B2RItS085960@banyan.cs.ait.ac.th> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: don@lizardhill.com, freebsd-questions@freebsd.org Subject: Re: Copying a file system w/ tar - symbolic links not copied right. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 May 2006 17:54:42 -0000 Olivier Nicole wrote: >> I'm trying to move a file system from one disk to another, and when I do >> this: > > I think that the way to go is: > > tar cf - /source/* | ( cd /destination && tar xfvBp - ) > > Note the Bp at the end of the extract tar. > > olivier Is that for BSD tar, or gtar (GNU)? We still haven't decided which is offering the problem, and I don't find "-B" described in bsdtar(1), although I can see why you'd want it in gtar, perhaps. Nonetheless, the tests I made with both tars didn't seem to have this problem. Can Don confirm whether this only occurs if /source/ is a filesystem mount point? (Also, which tar are you using? KDK -- Computer programs expand so as to fill the core available.