Author

Topic: Ubuntu and Bash on Windows 10 (Read 1392 times)

member
Activity: 70
Merit: 10
June 09, 2016, 12:58:38 AM
#6
The has to do with an issue with binding to ports from the Linux Subsystem. Because Bitcoin Core can't bind to the necessary ports, you can't access it over RPC nor will it be able to accept incoming connections. This is a problem with the subsystem itself so you will have to wait for later releases to fix that.

It should, however, be possible to fix programmatically IMHO?
No, it's a problem with the Linux subsystem itself.
No. Its a problem with people thinking every solution to software is to install Linux and Linux tools where they don't belong.

Compile it for Windows or run Linux in a VM but don't poison Windows with Linux hacks.

Lol. Wtf? Who suggested that? Cheesy
newbie
Activity: 5
Merit: 0
June 03, 2016, 06:19:19 AM
#5
The has to do with an issue with binding to ports from the Linux Subsystem. Because Bitcoin Core can't bind to the necessary ports, you can't access it over RPC nor will it be able to accept incoming connections. This is a problem with the subsystem itself so you will have to wait for later releases to fix that.

It should, however, be possible to fix programmatically IMHO?
No, it's a problem with the Linux subsystem itself.
No. Its a problem with people thinking every solution to software is to install Linux and Linux tools where they don't belong.

Compile it for Windows or run Linux in a VM but don't poison Windows with Linux hacks.
staff
Activity: 3458
Merit: 6793
Just writing some code
May 25, 2016, 11:18:14 AM
#4
The has to do with an issue with binding to ports from the Linux Subsystem. Because Bitcoin Core can't bind to the necessary ports, you can't access it over RPC nor will it be able to accept incoming connections. This is a problem with the subsystem itself so you will have to wait for later releases to fix that.

It should, however, be possible to fix programmatically IMHO?
No, it's a problem with the Linux subsystem itself.
member
Activity: 70
Merit: 10
May 25, 2016, 11:10:24 AM
#3
The has to do with an issue with binding to ports from the Linux Subsystem. Because Bitcoin Core can't bind to the necessary ports, you can't access it over RPC nor will it be able to accept incoming connections. This is a problem with the subsystem itself so you will have to wait for later releases to fix that.

It should, however, be possible to fix programmatically IMHO?
staff
Activity: 3458
Merit: 6793
Just writing some code
May 14, 2016, 08:01:26 AM
#2
The has to do with an issue with binding to ports from the Linux Subsystem. Because Bitcoin Core can't bind to the necessary ports, you can't access it over RPC nor will it be able to accept incoming connections. This is a problem with the subsystem itself so you will have to wait for later releases to fix that.
legendary
Activity: 896
Merit: 1001
May 14, 2016, 02:38:26 AM
#1
I was able to build bitcoind and launch the daemon but could not connect using bitcoin-cli.  The bitcoind was running and downloading blocks but I couldn't get any response when issuing commands with bitcoin-cli.

I'm sorry if this topic has been covered but it's new to me.  I did a search for "Ubuntu and Bash on Windows 10" but didn't find anything.  

Anyone else experimenting with Bash on Windows 10?  If so, do you have any tips regarding compiling and running bitcoin successfully?

Thanks

edit:

I'd like to point out that I haven't changed any of the Windows settings since the Ubuntu Bash instance operates in it's own space.  Everything worked as if I was at an linux command line.  Everything compiled.  The daemon started.  The block data file keep growing.  I just can't use the tools that the bitcoin-cli provides because it doesn't connect to the daemon.
Jump to: