From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville Herva Subject: filesystem transactions API Date: Tue, 26 Apr 2005 16:46:29 +0300 Message-ID: <20050426134629.GU16169@viasys.com> References: <20050424211942.GN13052@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from herkules.vianova.fi ([194.100.28.129]:26830 "HELO mail.vianova.fi") by vger.kernel.org with SMTP id S261519AbVDZNqj (ORCPT ); Tue, 26 Apr 2005 09:46:39 -0400 To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Apparently, Windows Longhorn will include something called "transactional NTFS". It's explained pretty well in http://blogs.msdn.com/because_we_can/ Basically, a process can create a fs transaction, and all fs changes made between start of the transaction and commit are atomical - meaning nothing is visible until commit, and if commit fails, everything is rolled back. Sound useful... Although there are no service pack installs that could fail in Linux, the same thing could be useful in rpm, yum, almost anything. What do you think? -- v -- v@iki.fi