From owner-freebsd-questions Wed May 9 3:51:35 2001 Delivered-To: freebsd-questions@freebsd.org Received: from cache1.hck.carroll.com (cache1.hck.carroll.com [216.44.20.19]) by hub.freebsd.org (Postfix) with ESMTP id A9A9437B42C for ; Wed, 9 May 2001 03:51:29 -0700 (PDT) (envelope-from damien@carroll.com) Received: from sprig.tougas.net ([216.44.20.42] verified) by cache1.hck.carroll.com (CommuniGate Pro SMTP 3.2.4) with ESMTP id 2848145; Wed, 09 May 2001 06:51:28 -0400 Date: Wed, 09 May 2001 06:51:27 -0400 From: Damien Tougas To: Otter Cc: Micke Josefsson , FreeBSD-questions Subject: RE: dump vs tar? Message-ID: <707940000.989405487@sprig.tougas.net> In-Reply-To: X-Mailer: Mulberry/2.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --On Wednesday, May 09, 2001 12:38:48 +0200 Micke Josefsson wrote: > As pointed out in another response dump works on entire filesystems. The > advantage is that a dump can be restored unto a completely new disk. I use > dump (and restore) for cloning entire machines. A dumped /-partition is > bootable when restored on another disk. If that is not your goal (it > isn't, right?) you should stick to tar. It is also worth noting that tar has a path limitation of 250 characters. This can be a bit of a pain if you have very deeply nested directores. There are ways around this, but it can sometimes be a bit of a pain. --- Damien Tougas Systems Administrator Carroll-Net, Inc. http://www.carroll.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message