From: Goswin v. B. <gos...@we...> - 2011-05-28 16:38:18
|
Mathias Panzenböck <gro...@gm...> writes: > Well, it's a read-only filesystem so setxattr/removexattr is not implemented. I use extended > attributes to expose some features of the underlying archive, e.g. the crc32 sums of the files. Hm, > maybe it would be good to always expose these values as big endian. My thinking is: at least in > theory it would be possible to network-mount a filesystem where my filesystem is mounted. I don't > know if NFS supports the transmission of xattrs, but if it does then the NFS client would not know > if the values are little or big ending (in case I just use the native endian). Also when you use big > endian and getfattr -e hex you get a proper hexadecimal crc32 value (that e.g. can be used in a script). Expose them as plain text (hex for crc32) in the byte order specified in the format of the file (and lets hope the file format doesn't specify host endianness). Returning pure binary data on getxattr() will cause no end of problems and will have little to no value to the user. For example what if your crc32 contains a 0 byte? MfG Goswin |