public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: Sten Spans <sten@blinkenlights.nl>, xfs@oss.sgi.com
Subject: Re: xfs_quota project + symlinks
Date: Tue, 31 Oct 2006 13:01:43 +1100	[thread overview]
Message-ID: <1162260103.17754.165.camel@edge> (raw)
In-Reply-To: <EFAEF35C8D3C3C927A1C43D3@timothy-shimmins-power-mac-g5.local>

On Tue, 2006-10-31 at 11:08 +1000, Timothy Shimmin wrote:
> 
> Okay, thanks, Nathan,
> 
> So does that mean we need a way for FSGETXATTR and FSSETXATTR
> ioctls to work on the symlink inode? Is this (symlink ioctls)
> done elsewhere? :)

The by-handle interfaces xfsdump is using must support symlinks,
right?  So, I assume theres a way (but I don't know for sure).

cheers.

-- 
Nathan

      reply	other threads:[~2006-10-31  1:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26 13:31 xfs_quota project + symlinks Sten Spans
2006-10-26 13:45 ` Sten Spans
2006-10-30  5:39   ` Timothy Shimmin
2006-10-30  7:54     ` Sten Spans
2006-10-30 22:24     ` Nathan Scott
2006-10-31  1:08       ` Timothy Shimmin
2006-10-31  2:01         ` Nathan Scott [this message]

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=1162260103.17754.165.camel@edge \
    --to=nscott@aconex.com \
    --cc=sten@blinkenlights.nl \
    --cc=tes@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox