From: Kyle Moffett <mrmacman_g4@mac.com>
To: Brad Boyer <flar@allandria.com>
Cc: "Jörn Engel" <joern@logfs.org>, "Theodore Tso" <tytso@mit.edu>,
"H. Peter Anvin" <hpa@zytor.com>, alan <alan@clueserver.org>,
"Bodo Eggert" <7eggert@gmx.de>,
"Jack Stone" <jack@hawkeye.stone.uk.eu.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org, viro@zeniv.linux.org.uk
Subject: Re: Versioning file system
Date: Mon, 18 Jun 2007 23:15:51 -0400 [thread overview]
Message-ID: <B6DEBB6D-9929-46BF-A43C-AB5B20070AAA@mac.com> (raw)
In-Reply-To: <20070618212423.GB19713@cynthia.pants.nu>
On Jun 18, 2007, at 17:24:23, Brad Boyer wrote:
> On Tue, Jun 19, 2007 at 12:26:57AM +0200, Jörn Engel wrote:
>> Pointless here means that _I_ don't see the point. Maybe there
>> are valid uses for extended attributes. If there are, noone has
>> explained them to me yet.
>
> The users of extended attributes that I've dealt with are ACL
> support and SELinux. These both use extended attributes under the
> covers. It's just not immediately obvious if you aren't looking.
Yeah, extended attributes are typically used for exactly that:
"attributes" like labels, permissions, encoding, cached file-type,
DOS/Windows/Mac metadata, etc. Sometimes people suggest sticking
icons in there, but that's probably a bad idea. At most stick an
"icon label" attribute which refers to a file "/usr/share/icons/
by_attr/$ICON_LABEL.png". If you're trying to put more than 256
bytes of data in an extended attribute then you're probably doing
something wrong. They're very good for cached attributes (like file-
type) where you don't care if the data is lost by "tar", and they're
reasonable for security-related attributes where you don't want
attribute-unaware programs trying to save and restore them (like
SELinux labels).
Cheers,
Kyle Moffett
next prev parent reply other threads:[~2007-06-19 3:17 UTC|newest]
Thread overview: 107+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8wst3-3kh-31@gated-at.bofh.it>
[not found] ` <8wsCC-3wf-21@gated-at.bofh.it>
[not found] ` <8wsW4-3UY-3@gated-at.bofh.it>
[not found] ` <8wJal-3KA-1@gated-at.bofh.it>
[not found] ` <8xm22-4Ql-1@gated-at.bofh.it>
[not found] ` <8xq5G-32l-7@gated-at.bofh.it>
[not found] ` <8xs7w-69W-21@gated-at.bofh.it>
2007-06-18 20:54 ` Versioning file system Bodo Eggert
2007-06-18 21:08 ` alan
2007-06-18 21:31 ` H. Peter Anvin
2007-06-18 21:34 ` Jeremy Allison
2007-06-18 22:10 ` Theodore Tso
2007-06-18 22:26 ` Jörn Engel
2007-06-18 21:24 ` Brad Boyer
2007-06-19 3:15 ` Kyle Moffett [this message]
2007-06-18 22:34 ` Jeremy Allison
2007-06-18 22:56 ` alan
2007-06-19 7:01 ` Theodore Tso
2007-06-18 22:48 ` Jeremy Allison
2007-06-18 23:00 ` alan
2007-06-19 7:05 ` Theodore Tso
2007-06-19 16:52 ` Jeremy Allison
2007-06-19 16:56 ` H. Peter Anvin
2007-06-18 22:47 ` alan
[not found] <OFC119F96F.A721E445-ON882572FE.0055140A-882572FE.00571482@us.ibm.com>
2007-06-18 16:37 ` Jack Stone
2007-06-18 16:56 ` H. Peter Anvin
2007-06-18 17:56 ` Bryan Henderson
2007-06-19 3:10 ` Kyle Moffett
2007-06-19 7:49 ` Jack Stone
2007-06-19 7:58 ` Bron Gondwana
2007-06-20 2:43 ` Kyle Moffett
2007-06-19 9:09 ` Martin Langhoff
2007-06-19 16:52 ` Jakub Narebski
2007-06-15 22:23 Jack Stone
2007-06-15 22:38 ` H. Peter Anvin
2007-06-15 22:51 ` alan
2007-06-15 22:59 ` H. Peter Anvin
2007-06-15 23:06 ` alan
2007-06-16 8:11 ` Jack Stone
2007-06-16 9:46 ` Jeffrey V. Merkey
2007-06-16 10:12 ` Jeffrey V. Merkey
2007-06-16 13:15 ` Mark Williamson
2007-06-16 19:57 ` Jeffrey V. Merkey
2007-06-16 16:49 ` Jan Harkes
2007-06-16 20:03 ` Jeffrey V. Merkey
2007-06-16 19:38 ` Jack Stone
2007-06-16 20:08 ` Alan Cox
2007-06-16 21:25 ` Jeffrey V. Merkey
2007-06-16 20:39 ` Jan Harkes
2007-06-16 20:43 ` Jack Stone
2007-06-16 22:17 ` Alan Cox
2007-06-17 2:18 ` Jeffrey V. Merkey
2007-06-17 2:39 ` Jeffrey V. Merkey
2007-06-17 22:11 ` Dale Amon
2007-06-16 21:06 ` Dale Amon
2007-06-16 11:42 ` Graham Murray
2007-06-16 14:53 ` Jörn Engel
2007-06-18 9:45 ` Andreas Dilger
2007-06-18 9:54 ` Jack Stone
2007-06-18 10:13 ` Jörn Engel
2007-06-18 14:01 ` Theodore Tso
2007-06-18 16:16 ` alan
2007-06-18 17:29 ` Theodore Tso
2007-06-18 17:33 ` Jeremy Allison
2007-06-18 20:30 ` Theodore Tso
2007-06-18 20:50 ` J. Bruce Fields
2007-06-18 17:46 ` H. Peter Anvin
2007-07-04 17:32 ` Erik Mouw
2007-07-04 20:47 ` Theodore Tso
2007-07-05 17:55 ` Erik Mouw
2007-07-05 13:57 ` John Stoffel
2007-07-05 14:23 ` Chris Mason
2007-07-05 17:57 ` Erik Mouw
2007-06-18 15:32 ` Chris Mason
2007-06-18 23:18 ` Bron Gondwana
2007-09-29 17:44 ` Sorin Faibish
2007-06-15 22:52 ` Chris Snook
2007-06-16 8:25 ` Jack Stone
2007-06-19 18:03 ` Chris Snook
2007-06-19 19:06 ` Jack Stone
2007-06-19 20:03 ` Chris Snook
2007-06-19 20:08 ` Jack Stone
2007-06-19 20:15 ` Chris Snook
2007-06-19 20:27 ` Jack Stone
2007-06-19 20:34 ` John Stoffel
2007-06-19 20:38 ` Jack Stone
2007-06-19 20:38 ` Matthew Wilcox
2007-06-19 21:02 ` John Stoffel
2007-06-19 19:08 ` H. Peter Anvin
2007-06-19 19:12 ` Jack Stone
2007-06-19 19:15 ` H. Peter Anvin
2007-06-19 19:22 ` Jack Stone
2007-06-19 20:10 ` Chris Snook
2007-06-19 20:14 ` Jack Stone
2007-06-19 20:31 ` Chris Snook
2007-06-20 8:34 ` Bernd Petrovitsch
2007-06-19 21:50 ` Alan Cox
2007-06-19 22:07 ` H. Peter Anvin
2007-06-20 8:05 ` Ph. Marek
2007-06-19 20:43 ` Lennart Sorensen
2007-06-19 22:07 ` david
2007-06-19 22:13 ` H. Peter Anvin
2007-06-19 23:07 ` Jan Harkes
2007-06-19 23:12 ` H. Peter Anvin
2007-06-19 22:21 ` Lennart Sorensen
2007-06-19 23:35 ` Bryan Henderson
2007-06-20 0:27 ` Trond Myklebust
2007-06-20 5:00 ` H. Peter Anvin
2007-06-20 17:04 ` Bryan Henderson
2007-06-20 17:10 ` H. Peter Anvin
2007-06-20 17:33 ` Chris Snook
2007-06-15 22:57 ` Kok, Auke
2007-06-15 23:01 ` alan
2007-06-16 11:20 ` Johannes Weiner
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=B6DEBB6D-9929-46BF-A43C-AB5B20070AAA@mac.com \
--to=mrmacman_g4@mac.com \
--cc=7eggert@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=alan@clueserver.org \
--cc=flar@allandria.com \
--cc=hpa@zytor.com \
--cc=jack@hawkeye.stone.uk.eu.org \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).