-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
does freedos kernel support exfat? #36
Comments
I believe exFAT doesn't support 8.3 filenames so I'm not sure how it could work with any DOS, ideas anyone...? |
The kernel does not currently support exfat. ExFat has patented components by Microsoft, though the inclusion into the Linux kernel means that may no longer be a road block. I have not looked into it much, but it may be possible to have limited support - long filenames are big blocker and support for exfat may have to wait until the kernel (if ever) has native long filename support. I believe (again off memory and haven't looked into in a long while), the on disk format may be similar enough to FAT that we can optionally support it on builds with 64 bit integer support (OpenWatcom and GCC?). |
Does this mean only a fat-based LFNs, or are |
I will be looking into redirector extensions. No specific plans yet, but I would like to make long names as first class as possible while remaining compatible |
does exfat only accept long file name? I know it first. The most I hope is a command as driver like lfn driver, ntfs driver for dos. |
Since the last reply above, there has been improvements to doslfn.com for freedos (mainly from March-April 2022). So the latest stable FreeDOS build (of February 2022) may not issue latest update to doslfn.com if anyone downloads today say. So, is it possible to have support for exfat, even if there are restrictions imposed? |
FWIW it looks like the exFAT specification was published by Microsoft in August 2019, with the express purpose of getting good Linux support. |
does freedos kernel support exfat?
The text was updated successfully, but these errors were encountered: