Windows - Support 'bash for Windows'

[bobsummerwill]

From @bobsummerwill on April 7, 2016 17:24

At the Microsoft //BUILD conference a few days ago, Microsoft unveiled "Bash for Windows", where they have added a subsystem to the OS which supports a full set of Linux syscalls. They are hosting a vanilla Ubuntu 14.04 (Trusty) userspace from Canonical on top of that.

I think that we should just be able to use these instructions and it should "just work".

http://www.ethdocs.org/en/latest/ethereum-clients/cpp-ethereum/building-from-source/linux.html#installing-dependencies-for-ubuntu

Copied from original issue: ethereum/webthree-umbrella#445

[bobsummerwill]

From @chriseth on April 11, 2016 13:11

This might pull in a lot of additional dependencies. Do we really want that?

[bobsummerwill]

It won't. It's literally the Ubuntu Trusty userland. Same binaries.

Just trying our Trusty instructions in this environment which should be the same.

I gave it a whirl last night. I'll just keep looking at this for fun. It shouldn't need any changes on our side. More a question of reporting any problems to Microsoft.

[bobsummerwill]

https://twitter.com/BobSummerwill/status/719591645440651264

[bobsummerwill]

From @chriseth on April 11, 2016 19:48

Sure, it will pull in the trusty userland. Admittedly, we also explicitly provide all the dependencies for the native build...

[bobsummerwill]

See https://twitter.com/juanfranblanco/status/719590736543531008

[bobsummerwill]

Issue reported microsoft/WSL#147.

[bobsummerwill]

From @adampoewilson on April 18, 2016 4:25

I've already found an issue with Bash on Linux on Windows; scary as todo el infierno for me. Ok... I go in to either Powershell, type 'bash' and go from there, or just go into the Bash on Ubuntu on Windows program itself & go from there. When I'm in, however I choose to get there, I've tried out the calls the demo guy does from the Channel 9 video, the one w/ Rich Turner & Russ Alexander demo'ing.

So I get to the part where Russ.... I think he's the one doing demo. But he is gonna show a piece of code in the vi editor, and I thought 'oooh.... how cool if I could go in & try to get at my VS code and throw it up here!!!!!!'.... so I (without quotes) 'cd /mnt/c', and I'm mounted; then I 'ls' and I get this error: 'ls: cannot access Documents and Settings: Input/output error', and then 2 other 'Permission Denied' errors. I'm more concerned about the Documents and Settings error... and obviously, not just because I want to throw something up to friggin' vi editor..... ugh!!!!!!!

I just turned on the Insider Preview builds on this machine last night, it's a Gateway NE5 laptop, Pentium 2.4 Gig, Windows 10 Home, Version 1511, Preview Build 143.16.1000.

Am I worrying for nothing, since this effectively IS a preview build? Everything really works great, I can access the Documents and Settings here in Windows, I can get to them via Powershell; I should note that I got an error the first time I installed Bash... it was 0x and a bunch of other numbers. Looked on forums and someone said you had to uncheck a box to do with Legacy Mode in Powershell/Cmd - disabled in one and turned off for all. :) And then I was able to get Bash on Ubuntu on Windows up and running. :D Sorry for being so damn long winded.

Hope somebody can help!!!!!

[bobsummerwill]

There are lots of issues in Bash-for-Windows at the moment, @adampoewilson, it seems.
It is in its very early stages.

Just report whatever you see at https://github.com/Microsoft/BashOnWindows/issues. They're been pretty responsive. I imagine they will be doing updates every month or so.

[bobsummerwill]

As of June 9th, we can build but not run eth on Bash-for-Windows.

See ethereum/webthree-umbrella#567.