From: Bernd Eckenfels <ecki@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: filesystem transactions API
Organization: Private Site running Debian GNU/Linux
In-Reply-To: <20050427151758.GE1957@mail.shareable.org>
User-Agent: tin/1.7.8-20050315 ("Scalpay") (UNIX) (Linux/2.6.8.1 (i686))
Message-Id: <E1DQprb-00024N-00@calista.eckenfels.6bone.ka-ip.net>
Date: Wed, 27 Apr 2005 18:58:15 +0200
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1184
Lines: 30

In article <20050427151758.GE1957@mail.shareable.org> you wrote:
> If we have transactions, then I'd like to be able to do this from a shell:
...
> I'd also like to write inside a single C program:

perhaps you will need to use plan9 or hurd? :)

Because this pretty much virtualisation/snapshots. Anyway, it would be a
nice thing to have, for sure (I am not sure if all the technical
implications like deadlocks and serialisations can be solved in a unix
compatible manner (and especially for at least more than one local and
networked file system).

> It's useful, and there is no good reason to disallow that.

There might be no good reasons, but a lot of hard problems.

> Nonetheless, there's a need for some kind of transaction handles.  A
> file descriptor representing a transaction seems like a natural fit.

Yes, that might be a good thing, beacause it can be passed, inherited and
access controled and possesed.

Greetings
Bernd
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/