| Revision as of 21:21, 12 August 2005 editClaunia (talk | contribs)Extended confirmed users576 editsNo edit summary | Latest revision as of 18:12, 27 June 2024 edit undoBoleyn (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, New page reviewers, Pending changes reviewers307,295 edits needs ref | ||
| (27 intermediate revisions by 19 users not shown) | |||
| Line 1: | Line 1: | ||
| {{Unreferenced|date=December 2009}} | |||
| This is the glossary of the |
This is the glossary of the ''common ] features'' table. | ||
| The intention of this table is to |
The intention of this table is to provide an at-a-glance list of features and specifications for each filesystem. | ||
| ==Inventor== | ==Inventor== | ||
| List the names of those credited with the design of the filesystem specification. This should not include those responsible for writing the implementation. | |||
| ==Name== | ==Name== | ||
| The full, non abbreviated, name of the filesystem itself. | |||
| ==Native |
==Native operating system== | ||
| The name of the operating system in which this filesystem debuted. | |||
| ==Partition identificator== | ==Partition identificator== | ||
| The partitioning scheme and marker used to identify that a partition is formatted to this filesystem. | |||
| Here comes the partition identificator, along with the partitioning scheme of it. | |||
| ==Bad sector allocation== | ==Bad sector allocation== | ||
| Describe how the filesystem allocates and isolates ]s. | |||
| ==File allocation== | ==File allocation== | ||
| Describes how the filesystem allocates sectors in-use by files. | |||
| ==Directory structure== | ==Directory structure== | ||
| Describes how the subdirectories are implemented. | |||
| ==Namespace== | ==Namespace== | ||
| Lists the characters that are legal within file and directory names. | |||
| ==Maximum filename size== | ==Maximum filename size== | ||
| The maximum number of characters that a file or directory name may contain. | |||
| ==Maximum files== | ==Maximum files== | ||
| The maximum number of files the filesystem can handle. | |||
| ==Maximum volume size== | ==Maximum volume size== | ||
| The maximum size of a volume that the filesystem specification can handle. This may differ from the maximum size an operating system supports using a given implementation of the filesystem. | |||
| NOTE: This is as the specification says not as any operating system implements this. | |||
| ==Dates handled== | ==Dates handled== | ||
| What type of dates and times the filesystem can support, which may include: | |||
| They can be: Creation, Access, Modified or Changed | |||
| ===Creation date=== | |||
| This is the date the file was “created” on the volume. This does not change when working normally with a file, e.g. opening, closing, saving, or modifying the file. | |||
| ⚫ | |||
| ===Access date=== | |||
| This is the date when the file was last accessed for read. | |||
| This is the date the file was last accessed. An access can be a move, an open, or any other simple access. It can also be tripped by Anti-virus scanners, or Windows system processes. Therefore, caution has to be used when stating a “file was last accessed by user XXX” if there is only the “File Access” date in NTFS to work from. | |||
| ⚫ | === |
||
| This is the date when the file was last accessed for write, no matter if no write was really made. | |||
| === |
===Modified date=== | ||
| This date as shown by Windows there has been a change to the file itself. E.g. if a notepad document has more data added to it, this would trip the date it was modified. | |||
| This is the date when anything related with the file, like attributes, ACLs, filename, etc, is modified. | |||
| ⚫ | ===Changed date=== | ||
| The date and time related attributes were modified. This may include ] and the file/directory name. | |||
| ===Backed-up date=== | |||
| ⚫ | The date and time when the file was last backed up. | ||
| ==Maximum date== | ==Maximum date== | ||
| The maximum year that can be handled by the filesystem, as per the specification. | |||
| ==Attributes== | ==Attributes== | ||
| Lists the basic file attributes available. | |||
| ==Named streams== | ==Named streams== | ||
| Determines if the filesystems supports multiple data streams. ] refers to these as alternate data streams, ] as extended attributes and ] calls them forks. | |||
| This describes if the filesystems supports more data streams than the normal one. | |||
| This is how ] calls them, ] calls them Extended Attributes and ] calls them forks. | |||
| ==Per-volume compression== | ==Per-volume compression== | ||
| Does the filesystem support real-time transparent compression and decompression of an entire volume. | |||
| ==Per-volume encryption== | ==Per-volume encryption== | ||
| Does the filesystem support real-time transparent encryption and decryption of an entire volume. | |||
| ==Per-file compression== | ==Per-file compression== | ||
| Does the filesystem support real-time transparent compression and decompression of individual files. | |||
| ==Per-file encryption== | ==Per-file encryption== | ||
| Does the filesystem support real-time transparent encryption and decryption of individual files. | |||
| ⚫ | ==Access control lists== | ||
| Does the filesystem support multi-user access control lists (ACLs). | |||
| ==References== | |||
| {{reflist}} | |||
| {{DEFAULTSORT:Common Filesystem Features}} | |||
| ⚫ | ==Access |
||
| ] | |||
| This describes if the filesystem supports multiuser Access Control Lists | |||
Latest revision as of 18:12, 27 June 2024
 | This article does not cite any sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Common filesystem features" – news · newspapers · books · scholar · JSTOR (December 2009) (Learn how and when to remove this message) |
This is the glossary of the common filesystem features table.
The intention of this table is to provide an at-a-glance list of features and specifications for each filesystem.
Inventor
List the names of those credited with the design of the filesystem specification. This should not include those responsible for writing the implementation.
Name
The full, non abbreviated, name of the filesystem itself.
Native operating system
The name of the operating system in which this filesystem debuted.
Partition identificator
The partitioning scheme and marker used to identify that a partition is formatted to this filesystem.
Bad sector allocation
Describe how the filesystem allocates and isolates bad sectors.
File allocation
Describes how the filesystem allocates sectors in-use by files.
Directory structure
Describes how the subdirectories are implemented.
Namespace
Lists the characters that are legal within file and directory names.
Maximum filename size
The maximum number of characters that a file or directory name may contain.
Maximum files
The maximum number of files the filesystem can handle.
Maximum volume size
The maximum size of a volume that the filesystem specification can handle. This may differ from the maximum size an operating system supports using a given implementation of the filesystem.
Dates handled
What type of dates and times the filesystem can support, which may include:
Creation date
This is the date the file was “created” on the volume. This does not change when working normally with a file, e.g. opening, closing, saving, or modifying the file.
Access date
This is the date the file was last accessed. An access can be a move, an open, or any other simple access. It can also be tripped by Anti-virus scanners, or Windows system processes. Therefore, caution has to be used when stating a “file was last accessed by user XXX” if there is only the “File Access” date in NTFS to work from.
Modified date
This date as shown by Windows there has been a change to the file itself. E.g. if a notepad document has more data added to it, this would trip the date it was modified.
Changed date
The date and time related attributes were modified. This may include ACLs and the file/directory name.
Backed-up date
The date and time when the file was last backed up.
Maximum date
The maximum year that can be handled by the filesystem, as per the specification.
Attributes
Lists the basic file attributes available.
Named streams
Determines if the filesystems supports multiple data streams. NTFS refers to these as alternate data streams, HPFS as extended attributes and HFS calls them forks.
Per-volume compression
Does the filesystem support real-time transparent compression and decompression of an entire volume.
Per-volume encryption
Does the filesystem support real-time transparent encryption and decryption of an entire volume.
Per-file compression
Does the filesystem support real-time transparent compression and decompression of individual files.
Per-file encryption
Does the filesystem support real-time transparent encryption and decryption of individual files.
Access control lists
Does the filesystem support multi-user access control lists (ACLs).