All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guido Schimmels <guido.schimmels@freenet.de>
To: reiserfs-list@namesys.com
Subject: Re: Will Reiser4 support a "hidden" attribute?
Date: Thu, 20 Nov 2003 20:45:55 +0100	[thread overview]
Message-ID: <20031120194555.GA23113@Benine> (raw)
In-Reply-To: <16317.3267.987713.833145@laputa.namesys.com> (from Nikita@Namesys.COM on Don, Nov 20, 2003 at 19:49:39 +0100)

Am 20.11.2003 19:49:39 schrieb(en) Nikita Danilov:
> 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.

I have outlined why this is not an option. Handling this above the  
kernel/libc level means maintaining dozens of patches to consistently  
hide files throughout the GUI. And for Acrobat Reader e.g. you  would  
still need LD_PRELOAD trickery which means you are again down at the  
libc level. Thinking of it, an even better example is Sun's Java,  
which, though the sources are available, I'm not allowed to hack on.

  parent reply	other threads:[~2003-11-20 19:45 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
2003-11-20 19:45         ` Guido Schimmels [this message]
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=20031120194555.GA23113@Benine \
    --to=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.