From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?B?SsO2cm4=?= Engel Subject: Re: Versioning file system Date: Sat, 16 Jun 2007 16:53:37 +0200 Message-ID: <20070616145337.GA13391@lazybastard.org> References: <46731169.2090002@hawkeye.stone.uk.eu.org> <467314E2.9010306@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "H. Peter Anvin" , Jack Stone , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org, viro@zeniv.linux.org.uk To: alan Return-path: Received: from [212.112.238.170] ([212.112.238.170]:56957 "EHLO longford.lazybastard.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1753264AbXFPQN4 (ORCPT ); Sat, 16 Jun 2007 12:13:56 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, 15 June 2007 15:51:07 -0700, alan wrote: >=20 > >Thus, in the end it turns out that this stuff is better handled by > >explicit version-control systems (which require explicit operations = to > >manage revisions) and atomic snapshots (for backup.) >=20 > ZFS is the cool new thing in that space. Too bad the license makes i= t=20 > hard to incorporate it into the kernel. It may be the coolest, but there are others as well. Btrfs looks good, nilfs finally has a cleaner and may be worth a try, logfs will get snapshots sooner or later. Heck, even my crusty old cowlinks can be viewed as snapshots. If one has spare cycles to waste, working on one of those makes more sense than implementing file versioning. J=C3=B6rn --=20 "Security vulnerabilities are here to stay." -- Scott Culp, Manager of the Microsoft Security Response Center, 2001 - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel= " in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html