| Directory
|
Description
|
| /usr/bin/ |
Common utilities, programming tools, and applications.
|
| /usr/home/user/ |
Home directory of an user
|
| /usr/include/ |
Standard C include files. But on GhostBSD without content
|
| /usr/jails/ |
Jails build upon the chroot(2) concept, which is used to change the root directory of a set of processes. This creates a safe environment, separate from the rest of the system. Processes created in the chrooted environment can not access files or resources outside of it. For that reason, compromising a service running in a chrooted environment should not allow the attacker to compromise the entire system. However, a chroot has several limitations. It is suited to easy tasks which do not require much flexibility or complex, advanced features. Over time, many ways have been found to escape from a chrooted environment, making it a less than ideal solution for securing services.
|
| /usr/lib/ |
Archive libraries
|
| /usr/lib32/ |
lib32 contains 32-bit libraries, which are required to run any i386-targeted binary, such as wine
|
| /usr/libdata/ |
Miscellaneous utility data files.
|
| /usr/libexec/ |
System daemons and system utilities executed by other programs.
|
| /usr/local |
Local executables like /usr/local/bin/ and /usr/local/sbin/. Also used as the default destination for the ports framework. Within /usr/local, the general layout sketched out by hier(7) for /usr should be used. Exceptions are the man directory, which is directly under /usr/local rather than under /usr/local/share, and the ports documentation is in share/doc/port.
|
| /usr/obj/ |
Architecture-specific target tree produced by building the /usr/src tree.
|
| /usr/ports/ |
The GhostBSD Ports Collection (optional).
|
| /usr/sbin/ |
System daemons and system utilities executed by users.
|
| /usr/share/ |
Architecture-independent files.
|
| /usr/src/ |
BSD and/or local source files.
|
Back to  Directory Structure
|
/usr/.
