2 ms·
> (mmap's created could only be as large as the file's current size as in Windows, while Linux/BSD semantics allows for a mmap larger than the file that's usabl
by xeonmc 1y ago
> (mmap's created could only be as large as the file's current size as in Windows, while Linux/BSD semantics allows for a mmap larger than the file that's usable without constant remapping as the file grows).
I thought you could do it using ntdll functions, no?
https://www.jeremyong.com/winapi/io/2024/11/03/windows-memory-mapped-file-io/ https://www.jeremyong.com/winapi/io/2024/11/03/windows-memor...
- whizzter 1y agoGood to know, still the obscureness of this function or semantics led WSL1 to be incompatible for a long time (Also skimming this article touches upon some 0-sized mappings being an issue?). Regardless this led WSL1 to have fatal incompatibilities for a long time, iirc basic stuff like the rpm system or something similarly fundamental for some distros/languages relied on it. And once WSL2 existed people just seems to have gone over.