Hacker News Reader

Maybe the NT kernel could gain a linux-syscall-compatible layer, instead of adding compatibility in userspace. That would allow for compatible (same-arch) binaries!

(EDIT: this would also require ELF loaders and all kinds of other good stuff, but still a possibility IMO)

View on HN

Guess what, there actually is an ELF loader in the compatibility layer: https://pbs.twimg.com/media/CcTwejAUEAAq_jR.jpg

One (more) thing that is conspicuously glossed over is non-ELF executables. We've seen Win32 programs invoking ELF64 binaries demonstrated. And of course the Windows NT Linux subsystem already "knows" that it's a Linux subsystem process when a program comes to exec() a script, and doesn't have to worry about checking binary formats over fork() because the program image doesn't change. But missing so far has been Win32 programs invoking Linux executable scripts, that have #! lines.

> Maybe the NT kernel could gain a linux-syscall-compatible layer [...]. That would allow for compatible (same-arch) binaries!

What makes you think "maybe"? This is (reportedly) exactly what's happening. What did you infer was happening from the headlined article?

Reply on news.ycombinator.com