Filesystem

From Just Solve the File Format Problem
(Difference between revisions)
Jump to: navigation, search
(Networked and cloud filesystems)
(Single-system filesystems)
Line 48: Line 48:
 
* [[HFS+]]
 
* [[HFS+]]
 
* [[HPFS]] (OS/2 native file system)
 
* [[HPFS]] (OS/2 native file system)
* [[ISO 9660]]
+
* [[ISO 9660]] (optical discs)
 
* [[JFFS2]]
 
* [[JFFS2]]
 
* [[LanyFS]] (Lanyard Filesystem)
 
* [[LanyFS]] (Lanyard Filesystem)
Line 68: Line 68:
 
* [[squashfs]]
 
* [[squashfs]]
 
* [[UCSD p-System Filesystem]] (UCSD Pascal)
 
* [[UCSD p-System Filesystem]] (UCSD Pascal)
* [[UDF]]
+
* [[UDF]] (optical discs)
 
* [[UFS]] (Unix Files System, Solaris and BSD)
 
* [[UFS]] (Unix Files System, Solaris and BSD)
 
** [[UFS2]]
 
** [[UFS2]]

Revision as of 01:48, 25 April 2014

File Format
Name Filesystem
Ontology

{{{caption}}}

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.

Contents

Single-system filesystems

(How files are organized on one system or device, 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 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.)

Format details

Links

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox