From owner-freebsd-stable@FreeBSD.ORG Thu Dec 2 21:22:05 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C1EA16A4CE for ; Thu, 2 Dec 2004 21:22:05 +0000 (GMT) Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06C2E43D48 for ; Thu, 2 Dec 2004 21:22:05 +0000 (GMT) (envelope-from kirk@strauser.com) Received: from localhost (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 525D0B863 for ; Thu, 2 Dec 2004 15:22:04 -0600 (CST) Received: from kanga.honeypot.net ([127.0.0.1]) by localhost (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30005-05 for ; Thu, 2 Dec 2004 15:22:03 -0600 (CST) Received: from janus.daycos.com (janus.daycos.com [204.26.70.77]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTP id B97ECB805 for ; Thu, 2 Dec 2004 15:22:03 -0600 (CST) From: Kirk Strauser To: freebsd-stable@freebsd.org Date: Thu, 2 Dec 2004 15:21:59 -0600 User-Agent: KMail/1.7.1 References: <47772.1101988548@thrush.ravenbrook.com> In-Reply-To: <47772.1101988548@thrush.ravenbrook.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart9050364.4o0ZWqOHmq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200412021522.02664.kirk@strauser.com> X-Virus-Scanned: by amavisd-new at honeypot.net Subject: Re: 4.x can't read 5.x dump? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2004 21:22:05 -0000 --nextPart9050364.4o0ZWqOHmq Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 02 December 2004 05:55, Nick Barnes wrote: > There's no theoretical reason why the formats used by dump and restore > shouldn't be forward and backward compatible, allowing an older > restore (to an older filesystem type) to pick out the parts of the > dump which make sense to it while ignoring parts which it doesn't > understand. There may be security reasons, though. If you've locked down a filesystem= =20 through the extensive use of ACLs, then you wouldn't want to dump/restore=20 it to another system that doesn't support those ACLs and expect your=20 security framework to still be intact - at least not without *lots* of=20 warnings. =2D-=20 Kirk Strauser --nextPart9050364.4o0ZWqOHmq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iD8DBQBBr4d65sRg+Y0CpvERAgREAJ9g1ErAWqgPo8rWUlg1Cmb3RbrygQCfQ3bF XQwlzuw1kZ2xPDB/oS4w4bw= =dLiX -----END PGP SIGNATURE----- --nextPart9050364.4o0ZWqOHmq--