Re:Why is the DOS path character "\"? (2005)
by tobias3 on Friday February 26, 2021 @05:27AM
(#26273332)
No, like io_uring which Linux got in 2019 and still doesn't cover everything yet (e.g. currently mkdirat() is being added). It also often falls back to a kernel-level thread pool, since many e.g. file systems don't implement async IO.
[ Parent
| on HN ]
Annoyingly IOCP didn’t cover everything as well - for example, CreateFile of all things!
Re:Why is the DOS path character "\"? (2005)
by scaladev on Friday February 26, 2021 @05:44AM
(#26273431)
>since many e.g. file systems don't implement async IO
If we're picking on Linux here we should also mention that this issue cannot exist on Windows because it doesn't support anything else besides NTFS and a couple of options dating back to the 18th century or so.
Oh, and WinFS, of course, F being short for future which is like the horizon, or the communism, always out there just a month or two away.
Re:Why is the DOS path character "\"? (2005)
by tinus_hn on Friday February 26, 2021 @05:51AM
(#26273474)
You can actually for example get drivers for APFS for Windows from third party vendors.
Re:Why is the DOS path character "\"? (2005)
by scaladev on Friday February 26, 2021 @05:54AM
(#26273489)
Sure, and there are third party drivers for ext* and btrfs and god knows what else… but we're talking about official support here, I think. You can find all sorts of craziness in out-of-tree patches for the Linux kernel.