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?
[deleted]
Bash and Windows Subsystem for Linux Demo [video]
181–190 of 316 posts
Re: Bash and Windows Subsystem for Linux Demo [video]
#182Any 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.
The way I solved the terminal emulator shortcommings is this: Install a gtk-based terminal emulator with gtk/gnome dependencies on you ubuntu subsystem and run it with `DISPLAY=localhost:0.0` environment variable. This works if you run XServer Client on your Windows side. I use XcSrv and pantheon-terminal.
Konsole or yaquake are far better options
Re: Bash and Windows Subsystem for Linux Demo [video]
#183Earlier 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.
NT is basically OpenVMS.
So it's about a decade more advanced than UNIX. Put like that, moving to UNIX would be a regression, but not a huge one.
The Linux kernel is of about the same vintage as NT, though. And it's had a lot more work and public review done on it.
Re: Bash and Windows Subsystem for Linux Demo [video]
#184Earlier quoted context omitted.
https://www.gnu.org/software/fileutils/fileutils.html
That's not the `file` command, it's tools for working with files: chgrp, chmod, mv, rm, etc. These have all been folded into coreutils these days, which also does not contain the `file` utility. Ubuntu and practically all other Linux distros ship BSD's file utility.
My apologies, I mis-spoke. I've flogged myself mercilessly and shall not make that same mistake again ;)
Re: Bash and Windows Subsystem for Linux Demo [video]
#185Can it run apps inside Wine? Windows emulating Linux syscalls so that Wine can emulate Windows syscalls.
WINE does not (iirc!) emulate syscalls, it rather provides its own user32.dll and a host of other libraries which then call Linux userland (e.g. DirectX->OpenGL) or syscalls (files, I guess).
Re: Bash and Windows Subsystem for Linux Demo [video]
#186I wonder when it will be RTM (release to manufacturing => stable)
I think it's coming in the Windows 10 Creators Update in April: http://www.theverge.com/2017/1/2/14146182/microsoft-windows-...
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.
Re: Bash and Windows Subsystem for Linux Demo [video]
#187Earlier 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. :)
I'm a big fan of this new feature, enough that I wrote and released some open source code to launch applications before this was possible. Mine's a hack, pure and simple but it worked to fill in the gap but I'm glad to not need it anymore. Thanks! https://github.com/jaegerpicker/Rockhopper
Re: Bash and Windows Subsystem for Linux Demo [video]
#188Earlier quoted context omitted.
Re: Elixir The Erlang/OTP 19.x releases are still broken because of some missing system calls. They seem to have an incoming fix though: https://github.com/Microsoft/BashOnWindows/issues/613 It's great that they keep open conversations like this for issue tracking and hopefully April will be working 100% by then.
For this reason, whenever I try to develop anything on Windows, especially systems related stuff, I will do so in a VM. I may develop a test suite and try running it on Windows, but the Windows Linux Subsystem will never be reliable to me, until it aims to guarantee 100% compatibly.
Bash and Windows Subsystem for Linux is a band-aid solution for a fundamental problem for Microsoft: Linux tooling and kernel are IT industry standards.
Re: Bash and Windows Subsystem for Linux Demo [video]
#189Earlier quoted context omitted.
Output from `bash --version` on macOS: `GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin16) Copyright (C) 2007 Free Software Foundation, Inc.` that's a 10yr old bash and there's barely any shell magic that you can do on Linux that won't work on macOS. And since by far most devs use macOS, most binaries support at least the macOS version of bash. All in all, no need to worry :p
Output from macOS Sierra: GNU bash, version 4.4.0(1)-release (x86_64-apple-darwin16.0.0).
That's your Homebrew bash..
Re: Bash and Windows Subsystem for Linux Demo [video]
#190Earlier 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. :)
WSL is great, I use it every day and am very much looking forward to the next update.
Regarding future work, are there any plans to make the emulated Linux filesystem usable in the rest of Windows e.g. via a drive mapping?