In Windows there’re perhaps only a couple of important folders (by important I mean important in my logical picture of the Windows file system) in the installation drive (in my case C:\). Namely Program Files and Windows. I simply stay away from Windows folder and the “add remove program files” is good enough to handle the program files folder of Windows. Of course there’s a folder named Users where the users (who are not admins) can access only their folders.

Thus there’s a clear picture at some level in my mind of the Windows file system. In Ubuntu, when I reach the location /, there’s a huge list of folders, most of which I have no clue as to what they contain. The /bin folder seems to be the equivalent of the Windows folder in windows. The /usr folder seems like it’s the equivalent of the Users folder in Windows. But even the /home folder looks like it can fit the bill.

Please understand that I do understand, that Ubuntu (Linux) has a different character than that of Windows, i.e., there need not be exact equivalent of Windows functions, in Ubuntu. All I am looking for is a bit more clearer picture of the Ubuntu file system.

This question is a part of a bigger question which I am splitting up to make it more answerable. The original question can be found here:

  • 3
    See also the directory-structure tag on Unix & Linux. All Linux distributions follow the same model. May 17, 2012 at 18:29
  • Thanks for all your answers. I am a bit confused about a few points: In Windows the setup usually provides through a prompt an option to install a software for all users. How to make that distinction in Ubuntu? Also, this is a usual problem in configuring development softwares to their IDEs. In windows, for example, in "program files\miktex\bin" there's the file "pdflatex.exe". Thus I can point the IDE to this file and configure it. How to go about this process in Ubuntu? Where's the general binary file associated with a software (esp. from the configuration point of view)? May 17, 2012 at 19:02
  • 2
    In Ubuntu, you normally install software for all users. Everything you do through the package manager is for all users. I don't understand the rest of your comment; one does not “configure” the “binary file associated with a software”. You should ask this as a separate question, and give a better explanation of what you're trying to do. May 17, 2012 at 19:05
  • Got it. I will frame a new question. Even then here's a short explanation of what I meant: In windows, the .exe files can be easily located. For example: "C:\Python27\python.exe". So I know where the program Python starts from. Now if I have to use the Eclipse IDE, I can simply point it to python.exe, and this is what I meant by "configure". I configured the IDE for Python. In Ubuntu where's the location where the program is installed? That is what still evades me. May 17, 2012 at 19:10
  • 2
    @Gilles Be careful when saying all. The GoboLinux project actually uses a more Windows like directory structure.
    – new123456
    May 18, 2012 at 1:28

6 Answers 6


You can read up on this on for instance wikipedia. An excerpt:

The Filesystem Hierarchy Standard (FHS) defines the main directories and their contents in Linux operating systems. For the most part, it is a formalization and extension of the traditional BSD filesystem hierarchy.

The FHS is maintained by the Linux Foundation, a non-profit organization consisting of major software and hardware vendors, such as HP, Red Hat, IBM and Dell. The current version is 3.0, released on June 3, 2015.

A visual representation with a short description:

enter image description here

Basically Linux has divided the directory structure based on the function of what is needed to make the system as secure as possible with the minimum amount of permissions needed. Otherwise someone is bound to have to do alot of avoidable work.

Remember that Unix and Linux were made as multi-user systems and Windows was created for a single user. Everything else can be explained from that idea. You can explain every directory when thinking about it being multi-user and security.

3 examples:

  • You will see that files and directories that are admin only are gathered in the same directory: the s in /sbin and /usr/sbin and /usr/local/sbin stands for system. A normal user can not even start programs that are in there. Files a normal user can start are in /bin, /usr/bin, /usr/local/bin based on where it most logically should reside. But if they are admin only they should go to the s version of that directory. There is a famous utility called fuser. You can kill processes with it. If a normal user could use this (s)he would be able to kill your session.

  • The same goes for /home: /home/user1 is property of user1. /home/user2 is property of user2. user2 has no business doing stuff in user1's home (and the other way around is also true: user1 has no business doing stuff in user2's home). If all the files would be in /home with no username underneath it you would have to give permissions to every file and asses if someone is allowed to write/remove those files. A nightmare if you have tens of users.

  • Addition regarding libraries.

    /lib/, /usr/lib/, and /usr/local/lib/ are the original locations, from before multilib systems existed and the exist to prevent breaking things. /usr/lib32, /usr/lib/64, /usr/local/lib32/, /usr/local/lib64/ are 32-/64-bit multilib inventions.

It is not a static concept by any means. Other Linux flavours made tweaks to this lay-out. For instance; currently you will see debian and Ubuntu changing a lot in the lay-out of the FHS since SSD is better off with read only files. There is a movement towards a new lay-out where files are split in to a 'read only' and a 'writable' directory/group so we can have a root partition that can be mounted read only (partition for a ssd) and writable (sata hdd). The new directory that is used for this (not in the image) is /run/.

  • 20
    +1 Rinzwind. I like the image, was actually looking for one. May 17, 2012 at 18:23
  • 6
    ha thought that would get attention :+ @LuisAlvarado
    – Rinzwind
    May 17, 2012 at 18:24
  • 1
    Wasn't /mnt what /media is now, a few years ago?
    – RobinJ
    May 23, 2012 at 10:47
  • 9
    @RobinJ: The diference is that /mnt has historically been manually managed. With the rise of many transient devices (flash drives, etc.) and auto-mounting becoming standard, there was a need to automatically handle mount points. A new directory was needed in order to avoid conflicts with existing manual configuration. Thus, these days /mnt has been relegated to the role of providing a convenient temporary mount point. May 23, 2012 at 11:06
  • 1
    Actually at least nowadays, many applications in /sbin are runnable by normal users (shutdown for example does not even need root rights any longer, same as swapon). So where would be the difference to /bin?
    – Byte Commander
    Sep 20, 2016 at 19:30

Give this command a try:

man 7 hier

You can also view this manual page here: https://manpages.ubuntu.com/manpages/en/man7/hier.7.html

  • 1
    good call! I always forget that one though it is always present (even when the net is down ;) )
    – Rinzwind
    May 17, 2012 at 20:01
  • man hier is now among my favourite commands! The explanations are clearer to me than the FHS doco, especially distinguishing between 'local to the machine' and 'site-wide', for an inexperienced Ubuntu user, crossing over from moderate DOS/Windows experience.
    – WillC
    Apr 6, 2017 at 0:39
  • 1
    BTW the number 7 stands of the section Miscellanea of hier man page. Jan 27, 2018 at 22:53
  • hmm. For what it's worth this kind of reminds me of a link-only answer, even though it's likely that every version of ubuntu will have this. Can you incorporate some of the content from the man page into your answer?
    – jrh
    Nov 15, 2018 at 18:25

Late Answer - I've created a roadmap for beginners to follow. If they are looking for a file but don't know where to look, they can use the map to roughly navigate around. You can download a hi-res PNG here. You can find the related post here. I will keep updating both the file and the post when time permits, incorporating helpful comments.

  • Interesting and helpful idea to produce a flowchart, but unfortunately it seems to have some dead-ends. My question is if I am performing a mysqldump where should I output the file to?
    – BadHorsie
    Dec 17, 2015 at 17:20
  • @BadHorsie of course it'd always depend on your specific use case, but dumping it in a /home/badhorsie/mysqldump directory would suffice. If you are running many apps you can create a new user to run each app and dump it in that app/user's home directory.
    – d4nyll
    Dec 19, 2015 at 15:58
  • Great & helpful illustration! Thanks. But I have a question. if it's neither installed from source, and nor it's installed using a package manager, then what is it?! You've said it then goes into /usr while the FHS documentation emphasizes that local software must not be installed within /usr since it can get overwritten in system upgrades and /usr/local should be used instead.
    – aderchox
    Apr 19, 2020 at 23:34
  • Very useful! If it doesn't make the chart too crowded, I'd add ~/.local/ that contains data and executables like personal scripts for a specific user. Jan 14, 2021 at 8:47
  • Usually in a flowchart you start with an oval (just as you end with an oval).
    – Adam
    Jan 5, 2022 at 20:33

This following text shows the directory structure.

mtk4@laptop:/$ pwd
mtk4@laptop:/$ tree -L 1
|-- bin
|-- boot
|-- cdrom
|-- dev
|-- etc
|-- home
|-- lib
|-- lost+found
|-- media
|-- mnt
|-- opt
|-- proc
|-- root
|-- run
|-- sbin
|-- selinux
|-- srv
|-- sys
|-- tmp
|-- usr
|-- var

The main components here are:

  1. /boot : Contains the boot loader

  2. /home : Contains the home directories of users.

  3. /bin : All the executable binaries and commands used by all the users on the system are located here.

  4. /sbin : This contains the system executable binaries typically used by system administrators.

  5. /lib : Contains the system libraries that support the binaries in /bin and /sbin.

  6. /etc : Contains the configuration files for network, boot-time, etc.

  7. /dev : This has the device files i.e. usb, terminal device or any other device attached to the system are shown here.

  8. /proc : Contains information about the process running.

  9. /tmp : This is the temporary directory where many processes create the temporary files required. This is purged each time the machine is booted.

For more details, Thegeekstuff link perfectly explain the generic linux file-system.


\Users is equivalent to /home. The name of /usr is a historical artifact.

The combined equivalent of \Windows and \Program Files is the combination of /bin, /boot, /etc, /lib, /sbin, /tmp, /usr and /var. Linux and Windows split up installed software differently. Windows distinguishes between the operating system and companion programs. Linux doesn't make this distinction in the same way; most if not all software comes through Ubuntu (the distributor) and is installed in the same directory hierarchy, and since software is tracked by the package manager, there is no need to store each program in its own directory. On Linux:

  • /etc is for system configuration files: configuration files that affect all users, whether they apply to the operating system as a whole or to a specific application.
  • /usr is for system code and data (programs, libraries, documentation, etc.).
  • /var is for variable or temporary data: temporary files, logs, package manager databases, printer spools, game save files, etc. There is also /tmp for temporary files that can be erased across reboots.
  • /bin, /lib and /sbin in the root directory have counterparts in /usr. The files that are outside /usr are the ones that are needed early in the boot process. This is a relic from the time when disks were small and /usr might be on a filesystem shared between several workstations over the network, it isn't really a useful distinction on most systems.
  • /boot contains a few files that are needed only to boot the operating system, and not for day-to-day operation.

There are additional directories that don't correspond to anything that Windows has:

  • /root is the root user's home directory. The root user is an administrator account not tied to any particular user; it's the user that you change to when you run sudo. Ubuntu doesn't let the root user log in by default.
  • /media and /mnt are mount points: they're where you can see the filesystems of other operating systems and remote drives. The Windows equivalent is other drive letters.
  • /proc and /sys show system information. On Windows, you need to wade through menus or call system commands or install third-party programs to see this information.

Ubuntu, like other Linux distributions, generally follows the Linux Filesystem Hierarchy Standard.


Ubuntu (like all UNIX-like systems) organizes files in a hierarchical tree, where relationships are thought of in teams of children and parent. Directories can contain other directories as well as regular files, which are the "leaves" of the tree. Any element of the tree can be references by a path name; an absolute path name starts with the character / (identifying the root directory, which contains all other directories and files), then every child directory that must be traversed to reach the element is listed, each separated by a / sign.

A relative path name is one that doesn't start with /; in that case, the directory tree is traversed starting from a given point, which changes depending on context, called the current directory. In every directory, there are two special directories called . and .., which refer respectively to the directory itself, and to its parent directory.

The fact that all files and directories have a common root means that, even if several different storage devices are present on the system, they are all seen as directories somewhere in the tree, once they are mounted to the desired place

Find examples and more information here:


You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .