<citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry>
system and service manager are organized based on a
file system hierarchy inspired by UNIX, more
- specificaly the hierarchy described in the <ulink
+ specifically the hierarchy described in the <ulink
url="http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html">File
System Hierarchy</ulink> specification and
<citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry>. This
root. Usually writable, but this is
not required. Possibly a temporary
file system (<literal>tmpfs</literal>). Not shared with
- other hosts (unless read-only). The
- administrator may create additional
- top-level subdirectories in this tree,
- if required and the name does not
- conflict with any of the directories
- listed below.</para></listitem>
+ other hosts (unless read-only).
+ </para></listitem>
</varlistentry>
<varlistentry>
System Partition, also see
<citerefentry><refentrytitle>systemd-boot-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>. This
directory is usually strictly local
- the host, and should be considered
+ to the host, and should be considered
read-only, except when a new kernel or
boot loader is installed. This
directory only exists on systems that
system users. This directory and
possibly the directories contained
within it might only become available
- or writable in late boot or even on
- user login only. This directory might
- be placed on limited-functionality
+ or writable in late boot or even only
+ after user authentication. This directory
+ might be placed on limited-functionality
network file systems, hence
applications should not assume the
full set of file API is available on
<listitem><para>The place for small
temporary files. This directory is
usually mounted as
- <literal>tmpfs</literal> instance, and
+ a <literal>tmpfs</literal> instance, and
should hence not be used for larger
files. (Use
<filename>/var/tmp</filename> for
for system packages to place runtime
data in. This directory is flushed on
boot, and generally writable for
- priviliged programs
+ privileged programs
only. Always writable.</para></listitem>
</varlistentry>
<term><filename>/run/user</filename></term>
<listitem><para>Contains per-user
runtime directories, each usually
- invidually mounted
+ individually mounted
<literal>tmpfs</literal>
instances. Always writable, flushed at
each reboot and when the user logs
identifier. This directory should not
be used for package-specific data,
unless this data is
- architecture-dependent,
- too.</para></listitem>
+ architecture-dependent, too. To query
+ <varname>$libdir</varname> for the
+ primary architecture of the system,
+ invoke
+ <programlisting># pkg-config --variable=libdir systemd</programlisting></para></listitem>
</varlistentry>
<varlistentry>
<term><filename>/usr/share</filename></term>
<listitem><para>Resources shared
- betwen multiple packages, such as
+ between multiple packages, such as
documentation, man pages, time zone
information, fonts and other
resources. Usually, the precise
<term><filename>/dev</filename></term>
<listitem><para>The root directory for
device nodes. Usually this directory
- is mounted as
+ is mounted as a
<literal>devtmpfs</literal> instance,
but might be of a different type in
sandboxed/containerized setups. This
programs) or
<varname>$XDG_RUNTIME_DIR</varname>
(for user programs) instead of POSIX
- shared memory segments, since they
+ shared memory segments, since those
directories are not world-writable and
hence not vulnerable to
security-sensitive name
<tbody>
<row>
<entry><filename>/usr/bin</filename></entry>
- <entry>Package executables that shall appear in the <varname>$PATH</varname> executable search path, compiled for the primary architecture of the operating system. It is not recommended to place internal binaries or binaries that are not commonly invoked from the shell in this directory, such as daemon binaries. As this directory is shared with most other packages of the system special care should be take to pick unique names for files placed here, that are unlikely to clash with other package's files.</entry>
+ <entry>Package executables that shall appear in the <varname>$PATH</varname> executable search path, compiled for the primary architecture of the operating system. It is not recommended to place internal binaries or binaries that are not commonly invoked from the shell in this directory, such as daemon binaries. As this directory is shared with most other packages of the system special care should be taken to pick unique names for files placed here, that are unlikely to clash with other package's files.</entry>
</row>
<row>
<entry><filename>$libdir</filename></entry>
</row>
<row>
<entry><filename>/etc/<replaceable>package</replaceable></filename></entry>
- <entry>System-specific configuration for the package. It is recommended to default to safe fallbacks if this configuration is missing, if this is possible. Alternatively, a <citerefentry><refentrytitle>tmpfiles.d</refentrytitle><manvolnum>5</manvolnum></citerefentry> fragment may be used to copy or symlink the necessary files and directores from <filename>/usr/share/factory</filename> during boot, via the <literal>L</literal> or <literal>C</literal> directives.</entry>
+ <entry>System-specific configuration for the package. It is recommended to default to safe fallbacks if this configuration is missing, if this is possible. Alternatively, a <citerefentry><refentrytitle>tmpfiles.d</refentrytitle><manvolnum>5</manvolnum></citerefentry> fragment may be used to copy or symlink the necessary files and directories from <filename>/usr/share/factory</filename> during boot, via the <literal>L</literal> or <literal>C</literal> directives.</entry>
</row>
<row>
<entry><filename>/run/<replaceable>package</replaceable></filename></entry>
<citerefentry><refentrytitle>hier</refentrytitle><manvolnum>7</manvolnum></citerefentry>,
<citerefentry><refentrytitle>systemd-boot-generator</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
<citerefentry><refentrytitle>sysctl.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
+ <citerefentry><refentrytitle>pkg-config</refentrytitle><manvolnum>1</manvolnum></citerefentry>
</para>
</refsect1>