3.6 will always be supported for bug fixes, but will not receive new
features if I can help it. It is stable supported code, and should be
kept that way.
Regarding the journaling implementation, let's see what Chris says
before I comment.
Hans
michael chang wrote:
On 8/31/05, Hifumi Hisashi
Thanks much Hifumi!
Chris, please comment on the patch.
Hans
Hifumi Hisashi wrote:
Hello.
I noticed that the Reiserfs has some problems related to meta-data
journaling.
I suppose that transactions regarding meta-data should be written to
a disk every
meta-data change (for example,
vs will respond at the end of the week, he is out at the moment.
Thanks for patch Charles,
Hans
-
To unsubscribe from this list: send the line unsubscribe linux-fsdevel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Daniel Phillips wrote:
Graciously accepted. Coming up with something sensible in a mere 6
months would be a minor miracle. ;-)
- what happens if the user forgets to close the transaction?
then the user has branched into his own version, or at least that would be my
take on it. Another
Chris Mason wrote:
--On 10/27/00 14:33:33 -0700 Hans Reiser [EMAIL PROTECTED] wrote:
The atomic restriction can be enforced in a component separate. I mean,
ACLs have all sorts of restrictions on them, and atomicity is one of a
great many of them, so you have to have a separate
Anton Altaparmakov wrote:
Hans,
At 18:30 28/10/2000, Hans Reiser wrote:
Anton Altaparmakov wrote:
You can't possibly have both using the same API since you would then get
name collision on filesystems where both named streams and EAs are
supported. (And I haven't even mentioned
Curtis Anderson wrote:
The problem with streams-style attributes comes from stepping onto the
slippery slope of trying to put too much generality into it. I chose the
block-access style of API so that there would be no temptation to start
down that slope.
I understand you right up until
"Stephen C. Tweedie" wrote:
Hi,
On Tue, Oct 24, 2000 at 09:20:05AM +0200, Ragnar Kj?rstad wrote:
I don't know how much need there is for inheritence here, but if a lot
of attributes will need it I think it should be supported in the
interface instead. (though hardlinks really make
"Stephen C. Tweedie" wrote:
Hi,
On Wed, Oct 25, 2000 at 09:09:57AM -0700, Hans Reiser wrote:
Why do you force the user to copy the data into the attrib structure, rather than
letting him leave
the data where it lies and simply specify the location to the kernel?
In the f
