Windows 9x Subsystem for Linux

Original Article ↗ Hacker News Discussion ↗

Legacy / Industrial Use Cases

  • Several commenters actively maintain 9x/XP-era systems for industrial SCADA, radio transmitters, paging systems, ATMs, and emergency services equipment.
  • Main constraints: bespoke hardware with only DOS/Win9x drivers and software that cannot be ported.
  • WSL9x is seen as potentially useful in such locked‑in environments, though concrete production workflows are not fully explored in the thread.

What WSL9x Actually Does

  • Clarified multiple times: Windows 9x boots first; a modern Linux kernel (e.g., 6.19) then runs cooperatively in ring 0 alongside the Win9x kernel.
  • The two kernels share the machine; if either crashes, the whole system goes down.
  • This differs from an earlier project (doslinux), where Linux actually owns the machine and DOS is effectively hosted inside it.

Architecture Context: 9x vs NT

  • NT has long supported multiple “subsystems” (POSIX, OS/2, Win32), which inspired WSL1’s design.
  • 9x is DOS‑derived and historically lacked that native multi‑personality architecture, so doing this on 9x is perceived as uniquely hacky and impressive.
  • Some explanations highlight that 9x does use protected mode and memory protection, but for compatibility and lack of security it left things very open.

Naming Confusion (“Windows Subsystem for Linux”)

  • Long sub‑thread about how “Windows Subsystem for Linux” seems backwards; many instinctively read it as “Linux subsystem that runs Windows.”
  • Explanations: legal constraints on starting product names with other companies’ trademarks; Microsoft precedent for “Subsystem for X” naming; marketing desire to lead with “Windows.”
  • Similar confusion arises for this project’s name (is it Windows on Linux or Linux on Windows 9x?).

Comparisons to Other Solutions

  • Prior art mentioned: CoLinux, flinux, Cygwin, Interix/SUA, Win4Lin, VMs (VMware, VirtualBox, Virtual PC).
  • Debate over “correct” approach:
    • Some favor Cygwin/MSYS2 for native POSIX on Windows but note DLL hell, slow forks, incomplete signal semantics, and distribution issues.
    • Others argue WSL‑style kernel integration scales better since app authors don’t need to port/recompile.

Retro Web & Nostalgia

  • Multiple tangents on browsing the modern web from Win9x or Pentium‑class machines: proxies that render remotely (BrowserBox), KernelEx + modern-ish browsers, Gemini/Gopher gateways.
  • Many view WSL9x primarily as a delightful, almost absurd hack rather than something broadly “needed,” and celebrate that it was done without AI assistance.