Core CS

Types Of Files

In an Operating System, a file is an abstract, named collection of related data stored on secondary storage. Because an OS interacts with varying kinds of information—ranging from user source code and multimedia to hardware peripherals—it classifies files into distinct types so the file system knows how to allocate space, enforce access permissions, and execute or open each file properly. Common types include ordinary files (text and binary), directory files, special or device files (character and block), and link or FIFO files.

<p></p><h2><p><br></p></h2><h3 style="color:rgb(31, 31, 31)">1. Ordinary / Regular Files</h3><h2><div><div style="color:rgb(31, 31, 31)">Files that contain user information such as plain text, source code, multimedia, databases, or compiled binaries. They do not hold system administrative file structures.</div><br><ul style="color:rgb(31, 31, 31)"><li><div><b>Key Points:</b></div><br><ul><li><div><b>Text Files:</b> Contain characters encoded in standard formats (ASCII, UTF-8); readable by humans.</div><br></li><li><div><b>Binary Files:</b> Contain machine-readable data (e.g., <code style="color:rgba(0, 0, 0, 0.55)">.exe</code>, <code style="color:rgba(0, 0, 0, 0.55)">.bin</code>, <code style="color:rgba(0, 0, 0, 0.55)">.mp4</code>); require specific interpreters or runtimes to execute.</div><br></li></ul></li><li><div><b>Significance</b></div></li></ul><div style="color:rgb(31, 31, 31)"> Serves as the primary medium for users and applications to save persistent work and install software.</div><span style="color:rgb(31, 31, 31)"><strong><br></strong></span><ul style="color:rgb(31, 31, 31)"><li><div><b>Advantages:</b></div><br><ul><li><div>Simple to create, modify, copy, and delete.</div><br></li><li><div>Compatible across diverse user applications and tools.</div><br></li></ul></li><li><div><b>Disadvantages:</b></div><br><ul><li><div>Binary files can pose security risks if malicious code executes.</div><br></li><li><div>Prone to corruption if write operations are interrupted unexpectedly.</div><br></li></ul></li></ul></div></h2><h3 style="color:rgb(31, 31, 31)">2. Directory Files</h3><h2><div><div style="color:rgb(31, 31, 31)">Files that contain lists of file names along with pointers (like node references) to the metadata and locations of other files or subdirectories.</div><br><ul style="color:rgb(31, 31, 31)"><li><div><b>Key Points:</b></div><br><ul><li><div>Forms the hierarchical tree structure (e.g., folders).</div><br></li><li><div>Maintained and updated directly by the operating system kernel.</div><br></li></ul></li><li><div><b>Significance:</b> </div></li></ul><span style="color:rgb(31, 31, 31)">Enables logical organization, fast path resolution, and multi-user file separation on storage devices.</span><br><span style="color:rgb(31, 31, 31)"><strong><br></strong></span><ul style="color:rgb(31, 31, 31)"><li><div><b>Advantages:</b></div><br><ul><li><div>Prevents naming collisions by allowing duplicate file names across different folders.</div><br></li><li><div>Simplifies file searches and access control at a group/folder level.</div><br></li></ul></li><li><div><b>Disadvantages:</b></div><br><ul><li><div>Deep directory nesting increases disk seek time and path lookup overhead.</div><br></li><li><div>Accidental deletion of a root folder can compromise entire sub-trees of data.</div><br></li></ul></li></ul></div></h2><h3 style="color:rgb(31, 31, 31)">3. Special / Device Files</h3><h2><div style="color:rgb(31, 31, 31)"><div>Files used by the OS to represent physical or virtual hardware devices (such as disks, terminals, keyboards, and printers), making hardware access uniform via standard file I/O operations (<code style="color:rgba(0, 0, 0, 0.55)">read</code>, <code style="color:rgba(0, 0, 0, 0.55)">write</code>).</div><br><ul><li><div><b>Key Points:</b></div><br><ul><li><div><b>Character Special Files:</b> Handle data byte-by-byte in an unbuffered stream (e.g., keyboards, serial ports, mice).</div><br></li><li><div><b>Block Special Files:</b> Transfer data in fixed-size blocks with system caching (e.g., HDDs, SSDs, USB drives).</div><br></li></ul></li><li><div><b>Significance:</b> Implements the "everything is a file" UNIX philosophy, providing a consistent API for programs to communicate with hardware without needing custom device drivers for every application.</div><br></li><li><div><b>Advantages:</b></div><br><ul><li><div>Standardizes device interaction using routine system calls (<code style="color:rgba(0, 0, 0, 0.55)">open()</code>, <code style="color:rgba(0, 0, 0, 0.55)">read()</code>, <code style="color:rgba(0, 0, 0, 0.55)">write()</code>).</div><br></li><li><div>Hides low-level hardware complexity from everyday software.</div><br></li></ul></li><li><div><b>Disadvantages:</b></div><br><ul><li><div>Direct write mistakes to raw block device files can overwrite critical partition tables.</div><br></li><li><div>Cannot perform random access (<code style="color:rgba(0, 0, 0, 0.55)">seek</code>) on stream-based character files.</div><br></li></ul></li></ul></div></h2><h3 style="color:rgb(31, 31, 31)">4. Link Files (Symbolic & Hard Links)</h3><h2><div style="color:rgb(31, 31, 31)"><div>Files that serve as pointers or aliases to other files within the file system.</div><br><ul><li><div><b>Key Points:</b></div><br><ul><li><div><b>Hard Link:</b> A direct directory entry pointing to the existing inode of a file; shares the exact same data blocks.</div><br></li><li><div><b>Symbolic (Soft) Link:</b> A small independent file containing the path string to another target file.</div><br></li></ul></li><li><div><b>Significance:</b> Allows multiple paths or workflows to share access to a single file without duplicating storage blocks.</div><br></li><li><div><b>Advantages:</b></div><br><ul><li><div>Saves secondary storage by referencing a single physical copy.</div><br></li><li><div>Simplifies library version management (e.g., pointing <code style="color:rgba(0, 0, 0, 0.55)">libssl.so</code> to a specific version like <code style="color:rgba(0, 0, 0, 0.55)">libssl.so.3</code>).</div><br></li></ul></li><li><div><b>Disadvantages:</b></div><br><ul><li><div>Deleting the target breaks symbolic links ("dangling link").</div><br></li><li><div>Hard links typically cannot span across different disk partitions or file systems.</div><br></li></ul></li></ul></div></h2><h3 style="color:rgb(31, 31, 31)">5. FIFO / Named Pipe Files</h3><h2><div style="color:rgb(31, 31, 31)"><div>Specialized temporary files used to establish inter-process communication (IPC) by allowing two separate processes to exchange data on a first-in, first-out basis.</div><br><ul><li><div><b>Key Points:</b></div><br><ul><li><div>Exists in the file system namespace like a standard file, but holds no actual disk blocks.</div><br></li><li><div>Operates entirely in main memory buffers managed by the OS kernel.</div><br></li></ul></li><li><div><b>Significance:</b> Provides a structured, bidirectional pipeline for unrelated processes running on the same machine to stream data.</div><br></li><li><div><b>Advantages:</b></div><br><ul><li><div>Facilitates clean, memory-efficient data streaming between independent processes.</div><br></li><li><div>Avoids disk write wear and cleanup overhead because data resides in RAM.</div><br></li></ul></li><li><div><b>Disadvantages:</b></div><br><ul><li><div>Read and write processes block if the other end is not open or reading fast enough.</div><br></li><li><div>Data is strictly transient and disappears once read or if the machine restarts.</div></li></ul></li></ul></div></h2><h3></h3><h3></h3><p></p>