Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Windows Linux

Windows 10 Spring Update Improves Linux On WSL With Unix Sockets and More (anandtech.com) 216

Billly Gates writes: Windows 10 build 1803 has come out this month, but with some problems. AnandTech has a deep-dive with the review examing many new features including the much better support for Linux. WSL (Windows Subsystem for Linux) now has native Curt and Tar from the command prompt as well as a utility to convert Unix to Windows pathnames called WSLpath.exe which is documented here. In addition it was mentioned on Slashdot in the past about OpenSSH being ported natively to Win32 in certain early builds. It now seems the reason was for Linux interoperability with this Spring Update 2. Unix sockets mean you can run Kali Linux on Windows 10 for penetration testing or run an Apache server in the background with full Linux networking support. Deemons now run in the background even with the command prompt closed. [...]
This discussion has been archived. No new comments can be posted.

Windows 10 Spring Update Improves Linux On WSL With Unix Sockets and More

Comments Filter:
  • They can get Linux to run as a layer or app under Windows, but can't figure out how to get it to run from a different drive. Some of us have a smaller SSD as C drive and would like to at least play with this without having to jump through hoops. Yes, I know about symlinks in Windows, but it's kind of a crappy fix, if it works at all.

    • by phantomfive ( 622387 ) on Monday May 28, 2018 @10:49PM (#56691136) Journal
      Be patient. Eventually the Linux subsystem will be all that's left of Windows. Maybe a legacy support module on the side.
      • You'd have to call it the Linux supersystem by then, I think. Also "mission accomplished"!
        • Eventually the Linux subsystem will be all that's left of Windows. Maybe a legacy support module on the side.

          You'd have to call it the Linux supersystem by then, I think. Also "mission accomplished"!

          Now you understand why the SystemD is on such a big phagocytosis spree :
          Swallowing the whole Microsoft Windows into "system-msctl" was Lennart's secret end goal all along !

    • by Rob Y. ( 110975 )

      Okay, you mentioned 'different drive', so I'll ask here. Since I installed this update, Windows 10 has refused to allow apps run from a remote drive to open sockets. The same app, when copied to the C: drive works fine. A simple example is PuTty.

      I'm sure this is some new security feature - but I need to disable it, since a win32 app I work on lives on a LAN drive (so, y'know, it gets backed up). I can build it there, but I can run it or debug it from there. I can run it if I copy it to my C: drive. Th

    • by I4ko ( 695382 )

      Why another drive? NTFS has had junction points for ages (at least since XP). You can mount a partition as a folder, just like you do on *nix. Check it out.

  • Comment removed (Score:4, Insightful)

    by account_deleted ( 4530225 ) on Monday May 28, 2018 @10:17PM (#56691056)
    Comment removed based on user account deletion
    • by DrYak ( 748999 )

      i presume we mean curl but this is moot. Anyone who needed curl or tar "from the command prompt" (as if it came anywhere else?) {...}

      Yes, curl comes anywhere else.
      It has also a library (libcurl) and that library is used for web interface by lots of modules.
      Probably lots of GUI application use curl as their peculiar backend to download stuff.

      Except that in WSL's specific case, support for GUI isn't stellar (basically, you need to X-over-network to a Windows native X-Server), so probably nobody is using GUI, and in practice, yes, curl is mostly only used on the command line in Windows-land.

    • So far bootstrapping things like Kinect, office, and exchange to their cloud offering has boosted its presence in much the same way that paying hosting providers to switch their park-web sites to IIS static pages improved their netcraft numbers.

      So ... translated into very real income and marketshare making it the most profitable part of the company?

       

    • > Daemons,Welcome to 1991.

      It's a lot older than that. I remember using nohup in BSD 4.3 in 1987, over thirty years ago.

  • Why would I want this?

    • by AlanBDee ( 2261976 ) on Monday May 28, 2018 @11:19PM (#56691202)

      You may not but I do. My work requires that I use Windows. With WSL I can use all the classic Linux commands that I've been using for 15 years. The better they make it the happier I am.

      • Re: (Score:2, Insightful)

        by Bert64 ( 520050 )

        My work requires that i get various tasks done, how i achieve them doesn't matter so long as they get done. If they are performed more efficiently using Linux then that's where they are performed.
        If you're being forced to use tools which make your work inefficient then you should raise it as a problem, or consider moving jobs.

      • Or you could just do it the sane way and run Linux, with Windows in a VM for running the one (or few) applications that you absolutely must have Windows to run.
        • If you can. Most companies are the other way, because the IT staff have literally zero experience with anything other than Windows.

      • by nyet ( 19118 )

        and you aren't competent enough to install cygwin?

    • Why would I want this?

      If you don't know why you want this then how do you know that nothing of value was gained?

    • I don't care what you want, but I use it so that I can use some nice Linux commands in Windows. For example wget, cloc etc. Those can be installed in native windows, but it's more quicker to install them in the wsl. It's a better version of "command line". Unfortunately I don't get to choose my work OS.
  • by Anonymous Coward

    who sees Microsoft using all of their friendliness towards open source, and Linux in particular, to "soften" the stance of using Linux as a standalone solution in lieu of actually using Linux. In the last few years, Linux has been its own worst enemy. What with systemd, utter balkanization, no "usable" desktop to go mainstream with (save Red Hat using Gnome internally), getting into bed with Azure.

    As a former Unix sysadmin who had to move cross country for family reasons, I have been forced into Windows job

    • by novakyu ( 636495 )

      Eh. As a user who have no choice but to use Windows, I welcome our new Bash-friendly Windows overlords. My choice is not whether to use Windows or Linux; my choice is whether to have a Linux dual-boot install which I hardly ever use (and have a Cygwin install which does not work well), or to have have access to Linux toolchain (without a reboot or a second device) while being able to use applications that my job requires me to use.

      • by swb ( 14022 )

        I often wonder what the Windows/Linux balance of power would look like if MS had released PowerShell with full BASH support, GNU tools and then the Microsoft-specific PowerShell commands as just extensions.

        I know PS advocates make a lot of noise about PS being object oriented but I don't see why that demands a completely new command line syntax. The shell may need object awareness to handle pipelining between PS object generators/consumers, but a totally new syntax from the ground up seems to be just a bar

        • by godefroi ( 52421 )

          What does "full BASH support" mean? You seem hung up on the syntax. If bash's syntax was universally accepted as "the best", then we wouldn't have things like csh, zsh, fish, etc with differing syntax.

          • by swb ( 14022 )

            Most "sh" variants are pretty close and derivative, leading to reasonable portability among them.

            I don't know that bash is "the best" but it is pretty widely used and basing PowerShell off its syntax would have provided a lot of existing compatibility. I guess Microsoft was really looking to do something else.

            • by godefroi ( 52421 )

              I mean, personally, I find bash's syntax awful, and powershell's functional-ish syntax not so bad, but that's just me. At least they didn't base it off of Windows' batch language.

    • by Srin Tuar ( 147269 ) <zeroday26@yahoo.com> on Tuesday May 29, 2018 @09:31AM (#56693036)

      The problem you are facing is more that sysadmin as a career is fading away to be replaced by devops.

      Linux is easy enough to admin that linux IT dept were always a fraction of the windows departments.

      Now that most linux admin work is scripted/automated, Linux IT jobs are all but non-existent.

      Windows IT jobs may last a bit longer, but as you can see, not much.

      • I thought devops was being split apart again now that experience shows that combining developers and operators was counter productive?

  • A big step towards running systemd on Windows!
  • by fahrbot-bot ( 874524 ) on Tuesday May 29, 2018 @01:17AM (#56691500)

    Unix sockets mean you can run Kali Linux on Windows 10 for penetration testing or run an Apache server in the background with full Linux networking support.

    You could just run Linux (and maybe Windows 10 in a VM).

    • Seems excessive if you want to just fire up one Linux app. What next, copy and past the output back into Windows? Why would you run Windows in a VM anyway? Anyone being remotely targeted by WSL is likely running Linux in the VM.

    • Not everyone is allowed to have a custom OS. This is a way to get around this. I installed a Centos VM on my Windows box and within a minute of joining it to the domain I had an IT person asking me why there was a Centos machine on the network. This quite rightly raised a security issue, because they can't just have random machines appearing on the network. However when I installed the WSL nothing came up in that alerting system. So now I can use Linux tools on my machine without registering as another "ma
      • That's a good point, thanks. I wasn't thinking about a corporate environment. However, I imagine IT should be concerned about WSL as well, at least to some extent, as it's another potential vector into the system.

    • VMs are painful at times. How do you back them up? A lot of backup programs are stupid and want to backup the entire VM image. Also the VMs are huge, taking up much more disk space than the equivalent WSL or Cygwin, and they suck up RAM so that having several VM images actively running will noticeably affect your computer's performance. If you can run things natively then that works better; save the VM for when you can't run things natively.

    • so i have to fire up a whole VM just to run `sed`? no thanks.

  • by biggaijin ( 126513 ) on Tuesday May 29, 2018 @09:30AM (#56693030)

    This means that I will be able to run Linux as a bag on the side of your wonderful Windows 10 product with two big advantages over a normal Linux installation: I will have the enormous overhead and slow boot time of Windows to deal with daily. And, Windows 10 will continue to spy on my every move and report it to you without telling me. I can hardly wait to get on the bandwagon with this one.

    • This means that I will be able to run Linux as a bag on the side of your wonderful Windows 10 product with two big advantages over a normal Linux installation: I will have the enormous overhead and slow boot time of Windows to deal with daily. And, Windows 10 will continue to spy on my every move and report it to you without telling me. I can hardly wait to get on the bandwagon with this one.

      It takes like five or six seconds after the boot splash for Windows to fully boot, unless I fat finger my password.

      • It takes like five or six seconds after the boot splash for Windows to fully boot, unless I fat finger my password.

        Wait, are you talking about in an enterprise? Then you're probably waiting on Group Policy, and that's... nearly unavoidable in an enterprise, unfortunately, especially if they haven't optimized it well.

    • i dual-boot linux & win10 on this machine. the linux machine takes significantly longer to boot than windows.

  • Now that you have proper OS support, just make the move and go to a proper OS! WSL is a joke, it's for users who want to act like their Linux users, without running Linux, so just bite the bullet and move to a proper OS.
  • Whoooohooooo now I can scp files directly to and from my linux boxes without the need for external programs like winscp and putty. I tried it out and work pretty well so not sure what all the hate in this thread is all about.

    At the end of the day I just want to get my work done as easily and quickly as possible and for me this helps a lot.

    On the downside it kinda sucks that this will probably kill both winscp and putty that I have been using for years.

  • Can you get a linux distribution installed *without* using the Microsoft store?

Avoid strange women and temporary variables.

Working...