Switching from macOS to Linux rarely poses difficulties when it comes to basic operations. Both systems have a file manager, a terminal, multitasking, and a similar UNIX heritage. Nevertheless, many users who have worked on a Mac for years encounter an unexpected problem.
Namely, the structure of the Linux file system looks unfamiliar even when the commands in the terminal seem recognizable. In macOS, there is a clear sense that applications reside in the Applications folder, and documents—in the user’s home directory.
At the same time, system components are hidden from prying eyes. Linux offers a different approach. Here, almost everything is organized according to the Filesystem Hierarchy Standard (FHS). That is, each directory has a specific purpose.
For comfortable work in Linux after using macOS, you need to know not only where files are located but also why the system is organized this way.
The Linux structure. What Mac Users Find Unusual
In macOS, most programs are packaged as .app files. To the user, this appears as a single file. But inside, there’s an entire directory structure.
That’s why many Linux beginners expect to find a similar central hub to manage their apps. However, Linux follows a different logic. Namely, the following are stored in different locations within the system:
- Executable files,
- Libraries,
- Program configs and data.
To better understand this difference, we should first mention how applications are organized in macOS. It is from this starting point that it is easiest to see why the Linux file hierarchy initially seems unusual.
So, before you dive into Linux directories, let’s recall the Applications folder on Mac role. It’s the standard location for system and user-installed programs. Located at the top level of the disk alongside system directories, you may access it via Finder, the Go menu, or the Shift+Command+A shortcut.
In Linux, there is no single directory that serves exactly the same role. Instead, program components are distributed across several directories. This depends on their purpose.
File system root
Unlike macOS, where we often interact with disks via Finder, Linux starts with a single root directory:
/
From hard drives to USB drives and network resources, everything in the system is mounted within this tree.
This approach has its roots in classic UNIX systems. It creates a single logical structure independent of the number of physical appliances.
/home Directory
For former Mac users, the /home directory is the easiest to understand.
In macOS, user home directories are located at:
/Users/username
In Linux, the path is:
/home/username
This is where downloads and images are stored, as well as documents, projects, and personal settings. The most modern distributions automatically create familiar folders such as Documents, Downloads, Pictures, or Music. So, the transition to everyday use happens quite naturally.
Hidden configuration files
A distinctive feature of Linux is the large number of hidden files whose names begin with a dot:
.gitconfig
.config
.bashrc
Here personal program settings are stored. In macOS, similar data is often located in the Library folder within the user’s home directory.
The Importance of the /usr Directory
The /usr directory often raises the most questions among beginners. Historically, it stands for “Unix System Resources.” In modern distributions, here a substantial part of the system software is located.
/usr/bin — the location for executable files.
When a user enters the following in the terminal:
python
git
ssh
the system often runs files from:
/usr/bin
That’s why the name of this directory is familiar to almost every Linux user. For a macOS user, you can compare it to system utilities that are hidden within the operating system’s structure. However, in Linux, executable files are transparent for viewing and accessible.
/usr/lib and libraries
The /usr/lib directory stores the libraries that programs require to run. Drawing an analogy with macOS, their role is somewhat similar to Frameworks, which many applications use at the same time. This approach:
- Avoids duplication of identical components;
- Reduces disk space usage.
/etc Directory: What It’s For
This directory stores the system’s global configuration files.
For instance:
- User data;
- Service configurations;
- Network settings;
- Security settings.
In macOS, similar info is spread across several system directories and graphical settings panels. In Linux, however, most critical settings can be viewed and changed directly via text files.
/var Directory as a Place for Continually Changing Data
The name comes from the word “variable.” This directory stores those data that actively changes while the system is running:
- Caches;
- Event logs;
- Print queues;
- Databases for certain services.
Understanding /var/log
This is the first place to look for diagnostics if the server behaves erratically or if the program crashes. Here you will find system logs which help identify the problem cause.
For many macOS users, this level of openness is a pleasant surprise, as Linux allows you to analyze the system’s internal workings in a direct way.
/opt, /srv, and Other Less Common Directories
Not all directories are used on a daily basis. Nevertheless, it is useful to know their purpose.
/opt
This directory often contains third-party programs which are not part of the distribution’s standard package set. Some commercial apps are installed here.
/srv
This directory is for data provided by system services. In particular, it may store files for an FTP server or a website.
/tmp
Most distributions automatically clean this directory on a regular basis. Temporary files are created here.
Thinking in a New Way After Switching to Linux
Linux organizes files not on the principle of “everything belonging to a program is organised together,” but rather by functional purpose. So:
Executable files go to /usr/bin
Logs go to /var/log
Libraries go to /usr/lib
User personal data — to /home
Configurations — to /etc
After a while, such structure starts to seem not more complicated, but rather more predictable. That is, when you know the role of each directory, you can find the file you need much more easily, no matter which distribution you’re using.
Conclusion
If you are a macOS user, the first encounter with the Linux file hierarchy can be like you explore a new path without a map. Directory names seem technical. The familiar Applications folder isn’t enough to understand where programs are located.
Yet there is a consistent logic behind this structure. It’s been shaped by UNIX-like system development for decades.
An understanding of the roles of /home, /usr, /etc, /var, and other key directories will help you navigate Linux with confidence.
Also, to better grasp the operating system’s underlying principles. Once this logic becomes clear, Linux starts to feel like a system where everything is exactly where it should be.
