The TTY device and the path of I/O from bash.exe to /bin/bash

[ionescu007]

The TTY device and the path of I/O from bash.exe to /bin/bash

[fpqc]

I convinced Russ Alexander to document this properly in a blogpost, so we're all good =].

[ionescu007]

Hey @fpqc I think version 1.2.0 of LxLaunch will answer most of your questions. As you can see, UTF-8 is now native to the console code in Windows, by using SetConsoleCP(CP_UTF8). The VT-100 support is also new and native to the Windows console, and achieved by using the VT100_EMULATION console mode.

The ttys are basically handled (hah!) by creating a pipe on the WIndows and Linux side, and setting that pipe as the Linux standard-in. ADSS IPC will take care of duplicating that into a linux pipe/tty on the other side. Meanwhile, we then wait for input on the Windows STDIN handle. When input is received, we read the input character, and simply write it back out on the pipe, which Linux will now receive as console input.

[fpqc]

Nifty! Thanks, will look at the sourcecode again.