From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
Line 80: Line 80:
* [[TR-DOS filesystem]] (ZX Spectrum)
* [[TR-DOS filesystem]] (ZX Spectrum)
* [[UCSD p-System Filesystem]] (UCSD Pascal)
* [[UCSD p-System Filesystem]] (UCSD Pascal)
* [[UFS]] (Unix Files System, Solaris and BSD)
* [[UFS]] (Unix File System, Solaris and BSD)
** [[UFS2]]
** [[UFS2]]
* [[Universal Disk Format]] (UDF) (optical discs)
* [[Universal Disk Format]] (UDF) (optical discs)

Revision as of 01:49, 12 July 2019

File Format
Name Filesystem


Filesystems are Electronic Formats that are a prerequisite to being able to read any file off a digital medium — you have to be able to mount the filesystem, and thus read it, in order to be able to read a file.


Single-system filesystems

(How files are organized on one system, device, or medium, such as a disk, tape, or flash memory; see next category for networked and cloud filesystems. Of course, any filesystem can be made available on a network to remote devices, but these are the native filesystems present on the storage device/medium itself.)

Networked and cloud filesystems

(Used to make files available to multiple systems over a local or wide area network, including "on the cloud" via the Internet; systems access files through a protocol or API. The low-level storage details, usually concealed from end users and even most developers, may be within one or more of the single-device filesystems above, and the networked/cloud filesystem is generally defined independently of such details and might have very different characteristics and rules as to how the files are named, addressed, and structured.)

Virtual filesystems

Other / Misc.

File content signature

(used to match files to a hash table or similar system in order to detect duplicates, help find specific files when their exact location is unknown, handle distributed networked filesystems, etc. See also Error detection and correction.)

Format details


Personal tools