3 ms·

What happened to NTSYNC? https://lore.kernel.org/lkml/f4cc1a38-1441-62f8-47e4-0c67f5ad1d43@codeweavers.com/T/#u https://lore.kernel.org/lkml/f4cc1a38-1441-62f8-

• elynl 6y ago
  It's still a thing! kernel: https://repo.or.cz/linux/zf.git/shortlog/refs/heads/winesync https://repo.or.cz/linux/zf.git/shortlog/refs/heads/winesync wine: https://repo.or.cz/wine/zf.git/shortlog/refs/heads/fastsync2 https://repo.or.cz/wine/zf.git/shortlog/refs/heads/fastsync2 They decided to rename it since the kernel maintainers don't want NT interfaces and having NT in the name doesn't help
  • Cloudef 6y ago
    Thats good to hear. Darling devs also went with kernel module approach. Its weird wine devs did not do the same until now. Wineserver is nice but as we see, its sometimes impossible to do accurate emulation of some apis there. https://docs.darlinghq.org/internals/basics/system-call-emulation.html https://docs.darlinghq.org/internals/basics/system-call-emul...
    • elynl 6y ago
      I guess they didn't go down that path in order to increase portability. A good chunk of crossover (wine with paid support) customers run macOS.
      • Cloudef 6y ago
        Thats a good point