picnoir
/
Systemd
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

typo fixes

This commit is contained in:
Thomas Hindoe Paaboel Andersen 2014-07-01 21:11:35 +02:00
parent 8900367cd2
commit ce1dde29b9
2 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
NEWS
View File

@ -38,7 +38,7 @@ CHANGES WITH 215:
dynamic loader cache (ldconfig). The systemd-sysusers tool
described above also makes use of this now. With this in
place it is now possible to start up a minimal operating
system with /etc empty cleanly. Fore more information on the
system with /etc empty cleanly. For more information on the
concepts involved see this recent blog story:
http://0pointer.de/blog/projects/stateless.html
@ -93,7 +93,7 @@ CHANGES WITH 215:
* For tmpfiles' "L", "L+", "C" and "C+" directives the final
'argument' field (which so far specified the source to
symlink/copy the files from) is now optional. If ommited the
symlink/copy the files from) is now optional. If omitted the
same file os copied from /usr/share/factory/ suffixed by the
full destination path. This is useful for populating /etc
with essential files, by copying them from vendor defaults
@ -107,7 +107,7 @@ CHANGES WITH 215:
* A new command "systemctl is-system-running" has been added
that allows checking the overall state of the system, for
example whether it is fully up an running.
example whether it is fully up and running.
* When the system boots up with an empty /etc, the equivalent
to "systemctl preset-all" is executed during early boot, to
@ -151,7 +151,7 @@ CHANGES WITH 215:
the old name to the new name.
* journald's SplitMode= now defaults to "uid". This makes sure
that unpriviliged users can access their own coredumps with
that unprivileged users can access their own coredumps with
coredumpctl without restrictions.
* New kernel command line options "systemd.wants=" (for

12
man/file-hierarchy.xml
View File

@ -719,9 +719,9 @@
<refsect1>
<title>Unpriviliged Write Access</title>
<title>Unprivileged Write Access</title>
<para>Unpriviliged processes generally lack
<para>Unprivileged processes generally lack
write access to most of the hierarchy.</para>
<para>The exceptions for normal users are
@ -734,14 +734,14 @@
below <filename>/run/user</filename>) of the
user, which are all writable.</para>
<para>For unpriviliged system processes only
<para>For unprivileged system processes only
<filename>/tmp</filename>,
<filename>/var/tmp</filename> and
<filename>/dev/shm</filename> are writable. If an
unpriviliged system process needs a private, writable
unprivileged system process needs a private, writable
directory in <filename>/var</filename> or
<filename>/run</filename>, it is recommended to either
create it before dropping priviliges in the daemon
create it before dropping privileges in the daemon
code, to create it via
<citerefentry><refentrytitle>tmpfiles.d</refentrytitle><manvolnum>5</manvolnum></citerefentry>
fragments during boot, or via the
@ -802,7 +802,7 @@
</row>
<row>
<entry><filename>/usr/lib/<replaceable>arch-id</replaceable>/<replaceable>package</replaceable></filename></entry>
<entry>Private other vendor resources of the package that are architecture-specific and cannot be shared between architectures. Note that this generally does not include private exectuables since binaries of a specific architecture may be freely invoked from any other supported system architecture.</entry>
<entry>Private other vendor resources of the package that are architecture-specific and cannot be shared between architectures. Note that this generally does not include private executables since binaries of a specific architecture may be freely invoked from any other supported system architecture.</entry>
</row>
<row>
<entry><filename>/usr/include/<replaceable>package</replaceable></filename></entry>