From: Theodore Tso <tytso@mit.edu>
To: "Nicolò Chieffo" <84yelo3@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Jeremy Allison <jra@samba.org>,
Alexander Larsson <alexl@redhat.com>,
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: Fri, 10 Oct 2008 21:36:15 -0400 [thread overview]
Message-ID: <20081011013615.GI8645@mit.edu> (raw)
In-Reply-To: <641322f90810101533p78d1bb9ame14a5c3c99b0b06e@mail.gmail.com>
On Sat, Oct 11, 2008 at 12:33:09AM +0200, Nicolò Chieffo wrote:
> Mm ok, with "hidden" I mean files that are not normally displayed when
> you list the directory, nothing more, sorry if I coulnd't explain
> well.
>
> I'm just talking as a normal user, sorry.
>
> Which is the correct definition of what I'm trying to explain?
The convention on all Unix systems is that files that begin with the
'.' character are not displayed by "ls" unless it is given the -a
option. It is not done using an attribute; it is merely a convention
based on a filename. So you can't "set an attribute" on all standard
Unix filesystems, and there's no hidden attribute to "get".
Note also that if you create a file named ".bashrc" and store it on a
VFAT or ntfs filesystem, it will not be displayed by the ls program.
It has nothing to do with any kind of attribute.
Part of what you clearly don't understand is that different operating
systems and different filesystems do this very differently.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-10-11 1:36 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 [this message]
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=20081011013615.GI8645@mit.edu \
--to=tytso@mit.edu \
--cc=84yelo3@gmail.com \
--cc=alexl@redhat.com \
--cc=hch@infradead.org \
--cc=jbacik@redhat.com \
--cc=jra@samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=szaka@ntfs-3g.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