[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0706181406250.25913@blackbox.fnordora.org>
Date: Mon, 18 Jun 2007 14:08:03 -0700 (PDT)
From: alan <alan@...eserver.org>
To: Bodo Eggert <7eggert@....de>
cc: Theodore Tso <tytso@....edu>,
Jörn Engel <joern@...fs.org>,
"H. Peter Anvin" <hpa@...or.com>,
Jack Stone <jack@...keye.stone.uk.eu.org>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
akpm@...ux-foundation.org, viro@...iv.linux.org.uk
Subject: Re: Versioning file system
On Mon, 18 Jun 2007, Bodo Eggert wrote:
> alan <alan@...eserver.org> wrote:
>
>> I just wish that people would learn from the mistakes of others. The
>> MacOS is a prime example of why you do not want to use a forked
>> filesystem, yet some people still seem to think it is a good idea.
>> (Forked filesystems tend to be fragile and do not play well with
>> non-forked filesystems.)
>
> What's the conceptual difference between forks and extended user attributes?
Forks tend to contain more than just extended attributes. They contain
all sorts of other meta-data including icons, descriptions, author
information, copyright data, and whatever else can be shoveled into them
by the author/user.
--
"ANSI C says access to the padding fields of a struct is undefined.
ANSI C also says that struct assignment is a memcpy. Therefore struct
assignment in ANSI C is a violation of ANSI C..."
- Alan Cox
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists