View Single Post
Old 11-03-2010, 03:58 PM   #3
mgmueller
Member Retired
mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.mgmueller ought to be getting tired of karma fortunes by now.
 
mgmueller's Avatar
 
Posts: 3,308
Karma: 13024950
Join Date: Nov 2008
Location: Augsburg (near Munich), Germany
Device: 26 Readers, 44 Tablets
Quote:
Originally Posted by twobits View Post
It is not a limit of memory cards on Android but a limit of the FAT32 file system itself. The `solution` usually is to split the files into parts and have
the software know to glue it back together again for you.

Ext3 is another filesystem, why is that 'even worse'? The BSD FFS would also work, as would NTFS. Of course the linux kernel needs to be built to support those file sytems, or you need a loadable module for them, which is why you saw ext3 mentioned as that is in almost all kernel builds. None of these are ideal for use with flash cards anyway, ideally we would all be using some type of JFS with them.
Re. "Ext3" = "Even worse" because I find it extremely inefficient and even unprofessional, to claim those units being multimedia devices as well and not even being able to handle the easiest of tasks.
I wouldn't mind, if the system automatically would use an adequate file system. But doing it manually? That's why iOS (unfortunately) still shines...

Last edited by mgmueller; 11-03-2010 at 04:00 PM.
mgmueller is offline   Reply With Quote