3 ms·
> So even if there was an NT API fork syscall You can do it with NtCreateProcess: https://groups.google.com/d/msg/microsoft.public.win32.programmer.kernel/ejtH
by pcwalton 10y ago
> So even if there was an NT API fork syscall
You can do it with NtCreateProcess: https://groups.google.com/d/msg/microsoft.public.win32.programmer.kernel/ejtHCZmdyaI/k0D0Jinx9KwJ https://groups.google.com/d/msg/microsoft.public.win32.progr...
(The Win32 userland won't understand what you did, but you can still do it.)
- xorblurb 10y agoWell, you can do it on some versions of Windows. On Windows 10, and even future version of Windows 10, not so sure...
- lmm 10y agoWindows 10 is still windows NT. The NT native API is widely used these days. It would be a huge departure for MS to stop supporting it in future versions of windows.
- xorblurb 10y agoMost parts of the NT API have never been officially documented, officially supported, stable (in the "won't change" meaning), and the tiny parts that have actually been documented come with caveats that they are susceptible to change. Supporting fork through the NT API forever makes no sense if there are no users anymore. They could continue to do it for no specific reason, just because fork is internally needed by WSL for example, and so because it is easy to export the capability through the NT API, but I really don't see why they would necessarily do that.
- lmm 10y agoMS has historically maintained compatibility with even undocumented APIs. Of course that could change.