This is brilliant. I might actually consider switching to Windows now. Both Arch and macOS have been getting on my nerves lately.
Switching from Arch (linux) to emulated linux (ubuntu) under Windows makes lot of sense. :-)
What’s New in Bash/WSL and Windows Console
81–90 of 251 posts
Re: What’s New in Bash/WSL and Windows Console
#82Earlier quoted context omitted.
I'm wondering if you are misguided here - and what Microsoft is working on right now is "Bash on Windows" - I.E. The console environment that people want to interact with when writing quick scripts, connecting to remote servers, maybe running a little bit of a local web instance. Speaking for myself, personally - if I want to run GNU/Linux software through the Linux ABI - I'm not going to be doing it on WSL - I'll do…
Bash is merely a Unix shell, one of many. What you describe is the GNU/Linux userland. They are working on people being able to execute unmodified Linux binaries on Windows machines through an Application Binary Interface that implements the Linux system calls and translates them into Windows system calls, among other things... and doing it in the most transparent way possible (not requiring specific builds of each s…
Everyone you're replying to understands how WSL and UNIX shells work. The error is on your part because you keep misunderstanding that the Windows executable one runs to invoke WSL is literally
C:\Windows\System32\bash.exe
Now you are welcome to rant about how the WSL "invoker" should be isolated from the POSIX shell, but that's very different from the point you keep raising and thus keep getting down voted for.
Re: What’s New in Bash/WSL and Windows Console
#83Earlier quoted context omitted.
I also remember the standardization process of OOXML. https://en.wikipedia.org/wiki/Standardization_of_Office_Open... I also think their current strategy could be the one you describe. We're at the Embrace phase. It's not sure that Extend will follow but I wonder what it could look like. Maybe it will be something convenient you can do in Linux only if you're running it inside WSL. Given how Linux is used it should b…
It's named like this because it is a subsytem of the NT kernel (hence the Windows subsystem part) that implements Linux system calls to run Linux applications (hence the for Linux part). Naming it the other way around ie Linux for Windows would imply that the Linux kernel is involved which is actually not the case at all.
If I say Firefox for Linux, I'm thinking the Linux kernel is involved, and that the application(Firefox) will be running on Linux.
If I say Firefox for Windows, I'm thinking the Windows kernel is involved, and that the application(Firefox) will be running on Windows.
So calling something $x for Linux, when it's actually running on Windows makes no sense.
Re: What’s New in Bash/WSL and Windows Console
#84Windows Console folk: any chance of tabs in the official terminal? Current Windows terminal options: - ConEmu: mainly excellent but a little dated - eg, the active tab color is hard to distinguish but it can't be changed, apparently due to maintainer's insistence it works on Windows XP. - Hyper: excellent but Ctrl C, Ctrl R etc broken in powershell. Adding tabs to the Windows console makes more sense than have a thir…
What I do is start sshd in WSL then ssh to @localhost from mobaxterm which is quite a nice (tabbed) terminal app. Works a treat, even with the free edition.
Re: What’s New in Bash/WSL and Windows Console
#85WOW. cmd can actually parse escape codes now AND run Linux scripts! What a time to be alive.
I've been using WSL for the last year now on my Surface Pro 4, and it has been nothing short of fantastic. This bridges a HUGE gap that made the MacBook attractive.
Re: What’s New in Bash/WSL and Windows Console
#86Still not any option to hide that ugly scrollbar and having unlimited buffer ? (like Gnome-Terminal)
I usually start sshd and use KiTTY to access WSL.
Re: What’s New in Bash/WSL and Windows Console
#87Windows Console folk: any chance of tabs in the official terminal? Current Windows terminal options: - ConEmu: mainly excellent but a little dated - eg, the active tab color is hard to distinguish but it can't be changed, apparently due to maintainer's insistence it works on Windows XP. - Hyper: excellent but Ctrl C, Ctrl R etc broken in powershell. Adding tabs to the Windows console makes more sense than have a thir…
This is a more modern wrapper around ConEmu: http://cmder.net
Cmder is ConEmu, just with a bunch of other stuff added to the download, including:
- Something called 'git-for-windows' which isn't actually git for Windows https://git-scm.com/download/win but unremarkable things like shell additions which give you git status in the prompt, and a not-particularly-good GUI.
- Clink (which is for cmd.exe).
I.e., this doesn't in any way address the limitations mentioned in the post you're replying to.
Re: What’s New in Bash/WSL and Windows Console
#88Earlier quoted context omitted.
Opinions are bound to differ so I do appreciate your point. I personally found Cygwin a nightmare to install, a nightmare to maintain, and a crash prone on every system I used it on since XP. While you're right that MinGW is only a subset, it did address the issues I raised with Cygwin which made it a better default environment for me most of the time; falling back to Cygwin on those occasions MinGW couldn't fulfil.…
I've also been using Cygwin for 10 years now. It's a bit annoying to install and update it, but it's far from a nightmare :) Just run the setup.exe, click through the 5-10 pages and that's about it. To update package, just run the setup.exe, click through the 5-10 pages and that's about it :) Or use this: https://github.com/transcode-open/apt-cyg (I haven't needed so far, but I've read good reviews about it) Regardin…
We can argue about whether "nightmare" is overstating the problem but let's be honest that it's easily more than just "a bit annoying". The installer took an hour on one system and the options in those 5-10 pages are far from user friendly. Sure it's stuff I can manage being a seasoned Linux sysadmin but frankly I've found installing ArchLinux (with it's deliberately anti-user approach) easier; never mind your more "mainstream" platforms like CentOS and Debian.
apt-cyg is pretty good though. However that didn't always work. But in fairness to apt-cyg this was about 18 months ago and I believe it was still marked as experimental at that time.
As for crashing, the issues I had last year were with the ssh-agent hanging. The only remedy was killing them from Windows then restarting Cygwin. Killing the process from within Cygwin (ie using `kill`) and then restarting the daemon weirdly left it hanging still. I've not used Cygwin since to see if that issue had been fixed.
Cygwin is one of those products that when it works, it works really well. But when it doesn't it can be hateful. Sadly I've run into a few edge cases that have left me with a sour taste after using it.
Re: What’s New in Bash/WSL and Windows Console
#89Earlier quoted context omitted.
Bash is merely a Unix shell, one of many. What you describe is the GNU/Linux userland. They are working on people being able to execute unmodified Linux binaries on Windows machines through an Application Binary Interface that implements the Linux system calls and translates them into Windows system calls, among other things... and doing it in the most transparent way possible (not requiring specific builds of each s…
Everyone you're replying to understands how WSL and UNIX shells work. The error is on your part because you keep misunderstanding that the Windows executable one runs to invoke WSL is literally C:\Windows\System32\bash.exe Sure, once you've started bash you can then probably switch to whichever shell you want afterwards (NOTE: I say that but I've not tested to see if other shells work). But to use your WINE example,…
When I say bash, I am referring to GNU bash, the shell that has existed for decades now on Linux, BSD, macOS, Solaris and an endless list of other operating systems.
I do not care if Microsoft couples their ABI and the shell and decides to call that "bash". GNU bash will continue to be what it has been for decades now.
I also do not care if a lot of people want to take the entire GNU/Linux userland and decide to call that "bash". That is not bash either, and will never be no matter how many people insist on it, not even Microsoft.
bash is GNU Bash, a project that you can learn from here: https://www.gnu.org/software/bash/
Finally, if Microsoft decided to couple bash with WSL, think that they went through the effort of replicating most Linux system calls. Having bash as a default shell is not a technical requirement on their part. Maybe now it will be, for backward compatibility reasons, but that's a different issue.
Then, you can downvote and insult all you want, that won't make you right.
Re: What’s New in Bash/WSL and Windows Console
#90Ok, this is awesome, if everything works as advertised. I have been mostly a Linux user for quite some time - at least on my own computer, clients always have Windows. But this year I bought a Surface Pro as a secondary device. I first evaluated WSL and really liked it, but I switched to Hyper+Git Bash because networking in node.js was not working properly, and because I could not start Windows programs from the comm…
Unfortunately, I found Windows command-line interop isn't as useful as I had hoped. You can start Windows executables, but you can't kill them: ctrl-c gets you your shell back, but the executable is still running in the background, headless. See: https://github.com/Microsoft/BashOnWindows/issues/1614
And since USB ports aren't mapped into WSL, I have to use a Windows program to talk to them.
Besides this hiccup, everything else seems to work great.