Directory structure
In computing, a directory structure is the way an operating system's file system and its files are displayed to the user. Files are typically displayed in a hierarchical tree structure.
File names and extensionsxcxcx
A filename is a string used to uniquely identify a file stored on the file system of a computer. Before the advent of 32-bit operating systems, file names were typically limited to short names (6 to 14 characters in size). Modern operating systems now typically allow much longer filenames (moererd added to Ed and ddddddx Xbox xlive is xun4 x xxXbox x
Windows, DOS and OS/2 x x sx n
In DOS, Windows, and OS/2, the root directory is "drive:\", for example, the root directory is usually "C:\". The directory separator is usually a "\", but the operating system also internally recognizes a "/". Physical and virtual drives are named by a drive letter, as opposed to being combined as one.[1] This means that there is no "formal" root directory, but rather that there are independent root directories on each drive. However, it is possible to combine two drives into one virtual drive letter, by setting a hard drive into a RAID setting of 0.[2]
Windows 10cvncccccccccbn
r tr4he root of a boot partition. vvvvvvvvvvvvvvvvvvver
| Folder | Description |
|---|---|
|
|
c |
|
|
ene4444444her |
|
|
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
|
|
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
|
|
t |
|
tgfgdcg |
|
This folder stores per-user application data and settings. The folder contains three subfolders: Roaming, Local, and LocalLow. Roaming is for networked based logins for roaming profiles. Data saved in Roaming will synchronize to the computer when the user logs into that. Local and LocalLow does not sync up with networked computers. [3]
|
|
|
Windows itself is installed into this folder. |
|
These folders store dynamic-link library (DLL) files that implement the core features of Windows and Windows API. Any time a program asks Windows to load a DLL file and do not specify a path, these folders are searched after program's own folder is searched.[4] "System" stores 16-bit DLLs and is normally empty on 64-bit editions of Windows. "System32" stores either 32-bit or 64-bit DLL files, depending on whether the Windows edition is 32-bit or 64-bit. "SysWOW64" only appears on 64-bit editions of Windows and stores 32-bit DLLs.[5] |
| This folder is officially called "Windows component store" and constitutes the majority of Windows. A copy of all Windows components, as well as all Windows updates and service packs is stored in this folder. Starting with Windows 7 and Windows Server 2008 R2, Windows automatically scavenges this folder to keep its size in check. For security reasons and to avoid the DLL Hell issue, Windows enforces very stringent requirements on how the files in this folder are organized.[6] |
Unix
Unix and Unix-like operating systems use the Filesystem Hierarchy Standard as the common form for their directory structures. All files and directories appear under the root directory "/", even if they are stored on different physical devices.[7]
See also
References
- ^ "Archived copy". Archived from the original on 2009-09-18. Retrieved 2009-08-30.
{{cite web}}: CS1 maint: archived copy as title (link) - ^ http://www.pcguide.com/ref/hdd/perf/raid/levels/singleLevel0-c.html
- ^ http://superuser.com/questions/21458/why-are-there-directories-called-local-locallow-and-roaming-under-users-user
- ^ "Dynamic-Link Library Search Order". MSDN. Microsoft. Retrieved 2 September 2015.
- ^ "Windows Confidential: History—the Long Way Through". TechNet Magazine. September 2010.
- ^ "How to address disk space issues that are caused by a large Windows component store (WinSxS) directory". Support. Microsoft. Retrieved 2 September 2015.
- ^ http://www.tuxfiles.org/linuxhelp/linuxdir.html