Timeline for Use or access large NTFS cluster sizes (e.g. 2048 kb / 2049 kb / 2M or 2MB) in an Android (or Linux) OS?
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jan 14, 2022 at 15:36 | history | edited | Andrew T.♦ | CC BY-SA 4.0 |
copyedit
|
Jan 14, 2022 at 6:47 | answer | added | Ryan Feeley | timeline score: 0 | |
Jun 22, 2020 at 10:46 | comment | added | Eliot | Cheers, @IrfanLatif, I didn't think it'd be as simple as bloody closed source horribleness. So the irony that routers, TVs, etc, won't recognise any other formats than FAT32 or NTFS (ie not exFAT), coupled with no decent cluster/file allocation methods in other file systems means that I'm basically banjaxed for large file storage ... would that be about right? | |
Jun 20, 2020 at 16:37 | comment | added | Irfan Latif | Same was the case with exFAT, but now MS open-sourced it a few months back. Some details here: android.stackexchange.com/a/223592/218526 | |
Jun 20, 2020 at 16:37 | comment | added | Irfan Latif | NTFS is Microsoft's proprietary filesystem. It means that unauthorized entities don't have the right to include an open source implementation of the driver in their products. That's why NTFS has never been fully supported in Linux/Android kernel. So if it works on your device, it's a bonus. If it doesn't, you cannot blame. The current in-kernel driver implementation (not being developed for years) is buggy and supports read-only mounting. There are FUSE implementations of NTFS drivers (which I've been using in Linux distros for years) and many OEMs/developers include that in their ROMs. | |
Jun 20, 2020 at 14:23 | history | edited | Eliot | CC BY-SA 4.0 |
added 55 characters in body; edited title
|
Jun 20, 2020 at 14:15 | review | First posts | |||
Jun 24, 2020 at 9:32 | |||||
Jun 20, 2020 at 14:15 | history | asked | Eliot | CC BY-SA 4.0 |