All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timothy Shimmin <tes@sgi.com>
To: Dan Am <xfs@lonx.net>
Cc: xfs@oss.sgi.com
Subject: Re: "xfs_io -c chattr +i " on a symlink
Date: Fri, 04 Aug 2006 19:13:17 +1000	[thread overview]
Message-ID: <44D30FAD.5070704@sgi.com> (raw)
In-Reply-To: <39340.62.159.242.114.1154679319.squirrel@otto.lonx.net>

Dan Am wrote:
> On Fri, August 4, 2006 6:20 am, Chris Wedgwood wrote:
>> I always disliked open/ioctl for this.  I think we should actually have
>> a separate syscall for chattr, etc. (FreeBSD does this I think?)
 >
> So how does "attr -s someAttribute symlink" work ? This does the job very
> well, distinguishing it from other filesystems.
> 

attr(1) sets the extended attribute and they are set by system calls.
It looks like you would need the -L option to attr(1) which ends up
calling the lsetxattr() syscall via the libattr library.
(Inode attributes shouldn't be confused with extended attributes, EAs, -
  a cause of much confusion for me and others in the past :)

--Tim

  reply	other threads:[~2006-08-04  9:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04  8:15 "xfs_io -c chattr +i " on a symlink Dan Am
2006-08-04  9:13 ` Timothy Shimmin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-03 10:26 Dan Am
2006-08-03 14:13 ` Eric Sandeen
2006-08-04  0:29   ` Nathan Scott
2006-08-04  2:38     ` Eric Sandeen
2006-08-04 11:37     ` Dan Am
2006-08-07  4:54       ` Nathan Scott
2006-08-04  0:28 ` Nathan Scott
2006-08-04  4:20   ` Chris Wedgwood
2006-08-03 10:18 Daniel Amthor

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=44D30FAD.5070704@sgi.com \
    --to=tes@sgi.com \
    --cc=xfs@lonx.net \
    --cc=xfs@oss.sgi.com \
    /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.