On Mon, Aug 07, 2006 at 11:25:06PM +0200, Adrian Dziubek wrote: > I would add, that the same message is also issued, when the user tries > to change non-user attribute. e.g.: > setfattr -n something -v something > setfattr -n user.something -v something > The first won't work on user_xattr enabled partiton, the latter will. > > The message should be at least different from the standard one, like: > "No permission to change non-user attribute."
Hmm, thats really not at all simple to code into the tools in an always-correct way. > The: "operation not supported" doesn't fit here at all. Sure it does. Its pretty generic, but that error is just fine. There's only so much that can be conveyed in a simple perror(3), and only so much that should be interpreted from it. One could add more special case error reporting, but it is questionable as to how much value that would really add in practice, IMO. > I don't know how wide the standard > is, but one could also make a special flag for this namely: There are no standards covering extended attributes. The mount(8) man page now describes the mount options (another problem is that different filesystems have different mechanisms for enabling these things - there is no mount option for XFS, for example, they are always available). I'm going to close this bug, as I'm unconvinced there's really an issue to solve in the attr package here. If someone wants to add specific words to attr(5) for example, please send them and I will include them, but I don't really see the value (most people would not look there either..). cheers. -- Nathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
