FAT32 / NTFS
Out of context: Reply #1
- Started
- Last post
- 14 Responses
- protoculture0
http://www.devhood.com/messages/…
Basically FAT32 is dead, NTFS is good.
reliability -this is done through it being a jornalling file system so that if there is a problem it can roll back the changes to the last comit. It also supports hot fixing so if a bad cluster is found during operation it can take care of it without the app noticing. And it doesn't have any special locations on the HDD like FAT32.
security - this is done with ACLs, owner of files
hard Links - two different filenames, which can be located in different directories, point to the same data.
reparse points - directory junctions and volume mount points
disk quotas
encryption- by way of EFS
streams-While I havn't seen this used it means multiple data globs can be under one filename. For example:
echo text>program:source_file
moresmaller clusters - less wasted disk space
compression at the cluster level
sparse files - programs can create very large files, but consume disk space only as needed
scales larger - can go up to 2^64 bytes (16 exabytes or 18,446,744,073,709,551,616 bytes)
unicode file names
distributed link-tracking