Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bash and Windows Subsystem for Linux Demo [video]

channel9.msdn.com

Post reply on HN
Print view View original

151–160 of 316 posts

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

#151

Post by bitcrazed »

OhSoHumble wrote: post #38

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 can create the correct socket semantics that Linux apps expect. We're also working with the NTFS team, process & scheduling team, management infrastructure, etc.

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

#152

Post by beefield »

trentnelson wrote: post #145
thebspatrol wrote: post #89

Earlier quoted context omitted.

>Windows13 will be based 100% based on Great Linux I want to believe. I'd go fucking apeshit if Windows dropped the NT kernel for Linux or BSD.

That would be a huge regression. NT is far more advanced than Linux and BSD combined.

Source?

Personally, I wonder how long it takes before redmond realizes that they are wasting shareholder money by maintaining/developing a proprietary kernel. It's not like they could not sell windows/linux as a perfectly good OS with copyrighted components on top of the kernel.

Or then I have missed something significant.

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

#153

Post by isaac_is_goat »

nailer wrote: 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…

> - vt sequences fixed (so stuff like colored output, midnight commander, etc work and the terminal doesn't screw up)

Does this mean tmux will work?

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

#154

Post by hellcow »

chrisper wrote: post #118

I just ran my local go project in WSL. And I can confirm it works just like it does in Linux. This is huge for everyone!

Along those lines, a great trick for Go on Windows is to set your $GOPATH outside of the WSL filesystem, so you're developing in, e.g. /mnt/c/. This gives you full access in both Windows and Linux to your Go project, so if you need to open a file in Photoshop, etc. it's painless.

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

#155

Post by bitcrazed »

OhSoHumble wrote: post #38

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: Second Point:

"A couple weeks back I tried to give WSL a try but everything was broken"

Did you run an Insider build? 14986 completed a batch of inotify related syscall improvements since we first added inotify support in 14328 (Details here: https://msdn.microsoft.com/commandline/wsl/release_notes)

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

#156

Post by nailer »

bitcrazed wrote: post #135
kej wrote: post #113

Earlier quoted context omitted.

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.

Hi - yes, we register the '.exe' extension with binfmt that then triggers WSL whenever a .exe is launched, allowing us to go find and spawn the requested Win32 process. If you just want to type `code ` (without the .exe), then you can create an alias that resolves to code.exe. Same for Notepad, etc. :)

(HN: bitcrazed is Rich, the person presenting in the video)

Hey Rich, can you (or colleagues) tell us any news on console? I get the vibe from Michael Niksa back in August [1] [2] there's a big changes happening that will fix readline-type stuff and I'd love to know more about this - I use ConEmu / Win32 SSH on Windows and it, was well as bash, seem to occasionally suffer from terminal-corrupting weirdnesses.

I'd love to know more about the causes, the fixes, whether the fixes will make it into Creators Update, etc.

[1] https://github.com/Microsoft/BashOnWindows/issues/111#issuec...

[2] https://github.com/Microsoft/BashOnWindows/issues/111#issuec...

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

#157

Post by bitcrazed »

nailer wrote: post #45
oblio wrote: post #40

Earlier quoted context omitted.

Does anyone know the roadmap for WSL? My guess is that WSL itself is still unstable right now and later on it won't really need a lot of updates. On top of it, the Ubuntu userland should be freely upgradable - I think.

> My guess is that WSL itself is still unstable right now Correct, it's currently a 'technology preview'.

Actually, it's currently a 'beta' feature while we continue to expand the breadth and depth of WSL's syscall implementation & supporting tools.

That said, WSL is now far, FAR more compatible with the majority of mainstream dev tools than it was in Anniversary Update or early Insider builds.

Don't take my word for it - I am biased ;) - but if you've not taken a look at WSL in 2017, you might be surprised by how much now works very well :)

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

#158

Post by avlasyuk »

isaac_is_goat wrote: post #153
nailer wrote: 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…

> - vt sequences fixed (so stuff like colored output, midnight commander, etc work and the terminal doesn't screw up) Does this mean tmux will work?

I currently have zero issues running tmux and bunch of other software in mintty/wsltty

https://github.com/mintty/wsltty

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

#159

Post by bitcrazed »

oblio wrote: post #37
wyldfire wrote: post #10

Not since Windows 2000 have I been so interested in an upgrade to a new Windows release. Only at work do I have to suffer through Windows, but this would make things much nicer there. I hope/pray that readline and/or editline work correctly on bash et al? Do Windows CI services like Appveyor support WSL? If so I would hope that deploying to windows for lots of high level software is relatively painless. Head scratche…

The Notepad line ending thing is kind of shameful but Notepad is ok for what it's supposed to do. It truly is a Note pad. It launches quickly and has a non-nonsense interface. It's not meant to be a programmer's editor. It never was, it never will be.

Agree 1000%! Was waiting for a comment like yours to help drive the case for some updates to Notepad to support NIX file endings, etc. ;)

Anyone running Win10 who wants to see Notepad support NIX file endings, PLEASE submit feedback via the feedback app - that way Notepad's owners get to see your pleas ;)

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

#160

Post by bitcrazed »

nailer wrote: post #52
wyldfire wrote: post #10

Not since Windows 2000 have I been so interested in an upgrade to a new Windows release. Only at work do I have to suffer through Windows, but this would make things much nicer there. I hope/pray that readline and/or editline work correctly on bash et al? Do Windows CI services like Appveyor support WSL? If so I would hope that deploying to windows for lots of high level software is relatively painless. Head scratche…

> The demo clearly shows the shebang line mashed in with the rest of the file contents. Demoer specifically comments that it's broken (obvously CR/LF differences) and they're fixing it. Also VS Code for Windows might have been a better example than Notepad but you get how this could be useful.

I was so split as to whether to show Notepad or Code, but figured that more people were aware of Notepad and would grok what I was trying to demo so went that way.

Plus it nicely demonstrates one of Notepad's key weaknesses to help drive awareness with the Notepad team ;)

Post reply on HN