From: "Stephen C. Tweedie" <sct@redhat.com>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
"Stephen C. Tweedie" <sct@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] [RFC] [PATCH 3/4] Add extended attributes to ext2/3
Date: Wed, 9 Oct 2002 16:25:13 +0100 [thread overview]
Message-ID: <20021009162513.F2779@redhat.com> (raw)
In-Reply-To: <200210091329.28153.agruen@suse.de>; from agruen@suse.de on Wed, Oct 09, 2002 at 01:29:28PM +0200
Hi,
On Wed, Oct 09, 2002 at 01:29:28PM +0200, Andreas Gruenbacher wrote:
> On Wednesday 09 October 2002 00:17, Theodore Ts'o wrote:
> > Well, how about this as a compromise? We define a new superblock
> > field which reserves a certain amount of space in the EA block for
> > "system" attributes.
> > Andreas, does that sound good to you?
>
> I'd rather not store such policy things on the file system permanently, and
> make it a mount option. I'm wondering how many installations this would
> affect; to me it seems that it's not worth a super block flag.
We already have a lot of similar places where we do this in ext2/3.
The standard procedure is to store the default in the superblock but
to allow the user to override at mount time.
--Stephen
next prev parent reply other threads:[~2002-10-09 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-08 18:08 [RFC] [PATCH 3/4] Add extended attributes to ext2/3 tytso
2002-10-08 18:53 ` [Ext2-devel] " Christoph Hellwig
2002-10-08 19:14 ` Andreas Gruenbacher
2002-10-08 19:20 ` Christoph Hellwig
2002-10-08 20:41 ` Stephen C. Tweedie
2002-10-08 20:47 ` Christoph Hellwig
2002-10-08 21:19 ` Andreas Dilger
2002-10-08 22:17 ` Theodore Ts'o
2002-10-09 11:29 ` Andreas Gruenbacher
2002-10-09 15:25 ` Stephen C. Tweedie [this message]
2002-10-08 22:21 ` Theodore Ts'o
[not found] ` <20021009064242.GW3045@clusterfs.com>
2002-10-09 13:09 ` Christoph Hellwig
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=20021009162513.F2779@redhat.com \
--to=sct@redhat.com \
--cc=agruen@suse.de \
--cc=ext2-devel@lists.sourceforge.net \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.