All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Cole <cole@opteqint.net>
Cc: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
	Richard Weinberger <richard@nod.at>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Variant symlink filesystem
Date: Fri, 11 Mar 2016 21:51:06 +0000	[thread overview]
Message-ID: <20160311215106.GU17997@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CACsf_wxdF-BkddKbu_Yke6Sid1NVLTpW+JTRnoCwhBbc3CHpVw@mail.gmail.com>

On Fri, Mar 11, 2016 at 10:52:52PM +0200, Cole wrote:

> The implementation doesn't necessarily have to continue to work with
> env variables. On FreeBSD, the variant symlinks function by using
> variables stored in kernel memory, and have a hierarchical lookup,
> starting with user defined values and terminating with global entries.
> I am not aware of such functionality existing on linux, but if someone
> could point me at something similar to that, I would much prefer to
> use that, as there are issues with variables that are exported or
> modified during process execution.

Put your processes into a separate namespace and use mount --bind in it...

  reply	other threads:[~2016-03-11 21:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 16:20 Variant symlink filesystem Cole
2016-03-11 16:44 ` Austin S. Hemmelgarn
2016-03-11 20:04 ` Richard Weinberger
2016-03-11 20:15   ` Cole
2016-03-11 20:18     ` Richard Weinberger
2016-03-11 20:22       ` Cole
2016-03-11 20:24         ` Richard Weinberger
2016-03-11 20:32           ` Cole
2016-03-11 20:36             ` Richard Weinberger
2016-03-11 22:27             ` David Lang
2016-03-11 20:38           ` Austin S. Hemmelgarn
2016-03-11 20:52             ` Cole
2016-03-11 21:51               ` Al Viro [this message]
2016-03-11 22:03                 ` Cole
2016-03-11 22:24                   ` Al Viro
2016-03-11 22:31                     ` Cole
2016-03-11 22:48                       ` David Lang
2016-03-11 22:54                         ` Cole
2016-03-11 22:38                   ` David Lang

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=20160311215106.GU17997@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=ahferroin7@gmail.com \
    --cc=cole@opteqint.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard@nod.at \
    /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.