Files, directories and persistence
File contents, directory names and durable storage have distinct roles.
Key knowledge
In the stated UNIX-style model, a regular file is an indexed sequence of bytes. A directory associates names with filesystem objects; paths traverse this naming hierarchy. Persistent storage retains data beyond volatile memory, but a successful buffered write alone need not make data durable after a crash.
Conditions and scope
- Declare the filesystem and file format; stored bytes alone do not determine their interpretation.
- Durability depends on synchronization and storage guarantees; newly created names can require directory synchronization as well as file synchronization.
Sources · 2
References
Sources retain their recorded scope. A source link alone does not establish verification of every statement.
Evidence and review
File contents, directory names and durable storage have distinct roles.
2026-10-10 · Independent Physics and Measurement reference editor (AI editorial bounded review). Exact bounded introductory reference claims and this practical concept inventory are approved after closure. Existing university/research proof and source scopes remain separate; no universal knowledge-completeness or experimental-validation assertion.
Foundational review
2026-10-10 · Independent AI editorial inspection of this new compact reference entry, its equations, applicability, sources and knowledge connections.
Sources from other places
Scope or convention differs
Unix regular files as byte sequences, named through directories and paths.
The source does not establish the separate repository crash-durability or fsync condition.
UNSW Sydney, School of Computer Science and Engineering
- COMP1521 · Files (23T2) AustraliaEnglish
Slide 7 (PDF p.3); Slides 40–43 (PDF pp.14–15)
- COMP1521 · Files (23T2)
Entry details
Permanent link to this entry ↗- Record identity
- foundation-info-files-directories
- Revision
- foundations-audit.1
- Structured reference record
- Foundational core completion