Difference between revisions of "/usr/"
From GhostBSD Wiki
| (3 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
! scope="col" style="width: 350px;"|'''Description''' | ! scope="col" style="width: 350px;"|'''Description''' | ||
|- | |- | ||
| − | |/usr/bin/||Common utilities, programming tools, and applications. | + | |[[/usr/bin/]]||Common utilities, programming tools, and applications. |
|- | |- | ||
|/usr/home/''user''/||Home directory of an user | |/usr/home/''user''/||Home directory of an user | ||
|- | |- | ||
| − | |/usr/include/||Standard C include files. | + | |/usr/include/||Standard C include files. But on GhostBSD '''without content''' |
|- | |- | ||
|/usr/jails/||[https://www.freebsd.org/doc/handbook/jails.html Jails] build upon the [https://www.freebsd.org/cgi/man.cgi?query=chroot&sektion=2&manpath=freebsd-release-ports 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/jails/||[https://www.freebsd.org/doc/handbook/jails.html Jails] build upon the [https://www.freebsd.org/cgi/man.cgi?query=chroot&sektion=2&manpath=freebsd-release-ports 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. | ||
| Line 22: | Line 22: | ||
|/usr/libexec/||System daemons and system utilities executed by other programs. | |/usr/libexec/||System daemons and system utilities executed by other programs. | ||
|- | |- | ||
| − | |/usr/local||Local executables and | + | |/usr/local||Local executables like [[/usr/local/bin/]] and [[/usr/local/sbin/]]. Also used as the default destination for the ports framework. Within <code>/usr/local</code>, the general layout sketched out by [https://www.freebsd.org/cgi/man.cgi?query=hier&sektion=7&manpath=freebsd-release-ports hier(7)] for <code>/usr</code> should be used. Exceptions are the man directory, which is directly under <code>/usr/local</code> rather than under <code>/usr/local/share</code>, and the ports documentation is in share/doc/port. |
|- | |- | ||
|/usr/obj/||Architecture-specific target tree produced by building the <code>/usr/src</code> tree. | |/usr/obj/||Architecture-specific target tree produced by building the <code>/usr/src</code> tree. | ||
| Line 28: | Line 28: | ||
|/usr/ports/||The GhostBSD Ports Collection (optional). | |/usr/ports/||The GhostBSD Ports Collection (optional). | ||
|- | |- | ||
| − | |/usr/sbin/||System daemons and system utilities executed by users. | + | |[[/usr/sbin/]]||System daemons and system utilities executed by users. |
|- | |- | ||
|/usr/share/||Architecture-independent files. | |/usr/share/||Architecture-independent files. | ||
Latest revision as of 06:08, 13 July 2020
Welcome to  /usr/.
|
| 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
| |
