wsl-2

Getting the same filename when renaming with wget [closed]

妖精的绣舞 提交于 2020-07-23 06:34:09
问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 8 days ago . Improve this question Using Windows 10 and wget to download files from a specific location, installed and configured WSL2. Once the setup was done, opened and ran the following command sudo apt-get install wget Then, ran the following command wget --header='Accept-Language: en-US,en;q=0

Getting the same filename when renaming with wget [closed]

孤者浪人 提交于 2020-07-23 06:31:40
问题 Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 8 days ago . Improve this question Using Windows 10 and wget to download files from a specific location, installed and configured WSL2. Once the setup was done, opened and ran the following command sudo apt-get install wget Then, ran the following command wget --header='Accept-Language: en-US,en;q=0

How to set up working X11 forwarding on WSL2

隐身守侯 提交于 2020-07-04 06:54:06
问题 When moving from WSL1 to WSL2 many things change; apparently this applies to X11 forwarding as well. What steps do I need to make in order to use X11 forwarding with WSL2 on Windows 10 as I did with WSL1? 回答1: TL;DR: Add the following to your ~/.bashrc : export DISPLAY=$(awk '/nameserver / {print $2; exit}' /etc/resolv.conf 2>/dev/null):0 export LIBGL_ALWAYS_INDIRECT=1 Enable Public Access on your X11 server for Windows.* Add a separate inbound rule for TCP port 6000 to the windows firewall

Connecting to WSL2 server via local network

半腔热情 提交于 2020-06-27 18:48:25
问题 I'm developing a rails app using WSL2/Ubuntu on my Windows 10 machine, which is great! The problem is I can't connect to my server from another computer in the same network . For further clarity, I am running a Puma server on localhost:3000 I have tried the following: Directly connecting to the IP address assigned to Ethernet adapter vEthernet (WSL) -> 172.26.208.1:3000 Directly connecting to the host machine's IPv4 address -> 192.168.0.115 Adding a firewall exception (using Bitdefender)