From: Matthias Andree <matthias.andree@gmx.de>
To: "Theodore Ts'o" <tytso@mit.edu>, Timo Sirainen <tss@iki.fi>,
linux-kernel@vger.kernel.org
Subject: Re: readdir loses renamed files
Date: Thu, 28 Oct 2004 17:41:32 +0200 [thread overview]
Message-ID: <20041028154132.GA6202@merlin.emma.line.org> (raw)
In-Reply-To: <20041028114413.GL1343@schnapps.adilger.int>
On Thu, 28 Oct 2004, Andreas Dilger wrote:
> I read over in reiserfs-list that the reason for the crazy renaming is
> to store "attributes" as part of the filename. Why not just store them
> as EAs as they were intended? With the large inode patches (posted here
> a couple of times already) the cost of storing EAs is negligible.
The "attributes" stored are really mail flags such as "read", "replied
to", the size and so on. Not sure if it makes sense storing these as
extended attributes, or, the other way around, are EAs supposed to be
some "associated" generic file that can be attached to an existing file?
At any rate, the resulting software would no longer be able to call
its backing storage to be in "Maildir" format.
I know AmigaOS had a limited amount of space (some dozen characters) for
a generic file comment, but otherwise.
--
Matthias Andree
next prev parent reply other threads:[~2004-10-28 15:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 1:21 Timo Sirainen
2004-10-25 8:29 ` Chris Wedgwood
2004-10-25 12:35 ` Timo Sirainen
2004-10-25 12:47 ` Jan Engelhardt
2004-10-25 12:37 ` Theodore Ts'o
2004-10-25 13:22 ` Timo Sirainen
2004-10-28 9:34 ` Matthias Andree
2004-10-28 11:44 ` Andreas Dilger
2004-10-28 14:34 ` Jan Engelhardt
2004-10-28 15:41 ` Matthias Andree [this message]
2004-10-29 21:15 ` Hans Reiser
2004-10-29 21:28 ` Jan Engelhardt
2004-10-30 19:11 ` Hans Reiser
2004-10-31 6:32 ` Jan Engelhardt
2004-11-01 5:38 ` Hans Reiser
2004-10-28 17:06 ` Theodore Ts'o
2004-10-28 19:00 ` Bernd Eckenfels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041028154132.GA6202@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tss@iki.fi \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®