Tag: inode

π‘³π’Šπ’π’Œπ’Šπ’π’ˆ 𝑯𝒂𝒓𝒅? 𝑢𝒓 𝑱𝒖𝒔𝒕 π‘·π’π’Šπ’π’•π’Šπ’π’ˆ π‘Ίπ’π’‡π’•π’π’š?

In Unix-like systems, hard links and symbolic links ease file management by allowing files to appear in multiple directories without actual content duplication. Hard links are identical mirrors of the original file and reside within the same file system, while symbolic links act independently, can span different file systems, and can point to directories. Hard links are useful for resource optimization, image creation, multiversion software, and cache management, while symbolic links are handy for boot selection, linking to volatile storage, device pointers, and fallback mechanisms.

Read More π‘³π’Šπ’π’Œπ’Šπ’π’ˆ 𝑯𝒂𝒓𝒅? 𝑢𝒓 𝑱𝒖𝒔𝒕 π‘·π’π’Šπ’π’•π’Šπ’π’ˆ π‘Ίπ’π’‡π’•π’π’š?

INode

The file system’s inode, a central data structure, holds crucial file details such as type, size, permissions, owners, timestamps, links, data block pointers, and allocated blocks. In Linux, the stat system call accesses the inode to retrieve file information using the struct stat data structure. This enables gathering details about files and directories in the file system.

Read More INode