From: David Howells <dhowells@redhat.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/4] Enhanced file stat system call
Date: Fri, 18 Nov 2016 13:49:31 +0000 [thread overview]
Message-ID: <12943.1479476971@warthog.procyon.org.uk> (raw)
In-Reply-To: <20161118134107.5bfecb72@lxorguk.ukuu.org.uk>
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk> wrote:
> > Hmmm... Interesting question. Probably should. But you could be insane and
> > RAID an nbd and a local disk. Further, does NFS over a loopback device to
> > nfsd on the same machine qualify as root? What if that's exposing a local fs
> > on NBD? Perhaps I should drop 'REMOTE' for now. It sounds like something
> > that a GUI filemanager might find interesting, though.
>
> GUI file managers already try and guess some of this in order to decide
> whether to display icons off remote file systems.
>
> You could be insane but it's always going to be a hint and nothing more
> and if it can't be perfect then that just goes in the notes in the manual
> page.
I've dropped REMOTE, FABRICATED, KERNEL_API, NONUNIX_OWNERSHIP, HAS_ACL and
UNLISTED_DENTS for now. I'm keeping AUTOMOUNT as that seems fairly
straightforward - though I'm sure we can find someone to disagree! ;-)
David
prev parent reply other threads:[~2016-11-18 13:49 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 13:34 David Howells
2016-11-17 13:35 ` [PATCH 1/4] statx: Add a system call to make enhanced file info available David Howells
2016-11-17 18:39 ` Jeff Layton
2016-11-18 2:32 ` Andreas Dilger
2016-11-18 8:59 ` David Howells
2016-11-18 9:25 ` Andreas Dilger
2016-11-17 23:40 ` Dave Chinner
2016-11-18 3:28 ` Andreas Dilger
2016-11-18 22:07 ` Dave Chinner
2016-11-18 22:54 ` David Howells
2016-11-19 22:43 ` Dave Chinner
2016-11-21 14:30 ` One Thousand Gnomes
2016-11-21 20:43 ` Dave Chinner
2016-11-22 10:39 ` David Howells
2016-11-22 13:55 ` Jeff Layton
2016-11-22 20:58 ` Dave Chinner
2016-11-18 9:53 ` David Howells
2016-11-18 8:48 ` David Howells
2016-11-18 12:01 ` Jeff Layton
2016-11-18 9:36 ` David Howells
2016-11-18 17:17 ` Jeff Layton
2016-11-18 18:04 ` David Howells
2016-11-18 18:54 ` Jeff Layton
2016-11-18 19:08 ` David Howells
2016-11-18 9:43 ` David Howells
2016-11-18 21:41 ` Dave Chinner
2016-11-18 22:24 ` David Howells
2016-11-18 10:29 ` David Howells
2016-11-18 21:27 ` Dave Chinner
2016-11-18 21:48 ` David Howells
2016-11-18 22:17 ` Dave Chinner
2016-11-19 10:21 ` Michael Kerrisk (man-pages)
2016-11-17 13:35 ` [PATCH 2/4] statx: Ext4: Return enhanced file attributes David Howells
2016-11-18 3:30 ` Andreas Dilger
2016-11-17 13:35 ` [PATCH 3/4] statx: NFS: " David Howells
2016-11-17 13:35 ` [PATCH 4/4] statx: AFS: " David Howells
2016-11-18 3:34 ` Andreas Dilger
2016-11-18 8:47 ` David Howells
2016-11-17 14:39 ` [RFC][PATCH 0/4] Enhanced file stat system call One Thousand Gnomes
2016-11-17 15:10 ` Michael Kerrisk
2016-11-17 16:33 ` David Howells
2016-11-17 16:45 ` David Howells
2016-11-17 20:00 ` J. Bruce Fields
2016-11-18 2:30 ` Andreas Dilger
2016-11-18 4:29 ` NeilBrown
2016-11-18 13:41 ` One Thousand Gnomes
2016-11-18 13:49 ` David Howells [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=12943.1479476971@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome