On Sat, Jul 26, 2014 at 8:01 AM, Paul Colomiets <[email protected]> wrote:
> Hi Mike, > > On Sat, Jul 26, 2014 at 5:29 AM, Mike Shal <[email protected]> wrote: > > It's definitely something that should be supported in the future, > certainly > > for getting rid of the annoying .tup/mnt paths that show up in some > > sub-processes, as well as not having to make tup suid. Hopefully we'll > get > > there soon. I agree with Ben that until it's widespread, we should still > > support the suid way for older kernels. > > > > Sure. Looking forward to see it implemented :) > Well I know it's been a long time, but I was finally able to revisit this. I pushed a test patch to the 'unshare' branch on github, which avoids the .tup/mnt path issue, even without using the ^c flag and without suid. For those who are interested, can you try it out and let me know if there are any regressions? The test cases pass on Linux (it probably breaks OSX, which is why it's not on master). I've noticed a small degradation in performance, but I'm not totally sure yet where it's coming from. Thanks! -Mike -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
