From: "H. Peter Anvin" <hpa@zytor.com>
To: Nicholas Miell <nmiell@comcast.net>
Cc: hirofumi@mail.parknet.co.jp, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] get/set FAT filesystem attribute bits
Date: Mon, 03 Jan 2005 14:25:18 -0800 [thread overview]
Message-ID: <41D9C64E.7080508@zytor.com> (raw)
In-Reply-To: <1104790243.3604.23.camel@localhost.localdomain>
Nicholas Miell wrote:
>
> Yeah, I contemplated adding system.fattattrs, system.ntfsattrs, and
> system.linuxattrs (for the ext2 attrs that have popped up in several
> other filesystems) a while ago, but xattrs seem to be the red-headed
> left-handed stepchild of the Linux VFS and I lost interest in the
> project.
>
> Nice to see someone else interested in it, though.
>
I'm honestly not sure that using an ASCII string in an xattr is the sane
way of doing this. Even a binary byte in an xattr would make more sense
in some ways.
I think the xattr mechanism is ignored largely because it's painfully
complex.
A plus with using xattr is that in theory (but of course not in
practice!) it would let one store a copy of a DOS filesystem on an ext3
(or xfs, or...) filesystem and have it restored, all using standard (but
by necessity, xattr-aware) tools. However, the splitting of xattr into
namespaces may very well make that impossible, since what's a "system"
attribute to one filesystem is a "user" attribute to another. Classic
design flaw, by the way.
Anyway, I'm going to send out something to the various maintainers of
DOS-based filesystems (FAT, CIFS, NTFS) and see what they think.
-hpa
next prev parent reply other threads:[~2005-01-03 22:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 20:57 [PATCH] get/set FAT filesystem attribute bits H. Peter Anvin
2005-01-03 21:24 ` Nicholas Miell
2005-01-03 21:35 ` H. Peter Anvin
2005-01-03 21:46 ` Nicholas Miell
2005-01-03 22:02 ` H. Peter Anvin
2005-01-03 22:10 ` Nicholas Miell
2005-01-03 22:25 ` H. Peter Anvin [this message]
2005-01-03 23:16 ` Nicholas Miell
2005-01-03 23:22 ` H. Peter Anvin
2005-01-03 23:46 ` Nicholas Miell
2005-01-04 10:09 ` Anton Altaparmakov
2005-01-04 21:45 ` Nicholas Miell
2005-01-04 8:34 ` OGAWA Hirofumi
2005-01-04 9:41 ` H. Peter Anvin
[not found] <fa.ea9o20r.kje5qn@ifi.uio.no>
[not found] ` <fa.lub44op.a2ec2d@ifi.uio.no>
2005-01-04 11:57 ` Bodo Eggert
2005-01-04 21:26 ` H. Peter Anvin
[not found] <fa.i537e7s.1d6m90c@ifi.uio.no>
[not found] ` <fa.ihdqkec.1i5umji@ifi.uio.no>
2005-01-06 0:07 ` Bodo Eggert
2005-01-06 1:35 ` H. Peter Anvin
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=41D9C64E.7080508@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=hirofumi@mail.parknet.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=nmiell@comcast.net \
/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