public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexander Larsson <alexl@redhat.com>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: "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 12:59:57 +0200	[thread overview]
Message-ID: <1223895597.20751.34.camel@fatty> (raw)
In-Reply-To: <2FF8DF17-4056-447B-B18C-40103BFD2E73@cam.ac.uk>

On Mon, 2008-10-13 at 08:29 +0100, Anton Altaparmakov wrote:
> Hi,
> 
> On 10 Oct 2008, at 22:57, Theodore Tso wrote:
> > Ext3 has no concept of "hidden file".  Niether does ext2, ext4, jfs,
> > xfs, reseirfs, ufs, etc.
> >
> > The only ones that would have that concept is vfat (which supports
> > fat16/fat32), ntfs, nfsv4 and cifs/smbfs.  Even a filesystem which
> > normally has very bad taste, MacOS's HFS, doesn't support the hidden
> > attribute.
> 
> Sorry but you are somewhat wrong: UFS, HFS/HFS+, ZFS, and AFP all  
> support the UF_HIDDEN file flag (in addition to the ones you state  
> above).

FreeBSD seems to have added UF_HIDDEN to struct stat.st_flags back in
2006:
http://updraft3.jp.freebsd.org/cgi/query-pr.cgi?pr=kern/94519

They also have other useful flags like immutable, append only, no dump,
etc that certainly apply to ext3 too (i.e. these are settable with
chattr).

Sounds like a very good idea to me. There is even availible unused space
in the userspace/glibc struct stat to add them, and there seems to be
some in the kernel struct too.

They also have chflags/lchflags/fchflags to change these attributes.


      parent reply	other threads:[~2008-10-13 11:00 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
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 [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=1223895597.20751.34.camel@fatty \
    --to=alexl@redhat.com \
    --cc=84yelo3@gmail.com \
    --cc=aia21@cam.ac.uk \
    --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