Greg Freemyer wrote:
ntfs-3g has been supported since 10.3. It provides full ntfs read/write.
Greg
How stable and how fast is it? How well does it handle the esoteric NTFS stuff not in Linux -- like the access lists and such? Is this one of the drivers that runs MS-NTFS drivers in a compatibility mode? I was wondering -- MS supposedly opened up alot of their specs -- was NTFS one of them? Also -- I was wondering what people (if anyone) is thinking about doing for compatible filesystems for USB-thumb/flash drives? Wasn't there a 4G limit on FAT32?...or is that just XP creation? Still with a 32-bit FAT (1G), isn't it pretty much the case that the FAT's themselves need to be resident in memory all at once to maintain consistency? That sorta limits how big volumes might get. With a 32-bit FAT, all full, that would take what -- (assuming signed 32-bit integers, that's only 2-G blocks. I'm not sure what size blocks people are willing to go with -- but assuming an 8-K block size, we're still limiting volume sizes to 16-terabytes -- WITH a 2G FAT table -- which would be huge -- if not entirely impractical in practice. Just *guessing*, but anything more than maybe 8-16M of FAT table would be stretching FAT, using that as a limiting factor, that constraings FAT volumes to 8K(8M-16M)=64G-128G, which is still 3-4 years away for mem drives (8G chips were available for cameras a year ago...so doubling every every year would be 64G in 2, every 18 months=3 years. But main prob with FAT32 is the 2G file-size limitation. I started hitting that 2-4 years ago, at least. The other problems -- that large FAT size that ideally needs to fit in memory, might be redone to allow partial mappings -- but I think the device would need to be locked while a process is updating the FAT map -- certainly not ideal. I know there are plenty of file systems on linux -- but virtually none of them are ported to Win32, and I can't see NTFS becoming a defacto-industry standard as long as MS sits on it as proprietary. Already, on newer electronics w/cheap ROM's (phones), some are limited to using 4G chips because of addressability problems. Perhaps ideally, such a file system would get input from flash-ram designers to optimize file system operations with what's optimal for HW now -- and is likely to be optimal in the future. Anyone thinking about this stuff? linda -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org