Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932697AbcCKWft (ORCPT ); Fri, 11 Mar 2016 17:35:49 -0500 Received: from lang.hm ([66.167.227.134]:42513 "EHLO bifrost.lang.hm" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752766AbcCKWfq (ORCPT ); Fri, 11 Mar 2016 17:35:46 -0500 X-Greylist: delayed 461 seconds by postgrey-1.27 at vger.kernel.org; Fri, 11 Mar 2016 17:35:46 EST Date: Fri, 11 Mar 2016 14:27:59 -0800 (PST) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: Cole cc: Richard Weinberger , LKML Subject: Re: Variant symlink filesystem In-Reply-To: Message-ID: References: <56E327FF.1010103@nod.at> <56E3298A.1040008@nod.at> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1109 Lines: 28 On Fri, 11 Mar 2016, Cole wrote: > On 11 March 2016 at 22:24, Richard Weinberger wrote: >> Am 11.03.2016 um 21:22 schrieb Cole: >>> If I remember correctly, when we were testing the fuse version, we hard coded >>> the path to see if that solved the problem, and the difference between >>> the env lookup >>> code and the hard coded path was almost the same, but substantially slower than >>> the native file system. >> >> And where exactly as the performance problem? >> >> Anyway, if you submit your filesystem also provide a decent use case for it. :-) > > Thank you, I will do so. One example as a use case could be to allow > for multiple > package repositories to exist on a single computer, all in different > locations, but with > a fixed path so as not to break the package manager, the correct > repository then is > selected based on ENV variable. That way each user could have their own packages > installed that would be separate from the system packages, and no > collisions would > occur. why would this not be a case to use filesystem namespaces and bind mounts? David Lang