View Single Post
  #6  
Old 04-11-2017, 19:16
Mkz Mkz is offline
Friend
 
Join Date: Jan 2002
Posts: 98
Rept. Given: 0
Rept. Rcvd 2 Times in 2 Posts
Thanks Given: 5
Thanks Rcvd at 25 Times in 17 Posts
Mkz Reputation: 2
For me, the 2 main limitations it currently has are:

- Not possible to pipe between Lxss and non-Lxss processes, or even between them unless triggered from within the Bash console itself:

Code:
C:\>bash -c 'ls -l /mnt/c' | bash -c 'less'
Error: 0x80070057

C:\>dir C:\ | bash -c 'less'
Error: 0x80070057
- Tools such as ProcessExplorer are basically unable to inspect anything about the spawned processes under Bash (pico processes, I think).
The whole "Bash" installation is under %LOCALAPPDATA%\Lxss\ but PE shows the running pid and process names and not much more. I believe Process Hacker has slightly more info but still extremely limited, as the kernel itself doesn't provide the info.

For these reasons, when using Windows I mostly rely on Cygwin for the linux mixed-world stuff, as interoperability is far greater at least for the time being. And of course a full blown Ubuntu or CentOS for native environment when needed.
Reply With Quote