usr/local/app/database/ -> a link to /mnt/disk1/database/. mnt/disk1/database/ -> a real subdirectory on the second disk mnt/disk1/ -> mount point of second disk, or in equivalent to " D:/". usr/local/app/ -> a real subdirectory on the system volume ![]() The real contents on the extra storage, for example, a directory to hold all database repositories, are usually associated with the conventional path of application / services via symlinks, which works much like " Shortcuts" in Windows, but it's done in the file system level.įor example, in Linux system you can construct your file hierarchy as: In practice, the system volume that you're booting from will be mapped to the " /", and all the extra storage volumes will be collected in one place, such as /mnt in Linux. The process of mapping a volume into main file tree is called " mount", and the mapped subdirectory is called a " mount point". ![]() When the storage is attaching to system, the root of individual storage volume will be mapped to one subdirectory somewhere under the main file tree. "C:\" or "D:\") of the physical storage.Įach of the physical storages has its own hierarchical file tree. The absolute path of every file start from the same root, without having to specify the disk label (e.g. UNIX file system has only one single hierarchical file tree that started from " /". ![]() UNIX file system is vastly different from Windows. If you're asking the later, be prepared to read walls-of-text. NTFS vs HFS vs APFS, or the "file hierarchy structure" ?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |