Merge pull request #14573 from keszybz/docs-index

Docs index

docs/UIDS-GIDS.md

@@ -1,10 +1,10 @@
 ---
-title: Users, Groups, UIDs and GIDs on `systemd` Systems
+title: Users, Groups, UIDs and GIDs on systemd Systems
 category: Concepts
 layout: default
 ---
 
-# Users, Groups, UIDs and GIDs on `systemd` Systems
+# Users, Groups, UIDs and GIDs on systemd Systems
 
 Here's a summary of the requirements `systemd` (and Linux) make on UID/GID
 assignments and their ranges.

docs/index.md

@@ -8,8 +8,6 @@ systemd provides aggressive parallelization capabilities, uses socket and D-Bus
 
 Other parts include a logging daemon, utilities to control basic system configuration like the hostname, date, locale, maintain a list of logged-in users and running containers and virtual machines, system accounts, runtime directories and settings, and daemons to manage simple network configuration, network time synchronization, log forwarding, and name resolution.
 
-See the introductory blog story and three status updates for a longer introduction. Also see the [Wikipedia article](https://en.wikipedia.org/wiki/systemd).
-
 ---
 
 {% assign by_category = site.pages | group_by:"category" %}
@@ -24,3 +22,72 @@ See the introductory blog story and three status updates for a longer introducti
   {% endif %}
 {% endfor %}
 
+## See also
+
+* [Introductory blog story](http://0pointer.de/blog/projects/systemd.html)
+* [Three](http://0pointer.de/blog/projects/systemd-update.html) [status](http://0pointer.de/blog/projects/systemd-update-2.html) [updates](http://0pointer.de/blog/projects/systemd-update-3.html)
+* The [Wikipedia article](https://en.wikipedia.org/wiki/systemd).
+
+<pre style="float:right; color:white; background-color:black; font-size:smaller; width:45%; padding:6pt 8pt">
+Welcome to <span style="color:blue">Fedora 20 (Heisenbug)</span>!
+
+[  <span style="color:green">OK</span>  ] Reached target Remote File Systems.
+[  <span style="color:green">OK</span>  ] Listening on Delayed Shutdown Socket.
+[  <span style="color:green">OK</span>  ] Listening on /dev/initctl Compatibility Named Pipe.
+[  <span style="color:green">OK</span>  ] Reached target Paths.
+[  <span style="color:green">OK</span>  ] Reached target Encrypted Volumes.
+[  <span style="color:green">OK</span>  ] Listening on Journal Socket.
+         Mounting Huge Pages File System...
+         Mounting POSIX Message Queue File System...
+         Mounting Debug File System...
+         Starting Journal Service...
+[  <span style="color:green">OK</span>  ] Started Journal Service.
+         Mounting Configuration File System...
+         Mounting FUSE Control File System...
+[  <span style="color:green">OK</span>  ] Created slice Root Slice.
+[  <span style="color:green">OK</span>  ] Created slice User and Session Slice.
+[  <span style="color:green">OK</span>  ] Created slice System Slice.
+[  <span style="color:green">OK</span>  ] Reached target Slices.
+[  <span style="color:green">OK</span>  ] Reached target Swap.
+         Mounting Temporary Directory...
+[  <span style="color:green">OK</span>  ] Reached target Local File Systems (Pre).
+         Starting Load Random Seed...
+         Starting Load/Save Random Seed...
+[  <span style="color:green">OK</span>  ] Mounted Huge Pages File System.
+[  <span style="color:green">OK</span>  ] Mounted POSIX Message Queue File System.
+[  <span style="color:green">OK</span>  ] Mounted Debug File System.
+[  <span style="color:green">OK</span>  ] Mounted Configuration File System.
+[  <span style="color:green">OK</span>  ] Mounted FUSE Control File System.
+[  <span style="color:green">OK</span>  ] Mounted Temporary Directory.
+[  <span style="color:green">OK</span>  ] Started Load Random Seed.
+[  <span style="color:green">OK</span>  ] Started Load/Save Random Seed.
+[  <span style="color:green">OK</span>  ] Reached target Local File Systems.
+         Starting Recreate Volatile Files and Directories...
+         Starting Trigger Flushing of Journal to Persistent Storage...
+[  <span style="color:green">OK</span>  ] Started Recreate Volatile Files and Directories.
+         Starting Update UTMP about System Reboot/Shutdown...
+[  <span style="color:green">OK</span>  ] Started Trigger Flushing of Journal to Persistent Storage.
+[  <span style="color:green">OK</span>  ] Started Update UTMP about System Reboot/Shutdown.
+[  <span style="color:green">OK</span>  ] Reached target System Initialization.
+[  <span style="color:green">OK</span>  ] Reached target Timers.
+[  <span style="color:green">OK</span>  ] Listening on D-Bus System Message Bus Socket.
+[  <span style="color:green">OK</span>  ] Reached target Sockets.
+[  <span style="color:green">OK</span>  ] Reached target Basic System.
+         Starting Permit User Sessions...
+         Starting D-Bus System Message Bus...
+[  <span style="color:green">OK</span>  ] Started D-Bus System Message Bus.
+         Starting Login Service...
+         Starting Cleanup of Temporary Directories...
+[  <span style="color:green">OK</span>  ] Started Permit User Sessions.
+[  <span style="color:green">OK</span>  ] Started Cleanup of Temporary Directories.
+         Starting Console Getty...
+[  <span style="color:green">OK</span>  ] Started Console Getty.
+[  <span style="color:green">OK</span>  ] Reached target Login Prompts.
+[  <span style="color:green">OK</span>  ] Started Login Service.
+[  <span style="color:green">OK</span>  ] Reached target Multi-User System.
+
+Fedora release 20 (Heisenbug)
+Kernel 3.9.2-200.fc18.x86_64 on an x86_64 (console)
+
+fedora login:
+</pre>

man/systemd.scope.xml

@@ -46,14 +46,14 @@
     Control Group Interfaces</ulink> for an introduction on how to make
     use of scope units from programs.</para>
 
-    <para>Note that unlike service units scope units have no "main" process, all processes in the scope are
+    <para>Note that, unlike service units, scope units have no "main" process: all processes in the scope are
-    equivalent. The lifecycle of the scope unit is thus not bound to the lifetime of one specific process but
+    equivalent. The lifecycle of the scope unit is thus not bound to the lifetime of one specific process,
-    to the existance of any processes in the scope. This also means that the exit status of these processes
+    but to the existence of at least one process in the scope. This also means that the exit statuses of
-    do not cause the scope unit to enter a failure state. Scope units may still enter a failure state, for
+    these processes are not relevant for the scope unit failure state. Scope units may still enter a failure
-    example due to resource exhaustion or stop timeouts being reached, but not due to programs inside of them
+    state, for example due to resource exhaustion or stop timeouts being reached, but not due to programs
-    terminating uncleanly. Since processes managed as scope units generally remain children of the original
+    inside of them terminating uncleanly. Since processes managed as scope units generally remain children of
-    process that forked them off it's also the job of that process to collect their exit statuses and act on
+    the original process that forked them off, it is also the job of that process to collect their exit
-    them as needed.</para>
+    statuses and act on them as needed.</para>
   </refsect1>
 
   <refsect1>