Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1356242

Re: Variant symlink filesystem

From David Lang <david@lang.hm>
Newsgroups linux.kernel
Subject Re: Variant symlink filesystem
Date 2016-03-11 23:40 +0100
Message-ID <rbDSW-4EW-7@gated-at.bofh.it> (permalink)
References (2 earlier) <rbBHs-32u-9@gated-at.bofh.it> <rbBHs-32u-13@gated-at.bofh.it> <rbBR8-38o-7@gated-at.bofh.it> <rbBR8-38o-5@gated-at.bofh.it> <rbC0N-3ei-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On Fri, 11 Mar 2016, Cole wrote:

> On 11 March 2016 at 22:24, Richard Weinberger <richard@nod.at> 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

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Variant symlink filesystem Cole <cole@opteqint.net> - 2016-03-11 17:30 +0100
  Re: Variant symlink filesystem "Austin S. Hemmelgarn" <ahferroin7@gmail.com> - 2016-03-11 17:50 +0100
  Re: Variant symlink filesystem Richard Weinberger <richard.weinberger@gmail.com> - 2016-03-11 21:10 +0100
    Re: Variant symlink filesystem Cole <cole@opteqint.net> - 2016-03-11 21:20 +0100
      Re: Variant symlink filesystem Richard Weinberger <richard@nod.at> - 2016-03-11 21:20 +0100
        Re: Variant symlink filesystem Richard Weinberger <richard@nod.at> - 2016-03-11 21:30 +0100
          Re: Variant symlink filesystem "Austin S. Hemmelgarn" <ahferroin7@gmail.com> - 2016-03-11 21:40 +0100
            Re: Variant symlink filesystem Cole <cole@opteqint.net> - 2016-03-11 22:00 +0100
              Re: Variant symlink filesystem Al Viro <viro@ZenIV.linux.org.uk> - 2016-03-11 23:00 +0100
                Re: Variant symlink filesystem Cole <cole@opteqint.net> - 2016-03-11 23:10 +0100
                Re: Variant symlink filesystem Al Viro <viro@ZenIV.linux.org.uk> - 2016-03-11 23:30 +0100
                Re: Variant symlink filesystem Cole <cole@opteqint.net> - 2016-03-11 23:40 +0100
                Re: Variant symlink filesystem David Lang <david@lang.hm> - 2016-03-11 23:50 +0100
                Re: Variant symlink filesystem Cole <cole@opteqint.net> - 2016-03-12 00:00 +0100
                Re: Variant symlink filesystem David Lang <david@lang.hm> - 2016-03-11 23:50 +0100
          Re: Variant symlink filesystem Cole <cole@opteqint.net> - 2016-03-11 21:40 +0100
            Re: Variant symlink filesystem Richard Weinberger <richard@nod.at> - 2016-03-11 21:40 +0100
            Re: Variant symlink filesystem David Lang <david@lang.hm> - 2016-03-11 23:40 +0100
        Re: Variant symlink filesystem Cole <cole@opteqint.net> - 2016-03-11 21:30 +0100

csiph-web