From: "Michael Kerrisk" <mtk-lkml@gmx.net>
To: Jacky Malcles <Jacky.Malcles@bull.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A question about extended attributes of filesystem objects (setfattr command)
Date: Wed, 30 Jun 2004 15:31:59 +0200 (MEST) [thread overview]
Message-ID: <17330.1088602319@www51.gmx.net> (raw)
In-Reply-To: 40E2B795.35EA5824@bull.net
Gidday,
> I have a question regarding
> Attributes of symlinks vs. the files pointed to
>
> If I try to attach name:value pair to object symlink file
> then I'll get: "Operation not permitted"
What file system are you using? If ext2, ext3 (or patched kernel
supporting Reiserfs EAs), did you mount with "-o user_xattr?
(The above error suggests you haven't used this option.)
> reading the man pages of setfattr (or attr) I thought that it operates
> on the attributes of the symbolic link itself.
No, these commands follow symbolic links.
> show:
> -----
> touch f
> ln -s f l
> setfattr -n user.filename -v ascii1 f l
> setfattr -h -n user.filename -v ascii2 f
> getfattr -d f l
> setfattr -h -n user.filename -v ascii3 l
> setfattr -h --no-dereference -n user.filename -v ascii4 l
> getfattr -d f l
>
> so, my question is : what is expected ?
attr(5) specifically notes that USER EAs are disallowed on
symbolic links, but this is rather an issu that affects the
use of lsetxattr(2).
Cheers,
Michael
--
"Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen!
Jetzt aktivieren unter http://www.gmx.net/info
next prev parent reply other threads:[~2004-06-30 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 12:52 A question about extended attributes of filesystem objects (setfattr command) Jacky Malcles
2004-06-30 13:31 ` Michael Kerrisk [this message]
2004-06-30 14:04 ` Jacky Malcles
2004-06-30 14:21 ` Michael Kerrisk
2004-06-30 14:22 ` Jacky Malcles
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=17330.1088602319@www51.gmx.net \
--to=mtk-lkml@gmx.net \
--cc=Jacky.Malcles@bull.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.