I really wish that Docker could natively run in WSL. It's a really aspirational project for Microsoft, but it's not doing anything that Cygwin doesn't at this time.
Command Line and Windows Subsystem for Linux – The Windows 10 April Update
11–20 of 80 posts
Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update
#12I advice people to not use WSL. It seems to me that this is the first step of their well-known embrace, extend, extinguish microsoft's strategy. They are now embracing the gnu/linux way of working like the packaging tools, the command line with the shells, the easy of having a compiler and developer tools, etc etc. At the same time they don't let you create from WSL standard Windows application that you can redistrib…
bloated system and the updates are very heavy
Really though, they asume everyone has a 100Mbps and a SSD, every new update is like a new install of windows, glad I don't have to use it.
Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update
#13Was so sad, because vagrant stopped working on my colleague's computer after this update.
I had to force Vagrant to use the "system" ssh binary ( VAGRANT_PREFER_SYSTEM_BIN=1 ), since the internal vagrant OpenSSH stopped working.
And this is without WSL being in use.
It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it.
Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update
#14I really like WSL for systems where I have to use Windows either for corporate reasons or driver support. Now that you can do UNIX sockets between the 'sides' its pretty easy to add shims for special purpose USB devices as well.
Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update
#15I advice people to not use WSL. It seems to me that this is the first step of their well-known embrace, extend, extinguish microsoft's strategy. They are now embracing the gnu/linux way of working like the packaging tools, the command line with the shells, the easy of having a compiler and developer tools, etc etc. At the same time they don't let you create from WSL standard Windows application that you can redistrib…
How are they extending Linux? It also sounds like you are asking them to, since you want to build Windows apps from WSL! A large part of the attraction of WSL for many, is that native windows ports are not needed.
Windows will never extinguish Linux, while it remains closed and proprietary, so I wouldn't worry about that.
Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update
#16Was so sad, because vagrant stopped working on my colleague's computer after this update. I had to force Vagrant to use the "system" ssh binary ( VAGRANT_PREFER_SYSTEM_BIN=1 ), since the internal vagrant OpenSSH stopped working. And this is without WSL being in use. It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it.
> It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it.
I find Git fine, but the Vagrant/Virtualbox ecosystem...
I dread every Windows update because something will break the setup, and that will be a day lost to figuring out which version of every component I need in order for my Virtual Machines to boot/build.
I would pay money for something that "Just works". Wondering if VMWare rather than Virtualbox is that, but no way to test without spending money.
Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update
#17I advice people to not use WSL. It seems to me that this is the first step of their well-known embrace, extend, extinguish microsoft's strategy. They are now embracing the gnu/linux way of working like the packaging tools, the command line with the shells, the easy of having a compiler and developer tools, etc etc. At the same time they don't let you create from WSL standard Windows application that you can redistrib…
the updates .. reset without asking many of the configurations you carefully made on your system.
Funny you should say that, I am normally quite fond of Win10 but I just installed the April update on my HTPC which uses a 4k TV as monitor.
The graphics settings went to hell, making the screen push past the boundaries or "overscanning" them. Reinstalling Nvidia graphics drivers now to hopefully bring things back into order. Willing to bet colours will default to 16-235 instead of 0-255 as well.
Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update
#18Another nice update to the WSL which I believe arrived with this version, SIGIO and nonblockig reads. This is very nice for console textmode UI apps.
Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update
#19Was so sad, because vagrant stopped working on my colleague's computer after this update. I had to force Vagrant to use the "system" ssh binary ( VAGRANT_PREFER_SYSTEM_BIN=1 ), since the internal vagrant OpenSSH stopped working. And this is without WSL being in use. It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it.
> It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it. I find Git fine, but the Vagrant/Virtualbox ecosystem... I dread every Windows update because something will break the setup, and that will be a day lost to figuring out which version of every component I need in order for my Virtual Machines to boot/build. I would pay money for somethin…
Run the vagrant inside Debian (possibly inside virtual box/hyperv/VMware/parallels running on your host OS).
Debian doesn’t pull or push the proverbial update rug under your legs without asking, and things rarely if ever break on a Debian stable update.
Re: Command Line and Windows Subsystem for Linux – The Windows 10 April Update
#20Was so sad, because vagrant stopped working on my colleague's computer after this update. I had to force Vagrant to use the "system" ssh binary ( VAGRANT_PREFER_SYSTEM_BIN=1 ), since the internal vagrant OpenSSH stopped working. And this is without WSL being in use. It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it.
> It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it. I find Git fine, but the Vagrant/Virtualbox ecosystem... I dread every Windows update because something will break the setup, and that will be a day lost to figuring out which version of every component I need in order for my Virtual Machines to boot/build. I would pay money for somethin…
Run VMs in Hyper-V. That just works