Thanks Mike! I'll look user namespacing, and see what the current state is in WSL. The advantage of running on WSL versus native windows would be that currently there's no way for a windows process to initiate a linux process or vice versa, so if you had other tools that were only configured to be built on linux, the windows version of tup wouldn't "currently" be able to build them. Also, while WSL doesn't currently support things like inotify, support may come to WSL before native windows, which would be nice tup monitor. However, to be completely honest this was mainly an experiment, and I just wanted to look into the roadblocks.
Erik On Tue, Sep 13, 2016 at 5:40 PM Mike Shal <[email protected]> wrote: > On Tue, Sep 13, 2016 at 3:10 PM, Erik Brinkman <[email protected]> > wrote: > > Windows Subsystem for Linux, i.e. reverse wine, is a thing now, and so I > > figured I'd try to get to tup to work on it. It seems like currently > there > > is no support for fuse, so for the time being this is probably > irrelevant, > > but when I tried to do the bootstrapped update I got this error: > > > > /proc/114/uid_map: No such file or directory > > tup error: Unable to set the uid/gid map. > > tup error: master_fork server did not start up correctly. > > > > To those people more familiar with tup's backend / linux, do you know > what's > > behind this error? I'm assuming since windows needs a mapping for every > > kernel call, there are a lot missing, and this is one of them, but this > is > > pretty far outside my area of knowledge. > > That's for the user-namespacing / sandboxing that tup uses on Linux > (relevant search terms are probably "linux user namespaces" or "linux > unshare"). It allows tup to chroot and setup the FUSE mountpoint > without actually having root permissions or the suid bit set. With > user namespaces, tup can setup the subprocess' view of the filesystem > so that file access goes through the FUSE layer without having a > ".tup/mnt/" visible in the child process' CWD, and also prevent > subprocesses from circumventing dependency detection by using full > paths. > > I'm not familiar with WSL though - what's the benefit of getting tup > to run in that vs. using the native Windows tup binary? > > -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. > -- -- 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.
