From: Hans Reiser <reiser@namesys.com>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: Guido Schimmels <guido.schimmels@freenet.de>, reiserfs-list@namesys.com
Subject: Re: Will Reiser4 support a "hidden" attribute?
Date: Wed, 19 Nov 2003 23:03:16 -0800 [thread overview]
Message-ID: <3FBC6734.4070104@namesys.com> (raw)
In-Reply-To: <16317.3267.987713.833145@laputa.namesys.com>
I respectfully disagree, and I expect us to keep to the plan I
outlined. Mr. Demidov, put this on your list of tasks to complete.
Guido, I am sorry to say that this will probably get added after we
submit a reiser4 with fully debugged traditional functionality to Linus,
which means sometime next year if I don't go broke in January.
Hans
Nikita Danilov wrote:
>Hans Reiser writes:
> > Nikita, please update us all on how far we have gotten in implementing this.
>
>OK.
>
>We currently don't have ability to hide particular file. That is, there
>is no way to somehow mark file hidden at the kernel level. If I am
>allowed to humbly voice my opinion, usages shown by participants of this
>thread (trimming down list of files visible in the GUI front-end) should
>be done at the user level. In UNIX ls(1) command hides dot files for
>ages.
>
>On the other hand, some file system objects (pseudo files
>http://namesys.com/v4/pseudo.html) are not shown by the readdir(2). But
>this is to keep various utilities like cp(1) and friends from trying to
>read from them.
>
> >
> > --
> > Hans
> >
> >
>
>Nikita.
>
>
>
>
--
Hans
next prev parent reply other threads:[~2003-11-20 7:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-20 0:58 Will Reiser4 support a "hidden" attribute? Guido Schimmels
2003-11-20 5:18 ` Stewart Smith
2003-11-20 14:23 ` Guido Schimmels
2003-11-20 6:33 ` Hans Reiser
2003-11-20 18:49 ` Nikita Danilov
2003-11-20 7:03 ` Hans Reiser [this message]
2003-11-20 19:45 ` Guido Schimmels
2003-11-20 14:35 ` Guido Schimmels
2003-11-20 18:42 ` Hubert Chan
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=3FBC6734.4070104@namesys.com \
--to=reiser@namesys.com \
--cc=Nikita@Namesys.COM \
--cc=guido.schimmels@freenet.de \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.