public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Amit S. Kale" <akale@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Subject: Per user private directories - trfs
Date: Mon, 19 Mar 2001 07:14:17 -0800	[thread overview]
Message-ID: <E14f1MP-0004HZ-00@usw-pr-shell1.sourceforge.net> (raw)

Hi,

Translators for providing per user private directories and restricting
visibility of files and directories using the translation filesystem are
available now at
http://trfs.sourceforge.net/

Per user private directories:
Files created in a per user private directory are not visible to users
other than the owner of the files. Per user view enables users to use shared
directories as if they were private. Using a peruser view for a shared
directory like /tmp allows users to have their own copy of the directory.
It also helps reduce contention for directories like /var/spool/mail that
undergo a large number of file creations and removals.

Restricted visibility of files and directories:
Owner of a file can make it invisible to group (of the file) or others by
restricting its visibility. A directory listing by a user shows only those
files which are visibile to the user. Invisible files cannot be accessed
even by using a stat system call.
--
Amit S. Kale
<akale@users.sourceforge.net>

Linux kernel source level debugger    http://kgdb.sourceforge.net/
Translation filesystem                http://trfs.sourceforge.net/

             reply	other threads:[~2001-03-19 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-19 15:14 Amit S. Kale [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-19 15:27 Per user private directories - trfs Heusden, Folkert van

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=E14f1MP-0004HZ-00@usw-pr-shell1.sourceforge.net \
    --to=akale@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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