Live data from Hacker News

Bash and Windows Subsystem for Linux Demo [video]

channel9.msdn.com

111–120 of 316 posts

Re: Bash and Windows Subsystem for Linux Demo [video]

#111
post #78
post #9

Earlier quoted context omitted.

> - Visual Studio can compile with GNU/Linux C/C++ tools, gdb, linker etc First VS Core, now VS proper. Impressive! (going back to my ddd window on Linux, crying a bit inside).

I've been playing with NetBeans and it seems like a fairly reasonable C++ environment.

It is quite good, as it is the basis of Solaris IDE, just some features are missing.

Re: Bash and Windows Subsystem for Linux Demo [video]

#112

Can anyone please tell if Windows SubSystem for Linux coexists well with Cygwin64 and/or msys? I have Cygwin64 installed. I don't use it a lot but it helps to run some deployment bash scripts which otherwise won't run on Windows. So it will be good to know if Windows SubSystem for Linux messes up with it or not.

Both run fine next to each other. The only conflict I can think of is if you don't call "bash" via a complete path, but rather rely on PATH environment variable.

Btw. any reason you are not running those bash scripts in WSL now?

Re: Bash and Windows Subsystem for Linux Demo [video]

#113
post #2

This is coming to Windows stable in April: - vt sequences fixed (so stuff like colored output, midnight commander, etc work and the terminal doesn't screw up) - Elixir and Go work - Also Postgres and MySQL - You can launch Windows apps from bash. - inotify works - Visual Studio can compile with GNU/Linux C/C++ tools, gdb, linker etc There's some recent fast ring info on: https://blogs.msdn.microsoft.com/commandline/2…

> - You can launch Windows apps from bash. So I can basically do `code .` from inside bash and it will open VS Code in the linux sub-system folder? That's amazing!

Almost. `code.exe .` will do what you expect IF you are in a folder that's visible from the Windows side. If you're in a WSL folder, the Windows program will be run in C:\Windows\System32.

It has worked well for me to make a symlink under ~ to /mnt/c/Users/myaccount/, and that way anything under that symlinked folder is visible to WSL and Windows programs.

Re: Bash and Windows Subsystem for Linux Demo [video]

#115

With Visual Studio Code, Microsoft is making Windows 10 really appealing to developers. I personally won't jump any time soon, I am really satisfied with my work environment on macOS (and Linux inside VM) (unless I got locked down into Microsoft stack for work, in that case I will gladly switch, but it's not like I will have any other option). But anyway, I recognize and appreciate the change at Microsoft's direction…

[deleted]

Re: Bash and Windows Subsystem for Linux Demo [video]

#116
post #71

Earlier quoted context omitted.

Is iterating over network interfaces possible? IIRC that was causing a lot of issues with local nodejs dev servers

Yeah it works. I can finally ping, do ifconfig etc. Even htop runs. I am amazed! http://imgur.com/7P2J64h

This alone made WSL way more useful for me. Only thing that's missing now is traceroute.

Re: Bash and Windows Subsystem for Linux Demo [video]

#117
post #97
post #71

Earlier quoted context omitted.

Is iterating over network interfaces possible? IIRC that was causing a lot of issues with local nodejs dev servers

On their blog they state that raw sockets (ping), ip address / ip route will work.

Still some work there though. Traceroute errors with: setsockopt IP_MTU_DISCOVER: Protocol not available

Re: Bash and Windows Subsystem for Linux Demo [video]

#120
post #114

This should be really useful for people who are forced to use Windows (e.g. at work). Other than that, I don't think many Linux/Unix enthusiasts are looking forward to running a spyware-ridden closed-source non-Unix operating system.

No, I believe they're not really after the enthusiasts. I think they're after the fence sitters. Implementing these tools on Windows removes motivation for casual dissenters from building intertia and leaving their platform.

This is of course not the first time Microsoft has done something like this. Historically, step two is where they extend the functionality for Windows only. Let's keep them honest and make sure they don't do that again!

Post reply on HN