Messages in this thread | | | Subject | Re: [Ext2-devel] [PATCH 1/2] ext2/3: Support 2^32-1 blocks(Kernel) | From | "Stephen C. Tweedie" <> | Date | Mon, 27 Mar 2006 15:40:32 -0500 |
| |
Hi,
On Mon, 2006-03-27 at 22:05 +0200, Alfred M. Szmidt wrote: > Now, a non-Hurd system is not going to have any use for the gnu.* > xattr semantics, as translator is a Hurd-specific concept. > > gnu.* doesn't just concern itself with translators, it can also be > gnu.author (or some such) which is a normal UID, which GNU/Linux can > support without any problems.
OK, but would it have any active semantics on non-Hurd kernels? How would the behaviour of ext3 change in the presence of a gnu.author attribute on a file?
It would certainly be possible to add a generic ext2/3 namespace handler to allow those fields to be set on, say, Linux hosts; but that would just be a matter of matching the gnu.* syscall xattr encoding to the EXT2_XATTR_INDEX_GNU on-disk encoding; it wouldn't actually deal with any semantic expectations surrounding the use of those fields.
--Stephen
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |