From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>,
Cedric Blancher <cedric.blancher@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: <DOT>foo gets NFSv4 HIDDEN attribute by default by nfsd? Re: How to set the NFSv4 "HIDDEN" attribute on Linux?
Date: Sat, 25 Nov 2023 09:52:36 -0500 [thread overview]
Message-ID: <afb9281a81c2001588dbaf46e0ac13fc99ffbb41.camel@kernel.org> (raw)
In-Reply-To: <ZWDgvFfkAF8e3MFj@tissot.1015granger.net>
On Fri, 2023-11-24 at 12:43 -0500, Chuck Lever wrote:
> On Thu, Nov 23, 2023 at 11:24:10PM +0100, Cedric Blancher wrote:
> > Also, it is legal for a nfsd to give the DOT files (/.foo) the HIDDEN
> > attribute by default? Right now on Windows they show up because NFSv4
> > HIDDEN is not set, and it is annoying.
>
> I suppose an NFS server could do this, but I'm not aware of any
> other multi-protocol file server (eg, Oracle ZFS or NetApp) that
> does.
>
> Dot-files are obscured on POSIX systems by the NFS clients and their
> user space (ls and graphical file navigators). I don't see why the
> Windows NFS client can't be similarly architected. Or perhaps it
> could fabricate the HIDDEN attribute for such files itself.
>
>
Question. GETATTR operates on filehandles, which are roughly analogous
to inode with Linux nfsd:
$ touch visible
$ ln visible .hidden
Is the resulting inode and filehandle now considered HIDDEN or not?
These kinds of issues are endemic when trying to map MS Windows concepts
onto Linux (and vice-versa).
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-11-25 14:52 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
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 [this message]
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=afb9281a81c2001588dbaf46e0ac13fc99ffbb41.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cedric.blancher@gmail.com \
--cc=chuck.lever@oracle.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