3 ms·
WSL1 tries to do too much. WSL2 tries to do even more. msys2 mostly cares about running your textmode software. For example, someone talked about processes. H
by 1996 6y ago
WSL1 tries to do too much. WSL2 tries to do even more.
msys2 mostly cares about running your textmode software.
For example, someone talked about processes. Here's all that I see in msys2:
# ps xwau
PID PPID PGID WINPID TTY UID STIME COMMAND
480 479 480 18796 pty1 197611 14:13:13 /usr/bin/bash
479 1 479 16872 ? 197611 14:13:12 /usr/bin/mintty
1118 480 1118 16496 pty1 197611 17:00:32 /usr/bin/ps
Most of the time, I don't need to access Windows processes - and if I do, data can be exchanged through a file.
- shawnz 6y agoWSL1 also doesn't show windows proceses in 'ps', only the WSL processes. For example: shawnz@ShawnsPC:/mnt/c/Users/shawn$ ps xwau USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 8936 184 ? Ssl Nov17 0:00 /init root 6 0.0 0.0 8936 96 tty1 Ss Nov17 0:00 /init shawnz 7 0.0 0.0 18588 2708 tty1 S Nov17 0:00 -bash shawnz 252 0.0 0.0 18880 1984 tty1 R 18:04 0:00 ps xwau
- 1996 6y agoBut in your example, I can already see you have a init system and multiple users - neither of which will be needed in most cases.
- shawnz 6y agoThe "init" process is just a stub used by WSL, it is not a "real" init system. And Cygwin also allows the creation of multiple users within the Cygwin environment, doesn't it? It's just a matter of populating /etc/passwd. If you want to use WSL1 with a single user then you could just set the default user to root.