From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Special Kernel Modification Results
Date: 5 Nov 2001 00:01:47 -0800 [thread overview]
Message-ID: <9s5h1b$fih$1@cesium.transmeta.com> (raw)
In-Reply-To: <1004926188.3be5f4ec7e622@mail.outstep.com>
Followup to: <1004926188.3be5f4ec7e622@mail.outstep.com>
By author: lonnie@outstep.com
In newsgroup: linux.dev.kernel
>
> It is nice that in Linux a person can easily set permissions to
> prevent someone from entering a particular directory, but for the
> special projects when you want to somehow confine them to their HOME
> directory then the standard permissions are somewhat illsuited for
> the task.
>
> There is always the problem of being able to see the binaries from
> the users directories if you were to lock them in.
>
> In any case, I am thinking that a combination of chroot and
> hard-links might do the trick.
>
Either that, or chroot and vfsbinds (mount --bind), which might
actually serve you better (no one-filesystem limit.)
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
prev parent reply other threads:[~2001-11-05 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-05 2:09 Special Kernel Modification Results lonnie
2001-11-05 8:01 ` H. Peter Anvin [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='9s5h1b$fih$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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 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.