From owner-freebsd-hackers Thu Jul 26 12: 4:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp-2.enteract.com (smtp-2.enteract.com [207.229.143.4]) by hub.freebsd.org (Postfix) with ESMTP id 25AD937B403 for ; Thu, 26 Jul 2001 12:04:31 -0700 (PDT) (envelope-from dscheidt@tumbolia.com) Received: from shell-1.enteract.com (shell-1.enteract.com [207.229.143.40]) by smtp-2.enteract.com (Postfix) with ESMTP id 5C5CE6BF9; Thu, 26 Jul 2001 14:04:17 -0500 (CDT) Date: Thu, 26 Jul 2001 14:04:17 -0500 (CDT) From: David Scheidt X-X-Sender: To: James Howard Cc: =?iso-8859-1?Q?Lars_K=FChl?= , Subject: Re: Backup file formats: tar, cpio, pax, yadda, yadda, yadda In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 26 Jul 2001, James Howard wrote: :On Thu, 26 Jul 2001, [iso-8859-1] Lars K=FChl wrote: : :> Neither tar nor cpio is suitable for backup purposes. :> Use dump instead. : :A lot of people said this. Why? As near as I can tell, dump isn't that :great either. There is no way to exlude specific directories with dump From=20the dump(8) manpage: Dump honors the user ``nodump'' flag (UF_NODUMP) on regular files and directories. If a directory is marked ``nodump'', the latter and all files and directories under it will not be backed up. That is, dump propagates the ``nodump'' flag on directories. :and it appears to be quite painful to restore a specific directory (though :I could be wrong about this. Interactive restore isn't that painful, and -x is useful as well. --=20 dscheidt@tumbolia.com Bipedalism is only a fad. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message