Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932809AbcCKVvR (ORCPT ); Fri, 11 Mar 2016 16:51:17 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:58769 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932659AbcCKVvJ (ORCPT ); Fri, 11 Mar 2016 16:51:09 -0500 Date: Fri, 11 Mar 2016 21:51:06 +0000 From: Al Viro To: Cole Cc: "Austin S. Hemmelgarn" , Richard Weinberger , LKML Subject: Re: Variant symlink filesystem Message-ID: <20160311215106.GU17997@ZenIV.linux.org.uk> References: <56E327FF.1010103@nod.at> <56E3298A.1040008@nod.at> <56E32CD3.1010705@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 660 Lines: 12 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...