bitcrazed

10 ms·

61.
by bitcrazed 10y ago
We do implement (at least some of) prctl(), but not seccomp() yet. If this is important to you, please file a bug and the team will triage & respond. https://github.com/microsoft/bashonwindows
62.
by bitcrazed 10y ago
No - we won't be out of Beta in Creator's Update ... but we'll be close. There are a few last remaining things we need to enhance & modify before we feel comfortable before taking off the beta label.
63.
by bitcrazed 10y ago
My apologies, I mis-spoke. I've flogged myself mercilessly and shall not make that same mistake again ;)
64.
by bitcrazed 10y ago
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.
65.
by bitcrazed 10y ago
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:&#x2F
66.
by bitcrazed 10y ago
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.
67.
by bitcrazed 10y ago
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 f
68.
by bitcrazed 10y ago
I'll just leave this here: https://blogs.msdn.microsoft.com/commandline/2016/06/08/tmux... :)
69.
by bitcrazed 10y ago
Can't lead with someone else's trademarked product name. You'd be amazed how complex and difficult product naming can be ;) Just be glad we didn't call it WSRPGLCB - Windows Subsystem for Running POSIX, GNU and Linux Com
70.
by bitcrazed 10y ago
Yes - IO perf is not yet where we want it to be. We have some improvements coming in Creator's Update and more substantial improvements planned in future releases, once we've completed some work with the NT kernel filesystem team.
71.
by bitcrazed 10y ago
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 dri
72.
by bitcrazed 10y ago
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 t
73.
by bitcrazed 10y ago
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 main
74.
by bitcrazed 10y ago
@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 suppor
75.
by bitcrazed 10y ago
@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 t
76.
by bitcrazed 10y ago
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
77.
by bitcrazed 10y ago
Yes, in Insider build 14965, we added NETLINK_ROUTE's RTM_GETLINK and RTM_GETADDR support which enabled ifconfig and network connection enumeration support : https://msdn.microsoft.com/commandline/wsl/release_
78.
by bitcrazed 10y ago
You don't HAVE to nuke & reinstall your Linux environment to get up to 16.04 - we also support in-place upgrades too ... so long as you're running a Windows Insider build >= 14951 HTH
79.
by bitcrazed 10y ago
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 <filespec>` (without the
80.
by bitcrazed 10y ago
To be fair ... "UAC is always-in-your-face about everything..." Not true: UAC only pops up for apps that need to access a file/registry key, etc. that affects system-wide behavior "... often unexpectedly - it hijacks you
81.
by bitcrazed 10y ago
You called? ;) Also take a look at our Command-line blog ( https://blogs.msdn.microsoft.com/commandline ) for LOTS more about Console & Bash/WSL, including the page where I pull together our various learning resource
82.
by bitcrazed 10y ago
Yeah, native dependencies in Ruby Gems, node modules, etc., are the bane of the open-source developer. This is why we built the Windows Subsystem for Linux: Sometimes, you've just gotta run native Linux code or code that expects a genu
83.
by bitcrazed 10y ago
Hey there: PM for Windows Console & Bash here: If you're running Win10 Anniversary Update (AU), know that this was our first formal release of the Windows Subsystem for Linux (WSL) and was, as we made very clear prior to release, m
84.
by bitcrazed 10y ago
Hi. PM for Bash & Windows Console here: Glad you're digging Bash & WSL :D May I ask which Win10 build you're running. If you're on Win10 AU (build 14393.x), you're not yet seeing the huge raft of changes that we&
85.
by bitcrazed 10y ago
For those who are interested, the next version of Windows Internals is available for pre-order from Amazon :) https://www.amazon.com/Windows-Internals-Part-architecture-m... Oh, and @EvanAnderson - you might want to take a
86.
by bitcrazed 10y ago
As I am sure you can imagine, untangling the long-path limitation throughout the OS code, throughout RTL libraries, 3rd party libraries, .NET Framework & CLR, Windows Shell, etc. is a detailed, time-consuming process. This was never goi
87.
by bitcrazed 10y ago
To be fair, VSCode is open source so you could go look if you were interested: https://github.com/Microsoft/vscode
88.
by bitcrazed 10y ago
Oh, and just so we're all clear, if there are any problems uncovered in this implementation, we can all blame @felixrieseberg ;) :D
89.
by bitcrazed 10y ago
The primary motivation for adding the SYMBOLIC_LINK_FLAG_ALLOW_UNPRIVILEGED_CREATE flag is to not disrupt the behavior of existing code. Because of pre-existing behavior, existing apps are likely to be built to assume that symlinks cannot b
90.
by bitcrazed 10y ago
PM for Windows Console & Bash on Windows here: For what it's worth, you might also consider running "Bash on Windows" atop the new "Windows Subsystem for Linux" (WSL): https://msdn.microsoft.com/

More ›