From: Christoph Hellwig <hch@infradead.org>
To: Alexander Larsson <alexl@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Theodore Tso <tytso@mit.edu>, Nicol? Chieffo <84yelo3@gmail.com>,
Jeremy Allison <jra@samba.org>,
Szabolcs Szakacsits <szaka@ntfs-3g.org>,
Josef Bacik <jbacik@redhat.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: interface to ask is a file is hidden
Date: Mon, 13 Oct 2008 05:57:09 -0400 [thread overview]
Message-ID: <20081013095709.GA10373@infradead.org> (raw)
In-Reply-To: <1223886173.22225.159.camel@fatty>
On Mon, Oct 13, 2008 at 10:22:53AM +0200, Alexander Larsson wrote:
> This is a bad interface for most apps. You need to open each file to get
> a fd to pass to ioctl. This is problematic if for instance you don't
> have read access to the file. So, you really want a path-based operation
> for this.
Sorry, that just not how the unix file interface work like, and we're
not going to add crappy interface because your file manager wants to do
something stupid.
> Now, you could argue (and unsurpisingly you do) that ext3 & co doesn't
> have a hidden attribute, but that doesn't mean I can ignore actual users
> who have data on other filesystems and want to integrate nicely with
> them. This includes not showing weird system files that are normally
> hidden on said filesystems.
Yes, you can. These are foreign filesystems, and all access to the
filesystem (ls, echo, shell tab completion) also show them. No need to
be special in your fancy "file manager".
next prev parent reply other threads:[~2008-10-13 9:57 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 19:22 interface to ask is a file is hidden Nicolò Chieffo
2008-10-10 19:21 ` Josef Bacik
2008-10-10 19:35 ` Jeremy Allison
2008-10-10 20:00 ` Nicolò Chieffo
2008-10-10 19:57 ` Josef Bacik
2008-10-10 20:11 ` Nicolò Chieffo
2008-10-10 21:57 ` Theodore Tso
2008-10-10 22:01 ` Christoph Hellwig
2008-10-13 8:22 ` Alexander Larsson
2008-10-13 9:21 ` Nicolò Chieffo
2008-10-13 9:57 ` Christoph Hellwig [this message]
2008-10-13 10:37 ` Nicolò Chieffo
2008-10-13 10:37 ` Alexander Larsson
2008-10-13 10:43 ` Christoph Hellwig
2008-10-13 11:39 ` Alexander Larsson
2008-10-13 20:44 ` Jörn Engel
2008-10-13 20:50 ` Christoph Hellwig
2008-10-14 7:20 ` Alexander Larsson
2008-10-10 22:18 ` Szabolcs Szakacsits
2008-10-10 22:21 ` Nicolò Chieffo
2008-10-10 22:25 ` Christoph Hellwig
2008-10-10 22:33 ` Nicolò Chieffo
2008-10-10 22:36 ` Christoph Hellwig
2008-10-10 22:58 ` Nicolò Chieffo
2008-10-10 23:12 ` Szabolcs Szakacsits
2008-10-11 0:10 ` Bryan Henderson
2008-10-11 1:36 ` Theodore Tso
2008-10-10 22:57 ` Brad Boyer
2008-10-13 7:29 ` Anton Altaparmakov
2008-10-13 10:47 ` Christoph Hellwig
2008-10-13 10:59 ` Alexander Larsson
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=20081013095709.GA10373@infradead.org \
--to=hch@infradead.org \
--cc=84yelo3@gmail.com \
--cc=alexl@redhat.com \
--cc=jbacik@redhat.com \
--cc=jra@samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=szaka@ntfs-3g.org \
--cc=tytso@mit.edu \
/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