Live data from Hacker News

Bash and Windows Subsystem for Linux Demo [video]

channel9.msdn.com

171–180 of 316 posts

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

#171
post #98

Any news about 256-color support? I understand the desire for the extreme backwards compatibility, but it requires some manual magic done to display things properly in fish (which, thankfully, works really well with Bash on Windows after the aforementioned magic), and even then it will only support 16 colors.

Yes, we support every color sequence there is now, for full 256color/24bit color support.

At this point, I believe the terminal emulation is pretty close to complete, so if you notice any other shortcomings, make sure to take a look at or GH page for issue reporting:

https://github.com/Microsoft/BashOnWindows/issues

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

#172
post #117

Earlier quoted context omitted.

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

Yeah, to be clear here: We worked with the networking team to enable Linux Ping to open a raw socket, but we've not enabled carte blanche raw-socket support for all Linux processes. We are, however, continuing to work on solving these and several other networking issues to close the gap in our networking support. As a work-around, you could always call Windows' tracert.exe via the interop feature ;) An if you're just…

Any chance we'll see a first-party X11 server at some point? XMing, VCXsrv, and Cygwin/X all have some warts when it comes to stuff like windows previewing, copy/paste, acceleration, and fonts. OS X has shipped with an optional X11 server forever, and it would be great to see that feature parity in Windows.

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

#173
I'm pretty happy that Windows Subsystem for linux mostly works. I was able to get Don Melton's video scripts for video conversion to work on my Windows machine quite nicely. I do wish they'd update the base version of Ubuntu used to the 16.04 release. I had to update a bunch of the software needed as the releases for 14.04 were out of date. (ruby being the main one)

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

#174
post #100

Earlier quoted context omitted.

> - 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!

I was under the impression that only linux sub-system applications should be modifying files inside the linux sub-system. For example, using windows explorer to edit linux sub-system files would be a big no-no.

Yes, that is the guidance we're giving right now. See my post on this subject for more background: https://blogs.msdn.microsoft.com/commandline/2016/11/17/do-n...

However, it's fine to modify files stored in your Windows filesystem from within Bash, so if you were in `/mnt/c/dev/project/` and launched `code.exe ./`, Code would open the current (Windows-accessible) folder.

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

#176

Do you think they'll ever enable background Linux daemons, so that I don't have to keep a terminal open to keep Postgres running?

We're looking into it. No guarantees yet as there are several challenges and security / management obstacles to overcome, but we are keen to make daemons work if possible.

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

#177

The biggest problem I have with the WSL is that it is intrinsically tied to stable Windows releases; there is no way to get incremental updates for Bash on Windows unless you subscribe to the Windows Insider program, which is a way of running prerelease versions of Windows. So in order to get Linux features like inotify working you have to sacrifice the stability of your operating system. This looks like it'll be tru…

@OhSoHumble: We totally hear you. We'd love to ship WSL builds uncoupled from the rest of the OS, but at the moment, we're developing WSL at a breakneck pace alongside several other critical kernel feature changes which all have to ship in lock-step. A good example of this is the work we've been doing with the networking team to add additional network socket mode support to the NT kernel's networking stack so that we…

That's good to know. Maybe I'll try to use Windows as a development platform when it has another major release. I'm really impressed that WSL exists at all. I didn't think Microsoft had it in them to allow such a project to flourish.

At the end of the day, however, I really hate writing code on Windows. I don't write much Java or C#, instead sticking to Elixir, Ruby, Python, Node, and Golang. Every time I try to use Windows I just get super frustrated. I remember showing up to a Code for San Francisco meeting with a Windows laptop and being the only person there without a Mac. I mean, go check out node-gyp's 500 comment 'windows users arent happy' issue to see how deep the rabbit hole goes.

WSL makes an impact on a lot of the issues that frustrate me. Knowing I have a tool chain that can actually compile C extensions matters. I'll never, ever bet my career on Windows but I might one day use it as hobbyist development platform.

While I have you here, will the Windows console ever 'get better?' Rendering console text on Windows is... pretty awful, I'm not going to lie. Going from Linux to Windows is fairly painful; when I `cat` a large file in Windows it then takes seven years for all the text to render. Day to day usage just feels sluggish and awkward in comparison to a Linux terminal. Even if WSL was a flawless piece of engineering, the 'terminal experience' on Windows could do with some TLC. Are there any internal plans to make improvements?

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

#178
post #94
post #34

Earlier quoted context omitted.

* Yes, these are native, ELF binaries. Yes, you can compile it on your linux server, cp it across to windows, and run it. * No, it is not an emulation. The win10 kernel + compatibility layer just happens to be able to also run ELF binaries. Yes, these show up as standard processes, and can be interacted with using normal windows tools (eg taskmgr).

Windows also needs to simulate the Linux kernel ABI -- not just "run ELF binaries". It's like "kernel personalities" in BSD.

Erm ... that's exactly what WSL does. Not quite sure how we'd be able to run ELF64 Linux binaries without building a comprehensive Linux ABI compatible layer.

You might be interested in some of these videos and posts: https://blogs.msdn.microsoft.com/commandline/learn-about-bas...

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

#179
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.

KDevelop is also a very good C++ IDE for Linux.

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

#180

How is the file system performance going with this? The latest release version runs Rails worse than shared folders on VMWare which is slow in bad way. Running MySQL on top of it might "work" but is it fast?

IO perf isn't where we want it to be yet, but we've some improvements coming in Creators Update and more planned for future releases.
Post reply on HN