Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Cedric Blancher <cedric.blancher@gmail.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: How to set the NFSv4 "HIDDEN" attribute on Linux?
Date: Sat, 18 Nov 2023 06:56:25 -0500	[thread overview]
Message-ID: <83a30ef92afa05d50232bd3c933f8eb45ed8f98b.camel@kernel.org> (raw)
In-Reply-To: <CALXu0UdcCKBGR8FUSEeEMngKqwz98Xc2HFXnhX5i_1ioEiuaQg@mail.gmail.com>

On Sat, 2023-11-18 at 07:24 +0100, Cedric Blancher wrote:
> Good morning!
> 
> NFSv4 has a "hidden" filesystem object attribute. How can I set that
> on a Linux NFSv4 server, or in a filesystem exported on Linux via
> NFSv4, so that the NFSv4 client gets this attribute for a file?
> 

You can't. RFC 8881 defines that as "TRUE, if the file is considered
hidden with respect to the Windows API." There is no analogous Linux
inode attribute.

Cheers,
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2023-11-18 11:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-18  6:24 How to set the NFSv4 "HIDDEN" attribute on Linux? Cedric Blancher
2023-11-18 11:56 ` Jeff Layton [this message]
2023-11-19 16:51   ` Cedric Blancher
2023-11-20 11:46     ` Jeff Layton
2023-11-20 14:44       ` Chuck Lever III
2023-11-22 22:41         ` Cedric Blancher
2023-11-22 22:42       ` Cedric Blancher
2023-11-23 22:24         ` <DOT>foo gets NFSv4 HIDDEN attribute by default by nfsd? " Cedric Blancher
2023-11-23 22:46           ` Rick Macklem
2023-11-24 17:43           ` Chuck Lever
2023-11-25 14:52             ` Jeff Layton
2023-11-26 17:08               ` Chuck Lever
2023-11-27 13:33                 ` Jeff Layton
2023-11-30 10:28               ` Cedric Blancher
2023-11-30 14:17                 ` Jeff Layton
2023-11-24 17:30         ` Chuck Lever

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=83a30ef92afa05d50232bd3c933f8eb45ed8f98b.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=cedric.blancher@gmail.com \
    --cc=linux-nfs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox