guix-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

01/01: doc: Add German translation.


From: julien lepiller
Subject: 01/01: doc: Add German translation.
Date: Thu, 1 Nov 2018 07:38:56 -0400 (EDT)

roptat pushed a commit to branch master
in repository guix.

commit 1e40e70bfebba47ccea354ddf862276d2c4223ea
Author: Julien Lepiller <address@hidden>
Date:   Thu Nov 1 12:28:31 2018 +0100

    doc: Add German translation.
    
    * doc/contributing.de.texi: New file.
    * doc/guix.de.texi: New file
    * doc/local.mk (TRANSLATED_INFO): Add them.
    (info_TEXINFOS): Add guix.de.texi.
    * po/doc/guix-manual.de.po: New file.
    * po/doc/local.mk (EXTRA_DIST): Add it.
    * doc/guix.texi: Document the German translation.
---
 doc/contributing.de.texi        |   537 +
 doc/{guix.texi => guix.de.texi} | 16875 ++++++++--------
 doc/guix.texi                   |     5 +-
 doc/local.mk                    |     5 +-
 po/doc/guix-manual.de.po        | 39797 ++++++++++++++++++++++++++++++++++++++
 po/doc/local.mk                 |     1 +
 6 files changed, 48648 insertions(+), 8572 deletions(-)

diff --git a/doc/contributing.de.texi b/doc/contributing.de.texi
new file mode 100644
index 0000000..6c302ad
--- /dev/null
+++ b/doc/contributing.de.texi
@@ -0,0 +1,537 @@
address@hidden Mitwirken
address@hidden Mitwirken
+
+Dieses Projekt basiert auf Kooperation, daher benötigen wir Ihre Hilfe, um
+es wachsen zu lassen! Bitte kontaktieren Sie uns auf
address@hidden@@gnu.org} und @code{#guix} im Freenode-IRC-Netzwerk. Wir
+freuen uns auf Ihre Ideen, Fehlerberichte, Patches und alles, was hilfreich
+für das Projekt ist. Besonders willkommen ist Hilfe bei der Erstellung von
+Paketen (@pxref{Paketrichtlinien}).
+
address@hidden Verhaltensregeln, für Mitwirkende
address@hidden Verhaltenskodex für Mitwirkende
+Wir möchten eine angenehme, freundliche und von Belästigungen freie Umgebung
+bereitstellen, so dass jeder Beiträge nach seinen Fähigkeiten leisten
+kann. Zu diesem Zweck verwendet unser Projekt einen »Verhaltenskodex für
+Mitwirkende«, der von @url{http://contributor-covenant.org/} übernommen
+wurde. Eine übersetzte Fassung finden Sie auf
address@hidden://www.contributor-covenant.org/de/version/1/4/code-of-conduct}
+sowie eine mitgelieferte, englische Fassung in der Datei
address@hidden im Quellbaum.
+
+Von Mitwirkenden wird nicht erwartet, dass sie in Patches oder in der
+Online-Kommunikation ihre echten Namen preisgeben. Sie können einen
+beliebigen Namen oder ein Pseudonym ihrer Wahl verwenden.
+
address@hidden
+* Erstellung aus dem Git::   Das Neueste und Beste.
+* Guix vor der Installation ausführen::  Hacker-Tricks.
+* Perfekt eingerichtet::     Die richtigen Werkzeuge.
+* Code-Stil::                Wie Mitwirkende hygienisch arbeiten.
+* Einreichen von Patches::   Teilen Sie Ihre Arbeit.
address@hidden menu
+
address@hidden Erstellung aus dem Git
address@hidden Erstellung aus dem Git
+
+Wenn Sie an Guix selbst hacken wollen, ist es empfehlenswert, dass Sie die
+neueste Version aus dem Git-Softwarebestand verwenden:
+
address@hidden
+git clone https://git.savannah.gnu.org/git/guix.git
address@hidden example
+
+Wenn Sie Guix aus einem Checkout erstellen, sind außer den bereits in den
+Installationsanweisungen genannten Paketen weitere nötig
+(@pxref{Voraussetzungen}).
+
address@hidden
address@hidden @url{http://gnu.org/software/autoconf/, GNU Autoconf};
address@hidden @url{http://gnu.org/software/automake/, GNU Automake};
address@hidden @url{http://gnu.org/software/gettext/, GNU Gettext};
address@hidden @url{http://gnu.org/software/texinfo/, GNU Texinfo};
address@hidden @url{http://www.graphviz.org/, Graphviz};
address@hidden @url{http://www.gnu.org/software/help2man/, GNU Help2man 
(optional)}.
address@hidden itemize
+
+Der einfachste Weg, eine Entwicklungsumgebung für Guix einzurichten, ist
+natürlich, Guix zu benutzen! Der folgende Befehl startet eine neue Shell, in
+der alle Abhängigkeiten und Umgebungsvariablen bereits eingerichtet sind, um
+an Guix zu arbeiten:
+
address@hidden
+guix environment guix
address@hidden example
+
+In @xref{Aufruf von guix environment} finden Sie weitere Informationen zu
+diesem Befehl. Zusätzliche Abhängigkeiten können mit @option{--ad-hoc}
+hinzugefügt werden:
+
address@hidden
+guix environment guix --ad-hoc help2man git strace
address@hidden example
+
+Führen Sie @command{./bootstrap} aus, um die Infrastruktur des
+Erstellungssystems mit Autoconf und Automake zu erstellen. Möglicherweise
+erhalten Sie eine Fehlermeldung wie diese:
+
address@hidden
+configure.ac:46: error: possibly undefined macro: PKG_CHECK_MODULES
address@hidden example
+
address@hidden
+Das bedeutet wahrscheinlich, dass Autoconf @file{pkg.m4} nicht finden
+konnte, welches von pkg-config bereitgestellt wird. Stellen Sie sicher, dass
address@hidden verfügbar ist. Gleiches gilt für den von Guile
+bereitgestellten Makrosatz @file{guile.m4}. Wenn Sie beispielsweise Automake
+in @file{/usr/local} installiert haben, würde in @file{/usr/share} nicht
+nach @file{.m4}-Dateien geschaut. In einem solchen Fall müssen Sie folgenden
+Befehl aufrufen:
+
address@hidden
+export ACLOCAL_PATH=/usr/share/aclocal
address@hidden example
+
+In @xref{Macro Search Path,,, automake, The GNU Automake Manual} finden Sie
+weitere Informationen.
+
+Dann führen Sie wie gewohnt @command{./configure} aus. Achten Sie darauf,
address@hidden@var{Verzeichnis}} zu übergeben, wobei
address@hidden der von Ihrer aktuellen Installation verwendete
address@hidden ist (weitere Informationen auf @pxref{Der Store}).
+
+Zum Schluss müssen Sie @code{make check} aufrufen, um die Tests auszuführen
+(@pxref{Die Testsuite laufen lassen}). Falls etwas fehlschlägt, werfen Sie 
einen
+Blick auf die Installationsanweisungen (@pxref{Installation}) oder senden
+Sie eine E-Mail an @email{guix-devel@@gnu.org, Mailingliste}.
+
+
address@hidden Guix vor der Installation ausführen
address@hidden Guix vor der Installation ausführen
+
+Um eine gesunde Arbeitsumgebung zu behalten, ist es hilfreich, die im
+lokalen Quellbaum vorgenommenen Änderungen zunächst zu testen, ohne sie
+tatsächlich zu installieren. So können Sie zwischen Ihrem
+Endnutzer-»Straßenanzug« und Ihrem »Faschingskostüm« unterscheiden.
+
+To that end, all the command-line tools can be used even if you have not run
address@hidden install}.  To do that, you first need to have an environment with
+all the dependencies available (@pxref{Erstellung aus dem Git}), and then 
simply
+prefix each command with @command{./pre-inst-env} (the @file{pre-inst-env}
+script lives in the top build tree of Guix), as address@hidden @option{-E}
+flag to @command{sudo} guarantees that @code{GUILE_LOAD_PATH} is correctly
+set such that @command{guix-daemon} and the tools it uses can find the Guile
+modules they need.}:
+
address@hidden
+$ sudo -E ./pre-inst-env guix-daemon --build-users-group=guixbuild
+$ ./pre-inst-env guix build hello
address@hidden example
+
address@hidden
+Entsprechend, um eine Guile-Sitzung zu öffnen, die die Guix-Module benutzt:
+
address@hidden
+$ ./pre-inst-env guile -c '(use-modules (guix utils)) (pk (%current-system))'
+
+;;; ("x86_64-linux")
address@hidden example
+
address@hidden
address@hidden REPL
address@hidden Lese-Auswerten-Schreiben-Schleife
address@hidden und auf einer REPL (@pxref{Using Guile Interactively,,, guile, 
Guile
+Reference Manual}):
+
address@hidden
+$ ./pre-inst-env guile
+scheme@@(guile-user)> ,use(guix)
+scheme@@(guile-user)> ,use(gnu)
+scheme@@(guile-user)> (define snakes
+                       (fold-packages
+                         (lambda (package lst)
+                           (if (string-prefix? "python"
+                                               (package-name package))
+                               (cons package lst)
+                               lst))
+                         '()))
+scheme@@(guile-user)> (length snakes)
+$1 = 361
address@hidden example
+
+Das @command{pre-inst-env}-Skript richtet alle Umgebungsvariablen ein, die
+nötig sind, um dies zu ermöglichen, einschließlich @env{PATH} und
address@hidden
+
+Beachten Sie, dass @command{./pre-inst-env guix pull} den lokalen Quellbaum
address@hidden aktualisiert; es aktualisiert lediglich die symbolische
+Verknüpfung @file{~/.config/guix/current} (@pxref{Aufruf von guix pull}).  Um
+Ihren lokalen Quellbaum zu aktualisieren, müssen Sie stattdessen
address@hidden pull} benutzen.
+
+
address@hidden Perfekt eingerichtet
address@hidden Perfekt eingerichtet
+
+Um perfekt für das Hacken an Guix eingerichtet zu sein, brauchen Sie an sich
+dasselbe wie um perfekt für das Hacken mit Guile (@pxref{Using Guile in
+Emacs,,, guile, Guile Reference Manual}).  Zunächst brauchen Sie mehr als
+ein Textverarbeitungsprogramm, Sie brauchen
address@hidden://www.gnu.org/software/emacs, Emacs}, ermächtigt vom wunderbaren
address@hidden://nongnu.org/geiser/, Geiser}.
+
+Geiser ermöglicht interaktive und inkrementelle Entwicklung aus Emacs
+heraus: Code kann in Puffern kompiliert und ausgewertet werden. Zugang zu
+Online-Dokumentation (Docstrings) steht ebenso zur Verfügung wie
+kontextabhängige Vervollständigung, @kbd{M-.} um zu einer Objektdefinition
+zu springen, eine REPL, um Ihren Code auszuprobieren, und mehr
+(@pxref{Einführung,,, geiser, Geiser User Manual}). Zur bequemen
+Guix-Entwicklung sollten Sie Guiles Ladepfad so ergänzen, dass die
+Quelldateien in Ihrem Checkout gefunden werden.
+
address@hidden
+;; @r{Angenommen das Guix-Checkout ist in ~/src/guix.}
+(with-eval-after-load 'geiser-guile
+  (add-to-list 'geiser-guile-load-path "~/src/guix"))
address@hidden lisp
+
+Um den Code tatsächlich zu bearbeiten, bietet Emacs schon einen netten
+Scheme-Modus. Aber Sie dürfen auch
address@hidden://www.emacswiki.org/emacs/ParEdit, Paredit} nicht verpassen. Es
+bietet Hilfsmittel, um direkt mit dem Syntaxbaum zu arbeiten, und kann so
+zum Beispiel einen S-Ausdruck hochheben oder ihn umhüllen, ihn verschlucken
+oder den nachfolgenden S-Ausdruck verwerfen, etc.
+
address@hidden Code-Schnipsel
address@hidden Vorlagen
address@hidden Tipparbeit sparen
+Wir bieten auch Vorlagen für häufige Git-Commit-Nachrichten und
+Paketdefinitionen im Verzeichnis @file{etc/snippets}. Diese Vorlagen können
+mit @url{http://joaotavora.github.io/yasnippet/, YASnippet} zusammen benutzt
+werden, um kurze Auslöse-Zeichenketten zu interaktiven Textschnipseln
+umzuschreiben. Vielleicht möchten Sie das Schnipselverzeichnis zu Ihrer
address@hidden in Emacs hinzufügen.
+
address@hidden
+;; @r{Angenommen das Guix-Checkout ist in ~/src/guix.}
+(with-eval-after-load 'yasnippet
+  (add-to-list 'yas-snippet-dirs "~/src/guix/etc/snippets"))
address@hidden lisp
+
+The commit message snippets depend on @url{https://magit.vc/, Magit} to
+display staged files.  When editing a commit message type @code{add}
+followed by @kbd{TAB} to insert a commit message template for adding a
+package; type @code{update} followed by @kbd{TAB} to insert a template for
+updating a package; type @code{https} followed by @kbd{TAB} to insert a
+template for changing the home page URI of a package to HTTPS.
+
+Das Hauptschnipsel für @code{scheme-mode} wird ausgelöst, indem Sie
address@hidden gefolgt von @kbd{TAB} eintippen. Dieses Snippet fügt auch
+die Auslöse-Zeichenkette @code{origin...} ein, die danach weiter
+umgeschrieben werden kann. Das @code{origin}-Schnipsel kann wiederum andere
+Auslöse-Zeichenketten einfügen, die alle auf @code{...} enden, was selbst
+wieder weiter umgeschrieben werden kann.
+
+
address@hidden Code-Stil
address@hidden Code-Stil
+
+Im Allgemeinen folgt unser Code den GNU Coding Standards (@pxref{Top,,,
+standards, GNU Coding Standards}). Da diese aber nicht viel über Scheme zu
+sagen haben, folgen hier einige zusätzliche Regeln.
+
address@hidden
+* Programmierparadigmen::    Wie Sie Ihre Elemente zusammenstellen.
+* Module::                   Wo Sie Ihren Code unterbringen.
+* Datentypen und Mustervergleich::  Implementierung von Datenstrukturen.
+* Formatierung von Code::    Schreibkonventionen.
address@hidden menu
+
address@hidden Programmierparadigmen
address@hidden Programmierparadigmen
+
+Scheme-Code wird in Guix auf rein funktionale Weise geschrieben. Eine
+Ausnahme ist Code, der mit Ein- und Ausgabe zu tun hat, und Prozeduren, die
+grundlegende Konzepte implementieren, wie zum Beispiel die Prozedur
address@hidden
+
address@hidden Module
address@hidden Module
+
+Guile-Module, die beim Erstellen nutzbar sein sollen, müssen im Namensraum
address@hidden(guix build @dots{})} leben. Sie dürfen auf keine anderen Guix- 
oder
+GNU-Modules Bezug nehmen. Jedoch ist es in Ordnung, wenn ein »wirtsseitiges«
+Modul ein erstellungsseitiges Modul benutzt.
+
+Module, die mit dem weiteren GNU-System zu tun haben, sollten im Namensraum
address@hidden(gnu @dots{})} und nicht in @code{(guix @dots{})} stehen.
+
address@hidden Datentypen und Mustervergleich
address@hidden Datentypen und Mustervergleich
+
+Im klassischen Lisp gibt es die Tendenz, Listen zur Darstellung von allem zu
+benutzen, und diese dann »händisch« zu durchlaufen mit @code{car},
address@hidden, @code{cadr} und so weiter. Dieser Stil ist aus verschiedenen
+Gründen problematisch, insbesondere wegen der Tatsache, dass er schwer zu
+lesen, schnell fehlerbehaftet und ein Hindernis beim Melden von Typfehlern
+ist.
+
+Guix-Code sollte angemessene Datentypen definieren (zum Beispiel mit
address@hidden) statt Listen zu missbrauchen. Außerdem sollte er
+das @code{(ice-9 match)}-Modul von Guile zum Mustervergleich benutzen,
+besonders mit Listen.
+
address@hidden Formatierung von Code
address@hidden Formatierung von Code
+
address@hidden Formatierung von Code
address@hidden Code-Stil
+Beim Schreiben von Scheme-Code halten wir uns an die üblichen
+Gepflogenheiten unter Scheme-Programmierern. Im Allgemeinen bedeutet das,
+dass wir uns an @url{http://mumble.net/~campbell/scheme/style.txt,
+Riastradh's Lisp Style Rules} halten. Es hat sich ergeben, dass dieses
+Dokument auch die Konventionen beschreibt, die im Code von Guile
+hauptsächlich verwendet werden. Es ist gut durchdacht und schön geschrieben,
+also lesen Sie es bitte.
+
+Ein paar in Guix eingeführte Sonderformen, wie zum Beispiel das
address@hidden, haben abweichende Regeln für die Einrückung. Diese
+sind in der Datei @file{.dir-locals.el} definiert, die Emacs automatisch
+benutzt. Beachten Sie auch, dass Emacs-Guix einen Modus namens
address@hidden bereitstellt, der Guix-Code richtig einrückt und
+hervorhebt (@pxref{Development,,, emacs-guix, The Emacs-Guix Reference
+Manual}).
+
address@hidden Einrückung, Code-
address@hidden Formatierung, Code-
+Falls Sie nicht Emacs verwenden, sollten Sie sicherstellen, dass Ihr Editor
+diese Regeln kennt. Um eine Paketdefinition automatisch einzurücken, können
+Sie auch Folgendes ausführen:
+
address@hidden
+./etc/indent-code.el gnu/packages/@var{Datei}.scm @var{Paket}
address@hidden example
+
address@hidden
+Dadurch wird die Definition von @var{Paket} in
address@hidden/packages/@var{Datei}.scm} automatisch eingerückt, indem Emacs im
+Batch-Modus läuft. Um die Einrückung in einer gesamten Datei vorzunehmen,
+lassen Sie das zweite Argument weg:
+
address@hidden
+./etc/indent-code.el gnu/services/@var{Datei}.scm
address@hidden example
+
address@hidden Vim, zum Editieren von Scheme-Code
+Wenn Sie mit Code mit Vim bearbeiten, empfehlen wir, dass Sie @code{:set
+autoindent} ausführen, damit Ihr Code automatisch eingerückt wird, während
+Sie ihn schreiben. Außerdem könnte Ihnen
address@hidden://www.vim.org/scripts/script.php?script_id=3998,
address@hidden dabei helfen, mit all diesen Klammern fertigzuwerden.
+
+Wir fordern von allen Prozeduren auf oberster Ebene, dass sie über einen
+Docstring verfügen. Diese Voraussetzung kann jedoch bei einfachen, privaten
+Prozeduren im Namensraum @code{(guix build @dots{})} aufgeweicht werden.
+
+Prozeduren sollten nicht mehr als vier positionsbestimmte Parameter
+haben. Benutzen Sie Schlüsselwort-Parameter für Prozeduren, die mehr als
+vier Parameter entgegennehmen.
+
+
address@hidden Einreichen von Patches
address@hidden Einreichen von Patches
+
+Die Entwicklung wird mit Hilfe des verteilten Versionskontrollsystems Git
+durchgeführt. Daher ist eine ständige Verbindung zum Repository nicht
+unbedingt erforderlich. Wir begrüßen Beiträge in Form von Patches, die
+mittels @code{git format-patch} erstellt und an die Mailingliste
address@hidden@@gnu.org} geschickt werden.
+
+Diese Mailing-Liste setzt auf einer Debbugs-Instanz auf, die zugänglich ist
+unter @uref{https://bugs.gnu.org/guix-patches}, wodurch wir den Überblick
+über Eingereichtes behalten können. Jede an diese Mailing-Liste gesendete
+Nachricht bekommt eine neue Folgenummer zugewiesen, so dass man eine
+Folge-Email zur Einreichung an @address@hidden@@debbugs.gnu.org} senden
+kann, wobei @var{NNN} für die Folgenummer steht (@pxref{Senden einer 
Patch-Reihe}).
+
+Bitte schreiben Sie Commit-Logs im ChangeLog-Format (@pxref{Change Logs,,,
+standards, GNU Coding Standards}); dazu finden Sie Beispiele unter den
+bisherigen Commits.
+
+Bevor Sie einen Patch einreichen, der eine Paketdefinition hinzufügt oder
+verändert, gehen Sie bitte diese Prüfliste:
+
address@hidden
address@hidden
+Wenn die Autoren der verpackten Software eine kryptographische Signatur für
+den Tarball der Veröffentlichung anbieten, so machen Sie sich bitte die
+Mühe, die Echtheit des Archivs zu überprüfen.  Für eine abgetrennte
+GPG-Signaturdatei würden Sie das mit dem Befehl @code{gpg --verify} tun.
+
address@hidden
+Nehmen Sie sich die Zeit, eine passende Zusammenfassung und Beschreibung für
+das Paket zu verfassen. Unter @xref{Zusammenfassungen und Beschreibungen} 
finden Sie
+dazu einige Richtlinien.
+
address@hidden
+Verwenden Sie @code{guix lint @var{Paket}}, wobei @var{Paket} das neue oder
+geänderte Paket bezeichnet, und beheben Sie alle gemeldeten Fehler
+(@pxref{Aufruf von guix lint}).
+
address@hidden
+Stellen Sie sicher, dass das Paket auf Ihrer Plattform erstellt werden kann,
+indem Sie @code{guix build @var{Paket}} ausführen.
+
address@hidden
address@hidden gebündelt
+Achten Sie darauf, dass im Paket keine Software gebündelt mitgeliefert wird,
+die bereits in separaten Paketen zur Verfügung steht.
+
+Manchmal enthalten Pakete Kopien des Quellcodes ihrer Abhängigkeiten, um
+Nutzern die Installation zu erleichtern. Als eine Distribution wollen wir
+jedoch sicherstellen, dass für solche Pakete die schon in der Distribution
+verfügbare Fassung benutzen, sofern es eine gibt. Dadurch wird sowohl der
+Ressourcenverbrauch optimiert (die Abhängigkeit wird so nur einmal erstellt
+und gespeichert) als auch der Distribution die Möglichkeit gegeben,
+ergänzende Änderungen durchzuführen, um beispielsweise
+Sicherheitsaktualisierungen für ein bestimmtes Paket an nur einem Ort
+einzuspielen, die das gesamte System betreffen — gebündelt mitgelieferte
+Kopien würden dies verhindern.
+
address@hidden
+Schauen Sie sich das von @command{guix size} ausgegebene Profil an
+(@pxref{Aufruf von guix size}). Dadurch können Sie Referenzen auf andere
+Pakete finden, die ungewollt vorhanden sind. Dies kann auch dabei helfen, zu
+entscheiden, ob das Paket aufgespalten werden sollte (@pxref{Pakete mit 
mehreren Ausgaben.}) und welche optionalen Abhängigkeiten verwendet werden
+sollten.
+
address@hidden
+Achten Sie bei wichtigen Änderungen darauf, dass abhängige Pakete (falls
+vorhanden) nicht von der Änderung beeinträchtigt werden; @code{guix refresh
+--list-dependent @var{Paket}} hilft Ihnen dabei (@pxref{Aufruf von guix 
refresh}).
+
address@hidden 
===========================================================================
address@hidden
address@hidden This file was generated with po4a. Translate the source file.
address@hidden
address@hidden 
===========================================================================
address@hidden See 
<https://lists.gnu.org/archive/html/guix-devel/2016-10/msg00933.html>.
address@hidden Branching-Strategie
address@hidden Neuerstellungs-Zeitplan
+Je nachdem, wieviele abhängige Pakete es gibt, und entsprechend wieviele
+Neuerstellungen dadurch nötig würden, finden Commits auf anderen Branches
+statt, nach ungefähr diesen Regeln:
+
address@hidden @asis
address@hidden 300 abhängige Pakete oder weniger
address@hidden (störfreie Änderungen).
+
address@hidden zwischen 300 und 1200 abhängige Pakete
address@hidden (störfreie Änderungen). Dieser Branch wird circa alle
+3 Wochen in @code{master} gemerget. Themenbezogene Änderungen (z.B. eine
+Aktualisierung der GNOME-Plattform) können stattdessen auch auf einem
+eigenen Branch umgesetzt werden (wie @code{gnome-updates}).
+
address@hidden mehr als 1200 abhängige Pakete
address@hidden (kann auch größere und womöglich andere Software
+beeinträchtigende Änderungen umfassen). Dieser Branch wird planmäßig in
address@hidden alle 2,5 Monate oder so gemerget.
address@hidden table
+
+All diese Branches werden kontinuierlich
address@hidden://hydra.gnu.org/project/gnu, auf unserer Build-Farm} erstellt
+und in @code{master} gemerget, sobald alles erfolgreich erstellt worden
+ist. Dadurch können wir Probleme beheben, bevor sie bei Nutzern auftreten,
+und zudem das Zeitfenster, während dessen noch keine vorerstellten
+Binärdateien verfügbar sind, verkürzen.
+
address@hidden TODO: It would be good with badges on the website that tracks 
these
address@hidden branches.  Or maybe even a status page.
+Im Allgemeinen werden Branches außer @code{master} als @emph{unveränderlich}
+angesehen, wenn sie kürzlich ausgewertet wurden oder ein entsprechender
address@hidden existiert. Bitte fragen Sie auf der Mailing-Liste oder
+IRC, wenn Sie sich nicht sicher sind, wo ein Patch eingespielt werden
+sollte.
+
address@hidden
address@hidden Determinismus, von Erstellungsprozessen
address@hidden Reproduzierbare Erstellungen, Überprüfung
+Überprüfen Sie, ob der Erstellungsprozess deterministisch ist. Dazu prüfen
+Sie typischerweise, ob eine unabhängige Erstellung des Pakets genau dasselbe
+Ergebnis wie Ihre Erstellung hat, Bit für Bit.
+
+Dies können Sie leicht tun, indem Sie dasselbe Paket mehrere Male
+hintereinander auf Ihrer Maschine erstellen (@pxref{Aufruf von guix build}):
+
address@hidden
+guix build --rounds=2 mein-paket
address@hidden example
+
+Dies reicht aus, um eine ganze Klasse häufiger Ursachen von
+Nichtdeterminismus zu finden, wie zum Beispiel Zeitstempel oder
+zufallsgenerierte Ausgaben im Ergebnis der Erstellung.
+
+Eine weitere Möglichkeit ist, @command{guix challenge} (@pxref{Aufruf von guix 
challenge}) zu benutzen. Sie können es ausführen, sobald ein Paket commitet
+und von @code{hydra.gnu.org} erstellt wurde, um zu sehen, ob dort dasselbe
+Ergebnis wie bei Ihnen geliefert wurde. Noch besser: Finden Sie eine andere
+Maschine, die das Paket erstellen kann, und führen Sie @command{guix
+publish} aus. Da sich die entfernte Erstellungsmaschine wahrscheinlich von
+Ihrer unterscheidet, können Sie auf diese Weise Probleme durch
+Nichtdeterminismus erkennen, die mit der Hardware zu tun haben — zum
+Beispiel die Nutzung anderer Befehlssatzerweiterungen — oder mit dem
+Betriebssystem-Kernel — zum Beispiel, indem @code{uname} oder
address@hidden/proc}-Dateien verwendet werden.
+
address@hidden
+Beim Schreiben von Dokumentation achten Sie bitte auf eine
+geschlechtsneutrale Wortwahl, wenn Sie sich auf Personen beziehen, wie
address@hidden://en.wikipedia.org/wiki/Singular_they, address@hidden
address@hidden »them« im Singular}, und so weiter.
+
address@hidden
+Stelllen Sie sicher, dass Ihr Patch nur einen Satz zusammengehöriger
+Änderungen umfasst. Das Zusammenfassen nicht zusammengehöriger Änderungen
+erschwert und bremst das Durchsehen Ihres Patches.
+
+Beispiele für nicht zusammengehörige Änderungen sind das Hinzufügen mehrerer
+Pakete auf einmal, oder das Aktualisieren eines Pakets auf eine neue Version
+zusammen mit Fehlerbehebungen für das Paket.
+
address@hidden
+Bitte befolgen Sie unsere Richtlinien für die Code-Formatierung, womöglich
+wollen Sie dies automatisch tun lassen durch das Skript
address@hidden/indent-code.el} (@pxref{Formatierung von Code}).
+
address@hidden
+When possible, use mirrors in the source URL (@pxref{Aufruf von guix 
download}).  Use reliable URLs, not generated ones.  For instance, GitHub
+archives are not necessarily identical from one generation to the next, so
+in this case it's often better to clone the repository.  Don't use the
address@hidden field in the URL: it is not very useful and if the name
+changes, the URL will probably be wrong.
+
address@hidden enumerate
+
+Bitte benutzen Sie @samp{[PATCH] @dots{}} als Betreff, wenn Sie einen Patch
+an die Mailing-Liste schicken. Sie können dazu Ihr E-mail-Programm oder den
+Befehl @command{git send-email} benutzen (@pxref{Senden einer Patch-Reihe}). 
Wir bevorzugen es, Patches als reine Textnachrichten zu erhalten,
+entweder eingebettet (inline) oder als MIME-Anhänge. Sie sind dazu
+angehalten, zu überprüfen, ob Ihr Mail-Programm solche Dinge wie
+Zeilenumbrüche oder die Einrückung verändert, wodurch die Patches womöglich
+nicht mehr funktionieren.
+
+Wenn dadurch ein Fehler behoben wurde, schließen Sie bitte den Thread, indem
+Sie eine E-mail an @address@hidden@@debbugs.gnu.org} senden.
+
address@hidden Senden einer Patch-Reihe
address@hidden einer Patch-Reihe}
address@hidden Patch-Reihe
address@hidden @code{git send-email}
address@hidden @code{git-send-email}
+
address@hidden Debbugs bug: https://debbugs.gnu.org/db/15/15361.html
+Wenn Sie eine Patch-Reihe senden (z.B. mit @code{git send-email}), schicken
+Sie bitte als Erstes eine Nachricht an @email{guix-patches@@gnu.org} und
+dann nachfolgende Patches an @address@hidden@@debbugs.gnu.org}, um
+sicherzustellen, dass sie zusammen bearbeitet werden. Siehe
address@hidden://debbugs.gnu.org/Advanced.html, die Debbugs-Dokumentation} für
+weitere Informationen.
diff --git a/doc/guix.texi b/doc/guix.de.texi
similarity index 58%
copy from doc/guix.texi
copy to doc/guix.de.texi
index b41af61..e2138db 100644
--- a/doc/guix.texi
+++ b/doc/guix.de.texi
@@ -1,90 +1,96 @@
 \input texinfo
address@hidden 
===========================================================================
address@hidden
address@hidden This file was generated with po4a. Translate the source file.
address@hidden
address@hidden 
===========================================================================
 @c -*-texinfo-*-
 
 @c %**start of header
address@hidden guix.info
address@hidden guix.de.info
 @documentencoding UTF-8
address@hidden GNU Guix Reference Manual
address@hidden de
address@hidden on
address@hidden Referenzhandbuch zu GNU Guix
 @c %**end of header
 
address@hidden version.texi
address@hidden version-de.texi
 
 @c Identifier of the OpenPGP key used to sign tarballs and such.
 @set OPENPGP-SIGNING-KEY-ID 3CE464558A84FDC69DB40CFB090B11993D9AEBB5
 
 @copying
-Copyright @copyright{} 2012, 2013, 2014, 2015, 2016, 2017, 2018 Ludovic 
address@hidden
-Copyright @copyright{} 2013, 2014, 2016 Andreas address@hidden
-Copyright @copyright{} 2013 Nikita address@hidden
-Copyright @copyright{} 2014, 2015, 2016 Alex address@hidden
-Copyright @copyright{} 2015, 2016 Mathieu address@hidden
-Copyright @copyright{} 2014 Pierre-Antoine address@hidden
-Copyright @copyright{} 2015 Taylan Ulrich Bayırlı/address@hidden
-Copyright @copyright{} 2015, 2016, 2017 Leo address@hidden
-Copyright @copyright{} 2015, 2016, 2017, 2018 Ricardo address@hidden
-Copyright @copyright{} 2016 Ben address@hidden
-Copyright @copyright{} 2016, 2017, 2018 Chris address@hidden
-Copyright @copyright{} 2016, 2017, 2018 Efraim address@hidden
-Copyright @copyright{} 2016 John address@hidden
-Copyright @copyright{} 2016, 2017 Nils address@hidden
-Copyright @copyright{} 2016, 2017, 2018 Jan address@hidden
-Copyright @copyright{} 2016 Julien address@hidden
-Copyright @copyright{} 2016 Alex ter address@hidden
-Copyright @copyright{} 2017, 2018 Clément address@hidden
-Copyright @copyright{} 2017 Mathieu address@hidden
-Copyright @copyright{} 2017 Federico address@hidden
-Copyright @copyright{} 2017, 2018 Carlo address@hidden
-Copyright @copyright{} 2017 Thomas address@hidden
-Copyright @copyright{} 2017 address@hidden
-Copyright @copyright{} 2017 Christopher Allan address@hidden
-Copyright @copyright{} 2017, 2018 Marius address@hidden
-Copyright @copyright{} 2017 Hartmut address@hidden
-Copyright @copyright{} 2017 Maxim address@hidden
-Copyright @copyright{} 2017, 2018 Tobias address@hidden
-Copyright @copyright{} 2017 George address@hidden
-Copyright @copyright{} 2017 Andy address@hidden
-Copyright @copyright{} 2017, 2018 Arun address@hidden
-Copyright @copyright{} 2017 address@hidden
-Copyright @copyright{} 2018 Rutger address@hidden
-Copyright @copyright{} 2018 Oleg address@hidden
-Copyright @copyright{} 2018 Mike address@hidden
-Copyright @copyright{} 2018 Pierre-Antoine address@hidden
-Copyright @copyright{} 2018 Gábor address@hidden
-Copyright @copyright{} 2018 Florian address@hidden
-
-Permission is granted to copy, distribute and/or modify this document
-under the terms of the GNU Free Documentation License, Version 1.3 or
-any later version published by the Free Software Foundation; with no
-Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.  A
-copy of the license is included in the section entitled ``GNU Free
-Documentation License''.
+Copyright @copyright{} 2012, 2013, 2014, 2015, 2016, 2017, 2018 Ludovic
address@hidden Copyright @copyright{} 2013, 2014, 2016 Andreas address@hidden 
Copyright
address@hidden 2013 Nikita address@hidden Copyright @copyright{} 2014, 2015,
+2016 Alex address@hidden Copyright @copyright{} 2015, 2016 Mathieu 
address@hidden
+Copyright @copyright{} 2014 Pierre-Antoine address@hidden Copyright 
@copyright{}
+2015 Taylan Ulrich Bayırlı/address@hidden Copyright @copyright{} 2015, 2016, 
2017
+Leo address@hidden Copyright @copyright{} 2015, 2016, 2017, 2018 Ricardo
address@hidden Copyright @copyright{} 2016 Ben address@hidden Copyright 
@copyright{}
+2016, 2017, 2018 Chris address@hidden Copyright @copyright{} 2016, 2017, 2018
+Efraim address@hidden Copyright @copyright{} 2016 John address@hidden Copyright
address@hidden 2016, 2017 Nils address@hidden Copyright @copyright{} 2016, 2017,
+2018 Jan address@hidden Copyright @copyright{} 2016 Julien address@hidden
+Copyright @copyright{} 2016 Alex ter address@hidden Copyright @copyright{} 
2017,
+2018 Clément address@hidden Copyright @copyright{} 2017 Mathieu address@hidden
+Copyright @copyright{} 2017 Federico address@hidden Copyright @copyright{} 
2017,
+2018 Carlo address@hidden Copyright @copyright{} 2017 Thomas address@hidden
+Copyright @copyright{} 2017 address@hidden Copyright @copyright{} 2017
+Christopher Allan address@hidden Copyright @copyright{} 2017, 2018 Marius 
address@hidden
+Copyright @copyright{} 2017 Hartmut address@hidden Copyright @copyright{} 2017
+Maxim address@hidden Copyright @copyright{} 2017, 2018 Tobias address@hidden
+Copyright @copyright{} 2017 George address@hidden Copyright @copyright{} 2017
+Andy address@hidden Copyright @copyright{} 2017, 2018 Arun address@hidden 
Copyright
address@hidden 2017 address@hidden Copyright @copyright{} 2018 Rutger 
address@hidden
+Copyright @copyright{} 2018 Oleg address@hidden Copyright @copyright{} 2018 
Mike
address@hidden Copyright @copyright{} 2018 Pierre-Antoine address@hidden 
Copyright
address@hidden 2018 Gábor address@hidden Copyright @copyright{} 2018 Florian
address@hidden
+
+Es ist Ihnen gestattet, dieses Dokument zu vervielfältigen, weiterzugeben
+und/oder zu verändern, unter den Bedingungen der GNU Free Documentation
+License, entweder gemäß Version 1.3 der Lizenz oder (nach Ihrer Option)
+einer späteren Version, die von der Free Software Foundation veröffentlicht
+wurde, ohne unveränderliche Abschnitte, ohne vorderen Umschlagtext und ohne
+hinteren Umschlagtext. Eine Kopie der Lizenz finden Sie im Abschnitt mit dem
+Titel »GNU Free Documentation License«.
 @end copying
 
address@hidden System administration
address@hidden Systemadministration
 @direntry
-* Guix: (guix).       Manage installed software and system configuration.
-* guix package: (guix)Invoking guix package.  Installing, removing, and 
upgrading packages.
-* guix gc: (guix)Invoking guix gc.            Reclaiming unused disk space.
-* guix pull: (guix)Invoking guix pull.        Update the list of available 
packages.
-* guix system: (guix)Invoking guix system.    Manage the operating system 
configuration.
+* Guix: (guix.de).           Installierte Software und Systemkonfigurationen 
+                               verwalten.
+* guix package: (guix.de)guix package aufrufen.  Pakete installieren, 
+                                                   entfernen und 
+                                                   aktualisieren.
+* guix gc: (guix.de)guix gc aufrufen.  Unbenutzten Plattenspeicher wieder 
+                                         freigeben.
+* guix pull: (guix.de)guix pull aufrufen.  Die Liste verfügbarer Pakete 
+                                             aktualisieren.
+* guix system: (guix.de)guix system aufrufen.  Die 
+                                                 Betriebssystemkonfiguration 
+                                                 verwalten.
 @end direntry
 
address@hidden Software development
address@hidden Softwareentwicklung
 @direntry
-* guix environment: (guix)Invoking guix environment. Building development 
environments with Guix.
-* guix build: (guix)Invoking guix build.      Building packages.
-* guix pack: (guix)Invoking guix pack.        Creating binary bundles.
+* guix environment: (guix.de)guix environment aufrufen.  Umgebungen für 
+                                                           Entwickler 
+                                                           erstellen
+* guix build: (guix.de)guix build aufrufen.  Erstellen von Paketen.
+* guix pack: (guix.de)guix pack aufrufen.  Bündel aus Binärdateien 
+                                             erstellen.
 @end direntry
 
 @titlepage
address@hidden GNU Guix Reference Manual
address@hidden Using the GNU Guix Functional Package Manager
address@hidden The GNU Guix Developers
address@hidden Referenzhandbuch zu GNU Guix
address@hidden Den funktionalen Paketmanager GNU Guix benutzen
address@hidden Die GNU-Guix-Entwickler
 
 @page
 @vskip 0pt plus 1filll
-Edition @value{EDITION} @*
address@hidden @*
+Edition @value{EDITION} @* @value{UPDATED} @*
 
 @insertcopying
 @end titlepage
@@ -95,8 +101,9 @@ Edition @value{EDITION} @*
 @node Top
 @top GNU Guix
 
-This document describes GNU Guix version @value{VERSION}, a functional
-package management tool written for the GNU system.
+Dieses Dokument beschreibt GNU Guix, Version @value{VERSION}, ein
+funktionales Paketverwaltungswerkzeug, das für das GNU-System geschrieben
+wurde.
 
 @c TRANSLATORS: You can replace the following paragraph with information on
 @c how to join your own translation team and how to report issues with the
@@ -108,361 +115,430 @@ language, consider joining the
 Project}.
 
 @menu
-* Introduction::                What is Guix about?
-* Installation::                Installing Guix.
-* Package Management::          Package installation, upgrade, etc.
-* Programming Interface::       Using Guix in Scheme.
-* Utilities::                   Package management commands.
-* GNU Distribution::            Software for your friendly GNU system.
-* Contributing::                Your help needed!
-
-* Acknowledgments::             Thanks!
-* GNU Free Documentation License::  The license of this manual.
-* Concept Index::               Concepts.
-* Programming Index::           Data types, functions, and variables.
+* Einführung::              Was ist Guix überhaupt?
+* Installation::             Guix installieren.
+* Paketverwaltung::          Pakete installieren, aktualisieren usw.
+* Programmierschnittstelle::  Guix in Scheme verwenden.
+* Zubehör::                 Befehle zur Paketverwaltung.
+* GNU-Distribution::         Software für Ihr freundliches GNU-System.
+* Mitwirken::                Ihre Hilfe ist nötig!
+
+* Danksagungen::             Danke!
+* GNU-Lizenz für freie Dokumentation::  Die Lizenz dieses Handbuchs.
+* Konzeptverzeichnis::       Konzepte.
+* Programmierverzeichnis::   Datentypen, Funktionen und Variable.
 
 @detailmenu
- --- The Detailed Node Listing ---
+ --- Detaillierte Liste der Knoten ---
+
+
 
 Installation
 
-* Binary Installation::         Getting Guix running in no time!
-* Requirements::                Software needed to build and run Guix.
-* Running the Test Suite::      Testing Guix.
-* Setting Up the Daemon::       Preparing the build daemon's environment.
-* Invoking guix-daemon::        Running the build daemon.
-* Application Setup::           Application-specific setup.
-
-Setting Up the Daemon
-
-* Build Environment Setup::     Preparing the isolated build environment.
-* Daemon Offload Setup::        Offloading builds to remote machines.
-* SELinux Support::             Using an SELinux policy for the daemon.
-
-Package Management
-
-* Features::                    How Guix will make your life brighter.
-* Invoking guix package::       Package installation, removal, etc.
-* Substitutes::                 Downloading pre-built binaries.
-* Packages with Multiple Outputs::  Single source package, multiple outputs.
-* Invoking guix gc::            Running the garbage collector.
-* Invoking guix pull::          Fetching the latest Guix and distribution.
-* Channels::                    Customizing the package collection.
-* Inferiors::                   Interacting with another revision of Guix.
-* Invoking guix describe::      Display information about your Guix revision.
-* Invoking guix pack::          Creating software bundles.
-* Invoking guix archive::       Exporting and importing store files.
-
-Substitutes
-
-* Official Substitute Server::  One particular source of substitutes.
-* Substitute Server Authorization::  How to enable or disable substitutes.
-* Substitute Authentication::   How Guix verifies substitutes.
-* Proxy Settings::              How to get substitutes via proxy.
-* Substitution Failure::        What happens when substitution fails.
-* On Trusting Binaries::        How can you trust that binary blob?
-
-Programming Interface
-
-* Defining Packages::           Defining new packages.
-* Build Systems::               Specifying how packages are built.
-* The Store::                   Manipulating the package store.
-* Derivations::                 Low-level interface to package derivations.
-* The Store Monad::             Purely functional interface to the store.
-* G-Expressions::               Manipulating build expressions.
-* Invoking guix repl::          Fiddling with Guix interactively.
-
-Defining Packages
-
-* package Reference::           The package data type.
-* origin Reference::            The origin data type.
-
-Utilities
-
-* Invoking guix build::         Building packages from the command line.
-* Invoking guix edit::          Editing package definitions.
-* Invoking guix download::      Downloading a file and printing its hash.
-* Invoking guix hash::          Computing the cryptographic hash of a file.
-* Invoking guix import::        Importing package definitions.
-* Invoking guix refresh::       Updating package definitions.
-* Invoking guix lint::          Finding errors in package definitions.
-* Invoking guix size::          Profiling disk usage.
-* Invoking guix graph::         Visualizing the graph of packages.
-* Invoking guix environment::   Setting up development environments.
-* Invoking guix publish::       Sharing substitutes.
-* Invoking guix challenge::     Challenging substitute servers.
-* Invoking guix copy::          Copying to and from a remote store.
-* Invoking guix container::     Process isolation.
-* Invoking guix weather::       Assessing substitute availability.
-* Invoking guix processes::     Listing client processes.
-
-Invoking @command{guix build}
-
-* Common Build Options::        Build options for most commands.
-* Package Transformation Options::  Creating variants of packages.
-* Additional Build Options::    Options specific to 'guix build'.
-* Debugging Build Failures::    Real life packaging experience.
-
-GNU Distribution
-
-* System Installation::         Installing the whole operating system.
-* System Configuration::        Configuring the operating system.
-* Documentation::               Browsing software user manuals.
-* Installing Debugging Files::  Feeding the debugger.
-* Security Updates::            Deploying security fixes quickly.
-* Package Modules::             Packages from the programmer's viewpoint.
-* Packaging Guidelines::        Growing the distribution.
-* Bootstrapping::               GNU/Linux built from scratch.
-* Porting::                     Targeting another platform or kernel.
-
-System Installation
-
-* Limitations::                 What you can expect.
-* Hardware Considerations::     Supported hardware.
-* USB Stick and DVD Installation::  Preparing the installation medium.
-* Preparing for Installation::  Networking, partitioning, etc.
-* Proceeding with the Installation::  The real thing.
-* Installing GuixSD in a VM::   GuixSD playground.
-* Building the Installation Image::  How this comes to be.
-
-System Configuration
-
-* Using the Configuration System::  Customizing your GNU system.
-* operating-system Reference::  Detail of operating-system declarations.
-* File Systems::                Configuring file system mounts.
-* Mapped Devices::              Block device extra processing.
-* User Accounts::               Specifying user accounts.
-* Locales::                     Language and cultural convention settings.
-* Services::                    Specifying system services.
-* Setuid Programs::             Programs running with root privileges.
-* X.509 Certificates::          Authenticating HTTPS servers.
-* Name Service Switch::         Configuring libc's name service switch.
-* Initial RAM Disk::            Linux-Libre bootstrapping.
-* Bootloader Configuration::    Configuring the boot loader.
-* Invoking guix system::        Instantiating a system configuration.
-* Running GuixSD in a VM::      How to run GuixSD in a virtual machine.
-* Defining Services::           Adding new service definitions.
-
-Services
-
-* Base Services::               Essential system services.
-* Scheduled Job Execution::     The mcron service.
-* Log Rotation::                The rottlog service.
-* Networking Services::         Network setup, SSH daemon, etc.
-* X Window::                    Graphical display.
-* Printing Services::           Local and remote printer support.
-* Desktop Services::            D-Bus and desktop services.
-* Sound Services::              ALSA and Pulseaudio services.
-* Database Services::           SQL databases, key-value stores, etc.
-* Mail Services::               IMAP, POP3, SMTP, and all that.
-* Messaging Services::          Messaging services.
-* Telephony Services::          Telephony services.
-* Monitoring Services::         Monitoring services.
-* Kerberos Services::           Kerberos services.
-* Web Services::                Web servers.
-* Certificate Services::        TLS certificates via Let's Encrypt.
-* DNS Services::                DNS daemons.
-* VPN Services::                VPN daemons.
-* Network File System::         NFS related services.
-* Continuous Integration::      The Cuirass service.
-* Power Management Services::   Extending battery life.
-* Audio Services::              The MPD.
-* Virtualization Services::     Virtualization services.
-* Version Control Services::    Providing remote access to Git repositories.
-* Game Services::               Game servers.
-* Miscellaneous Services::      Other services.
-
-Defining Services
-
-* Service Composition::         The model for composing services.
-* Service Types and Services::  Types and services.
-* Service Reference::           API reference.
-* Shepherd Services::           A particular type of service.
-
-Packaging Guidelines
-
-* Software Freedom::            What may go into the distribution.
-* Package Naming::              What's in a name?
-* Version Numbers::             When the name is not enough.
-* Synopses and Descriptions::   Helping users find the right package.
-* Python Modules::              A touch of British comedy.
-* Perl Modules::                Little pearls.
-* Java Packages::               Coffee break.
-* Fonts::                       Fond of fonts.
-
-Contributing
-
-* Building from Git::           The latest and greatest.
-* Running Guix Before It Is Installed::  Hacker tricks.
-* The Perfect Setup::           The right tools.
-* Coding Style::                Hygiene of the contributor.
-* Submitting Patches::          Share your work.
-
-Coding Style
-
-* Programming Paradigm::        How to compose your elements.
-* Modules::                     Where to store your code?
-* Data Types and Pattern Matching::  Implementing data structures.
-* Formatting Code::             Writing conventions.
+
+
+* Aus Binärdatei installieren::  Guix installieren, ohne Zeit zu verlieren!
+* Voraussetzungen::          Zum Erstellen und Benutzen von Guix nötige 
+                               Software.
+* Die Testsuite laufen lassen::  Guix testen.
+* Den Daemon einrichten::    Wie man die Umgebung des Erstellungs-Daemons 
+                               einrichtet.
+* Aufruf des guix-daemon::   Den Erstellungs-Daemon laufen lassen.
+* Anwendungen einrichten::   Anwendungsspezifische Einstellungen.
+
+Den Daemon einrichten
+
+
+
+* Einrichten der Erstellungsumgebung::  Die isolierte Umgebung zum Erstellen 
+                                          vorbereiten.
+* Auslagern des Daemons einrichten::  Erstellungen auf entfernte Maschinen 
+                                        auslagern.
+* SELinux-Unterstützung::   Wie man eine SELinux-Richtlinie für den Daemon 
+                               einrichtet.
+
+Paketverwaltung
+
+
+
+* Funktionalitäten::        Wie Guix Ihr Leben schöner machen wird.
+* Aufruf von guix package::  Pakete installieren, entfernen usw.
+* Substitute::               Vorerstelle Binärdateien herunterladen.
+* Pakete mit mehreren Ausgaben.::  Ein Quellpaket, mehrere Ausgaben.
+* Aufruf von guix gc::       Den Müllsammler laufen lassen.
+* Aufruf von guix pull::     Das neueste Guix samt Distribution laden.
+* Channels::                 Customizing the package collection.
+* Inferiors::                Interacting with another revision of Guix.
+* Invoking guix describe::   Display information about your Guix revision.
+* Aufruf von guix pack::     Software-Bündel erstellen.
+* Aufruf von guix archive::  Import und Export von Store-Dateien.
+
+Substitute
+
+
+
+* Offizieller Substitut-Server::  Eine besondere Quelle von Substituten.
+* Substitut-Server autorisieren::  Wie man Substitute an- und abschaltet.
+* Substitutauthentifizierung::  Wie Guix Substitute verifiziert.
+* Proxy-Einstellungen::      Wie Sie Substitute über einen Proxy beziehen.
+* Fehler bei der Substitution::  Was passiert, wenn die Substitution 
+                                   fehlschlägt.
+* Vom Vertrauen gegenüber Binärdateien::  Wie können Sie diesem binären 
+                                              Blob trauen?
+
+Programmierschnittstelle
+
+
+
+* Pakete definieren::        Wie Sie neue Pakete definieren.
+* Erstellungssysteme::       Angeben, wie Pakete erstellt werden.
+* Der Store::                Den Paket-Store verändern.
+* Ableitungen::              Systemnahe Schnittstelle für Paketableitungen.
+* Die Store-Monade::         Rein funktionale Schnittstelle zum Store.
+* G-Ausdrücke::             Erstellungsausdrücke verarbeiten.
+* Invoking guix repl::       Fiddling with Guix interactively.
+
+Pakete definieren
+
+
+
+* „package“-Referenz::   Der Datentyp für Pakete.
+* „origin“-Referenz::    Datentyp für Paketursprünge.
+
+Zubehör
+
+
+
+* Aufruf von guix build::    Pakete aus der Befehlszeile heraus erstellen.
+* Aufruf von guix edit::     Paketdefinitionen bearbeiten.
+* Aufruf von guix download::  Herunterladen einer Datei und Ausgabe ihres 
+                                Hashes.
+* Aufruf von guix hash::     Den kryptographischen Hash einer Datei 
+                               berechnen.
+* Aufruf von guix import::   Paketdefinitionen importieren.
+* Aufruf von guix refresh::  Paketdefinitionen aktualisieren.
+* Aufruf von guix lint::     Fehler in Paketdefinitionen finden.
+* Aufruf von guix size::     Plattenverbrauch profilieren.
+* Aufruf von guix graph::    Den Paketgraphen visualisieren.
+* Aufruf von guix environment::  Entwicklungsumgebungen einrichten.
+* Aufruf von guix publish::  Substitute teilen.
+* Aufruf von guix challenge::  Die Substitut-Server anfechten.
+* Aufruf von guix copy::     Mit einem entfernten Store Dateien austauschen.
+* Aufruf von guix container::  Prozesse isolieren.
+* Aufruf von guix weather::  Die Verfügbarkeit von Substituten 
+                               einschätzen.
+* Invoking guix processes::  Listing client processes.
+
+Aufruf von @command{guix build}
+
+
+
+* Gemeinsame Erstellungsoptionen::  Erstellungsoptionen für die meisten 
+                                      Befehle.
+* Paketumwandlungsoptionen::  Varianten von Paketen erzeugen.
+* Zusätzliche Erstellungsoptionen::  Optionen spezifisch für »guix 
+                                        build«.
+* Fehlschläge beim Erstellen untersuchen::  Praxiserfahrung bei der 
+                                               Paketerstellung.
+
+GNU-Distribution
+
+
+
+* Systeminstallation::       Das ganze Betriebssystem installieren.
+* Systemkonfiguration::      Das Betriebssystem konfigurieren.
+* Dokumentation::            Wie man Nutzerhandbücher von Software liest.
+* Dateien zur Fehlersuche installieren::  Womit man seinen Debugger 
+                                            füttert.
+* Sicherheitsaktualisierungen::  Sicherheits-Patches schnell einspielen.
+* Paketmodule::              Pakete aus Sicht des Programmierers.
+* Paketrichtlinien::         Die Distribution wachsen lassen.
+* Bootstrapping::            GNU/Linux von Grund auf selbst erstellen.
+* Portierung::               Guix auf andere Plattformen und Kernels 
+                               bringen.
+
+Systeminstallation
+
+
+
+* Einschränkungen::         Was Sie erwarten dürfen.
+* Hardware-Überlegungen::   Unterstützte Hardware.
+* Installation von USB-Stick oder DVD::  Das Installationsmedium 
+                                           vorbereiten.
+* Vor der Installation::     Netzwerkanbindung, Partitionierung etc.
+* Fortfahren mit der Installation::  Die Hauptsache.
+* GuixSD in einer VM installieren::  Ein GuixSD-Spielplatz.
+* Ein Abbild zur Installation erstellen::  Wie ein solches entsteht.
+
+Systemkonfiguration
+
+
+
+* Das Konfigurationssystems nutzen::  Ihr GNU-System anpassen
+* „operating-system“-Referenz::  Details der 
+                                       Betriebssystem-Deklarationen.
+* Dateisysteme::             Die Dateisystemeinbindungen konfigurieren.
+* Abgebildete Geräte::      Zusatzverarbeitungsschritte für blockbasierte 
+                               Geräte.
+* Benutzerkonten::           Benutzerkonten festlegen.
+* Locales::                  Sprach- und kulturelle 
+                               Konventionseinstellungen.
+* Dienste::                  Systemdienste festlegen.
+* Setuid-Programme::         Programme mit Administratorrechten ausführen
+* X.509-Zertifikate::        HTTPS-Server authentifizieren.
+* Name Service Switch::      Den Name Service Switch von libc konfigurieren.
+* Initiale RAM-Disk::        Linux-libre hochfahren.
+* Bootloader-Konfiguration::  Den Bootloader konfigurieren.
+* Aufruf von guix system::   Instanzierung einer Systemkonfiguration
+* GuixSD in einer VM starten::  Wie man GuixSD in einer virtuellen Maschine 
+                                  startet.
+* Dienste definieren::       Neue Dienstdefinitionen hinzufügen.
+
+Dienste
+
+
+
+* Basisdienste::             Essenzielle Systemdienste
+* Geplante Auftragsausführung::  Der mcron-Dienst.
+* Log-Rotation::             Der rottlog-Dienst.
+* Netzwerkdienste::          Netzwerkeinrichtung, SSH-Daemon etc.
+* X Window::                 Graphische Anzeige.
+* Druckdienste::             Unterstützung für lokale und entfernte 
+                               Drucker.
+* Desktop-Dienste::          D-Bus- und Desktop-Dienste.
+* Tondienste::               Dienste für ALSA und Pulseaudio.
+* Datenbankdienste::         SQL-Datenbanken, Schlüssel-Wert-Speicher etc.
+* Mail-Dienste::             IMAP, POP3, SMTP und so weiter.
+* Kurznachrichtendienste::   Dienste für Kurznachrichten.
+* Telefondienste::           Telefoniedienste.
+* Überwachungsdienste::     Dienste zur Systemüberwachung.
+* Kerberos-Dienste::         Kerberos-Dienste.
+* Web-Dienste::              Web-Server.
+* Zertifikatsdienste::       TLS-Zertifikate via Let’s Encrypt.
+* DNS-Dienste::              DNS-Daemons.
+* VPN-Dienste::              VPN-Daemons.
+* Network File System::      Dienste mit Bezug zum Netzwerkdateisystem.
+* Kontinuierliche Integration::  Der Cuirass-Dienst
+* Power Management Services::  Extending battery life.
+* Audio-Dienste::            Der MPD.
+* Virtualisierungsdienste::  Dienste für virtuelle Maschinen.
+* Versionskontrolldienste::  Entfernten Zugang zu Git-Repositorys bieten.
+* Spieldienste::             Spielserver.
+* Verschiedene Dienste::     Andere Dienste.
+
+Dienste definieren
+
+
+
+* Dienstkompositionen::      Wie Dienste zusammengestellt werden.
+* Diensttypen und Dienste::  Typen und Dienste.
+* Service-Referenz::         Referenz zur Programmierschnittstelle
+* Shepherd-Dienste::         Eine spezielle Art von Dienst.
+
+Paketrichtlinien
+
+
+
+* Software-Freiheit::        Was in die Distribution aufgenommen werden 
+                               darf.
+* Paketbenennung::           Was macht einen Namen aus?
+* Versionsnummern::          Wenn der Name noch nicht genug ist.
+* Zusammenfassungen und Beschreibungen::  Den Nutzern helfen, das richtige 
+                                            Paket zu finden.
+* Python-Module::            Ein Touch britischer Comedy.
+* Perl-Module::              Kleine Perlen.
+* Java-Pakete::              Kaffeepause.
+* Schriftarten::             Schriften verschriftlicht.
+
+Mitwirken
+
+
+
+* Erstellung aus dem Git::   Das Neueste und Beste.
+* Guix vor der Installation ausführen::  Hacker-Tricks.
+* Perfekt eingerichtet::     Die richtigen Werkzeuge.
+* Code-Stil::                Wie Mitwirkende hygienisch arbeiten.
+* Einreichen von Patches::   Teilen Sie Ihre Arbeit.
+
+Code-Stil
+
+
+
+* Programmierparadigmen::    Wie Sie Ihre Elemente zusammenstellen.
+* Module::                   Wo Sie Ihren Code unterbringen.
+* Datentypen und Mustervergleich::  Implementierung von Datenstrukturen.
+* Formatierung von Code::    Schreibkonventionen.
 
 @end detailmenu
 @end menu
 
 @c *********************************************************************
address@hidden Introduction
address@hidden Introduction
-
address@hidden purpose
-GNU address@hidden'' is pronounced like ``geeks'', or ``ɡiːks''
-using the international phonetic alphabet (IPA).} is a package
-management tool for the GNU system.  Guix makes it easy for unprivileged
-users to install, upgrade, or remove packages, to roll back to a
-previous package set, to build packages from source, and generally
-assists with the creation and maintenance of software environments.
-
address@hidden user interfaces
-Guix provides a command-line package management interface
-(@pxref{Invoking guix package}), a set of command-line utilities
-(@pxref{Utilities}), as well as Scheme programming interfaces
-(@pxref{Programming Interface}).
address@hidden build daemon
-Its @dfn{build daemon} is responsible for building packages on behalf of
-users (@pxref{Setting Up the Daemon}) and for downloading pre-built
-binaries from authorized sources (@pxref{Substitutes}).
-
address@hidden extensibility of the distribution
address@hidden customization, of packages
-Guix includes package definitions for many GNU and non-GNU packages, all
-of which @uref{https://www.gnu.org/philosophy/free-sw.html, respect the
-user's computing freedom}.  It is @emph{extensible}: users can write
-their own package definitions (@pxref{Defining Packages}) and make them
-available as independent package modules (@pxref{Package Modules}).  It
-is also @emph{customizable}: users can @emph{derive} specialized package
-definitions from existing ones, including from the command line
-(@pxref{Package Transformation Options}).
address@hidden Einführung
address@hidden Einführung
+
address@hidden Zweck
+GNU address@hidden wird wie »geeks« ausgesprochen, also als »ɡiːks« in
+der Notation des Internationalen Phonetischen Alphabets (IPA).} ist ein
+Werkzeug zur Paketverwaltung für das GNU-System. Guix macht es
+unprivilegierten Nutzern leicht, Pakete zu installieren, zu aktualisieren
+oder zu entfernen, zu einem vorherigen Satz von Paketen zurückzuwechseln,
+Pakete aus ihrem Quellcode heraus zu erstellen und hilft allgemein bei der
+Schöpfung und Wartung von Software-Umgebungen.
+
address@hidden Benutzeroberflächen
+Guix bietet eine kommandozeilenbasierte Paketverwaltungsschnittstelle
+(@pxref{Aufruf von guix package}), einen Satz Befehlszeilenwerkzeuge
+(@pxref{Zubehör}) sowie Schnittstellen zur Programmierung in Scheme
+(@pxref{Programmierschnittstelle}).
address@hidden Erstellungs-Daemon
+Der @dfn{Erstellungs-Daemon} ist für das Erstellen von Paketen im Auftrag
+von Nutzern verantwortlich (@pxref{Den Daemon einrichten}) und für das
+Herunterladen vorerstellter Binärdateien aus autorisierten Quellen
+(@pxref{Substitute}).
+
address@hidden Erweiterbarkeit der Distribution
address@hidden Anpassung, von Paketen
+Guix enthält Paketdefinitionen für viele Pakete, von GNU und nicht von GNU,
+die alle @uref{https://www.gnu.org/philosophy/free-sw.html, die Freiheit des
+Computernutzers respektieren}. Es ist @emph{erweiterbar}: Nutzer können ihre
+eigenen Paketdefinitionen schreiben (@pxref{Pakete definieren}) und sie als
+unabhängige Paketmodule verfügbar machen (@pxref{Paketmodule}). Es ist
+auch @emph{anpassbar}: Nutzer können spezialisierte Paketdefinitionen aus
+bestehenden @emph{ableiten}, auch von der Befehlszeile 
(@pxref{Paketumwandlungsoptionen}).
 
 @cindex Guix System Distribution
 @cindex GuixSD
-You can install address@hidden on top of an existing GNU/Linux system
-where it complements the available tools without interference
-(@pxref{Installation}), or you can use it as part of the standalone
address@hidden System Distribution} or GuixSD (@pxref{GNU Distribution}).
-With address@hidden, you @emph{declare} all aspects of the operating
-system configuration and Guix takes care of instantiating the
-configuration in a transactional, reproducible, and stateless fashion
-(@pxref{System Configuration}).
-
address@hidden functional package management
-Under the hood, Guix implements the @dfn{functional package management}
-discipline pioneered by Nix (@pxref{Acknowledgments}).
-In Guix, the package build and installation process is seen
-as a @emph{function}, in the mathematical sense.  That function takes inputs,
-such as build scripts, a compiler, and libraries, and
-returns an installed package.  As a pure function, its result depends
-solely on its inputs---for instance, it cannot refer to software or
-scripts that were not explicitly passed as inputs.  A build function
-always produces the same result when passed a given set of inputs.  It
-cannot alter the environment of the running system in
-any way; for instance, it cannot create, modify, or delete files outside
-of its build and installation directories.  This is achieved by running
-build processes in isolated environments (or @dfn{containers}), where only 
their
-explicit inputs are visible.
-
address@hidden store
-The result of package build functions is @dfn{cached} in the file
-system, in a special directory called @dfn{the store} (@pxref{The
-Store}).  Each package is installed in a directory of its own in the
-store---by default under @file{/gnu/store}.  The directory name contains
-a hash of all the inputs used to build that package; thus, changing an
-input yields a different directory name.
-
-This approach is the foundation for the salient features of Guix: support
-for transactional package upgrade and rollback, per-user installation, and
-garbage collection of packages (@pxref{Features}).
+Sie können address@hidden auf ein bestehendes GNU/Linux-System aufsetzen, wo
+es die bereits verfügbaren Werkzeuge ergänzt, ohne zu stören
+(@pxref{Installation}), oder Sie können es eigenständig als Teil der
address@hidden System Distribution}, kurz GuixSD (@pxref{GNU-Distribution}),
+verwenden. Mit address@hidden @emph{deklarieren} Sie alle Aspekte der
+Betriebssystemkonfiguration und Guix kümmert sich darum, die Konfiguration
+oft transaktionsbasierte, reproduzierbare und zustandslose Weise zu
+instanzieren (@pxref{Systemkonfiguration}).
+
address@hidden funktionale Paketverwaltung
+Intern implementiert Guix die Disziplin der @dfn{funktionalen
+Paketverwaltung}, zu der Nix schon die Pionierarbeit geleistet hat
+(@pxref{Danksagungen}). In Guix wird der Prozess, ein Paket zu erstellen
+und zu installieren, als eine @emph{Funktion} im mathematischen Sinn
+aufgefasst. Diese Funktion hat Eingaben, wie zum Beispiel
+Erstellungs-Skripts, einen Compiler und Bibliotheken, und liefert ein
+installiertes Paket. Als eine reine Funktion hängt sein Ergebnis allein von
+seinen Eingaben ab — zum Beispiel kann er nicht auf Software oder Skripts
+Bezug nehmen, die nicht ausdrücklich als Eingaben übergeben wurden. Eine
+Erstellungsfunktion führt immer zum selben Ergebnis, wenn ihr die gleiche
+Menge an Eingaben übergeben wurde. Sie kann die Umgebung des laufenden
+Systems auf keine Weise beeinflussen, zum Beispiel kann sie keine Dateien
+außerhalb ihrer Erstellungs- und Installationsverzeichnisse verändern. Um
+dies zu erreichen, laufen Erstellungsprozesse in isolieren Umgebungen
+(sogenannte @dfn{Container}), wo nur ausdrückliche Eingaben sichtbar sind.
+
address@hidden Store
+Das Ergebnis von Paketerstellungsfunktionen wird im Dateisystem
address@hidden in einem besonderen Verzeichnis, was als @dfn{der
+Store} bezeichnet wird (@pxref{Der Store}). Jedes Paket wird in sein eigenes
+Verzeichnis im Store installiert — standardmäßig ist er unter
address@hidden/gnu/store} zu finden. Der Verzeichnisname enthält einen Hash 
aller
+Eingaben, anhand derer das Paket erzeugt wurde, somit hat das Ändern einer
+Eingabe einen völlig anderen Verzeichnisnamen zur Folge.
+
+Dieses Vorgehen ist die Grundlage für die Guix auszeichnenden
+Funktionalitäten: Unterstützung transaktionsbasierter Paketaktualisierungen
+und -rückstufungen, Installation von Paketen als einfacher Nutzer sowie
+Garbage Collection für Pakete (@pxref{Funktionalitäten}).
 
 
 @c *********************************************************************
 @node Installation
 @chapter Installation
 
address@hidden installing Guix
-GNU Guix is available for download from its website at
address@hidden://www.gnu.org/software/guix/}.  This section describes the
-software requirements of Guix, as well as how to install it and get
-ready to use it.
-
-Note that this section is concerned with the installation of the package
-manager, which can be done on top of a running GNU/Linux system.  If,
-instead, you want to install the complete GNU operating system,
address@hidden Installation}.
-
address@hidden foreign distro
-When installed on a running GNU/Linux system---thereafter called a
address@hidden address@hidden complements the available tools
-without interference.  Its data lives exclusively in two directories,
-usually @file{/gnu/store} and @file{/var/guix}; other files on your
-system, such as @file{/etc}, are left untouched.
-
-Once installed, Guix can be updated by running @command{guix pull}
-(@pxref{Invoking guix pull}).
address@hidden Guix installieren
+GNU Guix kann von seiner Webseite unter
address@hidden://www.gnu.org/software/guix/} heruntergeladen werden. Dieser
+Abschnitt beschreibt die Software-Voraussetzungen von Guix und wie man es
+installiert, so dass man es benutzen kann.
+
+Beachten Sie, dass es in diesem Abschnitt um die Installation des
+Paketverwaltungswerkzeugs geht, welche auf einem laufenden GNU/Linux-System
+vollzogen werden kann. Falls Sie stattdessen das vollständige
+GNU-Betriebssystem installieren möchten, werfen Sie einen Blick in den
+Abschnitt @pxref{Systeminstallation}.
+
address@hidden Fremddistribution
+Wenn es auf ein bestehendes GNU/Linux-System installiert wird — im Folgenden
+als @dfn{Fremddistribution} bezeichnet —, ergänzt address@hidden die
+verfügbaren Werkzeuge, ohne dass sie sich gegenseitig stören. Guix’ Daten
+befinden sich ausschließlich in zwei Verzeichnissen, üblicherweise
address@hidden/gnu/store} und @file{/var/guix}; andere Dateien auf Ihrem System 
wie
address@hidden/etc} bleiben unberührt.
+
+Sobald es installiert ist, kann Guix durch Ausführen von @command{guix pull}
+aktualisiert werden (@pxref{Aufruf von guix pull}).
 
 @menu
-* Binary Installation::         Getting Guix running in no time!
-* Requirements::                Software needed to build and run Guix.
-* Running the Test Suite::      Testing Guix.
-* Setting Up the Daemon::       Preparing the build daemon's environment.
-* Invoking guix-daemon::        Running the build daemon.
-* Application Setup::           Application-specific setup.
+* Aus Binärdatei installieren::  Guix installieren, ohne Zeit zu verlieren!
+* Voraussetzungen::          Zum Erstellen und Benutzen von Guix nötige 
+                               Software.
+* Die Testsuite laufen lassen::  Guix testen.
+* Den Daemon einrichten::    Wie man die Umgebung des Erstellungs-Daemons 
+                               einrichtet.
+* Aufruf des guix-daemon::   Den Erstellungs-Daemon laufen lassen.
+* Anwendungen einrichten::   Anwendungsspezifische Einstellungen.
 @end menu
 
address@hidden Binary Installation
address@hidden Binary Installation
address@hidden Aus Binärdatei installieren
address@hidden Aus Binärdatei installieren
 
address@hidden installing Guix from binaries
-This section describes how to install Guix on an arbitrary system from a
-self-contained tarball providing binaries for Guix and for all its
-dependencies.  This is often quicker than installing from source, which
-is described in the next sections.  The only requirement is to have
address@hidden and Xz.
address@hidden Guix aus Binärdateien installieren
+Dieser Abschnitt beschreibt, wie sich Guix auf einem beliebigen System aus
+einem alle Komponenten umfassenden Tarball installieren lässt, der
+Binärdateien für Guix und all seine Abhängigkeiten liefert. Dies geht in der
+Regel schneller, als Guix aus seinen Quelldateien zu installieren, was im
+nächsten Abschnitt beschrieben wird. Vorausgesetzt wird hier lediglich, dass
address@hidden und Xz verfügbar sind.
 
-We provide a
+Wir bieten ein
 @uref{https://git.savannah.gnu.org/cgit/guix.git/plain/etc/guix-install.sh,
-shell installer script}, which automates the download, installation, and
-initial configuration of Guix.  It should be run as the root user.
+Installations-Skript für die Shell}, welches Guix automatisch herunterlädt,
+installiert und eine erste Konfiguration von Guix mit sich bringt. Es sollte
+als der Administratornutzer (als »root«) ausgeführt werden.
 
-Installing goes along these lines:
+Die Installation läuft so ab:
 
 @enumerate
 @item
address@hidden downloading Guix binary
address@hidden Guix-Binärdatei herunterladen
 Download the binary tarball from
 @indicateurl{https://alpha.gnu.org/gnu/guix/address@hidden@var{system}.tar.xz},
 where @var{system} is @code{x86_64-linux} for an @code{x86_64} machine
 already running the kernel Linux, and so on.
 
 @c The following is somewhat duplicated in ``System Installation''.
-Make sure to download the associated @file{.sig} file and to verify the
-authenticity of the tarball against it, along these lines:
+Achten Sie darauf, auch die zugehörige @file{.sig}-Datei herunterzuladen und
+verifizieren Sie damit die Authentizität des Tarballs, ungefähr so:
 
 @example
 $ wget https://alpha.gnu.org/gnu/guix/address@hidden@var{system}.tar.xz.sig
 $ gpg --verify address@hidden@var{system}.tar.xz.sig
 @end example
 
-If that command fails because you do not have the required public key,
-then run this command to import it:
+Falls dieser Befehl fehlschlägt, weil Sie nicht über den nötigen
+öffentlichen Schlüssel verfügen, können Sie ihn mit diesem Befehl
+importieren:
 
 @example
 $ gpg --keyserver pgp.mit.edu --recv-keys @value{OPENPGP-SIGNING-KEY-ID}
 @end example
 
 @noindent
-and rerun the @code{gpg --verify} command.
 @c end authentication part
+und den Befehl @code{gpg --verify} erneut ausführen.
 
 @item
-Now, you need to become the @code{root} user.  Depending on your distribution,
-you may have to run @code{su -} or @code{sudo -i}.  As @code{root}, run:
+Nun müssen Sie zum Administratornutzer @code{root} wechseln. Abhängig von
+Ihrer Distribution müssen Sie dazu etwa @code{su -} oder @code{sudo -i}
+ausführen. Danach führen Sie als @code{root}-Nutzer aus:
 
 @example
 # cd /tmp
@@ -471,33 +547,32 @@ you may have to run @code{su -} or @code{sudo -i}.  As 
@code{root}, run:
 # mv var/guix /var/ && mv gnu /
 @end example
 
-This creates @file{/gnu/store} (@pxref{The Store}) and @file{/var/guix}.
-The latter contains a ready-to-use profile for @code{root} (see next
-step.)
+Dadurch wird @file{/gnu/store} (@pxref{Der Store}) und @file{/var/guix}
+erzeugt. Letzteres enthält ein Profil, welches bereit zur Nutzung durch
address@hidden ist (wie im nächsten Schritt beschrieben).
 
-Do @emph{not} unpack the tarball on a working Guix system since that
-would overwrite its own essential files.
+Entpacken Sie den Tarball @emph{nicht} auf einem schon funktionierenden
+Guix-System, denn es würde seine eigenen essenziellen Dateien überschreiben.
 
-The @code{--warning=no-timestamp} option makes sure address@hidden does
-not emit warnings about ``implausibly old time stamps'' (such
-warnings were triggered by address@hidden 1.26 and older; recent
-versions are fine.)
-They stem from the fact that all the
-files in the archive have their modification time set to zero (which
-means January 1st, 1970.)  This is done on purpose to make sure the
-archive content is independent of its creation time, thus making it
-reproducible.
+Die Befehlszeilenoption @code{--warning=no-timestamp} stellt sicher, dass
address@hidden nicht vor »unplausibel alten Zeitstempeln« warnt (solche
+Warnungen traten bei address@hidden 1.26 und älter auf, neue Versionen machen
+keine Probleme). Sie kommen daher, dass alle Dateien im Archiv als
+Änderungszeitpunkt null eingetragen bekommen haben (das bezeichnet den
+1. Januar 1970). Das ist Absicht, damit der Inhalt des Archivs nicht davon
+abhängt, wann es erstellt wurde, und es somit reproduzierbar wird.
 
 @item
-Make @code{root}'s profile available under @file{~root/.guix-profile}:
+Machen Sie das Profil von @code{root} verfügbar als
address@hidden/.guix-profile}:
 
 @example
 # ln -sf /var/guix/profiles/per-user/root/guix-profile \
          ~root/.guix-profile
 @end example
 
-Source @file{etc/profile} to augment @code{PATH} and other relevant
-environment variables:
+»Sourcen« Sie @file{etc/profile}, um @code{PATH} und andere relevante
+Umgebungsvariable zu ergänzen:
 
 @example
 # GUIX_PROFILE="`echo ~root`/.guix-profile" ; \
@@ -505,14 +580,15 @@ environment variables:
 @end example
 
 @item
-Create the group and user accounts for build users as explained below
-(@pxref{Build Environment Setup}).
+Erzeugen Sie Nutzergruppe und Nutzerkonten für die Erstellungs-Benutzer wie
+folgt (@pxref{Einrichten der Erstellungsumgebung}).
 
 @item
-Run the daemon, and set it to automatically start on boot.
+Führen Sie den Daemon aus, und lassen Sie ihn automatisch bei jedem
+Hochfahren starten.
 
-If your host distro uses the systemd init system, this can be achieved
-with these commands:
+Wenn Ihre Wirts-Distribution systemd als »init«-System verwendet, können Sie
+das mit folgenden Befehlen veranlassen:
 
 @c Versions of systemd that supported symlinked service files are not
 @c yet widely deployed, so we should suggest that users copy the service
@@ -527,7 +603,7 @@ with these commands:
 # systemctl start guix-daemon && systemctl enable guix-daemon
 @end example
 
-If your host distro uses the Upstart init system:
+Wenn Ihre Wirts-Distribution als »init«-System Upstart verwendet:
 
 @example
 # initctl reload-configuration
@@ -535,15 +611,15 @@ If your host distro uses the Upstart init system:
 # start guix-daemon
 @end example
 
-Otherwise, you can still start the daemon manually with:
+Andernfalls können Sie den Daemon immer noch manuell starten, mit:
 
 @example
 # ~root/.guix-profile/bin/guix-daemon --build-users-group=guixbuild
 @end example
 
 @item
-Make the @command{guix} command available to other users on the machine,
-for instance with:
+Stellen Sie den @command{guix}-Befehl auch anderen Nutzern Ihrer Maschine
+zur Verfügung, zum Beispiel so:
 
 @example
 # mkdir -p /usr/local/bin
@@ -551,8 +627,8 @@ for instance with:
 # ln -s /var/guix/profiles/per-user/root/guix-profile/bin/guix
 @end example
 
-It is also a good idea to make the Info version of this manual available
-there:
+Es ist auch eine gute Idee, die Info-Version dieses Handbuchs ebenso
+verfügbar zu machen:
 
 @example
 # mkdir -p /usr/local/share/info
@@ -561,256 +637,275 @@ there:
   do ln -s $i ; done
 @end example
 
-That way, assuming @file{/usr/local/share/info} is in the search path,
-running @command{info guix} will open this manual (@pxref{Other Info
-Directories,,, texinfo, GNU Texinfo}, for more details on changing the
-Info search path.)
+Auf diese Art wird, unter der Annahme, dass bei Ihnen
address@hidden/usr/local/share/info} im Suchpfad eingetragen ist, das Ausführen 
von
address@hidden guix} dieses Handbuch öffnen (@pxref{Other Info Directories,,,
+texinfo, GNU Texinfo} hat weitere Details, wie Sie den Info-Suchpfad ändern
+können).
 
 @item
address@hidden substitutes, authorization thereof
-To use substitutes from @code{hydra.gnu.org} or one of its mirrors
-(@pxref{Substitutes}), authorize them:
address@hidden Substitute, deren Autorisierung
+Um Substitute von @code{hydra.gnu.org} oder einem Spiegelserver davon zu
+benutzen (@pxref{Substitute}), müssen sie erst autorisiert werden:
 
 @example
 # guix archive --authorize < ~root/.guix-profile/share/guix/hydra.gnu.org.pub
 @end example
 
 @item
-Each user may need to perform a few additional steps to make their Guix
-environment ready for use, @pxref{Application Setup}.
+Alle Nutzer müssen womöglich ein paar zusätzliche Schritte ausführen, damit
+ihre Guix-Umgebung genutzt werden kann, siehe @pxref{Anwendungen einrichten}.
 @end enumerate
 
-Voilà, the installation is complete!
+Voilà, die installation ist fertig!
 
-You can confirm that Guix is working by installing a sample package into
-the root profile:
+Sie können nachprüfen, dass Guix funktioniert, indem Sie ein Beispielpaket
+in das root-Profil installieren:
 
 @example
 # guix package -i hello
 @end example
 
-The @code{guix} package must remain available in @code{root}'s profile,
-or it would become subject to garbage collection---in which case you
-would find yourself badly handicapped by the lack of the @command{guix}
-command.  In other words, do not remove @code{guix} by running
address@hidden package -r guix}.
+The @code{guix} package must remain available in @code{root}'s profile, or
+it would become subject to garbage collection---in which case you would find
+yourself badly handicapped by the lack of the @command{guix} command.  In
+other words, do not remove @code{guix} by running @code{guix package -r
+guix}.
 
-The binary installation tarball can be (re)produced and verified simply
-by running the following command in the Guix source tree:
+Der Tarball zur Installation aus einer Binärdatei kann einfach durch
+Ausführung des folgenden Befehls im Guix-Quellbaum (re-)produziert und
+verifiziert werden:
 
 @example
 make address@hidden
 @end example
 
 @noindent
-... which, in turn, runs:
+…was wiederum dies ausführt:
 
 @example
 guix pack -s @var{system} --localstatedir guix
 @end example
 
address@hidden guix pack}, for more info on this handy tool.
+Siehe @xref{Aufruf von guix pack} für weitere Informationen zu diesem
+praktischen Werkzeug.
 
address@hidden Requirements
address@hidden Requirements
address@hidden Voraussetzungen
address@hidden Voraussetzungen
 
-This section lists requirements when building Guix from source.  The
-build procedure for Guix is the same as for other GNU software, and is
-not covered here.  Please see the files @file{README} and @file{INSTALL}
-in the Guix source tree for additional details.
+Dieser Abschnitt listet Voraussetzungen auf, um Guix aus seinem Quellcode zu
+erstellen. Der Erstellungsprozess für Guix ist derselbe wie für andere
+GNU-Software und wird hier nicht beschrieben. Bitte lesen Sie die Dateien
address@hidden und @file{INSTALL} im Guix-Quellbaum, um weitere Details zu
+erfahren.
 
-GNU Guix depends on the following packages:
+GNU Guix hat folgende Pakete als Abhängigkeiten:
 
 @itemize
address@hidden @url{http://gnu.org/software/guile/, GNU Guile}, version 2.0.13 
or
-later, including 2.2.x;
address@hidden @url{http://gnu.org/software/guile/, GNU Guile}, Version 2.0.13 
oder
+neuer, einschließlich 2.2.x,
 @item @url{https://notabug.org/cwebber/guile-gcrypt, Guile-Gcrypt}, version
 0.1.0 or later;
 @item
address@hidden://gnutls.org/, GnuTLS}, specifically its Guile bindings
-(@pxref{Guile Preparations, how to install the GnuTLS bindings for
-Guile,, gnutls-guile, GnuTLS-Guile});
address@hidden://gnutls.org/, GnuTLS}, im Speziellen dessen Bindungen für Guile
+(@pxref{Guile Preparations, how to install the GnuTLS bindings for Guile,,
+gnutls-guile, GnuTLS-Guile}),
 @item
address@hidden://notabug.org/civodul/guile-sqlite3, Guile-SQLite3}, version 
0.1.0
-or later;
address@hidden://notabug.org/civodul/guile-sqlite3, Guile-SQLite3}, version
+0.1.0 or later;
 @item
 @c FIXME: Specify a version number once a release has been made.
address@hidden://gitlab.com/guile-git/guile-git, Guile-Git}, from August
-2017 or later;
address@hidden @url{http://zlib.net, zlib};
address@hidden://gitlab.com/guile-git/guile-git, Guile-Git}, vom August 2017
+oder neuer,
address@hidden @url{http://zlib.net, zlib},
 @item @url{http://www.gnu.org/software/make/, GNU Make}.
 @end itemize
 
-The following dependencies are optional:
+Folgende Abhängigkeiten sind optional:
 
 @itemize
 @item
-Installing
address@hidden://savannah.nongnu.org/projects/guile-json/, Guile-JSON} will
-allow you to use the @command{guix import pypi} command (@pxref{Invoking
-guix import}).  It is of
-interest primarily for developers and not for casual users.
+Wenn Sie @url{http://savannah.nongnu.org/projects/guile-json/, Guile-JSON}
+installieren, können Sie den Befehl @command{guix import pypi} benutzen
+(@pxref{Aufruf von guix import}). Das spielt hauptsächlich für Entwickler und
+nicht für Gelegenheitsnutzer eine Rolle.
 
 @item
 @c Note: We need at least 0.10.2 for 'channel-send-eof'.
-Support for build offloading (@pxref{Daemon Offload Setup}) and
address@hidden copy} (@pxref{Invoking guix copy}) depends on
address@hidden://github.com/artyom-poptsov/guile-ssh, Guile-SSH},
-version 0.10.2 or later.
+Unterstützung für das Auslagern von Erstellungen (@pxref{Auslagern des Daemons 
einrichten}) und @command{guix copy} (@pxref{Aufruf von guix copy}) hängt von
address@hidden://github.com/artyom-poptsov/guile-ssh, Guile-SSH}, Version
+0.10.2 oder neuer, ab.
 
 @item
-When @url{http://www.bzip.org, libbz2} is available,
address@hidden can use it to compress build logs.
+Wenn @url{http://www.bzip.org, libbz2} verfügbar ist, kann
address@hidden damit Erstellungsprotokolle komprimieren.
 @end itemize
 
-Unless @code{--disable-daemon} was passed to @command{configure}, the
-following packages are also needed:
+Sofern nicht @code{--disable-daemon} beim Aufruf von @command{configure}
+übergeben wurde, benötigen Sie auch folgende Pakete:
 
 @itemize
address@hidden @url{http://gnupg.org/, GNU libgcrypt};
address@hidden @url{http://sqlite.org, SQLite 3};
address@hidden @url{http://gcc.gnu.org, GCC's g++}, with support for the
-C++11 standard.
address@hidden @url{http://gnupg.org/, GNU libgcrypt},
address@hidden @url{http://sqlite.org, SQLite 3},
address@hidden @url{http://gcc.gnu.org, GCC's g++} mit Unterstützung für den
+C++11-Standard.
 @end itemize
 
address@hidden state directory
-When configuring Guix on a system that already has a Guix installation,
-be sure to specify the same state directory as the existing installation
-using the @code{--localstatedir} option of the @command{configure}
-script (@pxref{Directory Variables, @code{localstatedir},, standards,
-GNU Coding Standards}).  The @command{configure} script protects against
-unintended misconfiguration of @var{localstatedir} so you do not
-inadvertently corrupt your store (@pxref{The Store}).
-
address@hidden Nix, compatibility
-When a working installation of @url{http://nixos.org/nix/, the Nix package
-manager} is available, you
-can instead configure Guix with @code{--disable-daemon}.  In that case,
-Nix replaces the three dependencies above.
-
-Guix is compatible with Nix, so it is possible to share the same store
-between both.  To do so, you must pass @command{configure} not only the
-same @code{--with-store-dir} value, but also the same
address@hidden value.  The latter is essential because it
-specifies where the database that stores metadata about the store is
-located, among other things.  The default values for Nix are
address@hidden/nix/store} and @code{--localstatedir=/nix/var}.
-Note that @code{--disable-daemon} is not required if
-your goal is to share the store with Nix.
-
address@hidden Running the Test Suite
address@hidden Running the Test Suite
-
address@hidden test suite
-After a successful @command{configure} and @code{make} run, it is a good
-idea to run the test suite.  It can help catch issues with the setup or
-environment, or bugs in Guix itself---and really, reporting test
-failures is a good way to help improve the software.  To run the test
-suite, type:
address@hidden Zustandsverzeichnis
+Sollten Sie Guix auf einem System konfigurieren, auf dem Guix bereits
+installiert ist, dann stellen Sie sicher, dasselbe Zustandsverzeichnis wie
+für die bestehende Installation zu verwenden. Benutzen Sie dazu die
+Befehlszeilenoption @code{--localstatedir} des @command{configure}-Skripts
+(@pxref{Directory Variables, @code{localstatedir},, standards, GNU Coding
+Standards}). Das @command{configure}-Skript schützt vor ungewollter
+Fehlkonfiguration der @var{localstatedir}, damit sie nicht versehentlich
+Ihren Store verfälschen (@pxref{Der Store}).
+
address@hidden Nix, Kompatibilität
+Wenn eine funktionierende Installation of @url{http://nixos.org/nix/, the
+Nix package manager} verfügbar ist, können Sie Guix stattdessen mit
address@hidden konfigurieren. In diesem Fall ersetzt Nix die drei
+obengenannten Abhängigkeiten.
+
+Guix ist mit Nix kompatibel, daher ist es möglich, denselben Store für beide
+zu verwenden. Dazu müssen Sie an @command{configure} nicht nur denselben
+Wert für @code{--with-store-dir} übergeben, sondern auch denselben Wert für
address@hidden Letzterer ist deswegen essenziell, weil er unter
+Anderem angibt, wo die Datenbank liegt, in der sich die Metainformationen
+über den Store befinden. Für Nix sind die Werte standardmäßig
address@hidden/nix/store} und
address@hidden/nix/var}. Beachten Sie, dass @code{--disable-daemon}
+nicht erforderlich ist, wenn Sie die Absicht haben, den Store mit Nix zu
+teilen.
+
address@hidden Die Testsuite laufen lassen
address@hidden Die Testsuite laufen lassen
+
address@hidden Testkatalog
+Nachdem @command{configure} und @code{make} erfolgreich durchgelaufen sind,
+ist es ratsam, den Testkatalog auszuführen. Er kann dabei helfen, Probleme
+mit der Einrichtung oder Systemumgebung zu finden, oder auch Probleme in
+Guix selbst — und Testfehler zu melden ist eine wirklich gute Art und Weise,
+bei der Verbesserung von Guix mitzuhelfen. Um den Testkatalog auszuführen,
+geben Sie Folgendes ein:
 
 @example
 make check
 @end example
 
-Test cases can run in parallel: you can use the @code{-j} option of
address@hidden to speed things up.  The first run may take a few minutes
-on a recent machine; subsequent runs will be faster because the store
-that is created for test purposes will already have various things in
-cache.
+Testfälle können parallel ausgeführt werden. Sie können die
+Befehlszeiltenoption @code{-j} von address@hidden benutzen, damit es
+schneller geht. Der erste Durchlauf kann auf neuen Maschinen ein paar
+Minuten dauern, nachfolgende Ausführungen werden schneller sein, weil der
+für die Tests erstellte Store schon einige Dinge zwischengespeichert haben
+wird.
 
-It is also possible to run a subset of the tests by defining the
address@hidden makefile variable as in this example:
+Es ist auch möglich, eine Teilmenge der Tests laufen zu lassen, indem Sie
+die @code{TESTS}-Variable des Makefiles ähnlich wie in diesem Beispiel
+definieren:
 
 @example
 make check TESTS="tests/store.scm tests/cpio.scm"
 @end example
 
-By default, tests results are displayed at a file level.  In order to
-see the details of every individual test cases, it is possible to define
-the @code{SCM_LOG_DRIVER_FLAGS} makefile variable as in this example:
+Standardmäßig werden Testergebnisse pro Datei angezeigt. Um die Details
+jedes einzelnen Testfalls zu sehen, können Sie wie in diesem Beispiel die
address@hidden des Makefiles definieren:
 
 @example
 make check TESTS="tests/base64.scm" SCM_LOG_DRIVER_FLAGS="--brief=no"
 @end example
 
-Upon failure, please email @email{bug-guix@@gnu.org} and attach the
address@hidden file.  Please specify the Guix version being used
-as well as version numbers of the dependencies (@pxref{Requirements}) in
-your message.
+Kommt es zum Fehlschlag, senden Sie bitte eine E-mail an
address@hidden@@gnu.org} und fügen Sie die Datei @file{test-suite.log} als
+Anhang bei. Bitte geben Sie dabei in Ihrer Nachricht die benutze Version von
+Guix an sowie die Versionsnummern der Abhängigkeiten (@pxref{Voraussetzungen}).
 
-Guix also comes with a whole-system test suite that tests complete
-GuixSD operating system instances.  It can only run on systems where
-Guix is already installed, using:
+Guix wird auch mit einem Testkatalog für das ganze System ausgeliefert, der
+vollständige Instanzen des GuixSD-Betriebssystems testet. Er kann nur auf
+Systemen benutzt werden, auf denen Guix bereits installiert ist, mit
+folgendem Befehl:
 
 @example
 make check-system
 @end example
 
 @noindent
-or, again, by defining @code{TESTS} to select a subset of tests to run:
+Oder, auch hier, indem Sie @code{TESTS} definieren, um eine Teilmenge der
+auszuführenden Tests anzugeben:
 
 @example
 make check-system TESTS="basic mcron"
 @end example
 
-These system tests are defined in the @code{(gnu tests @dots{})}
-modules.  They work by running the operating systems under test with
-lightweight instrumentation in a virtual machine (VM).  They can be
-computationally intensive or rather cheap, depending on whether
-substitutes are available for their dependencies (@pxref{Substitutes}).
-Some of them require a lot of storage space to hold VM images.
+Diese Systemtests sind in den @code{(gnu tests @dots{})}-Modulen
+definiert. Sie funktionieren, indem Sie das getestete Betriebssystem mitsamt
+schlichter Instrumentierung in einer virtuellen Maschine (VM) ausführen. Die
+Tests können aufwendige Berechnungen durchführen oder sie günstig umgehen,
+je nachdem, ob für ihre Abhängigkeiten Substitute zur Verfügung stehen
+(@pxref{Substitute}). Manche von ihnen nehmen viel Speicherplatz in
+Anspruch, um die VM-Abbilder zu speichern.
 
-Again in case of test failures, please send @email{bug-guix@@gnu.org}
-all the details.
+Auch hier gilt: Falls Testfehler auftreten, senden Sie bitte alle Details an
address@hidden@@gnu.org}.
 
address@hidden Setting Up the Daemon
address@hidden Setting Up the Daemon
address@hidden Den Daemon einrichten
address@hidden Den Daemon einrichten
 
address@hidden daemon
-Operations such as building a package or running the garbage collector
-are all performed by a specialized process, the @dfn{build daemon}, on
-behalf of clients.  Only the daemon may access the store and its
-associated database.  Thus, any operation that manipulates the store
-goes through the daemon.  For instance, command-line tools such as
address@hidden package} and @command{guix build} communicate with the
-daemon (@i{via} remote procedure calls) to instruct it what to do.
address@hidden Daemon
+Operationen wie das Erstellen eines Pakets oder Laufenlassen des
+Müllsammlers werden alle durch einen spezialisierten Prozess durchgeführt,
+den @dfn{Erstellungs-Daemon}, im Auftrag seiner Kunden (Clients). Nur der
+Daemon darf auf den Store und seine zugehörige Datenbank zugreifen. Daher
+wird jede den Store verändernde Operation durch den Daemon durchgeführt. Zum
+Beispiel kommunizieren Befehlszeilenwerkzeuge wie @command{guix package} und
address@hidden build} mit dem Daemon (mittels entfernter Prozeduraufrufe), um
+ihm Anweisungen zu geben, was er tun soll.
 
-The following sections explain how to prepare the build daemon's
-environment.  See also @ref{Substitutes}, for information on how to allow
-the daemon to download pre-built binaries.
+Folgende Abschnitte beschreiben, wie Sie die Umgebung des
+Erstellungs-Daemons ausstatten sollten. Siehe auch @ref{Substitute} für
+Informationen darüber, wie Sie es dem Daemon ermöglichen, vorerstellte
+Binärdateien herunterzuladen.
 
 @menu
-* Build Environment Setup::     Preparing the isolated build environment.
-* Daemon Offload Setup::        Offloading builds to remote machines.
-* SELinux Support::             Using an SELinux policy for the daemon.
+* Einrichten der Erstellungsumgebung::  Die isolierte Umgebung zum Erstellen 
+                                          vorbereiten.
+* Auslagern des Daemons einrichten::  Erstellungen auf entfernte Maschinen 
+                                        auslagern.
+* SELinux-Unterstützung::   Wie man eine SELinux-Richtlinie für den Daemon 
+                               einrichtet.
 @end menu
 
address@hidden Build Environment Setup
address@hidden Build Environment Setup
-
address@hidden build environment
-In a standard multi-user setup, Guix and its daemon---the
address@hidden program---are installed by the system
-administrator; @file{/gnu/store} is owned by @code{root} and
address@hidden runs as @code{root}.  Unprivileged users may use
-Guix tools to build packages or otherwise access the store, and the
-daemon will do it on their behalf, ensuring that the store is kept in a
-consistent state, and allowing built packages to be shared among users.
-
address@hidden build users
-When @command{guix-daemon} runs as @code{root}, you may not want package
-build processes themselves to run as @code{root} too, for obvious
-security reasons.  To avoid that, a special pool of @dfn{build users}
-should be created for use by build processes started by the daemon.
-These build users need not have a shell and a home directory: they will
-just be used when the daemon drops @code{root} privileges in build
-processes.  Having several such users allows the daemon to launch
-distinct build processes under separate UIDs, which guarantees that they
-do not interfere with each other---an essential feature since builds are
-regarded as pure functions (@pxref{Introduction}).
-
-On a GNU/Linux system, a build user pool may be created like this (using
-Bash syntax and the @code{shadow} commands):
address@hidden Einrichten der Erstellungsumgebung
address@hidden Einrichten der Erstellungsumgebung
+
address@hidden Erstellungsumgebung
+In einem normalen Mehrbenutzersystem werden Guix und sein Daemon — das
+Programm @command{guix-daemon} — vom Systemadministrator installiert;
address@hidden/gnu/store} gehört @code{root} und @command{guix-daemon} läuft als
address@hidden Nicht mit erweiterten Rechten ausgestattete Nutzer können
+Guix-Werkzeuge benutzen, um Pakete zu erstellen oder anderweitig auf den
+Store zuzugreifen, und der Daemon wird dies für sie erledigen und dabei
+sicherstellen, dass der Store in einem konsistenten Zustand verbleibt und
+sich die Nutzer erstellte Pakete teilen.
+
address@hidden Erstellungsbenutzer
+Wenn @command{guix-daemon} als Administratornutzer @code{root} läuft, wollen
+Sie aber vielleicht dennoch nicht, dass Paketerstellungsprozesse auch als
address@hidden ablaufen, aus offensichtlichen Sicherheitsgründen. Um dies zu
+vermeiden, sollte ein besonderer Pool aus @dfn{Erstellungsbenutzern}
+geschaffen werden, damit vom Daemon gestartete Erstellungsprozesse ihn
+benutzen. Diese Erstellungsbenutzer müssen weder eine Shell noch einen
+Persönlichen Ordner zugewiesen bekommen, sie werden lediglich benutzt, wenn
+der Daemon @code{root}-Rechte in Erstellungsprozessen ablegt. Mehrere solche
+Benutzer zu haben, ermöglicht es dem Daemon, verschiedene
+Erstellungsprozessen unter verschiedenen Benutzeridentifikatoren (UIDs) zu
+starten, was garantiert, dass sie einander nicht stören — eine essenzielle
+Funktionalität, da Erstellungen als reine Funktionen angesehen werden
+(@pxref{Einführung}).
+
+Auf einem GNU/Linux-System kann ein Pool von Erstellungsbenutzern wie folgt
+erzeugt werden (mit Bash-Syntax und den Befehlen von @code{shadow}):
 
 @c See http://lists.gnu.org/archive/html/bug-guix/2013-01/msg00239.html
 @c for why `-G' is needed.
@@ -818,30 +913,32 @@ Bash syntax and the @code{shadow} commands):
 # groupadd --system guixbuild
 # for i in `seq -w 1 10`;
   do
-    useradd -g guixbuild -G guixbuild           \
-            -d /var/empty -s `which nologin`    \
-            -c "Guix build user $i" --system    \
+    useradd -g guixbuild -G guixbuild                  \
+            -d /var/empty -s `which nologin`           \
+            -c "Guix-Erstellungsbenutzer $i" --system  \
             guixbuilder$i;
   done
 @end example
 
 @noindent
-The number of build users determines how many build jobs may run in
-parallel, as specified by the @option{--max-jobs} option
-(@pxref{Invoking guix-daemon, @option{--max-jobs}}).  To use
address@hidden system vm} and related commands, you may need to add the
-build users to the @code{kvm} group so they can access @file{/dev/kvm},
-using @code{-G guixbuild,kvm} instead of @code{-G guixbuild}
-(@pxref{Invoking guix system}).
-
-The @code{guix-daemon} program may then be run as @code{root} with the
-following address@hidden your machine uses the systemd init system,
-dropping the @address@hidden/lib/systemd/system/guix-daemon.service}
-file in @file{/etc/systemd/system} will ensure that
address@hidden is automatically started.  Similarly, if your
-machine uses the Upstart init system, drop the
address@hidden@var{prefix}/lib/upstart/system/guix-daemon.conf}
-file in @file{/etc/init}.}:
+Die Anzahl der Erstellungsbenutzer entscheidet, wieviele Erstellungsaufträge
+parallel ausgeführt werden können, wie es mit der Befehlszeilenoption
address@hidden vorgeben werden kann (@pxref{Aufruf des guix-daemon,
address@hidden). Um @command{guix system vm} und ähnliche Befehle
+nutzen zu können, müssen Sie die Erstellungsbenutzer unter Umständen zur
address@hidden hinzufügen, damit sie Zugriff auf @file{/dev/kvm}
+haben, mit @code{-G guixbuild,kvm} statt @code{-G guixbuild}
+(@pxref{Aufruf von guix system}).
+
+Das Programm @code{guix-daemon} kann mit dem folgenden Befehl als
address@hidden gestartet address@hidden Ihre Maschine systemd als
+»init«-System verwendet, genügt es, die Datei
address@hidden@var{prefix}/lib/systemd/system/guix-daemon.service} in
address@hidden/etc/systemd/system} zu platzieren, damit @command{guix-daemon}
+automatisch gestartet wird. Ebenso können Sie, wenn Ihre Maschine Upstart
+als »init«-System benutzt, die Datei
address@hidden@var{prefix}/lib/upstart/system/guix-daemon.conf} in 
@file{/etc/init}
+platzieren.}:
 
 @example
 # guix-daemon --build-users-group=guixbuild
@@ -849,79 +946,84 @@ file in @file{/etc/init}.}:
 
 @cindex chroot
 @noindent
-This way, the daemon starts build processes in a chroot, under one of
-the @code{guixbuilder} users.  On GNU/Linux, by default, the chroot
-environment contains nothing but:
+Auf diese Weise startet der Daemon Erstellungsprozesse in einem chroot als
+einer der @code{guixbuilder}-Benutzer. Auf GNU/Linux enthält die
+chroot-Umgebung standardmäßig nichts außer:
 
 @c Keep this list in sync with libstore/build.cc! -----------------------
 @itemize
 @item
-a minimal @code{/dev} directory, created mostly independently from the
-host @code{/address@hidden'', because while the set of files
-that appear in the chroot's @code{/dev} is fixed, most of these files
-can only be created if the host has them.};
+einem minimalen @code{/dev}-Verzeichnis, was größtenteils vom @code{/dev}
+des Wirtssystems unabhängig erstellt address@hidden, denn
+obwohl die Menge an Dateien, die im @code{/dev} des chroots vorkommen, fest
+ist, können die meisten dieser Dateien nur dann erstellt werden, wenn das
+Wirtssystem sie auch hat.},
 
 @item
-the @code{/proc} directory; it only shows the processes of the container
-since a separate PID name space is used;
+dem @code{/proc}-Verzeichnis, es zeigt nur die Prozesse des Containers, weil
+ein separater Namensraum für Prozess-IDs (PIDs) benutzt wird,
 
 @item
address@hidden/etc/passwd} with an entry for the current user and an entry for
-user @file{nobody};
address@hidden/etc/passwd} mit einem Eintrag für den aktuellen Benutzer und 
einem
+Eintrag für den Benutzer @file{nobody},
 
 @item
address@hidden/etc/group} with an entry for the user's group;
address@hidden/etc/group} mit einem Eintrag für die Gruppe des Benutzers,
 
 @item
address@hidden/etc/hosts} with an entry that maps @code{localhost} to
address@hidden;
address@hidden/etc/hosts} mit einem Eintrag, der @code{localhost} auf
address@hidden abbildet,
 
 @item
-a writable @file{/tmp} directory.
+einem @file{/tmp}-Verzeichnis mit Schreibrechten.
 @end itemize
 
-You can influence the directory where the daemon stores build trees
address@hidden the @code{TMPDIR} environment variable.  However, the build tree
-within the chroot is always called @file{/tmp/address@hidden,
-where @var{name} is the derivation name---e.g., @code{coreutils-8.24}.
-This way, the value of @code{TMPDIR} does not leak inside build
-environments, which avoids discrepancies in cases where build processes
-capture the name of their build tree.
+Sie können beeinflussen, in welchem Verzeichnis der Daemon Erstellungsbäume
+unterbringt, indem sie den Wert der Umgebungsvariablen @code{TMPDIR}
+ändern. Allerdings heißt innerhalb des chroots der Erstellungsbaum immer
address@hidden/tmp/address@hidden, wobei @var{name} der Ableitungsname
+ist — z.B. @code{coreutils-8.24}. Dadurch hat der Wert von @code{TMPDIR}
+keinen Einfluss auf die Erstellungsumgebung, wodurch Unterschiede vermieden
+werden, falls Erstellungsprozesse den Namen ihres Erstellungsbaumes
+einfangen.
 
 @vindex http_proxy
-The daemon also honors the @code{http_proxy} environment variable for
-HTTP downloads it performs, be it for fixed-output derivations
-(@pxref{Derivations}) or for substitutes (@pxref{Substitutes}).
-
-If you are installing Guix as an unprivileged user, it is still possible
-to run @command{guix-daemon} provided you pass @code{--disable-chroot}.
-However, build processes will not be isolated from one another, and not
-from the rest of the system.  Thus, build processes may interfere with
-each other, and may access programs, libraries, and other files
-available on the system---making it much harder to view them as
address@hidden functions.
-
-
address@hidden Daemon Offload Setup
address@hidden Using the Offload Facility
-
address@hidden offloading
address@hidden build hook
-When desired, the build daemon can @dfn{offload} derivation builds to
-other machines running Guix, using the @code{offload} @dfn{build
address@hidden feature is available only when
address@hidden://github.com/artyom-poptsov/guile-ssh, Guile-SSH} is
-present.}.  When that
-feature is enabled, a list of user-specified build machines is read from
address@hidden/etc/guix/machines.scm}; every time a build is requested, for
-instance via @code{guix build}, the daemon attempts to offload it to one
-of the machines that satisfy the constraints of the derivation, in
-particular its system type---e.g., @file{x86_64-linux}.  Missing
-prerequisites for the build are copied over SSH to the target machine,
-which then proceeds with the build; upon success the output(s) of the
-build are copied back to the initial machine.
-
-The @file{/etc/guix/machines.scm} file typically looks like this:
+Der Daemon befolgt außerdem den Wert der Umgebungsvariablen
address@hidden für von ihm durchgeführte HTTP-Downloads, sei es für
+Ableitungen mit fester Ausgabe (@pxref{Ableitungen}) oder für Substitute
+(@pxref{Substitute}).
+
+Wenn Sie Guix als ein Benutzer ohne erweiterte Rechte installieren, ist es
+dennoch möglich, @command{guix-daemon} auszuführen, sofern Sie
address@hidden übergeben. Allerdings können Erstellungsprozesse
+dann nicht voneinander und vom Rest des Systems isoliert werden. Daher
+können sich Erstellungsprozesse gegenseitig stören und auf Programme,
+Bibliotheken und andere Dateien zugreifen, die dem restlichen System zur
+Verfügung stehen — was es deutlich schwerer macht, die als @emph{reine}
+Funktionen aufzufassen.
+
+
address@hidden Auslagern des Daemons einrichten
address@hidden Nutzung der Auslagerungsfunktionalität
+
address@hidden auslagern
address@hidden Build-Hook
+Wenn erwünscht kann der Erstellungs-Daemon Ableitungserstellungen
address@hidden auf andere Maschinen, auf denen Guix läuft, mit Hilfe des
address@hidden@address@hidden Funktionalität ist nur
+verfügbar, wenn @uref{https://github.com/artyom-poptsov/guile-ssh,
+Guile-SSH} vorhanden ist.}. Wenn diese Funktionalität aktiviert ist, wird
+eine nutzerspezifizierte Liste von Erstellungsmaschinen aus
address@hidden/etc/guix/machines.scm} gelesen. Wann immer eine Erstellung 
angefragt
+wird, zum Beispiel durch @code{guix build}, versucht der Daemon, sie an eine
+der Erstellungsmaschinen auszulagern, die die Einschränkungen der Ableitung
+erfüllen, insbesondere ihren Systemtyp — z.B. @file{x86_64-linux}. Fehlende
+Voraussetzungen für die Erstellung werden über SSH auf die Zielmaschine
+kopiert, welche dann mit der Erstellung weitermacht. Hat sie Erfolg damit,
+so werden die Ausgabe oder Ausgaben der Erstellung zurück auf die
+ursprüngliche Maschine kopiert.
+
+Die Datei @file{/etc/guix/machines.scm} sieht normalerweise so aus:
 
 @example
 (list (build-machine
@@ -929,7 +1031,7 @@ The @file{/etc/guix/machines.scm} file typically looks 
like this:
         (system "x86_64-linux")
         (host-key "ssh-ed25519 address@hidden")
         (user "bob")
-        (speed 2.))     ;incredibly fast!
+        (speed 2.))     ;unglaublich schnell!
 
       (build-machine
         (name "meeps.example.org")
@@ -938,57 +1040,61 @@ The @file{/etc/guix/machines.scm} file typically looks 
like this:
         (user "alice")
         (private-key
          (string-append (getenv "HOME")
-                        "/.ssh/identity-for-guix"))))
+                        "/.ssh/identität-für-guix"))))
 @end example
 
 @noindent
-In the example above we specify a list of two build machines, one for
-the @code{x86_64} architecture and one for the @code{mips64el}
-architecture.
-
-In fact, this file is---not surprisingly!---a Scheme file that is
-evaluated when the @code{offload} hook is started.  Its return value
-must be a list of @code{build-machine} objects.  While this example
-shows a fixed list of build machines, one could imagine, say, using
-DNS-SD to return a list of potential build machines discovered in the
-local network (@pxref{Introduction, Guile-Avahi,, guile-avahi, Using
-Avahi in Guile Scheme Programs}).  The @code{build-machine} data type is
-detailed below.
-
address@hidden {Data Type} build-machine
-This data type represents build machines to which the daemon may offload
-builds.  The important fields are:
+Im obigen Beispiel geben wir eine Liste mit zwei Erstellungsmaschinen vor,
+eine für die @code{x86_64}-Architektur und eine für die
address@hidden
+
+Tatsächlich ist diese Datei — wenig überraschend! — eine Scheme-Datei, die
+ausgewertet wird, wenn der @code{offload}-Hook gestartet wird. Der Wert, den
+sie zurückliefert, muss eine Liste von @code{build-machine}-Objekten
+sein. Obwohl dieses Beispiel eine feste Liste von Erstellungsmaschinen
+zeigt, könnte man auch auf die Idee kommen, etwa mit DNS-SD eine Liste
+möglicher im lokalen Netzwerk entdeckter Erstellungsmaschinen zu liefern
+(@pxref{Einführung, Guile-Avahi,, guile-avahi, Using Avahi in Guile Scheme
+Programs}). Der Datentyp @code{build-machine} wird im Folgenden weiter
+ausgeführt.
+
address@hidden {Datentyp} build-machine
+Dieser Datentyp repräsentiert Erstellungsmaschinen, an die der Daemon
+Erstellungen auslagern darf. Die wichtigen Felder sind:
 
 @table @code
 
 @item name
-The host name of the remote machine.
+Der Hostname der entfernten Maschine.
 
 @item system
-The system type of the remote machine---e.g., @code{"x86_64-linux"}.
+Der Systemtyp der entfernten Maschine — z.B. @code{"x86_64-linux"}.
 
 @item user
-The user account to use when connecting to the remote machine over SSH.
-Note that the SSH key pair must @emph{not} be passphrase-protected, to
-allow non-interactive logins.
+Das Benutzerkonto, mit dem eine Verbindung zur entfernten Maschine über SSH
+aufgebaut werden soll. Beachten Sie, dass das SSH-Schlüsselpaart
address@hidden durch eine Passphrase geschützt sein darf, damit
+nicht-interaktive Anmeldungen möglich sind.
 
 @item host-key
-This must be the machine's SSH @dfn{public host key} in OpenSSH format.
-This is used to authenticate the machine when we connect to it.  It is a
-long string that looks like this:
+Dies muss der @dfn{öffentliche SSH-Host-Schlüssel} der Maschine im
+OpenSSH-Format sein. Er wird benutzt, um die Identität der Maschine zu
+prüfen, wenn wir uns mit ihr verbinden. Er ist eine lange Zeichenkette, die
+ungefähr so aussieht:
 
 @example
 ssh-ed25519 address@hidden hint@@example.org
 @end example
 
-If the machine is running the OpenSSH daemon, @command{sshd}, the host
-key can be found in a file such as
address@hidden/etc/ssh/ssh_host_ed25519_key.pub}.
+Wenn auf der Maschine der OpenSSH-Daemon, @command{sshd}, läuft, ist der
+Host-Schlüssel in einer Datei wie @file{/etc/ssh/ssh_host_ed25519_key.pub}
+zu finden.
 
-If the machine is running the SSH daemon of address@hidden,
address@hidden, the host key is in @file{/etc/lsh/host-key.pub} or a
-similar file.  It can be converted to the OpenSSH format using
address@hidden (@pxref{Converting keys,,, lsh, LSH Manual}):
+Wenn auf der Maschine der SSH-Daemon von address@hidden, nämlich
address@hidden, läuft, befindet sich der Host-Schlüssel in
address@hidden/etc/lsh/host-key.pub} oder einer ähnlichen Datei. Er kann ins
+OpenSSH-Format umgewandelt werden durch @command{lsh-export-key}
+(@pxref{Converting keys,,, lsh, LSH Manual}):
 
 @example
 $ lsh-export-key --openssh < /etc/lsh/host-key.pub 
@@ -997,408 +1103,443 @@ ssh-rsa address@hidden
 
 @end table
 
-A number of optional fields may be specified:
+Eine Reihe optionaler Felder kann festgelegt werden:
 
 @table @asis
 
address@hidden @code{port} (default: @code{22})
-Port number of SSH server on the machine.
address@hidden @code{port} (Vorgabe: @code{22})
+Portnummer des SSH-Servers auf der Maschine.
 
address@hidden @code{private-key} (default: @file{~root/.ssh/id_rsa})
-The SSH private key file to use when connecting to the machine, in
-OpenSSH format.  This key must not be protected with a passphrase.
address@hidden @code{private-key} (Vorgabe: @file{~root/.ssh/id_rsa})
+The SSH private key file to use when connecting to the machine, in OpenSSH
+format.  This key must not be protected with a passphrase.
 
-Note that the default value is the private key @emph{of the root
-account}.  Make sure it exists if you use the default.
+Beachten Sie, dass als Vorgabewert der private Schlüssel @emph{des
+root-Benutzers} genommen wird. Vergewissern Sie sich, dass er existiert,
+wenn Sie die Standardeinstellung verwenden.
 
address@hidden @code{compression} (default: @code{"zlib@@openssh.com,zlib"})
address@hidden @code{compression-level} (default: @code{3})
-The SSH-level compression methods and compression level requested.
address@hidden @code{compression} (Vorgabe: @code{"zlib@@openssh.com,zlib"})
address@hidden @code{compression-level} (Vorgabe: @code{3})
+Die Kompressionsmethoden auf SSH-Ebene und das angefragte
+Kompressionsniveau.
 
-Note that offloading relies on SSH compression to reduce bandwidth usage
-when transferring files to and from build machines.
+Beachten Sie, dass Auslagerungen SSH-Kompression benötigen, um beim
+Übertragen von Dateien an Erstellungsmaschinen und zurück weniger Bandbreite
+zu benutzen.
 
address@hidden @code{daemon-socket} (default: 
@code{"/var/guix/daemon-socket/socket"})
-File name of the Unix-domain socket @command{guix-daemon} is listening
-to on that machine.
address@hidden @code{daemon-socket} (Vorgabe: 
@code{"/var/guix/daemon-socket/socket"})
+Dateiname des Unix-Sockets, auf dem @command{guix-daemon} auf der Maschine
+lauscht.
 
address@hidden @code{parallel-builds} (default: @code{1})
-The number of builds that may run in parallel on the machine.
address@hidden @code{parallel-builds} (Vorgabe: @code{1})
+Die Anzahl der Erstellungen, die auf der Maschine parallel ausgeführt werden
+können.
 
address@hidden @code{speed} (default: @code{1.0})
-A ``relative speed factor''.  The offload scheduler will tend to prefer
-machines with a higher speed factor.
address@hidden @code{speed} (Vorgabe: @code{1.0})
+Ein »relativer Geschwindigkeitsfaktor«. Der Auslagerungsplaner gibt
+tendenziell Maschinen mit höherem Geschwindigkeitsfaktor den Vorrang.
 
address@hidden @code{features} (default: @code{'()})
-A list of strings denoting specific features supported by the machine.
-An example is @code{"kvm"} for machines that have the KVM Linux modules
-and corresponding hardware support.  Derivations can request features by
-name, and they will be scheduled on matching build machines.
address@hidden @code{features} (Vorgabe: @code{'()})
+Eine Liste von Zeichenketten, die besondere von der Maschine unterstützte
+Funktionalitäten bezeichnen. Ein Beispiel ist @code{"kvm"} für Maschinen,
+die über die KVM-Linux-Module zusammen mit entsprechender
+Hardware-Unterstützung verfügen. Ableitungen können Funktionalitäten dem
+Namen nach anfragen und werden dann auf passenden Erstellungsmaschinen
+eingeplant.
 
 @end table
 @end deftp
 
-The @code{guile} command must be in the search path on the build
-machines.  In addition, the Guix modules must be in
address@hidden on the build machine---you can check whether
-this is the case by running:
+Der Befehl @code{guile} muss sich im Suchpfad der Erstellungsmaschinen
+befinden. Zusätzlich müssen die Guix-Module im @code{$GUILE_LOAD_PATH} auf
+den Erstellungsmaschinen zu finden sein — um dies nachzuprüfen, können Sie
+Folgendes ausführen:
 
 @example
 ssh build-machine guile -c "'(use-modules (guix config))'"
 @end example
 
-There is one last thing to do once @file{machines.scm} is in place.  As
-explained above, when offloading, files are transferred back and forth
-between the machine stores.  For this to work, you first need to
-generate a key pair on each machine to allow the daemon to export signed
-archives of files from the store (@pxref{Invoking guix archive}):
+Es gibt noch eine weitere Sache zu tun, sobald @file{machines.scm}
+eingerichtet ist. Wie zuvor erklärt, werden beim Auslagern Dateien zwischen
+den Stores der Maschinen hin- und hergeschickt. Damit das funktioniert,
+müssen Sie als Erstes ein Schlüsselpaar auf jeder Maschine erzeugen, damit
+der Daemon signierte Archive mit den Dateien aus dem Store versenden kann
+(@pxref{Aufruf von guix archive}):
 
 @example
 # guix archive --generate-key
 @end example
 
 @noindent
-Each build machine must authorize the key of the master machine so that
-it accepts store items it receives from the master:
+Jede Erstellungsmaschine muss den Schlüssel der Hauptmaschine autorisieren,
+damit diese Store-Objekte von der Hauptmaschine empfangen kann:
 
 @example
-# guix archive --authorize < master-public-key.txt
+# guix archive --authorize < öffentlicher-schlüssel-hauptmaschine.txt
 @end example
 
 @noindent
-Likewise, the master machine must authorize the key of each build machine.
+Andersherum muss auch die Hauptmaschine den jeweiligen Schlüssel jeder
+Erstellungsmaschine autorisieren.
 
-All the fuss with keys is here to express pairwise mutual trust
-relations between the master and the build machines.  Concretely, when
-the master receives files from a build machine (and @i{vice versa}), its
-build daemon can make sure they are genuine, have not been tampered
-with, and that they are signed by an authorized key.
+Der ganze Umstand mit den Schlüsseln soll ausdrücken, dass sich Haupt- und
+Erstellungsmaschinen paarweise gegenseitig vertrauen. Konkret kann der
+Erstellungs-Daemon auf der Hauptmaschine die Echtheit von den
+Erstellungsmaschinen empfangener Dateien gewährleisten (und umgekehrt), und
+auch dass sie nicht sabotiert wurden und mit einem autorisierten Schlüssel
+signiert wurden.
 
address@hidden offload test
-To test whether your setup is operational, run this command on the
-master node:
address@hidden Auslagerung testen
+Um zu testen, ob Ihr System funktioniert, führen Sie diesen Befehl auf der
+Hauptmaschine aus:
 
 @example
 # guix offload test
 @end example
 
-This will attempt to connect to each of the build machines specified in
address@hidden/etc/guix/machines.scm}, make sure Guile and the Guix modules are
-available on each machine, attempt to export to the machine and import
-from it, and report any error in the process.
+Dadurch wird versucht, zu jeder Erstellungsmaschine eine Verbindung
+herzustellen, die in @file{/etc/guix/machines.scm} angegeben wurde,
+sichergestellt, dass auf jeder Guile und die Guix-Module nutzbar sind, und
+jeweils versucht, etwas auf die Erstellungsmaschine zu exportieren und von
+dort zu imporieren. Dabei auftretende Fehler werden gemeldet.
 
-If you want to test a different machine file, just specify it on the
-command line:
+Wenn Sie stattdessen eine andere Maschinendatei verwenden möchten, geben Sie
+diese einfach auf der Befehlszeile an:
 
 @example
-# guix offload test machines-qualif.scm
+# guix offload test maschinen-qualif.scm
 @end example
 
-Last, you can test the subset of the machines whose name matches a
-regular expression like this:
+Letztendlich können Sie hiermit nur die Teilmenge der Maschinen testen,
+deren Name zu einem regulären Ausdruck passt:
 
 @example
-# guix offload test machines.scm '\.gnu\.org$'
+# guix offload test maschinen.scm '\.gnu\.org$'
 @end example
 
address@hidden offload status
-To display the current load of all build hosts, run this command on the
-main node:
address@hidden Auslagerungs-Lagebericht
+Um die momentane Auslastung aller Erstellungs-Hosts anzuzeigen, führen Sie
+diesen Befehl auf dem Hauptknoten aus:
 
 @example
 # guix offload status
 @end example
 
 
address@hidden SELinux Support
address@hidden SELinux Support
address@hidden SELinux-Unterstützung
address@hidden SELinux-Unterstützung
 
address@hidden SELinux, daemon policy
address@hidden mandatory access control, SELinux
address@hidden security, guix-daemon
-Guix includes an SELinux policy file at @file{etc/guix-daemon.cil} that
-can be installed on a system where SELinux is enabled, in order to label
-Guix files and to specify the expected behavior of the daemon.  Since
-GuixSD does not provide an SELinux base policy, the daemon policy cannot
-be used on GuixSD.
address@hidden SELinux, Policy für den Daemon
address@hidden Mandatory Access Control, SELinux
address@hidden Sicherheit, des guix-daemon
+Guix enthält eine SELinux-Richtliniendatei (»Policy«) unter
address@hidden/guix-daemon.cil}, die auf einem System installiert werden
+kann, auf dem SELinux aktiviert ist, damit Guix-Dateien gekennzeichnet
+sind, und um das erwartete Verhalten des Daemons anzugeben. Da GuixSD
+keine Grundrichtlinie (»Base Policy«) für SELinux bietet, kann diese
+Richtlinie für den Daemon auf GuixSD nicht benutzt werden.
 
address@hidden Installing the SELinux policy
address@hidden SELinux, policy installation
-To install the policy run this command as root:
address@hidden Installieren der SELinux-Policy
address@hidden SELinux, Policy installieren
+Um die Richtlinie (Policy) zu installieren, führen Sie folgenden Befehl mit
+Administratorrechten aus:
 
 @example
 semodule -i etc/guix-daemon.cil
 @end example
 
-Then relabel the file system with @code{restorecon} or by a different
-mechanism provided by your system.
+Kennzeichnen Sie dann das Dateisystem neu mit @code{restorecon} oder einem
+anderen, von Ihrem System angebotenen Mechanismus.
 
-Once the policy is installed, the file system has been relabeled, and
-the daemon has been restarted, it should be running in the
address@hidden context.  You can confirm this with the following
-command:
+Sobald die Richtlinie installiert ist, das Dateisystem neu gekennzeichnet
+wurde und der Daemon neugestartet wurde, sollte er im Kontext
address@hidden laufen. Sie können dies mit dem folgenden Befehl
+nachprüfen:
 
 @example
 ps -Zax | grep guix-daemon
 @end example
 
-Monitor the SELinux log files as you run a command like @code{guix build
-hello} to convince yourself that SELinux permits all necessary
-operations.
+Beobachten Sie die Protokolldateien von SELinux, wenn Sie einen Befehl wie
address@hidden build hello} ausführen, um sich zu überzeugen, dass SELinux alle
+notwendigen Operationen gestattet.
 
address@hidden Limitations
address@hidden SELinux, limitations
address@hidden Einschränkungen
address@hidden SELinux, Einschränkungen
 
-This policy is not perfect.  Here is a list of limitations or quirks
-that should be considered when deploying the provided SELinux policy for
-the Guix daemon.
+Diese Richtlinie ist nicht perfekt. Im Folgenden finden Sie eine Liste von
+Einschränkungen oder merkwürdiger Verhaltensweisen, die bedacht werden
+sollten, wenn man die mitgelieferte SELinux-Richtlinie für den Guix-Daemon
+einspielt.
 
 @enumerate
 @item
address@hidden isn’t actually used.  None of the socket
-operations involve contexts that have anything to do with
address@hidden  It doesn’t hurt to have this unused label,
-but it would be preferrable to define socket rules for only this label.
address@hidden wird nicht wirklich benutzt. Keine der
+Socket-Operationen benutzt Kontexte, die irgendetwas mit
address@hidden zu tun haben. Es schadet nicht, diese ungenutzte
+Kennzeichnung zu haben, aber es wäre besser, für die Kennzeichnung auch
+Socket-Regeln festzulegen.
 
 @item
address@hidden gc} cannot access arbitrary links to profiles.  By design,
-the file label of the destination of a symlink is independent of the
-file label of the link itself.  Although all profiles under
-$localstatedir are labelled, the links to these profiles inherit the
-label of the directory they are in.  For links in the user’s home
-directory this will be @code{user_home_t}.  But for links from the root
-user’s home directory, or @file{/tmp}, or the HTTP server’s working
-directory, etc, this won’t work.  @code{guix gc} would be prevented from
-reading and following these links.
address@hidden gc} kann nicht auf beliebige Verknüpfungen zu Profilen
+zugreifen. Die Kennzeichnung des Ziels einer symbolischen Verknüpfung ist
+notwendigerweise unabhängig von der Dateikennzeichnung der
+Verknüpfung. Obwohl alle Profile unter $localstatedir gekennzeichnet sind,
+erben die Verknüpfungen auf diese Profile die Kennzeichnung desjenigen
+Verzeichnisses, in dem sie sich befinden. Für Verknüpfungen im Persönlichen
+Ordner des Benutzers ist das @code{user_home_t}, aber Verknüpfungen aus dem
+Persönlichen Ordner des Administratornutzers, oder @file{/tmp}, oder das
+Arbeitsverzeichnis des HTTP-Servers, etc., funktioniert das
+nicht. @code{guix gc} würde es nicht gestattet, diese Verknüpfungen
+auszulesen oder zu verfolgen.
 
 @item
-The daemon’s feature to listen for TCP connections might no longer work.
-This might require extra rules, because SELinux treats network sockets
-differently from files.
+Die vom Daemon gebotene Funktionalität, auf TCP-Verbindungen zu lauschen,
+könnte nicht mehr funktionieren. Dies könnte zusätzliche Regeln brauchen,
+weil SELinux Netzwerk-Sockets anders behandelt als Dateien.
 
 @item
-Currently all files with a name matching the regular expression
address@hidden/gnu/store/.+-(guix-.+|profile)/bin/guix-daemon} are assigned the
-label @code{guix_daemon_exec_t}; this means that @emph{any} file with
-that name in any profile would be permitted to run in the
address@hidden domain.  This is not ideal.  An attacker could
-build a package that provides this executable and convince a user to
-install and run it, which lifts it into the @code{guix_daemon_t} domain.
-At that point SELinux could not prevent it from accessing files that are
-allowed for processes in that domain.
-
-We could generate a much more restrictive policy at installation time,
-so that only the @emph{exact} file name of the currently installed
address@hidden executable would be labelled with
address@hidden, instead of using a broad regular expression.
-The downside is that root would have to install or upgrade the policy at
-installation time whenever the Guix package that provides the
-effectively running @code{guix-daemon} executable is upgraded.
+Derzeit wird allen Dateien mit einem Namen, der zum regulären Ausdruck
address@hidden/gnu/store/.+-(guix-.+|profile)/bin/guix-daemon} passt, die
+Kennzeichnung @code{guix_daemon_exec_t} zugewiesen, wodurch @emph{jedee
+beliebigee} Datei mit diesem Namen in irgendeinem Profil gestatttet wäre, in
+der Domäne @code{guix_daemon_t} ausgeführt zu werden. Das ist nicht
+ideal. Ein Angreifer könnte ein Paket erstellen, dass solch eine ausführbare
+Datei enthält, und den Nutzer überzeugen, es zu installieren und
+auszuführen. Dadurch käme es in die Domäne @code{guix_daemon_t}. Ab diesem
+Punkt könnte SELinux nicht mehr verhindern, dass es auf Dateien zugreift,
+auf die Prozesse in dieser Domäne zugreifen dürfen.
+
+Wir könnten zum Zeitpunkt der Installation eine wesentlich restriktivere
+Richtlinie generieren, für die nur @emph{genau derselbe} Dateiname des
+gerade installierten @code{guix-daemon}-Programms als
address@hidden gekennzeichnet würde, statt einen vieles
+umfassenden regulären Ausdruck zu benutzen. Aber dann müsste der
+Administratornutzer zum Zeitpunkt der Installation jedes Mal die Richtlinie
+installieren oder aktualisieren müssen, sobald das Guix-Paket aktualisiert
+wird, dass das tatsächlich in Benutzung befindliche
address@hidden enthält.
 @end enumerate
 
address@hidden Invoking guix-daemon
address@hidden Invoking @command{guix-daemon}
address@hidden Aufruf des guix-daemon
address@hidden Aufruf von @command{guix-daemon}
 
-The @command{guix-daemon} program implements all the functionality to
-access the store.  This includes launching build processes, running the
-garbage collector, querying the availability of a build result, etc.  It
-is normally run as @code{root} like this:
+Das Programm @command{guix-daemon} implementiert alle Funktionalitäten, um
+auf den Store zuzugreifen. Dazu gehört das Starten von Erstellungsprozessen,
+das Ausführen des Müllsammlers, das Abfragen, ob ein Erstellungsergebnis
+verfügbar ist, etc. Normalerweise wird er so als Administratornutzer
+(@code{root}) gestartet:
 
 @example
 # guix-daemon --build-users-group=guixbuild
 @end example
 
 @noindent
-For details on how to set it up, @pxref{Setting Up the Daemon}.
+Details, wie Sie ihn einrichten, finden Sie im Abschnitt @pxref{Den Daemon 
einrichten}.
 
 @cindex chroot
address@hidden container, build environment
address@hidden build environment
address@hidden reproducible builds
-By default, @command{guix-daemon} launches build processes under
-different UIDs, taken from the build group specified with
address@hidden  In addition, each build process is run in a
-chroot environment that only contains the subset of the store that the
-build process depends on, as specified by its derivation
-(@pxref{Programming Interface, derivation}), plus a set of specific
-system directories.  By default, the latter contains @file{/dev} and
address@hidden/dev/pts}.  Furthermore, on GNU/Linux, the build environment is a
address@hidden: in addition to having its own file system tree, it has
-a separate mount name space, its own PID name space, network name space,
-etc.  This helps achieve reproducible builds (@pxref{Features}).
-
-When the daemon performs a build on behalf of the user, it creates a
-build directory under @file{/tmp} or under the directory specified by
-its @code{TMPDIR} environment variable; this directory is shared with
-the container for the duration of the build.  Be aware that using a
-directory other than @file{/tmp} can affect build results---for example,
-with a longer directory name, a build process that uses Unix-domain
-sockets might hit the name length limitation for @code{sun_path}, which
-it would otherwise not hit.
-
-The build directory is automatically deleted upon completion, unless the
-build failed and the client specified @option{--keep-failed}
-(@pxref{Invoking guix build, @option{--keep-failed}}).
-
-The daemon listens for connections and spawns one sub-process for each session
-started by a client (one of the @command{guix} sub-commands.)  The
address@hidden processes} command allows you to get an overview of the activity
-on your system by viewing each of the active sessions and clients.
address@hidden Container, Erstellungsumgebung
address@hidden Erstellungsumgebung
address@hidden Reproduzierbare Erstellungen
+Standardmäßig führt @command{guix-daemon} Erstellungsprozesse mit
+unterschiedlichen UIDs aus, die aus der Erstellungsgruppe stammen, deren
+Name mit @code{--build-users-group} übergeben wurde. Außerdem läuft jeder
+Erstellungsprozess in einer chroot-Umgebung, die nur die Teilmenge des
+Stores enthält, von der der Erstellungsprozess abhängt, entsprechend seiner
+Ableitung (@pxref{Programmierschnittstelle, derivation}), und ein paar
+bestimmte Systemverzeichnisse, darunter standardmäßig auch @file{/dev} und
address@hidden/dev/pts}. Zudem ist die Erstellungsumgebung auf GNU/Linux ein
address@hidden: Nicht nur hat er seinen eigenen Dateisystembaum, er hat
+auch einen separaten Namensraum zum Einhängen von Dateisystemen, seinen
+eigenen Namensraum für PIDs, für Netzwerke, etc. Dies hilft dabei,
+reproduzierbare Erstellungen zu garantieren (@pxref{Funktionalitäten}).
+
+When the daemon performs a build on behalf of the user, it creates a build
+directory under @file{/tmp} or under the directory specified by its
address@hidden environment variable; this directory is shared with the
+container for the duration of the build.  Be aware that using a directory
+other than @file{/tmp} can affect build results---for example, with a longer
+directory name, a build process that uses Unix-domain sockets might hit the
+name length limitation for @code{sun_path}, which it would otherwise not
+hit.
+
+Nach Abschluss der Erstellung wird das Erstellungsverzeichnis automatisch
+entfernt, außer wenn die Erstellung fehlgeschlagen ist und der Client
address@hidden angegeben hat (@pxref{Aufruf von guix build,
address@hidden).
+
+The daemon listens for connections and spawns one sub-process for each
+session started by a client (one of the @command{guix} sub-commands.)  The
address@hidden processes} command allows you to get an overview of the
+activity on your system by viewing each of the active sessions and clients.
 @xref{Invoking guix processes}, for more information.
 
-The following command-line options are supported:
+Die folgenden Befehlszeilenoptionen werden unterstützt:
 
 @table @code
address@hidden address@hidden
-Take users from @var{group} to run build processes (@pxref{Setting Up
-the Daemon, build users}).
address@hidden address@hidden
+Verwende die Benutzerkonten aus der @var{Gruppe}, um Erstellungsprozesse
+auszuführen (@pxref{Den Daemon einrichten, build users}).
 
 @item --no-substitutes
address@hidden substitutes
-Do not use substitutes for build products.  That is, always build things
-locally instead of allowing downloads of pre-built binaries
-(@pxref{Substitutes}).
address@hidden Substitute
+Benutze keine Substitute für Erstellungsergebnisse. Das heißt, dass alle
+Objekte lokal erstellt werden müssen, und kein Herunterladen von vorab
+erstellten Binärdateien erlaubt ist (@pxref{Substitute}).
 
-When the daemon runs with @code{--no-substitutes}, clients can still
-explicitly enable substitution @i{via} the @code{set-build-options}
-remote procedure call (@pxref{The Store}).
+Wenn der Daemon mit @code{--no-substitutes} ausgeführt wird, können Clients
+trotzdem Substitute explizit aktivieren über den entfernten Prozeduraufruf
address@hidden (@pxref{Der Store}).
 
address@hidden address@hidden
address@hidden address@hidden
 @anchor{daemon-substitute-urls}
-Consider @var{urls} the default whitespace-separated list of substitute
-source URLs.  When this option is omitted,
address@hidden://mirror.hydra.gnu.org https://hydra.gnu.org} is used
-(@code{mirror.hydra.gnu.org} is a mirror of @code{hydra.gnu.org}).
+Benutze @var{URLs} als standardmäßige, leerzeichengetrennte Liste der
+Quell-URLs für Substitute. Wenn diese Befehlszeilenoption nicht angegeben
+wird, wird @indicateurl{https://mirror.hydra.gnu.org https://hydra.gnu.org}
+verwendet (@code{mirror.hydra.gnu.org} ist ein Spiegelserver für
address@hidden).
 
-This means that substitutes may be downloaded from @var{urls}, as long
-as they are signed by a trusted signature (@pxref{Substitutes}).
+Das hat zur Folge, dass Substitute von den @var{URLs} heruntergeladen werden
+können, solange sie mit einer Signatur versehen sind, der vertraut wird
+(@pxref{Substitute}).
 
address@hidden build hook
address@hidden Build-Hook
 @item --no-build-hook
-Do not use the @dfn{build hook}.
+Den address@hidden nicht benutzen.
 
-The build hook is a helper program that the daemon can start and to
-which it submits build requests.  This mechanism is used to offload
-builds to other machines (@pxref{Daemon Offload Setup}).
+»Build-Hook« ist der Name eines Hilfsprogramms, das der Daemon starten kann
+und an das er Erstellungsanfragen übermittelt. Durch diesen Mechanismus
+können Erstellungen an andere Maschinen ausgelagert werden (@pxref{Auslagern 
des Daemons einrichten}).
 
 @item --cache-failures
-Cache build failures.  By default, only successful builds are cached.
+Fehler bei der Erstellung zwischenspeichern. Normalerweise werden nur
+erfolgreiche Erstellungen gespeichert.
 
-When this option is used, @command{guix gc --list-failures} can be used
-to query the set of store items marked as failed; @command{guix gc
---clear-failures} removes store items from the set of cached failures.
address@hidden guix gc}.
+Wenn diese Befehlszeilenoption benutzt wird, kann @command{guix gc
+--list-failures} benutzt werden, um die Menge an Store-Objekten abzufragen,
+die als Fehlschläge markiert sind; @command{guix gc --clear-failures}
+entfernt Store-Objekte aus der Menge zwischengespeicherter
+Fehlschläge. @xref{Aufruf von guix gc}.
 
 @item address@hidden
 @itemx -c @var{n}
-Use @var{n} CPU cores to build each derivation; @code{0} means as many
-as available.
address@hidden CPU-Kerne zum Erstellen jeder Ableitung benutzen; @code{0} 
heißt, so
+viele wie verfügbar sind.
 
-The default value is @code{0}, but it may be overridden by clients, such
-as the @code{--cores} option of @command{guix build} (@pxref{Invoking
-guix build}).
+Der Vorgabewert ist @code{0}, jeder Client kann jedoch eine abweichende
+Anzahl vorgeben, zum Beispiel mit der Befehlszeilenoption @code{--cores} von
address@hidden build} (@pxref{Aufruf von guix build}).
 
-The effect is to define the @code{NIX_BUILD_CORES} environment variable
-in the build process, which can then use it to exploit internal
-parallelism---for instance, by running @code{make -j$NIX_BUILD_CORES}.
+Dadurch wird die Umgebungsvariable @code{NIX_BUILD_CORES} im
+Erstellungsprozess definiert, welcher sie benutzen kann, um intern parallele
+Ausführungen zuzulassen — zum Beispiel durch Nutzung von @code{make
+-j$NIX_BUILD_CORES}.
 
 @item address@hidden
 @itemx -M @var{n}
-Allow at most @var{n} build jobs in parallel.  The default value is
address@hidden  Setting it to @code{0} means that no builds will be performed
-locally; instead, the daemon will offload builds (@pxref{Daemon Offload
-Setup}), or simply fail.
+Höchstenss @var{n} Erstellungsaufträge parallel bearbeiten. Der Vorgabewert
+liegt bei @code{1}. Wird er auf @code{0} gesetzt, werden keine Erstellungen
+lokal durchgeführt, stattdessen lagert der Daemon sie nur aus 
(@pxref{Auslagern des Daemons einrichten}) oder sie schlagen einfach fehl.
 
address@hidden address@hidden
-When the build or substitution process remains silent for more than
address@hidden, terminate it and report a build failure.
address@hidden address@hidden
+Wenn der Erstellungs- oder Substitutionsprozess länger als
address@hidden keine Ausgabe erzeugt, wird er abgebrochen und ein
+Fehler beim Erstellen gemeldet.
 
-The default value is @code{0}, which disables the timeout.
+Der Vorgabewert ist @code{0}, was bedeutet, dass es keine Zeitbeschränkung
+gibt.
 
-The value specified here can be overridden by clients (@pxref{Common
-Build Options, @code{--max-silent-time}}).
+Clients können einen anderen Wert als den hier angegebenen verwenden lassen
+(@pxref{Gemeinsame Erstellungsoptionen, @code{--max-silent-time}}).
 
address@hidden address@hidden
-Likewise, when the build or substitution process lasts for more than
address@hidden, terminate it and report a build failure.
address@hidden address@hidden
+Entsprechend wird hier der Erstellungs- oder Substitutionsprozess
+abgebrochen und als Fehlschlag gemeldet, wenn er mehr als
address@hidden dauert.
 
-The default value is @code{0}, which disables the timeout.
+Der Vorgabewert ist @code{0}, was bedeutet, dass es keine Zeitbeschränkung
+gibt.
 
-The value specified here can be overridden by clients (@pxref{Common
-Build Options, @code{--timeout}}).
+Clients können einen anderen Wert verwenden lassen (@pxref{Gemeinsame 
Erstellungsoptionen, @code{--timeout}}).
 
 @item address@hidden
-Build each derivation @var{n} times in a row, and raise an error if
-consecutive build results are not bit-for-bit identical.  Note that this
-setting can be overridden by clients such as @command{guix build}
-(@pxref{Invoking guix build}).
+Jede Ableitung @var{n}-mal hintereinander erstellen und einen Fehler melden,
+wenn nacheinander ausgewertete Erstellungsergebnisse nicht Bit für Bit
+identisch sind. Beachten Sie, dass Clients wie @command{guix build} einen
+anderen Wert verwenden lassen können (@pxref{Aufruf von guix build}).
 
-When used in conjunction with @option{--keep-failed}, the differing
-output is kept in the store, under @file{/gnu/store/@dots{}-check}.
-This makes it easy to look for differences between the two results.
+Wenn dies zusammen mit @option{--keep-failed} benutzt wird, bleiben die sich
+unterscheidenden Ausgaben im Store unter dem Namen
address@hidden/gnu/store/@dots{}-check}. Dadurch können Unterschiede zwischen 
den
+beiden Ergebnissen leicht erkannt werden.
 
 @item --debug
-Produce debugging output.
+Informationen zur Fehlersuche ausgeben.
 
-This is useful to debug daemon start-up issues, but then it may be
-overridden by clients, for example the @code{--verbosity} option of
address@hidden build} (@pxref{Invoking guix build}).
+Dies ist nützlich, um Probleme beim Starten des Daemons nachzuvollziehen;
+Clients könn aber auch ein abweichenden Wert verwenden lassen, zum Beispiel
+mit der Befehlszeilenoption @code{--verbosity} von @command{guix build}
+(@pxref{Aufruf von guix build}).
 
address@hidden address@hidden
-Add @var{dir} to the build chroot.
address@hidden address@hidden
+Füge das @var{Verzeichnis} zum chroot von Erstellungen hinzu.
 
-Doing this may change the result of build processes---for instance if
-they use optional dependencies found in @var{dir} when it is available,
-and not otherwise.  For that reason, it is not recommended to do so.
-Instead, make sure that each derivation declares all the inputs that it
-needs.
+Dadurch kann sich das Ergebnis von Erstellungsprozessen ändern — zum
+Beispiel, wenn diese optionale Abhängigkeiten aus dem @var{Verzeichnis}
+verwenden, wenn sie verfügbar sind, und nicht, wenn es fehlt. Deshalb ist es
+nicht empfohlen, dass Sie diese Befehlszeilenoption besser verwenden, besser
+sollten Sie dafür sorgen, dass jede Ableitung alle von ihr benötigten
+Eingabgen deklariert.
 
 @item --disable-chroot
-Disable chroot builds.
+Erstellungen ohne chroot durchführen.
 
-Using this option is not recommended since, again, it would allow build
-processes to gain access to undeclared dependencies.  It is necessary,
-though, when @command{guix-daemon} is running under an unprivileged user
-account.
+Diese Befehlszeilenoption zu benutzen, wird nicht empfohlen, denn auch
+dadurch bekämen Erstellungsprozesse Zugriff auf nicht deklarierte
+Abhängigkeiten. Sie ist allerdings unvermeidlich, wenn @command{guix-daemon}
+auf einem Benutzerkonto ohne ausreichende Berechtigungen ausgeführt wird.
 
address@hidden address@hidden
-Compress build logs according to @var{type}, one of @code{gzip},
address@hidden, or @code{none}.
address@hidden address@hidden
+Erstellungsprotokolle werden entsprechend dem @var{Typ} komprimiert, der
+entweder @code{gzip}, @code{bzip2} oder @code{none} (für keine Kompression)
+sein muss.
 
-Unless @code{--lose-logs} is used, all the build logs are kept in the
address@hidden  To save space, the daemon automatically compresses
-them with bzip2 by default.
+Sofern nicht @code{--lose-logs} angegeben wurde, werden alle
+Erstellungsprotokolle in der @var{localstatedir} gespeichert. Um Platz zu
+sparen, komprimiert sie der Daemon standardmäßig automatisch mit bzip2.
 
 @item --disable-deduplication
address@hidden deduplication
-Disable automatic file ``deduplication'' in the store.
address@hidden Deduplizieren
+Automatische Dateien-»Deduplizierung« im Store ausschalten.
 
-By default, files added to the store are automatically ``deduplicated'':
-if a newly added file is identical to another one found in the store,
-the daemon makes the new file a hard link to the other file.  This can
-noticeably reduce disk usage, at the expense of slightly increased
-input/output load at the end of a build process.  This option disables
-this optimization.
+Standardmäßig werden zum Store hinzugefügte Objekte automatisch
+»dedupliziert«: Wenn eine neue Datei mit einer anderen im Store
+übereinstimmt, wird die neue Datei stattdessen als harte Verknüpfung auf die
+andere Datei angelegt. Dies reduziert den Speicherverbrauch auf der Platte
+merklich, jedoch steigt andererseits die Auslastung bei der Ein-/Ausgabe im
+Erstellungsprozess geringfügig. Durch diese Option wird keine solche
+Optimierung durchgeführt.
 
 @item --gc-keep-outputs[=yes|no]
-Tell whether the garbage collector (GC) must keep outputs of live
-derivations.
+Gibt an, ob der Müllsammler (Garbage Collector, GC) die Ausgaben lebendiger
+Ableitungen behalten muss (»yes«) oder nicht (»no«).
 
address@hidden GC roots
address@hidden garbage collector roots
address@hidden GC-Wurzeln
address@hidden Müllsammlerwurzeln
 When set to ``yes'', the GC will keep the outputs of any live derivation
 available in the store---the @code{.drv} files.  The default is ``no'',
-meaning that derivation outputs are kept only if they are reachable from a GC
-root.  @xref{Invoking guix gc}, for more on GC roots.
+meaning that derivation outputs are kept only if they are reachable from a
+GC root.  @xref{Aufruf von guix gc}, for more on GC roots.
 
 @item --gc-keep-derivations[=yes|no]
-Tell whether the garbage collector (GC) must keep derivations
-corresponding to live outputs.
+Gibt an, ob der Müllsammler (GC) Ableitungen behalten muss (»yes«), wenn sie
+lebendige Ausgaben haben, oder nicht (»no«).
 
-When set to ``yes'', as is the case by default, the GC keeps
-derivations---i.e., @code{.drv} files---as long as at least one of their
-outputs is live.  This allows users to keep track of the origins of
-items in their store.  Setting it to ``no'' saves a bit of disk space.
+Für »yes«, den Vorgabewert, behält der Müllsammler Ableitungen —
+z.B. @code{.drv}-Dateien —, solange zumindest eine ihrer Ausgaben lebendig
+ist. Dadurch können Nutzer den Ursprung der Dateien in ihrem Store
+nachvollziehen. Setzt man den Wert auf »no«, wird ein bisschen weniger
+Speicher auf der Platte verbraucht.
 
 In this way, setting @code{--gc-keep-derivations} to ``yes'' causes liveness
 to flow from outputs to derivations, and setting @code{--gc-keep-outputs} to
@@ -1406,202 +1547,214 @@ to flow from outputs to derivations, and setting 
@code{--gc-keep-outputs} to
 set to ``yes'', the effect is to keep all the build prerequisites (the
 sources, compiler, libraries, and other build-time tools) of live objects in
 the store, regardless of whether these prerequisites are reachable from a GC
-root.  This is convenient for developers since it saves rebuilds or downloads.
+root.  This is convenient for developers since it saves rebuilds or
+downloads.
 
 @item --impersonate-linux-2.6
-On Linux-based systems, impersonate Linux 2.6.  This means that the
-kernel's @code{uname} system call will report 2.6 as the release number.
+Auf Linux-basierten Systemen wird hiermit vorgetäuscht, dass es sich um
+Linux 2.6 handeln würde, indem der Kernel für einen
address@hidden als Version der Veröffentlichung mit 2.6
+antwortet.
 
-This might be helpful to build programs that (usually wrongfully) depend
-on the kernel version number.
+Dies kann hilfreich sein, um Programme zu erstellen, die (normalerweise zu
+Unrecht) von der Kernel-Versionsnummer abhängen.
 
 @item --lose-logs
-Do not keep build logs.  By default they are kept under
address@hidden@var{localstatedir}/guix/log}.
+Keine Protokolle der Erstellungen vorhalten. Normalerweise würden solche in
address@hidden@var{localstatedir}/guix/log} gespeichert.
 
address@hidden address@hidden
-Assume @var{system} as the current system type.  By default it is the
-architecture/kernel pair found at configure time, such as
address@hidden
address@hidden address@hidden
+Verwende @var{System} als aktuellen Systemtyp. Standardmäßig ist dies das
+Paar aus Befehlssatz und Kernel, welches beim Aufruf von @code{configure}
+erkannt wurde, wie zum Beispiel @code{x86_64-linux}.
 
address@hidden address@hidden
-Listen for connections on @var{endpoint}.  @var{endpoint} is interpreted
-as the file name of a Unix-domain socket if it starts with
address@hidden/} (slash sign).  Otherwise, @var{endpoint} is interpreted as a
-host name or host name and port to listen to.  Here are a few examples:
address@hidden address@hidden
+Lausche am @var{Endpunkt} auf Verbindungen. Dabei wird der @var{Endpunkt}
+als Dateiname eines Unix-Sockets verstanden, wenn er mit einem @code{/}
+(Schrägstrich) beginnt. Andernfalls wird der @var{Endpunkt} als Hostname
+oder als Hostname-Port-Paar verstanden, auf dem gelauscht wird. Hier sind
+ein paar Beispiele:
 
 @table @code
 @item --listen=/gnu/var/daemon
-Listen for connections on the @file{/gnu/var/daemon} Unix-domain socket,
-creating it if needed.
+Lausche auf Verbindungen am Unix-Socket @file{/gnu/var/daemon}, falls nötig
+wird er dazu erstellt.
 
 @item --listen=localhost
address@hidden daemon, remote access
address@hidden remote access to the daemon
address@hidden daemon, cluster setup
address@hidden clusters, daemon setup
-Listen for TCP connections on the network interface corresponding to
address@hidden, on port 44146.
address@hidden Daemon, Fernzugriff
address@hidden Fernzugriff auf den Daemon
address@hidden Daemon, Einrichten auf Clustern
address@hidden Cluster, Einrichtung des Daemons
+Lausche auf TCP-Verbindungen an der Netzwerkschnittstelle, die
address@hidden entspricht, auf Port 44146.
 
 @item --listen=128.0.0.42:1234
-Listen for TCP connections on the network interface corresponding to
address@hidden, on port 1234.
+Lausche auf TCP-Verbindungen an der Netzwerkschnittstelle, die
address@hidden entspricht, auf Port 1234.
 @end table
 
-This option can be repeated multiple times, in which case
address@hidden accepts connections on all the specified
-endpoints.  Users can tell client commands what endpoint to connect to
-by setting the @code{GUIX_DAEMON_SOCKET} environment variable
-(@pxref{The Store, @code{GUIX_DAEMON_SOCKET}}).
-
address@hidden Note
-The daemon protocol is @emph{unauthenticated and unencrypted}.  Using
address@hidden@var{host}} is suitable on local networks, such as
-clusters, where only trusted nodes may connect to the build daemon.  In
-other cases where remote access to the daemon is needed, we recommend
-using Unix-domain sockets along with SSH.
+Diese Befehlszeilenoption kann mehrmals wiederholt werden. In diesem Fall
+akzeptiert @command{guix-daemon} Verbindungen auf allen angegebenen
+Endpunkten. Benutzer können bei Client-Befehlen angeben, mit welchem
+Endpunkt sie sich verbinden möchten, indem sie die Umgebungsvariable
address@hidden festlegen (@pxref{Der Store,
address@hidden).
+
address@hidden Anmerkung
+Das Daemon-Protokoll ist @emph{weder authentifiziert noch
+verschlüsselt}. Die Benutzung von @address@hidden eignet sich für
+lokale Netzwerke, wie z.B. in Rechen-Clustern, wo sich nur solche Knoten mit
+dem Daemon verbinden, denen man vertraut. In Situationen, wo ein Fernzugriff
+auf den Daemon durchgeführt wird, empfehlen wir, über Unix-Sockets in
+Verbindung mit SSH zuzugreifen.
 @end quotation
 
-When @code{--listen} is omitted, @command{guix-daemon} listens for
-connections on the Unix-domain socket located at
address@hidden@var{localstatedir}/guix/daemon-socket/socket}.
+Wird @code{--listen} nicht angegeben, lauscht @command{guix-daemon} auf
+Verbindungen auf dem Unix-Socket, der sich unter
address@hidden@var{localstatedir}/guix/daemon-socket/socket} befindet.
 @end table
 
 
address@hidden Application Setup
address@hidden Application Setup
address@hidden Anwendungen einrichten
address@hidden Anwendungen einrichten
 
address@hidden foreign distro
-When using Guix on top of GNU/Linux distribution other than GuixSD---a
-so-called @dfn{foreign distro}---a few additional steps are needed to
-get everything in place.  Here are some of them.
address@hidden Fremddistribution
+Läuft Guix aufgesetzt auf einer GNU/Linux-Distribution außer GuixSD — einer
+sogenannten @dfn{Fremddistribution} —, so sind ein paar zusätzliche Schritte
+bei der Einrichtung nötig. Hier finden Sie manche davon.
 
 @subsection Locales
 
 @anchor{locales-and-locpath}
address@hidden locales, when not on GuixSD
address@hidden Locales, nicht auf GuixSD
 @vindex LOCPATH
 @vindex GUIX_LOCPATH
-Packages installed @i{via} Guix will not use the locale data of the
-host system.  Instead, you must first install one of the locale packages
-available with Guix and then define the @code{GUIX_LOCPATH} environment
-variable:
+Über Guix installierte Pakete benutzen nicht die Daten zu Regions- und
+Spracheinstellungen (Locales) des Wirtssystems. Stattdessen müssen Sie erst
+eines der Locale-Pakete installieren, die für Guix verfügbar sind, und dann
+den Wert Ihrer Umgebungsvariablen @code{GUIX_LOCPATH} passend festlegen:
 
 @example
 $ guix package -i glibc-locales
 $ export GUIX_LOCPATH=$HOME/.guix-profile/lib/locale
 @end example
 
-Note that the @code{glibc-locales} package contains data for all the
-locales supported by the address@hidden and weighs in at around
address@hidden  Alternatively, the @code{glibc-utf8-locales} is smaller but
-limited to a few UTF-8 locales.
+Beachten Sie, dass das Paket @code{glibc-locales} Daten für alle von
address@hidden unterstützten Locales enthält und deswegen um die address@hidden
+wiegt. Alternativ gibt es auch @code{glibc-utf8-locales}, was kleiner, aber
+auf ein paar UTF-8-Locales beschränkt ist.
 
-The @code{GUIX_LOCPATH} variable plays a role similar to @code{LOCPATH}
-(@pxref{Locale Names, @code{LOCPATH},, libc, The GNU C Library Reference
-Manual}).  There are two important differences though:
+Die Variable @code{GUIX_LOCPATH} spielt eine ähnliche Rolle wie
address@hidden (@pxref{Locale Names, @code{LOCPATH},, libc, The GNU C
+Library Reference Manual}). Es gibt jedoch zwei wichtige Unterschiede:
 
 @enumerate
 @item
address@hidden is honored only by the libc in Guix, and not by the libc
-provided by foreign distros.  Thus, using @code{GUIX_LOCPATH} allows you
-to make sure the programs of the foreign distro will not end up loading
-incompatible locale data.
address@hidden wird nur von der libc in Guix beachtet und nicht der von
+Fremddistributionen bereitgestellten libc. Mit @code{GUIX_LOCPATH} können
+Sie daher sicherstellen, dass die Programme der Fremddistribution keine
+inkompatiblen Locale-Daten von Guix laden.
 
 @item
-libc suffixes each entry of @code{GUIX_LOCPATH} with @code{/X.Y}, where
address@hidden is the libc version---e.g., @code{2.22}.  This means that,
-should your Guix profile contain a mixture of programs linked against
-different libc version, each libc version will only try to load locale
-data in the right format.
+libc hängt an jeden @code{GUIX_LOCPATH}-Eintrag @code{/X.Y} an, wobei
address@hidden die Version von libc ist — z.B. @code{2.22}. Sollte Ihr
+Guix-Profil eine Mischung aus Programmen enthalten, die an verschiedene
+libc-Versionen gebunden sind, wird jede nur die Locale-Daten im richtigen
+Format zu laden versuchen.
 @end enumerate
 
-This is important because the locale data format used by different libc
-versions may be incompatible.
+Das ist wichtig, weil das Locale-Datenformat verschiedener libc-Versionen
+inkompatibel sein könnte.
 
 @subsection Name Service Switch
 
address@hidden name service switch, glibc
address@hidden NSS (name service switch), glibc
address@hidden nscd (name service caching daemon)
address@hidden name service caching daemon (nscd)
-When using Guix on a foreign distro, we @emph{strongly recommend} that
-the system run the GNU C library's @dfn{name service cache daemon},
address@hidden, which should be listening on the
address@hidden/var/run/nscd/socket} socket.  Failing to do that, applications
-installed with Guix may fail to look up host names or user accounts, or
-may even crash.  The next paragraphs explain why.
address@hidden Name Service Switch, glibc
address@hidden NSS (Name Service Switch), glibc
address@hidden nscd (Name Service Caching Daemon)
address@hidden Name Service Caching Daemon (nscd)
+Wenn Sie Guix auf einer Fremddistribution verwenden, @emph{empfehlen wir
+stärkstens}, dass Sie den @dfn{Name Service Cache Daemon} der
+GNU-C-Bibliothek, @command{nscd}, laufen lassen, welcher auf dem Socket
address@hidden/var/run/nscd/socket} lauschen sollte. Wenn Sie das nicht tun, 
könnten
+mit Guix installierte Anwendungen Probleme beim Auflösen von Hostnamen oder
+Benutzerkonten haben, oder sogar abstürzen. Die nächsten Absätze erklären,
+warum.
 
 @cindex @file{nsswitch.conf}
-The GNU C library implements a @dfn{name service switch} (NSS), which is
-an extensible mechanism for ``name lookups'' in general: host name
-resolution, user accounts, and more (@pxref{Name Service Switch,,, libc,
-The GNU C Library Reference Manual}).
-
address@hidden Network information service (NIS)
address@hidden NIS (Network information service)
-Being extensible, the NSS supports @dfn{plugins}, which provide new name
-lookup implementations: for example, the @code{nss-mdns} plugin allow
-resolution of @code{.local} host names, the @code{nis} plugin allows
-user account lookup using the Network information service (NIS), and so
-on.  These extra ``lookup services'' are configured system-wide in
address@hidden/etc/nsswitch.conf}, and all the programs running on the system
-honor those settings (@pxref{NSS Configuration File,,, libc, The GNU C
-Reference Manual}).
-
-When they perform a name lookup---for instance by calling the
address@hidden function in C---applications first try to connect to
-the nscd; on success, nscd performs name lookups on their behalf.  If
-the nscd is not running, then they perform the name lookup by
-themselves, by loading the name lookup services into their own address
-space and running it.  These name lookup services---the
address@hidden files---are @code{dlopen}'d, but they may come from
-the host system's C library, rather than from the C library the
-application is linked against (the C library coming from Guix).
-
-And this is where the problem is: if your application is linked against
-Guix's C library (say, glibc 2.24) and tries to load NSS plugins from
-another C library (say, @code{libnss_mdns.so} for glibc 2.22), it will
-likely crash or have its name lookups fail unexpectedly.
-
-Running @command{nscd} on the system, among other advantages, eliminates
-this binary incompatibility problem because those @code{libnss_*.so}
-files are loaded in the @command{nscd} process, not in applications
-themselves.
-
address@hidden X11 Fonts
-
address@hidden fonts
-The majority of graphical applications use Fontconfig to locate and
-load fonts and perform X11-client-side rendering.  The @code{fontconfig}
-package in Guix looks for fonts in @file{$HOME/.guix-profile}
-by default.  Thus, to allow graphical applications installed with Guix
-to display fonts, you have to install fonts with Guix as well.
-Essential font packages include @code{gs-fonts}, @code{font-dejavu}, and
+Die GNU-C-Bibliothek implementiert einen @dfn{Name Service Switch} (NSS),
+welcher einen erweiterbaren Mechanismus zur allgemeinen »Namensauflösung«
+darstellt: Hostnamensauflösung, Benutzerkonten und weiteres (@pxref{Name 
Service Switch,,, libc, The GNU C Library Reference Manual}).
+
address@hidden Network Information Service (NIS)
address@hidden NIS (Network Information Service)
+Für die Erweiterbarkeit unterstützt der NSS @dfn{Plugins}, welche neue
+Implementierungen zur Namensauflösung bieten: Zum Beispiel ermöglicht das
+Plugin @code{nss-mdns} die Namensauflösung für @code{.local}-Hostnamen, das
+Plugin @code{nis} gestattet die Auflösung von Benutzerkonten über den
+Network Information Service (NIS) und so weiter. Diese zusätzlichen
+»Auflösungsdienste« werden systemweit konfiguriert in
address@hidden/etc/nsswitch.conf} und alle auf dem System laufenden Programme 
halten
+sich an diese Einstellungen (@pxref{NSS Configuration File,,, libc, The GNU
+C Reference Manual}).
+
+Wenn sie eine Namensauflösung durchführen — zum Beispiel, indem sie die
address@hidden in C aufrufen — versuchen die Anwendungen als
+Erstes, sich mit dem nscd zu verbinden; ist dies erfolgreich, führt nscd für
+sie die weiteren Namensauflösungen durch. Falls nscd nicht läuft, führen sie
+selbst die Namensauflösungen durch, indem sie die Namensauflösungsdienste in
+ihren eigenen Adressraum laden und ausführen. Diese Namensauflösungsdienste
+— die @file{libnss_*.so}-Dateien — werden mit @code{dlopen} geladen, aber
+sie kommen von der C-Bibliothek des Wirtssystems und nicht von der
+C-Bibliothek, mit der die Anwendung gebunden wurde (also der C-Bibliothek
+von Guix).
+
+Und hier kommt es zum Problem: Wenn die Anwendung mit der C-Bibliothek von
+Guix (etwa glibc 2.24) gebunden wurde und die NSS-Plugins von einer anderen
+C-Bibliothek (etwa @code{libnss_mdns.so} für glibc 2.22) zu laden versucht,
+wird sie vermutlich abstürzen oder die Namensauflösungen werden unerwartet
+fehlschlagen.
+
+Durch das Ausführen von @command{nscd} auf dem System wird, neben anderen
+Vorteilen, dieses Problem der binären Inkompatibilität vermieden, weil diese
address@hidden vom @command{nscd}-Prozess geladen werden, nicht
+in den Anwendungen selbst.
+
address@hidden X11-Schriftarten
+
address@hidden Schriftarten
+Die Mehrheit der graphischen Anwendungen benutzen Fontconfig zum Finden und
+Laden von Schriftarten und für die Darstellung im X11-Client. Im Paket
address@hidden in Guix werden Schriftarten standardmäßig in
address@hidden/.guix-profile} gesucht. Um es graphischen Anwendungen, die mit
+Guix installiert wurden, zu ermöglichen, Schriftarten anzuzeigen, müssen Sie
+die Schriftarten auch mit Guix installieren. Essenzielle Pakete für
+Schriftarten sind unter Anderem @code{gs-fonts}, @code{font-dejavu} und
 @code{font-gnu-freefont-ttf}.
 
-To display text written in Chinese languages, Japanese, or Korean in
-graphical applications, consider installing
address@hidden or @code{font-wqy-zenhei}.  The former
-has multiple outputs, one per language family (@pxref{Packages with
-Multiple Outputs}).  For instance, the following command installs fonts
-for Chinese languages:
+Um auf Chinesisch, Japanisch oder Koreanisch verfassten Text in graphischen
+Anwendungen anzeigen zu können, möchten Sie vielleicht
address@hidden oder @code{font-wqy-zenhei}
+installieren. Ersteres hat mehrere Ausgaben, für jede Sprachfamilie eine
+(@pxref{Pakete mit mehreren Ausgaben.}). Zum Beispiel installiert folgender
+Befehl Schriftarten für chinesische Sprachen:
 
 @example
 guix package -i font-adobe-source-han-sans:cn
 @end example
 
 @cindex @code{xterm}
-Older programs such as @command{xterm} do not use Fontconfig and instead
-rely on server-side font rendering.  Such programs require to specify a
-full name of a font using XLFD (X Logical Font Description), like this:
+Ältere Programme wie @command{xterm} benutzen kein Fontconfig, sondern
+X-Server-seitige Schriftartendarstellung. Solche Programme setzen voraus,
+dass der volle Name einer Schriftart mit XLFD (X Logical Font Description)
+angegeben wird, z.B. so:
 
 @example
 -*-dejavu sans-medium-r-normal-*-*-100-*-*-*-*-*-1
 @end example
 
-To be able to use such full names for the TrueType fonts installed in
-your Guix profile, you need to extend the font path of the X server:
+Um solche vollen Namen für die in Ihrem Guix-Profil installierten
+TrueType-Schriftarten zu verwenden, müssen Sie den Pfad für Schriftarten
+(Font Path) des X-Servers anpassen:
 
 @c Note: 'xset' does not accept symlinks so the trick below arranges to
 @c get at the real directory.  See <https://bugs.gnu.org/30655>.
@@ -1610,373 +1763,385 @@ xset +fp $(dirname $(readlink -f 
~/.guix-profile/share/fonts/truetype/fonts.dir)
 @end example
 
 @cindex @code{xlsfonts}
-After that, you can run @code{xlsfonts} (from @code{xlsfonts} package)
-to make sure your TrueType fonts are listed there.
+Danach können Sie den Befehl @code{xlsfonts} ausführen (aus dem Paket
address@hidden), um sicherzustellen, dass dort Ihre TrueType-Schriftarten
+aufgeführt sind.
 
 @cindex @code{fc-cache}
address@hidden font cache
-After installing fonts you may have to refresh the font cache to use
-them in applications.  The same applies when applications installed via
-Guix do not seem to find fonts.  To force rebuilding of the font cache
-run @code{fc-cache -f}.  The @code{fc-cache} command is provided by the
address@hidden package.
address@hidden Font-Cache
+Nach der Installation der Schriftarten müssen Sie unter Umständen den
+Schriftarten-Zwischenspeicher (Font-Cache) erneuern, um diese in Anwendungen
+benutzen zu können. Gleiches gilt, wenn mit Guix installierte Anwendungen
+anscheinend keine Schriftarten finden können. Um das Erneuern des
+Font-Caches zu erzwingen, führen Sie @code{fc-cache -f} aus. Der Befehl
address@hidden wird vom Paket @code{fontconfig} angeboten.
 
address@hidden X.509 Certificates
address@hidden X.509-Zertifikate
 
 @cindex @code{nss-certs}
-The @code{nss-certs} package provides X.509 certificates, which allow
-programs to authenticate Web servers accessed over HTTPS.
+Das Paket @code{nss-certs} bietet X.509-Zertifikate, womit Programme die
+Identität von Web-Servern authentifizieren können, auf die über HTTPS
+zugegriffen wird.
 
-When using Guix on a foreign distro, you can install this package and
-define the relevant environment variables so that packages know where to
-look for certificates.  @xref{X.509 Certificates}, for detailed
-information.
+Wenn Sie Guix auf einer Fremddistribution verwenden, können Sie dieses Paket
+installieren und die relevanten Umgebungsvariablen festlegen, damit Pakete
+wissen, wo sie Zertifikate finden. In @xref{X.509-Zertifikate} stehen
+genaue Informationen.
 
address@hidden Emacs Packages
address@hidden Emacs-Pakete
 
 @cindex @code{emacs}
-When you install Emacs packages with Guix, the elisp files may be placed
-either in @file{$HOME/.guix-profile/share/emacs/site-lisp/} or in
-sub-directories of
address@hidden/.guix-profile/share/emacs/site-lisp/guix.d/}.  The latter
-directory exists because potentially there may exist thousands of Emacs
-packages and storing all their files in a single directory may not be
-reliable (because of name conflicts).  So we think using a separate
-directory for each package is a good idea.  It is very similar to how
-the Emacs package system organizes the file structure (@pxref{Package
-Files,,, emacs, The GNU Emacs Manual}).
-
-By default, Emacs (installed with Guix) ``knows'' where these packages
-are placed, so you do not need to perform any configuration.  If, for
-some reason, you want to avoid auto-loading Emacs packages installed
-with Guix, you can do so by running Emacs with @code{--no-site-file}
-option (@pxref{Init File,,, emacs, The GNU Emacs Manual}).
-
address@hidden The GCC toolchain
+Wenn Sie mit Guix Pakete für Emacs installieren, werden deren elisp-Dateien
+entweder in @file{$HOME/.guix-profile/share/emacs/site-lisp/} oder in
+Unterverzeichnissen von
address@hidden/.guix-profile/share/emacs/site-lisp/guix.d/}
+gespeichert. Letzteres Verzeichnis gibt es, weil es Tausende von
+Emacs-Paketen gibt und sie alle im selben Verzeichnis zu speichern
+vielleicht nicht verlässlich funktioniert (wegen Namenskonflikten). Daher
+halten wir es für richtig, für jedes Paket ein anderes Verzeichnis zu
+benutzen. Das Emacs-Paketsystem organisiert die Dateistruktur ähnlich
+(@pxref{Package Files,,, emacs, The GNU Emacs Manual}).
+
+Standardmäßig »weiß« Emacs (wenn er mit Guix installiert wurde), wo diese
+Pakete liegen, sie müssen also nichts selbst konfigurieren. Wenn Sie aber
+aus irgendeinem Grund mit Guix installierte Pakete nicht automatisch laden
+lassen möchten, können Sie Emacs mit der Befehlszeilenoption
address@hidden starten (@pxref{Init File,,, emacs, The GNU Emacs
+Manual}).
+
address@hidden GCC-Toolchain
 
 @cindex GCC
 @cindex ld-wrapper
 
-Guix offers individual compiler packages such as @code{gcc} but if you
-are in need of a complete toolchain for compiling and linking source
-code what you really want is the @code{gcc-toolchain} package.  This
-package provides a complete GCC toolchain for C/C++ development,
-including GCC itself, the GNU C Library (headers and binaries, plus
-debugging symbols in the @code{debug} output), Binutils, and a linker
-wrapper.
-
address@hidden attempt to use impure library, error message
-
-The wrapper's purpose is to inspect the @code{-L} and @code{-l} switches
-passed to the linker, add corresponding @code{-rpath} arguments, and
-invoke the actual linker with this new set of arguments.  By default,
-the linker wrapper refuses to link to libraries outside the store to
-ensure ``purity''.  This can be annoying when using the toolchain to
-link with local libraries.  To allow references to libraries outside the
-store you need to define the environment variable
address@hidden
+Guix bietet individuelle Compiler-Pakete wie etwa @code{gcc}, aber wenn Sie
+einen vollständigen Satz an Werkzeugen zum Kompilieren und Binden von
+Quellcode brauchen, werden Sie eigentlich das Paket @code{gcc-toolchain}
+haben wollen. Das Paket bietet eine vollständige GCC-Toolchain für die
+Entwicklung mit C/C++, einschließlich GCC selbst, der GNU-C-Bibliothek
+(Header-Dateien und Binärdateien samt Symbolen zur Fehlersuche/Debugging in
+der @code{debug}-Ausgabe), Binutils und einen Wrapper für den Binder/Linker.
+
address@hidden Versuch, unreine Bibliothek zu benutzen, Fehlermeldung
+
+Der Zweck des Wrappers ist, die an den Binder übergebenen
+Befehlszeilenoptionen mit @code{-L} und @code{-l} zu überprüfen und jeweils
+passende Argumente mit @code{-rpath} anzufügen, womit dann der echte Binder
+aufgerufen wird. Standardmäßig weigert sich der Binder-Wrapper, mit
+Bibliotheken außerhalb des Stores zu binden, um »Reinheit« zu
+gewährleisten. Das kann aber stören, wenn man die Toolchain benutzt, um mit
+lokalen Bibliotheken zu binden. Um Referenzen auf Bibliotheken außerhalb des
+Stores zu erlauben, müssen Sie die Umgebungsvariable
address@hidden setzen.
 
 @c TODO What else?
 
 @c *********************************************************************
address@hidden Package Management
address@hidden Package Management
address@hidden Paketverwaltung
address@hidden Paketverwaltung
 
address@hidden packages
-The purpose of GNU Guix is to allow users to easily install, upgrade, and
-remove software packages, without having to know about their build
-procedures or dependencies.  Guix also goes beyond this obvious set of
-features.
address@hidden Pakete
+Der Zweck von GNU Guix ist, Benutzern die leichte Installation,
+Aktualisierung und Entfernung von Software-Paketen zu ermöglichen, ohne dass
+sie ihre Erstellungsprozeduren oder Abhängigkeiten kennen müssen. Guix kann
+natürlich noch mehr als diese offensichtlichen Funktionalitäten.
 
-This chapter describes the main features of Guix, as well as the
-package management tools it provides.  Along with the command-line
-interface described below (@pxref{Invoking guix package, @code{guix
-package}}), you may also use the Emacs-Guix interface (@pxref{Top,,,
-emacs-guix, The Emacs-Guix Reference Manual}), after installing
address@hidden package (run @kbd{M-x guix-help} command to start
-with it):
+Dieses Kapitel beschreibt die Hauptfunktionalitäten von Guix, sowie die von
+Guix angebotenen Paketverwaltungswerkzeuge. Zusätzlich von den im Folgenden
+beschriebenen Befehlszeilen-Benutzerschnittstellen (@pxref{Aufruf von guix 
package, @code{guix package}}) können Sie auch mit der
+Emacs-Guix-Schnittstelle (@pxref{Top,,, emacs-guix, The Emacs-Guix Reference
+Manual}) arbeiten, nachdem Sie das Paket @code{emacs-guix} installiert haben
+(führen Sie zum Einstieg in Emacs-Guix den Emacs-Befehl @kbd{M-x guix-help}
+aus):
 
 @example
 guix package -i emacs-guix
 @end example
 
 @menu
-* Features::                    How Guix will make your life brighter.
-* Invoking guix package::       Package installation, removal, etc.
-* Substitutes::                 Downloading pre-built binaries.
-* Packages with Multiple Outputs::  Single source package, multiple outputs.
-* Invoking guix gc::            Running the garbage collector.
-* Invoking guix pull::          Fetching the latest Guix and distribution.
-* Channels::                    Customizing the package collection.
-* Inferiors::                   Interacting with another revision of Guix.
-* Invoking guix describe::      Display information about your Guix revision.
-* Invoking guix pack::          Creating software bundles.
-* Invoking guix archive::       Exporting and importing store files.
+* Funktionalitäten::        Wie Guix Ihr Leben schöner machen wird.
+* Aufruf von guix package::  Pakete installieren, entfernen usw.
+* Substitute::               Vorerstelle Binärdateien herunterladen.
+* Pakete mit mehreren Ausgaben.::  Ein Quellpaket, mehrere Ausgaben.
+* Aufruf von guix gc::       Den Müllsammler laufen lassen.
+* Aufruf von guix pull::     Das neueste Guix samt Distribution laden.
+* Channels::                 Customizing the package collection.
+* Inferiors::                Interacting with another revision of Guix.
+* Invoking guix describe::   Display information about your Guix revision.
+* Aufruf von guix pack::     Software-Bündel erstellen.
+* Aufruf von guix archive::  Import und Export von Store-Dateien.
 @end menu
 
address@hidden Features
address@hidden Features
-
-When using Guix, each package ends up in the @dfn{package store}, in its
-own directory---something that resembles
address@hidden/gnu/store/xxx-package-1.2}, where @code{xxx} is a base32 string.
-
-Instead of referring to these directories, users have their own
address@hidden, which points to the packages that they actually want to
-use.  These profiles are stored within each user's home directory, at
address@hidden/.guix-profile}.
-
-For example, @code{alice} installs GCC 4.7.2.  As a result,
address@hidden/home/alice/.guix-profile/bin/gcc} points to
address@hidden/gnu/store/@dots{}-gcc-4.7.2/bin/gcc}.  Now, on the same machine,
address@hidden had already installed GCC 4.8.0.  The profile of @code{bob}
-simply continues to point to
address@hidden/gnu/store/@dots{}-gcc-4.8.0/bin/gcc}---i.e., both versions of GCC
-coexist on the same system without any interference.
-
-The @command{guix package} command is the central tool to manage
-packages (@pxref{Invoking guix package}).  It operates on the per-user
-profiles, and can be used @emph{with normal user privileges}.
-
address@hidden transactions
-The command provides the obvious install, remove, and upgrade
-operations.  Each invocation is actually a @emph{transaction}: either
-the specified operation succeeds, or nothing happens.  Thus, if the
address@hidden package} process is terminated during the transaction,
-or if a power outage occurs during the transaction, then the user's
-profile remains in its previous state, and remains usable.
-
-In addition, any package transaction may be @emph{rolled back}.  So, if,
-for example, an upgrade installs a new version of a package that turns
-out to have a serious bug, users may roll back to the previous instance
-of their profile, which was known to work well.  Similarly, the global
-system configuration on GuixSD is subject to
-transactional upgrades and roll-back
-(@pxref{Using the Configuration System}).
-
-All packages in the package store may be @emph{garbage-collected}.
-Guix can determine which packages are still referenced by user
-profiles, and remove those that are provably no longer referenced
-(@pxref{Invoking guix gc}).  Users may also explicitly remove old
-generations of their profile so that the packages they refer to can be
-collected.
-
address@hidden reproducibility
address@hidden reproducible builds
-Guix takes a @dfn{purely functional} approach to package
-management, as described in the introduction (@pxref{Introduction}).
-Each @file{/gnu/store} package directory name contains a hash of all the
-inputs that were used to build that package---compiler, libraries, build
-scripts, etc.  This direct correspondence allows users to make sure a
-given package installation matches the current state of their
-distribution.  It also helps maximize @dfn{build reproducibility}:
-thanks to the isolated build environments that are used, a given build
-is likely to yield bit-identical files when performed on different
-machines (@pxref{Invoking guix-daemon, container}).
-
address@hidden substitutes
-This foundation allows Guix to support @dfn{transparent binary/source
-deployment}.  When a pre-built binary for a @file{/gnu/store} item is
-available from an external source---a @dfn{substitute}, Guix just
-downloads it and unpacks it;
-otherwise, it builds the package from source, locally
-(@pxref{Substitutes}).  Because build results are usually bit-for-bit
-reproducible, users do not have to trust servers that provide
-substitutes: they can force a local build and @emph{challenge} providers
-(@pxref{Invoking guix challenge}).
-
-Control over the build environment is a feature that is also useful for
-developers.  The @command{guix environment} command allows developers of
-a package to quickly set up the right development environment for their
-package, without having to manually install the dependencies of the
-package into their profile (@pxref{Invoking guix environment}).
address@hidden Funktionalitäten
address@hidden Funktionalitäten
+
+Wenn Sie Guix benutzen, landet jedes Paket schließlich im @dfn{Paket-Store}
+in seinem eigenen Verzeichnis — der Name ist ähnlich wie
address@hidden/gnu/store/xxx-package-1.2}, wobei @code{xxx} eine Zeichenkette in
+Base32-Darstellung ist.
+
+Statt diese Verzeichnisse direkt anzugeben, haben Nutzer ihr eigenes
address@hidden, welches auf diejenigen Pakete zeigt, die sie tatsächlich
+benutzen wollen. Diese Profile sind im Persönlichen Ordner des jeweiligen
+Nutzers gespeichert als @code{$HOME/.guix-profile}.
+
+Zum Beispiel installiert @code{alice} GCC 4.7.2. Dadurch zeigt dann
address@hidden/home/alice/.guix-profile/bin/gcc} auf
address@hidden/gnu/store/@dots{}-gcc-4.7.2/bin/gcc}. Auf demselben Rechner hat
address@hidden bbereits GCC 4.8.0 installiert. Das Profil von @code{bob} zeigt
+dann einfach weiterhin auf @file{/gnu/store/@dots{}-gcc-4.8.0/bin/gcc} —
+d.h. beide Versionen von GCC koexistieren auf demselben System, ohne sich zu
+stören.
+
+Der Befehl @command{guix package} ist das zentrale Werkzeug, um Pakete zu
+verwalten (@pxref{Aufruf von guix package}). Es arbeitet auf dem eigenen
+Profil jedes Nutzers und kann @emph{mit normalen Benutzerrechten} ausgeführt
+werden.
+
address@hidden Transaktionen
+Der Befehl stellt die offensichtlichen Installations-, Entfernungs- und
+Aktualisierungsoperationen zur Verfügung. Jeder Aufruf ist tatsächlich eine
+eigene @emph{Transaktion}: Entweder die angegebene Operation wird
+erfolgreich durchgeführt, oder gar nichts passiert. Wenn also der Prozess
+von @command{guix package} während der Transaktion beendet wird, oder es zum
+Stromausfall während der Transaktion kommt, dann bleibt der alte, nutzbare
+Zustands des Nutzerprofils erhalten.
+
+Zudem kann jede Pakettransaktion @emph{zurückgesetzt} werden
+(Rollback). Wenn also zum Beispiel durch eine Aktualisierung eine neue
+Version eines Pakets installiert, die einen schwerwiegenden Fehler zur Folge
+hat, können Nutzer ihr Profil einfach auf die vorherige Profilinstanz
+zurücksetzen, von der sie wissen, dass sie gut lief. Ebenso unterliegt auf
+GuixSD auch die globale Systemkonfiguration transaktionellen
+Aktualisierungen und Rücksetzungen (@pxref{Das Konfigurationssystems nutzen}).
+
+Alle Pakete im Paket-Store können vom @emph{Müllsammler} (Garbage Collector)
+gelöscht werden. Guix ist in der Lage, festzustellen, welche Pakete noch
+durch Benutzerprofile referenziert werden, und entfernt nur diese, die
+nachweislich nicht mehr referenziert werden (@pxref{Aufruf von guix gc}). 
Benutzer können auch ausdrücklich alte Generationen ihres Profils
+löschen, damit die zugehörigen Pakete vom Müllsammler gelöscht werden
+können.
+
address@hidden Reproduzierbarkeit
address@hidden Reproduzierbare Erstellungen
+Guix takes a @dfn{purely functional} approach to package management, as
+described in the introduction (@pxref{Einführung}).  Each
address@hidden/gnu/store} package directory name contains a hash of all the 
inputs
+that were used to build that package---compiler, libraries, build scripts,
+etc.  This direct correspondence allows users to make sure a given package
+installation matches the current state of their distribution.  It also helps
+maximize @dfn{build reproducibility}: thanks to the isolated build
+environments that are used, a given build is likely to yield bit-identical
+files when performed on different machines (@pxref{Aufruf des guix-daemon,
+container}).
+
address@hidden Substitute
+Auf dieser Grundlage kann Guix @dfn{transparent Binär- oder Quelldateien
+ausliefern}. Wenn eine vorerstellte Binärdatei für ein
address@hidden/gnu/store}-Objekt von einer externen Quelle verfügbar ist — ein
address@hidden —, lädt Guix sie einfach herunter und entpackt sie,
+andernfalls erstellt Guix das Paket lokal aus seinem Quellcode
+(@pxref{Substitute}). Weil Erstellungsergebnisse normalerweise Bit für Bit
+reproduzierbar sind, müssen die Nutzer den Servern, die Substitute anbieten,
+nicht blind vertrauen; sie können eine lokale Erstellung erzwingen und
+Substitute @emph{anfechten} (@pxref{Aufruf von guix challenge}).
+
+Kontrolle über die Erstellungsumgebung ist eine auch für Entwickler
+nützliche Funktionalität. Der Befehl @command{guix environment} ermöglicht
+es Entwicklern eines Pakets, schnell die richtige Entwicklungsumgebung für
+ihr Paket einzurichten, ohne manuell die Abhängigkeiten des Pakets in ihr
+Profil installieren zu müssen (@pxref{Aufruf von guix environment}).
 
 @cindex replication, of software environments
 @cindex provenance tracking, of software artifacts
 All of Guix and its package definitions is version-controlled, and
 @command{guix pull} allows you to ``travel in time'' on the history of Guix
-itself (@pxref{Invoking guix pull}).  This makes it possible to replicate a
+itself (@pxref{Aufruf von guix pull}).  This makes it possible to replicate a
 Guix instance on a different machine or at a later point in time, which in
 turn allows you to @emph{replicate complete software environments}, while
 retaining precise @dfn{provenance tracking} of the software.
 
address@hidden Invoking guix package
address@hidden Aufruf von guix package
 @section Invoking @command{guix package}
 
address@hidden installing packages
address@hidden removing packages
address@hidden package installation
address@hidden package removal
-The @command{guix package} command is the tool that allows users to
-install, upgrade, and remove packages, as well as rolling back to
-previous configurations.  It operates only on the user's own profile,
-and works with normal user privileges (@pxref{Features}).  Its syntax
-is:
address@hidden Installieren von Paketen
address@hidden Entfernen von Paketen
address@hidden Paketinstallation
address@hidden Paketentfernung
+Der Befehl @command{guix package} ist ein Werkzeug, womit Nutzer Pakete
+installieren, aktualisieren, entfernen und auf vorherige Konfigurationen
+zurücksetzen können. Dabei wird nur das eigene Profil des Nutzers verwendet,
+und es funktioniert mit normalen Benutzerrechten, ohne Administratorrechte
+(@pxref{Funktionalitäten}). Die Syntax ist:
 
 @example
-guix package @var{options}
+guix package @var{Optionen}
 @end example
address@hidden transactions
-Primarily, @var{options} specifies the operations to be performed during
-the transaction.  Upon completion, a new profile is created, but
-previous @dfn{generations} of the profile remain available, should the user
-want to roll back.
address@hidden Transaktionen
+In erster Linie geben die @var{Optionen} an, welche Operationen in der
+Transaktion durchgeführt werden sollen. Nach Abschluss wird ein neues Profil
+erzeugt, aber vorherige @dfn{Generationen} des Profils bleiben verfügbar,
+falls der Benutzer auf sie zurückwechseln will.
 
-For example, to remove @code{lua} and install @code{guile} and
address@hidden in a single transaction:
+Um zum Beispiel @code{lua} zu entfernen und @code{guile} und
address@hidden in einer einzigen Transaktion zu installieren:
 
 @example
 guix package -r lua -i guile guile-cairo
 @end example
 
address@hidden package} also supports a @dfn{declarative approach}
-whereby the user specifies the exact set of packages to be available and
-passes it @i{via} the @option{--manifest} option
address@hidden package} unterstützt auch ein @dfn{deklaratives Vorgehen},
+wobei der Nutzer die genaue Menge an Paketen, die verfügbar sein sollen,
+festlegt und über die Befehlszeilenoption @option{--manifest} übergibt
 (@pxref{profile-manifest, @option{--manifest}}).
 
address@hidden profile
-For each user, a symlink to the user's default profile is automatically
-created in @file{$HOME/.guix-profile}.  This symlink always points to the
-current generation of the user's default profile.  Thus, users can add
address@hidden/.guix-profile/bin} to their @code{PATH} environment
-variable, and so on.
address@hidden search paths
-If you are not using the Guix System Distribution, consider adding the
-following lines to your @file{~/.bash_profile} (@pxref{Bash Startup
-Files,,, bash, The GNU Bash Reference Manual}) so that newly-spawned
-shells get all the right environment variable definitions:
address@hidden Profil
+Für jeden Benutzer wird automatisch eine symbolische Verknüpfung zu seinem
+Standardprofil angelegt als @file{$HOME/.guix-profile}. Diese symbolische
+Verknüpfung zeigt immer auf die aktuelle Generation des Standardprofils des
+Benutzers. Somit können Nutzer @file{$HOME/.guix-profile/bin} z.B. zu ihrer
+Umgebungsvariablen @code{PATH} hinzufügen.
address@hidden Suchpfade
+Wenn Sie nicht die Guix System Distribution benutzen, sollten Sie in
+Betracht ziehen, folgende Zeilen zu Ihrem @file{~/.bash_profile}
+hinzuzufügen (@pxref{Bash Startup Files,,, bash, The GNU Bash Reference
+Manual}), damit in neu erzeugten Shells alle Umgebungsvariablen richtig
+definiert werden:
 
 @example
 GUIX_PROFILE="$HOME/.guix-profile" ; \
 source "$HOME/.guix-profile/etc/profile"
 @end example
 
-In a multi-user setup, user profiles are stored in a place registered as
-a @dfn{garbage-collector root}, which @file{$HOME/.guix-profile} points
-to (@pxref{Invoking guix gc}).  That directory is normally
address@hidden@var{localstatedir}/guix/profiles/per-user/@var{user}}, where
address@hidden is the value passed to @code{configure} as
address@hidden, and @var{user} is the user name.  The
address@hidden directory is created when @command{guix-daemon} is
-started, and the @var{user} sub-directory is created by @command{guix
-package}.
+Ist Ihr System für mehrere Nutzer eingerichtet, werden Nutzerprofile an
+einem Ort gespeichert, der als @dfn{Müllsammlerwurzel} registriert ist, auf
+die @file{$HOME/.guix-profile} zeigt (@pxref{Aufruf von guix gc}). Dieses
+Verzeichnis ist normalerweise
address@hidden@var{localstatedir}/guix/profiles/per-user/@var{Benutzer}}, wobei
address@hidden der an @code{configure} als @code{--localstatedir}
+übergebene Wert ist und @var{Benutzer} für den jeweiligen Benutzernamen
+steht. Das @file{per-user}-Verzeichnis wird erstellt, wenn
address@hidden gestartet wird, und das Unterverzeichnis
address@hidden wird durch @command{guix package} erstellt.
 
-The @var{options} can be among the following:
+Als @var{Optionen} kann vorkommen:
 
 @table @code
 
address@hidden address@hidden @dots{}
address@hidden -i @var{package} @dots{}
-Install the specified @var{package}s.
-
-Each @var{package} may specify either a simple package name, such as
address@hidden, or a package name followed by an at-sign and version number,
-such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
-case, the newest version prefixed by @code{1.8} is selected.)
-
-If no version number is specified, the
-newest available version will be selected.  In addition, @var{package}
-may contain a colon, followed by the name of one of the outputs of the
-package, as in @code{gcc:doc} or @code{binutils@@2.22:lib}
-(@pxref{Packages with Multiple Outputs}).  Packages with a corresponding
-name (and optionally version) are searched for among the GNU
-distribution modules (@pxref{Package Modules}).
-
address@hidden propagated inputs
-Sometimes packages have @dfn{propagated inputs}: these are dependencies
-that automatically get installed along with the required package
-(@pxref{package-propagated-inputs, @code{propagated-inputs} in
address@hidden objects}, for information about propagated inputs in
-package definitions).
address@hidden address@hidden @dots{}
address@hidden -i @var{Paket} @dots{}
+Die angegebenen @var{Paket}e installieren.
+
+Jedes @var{Paket} kann entweder einfach durch seinen Paketnamen aufgeführt
+werden, wie @code{guile}, oder als Paketname gefolgt von einem At-Zeichen @@
+und einer Versionsnummer, wie @code{guile@@1.8.8} oder auch nur
address@hidden@@1.8} (in letzterem Fall wird die neueste Version mit Präfix
address@hidden ausgewählt.)
+
+Wird keine Versionsnummer angegeben, wird die neueste verfügbare Version
+ausgewählt. Zudem kann im @var{Paket} ein Doppelpunkt auftauchen, gefolgt
+vom Namen einer der Ausgaben des Pakets, wie @code{gcc:doc} oder
address@hidden@@2.22:lib} (@pxref{Pakete mit mehreren Ausgaben.}). Pakete
+mit zugehörigem Namen (und optional der Version) werden unter den Modulen
+der GNU-Distribution gesucht (@pxref{Paketmodule}).
+
address@hidden propagierte Eingaben
+Manchmal haben Pakete @dfn{propagierte Eingaben}: Als solche werden
+Abhängigkeiten bezeichnet, die automatisch zusammen mit dem angeforderten
+Paket installiert werden (im Abschnitt @pxref{package-propagated-inputs,
address@hidden in @code{package} objects} sind weitere
+Informationen über propagierte Eingaben in Paketdefinitionen zu finden).
 
 @anchor{package-cmd-propagated-inputs}
-An example is the GNU MPC library: its C header files refer to those of
-the GNU MPFR library, which in turn refer to those of the GMP library.
-Thus, when installing MPC, the MPFR and GMP libraries also get installed
-in the profile; removing MPC also removes MPFR and GMP---unless they had
-also been explicitly installed by the user.
+Ein Beispiel ist die GNU-MPC-Bibliothek: Ihre C-Headerdateien verweisen auf
+die der GNU-MPFR-Bibliothek, welche wiederum auf die der GMP-Bibliothek
+verweisen. Wenn also MPC installiert wird, werden auch die MPFR- und
+GMP-Bibliotheken in das Profil installiert; entfernt man MPC, werden auch
+MPFR und GMP entfernt — außer sie wurden noch auf andere Art ausdrücklich
+vom Nutzer installiert.
 
-Besides, packages sometimes rely on the definition of environment
-variables for their search paths (see explanation of
address@hidden below).  Any missing or possibly incorrect
-environment variable definitions are reported here.
+Abgesehen davon setzen Pakete manchmal die Definition von Umgebungsvariablen
+für ihre Suchpfade voraus (siehe die Erklärung von @code{--search-paths}
+weiter unten). Alle fehlenden oder womöglich falschen Definitionen von
+Umgebungsvariablen werden hierbei gemeldet.
 
address@hidden address@hidden
address@hidden -e @var{exp}
-Install the package @var{exp} evaluates to.
address@hidden address@hidden
address@hidden -e @var{Ausdruck}
+Das Paket installieren, zu dem der @var{Ausdruck} ausgewertet wird.
 
address@hidden must be a Scheme expression that evaluates to a
address@hidden<package>} object.  This option is notably useful to disambiguate
-between same-named variants of a package, with expressions such as
address@hidden(@@ (gnu packages base) guile-final)}.
+Beim @var{Ausdruck} muss es sich um einen Scheme-Ausdruck handeln, der zu
+einem @code{<package>}-Objekt ausgewertet wird. Diese Option ist besonders
+nützlich, um zwischen gleichnamigen Varianten eines Pakets zu unterscheiden,
+durch Ausdrücke wie @code{(@@ (gnu packages base) guile-final)}.
 
-Note that this option installs the first output of the specified
-package, which may be insufficient when needing a specific output of a
-multiple-output package.
+Beachten Sie, dass mit dieser Option die erste Ausgabe des angegebenen
+Pakets installiert wird, was unzureichend sein kann, wenn eine bestimmte
+Ausgabe eines Pakets mit mehreren Ausgaben gewünscht ist.
 
address@hidden address@hidden
address@hidden -f @var{file}
-Install the package that the code within @var{file} evaluates to.
address@hidden address@hidden
address@hidden -f @var{Datei}
+Das Paket installieren, zu dem der Code in der @var{Datei} ausgewertet wird.
 
-As an example, @var{file} might contain a definition like this
-(@pxref{Defining Packages}):
+Zum Beispiel könnte die @var{Datei} eine Definition wie diese enthalten
+(@pxref{Pakete definieren}):
 
 @example
 @verbatiminclude package-hello.scm
 @end example
 
-Developers may find it useful to include such a @file{guix.scm} file
-in the root of their project source tree that can be used to test
-development snapshots and create reproducible development environments
-(@pxref{Invoking guix environment}).
+Entwickler könnten es für nützlich erachten, eine solche
address@hidden im Quellbaum ihres Projekts abzulegen, mit der
+Zwischenstände der Entwicklung getestet und reproduzierbare
+Erstellungsumgebungen aufgebaut werden können (@pxref{Aufruf von guix 
environment}).
 
address@hidden address@hidden @dots{}
address@hidden -r @var{package} @dots{}
-Remove the specified @var{package}s.
address@hidden address@hidden @dots{}
address@hidden -r @var{Paket} @dots{}
+Die angegebenen @var{Paket}e entfernen.
 
-As for @code{--install}, each @var{package} may specify a version number
-and/or output name in addition to the package name.  For instance,
address@hidden glibc:debug} would remove the @code{debug} output of
address@hidden
+Wie auch bei @code{--install} kann jedes @var{Paket} neben dem Paketnamen
+auch eine Versionsnummer und/oder eine Ausgabe benennen. Zum Beispiel würde
address@hidden glibc:debug} die @code{debug}-Ausgabe von @code{glibc} aus dem
+Profil entfernen.
 
address@hidden address@hidden @dots{}]
address@hidden -u address@hidden @dots{}]
address@hidden upgrading packages
-Upgrade all the installed packages.  If one or more @var{regexp}s are
-specified, upgrade only installed packages whose name matches a
address@hidden  Also see the @code{--do-not-upgrade} option below.
address@hidden address@hidden @dots{}]
address@hidden -u address@hidden @dots{}]
address@hidden Pakete aktualisieren
+Alle installierten Pakete aktualisieren. Wenn einer oder mehr reguläre
+Ausdrücke (Regexps) angegeben wurden, werden nur diejenigen installierten
+Pakete aktualisiert, deren Name zu einer der @var{Regexp}s passt. Siehe auch
+weiter unten die Befehlszeilenoption @code{--do-not-upgrade}.
 
-Note that this upgrades package to the latest version of packages found
-in the distribution currently installed.  To update your distribution,
-you should regularly run @command{guix pull} (@pxref{Invoking guix
-pull}).
+Beachten Sie, dass das Paket so auf die neueste Version unter den Paketen
+gebracht wird, die in der aktuell installierten Distribution vorliegen. Um
+jedoch Ihre Distribution zu aktualisieren, sollten Sie regelmäßig
address@hidden pull} ausführen (@pxref{Aufruf von guix pull}).
 
address@hidden address@hidden @dots{}]
-When used together with the @code{--upgrade} option, do @emph{not}
-upgrade any packages whose name matches a @var{regexp}.  For example, to
-upgrade all packages in the current profile except those containing the
-substring ``emacs'':
address@hidden address@hidden @dots{}]
+In Verbindung mit der Befehlszeilenoption @code{--upgrade}, führe
address@hidden Aktualisierung von Paketen durch, deren Name zum regulären
+Ausdruck @var{Regexp} passt. Um zum Beispiel alle Pakete im aktuellen Profil
+zu aktualisieren mit Ausnahme derer, die »emacs« im Namen haben:
 
 @example
 $ guix package --upgrade . --do-not-upgrade emacs
 @end example
 
address@hidden @address@hidden
address@hidden -m @var{file}
address@hidden profile declaration
address@hidden profile manifest
-Create a new generation of the profile from the manifest object
-returned by the Scheme code in @var{file}.
address@hidden @address@hidden
address@hidden -m @var{Datei}
address@hidden Profildeklaration
address@hidden Profilmanifest
+Erstellt eine neue Generation des Profils aus dem vom Scheme-Code in
address@hidden gelieferten Manifest-Objekt.
 
-This allows you to @emph{declare} the profile's contents rather than
-constructing it through a sequence of @code{--install} and similar
-commands.  The advantage is that @var{file} can be put under version
-control, copied to different machines to reproduce the same profile, and
-so on.
+Dadurch könnrn Sie den Inhalt des Profils @emph{deklarieren}, statt ihn
+durch eine Folge von Befehlen wie @code{--install} u.Ä. zu generieren. Der
+Vorteil ist, dass die @var{Datei} unter Versionskontrolle gestellt werden
+kann, auf andere Maschinen zum Reproduzieren desselben Profils kopiert
+werden kann und Ähnliches.
 
 @c FIXME: Add reference to (guix profile) documentation when available.
address@hidden must return a @dfn{manifest} object, which is roughly a list
-of packages:
+Der Code in der @var{Datei} muss ein @dfn{Manifest}-Objekt liefern, was
+ungefähr einer Liste von Paketen entspricht:
 
 @findex packages->manifest
 @example
@@ -1985,17 +2150,17 @@ of packages:
 (packages->manifest
  (list emacs
        guile-2.0
-       ;; Use a specific package output.
+       ;; Eine bestimmte Paketausgabe nutzen.
        (list guile-2.0 "debug")))
 @end example
 
 @findex specifications->manifest
-In this example we have to know which modules define the @code{emacs}
-and @code{guile-2.0} variables to provide the right
address@hidden line, which can be cumbersome.  We can
-instead provide regular package specifications and let
address@hidden>manifest} look up the corresponding package
-objects, like this:
+In diesem Beispiel müssen wir wissen, welche Module die Variablen
address@hidden und @code{guile-2.0} definieren, um die richtige Angabe mit
address@hidden machen zu können, was umständlich sein kann. Wir
+können auch normale Paketnamen angeben und sie durch
address@hidden>manifest} zu den entsprechenden Paketobjekten
+auflösen, zum Beispiel so:
 
 @example
 (specifications->manifest
@@ -2003,68 +2168,70 @@ objects, like this:
 @end example
 
 @item --roll-back
address@hidden rolling back
address@hidden undoing transactions
address@hidden transactions, undoing
-Roll back to the previous @dfn{generation} of the profile---i.e., undo
-the last transaction.
-
-When combined with options such as @code{--install}, roll back occurs
-before any other actions.
-
-When rolling back from the first generation that actually contains
-installed packages, the profile is made to point to the @dfn{zeroth
-generation}, which contains no files apart from its own metadata.
-
-After having rolled back, installing, removing, or upgrading packages
-overwrites previous future generations.  Thus, the history of the
-generations in a profile is always linear.
-
address@hidden address@hidden
address@hidden -S @var{pattern}
address@hidden generations
-Switch to a particular generation defined by @var{pattern}.
-
address@hidden may be either a generation number or a number prefixed
-with ``+'' or ``-''.  The latter means: move forward/backward by a
-specified number of generations.  For example, if you want to return to
-the latest generation after @code{--roll-back}, use
address@hidden
-
-The difference between @code{--roll-back} and
address@hidden is that @code{--switch-generation} will
-not make a zeroth generation, so if a specified generation does not
-exist, the current generation will not be changed.
-
address@hidden address@hidden
address@hidden search paths
-Report environment variable definitions, in Bash syntax, that may be
-needed in order to use the set of installed packages.  These environment
-variables are used to specify @dfn{search paths} for files used by some
-of the installed packages.
-
-For example, GCC needs the @code{CPATH} and @code{LIBRARY_PATH}
-environment variables to be defined so it can look for headers and
-libraries in the user's profile (@pxref{Environment Variables,,, gcc,
-Using the GNU Compiler Collection (GCC)}).  If GCC and, say, the C
-library are installed in the profile, then @code{--search-paths} will
-suggest setting these variables to @address@hidden/include} and
address@hidden@var{profile}/lib}, respectively.
-
-The typical use case is to define these environment variables in the
-shell:
address@hidden rücksetzen
address@hidden Zurücksetzen von Transaktionen
address@hidden Transaktionen, zurücksetzen
+Wechselt zur vorherigen @dfn{Generation} des Profils zurück — d.h. mache die
+letzte Transaktion rückgängig.
+
+In Verbindung mit Befehlszeilenoptionen wie @code{--install} wird zuerst
+zurückgesetzt, bevor andere Aktionen durchgeführt werden.
+
+Ein Rücksetzen der ersten Generation, die installierte Pakete enthält,
+wechselt das Profil zur @dfn{nullten Generation}, die keinerlei Dateien
+enthält, abgesehen von Metadaten über sich selbst.
+
+Nach dem Zurücksetzen überschreibt das Installieren, Entfernen oder
+Aktualisieren von Paketen vormals zukünftige Generationen, d.h. der Verlauf
+der Generationen eines Profils ist immer linear.
+
address@hidden address@hidden
address@hidden -S @var{Muster}
address@hidden Generationen
+Wechselt zu der bestimmten Generation, die durch das @var{Muster} bezeichnet
+wird.
+
+Als @var{Muster} kann entweder die Nummer einer Generation oder eine Nummer
+mit vorangestelltem »+« oder »-« dienen. Letzteres springt die angegebene
+Anzahl an Generationen vor oder zurück. Zum Beispiel kehrt
address@hidden nach einem Zurücksetzen wieder zur neueren
+Generation zurück.
+
+Der Unterschied zwischen @code{--roll-back} und
address@hidden ist, dass @code{--switch-generation} keine
+nullte Generation erzeugen wird; existiert die angegebene Generation nicht,
+bleibt schlicht die aktuelle Generation erhalten.
+
address@hidden address@hidden
address@hidden Suchpfade
+Führe die Definitionen von Umgebungsvariablen auf, in Bash-Syntax, die nötig
+sein könnten, um alle installierten Pakete nutzen zu können. Diese
+Umgebungsvariablen werden benutzt, um die @dfn{Suchpfade} für Dateien
+festzulegen, die von einigen installierten Paketen benutzt werden.
+
+Zum Beispiel braucht GCC die Umgebungsvariablen @code{CPATH} und
address@hidden, um zu wissen, wo sich im Benutzerprofil Header und
+Bibliotheken befinden (@pxref{Environment Variables,,, gcc, Using the GNU
+Compiler Collection (GCC)}). Wenn GCC und, sagen wir, die C-Bibliothek im
+Profil installiert sind, schlägt @code{--search-paths} also vor, diese
+Variablen jeweils auf @address@hidden/include} und
address@hidden@var{profile}/lib} verweisen zu lassen.
+
+Die typische Nutzung ist, in der Shell diese Variablen zu definieren:
 
 @example
 $ eval `guix package --search-paths`
 @end example
 
address@hidden may be one of @code{exact}, @code{prefix}, or @code{suffix},
-meaning that the returned environment variable definitions will either
-be exact settings, or prefixes or suffixes of the current value of these
-variables.  When omitted, @var{kind} defaults to @code{exact}.
+Als @var{Art} kann entweder @code{exact}, @code{prefix} oder @code{suffix}
+gewählt werden, wodurch die gelieferten Definitionen der Umgebungsvariablen
+entweder exakt die Einstellungen für Guix meldet, oder sie als Präfix oder
+Suffix an den aktuellen Wert dieser Variablen anhängt. Gibt man keine
address@hidden an, wird der Vorgabewert @code{exact} verwendet.
 
-This option can also be used to compute the @emph{combined} search paths
-of several profiles.  Consider this example:
+Diese Befehlszeilenoption kann auch benutzt werden, um die
address@hidden Suchpfade mehrerer Profile zu berechnen. Betrachten Sie
+dieses Beispiel:
 
 @example
 $ guix package -p foo -i guile
@@ -2072,51 +2239,53 @@ $ guix package -p bar -i guile-json
 $ guix package -p foo -p bar --search-paths
 @end example
 
-The last command above reports about the @code{GUILE_LOAD_PATH}
-variable, even though, taken individually, neither @file{foo} nor
address@hidden would lead to that recommendation.
+Der letzte Befehl oben meldet auch die Definition der Umgebungsvariablen
address@hidden, obwohl für sich genommen weder @file{foo} noch
address@hidden zu dieser Empfehlung führen würden.
 
 
address@hidden address@hidden
address@hidden -p @var{profile}
-Use @var{profile} instead of the user's default profile.
address@hidden address@hidden
address@hidden -p @var{Profil}
+Auf @var{Profil} anstelle des Standardprofils des Benutzers arbeiten.
 
address@hidden collisions, in a profile
address@hidden colliding packages in profiles
address@hidden profile collisions
address@hidden Kollisionen, in einem Profil
address@hidden Paketkollisionen in Profilen
address@hidden Profilkollisionen
 @item --allow-collisions
-Allow colliding packages in the new profile.  Use at your own risk!
+Kollidierende Pakete im neuen Profil zulassen. Benutzung auf eigene Gefahr!
 
-By default, @command{guix package} reports as an error @dfn{collisions}
-in the profile.  Collisions happen when two or more different versions
-or variants of a given package end up in the profile.
+Standardmäßig wird @command{guix package} @dfn{Kollisionen} als Fehler
+auffassen und melden. Zu Kollisionen kommt es, wenn zwei oder mehr
+verschiedene Versionen oder Varianten desselben Pakets im Profil landen.
 
 @item --verbose
-Produce verbose output.  In particular, emit the build log of the
-environment on the standard error port.
+Erzeugt ausführliche Textausgaben. Insbesondere wird auch das
+Erstellungsprotokoll der Umgebung auf dem Standard-Fehler-Port (stderr)
+ausgegeben.
 
 @item --bootstrap
-Use the bootstrap Guile to build the profile.  This option is only
-useful to distribution developers.
+Erstellt das Profil mit dem Bootstrap-Guile. Diese Option ist nur für
+Entwickler der Distribution nützlich.
 
 @end table
 
-In addition to these actions, @command{guix package} supports the
-following options to query the current state of a profile, or the
-availability of packages:
+Zusätzlich zu diesen Aktionen unterstützt @command{guix package} folgende
+Befehlszeilenoptionen, um den momentanen Zustand eines Profils oder die
+Verfügbarkeit von Paketen nachzulesen:
 
 @table @option
 
address@hidden address@hidden
address@hidden -s @var{regexp}
address@hidden searching for packages
-List the available packages whose name, synopsis, or description matches
address@hidden, sorted by relevance.  Print all the metadata of matching 
packages in
address@hidden format (@pxref{Top, GNU recutils databases,, recutils,
-GNU recutils manual}).
address@hidden address@hidden
address@hidden -s @var{Regexp}
address@hidden Suche nach Paketen
+Führt alle verfügbaren Pakete aus, deren Name, Zusammenfassung oder
+Beschreibung zum regulären Ausdruck @var{Regexp} passt, sortiert nach ihrer
+Relevanz. Alle Metadaten passender Pakete werden im @code{recutils}-Format
+geliefert (@pxref{Top, GNU recutils databases,, recutils, GNU recutils
+manual}).
 
-This allows specific fields to be extracted using the @command{recsel}
-command, for instance:
+So können bestimmte Felder mit dem Befehl @command{recsel} extrahiert
+werden, zum Beispiel:
 
 @example
 $ guix package -s malloc | recsel -p name,version,relevance
@@ -2133,8 +2302,8 @@ version: 7.6.0
 relevance: 1
 @end example
 
-Similarly, to show the name of all the packages available under the
-terms of the address@hidden version 3:
+Ebenso kann der Name aller zu den Bedingungen der address@hidden, Version 3,
+verfügbaren Pakete ermittelt werden:
 
 @example
 $ guix package -s "" | recsel -p name -e 'license ~ "LGPL 3"'
@@ -2144,9 +2313,9 @@ name: gmp
 @dots{}
 @end example
 
-It is also possible to refine search results using several @code{-s}
-flags.  For example, the following command returns a list of board
-games:
+Es ist auch möglich, Suchergebnisse näher einzuschränken, indem Sie
address@hidden mehrmals übergeben. Zum Beispiel liefert folgender Befehl eines
+Liste von Brettspielen:
 
 @example
 $ guix package -s '\<board\>' -s game | recsel -p name
@@ -2154,14 +2323,16 @@ name: gnubg
 @dots{}
 @end example
 
-If we were to omit @code{-s game}, we would also get software packages
-that deal with printed circuit boards; removing the angle brackets
-around @code{board} would further add packages that have to do with
-keyboards.
+Würden wir @code{-s game} weglassen, bekämen wir auch Software-Pakete
+aufgelistet, die mit »printed circuit boards« (elektronischen Leiterplatten)
+zu tun haben; ohne die spitzen Klammern um @code{board} bekämen wir auch
+Pakete, die mit »keyboards« (Tastaturen, oder musikalischen Keyboard) zu tun
+haben.
 
-And now for a more elaborate example.  The following command searches
-for cryptographic libraries, filters out Haskell, Perl, Python, and Ruby
-libraries, and prints the name and synopsis of the matching packages:
+Es ist Zeit für ein komplexeres Beispiel. Folgender Befehl sucht
+kryptographische Bibliotheken, filtert Haskell-, Perl-, Python- und
+Ruby-Bibliotheken heraus und gibt Namen und Zusammenfassung passender Pakete
+aus:
 
 @example
 $ guix package -s crypto -s library | \
@@ -2169,12 +2340,12 @@ $ guix package -s crypto -s library | \
 @end example
 
 @noindent
address@hidden Expressions,,, recutils, GNU recutils manual}, for more
-information on @dfn{selection expressions} for @code{recsel -e}.
address@hidden Expressions,,, recutils, GNU recutils manual} enthält
+weitere Informationen über @dfn{Auswahlausdrücke} mit @code{recsel -e}.
 
address@hidden address@hidden
-Show details about @var{package}, taken from the list of available packages, in
address@hidden format (@pxref{Top, GNU recutils databases,, recutils, GNU
address@hidden address@hidden
+Zeigt Details über das @var{Paket} aus der Liste verfügbarer Pakete, im
address@hidden (@pxref{Top, GNU recutils databases,, recutils, GNU
 recutils manual}).
 
 @example
@@ -2186,8 +2357,8 @@ name: python
 version: 3.3.5
 @end example
 
-You may also specify the full name of a package to only get details about a
-specific version of it:
+Sie können auch den vollständigen Namen eines Pakets angeben, um Details nur
+über diese Version angezeigt zu bekommen:
 @example
 $ guix package --show=python@@3.4 | recsel -p name,version
 name: python
@@ -2196,187 +2367,197 @@ version: 3.4.3
 
 
 
address@hidden address@hidden
address@hidden -I address@hidden
-List the currently installed packages in the specified profile, with the
-most recently installed packages shown last.  When @var{regexp} is
-specified, list only installed packages whose name matches @var{regexp}.
address@hidden address@hidden
address@hidden -I address@hidden
+Listet die derzeit installierten Pakete im angegebenen Profil auf, die
+zuletzt installierten Pakete zuletzt. Wenn ein regulärer Ausdruck
address@hidden angegeben wird, werden nur installierte Pakete aufgeführt,
+deren Name zu @var{Regexp} passt.
 
-For each installed package, print the following items, separated by
-tabs: the package name, its version string, the part of the package that
-is installed (for instance, @code{out} for the default output,
address@hidden for its headers, etc.), and the path of this package in
-the store.
+Zu jedem installierten Paket werden folgende Informationen angezeigt, durch
+Tabulatorzeichen getrennt: der Paketname, die Version als Zeichenkette,
+welche Teile des Pakets installiert sind (zum Beispiel @code{out}, wenn die
+Standard-Paketausgabe installiert ist, @code{include}, wenn seine Header
+installiert sind, usw.) und an welchem Pfad das Paket im Store zu finden
+ist.
 
address@hidden address@hidden
address@hidden -A address@hidden
-List packages currently available in the distribution for this system
-(@pxref{GNU Distribution}).  When @var{regexp} is specified, list only
-installed packages whose name matches @var{regexp}.
address@hidden address@hidden
address@hidden -A address@hidden
+Listet Pakete auf, die in der aktuell installierten Distribution dieses
+Systems verfügbar sind (@pxref{GNU-Distribution}). Wenn ein regulärer
+Ausdruck @var{Regexp} angegeben wird, werden nur Pakete aufgeführt, deren
+Name zum regulären Ausdruck @var{Regexp} passt.
 
-For each package, print the following items separated by tabs: its name,
-its version string, the parts of the package (@pxref{Packages with
-Multiple Outputs}), and the source location of its definition.
+Zu jedem Paket werden folgende Informationen getrennt durch Tabulatorzeichen
+ausgegeben: der Name, die Version als Zeichenkette, die Teile des Programms
+(@pxref{Pakete mit mehreren Ausgaben.}) und die Stelle im Quellcode, an der
+das Paket definiert ist.
 
address@hidden address@hidden
address@hidden -l address@hidden
address@hidden generations
-Return a list of generations along with their creation dates; for each
-generation, show the installed packages, with the most recently
-installed packages shown last.  Note that the zeroth generation is never
-shown.
address@hidden address@hidden
address@hidden -l address@hidden
address@hidden Generationen
+Liefert eine Liste der Generationen zusammen mit dem Datum, an dem sie
+erzeugt wurden; zu jeder Generation werden zudem die installierten Pakete
+angezeigt, zuletzt installierte Pakete zuletzt. Beachten Sie, dass die
+nullte Generation niemals angezeigt wird.
 
-For each installed package, print the following items, separated by
-tabs: the name of a package, its version string, the part of the package
-that is installed (@pxref{Packages with Multiple Outputs}), and the
-location of this package in the store.
+Zu jedem installierten Paket werden folgende Informationen durch
+Tabulatorzeichen getrennt angezeigt: der Name des Pakets, die Version als
+Zeichenkette, welcher Teil des Pakets installiert ist (@pxref{Pakete mit 
mehreren Ausgaben.}) und an welcher Stelle sich das Paket im Store befindet.
 
-When @var{pattern} is used, the command returns only matching
-generations.  Valid patterns include:
+Wenn ein @var{Muster} angegeben wird, liefert der Befehl nur dazu passende
+Generationen. Gültige Muster sind zum Beispiel:
 
 @itemize
address@hidden @emph{Integers and comma-separated integers}.  Both patterns 
denote
-generation numbers.  For instance, @code{--list-generations=1} returns
-the first one.
address@hidden @emph{Ganze Zahlen und kommagetrennte ganze Zahlen}. Beide 
Muster bezeichnen
+Generationsnummern. Zum Beispiel liefert @code{--list-generations=1} die
+erste Generation.
 
-And @code{--list-generations=1,8,2} outputs three generations in the
-specified order.  Neither spaces nor trailing commas are allowed.
+Durch @code{--list-generations=1,8,2} werden drei Generationen in der
+angegebenen Reihenfolge angezeigt. Weder Leerzeichen noch ein Komma am
+Schluss der Liste ist erlaubt.
 
address@hidden @emph{Ranges}.  @code{--list-generations=2..9} prints the
-specified generations and everything in between.  Note that the start of
-a range must be smaller than its end.
address@hidden @emph{Bereiche}. @code{--list-generations=2..9} gibt die
+angegebenen Generationen und alles dazwischen aus. Beachten Sie, dass der
+Bereichsanfang eine kleinere Zahl als das Bereichsende sein muss.
 
-It is also possible to omit the endpoint.  For example,
address@hidden, returns all generations starting from the
-second one.
+Sie können auch kein Bereichsende angeben, zum Beispiel liefert
address@hidden alle Generationen ab der zweiten.
 
address@hidden @emph{Durations}.  You can also get the last @address@hidden, 
weeks,
address@hidden @emph{Zeitdauern}. Sie können auch die letzten @address@hidden, 
Wochen
 or months by passing an integer along with the first letter of the
-duration.  For example, @code{--list-generations=20d} lists generations
-that are up to 20 days old.
+duration.  For example, @code{--list-generations=20d} lists generations that
+are up to 20 days old.
 @end itemize
 
address@hidden address@hidden
address@hidden -d address@hidden
-When @var{pattern} is omitted, delete all generations except the current
-one.
address@hidden address@hidden
address@hidden -d address@hidden
+Wird kein @var{Muster} angegeben, werden alle Generationen außer der
+aktuellen entfernt.
 
-This command accepts the same patterns as @option{--list-generations}.
-When @var{pattern} is specified, delete the matching generations.  When
address@hidden specifies a duration, generations @emph{older} than the
-specified duration match.  For instance, @code{--delete-generations=1m}
-deletes generations that are more than one month old.
+Dieser Befehl akzeptiert dieselben Muster wie
address@hidden Wenn ein @var{Muster} angegeben wird, werden
+die passenden Generationen gelöscht. Wenn das @var{Muster} für eine
+Zeitdauer steht, werden diejenigen Generationen gelöscht, die @emph{älter}
+als die angegebene Dauer sind. Zum Beispiel löscht
address@hidden die Generationen, die mehr als einen Monat
+alt sind.
 
-If the current generation matches, it is @emph{not} deleted.  Also, the
-zeroth generation is never deleted.
+Falls die aktuelle Generation zum Muster passt, wird sie @emph{nicht}
+gelöscht. Auch die nullte Generation wird niemals gelöscht.
 
-Note that deleting generations prevents rolling back to them.
-Consequently, this command must be used with care.
+Beachten Sie, dass Sie auf gelöschte Generationen nicht zurückwechseln
+können. Dieser Befehl sollte also nur mit Vorsicht benutzt werden.
 
 @end table
 
-Finally, since @command{guix package} may actually start build
-processes, it supports all the common build options (@pxref{Common Build
-Options}).  It also supports package transformation options, such as
address@hidden (@pxref{Package Transformation Options}).
-However, note that package transformations are lost when upgrading; to
-preserve transformations across upgrades, you should define your own
-package variant in a Guile module and add it to @code{GUIX_PACKAGE_PATH}
-(@pxref{Defining Packages}).
-
address@hidden Substitutes
address@hidden Substitutes
-
address@hidden substitutes
address@hidden pre-built binaries
-Guix supports transparent source/binary deployment, which means that it
-can either build things locally, or download pre-built items from a
-server, or both.  We call these pre-built items @dfn{substitutes}---they
-are substitutes for local build results.  In many cases, downloading a
-substitute is much faster than building things locally.
-
-Substitutes can be anything resulting from a derivation build
-(@pxref{Derivations}).  Of course, in the common case, they are
-pre-built package binaries, but source tarballs, for instance, which
-also result from derivation builds, can be available as substitutes.
+Zu guter Letzt können Sie, da @command{guix package} Erstellungsprozesse zu
+starten vermag, auch alle gemeinsamen Erstellungsoptionen (@pxref{Gemeinsame 
Erstellungsoptionen}) verwenden. Auch Paketumwandlungsoptionen wie
address@hidden sind möglich (@pxref{Paketumwandlungsoptionen}). Beachten Sie 
jedoch, dass die verwendeten
+Paketumwandlungsoptionen verloren gehen, nachdem Sie die Pakete aktualisiert
+haben. Damit Paketumwandlungen über Aktualisierungen hinweg erhalten
+bleiben, sollten Sie Ihre eigene Paketvariante in einem Guile-Modul
+definieren und zur Umgebungsvariablen @code{GUIX_PACKAGE_PATH} hinzufügen
+(@pxref{Pakete definieren}).
+
address@hidden Substitute
address@hidden Substitute
+
address@hidden Substitute
address@hidden vorerstellte Binärdateien
+Guix kann transparent Binär- oder Quelldateien ausliefern. Das heißt, Dinge
+können sowohl lokal erstellt, als auch als vorerstellte Objekte von einem
+Server heruntergeladen werden, oder beides gemischt. Wir bezeichnen diese
+vorerstellten Objekte als @dfn{Substitute} — sie substituieren lokale
+Erstellungsergebnisse. In vielen Fällen geht das Herunterladen eines
+Substituts wesentlich schneller, als Dinge lokal zu erstellen.
+
+Substitute können alles sein, was das Ergebnis einer Ableitungserstellung
+ist (@pxref{Ableitungen}). Natürlich sind sie üblicherweise vorerstellte
+Paket-Binärdateien, aber wenn zum Beispiel ein Quell-Tarball das Ergebnis
+einer Ableitungserstellung ist, kann auch er als Substitut verfügbar sein.
 
 @menu
-* Official Substitute Server::  One particular source of substitutes.
-* Substitute Server Authorization::  How to enable or disable substitutes.
-* Substitute Authentication::   How Guix verifies substitutes.
-* Proxy Settings::              How to get substitutes via proxy.
-* Substitution Failure::        What happens when substitution fails.
-* On Trusting Binaries::        How can you trust that binary blob?
+* Offizieller Substitut-Server::  Eine besondere Quelle von Substituten.
+* Substitut-Server autorisieren::  Wie man Substitute an- und abschaltet.
+* Substitutauthentifizierung::  Wie Guix Substitute verifiziert.
+* Proxy-Einstellungen::      Wie Sie Substitute über einen Proxy beziehen.
+* Fehler bei der Substitution::  Was passiert, wenn die Substitution 
+                                   fehlschlägt.
+* Vom Vertrauen gegenüber Binärdateien::  Wie können Sie diesem binären 
+                                              Blob trauen?
 @end menu
 
address@hidden Official Substitute Server
address@hidden Official Substitute Server
-
address@hidden hydra
address@hidden build farm
-The @code{mirror.hydra.gnu.org} server is a front-end to an official build farm
-that builds packages from Guix continuously for some
-architectures, and makes them available as substitutes.  This is the
-default source of substitutes; it can be overridden by passing the
address@hidden option either to @command{guix-daemon}
-(@pxref{daemon-substitute-urls,, @code{guix-daemon --substitute-urls}})
-or to client tools such as @command{guix package}
-(@pxref{client-substitute-urls,, client @option{--substitute-urls}
-option}).
-
-Substitute URLs can be either HTTP or HTTPS.
-HTTPS is recommended because communications are encrypted; conversely,
-using HTTP makes all communications visible to an eavesdropper, who
-could use the information gathered to determine, for instance, whether
-your system has unpatched security vulnerabilities.
-
-Substitutes from the official build farm are enabled by default when
-using the Guix System Distribution (@pxref{GNU Distribution}).  However,
-they are disabled by default when using Guix on a foreign distribution,
-unless you have explicitly enabled them via one of the recommended
-installation steps (@pxref{Installation}).  The following paragraphs
-describe how to enable or disable substitutes for the official build
-farm; the same procedure can also be used to enable substitutes for any
-other substitute server.
-
address@hidden Substitute Server Authorization
address@hidden Substitute Server Authorization
-
address@hidden security
address@hidden substitutes, authorization thereof
address@hidden access control list (ACL), for substitutes
address@hidden ACL (access control list), for substitutes
-To allow Guix to download substitutes from @code{hydra.gnu.org} or a
-mirror thereof, you
-must add its public key to the access control list (ACL) of archive
-imports, using the @command{guix archive} command (@pxref{Invoking guix
-archive}).  Doing so implies that you trust @code{hydra.gnu.org} to not
-be compromised and to serve genuine substitutes.
-
-The public key for @code{hydra.gnu.org} is installed along with Guix, in
address@hidden@var{prefix}/share/guix/hydra.gnu.org.pub}, where @var{prefix} is
-the installation prefix of Guix.  If you installed Guix from source,
-make sure you checked the GPG signature of
address@hidden@value{VERSION}.tar.gz}, which contains this public key file.
-Then, you can run something like this:
address@hidden Offizieller Substitut-Server
address@hidden Offizieller Substitut-Server
+
address@hidden Hydra
address@hidden Build-Farm
+Der Server @code{mirror.hydra.gnu.org} ist die Façade für eine offizielle
+»Build-Farm«, ein Erstellungswerk, das kontinuierlich Guix-Pakete für einige
+Prozessorarchitekturen erstellt und sie als Substitute zur Verfügung
+stellt. Dies ist die standardmäßige Quelle von Substituten; durch Übergeben
+der Befehlszeilenoption @option{--substitute-urls} an entweder den
address@hidden (@pxref{daemon-substitute-urls,, @code{guix-daemon
+--substitute-urls}}) oder Client-Werkzeuge wie @command{guix package}
+(@pxref{client-substitute-urls,, client @option{--substitute-urls} option})
+kann eine abweichende Einstellung benutzt werden.
+
+Substitut-URLs können entweder HTTP oder HTTPS sein. HTTPS wird empfohlen,
+weil die Kommunikation verschlüsselt ist; umgekehrt kann bei HTTP die
+Kommunikation belauscht werden, wodurch der Angreifer zum Beispiel erfahren
+könnte, ob Ihr System über noch nicht behobene Sicherheitsschwachstellen
+verfügt.
+
+Substitute von der offiziellen Build-Farm sind standardmäßig erlaubt, wenn
+Sie die Guix System Distribution verwenden (@pxref{GNU-Distribution}). Auf
+Fremddistributionen sind sie allerdings standardmäßig ausgeschaltet, solange
+Sie sie nicht ausdrücklich in einem der empfohlenen Installationsschritte
+erlaubt haben (@pxref{Installation}). Die folgenden Absätze beschreiben, wie
+Sie Substitute für die offizielle Build-Farm an- oder ausschalten; dieselbe
+Prozedur kann auch benutzt werden, um Substitute für einen beliebigen
+anderen Substitutsserver zu erlauben.
+
address@hidden Substitut-Server autorisieren
address@hidden Substitut-Server autorisieren
+
address@hidden Sicherheit
address@hidden Substitute, deren Autorisierung
address@hidden Access Control List (ACL), für Substitute
address@hidden ACL (Access Control List), für Substitute
+Um es Guix zu gestatten, Substitute von @code{hydra.gnu.org} oder einem
+Spiegelserver davon herunterzuladen, müssen Sie den zugehörigen öffentlichen
+Schlüssel zur Access Control List (ACL, Zugriffssteuerungsliste) für
+Archivimporte hinzufügen, mit Hilfe des Befehls @command{guix archive}
+(@pxref{Aufruf von guix archive}). Dies impliziert, dass Sie darauf vertrauen,
+dass @code{hydra.gnu.org} nicht kompromittiert wurde und echte Substitute
+liefert.
+
+Der öffentliche Schlüssel für @code{hydra.gnu.org} wird zusammen mit Guix
+installiert, in das Verzeichnis
address@hidden@var{prefix}/share/guix/hydra.gnu.org.pub}, wobei @var{prefix} das
+Installationspräfix von Guix ist. Wenn Sie Guix aus seinem Quellcode heraus
+installieren, stellen Sie sicher, dass Sie die GPG-Signatur von
address@hidden@value{VERSION}.tar.gz} prüfen, worin sich dieser öffentliche
+Schlüssel befindet. Dann können Sie so etwas wie hier ausführen:
 
 @example
 # guix archive --authorize < @var{prefix}/share/guix/hydra.gnu.org.pub
 @end example
 
address@hidden Note
-Similarly, the @file{berlin.guixsd.org.pub} file contains the public key
-for the project's new build farm, reachable at
address@hidden://berlin.guixsd.org}.
address@hidden Anmerkung
+Genauso enthält die Datei @file{berlin.guixsd.org.pub} den öffentlichen
+Schlüssel für die neue Build-Farm des Guix-Projekts, die unter
address@hidden://berlin.guixsd.org} erreichbar ist.
 
-As of this writing @code{berlin.guixsd.org} is being upgraded so it can
-better scale up, but you might want to give it a try.  It is backed by
-20 x86_64/i686 build nodes and may be able to provide substitutes more
-quickly than @code{mirror.hydra.gnu.org}.
+Derzeit, als dieser Text geschrieben wurde, wird @code{berlin.guixsd.org}
+ausgebaut, um besser skalieren zu können, aber Sie könnten es
+ausprobieren. Dahinter stecken 20 x86_64-/i686-Erstellungsknoten, die
+Substitute früher anbieten könnten als @code{mirror.hydra.gnu.org}.
 @end quotation
 
-Once this is in place, the output of a command like @code{guix build}
-should change from something like:
+Sobald es eingerichtet wurde, sollte sich die Ausgabe eines Befehls wie
address@hidden build} von so etwas:
 
 @example
 $ guix build emacs --dry-run
@@ -2389,7 +2570,7 @@ The following derivations would be built:
 @end example
 
 @noindent
-to something like:
+in so etwas verwandeln:
 
 @example
 $ guix build emacs --dry-run
@@ -2402,403 +2583,422 @@ $ guix build emacs --dry-run
 @end example
 
 @noindent
-This indicates that substitutes from @code{hydra.gnu.org} are usable and
-will be downloaded, when possible, for future builds.
+Das zeigt an, dass Substitute von @code{hydra.gnu.org} nutzbar sind und für
+zukünftige Erstellungen heruntergeladen, wann immer es möglich ist.
 
address@hidden substitutes, how to disable
-The substitute mechanism can be disabled globally by running
address@hidden with @code{--no-substitutes} (@pxref{Invoking
-guix-daemon}).  It can also be disabled temporarily by passing the
address@hidden option to @command{guix package}, @command{guix
-build}, and other command-line tools.
address@hidden Substitute, wie man sie ausschaltet
+Der Substitutsmechanismus kann global ausgeschaltet werden, indem Sie dem
address@hidden beim Starten die Befehlszeilenoption
address@hidden übergeben (@pxref{Aufruf des guix-daemon}). Er kann
+auch temporär ausgeschaltet werden, indem Sie @code{--no-substitutes} an
address@hidden package}, @command{guix build} und andere
+Befehlszeilenwerkzeuge übergeben.
 
address@hidden Substitute Authentication
address@hidden Substitute Authentication
address@hidden Substitutauthentifizierung
address@hidden Substitutauthentifizierung
 
address@hidden digital signatures
-Guix detects and raises an error when attempting to use a substitute
-that has been tampered with.  Likewise, it ignores substitutes that are
-not signed, or that are not signed by one of the keys listed in the ACL.
address@hidden digitale Signaturen
+Guix erkennt, wenn ein verfälschtes Substitut benutzt würde, und meldet
+einen Fehler. Ebenso werden Substitute ignoriert, die nich signiert sind,
+oder nicht mit einem in der ACL aufgelisteten Schlüssel signiert sind.
 
-There is one exception though: if an unauthorized server provides
-substitutes that are @emph{bit-for-bit identical} to those provided by
-an authorized server, then the unauthorized server becomes eligible for
-downloads.  For example, assume we have chosen two substitute servers
-with this option:
+Es gibt nur eine Ausnahme: Wenn ein unautorisierter Server Substitute
+anbietet, die @emph{Bit für Bit identisch} mit denen von einem
+authorisierten Server sind, können sie auch vom unautorisierten Server
+heruntergeladen werden. Zum Beispiel, angenommen wir haben zwei
+Substitutserver mit dieser Befehlszeilenoption ausgewählt:
 
 @example
 --substitute-urls="https://a.example.org https://b.example.org";
 @end example
 
 @noindent
address@hidden reproducible builds
-If the ACL contains only the key for @code{b.example.org}, and if
address@hidden happens to serve the @emph{exact same} substitutes,
-then Guix will download substitutes from @code{a.example.org} because it
-comes first in the list and can be considered a mirror of
address@hidden  In practice, independent build machines usually
-produce the same binaries, thanks to bit-reproducible builds (see
-below).
-
-When using HTTPS, the server's X.509 certificate is @emph{not} validated
-(in other words, the server is not authenticated), contrary to what
-HTTPS clients such as Web browsers usually do.  This is because Guix
-authenticates substitute information itself, as explained above, which
-is what we care about (whereas X.509 certificates are about
-authenticating bindings between domain names and public keys.)
-
address@hidden Proxy Settings
address@hidden Proxy Settings
address@hidden Reproduzierbare Erstellungen
+Wenn in der ACL nur der Schlüssel für @code{b.example.org} aufgeführt wurde,
+aber @code{a.example.org} @emph{exakt dieselben} Substitute anbietet, wird
+Guix auch Substitute von @code{a.example.org} herunterladen, weil es in der
+Liste zuerst kommt und als Spiegelserver für @code{b.example.org} aufgefasst
+werden kann. In der Praxis haben unabhängige Maschinen bei der Erstellung
+normalerweise dieselben Binärdateien als Ergebnis, dank bit-reproduzierbarer
+Erstellungen (siehe unten).
+
+Wenn Sie HTTPS benutzen, wird das X.509-Zertifikat des Servers @emph{nicht}
+validiert (mit anderen Worten, die Identität des Servers wird nicht
+authentifiziert), entgegen dem, was HTTPS-Clients wie Web-Browser
+normalerweise tun. Da Guix Substitutinformationen selbst überprüft, wie oben
+erklärt, wäre es unnötig (wohingegen mit X.509-Zertifikaten geprüft wird, ob
+ein Domain-Name zu öffentlichen Schlüsseln passt).
+
address@hidden Proxy-Einstellungen
address@hidden Proxy-Einstellungen
 
 @vindex http_proxy
-Substitutes are downloaded over HTTP or HTTPS.
-The @code{http_proxy} environment
-variable can be set in the environment of @command{guix-daemon} and is
-honored for downloads of substitutes.  Note that the value of
address@hidden in the environment where @command{guix build},
address@hidden package}, and other client commands are run has
address@hidden no effect}.
-
address@hidden Substitution Failure
address@hidden Substitution Failure
-
-Even when a substitute for a derivation is available, sometimes the
-substitution attempt will fail.  This can happen for a variety of
-reasons: the substitute server might be offline, the substitute may
-recently have been deleted, the connection might have been interrupted,
-etc.
-
-When substitutes are enabled and a substitute for a derivation is
-available, but the substitution attempt fails, Guix will attempt to
-build the derivation locally depending on whether or not
address@hidden was given (@pxref{fallback-option,, common build
-option @code{--fallback}}).  Specifically, if @code{--fallback} was
-omitted, then no local build will be performed, and the derivation is
-considered to have failed.  However, if @code{--fallback} was given,
-then Guix will attempt to build the derivation locally, and the success
-or failure of the derivation depends on the success or failure of the
-local build.  Note that when substitutes are disabled or no substitute
-is available for the derivation in question, a local build will
address@hidden be performed, regardless of whether or not
address@hidden was given.
-
-To get an idea of how many substitutes are available right now, you can
-try running the @command{guix weather} command (@pxref{Invoking guix
-weather}).  This command provides statistics on the substitutes provided
-by a server.
-
address@hidden On Trusting Binaries
address@hidden On Trusting Binaries
-
address@hidden trust, of pre-built binaries
-Today, each individual's control over their own computing is at the
-mercy of institutions, corporations, and groups with enough power and
-determination to subvert the computing infrastructure and exploit its
-weaknesses.  While using @code{hydra.gnu.org} substitutes can be
-convenient, we encourage users to also build on their own, or even run
-their own build farm, such that @code{hydra.gnu.org} is less of an
-interesting target.  One way to help is by publishing the software you
-build using @command{guix publish} so that others have one more choice
-of server to download substitutes from (@pxref{Invoking guix publish}).
-
-Guix has the foundations to maximize build reproducibility
-(@pxref{Features}).  In most cases, independent builds of a given
-package or derivation should yield bit-identical results.  Thus, through
-a diverse set of independent package builds, we can strengthen the
-integrity of our systems.  The @command{guix challenge} command aims to
-help users assess substitute servers, and to assist developers in
-finding out about non-deterministic package builds (@pxref{Invoking guix
-challenge}).  Similarly, the @option{--check} option of @command{guix
-build} allows users to check whether previously-installed substitutes
-are genuine by rebuilding them locally (@pxref{build-check,
+Substitute werden über HTTP oder HTTPS heruntergeladen. Die
+Umgebungsvariable @code{http_proxy} kann in der Umgebung von
address@hidden definiert werden und wirkt sich dann auf das
+Herunterladen von Substituten aus. Beachten Sie, dass der Wert von
address@hidden in der Umgebung, in der @command{guix build},
address@hidden package} und andere Client-Befehle ausgeführt werden,
address@hidden Rolle spielt}.
+
address@hidden Fehler bei der Substitution
address@hidden Fehler bei der Substitution
+
+Selbst wenn ein Substitut für eine Ableitung verfügbar ist, schlägt die
+versuchte Substitution manchmal fehl. Das kann aus vielen Gründen geschehen:
+die Substitutsserver könnten offline sein, das Substitut könnte kürzlich
+gelöscht worden sein, die Netzwerkverbindunge könnte unterbrochen worden
+sein, usw.
+
+Wenn Substitute aktiviert sind und ein Substitut für eine Ableitung zwar
+verfügbar ist, aber die versuchte Substitution fehlschlägt, kann Guix
+versuchen, die Ableitung lokal zu erstellen, je nachdem, ob
address@hidden übergeben wurde (@pxref{fallback-option,, common build
+option @code{--fallback}}). Genauer gesagt, wird keine lokale Erstellung
+durchgeführt, solange kein @code{--fallback} angegeben wurde, und die
+Ableitung wird als Fehlschlag angesehen. Wenn @code{--fallback} übergeben
+wurde, wird Guix versuchen, die Ableitung lokal zu erstellen, und ob die
+Ableitung erfolgreich ist oder nicht, hängt davon ab, ob die lokale
+Erstellung erfolgreich ist oder nicht. Beachten Sie, dass, falls Substitute
+ausgeschaltet oder erst gar kein Substitut verfügbar ist, @emph{immer} eine
+lokale Erstellung durchgeführt wird, egal ob @code{--fallback} übergeben
+wurde oder nicht.
+
+Um eine Vorstellung zu bekommen, wieviele Substitute gerade verfügbar sind,
+können Sie den Befehl @command{guix weather} benutzen (@pxref{Aufruf von guix 
weather}). Dieser Befehl zeigt Statistiken darüber an, wie es um die von
+einem Server verfügbaren Substitute steht.
+
address@hidden Vom Vertrauen gegenüber Binärdateien
address@hidden Vom Vertrauen gegenüber Binärdateien
+
address@hidden Vertrauen, gegenüber vorerstellten Binärdateien
+Derzeit hängt die Kontrolle jedes Individuums über seine Rechner von
+Institutionen, Unternehmen undsolchen Gruppierungen ab, die über genug Macht
+und Entschlusskraft verfügen, die Rechnerinfrastruktur zu sabotieren und
+ihre Schwachstellen auszunutzen. Auch wenn es bequem ist, Substitute von
address@hidden zu benutzen, ermuntern wir Nutzer, auch selbst
+Erstellungen durchzuführen oder gar ihre eigene Build-Farm zu betreiben,
+damit @code{hydra.gnu.org} ein weniger interessantes Ziel wird. Eine Art,
+uns zu helfen, ist, die von Ihnen erstellte Software mit dem Befehl
address@hidden publish} zu veröffentlichen, damit andere eine größere Auswahl
+haben, von welchem Server sie Substitute beziehen möchten (@pxref{Aufruf von 
guix publish}).
+
+Guix hat die richtigen Grundlagen, um die Reproduzierbarkeit von
+Erstellungen zu maximieren (@pxref{Funktionalitäten}). In den meisten Fällen 
sollten
+unabhängige Erstellungen eines bestimmten Pakets zu bitweise identischen
+Ergebnissen führen. Wir können also mit Hilfe einer vielschichtigen Menge an
+unabhängigen Paketerstellungen die Integrität unseres Systems besser
+gewährleisten. Der Befehl @command{guix challenge} hat das Ziel, Nutzern zu
+ermöglichen, Substitutserver zu beurteilen, und Entwicklern zu ermöglichen,
+nichtdeterministische Paketerstellungen zu finden (@pxref{Aufruf von guix 
challenge}). Ebenso ermöglicht es die Befehlszeilenoption @option{--check}
+von @command{guix build}, dass Nutzer bereits installierte Substitute auf
+Echtheit zu prüfen, indem sie lokal nachgebaut werden (@pxref{build-check,
 @command{guix build --check}}).
 
-In the future, we want Guix to have support to publish and retrieve
-binaries to/from other users, in a peer-to-peer fashion.  If you would
-like to discuss this project, join us on @email{guix-devel@@gnu.org}.
-
address@hidden Packages with Multiple Outputs
address@hidden Packages with Multiple Outputs
-
address@hidden multiple-output packages
address@hidden package outputs
address@hidden outputs
-
-Often, packages defined in Guix have a single @dfn{output}---i.e., the
-source package leads to exactly one directory in the store.  When running
address@hidden package -i glibc}, one installs the default output of the
-GNU libc package; the default output is called @code{out}, but its name
-can be omitted as shown in this command.  In this particular case, the
-default output of @code{glibc} contains all the C header files, shared
-libraries, static libraries, Info documentation, and other supporting
-files.
-
-Sometimes it is more appropriate to separate the various types of files
-produced from a single source package into separate outputs.  For
-instance, the GLib C library (used by GTK+ and related packages)
-installs more than 20 MiB of reference documentation as HTML pages.
-To save space for users who do not need it, the documentation goes to a
-separate output, called @code{doc}.  To install the main GLib output,
-which contains everything but the documentation, one would run:
+In Zukunft wollen wir, dass Guix Binärdateien an und von Nutzern in einem
+Peer-to-Peer veröffentlichen kann. Wenn Sie mit uns dieses Projekt
+diskuttieren möchten, kommen Sie auf unsere Mailing-Liste
address@hidden@@gnu.org}.
+
address@hidden Pakete mit mehreren Ausgaben.
address@hidden Pakete mit mehreren Ausgaben.
+
address@hidden mehrere Ausgaben, bei Paketen
address@hidden Paketausgaben
address@hidden Ausgaben
+
+Oft haben in Guix definierte Pakete eine einzige @dfn{Ausgabe} — d.h. aus
+dem Quellpaket entsteht genau ein Verzeichnis im Store. Wenn Sie
address@hidden package -i glibc} ausführen, wird die Standard-Paketausgabe
+des GNU-libc-Pakets installiert; die Standardausgabe wird @code{out}
+genannt, aber ihr Name kann weggelassen werden, wie sie an obigem Befehl
+sehen. In diesem speziellen Fall enthält die Standard-Paketausgabe von
address@hidden alle C-Headerdateien, gemeinsamen Bibliotheken (»Shared
+Libraries«), statische Bibliotheken (»Static Libraries«), Dokumentation für
+Info sowie andere zusätzliche Dateien.
+
+Manchmal ist es besser, die verschiedenen Arten von Dateien, die aus einem
+einzelnen Quellpaket hervorgehen, in getrennte Ausgaben zu unterteilen. Zum
+Beispiel installiert die GLib-C-Bibliothek (die von GTK+ und damit
+zusammenhängenden Paketen benutzt wird) mehr als 20 MiB an HTML-Seiten mit
+Referenzdokumentation. Um den Nutzern, die das nicht brauchen, Platz zu
+sparen, wird die Dokumentation in einer separaten Ausgabe abgelegt, genannt
address@hidden Um also die Hauptausgabe von GLib zu installieren, zu der alles
+außer der Dokumentation gehört, ist der Befehl:
 
 @example
 guix package -i glib
 @end example
 
address@hidden documentation
-The command to install its documentation is:
address@hidden Dokumentation
+Der Befehl, um die Dokumentation zu installieren, ist:
 
 @example
 guix package -i glib:doc
 @end example
 
-Some packages install programs with different ``dependency footprints''.
-For instance, the WordNet package installs both command-line tools and
-graphical user interfaces (GUIs).  The former depend solely on the C
-library, whereas the latter depend on Tcl/Tk and the underlying X
-libraries.  In this case, we leave the command-line tools in the default
-output, whereas the GUIs are in a separate output.  This allows users
-who do not need the GUIs to save space.  The @command{guix size} command
-can help find out about such situations (@pxref{Invoking guix size}).
address@hidden graph} can also be helpful (@pxref{Invoking guix graph}).
-
-There are several such multiple-output packages in the GNU distribution.
-Other conventional output names include @code{lib} for libraries and
-possibly header files, @code{bin} for stand-alone programs, and
address@hidden for debugging information (@pxref{Installing Debugging
-Files}).  The outputs of a packages are listed in the third column of
-the output of @command{guix package --list-available} (@pxref{Invoking
-guix package}).
-
-
address@hidden Invoking guix gc
address@hidden Invoking @command{guix gc}
-
address@hidden garbage collector
address@hidden disk space
-Packages that are installed, but not used, may be @dfn{garbage-collected}.
-The @command{guix gc} command allows users to explicitly run the garbage
-collector to reclaim space from the @file{/gnu/store} directory.  It is
-the @emph{only} way to remove files from @file{/gnu/store}---removing
-files or directories manually may break it beyond repair!
-
address@hidden GC roots
address@hidden garbage collector roots
-The garbage collector has a set of known @dfn{roots}: any file under
address@hidden/gnu/store} reachable from a root is considered @dfn{live} and
-cannot be deleted; any other file is considered @dfn{dead} and may be
-deleted.  The set of garbage collector roots (``GC roots'' for short)
-includes default user profiles; by default, the symlinks under
address@hidden/var/guix/gcroots} represent these GC roots.  New GC roots can be
-added with @command{guix build --root}, for example (@pxref{Invoking
-guix build}).
-
-Prior to running @code{guix gc --collect-garbage} to make space, it is
-often useful to remove old generations from user profiles; that way, old
-package builds referenced by those generations can be reclaimed.  This
-is achieved by running @code{guix package --delete-generations}
-(@pxref{Invoking guix package}).
-
-Our recommendation is to run a garbage collection periodically, or when
-you are short on disk space.  For instance, to guarantee that at least
address@hidden are available on your disk, simply run:
+Manche Pakete installieren Programme mit unterschiedlich großem
+»Abhängigkeiten-Fußabdruck«. Zum Beispiel installiert das Paket WordNet
+sowohl Befehlszeilenwerkzeuge als auch grafische Benutzerschnittstellen
+(GUIs). Erstere hängen nur von der C-Bibliothek ab, während Letztere auch
+von Tcl/Tk und den zu Grunde liegenden X-Bibliotheken abhängen. Jedenfalls
+belassen wir deshalb die Befehlszeilenwerkzeuge in der
+Standard-Paketausgabe, während sich die GUIs in einer separaten Ausgabe
+befinden. So können Benutzer, die die GUIs nicht brauchen, Platz sparen. Der
+Befehl @command{guix size} kann dabei helfen, solche Situationen zu erkennen
+(@pxref{Aufruf von guix size}). @command{guix graph} kann auch helfen
+(@pxref{Aufruf von guix graph}).
+
+In der GNU-Distribution gibt es viele solche Pakete mit mehreren
+Ausgaben. Andere Konventionen für Ausgabenamen sind zum Beispiel @code{lib}
+für Bibliotheken und eventuell auch ihre Header-Dateien,, @code{bin} für
+eigenständige Programme und @code{debug} für Informationen zur
+Fehlerbehandlung (@pxref{Dateien zur Fehlersuche installieren}). Die Ausgaben 
eines
+Pakets stehen in der dritten Spalte der Anzeige von @command{guix package
+--list-available} (@pxref{Aufruf von guix package}).
+
+
address@hidden Aufruf von guix gc
address@hidden @command{guix gc} aufrufen
+
address@hidden Müllsammler
address@hidden Plattenspeicher
+Pakete, die zwar installiert sind, aber nicht benutzt werden, können vom
address@hidden entfernt werden. Mit dem Befehl @command{guix gc} können
+Benutzer den Müllsammler ausdrücklich aufrufen, um Speicher im Verzeichnis
address@hidden/gnu/store} freizugeben. Dies ist der @emph{einzige} Weg, Dateien 
aus
address@hidden/gnu/store} zu entfernen — das manuelle Entfernen von Dateien 
kann den
+Store irreparabel beschädigen!
+
address@hidden GC-Wurzeln
address@hidden Müllsammlerwurzeln
+Der Müllsammler kennt eine Reihe von @dfn{Wurzeln}: Jede Datei in
address@hidden/gnu/store}, die von einer Wurzel aus erreichbar ist, gilt als
address@hidden und kann nicht entfernt werden; jede andere Datei gilt als
address@hidden und ist ein Kandidat, gelöscht zu werden. Die Reihe der
+Müllsammlerwurzeln (kurz auch »GC-Wurzeln«, von englisch »Garbage
+Collector«) umfasst Standard-Benutzerprofile; standardmäßig werden diese
+Müllsammlerwurzeln durch symbolische Verknüpfungen in
address@hidden/var/guix/gcroots} dargestellt. Neue Müllsammlerwurzeln können zum
+Beispiel mit @command{guix build --root} festgelegt werden (@pxref{Aufruf von 
guix build}).
+
+Bevor Sie mit @code{guix gc --collect-garbage} Speicher freimachen, wollen
+Sie vielleicht alte Generationen von Benutzerprofilen löschen, damit alte
+Paketerstellungen von diesen Generationen entfernt werden können. Führen Sie
+dazu @code{guix package --delete-generations} aus (@pxref{Aufruf von guix 
package}).
+
+Unsere Empfehlung ist, dass Sie den Müllsammler regelmäßig laufen lassen und
+wenn Sie wenig freien Speicherplatz zur Verfügung haben. Um zum Beispiel
+sicherzustellen, dass Sie mindestens address@hidden are auf Ihrer Platte zur
+Verfügung haben, benutzen Sie einfach:
 
 @example
 guix gc -F 5G
 @end example
 
-It is perfectly safe to run as a non-interactive periodic job
-(@pxref{Scheduled Job Execution}, for how to set up such a job on
-GuixSD).  Running @command{guix gc} with no arguments will collect as
-much garbage as it can, but that is often inconvenient: you may find
-yourself having to rebuild or re-download software that is ``dead'' from
-the GC viewpoint but that is necessary to build other pieces of
-software---e.g., the compiler tool chain.
+Es ist völlig sicher, dafür eine nicht interaktive, regelmäßige
+Auftragsausführung vorzugeben (@pxref{Geplante Auftragsausführung}, für eine
+Erklärung, wie man das in GuixSD tun kann). @command{guix gc} ohne
+Befehlszeilenargumente auszuführen, lässt so viel Müll wie möglich sammeln,
+aber das ist oft nicht, was man will, denn so muss man unter Umständen
+Software erneut erstellen oder erneut herunterladen, weil der Müllsammler
+sie als »tot« ansieht, sie aber zur Erstellung anderer Software wiedeer
+gebraucht wird — das trifft zum Beispiel auf die Compiler-Toolchain zu.
 
-The @command{guix gc} command has three modes of operation: it can be
-used to garbage-collect any dead files (the default), to delete specific
-files (the @code{--delete} option), to print garbage-collector
-information, or for more advanced queries.  The garbage collection
-options are as follows:
+Der Befehl @command{guix gc} hat drei Arbeitsmodi: Er kann benutzt werden,
+um als Müllsammler tote Dateien zu entfernen (das Standardverhalten), um
+ganz bestimmte, angegebene Datein zu löschen (mit der Befehlszeilenoption
address@hidden), um Müllsammlerinformationen auszugeben oder
+fortgeschrittenere Anfragen zu verarbeiten. Die
+Müllsammler-Befehlszeilenoptionen sind wie folgt:
 
 @table @code
address@hidden address@hidden
address@hidden -C address@hidden
-Collect garbage---i.e., unreachable @file{/gnu/store} files and
-sub-directories.  This is the default operation when no option is
-specified.
address@hidden address@hidden
address@hidden -C address@hidden
+Lässt Müll sammeln — z.B. nicht erreichbare Dateien in @file{/gnu/store} und
+seinen Unterverzeichnissen. Wird keine andere Befehlszeilenoption angegeben,
+wird standardmäßig diese durchgeführt.
 
-When @var{min} is given, stop once @var{min} bytes have been collected.
address@hidden may be a number of bytes, or it may include a unit as a
-suffix, such as @code{MiB} for mebibytes and @code{GB} for gigabytes
-(@pxref{Block size, size specifications,, coreutils, GNU Coreutils}).
+Wenn ein @var{Minimum} angegeben wurde, hört der Müllsammler auf, sobald
address@hidden Bytes gesammelt wurden. Das @var{Minimum} kann die Anzahl der
+Bytes bezeichnen oder mit einer Einheit als Suffix versehen sein, wie etwa
address@hidden für Mebibytes und @code{GB} für Gigabytes (@pxref{Block size,
+size specifications,, coreutils, GNU Coreutils}).
 
-When @var{min} is omitted, collect all the garbage.
+Wird kein @var{Minimum} angegeben, sammelt der Müllsammler allen Müll.
 
address@hidden address@hidden
address@hidden -F @var{free}
-Collect garbage until @var{free} space is available under
address@hidden/gnu/store}, if possible; @var{free} denotes storage space, such
-as @code{500MiB}, as described above.
address@hidden address@hidden
address@hidden -F @var{Menge}
+Sammelt Müll, bis die angegebene @var{Menge} an freiem Speicher in
address@hidden/gnu/store} zur Verfügung steht, falls möglich; die @var{Menge} 
ist
+eine Speichergröße wie @code{500MiB}, wie oben beschrieben.
 
-When @var{free} or more is already available in @file{/gnu/store}, do
-nothing and exit immediately.
+Wenn die angegebene  @var{Menge} oder mehr bereits in @file{/gnu/store} frei
+verfügbar ist, passiert nichts.
 
 @item --delete
 @itemx -d
-Attempt to delete all the store files and directories specified as
-arguments.  This fails if some of the files are not in the store, or if
-they are still live.
+Versucht, alle als Argumente angegebenen Dateien oder Verzeichnisse im Store
+zu löschen. Dies schlägt fehl, wenn manche der Dateien oder Verzeichnisse
+nicht im Store oder noch immer lebendig sind.
 
 @item --list-failures
-List store items corresponding to cached build failures.
+Store-Objekte auflisten, die zwischengespeicherten Erstellungsfehlern
+entsprechen.
 
-This prints nothing unless the daemon was started with
address@hidden (@pxref{Invoking guix-daemon,
+Hierbei wird nichts ausgegeben, sofern der Daemon nicht mit
address@hidden gestartet wurde (@pxref{Aufruf des guix-daemon,
 @option{--cache-failures}}).
 
 @item --clear-failures
-Remove the specified store items from the failed-build cache.
+Die angegebenen Store-Objekte aus dem Zwischenspeicher für fehlgeschlagene
+Erstellungen entfernen.
 
-Again, this option only makes sense when the daemon is started with
address@hidden  Otherwise, it does nothing.
+Auch diese Option macht nur Sinn, wenn der Daemon mit
address@hidden gestartet wurde. Andernfalls passiert nichts.
 
 @item --list-dead
-Show the list of dead files and directories still present in the
-store---i.e., files and directories no longer reachable from any root.
+Zeigt die Liste toter Dateien und Verzeichnisse an, die sich noch im Store
+befinden — das heißt, Dateien, die von keiner Wurzel mehr erreichbar sind.
 
 @item --list-live
-Show the list of live store files and directories.
+Zeige die Liste lebendiger Store-Dateien und -Verzeichnisse.
 
 @end table
 
-In addition, the references among existing store files can be queried:
+Außerdem können Referenzen unter bestehenden Store-Dateien gefunden werden:
 
 @table @code
 
 @item --references
 @itemx --referrers
address@hidden package dependencies
-List the references (respectively, the referrers) of store files given
-as arguments.
address@hidden Paketabhängigkeiten
+Listet die referenzierten bzw. sie referenzierenden Objekte der angegebenen
+Store-Dateien auf.
 
 @item --requisites
 @itemx -R
address@hidden closure
-List the requisites of the store files passed as arguments.  Requisites
-include the store files themselves, their references, and the references
-of these, recursively.  In other words, the returned list is the
address@hidden closure} of the store files.
address@hidden Abschluss
+Listet alle Voraussetzungen der als Argumente übergebenen Store-Dateien
+auf. Voraussetzungen sind die Store-Dateien selbst, ihre Referenzen sowie
+die Referenzen davon, rekursiv. Mit anderen Worten, die zurückgelieferte
+Liste ist der @dfn{transitive Abschluss} dieser Store-Dateien.
 
address@hidden guix size}, for a tool to profile the size of the closure
-of an element.  @xref{Invoking guix graph}, for a tool to visualize
-the graph of references.
+Der Abschnitt @xref{Aufruf von guix size} erklärt ein Werkzeug, um den
+Speicherbedarf des Abschlusses eines Elements zu ermitteln. Siehe
address@hidden von guix graph} für ein Werkzeug, um den Referenzgraph zu
+veranschaulichen.
 
 @item --derivers
address@hidden derivation
-Return the derivation(s) leading to the given store items
-(@pxref{Derivations}).
address@hidden Ableitung
+Liefert die Ableitung(en), die zu den angegebenen Store-Objekten führen
+(@pxref{Ableitungen}).
 
-For example, this command:
+Zum Beispiel liefert dieser Befehl:
 
 @example
 guix gc --derivers `guix package -I ^emacs$ | cut -f4`
 @end example
 
 @noindent
-returns the @file{.drv} file(s) leading to the @code{emacs} package
-installed in your profile.
+die @file{.drv}-Datei(en), die zum in Ihrem Profil installierten
address@hidden führen.
 
-Note that there may be zero matching @file{.drv} files, for instance
-because these files have been garbage-collected.  There can also be more
-than one matching @file{.drv} due to fixed-output derivations.
+Beachten Sie, dass es auch sein kann, dass keine passenden
address@hidden existieren, zum Beispiel wenn diese Dateien bereits dem
+Müllsammler zum Opfer gefallen sind. Es kann auch passieren, dass es mehr
+als eine passende @file{.drv} gibt, bei Ableitungen mit fester Ausgabe.
 @end table
 
-Lastly, the following options allow you to check the integrity of the
-store and to control disk usage.
+Zuletzt können Sie mit folgenden Befehlszeilenoptionen die Integrität des
+Stores prüfen und den Plattenspeicherverbrauch im Zaum halten.
 
 @table @option
 
address@hidden address@hidden
address@hidden integrity, of the store
address@hidden integrity checking
-Verify the integrity of the store.
-
-By default, make sure that all the store items marked as valid in the
-database of the daemon actually exist in @file{/gnu/store}.
-
-When provided, @var{options} must be a comma-separated list containing one
-or more of @code{contents} and @code{repair}.
-
-When passing @option{--verify=contents}, the daemon computes the
-content hash of each store item and compares it against its hash in the
-database.  Hash mismatches are reported as data corruptions.  Because it
-traverses @emph{all the files in the store}, this command can take a
-long time, especially on systems with a slow disk drive.
-
address@hidden repairing the store
address@hidden corruption, recovering from
-Using @option{--verify=repair} or @option{--verify=contents,repair}
-causes the daemon to try to repair corrupt store items by fetching
-substitutes for them (@pxref{Substitutes}).  Because repairing is not
-atomic, and thus potentially dangerous, it is available only to the
-system administrator.  A lightweight alternative, when you know exactly
-which items in the store are corrupt, is @command{guix build --repair}
-(@pxref{Invoking guix build}).
address@hidden address@hidden
address@hidden Integrität, des Stores
address@hidden Integritätsprüfung
+Die Integrität des Stores verifizieren
+
+Standardmäßig wird sichergestellt, dass alle Store-Objekte, die in der
+Datenbank des Daemons als gültig markiert wurden, auch tatsächlich in
address@hidden/gnu/store} existieren.
+
+Wenn angegeben, müssen die @var{Optionen} eine kommagetrennte Liste aus
+mindestens einem der Worte @code{contents} und @code{repair} sein.
+
+Wenn Sie @option{--verify=contents} übergeben, berechnet der Daemon den Hash
+des Inhalts jedes Store-Objekts und vergleicht ihn mit dem Hash in der
+Datenbank. Sind die Hashes ungleich, wird eine Datenbeschädigung
+gemeldet. Weil dabei @emph{alle Dateien im Store} durchlaufen werden, kann
+der Befehl viel Zeit brauchen, besonders auf Systemen mit langsamer Platte.
+
address@hidden Store, reparieren
address@hidden Datenbeschädigung, Behebung
+Mit @option{--verify=repair} oder @option{--verify=contents,repair} versucht
+der Daemon, beschädigte Store-Objekte zu reparieren, indem er Substitute für
+selbige herunterlädt (@pxref{Substitute}). Weil die Reparatur nicht atomar
+und daher womöglich riskant ist, kann nur der Systemadministrator den Befehl
+benutzen. Eine weniger aufwendige Alternative, wenn Sie wissen, welches
+Objekt beschädigt ist, ist, @command{guix build --repair} zu benutzen
+(@pxref{Aufruf von guix build}).
 
 @item --optimize
address@hidden deduplication
-Optimize the store by hard-linking identical files---this is
address@hidden
address@hidden Deduplizieren
+Den Store durch Nutzung harter Verknüpfungen für identische Dateien
+optimieren — mit anderen Worten wird der Store @dfn{dedupliziert}.
 
-The daemon performs deduplication after each successful build or archive
-import, unless it was started with @code{--disable-deduplication}
-(@pxref{Invoking guix-daemon, @code{--disable-deduplication}}).  Thus,
-this option is primarily useful when the daemon was running with
address@hidden
+Der Daemon führt Deduplizierung automatisch nach jeder erfolgreichen
+Erstellung und jedem Importieren eines Archivs durch, sofern er nicht mit
address@hidden (@pxref{Aufruf des guix-daemon,
address@hidden) gestartet wurde. Diese Befehlszeilenoption
+brauchen Sie also in erster Linie dann, wenn der Daemon zuvor mit
address@hidden gestartet worden ist.
 
 @end table
 
address@hidden Invoking guix pull
address@hidden Invoking @command{guix pull}
address@hidden Aufruf von guix pull
address@hidden @command{guix pull} aufrufen
 
address@hidden upgrading Guix
address@hidden updating Guix
address@hidden Aktualisieren von Guix
address@hidden Updaten von Guix
 @cindex @command{guix pull}
 @cindex pull
-Packages are installed or upgraded to the latest version available in
-the distribution currently available on your local machine.  To update
-that distribution, along with the Guix tools, you must run @command{guix
-pull}: the command downloads the latest Guix source code and package
-descriptions, and deploys it.  Source code is downloaded from a
address@hidden://git-scm.com, Git} repository, by default the official
address@hidden repository, though this can be customized.
-
-On completion, @command{guix package} will use packages and package
-versions from this just-retrieved copy of Guix.  Not only that, but all
-the Guix commands and Scheme modules will also be taken from that latest
-version.  New @command{guix} sub-commands added by the update also
-become available.
-
-Any user can update their Guix copy using @command{guix pull}, and the
-effect is limited to the user who run @command{guix pull}.  For
-instance, when user @code{root} runs @command{guix pull}, this has no
-effect on the version of Guix that user @code{alice} sees, and vice
-versa.
-
-The result of running @command{guix pull} is a @dfn{profile} available
-under @file{~/.config/guix/current} containing the latest Guix.  Thus,
-make sure to add it to the beginning of your search path so that you use
-the latest version, and similarly for the Info manual
-(@pxref{Documentation}):
+Packages are installed or upgraded to the latest version available in the
+distribution currently available on your local machine.  To update that
+distribution, along with the Guix tools, you must run @command{guix pull}:
+the command downloads the latest Guix source code and package descriptions,
+and deploys it.  Source code is downloaded from a @uref{https://git-scm.com,
+Git} repository, by default the official address@hidden repository, though
+this can be customized.
+
+Danach wird @command{guix package} Pakete und ihre Versionen entsprechend
+der gerade heruntergeladenen Kopie von Guix benutzen. Nicht nur das, auch
+alle Guix-Befehle und Scheme-Module werden aus der neuesten Version von Guix
+kommen. Neue @command{guix}-Unterbefehle, die durch die Aktualisierung
+hinzugekommen sind, werden also auch verfügbar.
+
+Jeder Nutzer kann seine Kopie von Guix mittels @command{guix pull}
+aktualisieren, wodurch sich nur für den Nutzer etwas verändert, der
address@hidden pull} ausgeführt hat. Wenn also zum Beispiel der
+Administratornutzer @code{root} den Befehl @command{guix pull} ausführt, hat
+das keine Auswirkungen, auf die für den Benutzer @code{alice} sichtbare
+Guix-Version, und umgekehrt.
+
+Das Ergebnis von @command{guix pull} ist ein als
address@hidden/.config/guix/current} verfügbares @dfn{Profil} mit dem neuesten
+Guix. Stellen Sie sicher, dass es am Anfang Ihres Suchpfades steht, damit
+Sie auch wirklich das neueste Guix und sein Info-Handbuch sehen
+(@pxref{Dokumentation}):
 
 @example
 export PATH="$HOME/.config/guix/current/bin:$PATH"
 export INFOPATH="$HOME/.config/guix/current/share/info:$INFOPATH"
 @end example
 
-The @code{--list-generations} or @code{-l} option lists past generations
-produced by @command{guix pull}, along with details about their provenance:
+Die Befehlszeilenoption @code{--list-generations} oder kurz @code{-l} listet
+ältere von @command{guix pull} erzeugte Generationen auf, zusammen mit
+Informationen zu deren Provenienz.
 
 @example
 $ guix pull -l
@@ -2830,10 +3030,10 @@ Generation 3    Jun 13 2018 23:31:07    (current)
 @ref{Invoking guix describe, @command{guix describe}}, for other ways to
 describe the current status of Guix.
 
-This @code{~/.config/guix/current} profile works like any other profile
-created by @command{guix package} (@pxref{Invoking guix package}).  That
-is, you can list generations, roll back to the previous
-generation---i.e., the previous Guix---and so on:
+Das Profil @code{~/.config/guix/current} verhält sich genau wie jedes andere
+Profil, das von @command{guix package} erzeugt wurde (@pxref{Aufruf von guix 
package}). Das bedeutet, Sie können seine Generationen auflisten und es auf
+die vorherige Generation — also das vorherige Guix — zurücksetzen und so
+weiter:
 
 @example
 $ guix package -p ~/.config/guix/current --roll-back
@@ -2842,18 +3042,19 @@ $ guix package -p ~/.config/guix/current 
--delete-generations=1
 deleting /var/guix/profiles/per-user/charlie/current-guix-1-link
 @end example
 
-The @command{guix pull} command is usually invoked with no arguments,
-but it supports the following options:
+Der Befehl @command{guix pull} wird in der Regel ohne Befehlszeilenargumente
+aufgerufen, aber er versteht auch folgende Befehlszeilenoptionen:
 
 @table @code
 @item --verbose
-Produce verbose output, writing build logs to the standard error output.
+Ausführliche Informationen ausgeben und Erstellungsprotokolle auf der
+Standardfehlerausgabe ausgeben.
 
address@hidden address@hidden
address@hidden address@hidden
address@hidden address@hidden
-Download code from the specified @var{url}, at the given @var{commit} (a valid
-Git commit ID represented as a hexadecimal string), or @var{branch}.
address@hidden address@hidden
address@hidden address@hidden
address@hidden address@hidden
+Download code from the specified @var{url}, at the given @var{commit} (a
+valid Git commit ID represented as a hexadecimal string), or @var{branch}.
 
 @cindex @file{channels.scm}, configuration file
 @cindex configuration file for channels
@@ -2864,22 +3065,22 @@ configuration in the @file{~/.config/guix/channels.scm} 
file or using the
 @item address@hidden
 @itemx -C @var{file}
 Read the list of channels from @var{file} instead of
address@hidden/.config/guix/channels.scm}.  @var{file} must contain Scheme code 
that
-evaluates to a list of channel objects.  @xref{Channels}, for more
address@hidden/.config/guix/channels.scm}.  @var{file} must contain Scheme code
+that evaluates to a list of channel objects.  @xref{Channels}, for more
 information.
 
address@hidden address@hidden
address@hidden -l address@hidden
-List all the generations of @file{~/.config/guix/current} or, if @var{pattern}
-is provided, the subset of generations that match @var{pattern}.
-The syntax of @var{pattern} is the same as with @code{guix package
---list-generations} (@pxref{Invoking guix package}).
address@hidden address@hidden
address@hidden -l address@hidden
+List all the generations of @file{~/.config/guix/current} or, if
address@hidden is provided, the subset of generations that match
address@hidden  The syntax of @var{pattern} is the same as with @code{guix
+package --list-generations} (@pxref{Aufruf von guix package}).
 
 @ref{Invoking guix describe}, for a way to display information about the
 current generation only.
 
address@hidden address@hidden
address@hidden -p @var{profile}
address@hidden address@hidden
address@hidden -p @var{Profil}
 Use @var{profile} instead of @file{~/.config/guix/current}.
 
 @item --bootstrap
@@ -2888,12 +3089,12 @@ useful to Guix developers.
 @end table
 
 The @dfn{channel} mechanism allows you to instruct @command{guix pull} which
-repository and branch to pull from, as well as @emph{additional} repositories
-containing package modules that should be deployed.  @xref{Channels}, for more
-information.
+repository and branch to pull from, as well as @emph{additional}
+repositories containing package modules that should be deployed.
address@hidden, for more information.
 
 In addition, @command{guix pull} supports all the common build options
-(@pxref{Common Build Options}).
+(@pxref{Gemeinsame Erstellungsoptionen}).
 
 @node Channels
 @section Channels
@@ -2904,21 +3105,22 @@ In addition, @command{guix pull} supports all the 
common build options
 @cindex @command{guix pull}, configuration file
 @cindex configuration of @command{guix pull}
 Guix and its package collection are updated by running @command{guix pull}
-(@pxref{Invoking guix pull}).  By default @command{guix pull} downloads and
+(@pxref{Aufruf von guix pull}).  By default @command{guix pull} downloads and
 deploys Guix itself from the official address@hidden repository.  This can be
 customized by defining @dfn{channels} in the
address@hidden/.config/guix/channels.scm} file.  A channel specifies a URL and 
branch
-of a Git repository to be deployed, and @command{guix pull} can be instructed
-to pull from one or more channels.  In other words, channels can be used to
address@hidden and to @emph{extend} Guix, as we will see below.
address@hidden/.config/guix/channels.scm} file.  A channel specifies a URL and
+branch of a Git repository to be deployed, and @command{guix pull} can be
+instructed to pull from one or more channels.  In other words, channels can
+be used to @emph{customize} and to @emph{extend} Guix, as we will see below.
 
 @subsection Using a Custom Guix Channel
 
-The channel called @code{guix} specifies where Guix itself---its command-line
-tools as well as its package collection---should be downloaded.  For instance,
-suppose you want to update from your own copy of the Guix repository at
address@hidden, and specifically the @code{super-hacks} branch, you can
-write in @code{~/.config/guix/channels.scm} this specification:
+The channel called @code{guix} specifies where Guix itself---its
+command-line tools as well as its package collection---should be
+downloaded.  For instance, suppose you want to update from your own copy of
+the Guix repository at @code{example.org}, and specifically the
address@hidden branch, you can write in
address@hidden/.config/guix/channels.scm} this specification:
 
 @lisp
 ;; Tell 'guix pull' to use my own repo.
@@ -2929,8 +3131,8 @@ write in @code{~/.config/guix/channels.scm} this 
specification:
 @end lisp
 
 @noindent
-From there on, @command{guix pull} will fetch code from the @code{super-hacks}
-branch of the repository at @code{example.org}.
+From there on, @command{guix pull} will fetch code from the
address@hidden branch of the repository at @code{example.org}.
 
 @subsection Specifying Additional Channels
 
@@ -2941,43 +3143,45 @@ You can also specify @emph{additional channels} to pull 
from.  Let's say you
 have a bunch of custom package variants or personal packages that you think
 would make little sense to contribute to the Guix project, but would like to
 have these packages transparently available to you at the command line.  You
-would first write modules containing those package definitions (@pxref{Package
-Modules}), maintain them in a Git repository, and then you and anyone else can
-use it as an additional channel to get packages from.  Neat, no?
+would first write modules containing those package definitions
+(@pxref{Paketmodule}), maintain them in a Git repository, and then you
+and anyone else can use it as an additional channel to get packages from.
+Neat, no?
 
 @c What follows stems from discussions at
 @c <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=22629#134> as well as
 @c earlier discussions on address@hidden
 @quotation Warning
 Before you, dear user, shout---``woow this is @emph{soooo coool}!''---and
-publish your personal channel to the world, we would like to share a few words
-of caution:
+publish your personal channel to the world, we would like to share a few
+words of caution:
 
 @itemize
 @item
 Before publishing a channel, please consider contributing your package
-definitions to Guix proper (@pxref{Contributing}).  Guix as a project is open
-to free software of all sorts, and packages in Guix proper are readily
+definitions to Guix proper (@pxref{Mitwirken}).  Guix as a project is
+open to free software of all sorts, and packages in Guix proper are readily
 available to all Guix users and benefit from the project's quality assurance
 process.
 
 @item
 When you maintain package definitions outside Guix, we, Guix developers,
 consider that @emph{the compatibility burden is on you}.  Remember that
-package modules and package definitions are just Scheme code that uses various
-programming interfaces (APIs).  We want to remain free to change these APIs to
-keep improving Guix, possibly in ways that break your channel.  We never
-change APIs gratuitously, but we will @emph{not} commit to freezing APIs
-either.
+package modules and package definitions are just Scheme code that uses
+various programming interfaces (APIs).  We want to remain free to change
+these APIs to keep improving Guix, possibly in ways that break your
+channel.  We never change APIs gratuitously, but we will @emph{not} commit
+to freezing APIs either.
 
 @item
-Corollary: if you're using an external channel and that channel breaks, please
address@hidden the issue to the channel authors}, not to the Guix project.
+Corollary: if you're using an external channel and that channel breaks,
+please @emph{report the issue to the channel authors}, not to the Guix
+project.
 @end itemize
 
-You've been warned!  Having said this, we believe external channels are a
-practical way to exert your freedom to augment Guix' package collection and to
-share your improvements, which are basic tenets of
+You've been warned! Having said this, we believe external channels are a
+practical way to exert your freedom to augment Guix' package collection and
+to share your improvements, which are basic tenets of
 @uref{https://www.gnu.org/philosophy/free-sw.html, free software}.  Please
 email us at @email{guix-devel@@gnu.org} if you'd like to discuss this.
 @end quotation
@@ -2997,13 +3201,13 @@ channel(s):
 @end lisp
 
 @noindent
-Note that the snippet above is (as always!) Scheme code; we use @code{cons} to
-add a channel the list of channels that the variable @code{%default-channels}
-is bound to (@pxref{Pairs, @code{cons} and lists,, guile, GNU Guile Reference
-Manual}).  With this file in place, @command{guix pull} builds not only Guix
-but also the package modules from your own repository.  The result in
address@hidden/.config/guix/current} is the union of Guix with your own package
-modules:
+Note that the snippet above is (as always!) Scheme code; we use @code{cons}
+to add a channel the list of channels that the variable
address@hidden is bound to (@pxref{Pairs, @code{cons} and lists,,
+guile, GNU Guile Reference Manual}).  With this file in place, @command{guix
+pull} builds not only Guix but also the package modules from your own
+repository.  The result in @file{~/.config/guix/current} is the union of
+Guix with your own package modules:
 
 @example
 $ guix pull --list-generations
@@ -3022,21 +3226,22 @@ Generation 19   Aug 27 2018 16:20:48
 @end example
 
 @noindent
-The output of @command{guix pull} above shows that address@hidden includes
-both Guix and packages from the @code{my-personal-packages} channel.  Among
-the new and upgraded packages that are listed, some like @code{my-gimp} and
address@hidden might come from
address@hidden, while others come from the Guix default channel.
+The output of @command{guix pull} above shows that address@hidden
+includes both Guix and packages from the @code{my-personal-packages}
+channel.  Among the new and upgraded packages that are listed, some like
address@hidden and @code{my-emacs-with-cool-features} might come from
address@hidden, while others come from the Guix default
+channel.
 
 @subsection Replicating Guix
 
 @cindex pinning, channels
 @cindex replicating Guix
 @cindex reproducibility, of Guix
-The @command{guix pull --list-generations} output above shows precisely which
-commits were used to build this instance of Guix.  We can thus replicate it,
-say, on another machine, by providing a channel specification in
address@hidden/.config/guix/channels.scm} that is ``pinned'' to these commits:
+The @command{guix pull --list-generations} output above shows precisely
+which commits were used to build this instance of Guix.  We can thus
+replicate it, say, on another machine, by providing a channel specification
+in @file{~/.config/guix/channels.scm} that is ``pinned'' to these commits:
 
 @lisp
 ;; Deploy specific commits of my channels of interest.
@@ -3053,12 +3258,12 @@ say, on another machine, by providing a channel 
specification in
 The @command{guix describe --format=channels} command can even generate this
 list of channels directly (@pxref{Invoking guix describe}).
 
-At this point the two machines run the @emph{exact same Guix}, with access to
-the @emph{exact same packages}.  The output of @command{guix build gimp} on
-one machine will be exactly the same, bit for bit, as the output of the same
-command on the other machine.  It also means both machines have access to all
-the source code of Guix and, transitively, to all the source code of every
-package it defines.
+At this point the two machines run the @emph{exact same Guix}, with access
+to the @emph{exact same packages}.  The output of @command{guix build gimp}
+on one machine will be exactly the same, bit for bit, as the output of the
+same command on the other machine.  It also means both machines have access
+to all the source code of Guix and, transitively, to all the source code of
+every package it defines.
 
 This gives you super powers, allowing you to track the provenance of binary
 artifacts with very fine grain, and to reproduce software environments at
@@ -3069,7 +3274,7 @@ will---some sort of ``meta reproducibility'' 
capabilities, if you will.
 @section Inferiors
 
 @c TODO: Remove this once we're more confident about API stability.
address@hidden Note
address@hidden Anmerkung
 The functionality described here is a ``technology preview'' as of version
 @value{VERSION}.  As such, the interface is subject to change.
 @end quotation
@@ -3082,21 +3287,22 @@ Guix @dfn{inferiors} allow you to achieve that by 
composing different Guix
 revisions in arbitrary ways.
 
 @cindex inferior packages
-Technically, an ``inferior'' is essentially a separate Guix process connected
-to your main Guix process through a REPL (@pxref{Invoking guix repl}).  The
address@hidden(guix inferior)} module allows you to create inferiors and to
-communicate with them.  It also provides a high-level interface to browse and
-manipulate the packages that an inferior address@hidden packages}.
-
-When combined with channels (@pxref{Channels}), inferiors provide a simple way
-to interact with a separate revision of Guix.  For example, let's assume you
-want to install in your profile the current @code{guile} package, along with
-the @code{guile-json} as it existed in an older revision of Guix---perhaps
-because the newer @code{guile-json} has an incompatible API and you want to
-run your code against the old address@hidden  To do that, you could write a 
manifest for
-use by @code{guix package --manifest} (@pxref{Invoking guix package}); in that
-manifest, you would create an inferior for that old Guix revision you care
-about, and you would look up the @code{guile-json} package in the inferior:
+Technically, an ``inferior'' is essentially a separate Guix process
+connected to your main Guix process through a REPL (@pxref{Invoking guix
+repl}).  The @code{(guix inferior)} module allows you to create inferiors
+and to communicate with them.  It also provides a high-level interface to
+browse and manipulate the packages that an inferior address@hidden
+packages}.
+
+When combined with channels (@pxref{Channels}), inferiors provide a simple
+way to interact with a separate revision of Guix.  For example, let's assume
+you want to install in your profile the current @code{guile} package, along
+with the @code{guile-json} as it existed in an older revision of
+Guix---perhaps because the newer @code{guile-json} has an incompatible API
+and you want to run your code against the old address@hidden  To do that, you 
could
+write a manifest for use by @code{guix package --manifest} (@pxref{Aufruf von 
guix package}); in that manifest, you would create an inferior for that old
+Guix revision you care about, and you would look up the @code{guile-json}
+package in the inferior:
 
 @lisp
 (use-modules (guix inferior) (guix channels)
@@ -3123,27 +3329,26 @@ about, and you would look up the @code{guile-json} 
package in the inferior:
 @end lisp
 
 On its first run, @command{guix package --manifest} might have to build the
-channel you specified before it can create the inferior; subsequent runs will
-be much faster because the Guix revision will be cached.
+channel you specified before it can create the inferior; subsequent runs
+will be much faster because the Guix revision will be cached.
 
-The @code{(guix inferior)} module provides the following procedures to open an
-inferior:
+The @code{(guix inferior)} module provides the following procedures to open
+an inferior:
 
 @deffn {Scheme Procedure} inferior-for-channels @var{channels} @
-   [#:cache-directory] [#:ttl]
-Return an inferior for @var{channels}, a list of channels.  Use the cache at
address@hidden, where entries can be reclaimed after @var{ttl} seconds.
-This procedure opens a new connection to the build daemon.
+   [#:cache-directory] [#:ttl] Return an inferior for @var{channels}, a list of
+channels.  Use the cache at @var{cache-directory}, where entries can be
+reclaimed after @var{ttl} seconds.  This procedure opens a new connection to
+the build daemon.
 
 As a side effect, this procedure may build or substitute binaries for
 @var{channels}, which can take time.
 @end deffn
 
 @deffn {Scheme Procedure} open-inferior @var{directory} @
-  [#:command "bin/guix"]
-Open the inferior Guix in @var{directory}, running
address@hidden@var{directory}/@var{command} repl} or equivalent.  Return 
@code{#f} if
-the inferior could not be launched.
+  [#:command "bin/guix"] Open the inferior Guix in @var{directory}, running
address@hidden@var{directory}/@var{command} repl} or equivalent.  Return 
@code{#f}
+if the inferior could not be launched.
 @end deffn
 
 @cindex inferior packages
@@ -3155,10 +3360,10 @@ Return the list of packages known to @var{inferior}.
 @end deffn
 
 @deffn {Scheme Procedure} lookup-inferior-packages @var{inferior} @var{name} @
-   address@hidden
-Return the sorted list of inferior packages matching @var{name} in
address@hidden, with highest version numbers first.  If @var{version} is true,
-return only packages with a version number prefixed by @var{version}.
+   address@hidden Return the sorted list of inferior packages matching
address@hidden in @var{inferior}, with highest version numbers first.  If
address@hidden is true, return only packages with a version number prefixed
+by @var{version}.
 @end deffn
 
 @deffn {Scheme Procedure} inferior-package? @var{obj}
@@ -3179,15 +3384,15 @@ Return true if @var{obj} is an inferior package.
 @deffnx {Scheme Procedure} inferior-package-transitive-native-search-paths 
@var{package}
 @deffnx {Scheme Procedure} inferior-package-search-paths @var{package}
 These procedures are the counterpart of package record accessors
-(@pxref{package Reference}).  Most of them work by querying the inferior
+(@pxref{„package“-Referenz}).  Most of them work by querying the inferior
 @var{package} comes from, so the inferior must still be live when you call
 these procedures.
 @end deffn
 
 Inferior packages can be used transparently like any other package or
-file-like object in G-expressions (@pxref{G-Expressions}).  They are also
+file-like object in G-expressions (@pxref{G-Ausdrücke}).  They are also
 transparently handled by the @code{packages->manifest} procedure, which is
-commonly use in manifests (@pxref{Invoking guix package, the
+commonly use in manifests (@pxref{Aufruf von guix package, the
 @option{--manifest} option of @command{guix package}}).  Thus you can insert
 an inferior package pretty much anywhere you would insert a regular package:
 in manifests, in the @code{packages} field of your @code{operating-system}
@@ -3196,19 +3401,19 @@ declaration, and so on.
 @node Invoking guix describe
 @section Invoking @command{guix describe}
 
address@hidden reproducibility
address@hidden Reproduzierbarkeit
 @cindex replicating Guix
 Often you may want to answer questions like: ``Which revision of Guix am I
-using?'' or ``Which channels am I using?''  This is useful information in many
-situations: if you want to @emph{replicate} an environment on a different
-machine or user account, if you want to report a bug or to determine what
-change in the channels you are using caused it, or if you want to record your
-system state for reproducibility purposes.  The @command{guix describe}
-command answers these questions.
+using?'' or ``Which channels am I using?'' This is useful information in
+many situations: if you want to @emph{replicate} an environment on a
+different machine or user account, if you want to report a bug or to
+determine what change in the channels you are using caused it, or if you
+want to record your system state for reproducibility purposes.  The
address@hidden describe} command answers these questions.
 
-When run from a @command{guix pull}ed @command{guix}, @command{guix describe}
-displays the channel(s) that it was built from, including their repository URL
-and commit IDs (@pxref{Channels}):
+When run from a @command{guix pull}ed @command{guix}, @command{guix
+describe} displays the channel(s) that it was built from, including their
+repository URL and commit IDs (@pxref{Channels}):
 
 @example
 $ guix describe
@@ -3221,14 +3426,15 @@ Generation 10   Sep 03 2018 17:32:44    (current)
 
 If you're familiar with the Git version control system, this is similar in
 spirit to @command{git describe}; the output is also similar to that of
address@hidden pull --list-generations}, but limited to the current generation
-(@pxref{Invoking guix pull, the @option{--list-generations} option}).  Because
-the Git commit ID shown above unambiguously refers to a snapshot of Guix, this
-information is all it takes to describe the revision of Guix you're using, and
-also to replicate it.
address@hidden pull --list-generations}, but limited to the current
+generation (@pxref{Aufruf von guix pull, the @option{--list-generations}
+option}).  Because the Git commit ID shown above unambiguously refers to a
+snapshot of Guix, this information is all it takes to describe the revision
+of Guix you're using, and also to replicate it.
 
-To make it easier to replicate Guix, @command{guix describe} can also be asked
-to return a list of channels instead of the human-readable description above:
+To make it easier to replicate Guix, @command{guix describe} can also be
+asked to return a list of channels instead of the human-readable description
+above:
 
 @example
 $ guix describe -f channels
@@ -3242,10 +3448,10 @@ $ guix describe -f channels
 @noindent
 You can save this to a file and feed it to @command{guix pull -C} on some
 other machine or at a later point in time, which will instantiate @emph{this
-exact Guix revision} (@pxref{Invoking guix pull, the @option{-C} option}).
-From there on, since you're able to deploy the same revision of Guix, you can
-just as well @emph{replicate a complete software environment}.  We humbly
-think that this is @emph{awesome}, and we hope you'll like it too!
+exact Guix revision} (@pxref{Aufruf von guix pull, the @option{-C} option}).
+From there on, since you're able to deploy the same revision of Guix, you
+can just as well @emph{replicate a complete software environment}.  We
+humbly think that this is @emph{awesome}, and we hope you'll like it too!
 
 The details of the options supported by @command{guix describe} are as
 follows:
@@ -3260,23 +3466,22 @@ Produce output in the specified @var{format}, one of:
 produce human-readable output;
 @item channels
 produce a list of channel specifications that can be passed to @command{guix
-pull -C} or installed as @file{~/.config/guix/channels.scm} (@pxref{Invoking
-guix pull}).
+pull -C} or installed as @file{~/.config/guix/channels.scm} (@pxref{Aufruf von 
guix pull}).
 @end table
 @end table
 
address@hidden Invoking guix pack
address@hidden Aufruf von guix pack
 @section Invoking @command{guix pack}
 
-Occasionally you want to pass software to people who are not (yet!)
-lucky enough to be using Guix.  You'd tell them to run @command{guix
-package -i @var{something}}, but that's not possible in this case.  This
-is where @command{guix pack} comes in.
+Occasionally you want to pass software to people who are not (yet!)  lucky
+enough to be using Guix.  You'd tell them to run @command{guix package -i
address@hidden, but that's not possible in this case.  This is where
address@hidden pack} comes in.
 
address@hidden Note
-If you are looking for ways to exchange binaries among machines that
-already run Guix, @pxref{Invoking guix copy}, @ref{Invoking guix
-publish}, and @ref{Invoking guix archive}.
address@hidden Anmerkung
+If you are looking for ways to exchange binaries among machines that already
+run Guix, @pxref{Aufruf von guix copy}, @ref{Aufruf von guix publish}, and
address@hidden von guix archive}.
 @end quotation
 
 @cindex pack
@@ -3284,13 +3489,13 @@ publish}, and @ref{Invoking guix archive}.
 @cindex application bundle
 @cindex software bundle
 The @command{guix pack} command creates a shrink-wrapped @dfn{pack} or
address@hidden bundle}: it creates a tarball or some other archive
-containing the binaries of the software you're interested in, and all
-its dependencies.  The resulting archive can be used on any machine that
-does not have Guix, and people can run the exact same binaries as those
-you have with Guix.  The pack itself is created in a bit-reproducible
-fashion, so anyone can verify that it really contains the build results
-that you pretend to be shipping.
address@hidden bundle}: it creates a tarball or some other archive containing
+the binaries of the software you're interested in, and all its
+dependencies.  The resulting archive can be used on any machine that does
+not have Guix, and people can run the exact same binaries as those you have
+with Guix.  The pack itself is created in a bit-reproducible fashion, so
+anyone can verify that it really contains the build results that you pretend
+to be shipping.
 
 For example, to create a bundle containing Guile, Emacs, Geiser, and all
 their dependencies, you can run:
@@ -3301,17 +3506,16 @@ $ guix pack guile emacs geiser
 /gnu/store/@dots{}-pack.tar.gz
 @end example
 
-The result here is a tarball containing a @file{/gnu/store} directory
-with all the relevant packages.  The resulting tarball contains a
address@hidden with the three packages of interest; the profile is the
-same as would be created by @command{guix package -i}.  It is this
-mechanism that is used to create Guix's own standalone binary tarball
-(@pxref{Binary Installation}).
+The result here is a tarball containing a @file{/gnu/store} directory with
+all the relevant packages.  The resulting tarball contains a @dfn{profile}
+with the three packages of interest; the profile is the same as would be
+created by @command{guix package -i}.  It is this mechanism that is used to
+create Guix's own standalone binary tarball (@pxref{Aus Binärdatei 
installieren}).
 
 Users of this pack would have to run
address@hidden/gnu/store/@dots{}-profile/bin/guile} to run Guile, which you may
-find inconvenient.  To work around it, you can create, say, a
address@hidden/opt/gnu/bin} symlink to the profile:
address@hidden/gnu/store/@dots{}-profile/bin/guile} to run Guile, which you may 
find
+inconvenient.  To work around it, you can create, say, a @file{/opt/gnu/bin}
+symlink to the profile:
 
 @example
 guix pack -S /opt/gnu/bin=bin guile emacs geiser
@@ -3321,17 +3525,17 @@ guix pack -S /opt/gnu/bin=bin guile emacs geiser
 That way, users can happily type @file{/opt/gnu/bin/guile} and enjoy.
 
 @cindex relocatable binaries, with @command{guix pack}
-What if the recipient of your pack does not have root privileges on
-their machine, and thus cannot unpack it in the root file system?  In
-that case, you will want to use the @code{--relocatable} option (see
-below).  This option produces @dfn{relocatable binaries}, meaning they
-they can be placed anywhere in the file system hierarchy: in the example
-above, users can unpack your tarball in their home directory and
-directly run @file{./opt/gnu/bin/guile}.
+What if the recipient of your pack does not have root privileges on their
+machine, and thus cannot unpack it in the root file system? In that case,
+you will want to use the @code{--relocatable} option (see below).  This
+option produces @dfn{relocatable binaries}, meaning they they can be placed
+anywhere in the file system hierarchy: in the example above, users can
+unpack your tarball in their home directory and directly run
address@hidden/opt/gnu/bin/guile}.
 
 @cindex Docker, build an image with guix pack
-Alternatively, you can produce a pack in the Docker image format using
-the following command:
+Alternatively, you can produce a pack in the Docker image format using the
+following command:
 
 @example
 guix pack -f docker guile emacs geiser
@@ -3387,16 +3591,16 @@ procfs.
 @item --relocatable
 @itemx -R
 Produce @dfn{relocatable binaries}---i.e., binaries that can be placed
-anywhere in the file system hierarchy and run from there.  For example,
-if you create a pack containing Bash with:
+anywhere in the file system hierarchy and run from there.  For example, if
+you create a pack containing Bash with:
 
 @example
 guix pack -R -S /mybin=bin bash
 @end example
 
 @noindent
-... you can copy that pack to a machine that lacks Guix, and from your
-home directory as a normal user, run:
+... you can copy that pack to a machine that lacks Guix, and from your home
+directory as a normal user, run:
 
 @example
 tar xf pack.tar.gz
@@ -3405,48 +3609,46 @@ tar xf pack.tar.gz
 
 @noindent
 In that shell, if you type @code{ls /gnu/store}, you'll notice that
address@hidden/gnu/store} shows up and contains all the dependencies of
address@hidden, even though the machine actually lacks @file{/gnu/store}
-altogether!  That is probably the simplest way to deploy Guix-built
-software on a non-Guix machine.
-
-There's a gotcha though: this technique relies on the @dfn{user
-namespace} feature of the kernel Linux, which allows unprivileged users
-to mount or change root.  Old versions of Linux did not support it, and
-some GNU/Linux distributions turn it off; on these systems, programs
-from the pack @emph{will fail to run}, unless they are unpacked in the
-root file system.
address@hidden/gnu/store} shows up and contains all the dependencies of 
@code{bash},
+even though the machine actually lacks @file{/gnu/store} altogether! That is
+probably the simplest way to deploy Guix-built software on a non-Guix
+machine.
+
+There's a gotcha though: this technique relies on the @dfn{user namespace}
+feature of the kernel Linux, which allows unprivileged users to mount or
+change root.  Old versions of Linux did not support it, and some GNU/Linux
+distributions turn it off; on these systems, programs from the pack
address@hidden fail to run}, unless they are unpacked in the root file system.
 
 @item address@hidden
 @itemx -e @var{expr}
 Consider the package @var{expr} evaluates to.
 
-This has the same purpose as the same-named option in @command{guix
-build} (@pxref{Additional Build Options, @code{--expression} in
address@hidden build}}).
+This has the same purpose as the same-named option in @command{guix build}
+(@pxref{Zusätzliche Erstellungsoptionen, @code{--expression} in @command{guix
+build}}).
 
address@hidden address@hidden
address@hidden -m @var{file}
address@hidden address@hidden
address@hidden -m @var{Datei}
 Use the packages contained in the manifest object returned by the Scheme
 code in @var{file}.
 
 This has a similar purpose as the same-named option in @command{guix
-package} (@pxref{profile-manifest, @option{--manifest}}) and uses the
-same manifest files.  It allows you to define a collection of packages
-once and use it both for creating profiles and for creating archives
-for use on machines that do not have Guix installed.  Note that you can
-specify @emph{either} a manifest file @emph{or} a list of packages,
-but not both.
-
address@hidden address@hidden
+package} (@pxref{profile-manifest, @option{--manifest}}) and uses the same
+manifest files.  It allows you to define a collection of packages once and
+use it both for creating profiles and for creating archives for use on
+machines that do not have Guix installed.  Note that you can specify
address@hidden a manifest file @emph{or} a list of packages, but not both.
+
address@hidden address@hidden
 @itemx -s @var{system}
-Attempt to build for @var{system}---e.g., @code{i686-linux}---instead of
-the system type of the build host.
+Attempt to build for @var{system}---e.g., @code{i686-linux}---instead of the
+system type of the build host.
 
 @item address@hidden
 @cindex cross-compilation
-Cross-build for @var{triplet}, which must be a valid GNU triplet, such
-as @code{"mips64el-linux-gnu"} (@pxref{Specifying target triplets, GNU
+Cross-build for @var{triplet}, which must be a valid GNU triplet, such as
address@hidden"mips64el-linux-gnu"} (@pxref{Specifying target triplets, GNU
 configuration triplets,, autoconf, Autoconf}).
 
 @item address@hidden
@@ -3459,50 +3661,48 @@ Compress the resulting tarball using @var{tool}---one 
of @code{gzip},
 Add the symlinks specified by @var{spec} to the pack.  This option can
 appear several times.
 
address@hidden has the form @address@hidden@var{target}}, where
address@hidden is the symlink that will be created and @var{target} is the
-symlink target.
address@hidden has the form @address@hidden@var{target}}, where @var{source}
+is the symlink that will be created and @var{target} is the symlink target.
 
 For instance, @code{-S /opt/gnu/bin=bin} creates a @file{/opt/gnu/bin}
 symlink pointing to the @file{bin} sub-directory of the profile.
 
 @item --localstatedir
-Include the ``local state directory'', @file{/var/guix}, in the
-resulting pack.
+Include the ``local state directory'', @file{/var/guix}, in the resulting
+pack.
 
address@hidden/var/guix} contains the store database (@pxref{The Store}) as well
-as garbage-collector roots (@pxref{Invoking guix gc}).  Providing it in
-the pack means that the store is ``complete'' and manageable by Guix;
-not providing it pack means that the store is ``dead'': items cannot be
-added to it or removed from it after extraction of the pack.
address@hidden/var/guix} contains the store database (@pxref{Der Store}) as 
well as
+garbage-collector roots (@pxref{Aufruf von guix gc}).  Providing it in the
+pack means that the store is ``complete'' and manageable by Guix; not
+providing it pack means that the store is ``dead'': items cannot be added to
+it or removed from it after extraction of the pack.
 
 One use case for this is the Guix self-contained binary tarball
-(@pxref{Binary Installation}).
+(@pxref{Aus Binärdatei installieren}).
 
 @item --bootstrap
-Use the bootstrap binaries to build the pack.  This option is only
-useful to Guix developers.
+Use the bootstrap binaries to build the pack.  This option is only useful to
+Guix developers.
 @end table
 
 In addition, @command{guix pack} supports all the common build options
-(@pxref{Common Build Options}) and all the package transformation
-options (@pxref{Package Transformation Options}).
+(@pxref{Gemeinsame Erstellungsoptionen}) and all the package transformation 
options
+(@pxref{Paketumwandlungsoptionen}).
 
 
address@hidden Invoking guix archive
address@hidden Aufruf von guix archive
 @section Invoking @command{guix archive}
 
 @cindex @command{guix archive}
 @cindex archive
-The @command{guix archive} command allows users to @dfn{export} files
-from the store into a single archive, and to later @dfn{import} them on
-a machine that runs Guix.
-In particular, it allows store files to be transferred from one machine
-to the store on another machine.
+The @command{guix archive} command allows users to @dfn{export} files from
+the store into a single archive, and to later @dfn{import} them on a machine
+that runs Guix.  In particular, it allows store files to be transferred from
+one machine to the store on another machine.
 
address@hidden Note
address@hidden Anmerkung
 If you're looking for a way to produce archives in a format suitable for
-tools other than Guix, @pxref{Invoking guix pack}.
+tools other than Guix, @pxref{Aufruf von guix pack}.
 @end quotation
 
 @cindex exporting store items
@@ -3513,8 +3713,7 @@ guix archive --export @var{options} 
@var{specifications}...
 @end example
 
 @var{specifications} may be either store file names or package
-specifications, as for @command{guix package} (@pxref{Invoking guix
-package}).  For instance, the following command creates an archive
+specifications, as for @command{guix package} (@pxref{Aufruf von guix 
package}).  For instance, the following command creates an archive
 containing the @code{gui} output of the @code{git} package and the main
 output of @code{emacs}:
 
@@ -3524,18 +3723,18 @@ guix archive --export git:gui /gnu/store/...-emacs-24.3 
> great.nar
 
 If the specified packages are not built yet, @command{guix archive}
 automatically builds them.  The build process may be controlled with the
-common build options (@pxref{Common Build Options}).
+common build options (@pxref{Gemeinsame Erstellungsoptionen}).
 
-To transfer the @code{emacs} package to a machine connected over SSH,
-one would run:
+To transfer the @code{emacs} package to a machine connected over SSH, one
+would run:
 
 @example
 guix archive --export -r emacs | ssh the-machine guix archive --import
 @end example
 
 @noindent
-Similarly, a complete user profile may be transferred from one machine
-to another like this:
+Similarly, a complete user profile may be transferred from one machine to
+another like this:
 
 @example
 guix archive --export -r $(readlink -f ~/.guix-profile) | \
@@ -3543,31 +3742,30 @@ guix archive --export -r $(readlink -f ~/.guix-profile) 
| \
 @end example
 
 @noindent
-However, note that, in both examples, all of @code{emacs} and the
-profile as well as all of their dependencies are transferred (due to
address@hidden), regardless of what is already available in the store on the
-target machine.  The @code{--missing} option can help figure out which
-items are missing from the target store.  The @command{guix copy}
-command simplifies and optimizes this whole process, so this is probably
-what you should use in this case (@pxref{Invoking guix copy}).
+However, note that, in both examples, all of @code{emacs} and the profile as
+well as all of their dependencies are transferred (due to @code{-r}),
+regardless of what is already available in the store on the target machine.
+The @code{--missing} option can help figure out which items are missing from
+the target store.  The @command{guix copy} command simplifies and optimizes
+this whole process, so this is probably what you should use in this case
+(@pxref{Aufruf von guix copy}).
 
 @cindex nar, archive format
 @cindex normalized archive (nar)
-Archives are stored in the ``normalized archive'' or ``nar'' format, which is
-comparable in spirit to `tar', but with differences
-that make it more appropriate for our purposes.  First, rather than
-recording all Unix metadata for each file, the nar format only mentions
-the file type (regular, directory, or symbolic link); Unix permissions
-and owner/group are dismissed.  Second, the order in which directory
-entries are stored always follows the order of file names according to
-the C locale collation order.  This makes archive production fully
-deterministic.
-
-When exporting, the daemon digitally signs the contents of the archive,
-and that digital signature is appended.  When importing, the daemon
-verifies the signature and rejects the import in case of an invalid
-signature or if the signing key is not authorized.
+Archives are stored in the ``normalized archive'' or ``nar'' format, which
+is comparable in spirit to `tar', but with differences that make it more
+appropriate for our purposes.  First, rather than recording all Unix
+metadata for each file, the nar format only mentions the file type (regular,
+directory, or symbolic link); Unix permissions and owner/group are
+dismissed.  Second, the order in which directory entries are stored always
+follows the order of file names according to the C locale collation order.
+This makes archive production fully deterministic.
+
 @c FIXME: Add xref to daemon doc about signatures.
+When exporting, the daemon digitally signs the contents of the archive, and
+that digital signature is appended.  When importing, the daemon verifies the
+signature and rejects the import in case of an invalid signature or if the
+signing key is not authorized.
 
 The main options are:
 
@@ -3581,44 +3779,43 @@ Dependencies are @emph{not} included in the output, 
unless
 
 @item -r
 @itemx --recursive
-When combined with @code{--export}, this instructs @command{guix
-archive} to include dependencies of the given items in the archive.
-Thus, the resulting archive is self-contained: it contains the closure
-of the exported store items.
+When combined with @code{--export}, this instructs @command{guix archive} to
+include dependencies of the given items in the archive.  Thus, the resulting
+archive is self-contained: it contains the closure of the exported store
+items.
 
 @item --import
-Read an archive from the standard input, and import the files listed
-therein into the store.  Abort if the archive has an invalid digital
-signature, or if it is signed by a public key not among the authorized
-keys (see @code{--authorize} below.)
+Read an archive from the standard input, and import the files listed therein
+into the store.  Abort if the archive has an invalid digital signature, or
+if it is signed by a public key not among the authorized keys (see
address@hidden below.)
 
 @item --missing
-Read a list of store file names from the standard input, one per line,
-and write on the standard output the subset of these files missing from
-the store.
+Read a list of store file names from the standard input, one per line, and
+write on the standard output the subset of these files missing from the
+store.
 
 @item address@hidden
 @cindex signing, archives
 Generate a new key pair for the daemon.  This is a prerequisite before
 archives can be exported with @code{--export}.  Note that this operation
-usually takes time, because it needs to gather enough entropy to
-generate the key pair.
+usually takes time, because it needs to gather enough entropy to generate
+the key pair.
 
 The generated key pair is typically stored under @file{/etc/guix}, in
address@hidden (public key) and @file{signing-key.sec} (private
-key, which must be kept secret.)  When @var{parameters} is omitted,
-an ECDSA key using the Ed25519 curve is generated, or, for Libgcrypt
-versions before 1.6.0, it is a 4096-bit RSA key.
-Alternatively, @var{parameters} can specify
address@hidden parameters suitable for Libgcrypt (@pxref{General
-public-key related Functions, @code{gcry_pk_genkey},, gcrypt, The
-Libgcrypt Reference Manual}).
address@hidden (public key) and @file{signing-key.sec} (private key,
+which must be kept secret.)  When @var{parameters} is omitted, an ECDSA key
+using the Ed25519 curve is generated, or, for Libgcrypt versions before
+1.6.0, it is a 4096-bit RSA key.  Alternatively, @var{parameters} can
+specify @code{genkey} parameters suitable for Libgcrypt (@pxref{General
+public-key related Functions, @code{gcry_pk_genkey},, gcrypt, The Libgcrypt
+Reference Manual}).
 
 @item --authorize
 @cindex authorizing, archives
-Authorize imports signed by the public key passed on standard input.
-The public key must be in ``s-expression advanced format''---i.e., the
-same format as the @file{signing-key.pub} file.
+Authorize imports signed by the public key passed on standard input.  The
+public key must be in ``s-expression advanced format''---i.e., the same
+format as the @file{signing-key.pub} file.
 
 The list of authorized keys is kept in the human-editable file
 @file{/etc/guix/acl}.  The file contains
@@ -3630,11 +3827,11 @@ s-expressions''} and is structured as an access-control 
list in the
 @item address@hidden
 @itemx -x @var{directory}
 Read a single-item archive as served by substitute servers
-(@pxref{Substitutes}) and extract it to @var{directory}.  This is a
+(@pxref{Substitute}) and extract it to @var{directory}.  This is a
 low-level operation needed in only very narrow use cases; see below.
 
-For example, the following command extracts the substitute for Emacs
-served by @code{hydra.gnu.org} to @file{/tmp/emacs}:
+For example, the following command extracts the substitute for Emacs served
+by @code{hydra.gnu.org} to @file{/tmp/emacs}:
 
 @example
 $ wget -O - \
@@ -3642,63 +3839,62 @@ $ wget -O - \
   | bunzip2 | guix archive -x /tmp/emacs
 @end example
 
-Single-item archives are different from multiple-item archives produced
-by @command{guix archive --export}; they contain a single store item,
-and they do @emph{not} embed a signature.  Thus this operation does
address@hidden signature verification and its output should be considered
-unsafe.
+Single-item archives are different from multiple-item archives produced by
address@hidden archive --export}; they contain a single store item, and they
+do @emph{not} embed a signature.  Thus this operation does @emph{no}
+signature verification and its output should be considered unsafe.
 
-The primary purpose of this operation is to facilitate inspection of
-archive contents coming from possibly untrusted substitute servers.
+The primary purpose of this operation is to facilitate inspection of archive
+contents coming from possibly untrusted substitute servers.
 
 @end table
 
 @c *********************************************************************
address@hidden Programming Interface
address@hidden Programming Interface
address@hidden Programmierschnittstelle
address@hidden Programmierschnittstelle
 
-GNU Guix provides several Scheme programming interfaces (APIs) to
-define, build, and query packages.  The first interface allows users to
-write high-level package definitions.  These definitions refer to
-familiar packaging concepts, such as the name and version of a package,
-its build system, and its dependencies.  These definitions can then be
-turned into concrete build actions.
+GNU Guix provides several Scheme programming interfaces (APIs) to define,
+build, and query packages.  The first interface allows users to write
+high-level package definitions.  These definitions refer to familiar
+packaging concepts, such as the name and version of a package, its build
+system, and its dependencies.  These definitions can then be turned into
+concrete build actions.
 
 Build actions are performed by the Guix daemon, on behalf of users.  In a
 standard setup, the daemon has write access to the store---the
address@hidden/gnu/store} directory---whereas users do not.  The recommended
-setup also has the daemon perform builds in chroots, under a specific
-build users, to minimize interference with the rest of the system.
-
address@hidden derivation
-Lower-level APIs are available to interact with the daemon and the
-store.  To instruct the daemon to perform a build action, users actually
-provide it with a @dfn{derivation}.  A derivation is a low-level
-representation of the build actions to be taken, and the environment in
-which they should occur---derivations are to package definitions what
-assembly is to C programs.  The term ``derivation'' comes from the fact
-that build results @emph{derive} from them.
address@hidden/gnu/store} directory---whereas users do not.  The recommended 
setup
+also has the daemon perform builds in chroots, under a specific build users,
+to minimize interference with the rest of the system.
+
address@hidden Ableitung
+Lower-level APIs are available to interact with the daemon and the store.
+To instruct the daemon to perform a build action, users actually provide it
+with a @dfn{derivation}.  A derivation is a low-level representation of the
+build actions to be taken, and the environment in which they should
+occur---derivations are to package definitions what assembly is to C
+programs.  The term ``derivation'' comes from the fact that build results
address@hidden from them.
 
 This chapter describes all these APIs in turn, starting from high-level
 package definitions.
 
 @menu
-* Defining Packages::           Defining new packages.
-* Build Systems::               Specifying how packages are built.
-* The Store::                   Manipulating the package store.
-* Derivations::                 Low-level interface to package derivations.
-* The Store Monad::             Purely functional interface to the store.
-* G-Expressions::               Manipulating build expressions.
-* Invoking guix repl::          Fiddling with Guix interactively.
+* Pakete definieren::        Wie Sie neue Pakete definieren.
+* Erstellungssysteme::       Angeben, wie Pakete erstellt werden.
+* Der Store::                Den Paket-Store verändern.
+* Ableitungen::              Systemnahe Schnittstelle für Paketableitungen.
+* Die Store-Monade::         Rein funktionale Schnittstelle zum Store.
+* G-Ausdrücke::             Erstellungsausdrücke verarbeiten.
+* Invoking guix repl::       Fiddling with Guix interactively.
 @end menu
 
address@hidden Defining Packages
address@hidden Defining Packages
address@hidden Pakete definieren
address@hidden Pakete definieren
 
 The high-level interface to package definitions is implemented in the
 @code{(guix packages)} and @code{(guix build-system)} modules.  As an
-example, the package definition, or @dfn{recipe}, for the GNU Hello
-package looks like this:
+example, the package definition, or @dfn{recipe}, for the GNU Hello package
+looks like this:
 
 @example
 (define-module (gnu packages hello)
@@ -3729,85 +3925,83 @@ package looks like this:
 @end example
 
 @noindent
-Without being a Scheme expert, the reader may have guessed the meaning
-of the various fields here.  This expression binds the variable
address@hidden to a @code{<package>} object, which is essentially a record
-(@pxref{SRFI-9, Scheme records,, guile, GNU Guile Reference Manual}).
-This package object can be inspected using procedures found in the
address@hidden(guix packages)} module; for instance, @code{(package-name hello)}
+Without being a Scheme expert, the reader may have guessed the meaning of
+the various fields here.  This expression binds the variable @code{hello} to
+a @code{<package>} object, which is essentially a record (@pxref{SRFI-9,
+Scheme records,, guile, GNU Guile Reference Manual}).  This package object
+can be inspected using procedures found in the @code{(guix packages)}
+module; for instance, @code{(package-name hello)}
 address@hidden"hello"}.
 
-With luck, you may be able to import part or all of the definition of
-the package you are interested in from another repository, using the
address@hidden import} command (@pxref{Invoking guix import}).
+With luck, you may be able to import part or all of the definition of the
+package you are interested in from another repository, using the @code{guix
+import} command (@pxref{Aufruf von guix import}).
 
 In the example above, @var{hello} is defined in a module of its own,
address@hidden(gnu packages hello)}.  Technically, this is not strictly
-necessary, but it is convenient to do so: all the packages defined in
-modules under @code{(gnu packages @dots{})} are automatically known to
-the command-line tools (@pxref{Package Modules}).
address@hidden(gnu packages hello)}.  Technically, this is not strictly 
necessary,
+but it is convenient to do so: all the packages defined in modules under
address@hidden(gnu packages @dots{})} are automatically known to the 
command-line
+tools (@pxref{Paketmodule}).
 
 There are a few points worth noting in the above package definition:
 
 @itemize
 @item
 The @code{source} field of the package is an @code{<origin>} object
-(@pxref{origin Reference}, for the complete reference).
-Here, the @code{url-fetch} method from @code{(guix download)} is used,
-meaning that the source is a file to be downloaded over FTP or HTTP.
+(@pxref{„origin“-Referenz}, for the complete reference).  Here, the
address@hidden method from @code{(guix download)} is used, meaning that
+the source is a file to be downloaded over FTP or HTTP.
 
-The @code{mirror://gnu} prefix instructs @code{url-fetch} to use one of
-the GNU mirrors defined in @code{(guix download)}.
+The @code{mirror://gnu} prefix instructs @code{url-fetch} to use one of the
+GNU mirrors defined in @code{(guix download)}.
 
-The @code{sha256} field specifies the expected SHA256 hash of the file
-being downloaded.  It is mandatory, and allows Guix to check the
-integrity of the file.  The @code{(base32 @dots{})} form introduces the
-base32 representation of the hash.  You can obtain this information with
address@hidden download} (@pxref{Invoking guix download}) and @code{guix
-hash} (@pxref{Invoking guix hash}).
+The @code{sha256} field specifies the expected SHA256 hash of the file being
+downloaded.  It is mandatory, and allows Guix to check the integrity of the
+file.  The @code{(base32 @dots{})} form introduces the base32 representation
+of the hash.  You can obtain this information with @code{guix download}
+(@pxref{Aufruf von guix download}) and @code{guix hash} (@pxref{Aufruf von 
guix hash}).
 
 @cindex patches
 When needed, the @code{origin} form can also have a @code{patches} field
-listing patches to be applied, and a @code{snippet} field giving a
-Scheme expression to modify the source code.
+listing patches to be applied, and a @code{snippet} field giving a Scheme
+expression to modify the source code.
 
 @item
address@hidden GNU Build System
-The @code{build-system} field specifies the procedure to build the
-package (@pxref{Build Systems}).  Here, @var{gnu-build-system}
-represents the familiar GNU Build System, where packages may be
-configured, built, and installed with the usual @code{./configure &&
-make && make check && make install} command sequence.
address@hidden GNU-Erstellungssystem
+The @code{build-system} field specifies the procedure to build the package
+(@pxref{Erstellungssysteme}).  Here, @var{gnu-build-system} represents the
+familiar GNU Build System, where packages may be configured, built, and
+installed with the usual @code{./configure && make && make check && make
+install} command sequence.
 
 @item
 The @code{arguments} field specifies options for the build system
-(@pxref{Build Systems}).  Here it is interpreted by
address@hidden as a request run @file{configure} with the
address@hidden flag.
+(@pxref{Erstellungssysteme}).  Here it is interpreted by @var{gnu-build-system}
+as a request run @file{configure} with the @code{--enable-silent-rules}
+flag.
 
 @cindex quote
 @cindex quoting
 @findex '
 @findex quote
-What about these quote (@code{'}) characters?  They are Scheme syntax to
+What about these quote (@code{'}) characters? They are Scheme syntax to
 introduce a literal list; @code{'} is synonymous with @code{quote}.
address@hidden Syntax, quoting,, guile, GNU Guile Reference Manual},
-for details.  Here the value of the @code{arguments} field is a list of
address@hidden Syntax, quoting,, guile, GNU Guile Reference Manual}, for
+details.  Here the value of the @code{arguments} field is a list of
 arguments passed to the build system down the road, as with @code{apply}
-(@pxref{Fly Evaluation, @code{apply},, guile, GNU Guile Reference
-Manual}).
+(@pxref{Fly Evaluation, @code{apply},, guile, GNU Guile Reference Manual}).
 
 The hash-colon (@code{#:}) sequence defines a Scheme @dfn{keyword}
 (@pxref{Keywords,,, guile, GNU Guile Reference Manual}), and
address@hidden:configure-flags} is a keyword used to pass a keyword argument
-to the build system (@pxref{Coding With Keywords,,, guile, GNU Guile
-Reference Manual}).
address@hidden:configure-flags} is a keyword used to pass a keyword argument to 
the
+build system (@pxref{Coding With Keywords,,, guile, GNU Guile Reference
+Manual}).
 
 @item
 The @code{inputs} field specifies inputs to the build process---i.e.,
 build-time or run-time dependencies of the package.  Here, we define an
-input called @code{"gawk"} whose value is that of the @var{gawk}
-variable; @var{gawk} is itself bound to a @code{<package>} object.
+input called @code{"gawk"} whose value is that of the @var{gawk} variable;
address@hidden is itself bound to a @code{<package>} object.
 
 @cindex backquote (quasiquote)
 @findex `
@@ -3817,57 +4011,50 @@ variable; @var{gawk} is itself bound to a 
@code{<package>} object.
 @findex unquote
 @findex ,@@
 @findex unquote-splicing
-Again, @code{`} (a backquote, synonymous with @code{quasiquote}) allows
-us to introduce a literal list in the @code{inputs} field, while
address@hidden,} (a comma, synonymous with @code{unquote}) allows us to insert a
-value in that list (@pxref{Expression Syntax, unquote,, guile, GNU Guile
-Reference Manual}).
+Again, @code{`} (a backquote, synonymous with @code{quasiquote}) allows us
+to introduce a literal list in the @code{inputs} field, while @code{,} (a
+comma, synonymous with @code{unquote}) allows us to insert a value in that
+list (@pxref{Expression Syntax, unquote,, guile, GNU Guile Reference
+Manual}).
 
-Note that GCC, Coreutils, Bash, and other essential tools do not need to
-be specified as inputs here.  Instead, @var{gnu-build-system} takes care
-of ensuring that they are present (@pxref{Build Systems}).
+Note that GCC, Coreutils, Bash, and other essential tools do not need to be
+specified as inputs here.  Instead, @var{gnu-build-system} takes care of
+ensuring that they are present (@pxref{Erstellungssysteme}).
 
-However, any other dependencies need to be specified in the
address@hidden field.  Any dependency not specified here will simply be
-unavailable to the build process, possibly leading to a build failure.
+However, any other dependencies need to be specified in the @code{inputs}
+field.  Any dependency not specified here will simply be unavailable to the
+build process, possibly leading to a build failure.
 @end itemize
 
address@hidden Reference}, for a full description of possible fields.
-
-Once a package definition is in place, the
-package may actually be built using the @code{guix build} command-line
-tool (@pxref{Invoking guix build}), troubleshooting any build failures
-you encounter (@pxref{Debugging Build Failures}).  You can easily jump back to 
the
-package definition using the @command{guix edit} command
-(@pxref{Invoking guix edit}).
address@hidden Guidelines}, for
-more information on how to test package definitions, and
address@hidden guix lint}, for information on how to check a definition
-for style conformance.
address@hidden, for a full description of possible fields.
+
+Once a package definition is in place, the package may actually be built
+using the @code{guix build} command-line tool (@pxref{Aufruf von guix build}),
+troubleshooting any build failures you encounter (@pxref{Fehlschläge beim 
Erstellen untersuchen}).  You can easily jump back to the package definition 
using the
address@hidden edit} command (@pxref{Aufruf von guix edit}).  
@xref{Paketrichtlinien}, for more information on how to test package 
definitions, and
address@hidden von guix lint}, for information on how to check a definition for
+style conformance.
 @vindex GUIX_PACKAGE_PATH
-Lastly, @pxref{Channels}, for information
-on how to extend the distribution by adding your own package definitions
-in a ``channel''.
+Lastly, @pxref{Channels}, for information on how to extend the distribution
+by adding your own package definitions in a ``channel''.
 
-Finally, updating the package definition to a new upstream version
-can be partly automated by the @command{guix refresh} command
-(@pxref{Invoking guix refresh}).
+Finally, updating the package definition to a new upstream version can be
+partly automated by the @command{guix refresh} command (@pxref{Aufruf von guix 
refresh}).
 
-Behind the scenes, a derivation corresponding to the @code{<package>}
-object is first computed by the @code{package-derivation} procedure.
-That derivation is stored in a @code{.drv} file under @file{/gnu/store}.
-The build actions it prescribes may then be realized by using the
address@hidden procedure (@pxref{The Store}).
+Behind the scenes, a derivation corresponding to the @code{<package>} object
+is first computed by the @code{package-derivation} procedure.  That
+derivation is stored in a @code{.drv} file under @file{/gnu/store}.  The
+build actions it prescribes may then be realized by using the
address@hidden procedure (@pxref{Der Store}).
 
 @deffn {Scheme Procedure} package-derivation @var{store} @var{package} 
address@hidden
 Return the @code{<derivation>} object of @var{package} for @var{system}
-(@pxref{Derivations}).
+(@pxref{Ableitungen}).
 
address@hidden must be a valid @code{<package>} object, and @var{system}
-must be a string denoting the target system type---e.g.,
address@hidden"x86_64-linux"} for an x86_64 Linux-based GNU system.  @var{store}
-must be a connection to the daemon, which operates on the store
-(@pxref{The Store}).
address@hidden must be a valid @code{<package>} object, and @var{system} must
+be a string denoting the target system type---e.g., @code{"x86_64-linux"}
+for an x86_64 Linux-based GNU system.  @var{store} must be a connection to
+the daemon, which operates on the store (@pxref{Der Store}).
 @end deffn
 
 @noindent
@@ -3876,33 +4063,31 @@ Similarly, it is possible to compute a derivation that 
cross-builds a
 package for some other system:
 
 @deffn {Scheme Procedure} package-cross-derivation @var{store} @
-            @var{package} @var{target} address@hidden
-Return the @code{<derivation>} object of @var{package} cross-built from
address@hidden to @var{target}.
-
address@hidden must be a valid GNU triplet denoting the target hardware
-and operating system, such as @code{"mips64el-linux-gnu"}
-(@pxref{Configuration Names, GNU configuration triplets,, configure, GNU
-Configure and Build System}).
+            @var{package} @var{target} address@hidden Return the 
@code{<derivation>}
+object of @var{package} cross-built from @var{system} to @var{target}.
+
address@hidden must be a valid GNU triplet denoting the target hardware and
+operating system, such as @code{"mips64el-linux-gnu"} (@pxref{Configuration
+Names, GNU configuration triplets,, configure, GNU Configure and Build
+System}).
 @end deffn
 
 @cindex package transformations
 @cindex input rewriting
 @cindex dependency tree rewriting
 Packages can be manipulated in arbitrary ways.  An example of a useful
-transformation is @dfn{input rewriting}, whereby the dependency tree of
-a package is rewritten by replacing specific inputs by others:
+transformation is @dfn{input rewriting}, whereby the dependency tree of a
+package is rewritten by replacing specific inputs by others:
 
 @deffn {Scheme Procedure} package-input-rewriting @var{replacements} @
-           address@hidden
-Return a procedure that, when passed a package, replaces its direct and
-indirect dependencies (but not its implicit inputs) according to
address@hidden  @var{replacements} is a list of package pairs; the
-first element of each pair is the package to replace, and the second one
-is the replacement.
-
-Optionally, @var{rewrite-name} is a one-argument procedure that takes
-the name of a package and returns its new name after rewrite.
+           address@hidden Return a procedure that, when passed a package,
+replaces its direct and indirect dependencies (but not its implicit inputs)
+according to @var{replacements}.  @var{replacements} is a list of package
+pairs; the first element of each pair is the package to replace, and the
+second one is the replacement.
+
+Optionally, @var{rewrite-name} is a one-argument procedure that takes the
+name of a package and returns its new name after rewrite.
 @end deffn
 
 @noindent
@@ -3919,33 +4104,31 @@ Consider this example:
 @end example
 
 @noindent
-Here we first define a rewriting procedure that replaces @var{openssl}
-with @var{libressl}.  Then we use it to define a @dfn{variant} of the
address@hidden package that uses @var{libressl} instead of @var{openssl}.
-This is exactly what the @option{--with-input} command-line option does
-(@pxref{Package Transformation Options, @option{--with-input}}).
+Here we first define a rewriting procedure that replaces @var{openssl} with
address@hidden  Then we use it to define a @dfn{variant} of the @var{git}
+package that uses @var{libressl} instead of @var{openssl}.  This is exactly
+what the @option{--with-input} command-line option does 
(@pxref{Paketumwandlungsoptionen, @option{--with-input}}).
 
 A more generic procedure to rewrite a package dependency graph is
address@hidden: it supports arbitrary changes to nodes in the
-graph.
address@hidden: it supports arbitrary changes to nodes in the graph.
 
 @deffn {Scheme Procedure} package-mapping @var{proc} address@hidden
-Return a procedure that, given a package, applies @var{proc} to all the 
packages
-depended on and returns the resulting package.  The procedure stops recursion
-when @var{cut?} returns true for a given package.
+Return a procedure that, given a package, applies @var{proc} to all the
+packages depended on and returns the resulting package.  The procedure stops
+recursion when @var{cut?} returns true for a given package.
 @end deffn
 
 @menu
-* package Reference::           The package data type.
-* origin Reference::            The origin data type.
+* „package“-Referenz::   Der Datentyp für Pakete.
+* „origin“-Referenz::    Datentyp für Paketursprünge.
 @end menu
 
 
address@hidden package Reference
address@hidden „package“-Referenz
 @subsection @code{package} Reference
 
 This section summarizes all the options available in @code{package}
-declarations (@pxref{Defining Packages}).
+declarations (@pxref{Pakete definieren}).
 
 @deftp {Data Type} package
 This is the data type representing a package recipe.
@@ -3958,32 +4141,29 @@ The name of the package, as a string.
 The version of the package, as a string.
 
 @item @code{source}
-An object telling how the source code for the package should be
-acquired.  Most of the time, this is an @code{origin} object, which
-denotes a file fetched from the Internet (@pxref{origin Reference}).  It
-can also be any other ``file-like'' object such as a @code{local-file},
-which denotes a file from the local file system (@pxref{G-Expressions,
address@hidden).
+An object telling how the source code for the package should be acquired.
+Most of the time, this is an @code{origin} object, which denotes a file
+fetched from the Internet (@pxref{„origin“-Referenz}).  It can also be any
+other ``file-like'' object such as a @code{local-file}, which denotes a file
+from the local file system (@pxref{G-Ausdrücke, @code{local-file}}).
 
 @item @code{build-system}
-The build system that should be used to build the package (@pxref{Build
-Systems}).
+The build system that should be used to build the package 
(@pxref{Erstellungssysteme}).
 
 @item @code{arguments} (default: @code{'()})
-The arguments that should be passed to the build system.  This is a
-list, typically containing sequential keyword-value pairs.
+The arguments that should be passed to the build system.  This is a list,
+typically containing sequential keyword-value pairs.
 
 @item @code{inputs} (default: @code{'()})
 @itemx @code{native-inputs} (default: @code{'()})
 @itemx @code{propagated-inputs} (default: @code{'()})
 @cindex inputs, of packages
 These fields list dependencies of the package.  Each one is a list of
-tuples, where each tuple has a label for the input (a string) as its
-first element, a package, origin, or derivation as its second element,
-and optionally the name of the output thereof that should be used, which
-defaults to @code{"out"} (@pxref{Packages with Multiple Outputs}, for
-more on package outputs).  For example, the list below specifies three
-inputs:
+tuples, where each tuple has a label for the input (a string) as its first
+element, a package, origin, or derivation as its second element, and
+optionally the name of the output thereof that should be used, which
+defaults to @code{"out"} (@pxref{Pakete mit mehreren Ausgaben.}, for more
+on package outputs).  For example, the list below specifies three inputs:
 
 @example
 `(("libffi" ,libffi)
@@ -3992,16 +4172,16 @@ inputs:
 @end example
 
 @cindex cross compilation, package dependencies
-The distinction between @code{native-inputs} and @code{inputs} is
-necessary when considering cross-compilation.  When cross-compiling,
-dependencies listed in @code{inputs} are built for the @emph{target}
-architecture; conversely, dependencies listed in @code{native-inputs}
-are built for the architecture of the @emph{build} machine.
+The distinction between @code{native-inputs} and @code{inputs} is necessary
+when considering cross-compilation.  When cross-compiling, dependencies
+listed in @code{inputs} are built for the @emph{target} architecture;
+conversely, dependencies listed in @code{native-inputs} are built for the
+architecture of the @emph{build} machine.
 
address@hidden is typically used to list tools needed at
-build time, but not at run time, such as Autoconf, Automake, pkg-config,
-Gettext, or Bison.  @command{guix lint} can report likely mistakes in
-this area (@pxref{Invoking guix lint}).
address@hidden is typically used to list tools needed at build time,
+but not at run time, such as Autoconf, Automake, pkg-config, Gettext, or
+Bison.  @command{guix lint} can report likely mistakes in this area
+(@pxref{Aufruf von guix lint}).
 
 @anchor{package-propagated-inputs}
 Lastly, @code{propagated-inputs} is similar to @code{inputs}, but the
@@ -4010,45 +4190,44 @@ they belong to (@pxref{package-cmd-propagated-inputs, 
@command{guix
 package}}, for information on how @command{guix package} deals with
 propagated inputs.)
 
-For example this is necessary when a C/C++ library needs headers of
-another library to compile, or when a pkg-config file refers to another
-one @i{via} its @code{Requires} field.
+For example this is necessary when a C/C++ library needs headers of another
+library to compile, or when a pkg-config file refers to another one @i{via}
+its @code{Requires} field.
 
 Another example where @code{propagated-inputs} is useful is for languages
 that lack a facility to record the run-time search path akin to the
address@hidden of ELF files; this includes Guile, Python, Perl, and
-more.  To ensure that libraries written in those languages can find
-library code they depend on at run time, run-time dependencies must be
-listed in @code{propagated-inputs} rather than @code{inputs}.
address@hidden of ELF files; this includes Guile, Python, Perl, and more.
+To ensure that libraries written in those languages can find library code
+they depend on at run time, run-time dependencies must be listed in
address@hidden rather than @code{inputs}.
 
 @item @code{self-native-input?} (default: @code{#f})
-This is a Boolean field telling whether the package should use itself as
-a native input when cross-compiling.
+This is a Boolean field telling whether the package should use itself as a
+native input when cross-compiling.
 
 @item @code{outputs} (default: @code{'("out")})
-The list of output names of the package.  @xref{Packages with Multiple
-Outputs}, for typical uses of additional outputs.
+The list of output names of the package.  @xref{Pakete mit mehreren 
Ausgaben.}, for typical uses of additional outputs.
 
 @item @code{native-search-paths} (default: @code{'()})
 @itemx @code{search-paths} (default: @code{'()})
-A list of @code{search-path-specification} objects describing
-search-path environment variables honored by the package.
+A list of @code{search-path-specification} objects describing search-path
+environment variables honored by the package.
 
 @item @code{replacement} (default: @code{#f})
 This must be either @code{#f} or a package object that will be used as a
address@hidden for this package.  @xref{Security Updates, grafts},
-for details.
address@hidden for this package.  @xref{Sicherheitsaktualisierungen, grafts}, 
for
+details.
 
 @item @code{synopsis}
-A one-line description of the package.
+Eine einzeilige Beschreibung des Pakets.
 
 @item @code{description}
-A more elaborate description of the package.
+Eine ausführlichere Beschreibung des Pakets.
 
 @item @code{license}
 @cindex license, of packages
-The license of the package; a value from @code{(guix licenses)},
-or a list of such values.
+The license of the package; a value from @code{(guix licenses)}, or a list
+of such values.
 
 @item @code{home-page}
 The URL to the home-page of the package, as a string.
@@ -4068,21 +4247,21 @@ automatically corrected.
 @end deftp
 
 
address@hidden origin Reference
address@hidden „origin“-Referenz
 @subsection @code{origin} Reference
 
 This section summarizes all the options available in @code{origin}
-declarations (@pxref{Defining Packages}).
+declarations (@pxref{Pakete definieren}).
 
 @deftp {Data Type} origin
 This is the data type representing a source code origin.
 
 @table @asis
 @item @code{uri}
-An object containing the URI of the source.  The object type depends on
-the @code{method} (see below).  For example, when using the
address@hidden method of @code{(guix download)}, the valid @code{uri}
-values are: a URL represented as a string, or a list thereof.
+An object containing the URI of the source.  The object type depends on the
address@hidden (see below).  For example, when using the @var{url-fetch}
+method of @code{(guix download)}, the valid @code{uri} values are: a URL
+represented as a string, or a list thereof.
 
 @item @code{method}
 A procedure that handles the URI.
@@ -4091,8 +4270,8 @@ Examples include:
 
 @table @asis
 @item @var{url-fetch} from @code{(guix download)}
-download a file from the HTTP, HTTPS, or FTP URL specified in the
address@hidden field;
+download a file from the HTTP, HTTPS, or FTP URL specified in the @code{uri}
+field;
 
 @vindex git-fetch
 @item @var{git-fetch} from @code{(guix git-download)}
@@ -4109,31 +4288,28 @@ specified in the @code{uri} field as a 
@code{git-reference} object; a
 
 @item @code{sha256}
 A bytevector containing the SHA-256 hash of the source.  Typically the
address@hidden form is used here to generate the bytevector from a
-base-32 string.
address@hidden form is used here to generate the bytevector from a base-32
+string.
 
-You can obtain this information using @code{guix download}
-(@pxref{Invoking guix download}) or @code{guix hash} (@pxref{Invoking
-guix hash}).
+You can obtain this information using @code{guix download} (@pxref{Aufruf von 
guix download}) or @code{guix hash} (@pxref{Aufruf von guix hash}).
 
 @item @code{file-name} (default: @code{#f})
 The file name under which the source code should be saved.  When this is
address@hidden, a sensible default value will be used in most cases.  In case
-the source is fetched from a URL, the file name from the URL will be
-used.  For version control checkouts, it is recommended to provide the
-file name explicitly because the default is not very descriptive.
address@hidden, a sensible default value will be used in most cases.  In case 
the
+source is fetched from a URL, the file name from the URL will be used.  For
+version control checkouts, it is recommended to provide the file name
+explicitly because the default is not very descriptive.
 
 @item @code{patches} (default: @code{'()})
-A list of file names, origins, or file-like objects (@pxref{G-Expressions,
+A list of file names, origins, or file-like objects (@pxref{G-Ausdrücke,
 file-like objects}) pointing to patches to be applied to the source.
 
-This list of patches must be unconditional.  In particular, it cannot
-depend on the value of @code{%current-system} or
address@hidden
+This list of patches must be unconditional.  In particular, it cannot depend
+on the value of @code{%current-system} or @code{%current-target-system}.
 
 @item @code{snippet} (default: @code{#f})
-A G-expression (@pxref{G-Expressions}) or S-expression that will be run
-in the source directory.  This is a convenient way to modify the source,
+A G-expression (@pxref{G-Ausdrücke}) or S-expression that will be run in
+the source directory.  This is a convenient way to modify the source,
 sometimes more convenient than a patch.
 
 @item @code{patch-flags} (default: @code{'("-p1")})
@@ -4142,86 +4318,86 @@ command.
 
 @item @code{patch-inputs} (default: @code{#f})
 Input packages or derivations to the patching process.  When this is
address@hidden, the usual set of inputs necessary for patching are provided,
-such as address@hidden
address@hidden, the usual set of inputs necessary for patching are provided, 
such
+as address@hidden
 
 @item @code{modules} (default: @code{'()})
-A list of Guile modules that should be loaded during the patching
-process and while running the code in the @code{snippet} field.
+A list of Guile modules that should be loaded during the patching process
+and while running the code in the @code{snippet} field.
 
 @item @code{patch-guile} (default: @code{#f})
-The Guile package that should be used in the patching process.  When
-this is @code{#f}, a sensible default is used.
+The Guile package that should be used in the patching process.  When this is
address@hidden, a sensible default is used.
 @end table
 @end deftp
 
 
address@hidden Build Systems
address@hidden Build Systems
address@hidden Erstellungssysteme
address@hidden Erstellungssysteme
 
 @cindex build system
 Each package definition specifies a @dfn{build system} and arguments for
-that build system (@pxref{Defining Packages}).  This @code{build-system}
+that build system (@pxref{Pakete definieren}).  This @code{build-system}
 field represents the build procedure of the package, as well as implicit
 dependencies of that build procedure.
 
-Build systems are @code{<build-system>} objects.  The interface to
-create and manipulate them is provided by the @code{(guix build-system)}
-module, and actual build systems are exported by specific modules.
+Build systems are @code{<build-system>} objects.  The interface to create
+and manipulate them is provided by the @code{(guix build-system)} module,
+and actual build systems are exported by specific modules.
 
 @cindex bag (low-level package representation)
-Under the hood, build systems first compile package objects to
address@hidden  A @dfn{bag} is like a package, but with less
-ornamentation---in other words, a bag is a lower-level representation of
-a package, which includes all the inputs of that package, including some
-that were implicitly added by the build system.  This intermediate
-representation is then compiled to a derivation (@pxref{Derivations}).
+Under the hood, build systems first compile package objects to @dfn{bags}.
+A @dfn{bag} is like a package, but with less ornamentation---in other words,
+a bag is a lower-level representation of a package, which includes all the
+inputs of that package, including some that were implicitly added by the
+build system.  This intermediate representation is then compiled to a
+derivation (@pxref{Ableitungen}).
 
 Build systems accept an optional list of @dfn{arguments}.  In package
 definitions, these are passed @i{via} the @code{arguments} field
-(@pxref{Defining Packages}).  They are typically keyword arguments
-(@pxref{Optional Arguments, keyword arguments in Guile,, guile, GNU
-Guile Reference Manual}).  The value of these arguments is usually
-evaluated in the @dfn{build stratum}---i.e., by a Guile process launched
-by the daemon (@pxref{Derivations}).
+(@pxref{Pakete definieren}).  They are typically keyword arguments
+(@pxref{Optional Arguments, keyword arguments in Guile,, guile, GNU Guile
+Reference Manual}).  The value of these arguments is usually evaluated in
+the @dfn{build stratum}---i.e., by a Guile process launched by the daemon
+(@pxref{Ableitungen}).
 
 The main build system is @var{gnu-build-system}, which implements the
-standard build procedure for GNU and many other packages.  It
-is provided by the @code{(guix build-system gnu)} module.
+standard build procedure for GNU and many other packages.  It is provided by
+the @code{(guix build-system gnu)} module.
 
 @defvr {Scheme Variable} gnu-build-system
address@hidden represents the GNU Build System, and variants
-thereof (@pxref{Configuration, configuration and makefile conventions,,
-standards, GNU Coding Standards}).
address@hidden represents the GNU Build System, and variants thereof
+(@pxref{Configuration, configuration and makefile conventions,, standards,
+GNU Coding Standards}).
 
 @cindex build phases
 In a nutshell, packages using it are configured, built, and installed with
-the usual @code{./configure && make && make check && make install}
-command sequence.  In practice, a few additional steps are often needed.
-All these steps are split up in separate @dfn{phases},
address@hidden see the @code{(guix build gnu-build-system)}
-modules for more details about the build phases.}:
+the usual @code{./configure && make && make check && make install} command
+sequence.  In practice, a few additional steps are often needed.  All these
+steps are split up in separate @dfn{phases}, address@hidden see the
address@hidden(guix build gnu-build-system)} modules for more details about the
+build phases.}:
 
 @table @code
 @item unpack
-Unpack the source tarball, and change the current directory to the
-extracted source tree.  If the source is actually a directory, copy it
-to the build tree, and enter that directory.
+Unpack the source tarball, and change the current directory to the extracted
+source tree.  If the source is actually a directory, copy it to the build
+tree, and enter that directory.
 
 @item patch-source-shebangs
-Patch shebangs encountered in source files so they refer to the right
-store file names.  For instance, this changes @code{#!/bin/sh} to
+Patch shebangs encountered in source files so they refer to the right store
+file names.  For instance, this changes @code{#!/bin/sh} to
 @code{#!/gnu/store/@dots{}-bash-4.3/bin/sh}.
 
 @item configure
-Run the @file{configure} script with a number of default options, such
-as @code{--prefix=/gnu/store/@dots{}}, as well as the options specified
-by the @code{#:configure-flags} argument.
+Run the @file{configure} script with a number of default options, such as
address@hidden/gnu/store/@dots{}}, as well as the options specified by the
address@hidden:configure-flags} argument.
 
 @item build
-Run @code{make} with the list of flags specified with
address@hidden:make-flags}.  If the @code{#:parallel-build?} argument is true
-(the default), build with @code{make -j}.
+Run @code{make} with the list of flags specified with @code{#:make-flags}.
+If the @code{#:parallel-build?} argument is true (the default), build with
address@hidden -j}.
 
 @item check
 Run @code{make check}, or some other target specified with
@@ -4236,9 +4412,9 @@ Run @code{make install} with the flags listed in 
@code{#:make-flags}.
 Patch shebangs on the installed executable files.
 
 @item strip
-Strip debugging symbols from ELF files (unless @code{#:strip-binaries?}
-is false), copying them to the @code{debug} output when available
-(@pxref{Installing Debugging Files}).
+Strip debugging symbols from ELF files (unless @code{#:strip-binaries?} is
+false), copying them to the @code{debug} output when available
+(@pxref{Dateien zur Fehlersuche installieren}).
 @end table
 
 @vindex %standard-phases
@@ -4257,47 +4433,47 @@ The list of phases used for a particular package can be 
changed with the
 means that all the phases described above will be used, except the
 @code{configure} phase.
 
-In addition, this build system ensures that the ``standard'' environment
-for GNU packages is available.  This includes tools such as GCC, libc,
+In addition, this build system ensures that the ``standard'' environment for
+GNU packages is available.  This includes tools such as GCC, libc,
 Coreutils, Bash, Make, Diffutils, grep, and sed (see the @code{(guix
 build-system gnu)} module for a complete list).  We call these the
address@hidden inputs} of a package, because package definitions do not
-have to mention them.
address@hidden inputs} of a package, because package definitions do not have
+to mention them.
 @end defvr
 
-Other @code{<build-system>} objects are defined to support other
-conventions and tools used by free software packages.  They inherit most
-of @var{gnu-build-system}, and differ mainly in the set of inputs
-implicitly added to the build process, and in the list of phases
-executed.  Some of these build systems are listed below.
+Other @code{<build-system>} objects are defined to support other conventions
+and tools used by free software packages.  They inherit most of
address@hidden, and differ mainly in the set of inputs implicitly
+added to the build process, and in the list of phases executed.  Some of
+these build systems are listed below.
 
 @defvr {Scheme Variable} ant-build-system
-This variable is exported by @code{(guix build-system ant)}.  It
-implements the build procedure for Java packages that can be built with
+This variable is exported by @code{(guix build-system ant)}.  It implements
+the build procedure for Java packages that can be built with
 @url{http://ant.apache.org/, Ant build tool}.
 
-It adds both @code{ant} and the @dfn{Java Development Kit} (JDK) as
-provided by the @code{icedtea} package to the set of inputs.  Different
-packages can be specified with the @code{#:ant} and @code{#:jdk}
-parameters, respectively.
-
-When the original package does not provide a suitable Ant build file,
-the parameter @code{#:jar-name} can be used to generate a minimal Ant
-build file @file{build.xml} with tasks to build the specified jar
-archive.  In this case the parameter @code{#:source-dir} can be used to
-specify the source sub-directory, defaulting to ``src''.
-
-The @code{#:main-class} parameter can be used with the minimal ant 
-buildfile to specify the main class of the resulting jar.  This makes the 
-jar file executable.  The @code{#:test-include} parameter can be used to 
-specify the list of junit tests to run. It defaults to
address@hidden(list "**/*Test.java")}.  The @code{#:test-exclude} can be used to
-disable some tests. It defaults to @code{(list "**/Abstract*.java")},
-because abstract classes cannot be run as tests.
-
-The parameter @code{#:build-target} can be used to specify the Ant task
-that should be run during the @code{build} phase.  By default the
-``jar'' task will be run.
+It adds both @code{ant} and the @dfn{Java Development Kit} (JDK) as provided
+by the @code{icedtea} package to the set of inputs.  Different packages can
+be specified with the @code{#:ant} and @code{#:jdk} parameters,
+respectively.
+
+When the original package does not provide a suitable Ant build file, the
+parameter @code{#:jar-name} can be used to generate a minimal Ant build file
address@hidden with tasks to build the specified jar archive.  In this
+case the parameter @code{#:source-dir} can be used to specify the source
+sub-directory, defaulting to ``src''.
+
+The @code{#:main-class} parameter can be used with the minimal ant buildfile
+to specify the main class of the resulting jar.  This makes the jar file
+executable.  The @code{#:test-include} parameter can be used to specify the
+list of junit tests to run. It defaults to @code{(list "**/*Test.java")}.
+The @code{#:test-exclude} can be used to disable some tests. It defaults to
address@hidden(list "**/Abstract*.java")}, because abstract classes cannot be 
run as
+tests.
+
+The parameter @code{#:build-target} can be used to specify the Ant task that
+should be run during the @code{build} phase.  By default the ``jar'' task
+will be run.
 
 @end defvr
 
@@ -4309,14 +4485,14 @@ implements a build procedure for Android NDK (native 
development kit)
 packages using a Guix-specific build process.
 
 The build system assumes that packages install their public interface
-(header) files to the subdirectory "include" of the "out" output and
-their libraries to the subdirectory "lib" of the "out" output.
+(header) files to the subdirectory "include" of the "out" output and their
+libraries to the subdirectory "lib" of the "out" output.
 
-It's also assumed that the union of all the dependencies of a package
-has no conflicting files.
+It's also assumed that the union of all the dependencies of a package has no
+conflicting files.
 
-For the time being, cross-compilation is not supported - so right now
-the libraries and header files are assumed to be host tools.
+For the time being, cross-compilation is not supported - so right now the
+libraries and header files are assumed to be host tools.
 
 @end defvr
 
@@ -4329,53 +4505,52 @@ build procedures for Common Lisp packages using
 @url{https://common-lisp.net/project/asdf/, ``ASDF''}. ASDF is a system
 definition facility for Common Lisp programs and libraries.
 
-The @code{asdf-build-system/source} system installs the packages in
-source form, and can be loaded using any common lisp implementation, via
-ASDF.  The others, such as @code{asdf-build-system/sbcl}, install binary
-systems in the format which a particular implementation understands.
-These build systems can also be used to produce executable programs, or
-lisp images which contain a set of packages pre-loaded.
-
-The build system uses naming conventions.  For binary packages, the
-package name should be prefixed with the lisp implementation, such as
address@hidden for @code{asdf-build-system/sbcl}.
-
-Additionally, the corresponding source package should be labeled using
-the same convention as python packages (see @ref{Python Modules}), using
-the @code{cl-} prefix.
-
-For binary packages, each system should be defined as a Guix package.
-If one package @code{origin} contains several systems, package variants
-can be created in order to build all the systems.  Source packages,
-which use @code{asdf-build-system/source}, may contain several systems.
-
-In order to create executable programs and images, the build-side
-procedures @code{build-program} and @code{build-image} can be used.
-They should be called in a build phase after the @code{create-symlinks}
-phase, so that the system which was just built can be used within the
-resulting image.  @code{build-program} requires a list of Common Lisp
-expressions to be passed as the @code{#:entry-program} argument.
+The @code{asdf-build-system/source} system installs the packages in source
+form, and can be loaded using any common lisp implementation, via ASDF.  The
+others, such as @code{asdf-build-system/sbcl}, install binary systems in the
+format which a particular implementation understands.  These build systems
+can also be used to produce executable programs, or lisp images which
+contain a set of packages pre-loaded.
+
+The build system uses naming conventions.  For binary packages, the package
+name should be prefixed with the lisp implementation, such as @code{sbcl-}
+for @code{asdf-build-system/sbcl}.
+
+Additionally, the corresponding source package should be labeled using the
+same convention as python packages (see @ref{Python-Module}), using the
address@hidden prefix.
+
+For binary packages, each system should be defined as a Guix package.  If
+one package @code{origin} contains several systems, package variants can be
+created in order to build all the systems.  Source packages, which use
address@hidden/source}, may contain several systems.
+
+In order to create executable programs and images, the build-side procedures
address@hidden and @code{build-image} can be used.  They should be
+called in a build phase after the @code{create-symlinks} phase, so that the
+system which was just built can be used within the resulting image.
address@hidden requires a list of Common Lisp expressions to be passed
+as the @code{#:entry-program} argument.
 
 If the system is not defined within its own @code{.asd} file of the same
-name, then the @code{#:asd-file} parameter should be used to specify
-which file the system is defined in.  Furthermore, if the package
-defines a system for its tests in a separate file, it will be loaded
-before the tests are run if it is specified by the
address@hidden:test-asd-file} parameter.  If it is not set, the files
address@hidden<system>-tests.asd}, @code{<system>-test.asd}, @code{tests.asd},
-and @code{test.asd} will be tried if they exist.
+name, then the @code{#:asd-file} parameter should be used to specify which
+file the system is defined in.  Furthermore, if the package defines a system
+for its tests in a separate file, it will be loaded before the tests are run
+if it is specified by the @code{#:test-asd-file} parameter.  If it is not
+set, the files @code{<system>-tests.asd}, @code{<system>-test.asd},
address@hidden, and @code{test.asd} will be tried if they exist.
 
 If for some reason the package must be named in a different way than the
-naming conventions suggest, the @code{#:asd-system-name} parameter can
-be used to specify the name of the system.
+naming conventions suggest, the @code{#:asd-system-name} parameter can be
+used to specify the name of the system.
 
 @end defvr
 
 @defvr {Scheme Variable} cargo-build-system
 @cindex Rust programming language
 @cindex Cargo (Rust build system)
-This variable is exported by @code{(guix build-system cargo)}.  It
-supports builds of packages using Cargo, the build tool of the
+This variable is exported by @code{(guix build-system cargo)}.  It supports
+builds of packages using Cargo, the build tool of the
 @uref{https://www.rust-lang.org, Rust programming language}.
 
 In its @code{configure} phase, this build system replaces dependencies
@@ -4389,71 +4564,70 @@ This variable is exported by @code{(guix build-system 
cmake)}.  It
 implements the build procedure for packages using the
 @url{http://www.cmake.org, CMake build tool}.
 
-It automatically adds the @code{cmake} package to the set of inputs.
-Which package is used can be specified with the @code{#:cmake}
-parameter.
+It automatically adds the @code{cmake} package to the set of inputs.  Which
+package is used can be specified with the @code{#:cmake} parameter.
 
-The @code{#:configure-flags} parameter is taken as a list of flags
-passed to the @command{cmake} command.  The @code{#:build-type}
-parameter specifies in abstract terms the flags passed to the compiler;
-it defaults to @code{"RelWithDebInfo"} (short for ``release mode with
-debugging information''), which roughly means that code is compiled with
address@hidden -g}, as is the case for Autoconf-based packages by default.
+The @code{#:configure-flags} parameter is taken as a list of flags passed to
+the @command{cmake} command.  The @code{#:build-type} parameter specifies in
+abstract terms the flags passed to the compiler; it defaults to
address@hidden"RelWithDebInfo"} (short for ``release mode with debugging
+information''), which roughly means that code is compiled with @code{-O2
+-g}, as is the case for Autoconf-based packages by default.
 @end defvr
 
 @defvr {Scheme Variable} go-build-system
-This variable is exported by @code{(guix build-system go)}.  It
-implements a build procedure for Go packages using the standard
address@hidden://golang.org/cmd/go/#hdr-Compile_packages_and_dependencies,
-Go build mechanisms}.
+This variable is exported by @code{(guix build-system go)}.  It implements a
+build procedure for Go packages using the standard
address@hidden://golang.org/cmd/go/#hdr-Compile_packages_and_dependencies, Go
+build mechanisms}.
 
 The user is expected to provide a value for the key @code{#:import-path}
 and, in some cases, @code{#:unpack-path}.  The
address@hidden://golang.org/doc/code.html#ImportPaths, import path}
-corresponds to the file system path expected by the package's build
-scripts and any referring packages, and provides a unique way to
-refer to a Go package.  It is typically based on a combination of the
-package source code's remote URI and file system hierarchy structure.  In
-some cases, you will need to unpack the package's source code to a
-different directory structure than the one indicated by the import path,
-and @code{#:unpack-path} should be used in such cases.
address@hidden://golang.org/doc/code.html#ImportPaths, import path} corresponds
+to the file system path expected by the package's build scripts and any
+referring packages, and provides a unique way to refer to a Go package.  It
+is typically based on a combination of the package source code's remote URI
+and file system hierarchy structure.  In some cases, you will need to unpack
+the package's source code to a different directory structure than the one
+indicated by the import path, and @code{#:unpack-path} should be used in
+such cases.
 
 Packages that provide Go libraries should be installed along with their
-source code.  The key @code{#:install-source?}, which defaults to
address@hidden, controls whether or not the source code is installed.  It can
-be set to @code{#f} for packages that only provide executable files.
+source code.  The key @code{#:install-source?}, which defaults to @code{#t},
+controls whether or not the source code is installed.  It can be set to
address@hidden for packages that only provide executable files.
 @end defvr
 
 @defvr {Scheme Variable} glib-or-gtk-build-system
-This variable is exported by @code{(guix build-system glib-or-gtk)}.  It
-is intended for use with packages making use of GLib or GTK+.
+This variable is exported by @code{(guix build-system glib-or-gtk)}.  It is
+intended for use with packages making use of GLib or GTK+.
 
 This build system adds the following two phases to the ones defined by
 @var{gnu-build-system}:
 
 @table @code
 @item glib-or-gtk-wrap
-The phase @code{glib-or-gtk-wrap} ensures that programs in
address@hidden/} are able to find GLib ``schemas'' and
+The phase @code{glib-or-gtk-wrap} ensures that programs in @file{bin/} are
+able to find GLib ``schemas'' and
 @uref{https://developer.gnome.org/gtk3/stable/gtk-running.html, GTK+
-modules}.  This is achieved by wrapping the programs in launch scripts
-that appropriately set the @code{XDG_DATA_DIRS} and @code{GTK_PATH}
-environment variables.
+modules}.  This is achieved by wrapping the programs in launch scripts that
+appropriately set the @code{XDG_DATA_DIRS} and @code{GTK_PATH} environment
+variables.
 
 It is possible to exclude specific package outputs from that wrapping
 process by listing their names in the
address@hidden:glib-or-gtk-wrap-excluded-outputs} parameter.  This is useful
-when an output is known not to contain any GLib or GTK+ binaries, and
-where wrapping would gratuitously add a dependency of that output on
-GLib and GTK+.
address@hidden:glib-or-gtk-wrap-excluded-outputs} parameter.  This is useful 
when
+an output is known not to contain any GLib or GTK+ binaries, and where
+wrapping would gratuitously add a dependency of that output on GLib and
+GTK+.
 
 @item glib-or-gtk-compile-schemas
 The phase @code{glib-or-gtk-compile-schemas} makes sure that all
 @uref{https://developer.gnome.org/gio/stable/glib-compile-schemas.html,
 GSettings schemas} of GLib are compiled.  Compilation is performed by the
 @command{glib-compile-schemas} program.  It is provided by the package
address@hidden:bin} which is automatically imported by the build system.
-The @code{glib} package providing @command{glib-compile-schemas} can be
address@hidden:bin} which is automatically imported by the build system.  The
address@hidden package providing @command{glib-compile-schemas} can be
 specified with the @code{#:glib} parameter.
 @end table
 
@@ -4471,45 +4645,45 @@ installs documentation.
 This build system supports cross-compilation by using the @code{--target}
 option of @command{guild compile}.
 
-Packages built with @code{guile-build-system} must provide a Guile package in
-their @code{native-inputs} field.
+Packages built with @code{guile-build-system} must provide a Guile package
+in their @code{native-inputs} field.
 @end defvr
 
 @defvr {Scheme Variable} minify-build-system
 This variable is exported by @code{(guix build-system minify)}.  It
 implements a minification procedure for simple JavaScript packages.
 
-It adds @code{uglify-js} to the set of inputs and uses it to compress
-all JavaScript files in the @file{src} directory.  A different minifier
-package can be specified with the @code{#:uglify-js} parameter, but it
-is expected that the package writes the minified code to the standard
-output.
+It adds @code{uglify-js} to the set of inputs and uses it to compress all
+JavaScript files in the @file{src} directory.  A different minifier package
+can be specified with the @code{#:uglify-js} parameter, but it is expected
+that the package writes the minified code to the standard output.
 
 When the input JavaScript files are not all located in the @file{src}
-directory, the parameter @code{#:javascript-files} can be used to
-specify a list of file names to feed to the minifier.
+directory, the parameter @code{#:javascript-files} can be used to specify a
+list of file names to feed to the minifier.
 @end defvr
 
 @defvr {Scheme Variable} ocaml-build-system
-This variable is exported by @code{(guix build-system ocaml)}.  It implements
-a build procedure for @uref{https://ocaml.org, OCaml} packages, which consists
-of choosing the correct set of commands to run for each package.  OCaml
-packages can expect many different commands to be run.  This build system will
-try some of them.
-
-When the package has a @file{setup.ml} file present at the top-level, it will
-run @code{ocaml setup.ml -configure}, @code{ocaml setup.ml -build} and
+This variable is exported by @code{(guix build-system ocaml)}.  It
+implements a build procedure for @uref{https://ocaml.org, OCaml} packages,
+which consists of choosing the correct set of commands to run for each
+package.  OCaml packages can expect many different commands to be run.  This
+build system will try some of them.
+
+When the package has a @file{setup.ml} file present at the top-level, it
+will run @code{ocaml setup.ml -configure}, @code{ocaml setup.ml -build} and
 @code{ocaml setup.ml -install}.  The build system will assume that this file
-was generated by @uref{http://oasis.forge.ocamlcore.org/, OASIS} and will take
-care of setting the prefix and enabling tests if they are not disabled.  You
-can pass configure and build flags with the @code{#:configure-flags} and
address@hidden:build-flags}.  The @code{#:test-flags} key can be passed to 
change the
-set of flags used to enable tests.  The @code{#:use-make?} key can be used to
-bypass this system in the build and install phases.
+was generated by @uref{http://oasis.forge.ocamlcore.org/, OASIS} and will
+take care of setting the prefix and enabling tests if they are not
+disabled.  You can pass configure and build flags with the
address@hidden:configure-flags} and @code{#:build-flags}.  The 
@code{#:test-flags}
+key can be passed to change the set of flags used to enable tests.  The
address@hidden:use-make?} key can be used to bypass this system in the build and
+install phases.
 
 When the package has a @file{configure} file, it is assumed that it is a
-hand-made configure script that requires a different argument format than
-in the @code{gnu-build-system}.  You can add more flags with the
+hand-made configure script that requires a different argument format than in
+the @code{gnu-build-system}.  You can add more flags with the
 @code{#:configure-flags} key.
 
 When the package has a @file{Makefile} file (or @code{#:use-make?} is
@@ -4519,10 +4693,10 @@ install phases with the @code{#:make-flags} key.
 Finally, some packages do not have these files and use a somewhat standard
 location for its build system.  In that case, the build system will run
 @code{ocaml pkg/pkg.ml} or @code{ocaml pkg/build.ml} and take care of
-providing the path to the required findlib module.  Additional flags can
-be passed via the @code{#:build-flags} key.  Install is taken care of by
address@hidden  In this case, the @code{opam} package must
-be added to the @code{native-inputs} field of the package definition.
+providing the path to the required findlib module.  Additional flags can be
+passed via the @code{#:build-flags} key.  Install is taken care of by
address@hidden  In this case, the @code{opam} package must be
+added to the @code{native-inputs} field of the package definition.
 
 Note that most OCaml packages assume they will be installed in the same
 directory as OCaml, which is not what we want in guix.  In particular, they
@@ -4536,36 +4710,35 @@ variable points to @file{lib/ocaml/site-lib/stubslibs} 
and this is where
 @defvr {Scheme Variable} python-build-system
 This variable is exported by @code{(guix build-system python)}.  It
 implements the more or less standard build procedure used by Python
-packages, which consists in running @code{python setup.py build} and
-then @code{python setup.py install --prefix=/gnu/store/@dots{}}.
+packages, which consists in running @code{python setup.py build} and then
address@hidden setup.py install --prefix=/gnu/store/@dots{}}.
 
-For packages that install stand-alone Python programs under @code{bin/},
-it takes care of wrapping these programs so that their @code{PYTHONPATH}
+For packages that install stand-alone Python programs under @code{bin/}, it
+takes care of wrapping these programs so that their @code{PYTHONPATH}
 environment variable points to all the Python libraries they depend on.
 
-Which Python package is used to perform the build can be specified with
-the @code{#:python} parameter.  This is a useful way to force a package
-to be built for a specific version of the Python interpreter, which
-might be necessary if the package is only compatible with a single
-interpreter version.
+Which Python package is used to perform the build can be specified with the
address@hidden:python} parameter.  This is a useful way to force a package to be
+built for a specific version of the Python interpreter, which might be
+necessary if the package is only compatible with a single interpreter
+version.
 
-By default guix calls @code{setup.py} under control of
address@hidden, much like @command{pip} does.  Some packages are not
-compatible with setuptools (and pip), thus you can disable this by
-setting the @code{#:use-setuptools} parameter to @code{#f}.
+By default guix calls @code{setup.py} under control of @code{setuptools},
+much like @command{pip} does.  Some packages are not compatible with
+setuptools (and pip), thus you can disable this by setting the
address@hidden:use-setuptools} parameter to @code{#f}.
 @end defvr
 
 @defvr {Scheme Variable} perl-build-system
-This variable is exported by @code{(guix build-system perl)}.  It
-implements the standard build procedure for Perl packages, which either
-consists in running @code{perl Build.PL --prefix=/gnu/store/@dots{}},
-followed by @code{Build} and @code{Build install}; or in running
address@hidden Makefile.PL PREFIX=/gnu/store/@dots{}}, followed by
address@hidden and @code{make install}, depending on which of
address@hidden or @code{Makefile.PL} is present in the package
-distribution.  Preference is given to the former if both @code{Build.PL}
-and @code{Makefile.PL} exist in the package distribution.  This
-preference can be reversed by specifying @code{#t} for the
+This variable is exported by @code{(guix build-system perl)}.  It implements
+the standard build procedure for Perl packages, which either consists in
+running @code{perl Build.PL --prefix=/gnu/store/@dots{}}, followed by
address@hidden and @code{Build install}; or in running @code{perl Makefile.PL
+PREFIX=/gnu/store/@dots{}}, followed by @code{make} and @code{make install},
+depending on which of @code{Build.PL} or @code{Makefile.PL} is present in
+the package distribution.  Preference is given to the former if both
address@hidden and @code{Makefile.PL} exist in the package distribution.
+This preference can be reversed by specifying @code{#t} for the
 @code{#:make-maker?} parameter.
 
 The initial @code{perl Makefile.PL} or @code{perl Build.PL} invocation
@@ -4576,46 +4749,45 @@ Which Perl package is used can be specified with 
@code{#:perl}.
 @end defvr
 
 @defvr {Scheme Variable} r-build-system
-This variable is exported by @code{(guix build-system r)}.  It
-implements the build procedure used by @uref{http://r-project.org, R}
-packages, which essentially is little more than running @code{R CMD
-INSTALL --library=/gnu/store/@dots{}} in an environment where
address@hidden contains the paths to all R package inputs.  Tests
-are run after installation using the R function
address@hidden::testInstalledPackage}.
+This variable is exported by @code{(guix build-system r)}.  It implements
+the build procedure used by @uref{http://r-project.org, R} packages, which
+essentially is little more than running @code{R CMD INSTALL
+--library=/gnu/store/@dots{}} in an environment where @code{R_LIBS_SITE}
+contains the paths to all R package inputs.  Tests are run after
+installation using the R function @code{tools::testInstalledPackage}.
 @end defvr
 
 @defvr {Scheme Variable} texlive-build-system
-This variable is exported by @code{(guix build-system texlive)}.  It is
-used to build TeX packages in batch mode with a specified engine.  The
-build system sets the @code{TEXINPUTS} variable to find all TeX source
-files in the inputs.
+This variable is exported by @code{(guix build-system texlive)}.  It is used
+to build TeX packages in batch mode with a specified engine.  The build
+system sets the @code{TEXINPUTS} variable to find all TeX source files in
+the inputs.
 
 By default it runs @code{luatex} on all files ending on @code{ins}.  A
-different engine and format can be specified with the
address@hidden:tex-format} argument.  Different build targets can be specified
-with the @code{#:build-targets} argument, which expects a list of file
-names.  The build system adds only @code{texlive-bin} and
address@hidden (both from @code{(gnu packages tex}) to the
-inputs.  Both can be overridden with the arguments @code{#:texlive-bin}
-and @code{#:texlive-latex-base}, respectively.
-
-The @code{#:tex-directory} parameter tells the build system where to
-install the built files under the texmf tree.
+different engine and format can be specified with the @code{#:tex-format}
+argument.  Different build targets can be specified with the
address@hidden:build-targets} argument, which expects a list of file names.  The
+build system adds only @code{texlive-bin} and @code{texlive-latex-base}
+(both from @code{(gnu packages tex}) to the inputs.  Both can be overridden
+with the arguments @code{#:texlive-bin} and @code{#:texlive-latex-base},
+respectively.
+
+The @code{#:tex-directory} parameter tells the build system where to install
+the built files under the texmf tree.
 @end defvr
 
 @defvr {Scheme Variable} ruby-build-system
-This variable is exported by @code{(guix build-system ruby)}.  It
-implements the RubyGems build procedure used by Ruby packages, which
-involves running @code{gem build} followed by @code{gem install}.
-
-The @code{source} field of a package that uses this build system
-typically references a gem archive, since this is the format that Ruby
-developers use when releasing their software.  The build system unpacks
-the gem archive, potentially patches the source, runs the test suite,
-repackages the gem, and installs it.  Additionally, directories and
-tarballs may be referenced to allow building unreleased gems from Git or
-a traditional source release tarball.
+This variable is exported by @code{(guix build-system ruby)}.  It implements
+the RubyGems build procedure used by Ruby packages, which involves running
address@hidden build} followed by @code{gem install}.
+
+The @code{source} field of a package that uses this build system typically
+references a gem archive, since this is the format that Ruby developers use
+when releasing their software.  The build system unpacks the gem archive,
+potentially patches the source, runs the test suite, repackages the gem, and
+installs it.  Additionally, directories and tarballs may be referenced to
+allow building unreleased gems from Git or a traditional source release
+tarball.
 
 Which Ruby package is used can be specified with the @code{#:ruby}
 parameter.  A list of additional flags to be passed to the @command{gem}
@@ -4623,27 +4795,25 @@ command can be specified with the @code{#:gem-flags} 
parameter.
 @end defvr
 
 @defvr {Scheme Variable} waf-build-system
-This variable is exported by @code{(guix build-system waf)}.  It
-implements a build procedure around the @code{waf} script.  The common
+This variable is exported by @code{(guix build-system waf)}.  It implements
+a build procedure around the @code{waf} script.  The common
 address@hidden, @code{build}, and @code{install}---are
-implemented by passing their names as arguments to the @code{waf}
-script.
+implemented by passing their names as arguments to the @code{waf} script.
 
-The @code{waf} script is executed by the Python interpreter.  Which
-Python package is used to run the script can be specified with the
address@hidden:python} parameter.
+The @code{waf} script is executed by the Python interpreter.  Which Python
+package is used to run the script can be specified with the @code{#:python}
+parameter.
 @end defvr
 
 @defvr {Scheme Variable} scons-build-system
 This variable is exported by @code{(guix build-system scons)}.  It
 implements the build procedure used by the SCons software construction
-tool.  This build system runs @code{scons} to build the package,
address@hidden test} to run tests, and then @code{scons install} to install
-the package.
+tool.  This build system runs @code{scons} to build the package, @code{scons
+test} to run tests, and then @code{scons install} to install the package.
 
 Additional flags to be passed to @code{scons} can be specified with the
address@hidden:scons-flags} parameter.  The version of Python used to run SCons
-can be specified by selecting the appropriate SCons package with the
address@hidden:scons-flags} parameter.  The version of Python used to run SCons 
can
+be specified by selecting the appropriate SCons package with the
 @code{#:scons} parameter.
 @end defvr
 
@@ -4651,50 +4821,49 @@ can be specified by selecting the appropriate SCons 
package with the
 This variable is exported by @code{(guix build-system haskell)}.  It
 implements the Cabal build procedure used by Haskell packages, which
 involves running @code{runhaskell Setup.hs configure
---prefix=/gnu/store/@dots{}} and @code{runhaskell Setup.hs build}.
-Instead of installing the package by running @code{runhaskell Setup.hs
-install}, to avoid trying to register libraries in the read-only
-compiler store directory, the build system uses @code{runhaskell
-Setup.hs copy}, followed by @code{runhaskell Setup.hs register}.  In
-addition, the build system generates the package documentation by
-running @code{runhaskell Setup.hs haddock}, unless @code{#:haddock? #f}
-is passed.  Optional Haddock parameters can be passed with the help of
-the @code{#:haddock-flags} parameter.  If the file @code{Setup.hs} is
-not found, the build system looks for @code{Setup.lhs} instead.
+--prefix=/gnu/store/@dots{}} and @code{runhaskell Setup.hs build}.  Instead
+of installing the package by running @code{runhaskell Setup.hs install}, to
+avoid trying to register libraries in the read-only compiler store
+directory, the build system uses @code{runhaskell Setup.hs copy}, followed
+by @code{runhaskell Setup.hs register}.  In addition, the build system
+generates the package documentation by running @code{runhaskell Setup.hs
+haddock}, unless @code{#:haddock? #f} is passed.  Optional Haddock
+parameters can be passed with the help of the @code{#:haddock-flags}
+parameter.  If the file @code{Setup.hs} is not found, the build system looks
+for @code{Setup.lhs} instead.
 
 Which Haskell compiler is used can be specified with the @code{#:haskell}
 parameter which defaults to @code{ghc}.
 @end defvr
 
 @defvr {Scheme Variable} dub-build-system
-This variable is exported by @code{(guix build-system dub)}.  It
-implements the Dub build procedure used by D packages, which
-involves running @code{dub build} and @code{dub run}.
-Installation is done by copying the files manually.
+This variable is exported by @code{(guix build-system dub)}.  It implements
+the Dub build procedure used by D packages, which involves running @code{dub
+build} and @code{dub run}.  Installation is done by copying the files
+manually.
 
-Which D compiler is used can be specified with the @code{#:ldc}
-parameter which defaults to @code{ldc}.
+Which D compiler is used can be specified with the @code{#:ldc} parameter
+which defaults to @code{ldc}.
 @end defvr
 
 @defvr {Scheme Variable} emacs-build-system
 This variable is exported by @code{(guix build-system emacs)}.  It
-implements an installation procedure similar to the packaging system
-of Emacs itself (@pxref{Packages,,, emacs, The GNU Emacs Manual}).
-
-It first creates the @address@hidden file, then it
-byte compiles all Emacs Lisp files.  Differently from the Emacs
-packaging system, the Info documentation files are moved to the standard
-documentation directory and the @file{dir} file is deleted.  Each
-package is installed in its own directory under
address@hidden/emacs/site-lisp/guix.d}.
+implements an installation procedure similar to the packaging system of
+Emacs itself (@pxref{Packages,,, emacs, The GNU Emacs Manual}).
+
+It first creates the @address@hidden file, then it byte
+compiles all Emacs Lisp files.  Differently from the Emacs packaging system,
+the Info documentation files are moved to the standard documentation
+directory and the @file{dir} file is deleted.  Each package is installed in
+its own directory under @file{share/emacs/site-lisp/guix.d}.
 @end defvr
 
 @defvr {Scheme Variable} font-build-system
-This variable is exported by @code{(guix build-system font)}.  It
-implements an installation procedure for font packages where upstream
-provides pre-compiled TrueType, OpenType, etc. font files that merely
-need to be copied into place.  It copies font files to standard
-locations in the output directory.
+This variable is exported by @code{(guix build-system font)}.  It implements
+an installation procedure for font packages where upstream provides
+pre-compiled TrueType, OpenType, etc. font files that merely need to be
+copied into place.  It copies font files to standard locations in the output
+directory.
 @end defvr
 
 @defvr {Scheme Variable} meson-build-system
@@ -4702,11 +4871,11 @@ This variable is exported by @code{(guix build-system 
meson)}.  It
 implements the build procedure for packages that use
 @url{http://mesonbuild.com, Meson} as their build system.
 
-It adds both Meson and @uref{https://ninja-build.org/, Ninja} to the set
-of inputs, and they can be changed with the parameters @code{#:meson}
-and @code{#:ninja} if needed.  The default Meson is
address@hidden, which is special because it doesn't clear the
address@hidden of binaries and libraries when they are installed.
+It adds both Meson and @uref{https://ninja-build.org/, Ninja} to the set of
+inputs, and they can be changed with the parameters @code{#:meson} and
address@hidden:ninja} if needed.  The default Meson is @code{meson-for-build},
+which is special because it doesn't clear the @code{RUNPATH} of binaries and
+libraries when they are installed.
 
 This build system is an extension of @var{gnu-build-system}, but with the
 following phases changed to some specific for Meson:
@@ -4723,8 +4892,8 @@ The phase runs @code{ninja} to build the package in 
parallel by default, but
 this can be changed with @code{#:parallel-build?}.
 
 @item check
-The phase runs @code{ninja} with the target specified in @code{#:test-target},
-which is @code{"test"} by default.
+The phase runs @code{ninja} with the target specified in
address@hidden:test-target}, which is @code{"test"} by default.
 
 @item install
 The phase runs @code{ninja install} and can not be changed.
@@ -4735,8 +4904,8 @@ Apart from that, the build system also adds the following 
phases:
 @table @code
 
 @item fix-runpath
-This phase ensures that all binaries can find the libraries they need.
-It searches for required libraries in subdirectories of the package being
+This phase ensures that all binaries can find the libraries they need.  It
+searches for required libraries in subdirectories of the package being
 built, and adds those to @code{RUNPATH} where needed.  It also removes
 references to libraries left over from the build phase by
 @code{meson-for-build}, such as test dependencies, that aren't actually
@@ -4753,62 +4922,62 @@ is not enabled by default.  It can be enabled with 
@code{#:glib-or-gtk?}.
 @end defvr
 
 Lastly, for packages that do not need anything as sophisticated, a
-``trivial'' build system is provided.  It is trivial in the sense that
-it provides basically no support: it does not pull any implicit inputs,
-and does not have a notion of build phases.
+``trivial'' build system is provided.  It is trivial in the sense that it
+provides basically no support: it does not pull any implicit inputs, and
+does not have a notion of build phases.
 
 @defvr {Scheme Variable} trivial-build-system
 This variable is exported by @code{(guix build-system trivial)}.
 
-This build system requires a @code{#:builder} argument.  This argument
-must be a Scheme expression that builds the package output(s)---as
-with @code{build-expression->derivation} (@pxref{Derivations,
+This build system requires a @code{#:builder} argument.  This argument must
+be a Scheme expression that builds the package output(s)---as with
address@hidden>derivation} (@pxref{Ableitungen,
 @code{build-expression->derivation}}).
 @end defvr
 
address@hidden The Store
address@hidden The Store
address@hidden Der Store
address@hidden Der Store
 
address@hidden store
address@hidden Store
 @cindex store items
 @cindex store paths
 
-Conceptually, the @dfn{store} is the place where derivations that have
-been built successfully are stored---by default, @file{/gnu/store}.
+Conceptually, the @dfn{store} is the place where derivations that have been
+built successfully are stored---by default, @file{/gnu/store}.
 Sub-directories in the store are referred to as @dfn{store items} or
 sometimes @dfn{store paths}.  The store has an associated database that
-contains information such as the store paths referred to by each store
-path, and the list of @emph{valid} store items---results of successful
-builds.  This database resides in @address@hidden/guix/db},
-where @var{localstatedir} is the state directory specified @i{via}
+contains information such as the store paths referred to by each store path,
+and the list of @emph{valid} store items---results of successful builds.
+This database resides in @address@hidden/guix/db}, where
address@hidden is the state directory specified @i{via}
 @option{--localstatedir} at configure time, usually @file{/var}.
 
 The store is @emph{always} accessed by the daemon on behalf of its clients
-(@pxref{Invoking guix-daemon}).  To manipulate the store, clients
-connect to the daemon over a Unix-domain socket, send requests to it,
-and read the result---these are remote procedure calls, or RPCs.
-
address@hidden Note
-Users must @emph{never} modify files under @file{/gnu/store} directly.
-This would lead to inconsistencies and break the immutability
-assumptions of Guix's functional model (@pxref{Introduction}).
-
address@hidden guix gc, @command{guix gc --verify}}, for information on
-how to check the integrity of the store and attempt recovery from
-accidental modifications.
+(@pxref{Aufruf des guix-daemon}).  To manipulate the store, clients connect to
+the daemon over a Unix-domain socket, send requests to it, and read the
+result---these are remote procedure calls, or RPCs.
+
address@hidden Anmerkung
+Users must @emph{never} modify files under @file{/gnu/store} directly.  This
+would lead to inconsistencies and break the immutability assumptions of
+Guix's functional model (@pxref{Einführung}).
+
address@hidden von guix gc, @command{guix gc --verify}}, for information on how
+to check the integrity of the store and attempt recovery from accidental
+modifications.
 @end quotation
 
-The @code{(guix store)} module provides procedures to connect to the
-daemon, and to perform RPCs.  These are described below.  By default,
address@hidden, and thus all the @command{guix} commands,
-connect to the local daemon or to the URI specified by the
address@hidden environment variable.
+The @code{(guix store)} module provides procedures to connect to the daemon,
+and to perform RPCs.  These are described below.  By default,
address@hidden, and thus all the @command{guix} commands, connect to
+the local daemon or to the URI specified by the @code{GUIX_DAEMON_SOCKET}
+environment variable.
 
 @defvr {Environment Variable} GUIX_DAEMON_SOCKET
 When set, the value of this variable should be a file name or a URI
 designating the daemon endpoint.  When it is a file name, it denotes a
-Unix-domain socket to connect to.  In addition to file names, the
-supported URI schemes are:
+Unix-domain socket to connect to.  In addition to file names, the supported
+URI schemes are:
 
 @table @code
 @item file
@@ -4818,13 +4987,13 @@ These are for Unix-domain sockets.
 @file{/var/guix/daemon-socket/socket}.
 
 @item guix
address@hidden daemon, remote access
address@hidden remote access to the daemon
address@hidden daemon, cluster setup
address@hidden clusters, daemon setup
address@hidden Daemon, Fernzugriff
address@hidden Fernzugriff auf den Daemon
address@hidden Daemon, Einrichten auf Clustern
address@hidden Cluster, Einrichtung des Daemons
 These URIs denote connections over TCP/IP, without encryption nor
-authentication of the remote host.  The URI must specify the host name
-and optionally a port number (by default port 44146 is used):
+authentication of the remote host.  The URI must specify the host name and
+optionally a port number (by default port 44146 is used):
 
 @example
 guix://master.guix.example.org:1234
@@ -4834,38 +5003,38 @@ This setup is suitable on local networks, such as 
clusters, where only
 trusted nodes may connect to the build daemon at
 @code{master.guix.example.org}.
 
-The @code{--listen} option of @command{guix-daemon} can be used to
-instruct it to listen for TCP connections (@pxref{Invoking guix-daemon,
+The @code{--listen} option of @command{guix-daemon} can be used to instruct
+it to listen for TCP connections (@pxref{Aufruf des guix-daemon,
 @code{--listen}}).
 
 @item ssh
 @cindex SSH access to build daemons
-These URIs allow you to connect to a remote daemon over
address@hidden feature requires Guile-SSH (@pxref{Requirements}).}.
-A typical URL might look like this:
+These URIs allow you to connect to a remote daemon over address@hidden
+feature requires Guile-SSH (@pxref{Voraussetzungen}).}.  A typical URL might
+look like this:
 
 @example
 ssh://charlie@@guix.example.org:22
 @end example
 
-As for @command{guix copy}, the usual OpenSSH client configuration files
-are honored (@pxref{Invoking guix copy}).
+As for @command{guix copy}, the usual OpenSSH client configuration files are
+honored (@pxref{Aufruf von guix copy}).
 @end table
 
 Additional URI schemes may be supported in the future.
 
 @c XXX: Remove this note when the protocol incurs fewer round trips
 @c and when (guix derivations) no longer relies on file system access.
address@hidden Note
-The ability to connect to remote build daemons is considered
-experimental as of @value{VERSION}.  Please get in touch with us to
-share any problems or suggestions you may have (@pxref{Contributing}).
address@hidden Anmerkung
+The ability to connect to remote build daemons is considered experimental as
+of @value{VERSION}.  Please get in touch with us to share any problems or
+suggestions you may have (@pxref{Mitwirken}).
 @end quotation
 @end defvr
 
 @deffn {Scheme Procedure} open-connection address@hidden [#:reserve-space? #t]
-Connect to the daemon over the Unix-domain socket at @var{uri} (a string).  
When
address@hidden is true, instruct it to reserve a little bit of
+Connect to the daemon over the Unix-domain socket at @var{uri} (a string).
+When @var{reserve-space?} is true, instruct it to reserve a little bit of
 extra space on the file system so that the garbage collector can still
 operate should the disk become full.  Return a server object.
 
@@ -4882,15 +5051,13 @@ This variable is bound to a SRFI-39 parameter, which 
refers to the port
 where build and error logs sent by the daemon should be written.
 @end defvr
 
-Procedures that make RPCs all take a server object as their first
-argument.
+Procedures that make RPCs all take a server object as their first argument.
 
 @deffn {Scheme Procedure} valid-path? @var{server} @var{path}
 @cindex invalid store items
-Return @code{#t} when @var{path} designates a valid store item and
address@hidden otherwise (an invalid item may exist on disk but still be
-invalid, for instance because it is the result of an aborted or failed
-build.)
+Return @code{#t} when @var{path} designates a valid store item and @code{#f}
+otherwise (an invalid item may exist on disk but still be invalid, for
+instance because it is the result of an aborted or failed build.)
 
 A @code{&nix-protocol-error} condition is raised if @var{path} is not
 prefixed by the store directory (@file{/gnu/store}).
@@ -4903,26 +5070,25 @@ resulting store path.
 @end deffn
 
 @deffn {Scheme Procedure} build-derivations @var{server} @var{derivations}
-Build @var{derivations} (a list of @code{<derivation>} objects or
-derivation paths), and return when the worker is done building them.
-Return @code{#t} on success.
+Build @var{derivations} (a list of @code{<derivation>} objects or derivation
+paths), and return when the worker is done building them.  Return @code{#t}
+on success.
 @end deffn
 
 Note that the @code{(guix monads)} module provides a monad as well as
-monadic versions of the above procedures, with the goal of making it
-more convenient to work with code that accesses the store (@pxref{The
-Store Monad}).
+monadic versions of the above procedures, with the goal of making it more
+convenient to work with code that accesses the store (@pxref{Die 
Store-Monade}).
 
 @c FIXME
 @i{This section is currently incomplete.}
 
address@hidden Derivations
address@hidden Derivations
address@hidden Ableitungen
address@hidden Ableitungen
 
 @cindex derivations
-Low-level build actions and the environment in which they are performed
-are represented by @dfn{derivations}.  A derivation contains the
-following pieces of information:
+Low-level build actions and the environment in which they are performed are
+represented by @dfn{derivations}.  A derivation contains the following
+pieces of information:
 
 @itemize
 @item
@@ -4930,15 +5096,15 @@ The outputs of the derivation---derivations produce at 
least one file or
 directory in the store, but may produce more.
 
 @item
-The inputs of the derivations, which may be other derivations or plain
-files in the store (patches, build scripts, etc.)
+The inputs of the derivations, which may be other derivations or plain files
+in the store (patches, build scripts, etc.)
 
 @item
 The system type targeted by the derivation---e.g., @code{x86_64-linux}.
 
 @item
-The file name of a build script in the store, along with the arguments
-to be passed.
+The file name of a build script in the store, along with the arguments to be
+passed.
 
 @item
 A list of environment variables to be defined.
@@ -4946,76 +5112,71 @@ A list of environment variables to be defined.
 @end itemize
 
 @cindex derivation path
-Derivations allow clients of the daemon to communicate build actions to
-the store.  They exist in two forms: as an in-memory representation,
-both on the client- and daemon-side, and as files in the store whose
-name end in @code{.drv}---these files are referred to as @dfn{derivation
-paths}.  Derivations paths can be passed to the @code{build-derivations}
-procedure to perform the build actions they prescribe (@pxref{The
-Store}).
+Derivations allow clients of the daemon to communicate build actions to the
+store.  They exist in two forms: as an in-memory representation, both on the
+client- and daemon-side, and as files in the store whose name end in
address@hidden files are referred to as @dfn{derivation paths}.
+Derivations paths can be passed to the @code{build-derivations} procedure to
+perform the build actions they prescribe (@pxref{Der Store}).
 
 @cindex fixed-output derivations
-Operations such as file downloads and version-control checkouts for
-which the expected content hash is known in advance are modeled as
address@hidden derivations}.  Unlike regular derivations, the outputs
-of a fixed-output derivation are independent of its inputs---e.g., a
-source code download produces the same result regardless of the download
-method and tools being used.
+Operations such as file downloads and version-control checkouts for which
+the expected content hash is known in advance are modeled as
address@hidden derivations}.  Unlike regular derivations, the outputs of
+a fixed-output derivation are independent of its inputs---e.g., a source
+code download produces the same result regardless of the download method and
+tools being used.
 
 The @code{(guix derivations)} module provides a representation of
-derivations as Scheme objects, along with procedures to create and
-otherwise manipulate derivations.  The lowest-level primitive to create
-a derivation is the @code{derivation} procedure:
+derivations as Scheme objects, along with procedures to create and otherwise
+manipulate derivations.  The lowest-level primitive to create a derivation
+is the @code{derivation} procedure:
 
 @deffn {Scheme Procedure} derivation @var{store} @var{name} @var{builder} @
-  @var{args} [#:outputs '("out")] [#:hash #f] [#:hash-algo #f] @
-  [#:recursive? #f] [#:inputs '()] [#:env-vars '()] @
-  [#:system (%current-system)] [#:references-graphs #f] @
-  [#:allowed-references #f] [#:disallowed-references #f] @
-  [#:leaked-env-vars #f] [#:local-build? #f] @
-  [#:substitutable? #t]
-Build a derivation with the given arguments, and return the resulting
address@hidden<derivation>} object.
-
-When @var{hash} and @var{hash-algo} are given, a
address@hidden derivation} is created---i.e., one whose result is
-known in advance, such as a file download.  If, in addition,
address@hidden is true, then that fixed output may be an executable
-file or a directory and @var{hash} must be the hash of an archive
-containing this output.
-
-When @var{references-graphs} is true, it must be a list of file
-name/store path pairs.  In that case, the reference graph of each store
-path is exported in the build environment in the corresponding file, in
-a simple text format.
-
-When @var{allowed-references} is true, it must be a list of store items
-or outputs that the derivation's output may refer to.  Likewise,
address@hidden, if true, must be a list of things the
-outputs may @emph{not} refer to.
-
-When @var{leaked-env-vars} is true, it must be a list of strings
-denoting environment variables that are allowed to ``leak'' from the
-daemon's environment to the build environment.  This is only applicable
-to fixed-output derivations---i.e., when @var{hash} is true.  The main
-use is to allow variables such as @code{http_proxy} to be passed to
-derivations that download files.
-
-When @var{local-build?} is true, declare that the derivation is not a
-good candidate for offloading and should rather be built locally
-(@pxref{Daemon Offload Setup}).  This is the case for small derivations
-where the costs of data transfers would outweigh the benefits.
+  @var{args} [#:outputs '("out")] [#:hash #f] [#:hash-algo #f] @ [#:recursive?
+#f] [#:inputs '()] [#:env-vars '()] @ [#:system (%current-system)]
+[#:references-graphs #f] @ [#:allowed-references #f]
+[#:disallowed-references #f] @ [#:leaked-env-vars #f] [#:local-build? #f] @
+[#:substitutable? #t] Build a derivation with the given arguments, and
+return the resulting @code{<derivation>} object.
+
+When @var{hash} and @var{hash-algo} are given, a @dfn{fixed-output
+derivation} is created---i.e., one whose result is known in advance, such as
+a file download.  If, in addition, @var{recursive?} is true, then that fixed
+output may be an executable file or a directory and @var{hash} must be the
+hash of an archive containing this output.
+
+When @var{references-graphs} is true, it must be a list of file name/store
+path pairs.  In that case, the reference graph of each store path is
+exported in the build environment in the corresponding file, in a simple
+text format.
+
+When @var{allowed-references} is true, it must be a list of store items or
+outputs that the derivation's output may refer to.  Likewise,
address@hidden, if true, must be a list of things the outputs
+may @emph{not} refer to.
+
+When @var{leaked-env-vars} is true, it must be a list of strings denoting
+environment variables that are allowed to ``leak'' from the daemon's
+environment to the build environment.  This is only applicable to
+fixed-output derivations---i.e., when @var{hash} is true.  The main use is
+to allow variables such as @code{http_proxy} to be passed to derivations
+that download files.
+
+When @var{local-build?} is true, declare that the derivation is not a good
+candidate for offloading and should rather be built locally (@pxref{Auslagern 
des Daemons einrichten}).  This is the case for small derivations where the 
costs of
+data transfers would outweigh the benefits.
 
 When @var{substitutable?} is false, declare that substitutes of the
-derivation's output should not be used (@pxref{Substitutes}).  This is
+derivation's output should not be used (@pxref{Substitute}).  This is
 useful, for instance, when building packages that capture details of the
 host CPU instruction set.
 @end deffn
 
 @noindent
-Here's an example with a shell script as its builder, assuming
address@hidden is an open connection to the daemon, and @var{bash} points
-to a Bash executable in the store:
+Here's an example with a shell script as its builder, assuming @var{store}
+is an open connection to the daemon, and @var{bash} points to a Bash
+executable in the store:
 
 @lisp
 (use-modules (guix utils)
@@ -5032,41 +5193,38 @@ to a Bash executable in the store:
 @result{} #<derivation /gnu/store/@dots{}-foo.drv => /gnu/store/@dots{}-foo>
 @end lisp
 
-As can be guessed, this primitive is cumbersome to use directly.  A
-better approach is to write build scripts in Scheme, of course!  The
-best course of action for that is to write the build code as a
-``G-expression'', and to pass it to @code{gexp->derivation}.  For more
-information, @pxref{G-Expressions}.
+As can be guessed, this primitive is cumbersome to use directly.  A better
+approach is to write build scripts in Scheme, of course! The best course of
+action for that is to write the build code as a ``G-expression'', and to
+pass it to @code{gexp->derivation}.  For more information,
address@hidden
 
 Once upon a time, @code{gexp->derivation} did not exist and constructing
 derivations with build code written in Scheme was achieved with
address@hidden>derivation}, documented below.  This procedure
-is now deprecated in favor of the much nicer @code{gexp->derivation}.
address@hidden>derivation}, documented below.  This procedure is
+now deprecated in favor of the much nicer @code{gexp->derivation}.
 
 @deffn {Scheme Procedure} build-expression->derivation @var{store} @
-       @var{name} @var{exp} @
-       [#:system (%current-system)] [#:inputs '()] @
-       [#:outputs '("out")] [#:hash #f] [#:hash-algo #f] @
-       [#:recursive? #f] [#:env-vars '()] [#:modules '()] @
-       [#:references-graphs #f] [#:allowed-references #f] @
-       [#:disallowed-references #f] @
-       [#:local-build? #f] [#:substitutable? #t] [#:guile-for-build #f]
-Return a derivation that executes Scheme expression @var{exp} as a
-builder for derivation @var{name}.  @var{inputs} must be a list of
address@hidden(name drv-path sub-drv)} tuples; when @var{sub-drv} is omitted,
address@hidden"out"} is assumed.  @var{modules} is a list of names of Guile
-modules from the current search path to be copied in the store,
-compiled, and made available in the load path during the execution of
address@hidden, @code{((guix build utils) (guix build
-gnu-build-system))}.
-
address@hidden is evaluated in an environment where @code{%outputs} is bound
-to a list of output/path pairs, and where @code{%build-inputs} is bound
-to a list of string/output-path pairs made from @var{inputs}.
-Optionally, @var{env-vars} is a list of string pairs specifying the name
-and value of environment variables visible to the builder.  The builder
-terminates by passing the result of @var{exp} to @code{exit}; thus, when
address@hidden returns @code{#f}, the build is considered to have failed.
+       @var{name} @var{exp} @ [#:system (%current-system)] [#:inputs '()] @
+[#:outputs '("out")] [#:hash #f] [#:hash-algo #f] @ [#:recursive? #f]
+[#:env-vars '()] [#:modules '()] @ [#:references-graphs #f]
+[#:allowed-references #f] @ [#:disallowed-references #f] @ [#:local-build?
+#f] [#:substitutable? #t] [#:guile-for-build #f] Return a derivation that
+executes Scheme expression @var{exp} as a builder for derivation
address@hidden  @var{inputs} must be a list of @code{(name drv-path sub-drv)}
+tuples; when @var{sub-drv} is omitted, @code{"out"} is assumed.
address@hidden is a list of names of Guile modules from the current search
+path to be copied in the store, compiled, and made available in the load
+path during the execution of @var{exp}---e.g., @code{((guix build utils)
+(guix build gnu-build-system))}.
+
address@hidden is evaluated in an environment where @code{%outputs} is bound to 
a
+list of output/path pairs, and where @code{%build-inputs} is bound to a list
+of string/output-path pairs made from @var{inputs}.  Optionally,
address@hidden is a list of string pairs specifying the name and value of
+environment variables visible to the builder.  The builder terminates by
+passing the result of @var{exp} to @code{exit}; thus, when @var{exp} returns
address@hidden, the build is considered to have failed.
 
 @var{exp} is built using @var{guile-for-build} (a derivation).  When
 @var{guile-for-build} is omitted or is @code{#f}, the value of the
@@ -5074,8 +5232,7 @@ terminates by passing the result of @var{exp} to 
@code{exit}; thus, when
 
 See the @code{derivation} procedure for the meaning of
 @var{references-graphs}, @var{allowed-references},
address@hidden, @var{local-build?}, and
address@hidden
address@hidden, @var{local-build?}, and @var{substitutable?}.
 @end deffn
 
 @noindent
@@ -5094,33 +5251,32 @@ containing one file:
 @end lisp
 
 
address@hidden The Store Monad
address@hidden The Store Monad
address@hidden Die Store-Monade
address@hidden Die Store-Monade
 
 @cindex monad
 
-The procedures that operate on the store described in the previous
-sections all take an open connection to the build daemon as their first
-argument.  Although the underlying model is functional, they either have
-side effects or depend on the current state of the store.
+The procedures that operate on the store described in the previous sections
+all take an open connection to the build daemon as their first argument.
+Although the underlying model is functional, they either have side effects
+or depend on the current state of the store.
 
 The former is inconvenient: the connection to the build daemon has to be
 carried around in all those functions, making it impossible to compose
 functions that do not take that parameter with functions that do.  The
-latter can be problematic: since store operations have side effects
-and/or depend on external state, they have to be properly sequenced.
+latter can be problematic: since store operations have side effects and/or
+depend on external state, they have to be properly sequenced.
 
 @cindex monadic values
 @cindex monadic functions
 This is where the @code{(guix monads)} module comes in.  This module
 provides a framework for working with @dfn{monads}, and a particularly
-useful monad for our uses, the @dfn{store monad}.  Monads are a
-construct that allows two things: associating ``context'' with values
-(in our case, the context is the store), and building sequences of
-computations (here computations include accesses to the store).  Values
-in a monad---values that carry this additional context---are called
address@hidden values}; procedures that return such values are called
address@hidden procedures}.
+useful monad for our uses, the @dfn{store monad}.  Monads are a construct
+that allows two things: associating ``context'' with values (in our case,
+the context is the store), and building sequences of computations (here
+computations include accesses to the store).  Values in a monad---values
+that carry this additional context---are called @dfn{monadic values};
+procedures that return such values are called @dfn{monadic procedures}.
 
 Consider this ``normal'' procedure:
 
@@ -5134,8 +5290,8 @@ Consider this ``normal'' procedure:
                                   `(symlink ,sh %output))))
 @end example
 
-Using @code{(guix monads)} and @code{(guix gexp)}, it may be rewritten
-as a monadic function:
+Using @code{(guix monads)} and @code{(guix gexp)}, it may be rewritten as a
+monadic function:
 
 @example
 (define (sh-symlink)
@@ -5148,13 +5304,13 @@ as a monadic function:
 
 There are several things to note in the second version: the @code{store}
 parameter is now implicit and is ``threaded'' in the calls to the
address@hidden>derivation} and @code{gexp->derivation} monadic
-procedures, and the monadic value returned by @code{package->derivation}
-is @dfn{bound} using @code{mlet} instead of plain @code{let}.
address@hidden>derivation} and @code{gexp->derivation} monadic procedures,
+and the monadic value returned by @code{package->derivation} is @dfn{bound}
+using @code{mlet} instead of plain @code{let}.
 
-As it turns out, the call to @code{package->derivation} can even be
-omitted since it will take place implicitly, as we will see later
-(@pxref{G-Expressions}):
+As it turns out, the call to @code{package->derivation} can even be omitted
+since it will take place implicitly, as we will see later
+(@pxref{G-Ausdrücke}):
 
 @example
 (define (sh-symlink)
@@ -5166,9 +5322,9 @@ omitted since it will take place implicitly, as we will 
see later
 @c See
 @c <https://syntaxexclamation.wordpress.com/2014/06/26/escaping-continuations/>
 @c for the funny quote.
-Calling the monadic @code{sh-symlink} has no effect.  As someone once
-said, ``you exit a monad like you exit a building on fire: by running''.
-So, to exit the monad and get the desired effect, one must use
+Calling the monadic @code{sh-symlink} has no effect.  As someone once said,
+``you exit a monad like you exit a building on fire: by running''.  So, to
+exit the monad and get the desired effect, one must use
 @code{run-with-store}:
 
 @example
@@ -5178,8 +5334,8 @@ So, to exit the monad and get the desired effect, one 
must use
 
 Note that the @code{(guix monad-repl)} module extends the Guile REPL with
 new ``meta-commands'' to make it easier to deal with monadic procedures:
address@hidden, and @code{enter-store-monad}.  The former is used
-to ``run'' a single monadic value through the store:
address@hidden, and @code{enter-store-monad}.  The former is used to
+``run'' a single monadic value through the store:
 
 @example
 scheme@@(guile-user)> ,run-in-store (package->derivation hello)
@@ -5200,15 +5356,15 @@ scheme@@(guile-user)>
 @end example
 
 @noindent
-Note that non-monadic values cannot be returned in the
address@hidden REPL.
+Note that non-monadic values cannot be returned in the @code{store-monad}
+REPL.
 
-The main syntactic forms to deal with monads in general are provided by
-the @code{(guix monads)} module and are described below.
+The main syntactic forms to deal with monads in general are provided by the
address@hidden(guix monads)} module and are described below.
 
 @deffn {Scheme Syntax} with-monad @var{monad} @var{body} ...
-Evaluate any @code{>>=} or @code{return} forms in @var{body} as being
-in @var{monad}.
+Evaluate any @code{>>=} or @code{return} forms in @var{body} as being in
address@hidden
 @end deffn
 
 @deffn {Scheme Syntax} return @var{val}
@@ -5217,11 +5373,10 @@ Return a monadic value that encapsulates @var{val}.
 
 @deffn {Scheme Syntax} >>= @var{mval} @var{mproc} ...
 @dfn{Bind} monadic value @var{mval}, passing its ``contents'' to monadic
-procedures @address@hidden@footnote{This operation is commonly
-referred to as ``bind'', but that name denotes an unrelated procedure in
-Guile.  Thus we use this somewhat cryptic symbol inherited from the
-Haskell language.}.  There can be one @var{mproc} or several of them, as
-in this example:
+procedures @address@hidden@footnote{This operation is commonly referred
+to as ``bind'', but that name denotes an unrelated procedure in Guile.  Thus
+we use this somewhat cryptic symbol inherited from the Haskell language.}.
+There can be one @var{mproc} or several of them, as in this example:
 
 @example
 (run-with-state
@@ -5239,58 +5394,57 @@ in this example:
 @deffn {Scheme Syntax} mlet @var{monad} ((@var{var} @var{mval}) ...) @
        @var{body} ...
 @deffnx {Scheme Syntax} mlet* @var{monad} ((@var{var} @var{mval}) ...) @
-       @var{body} ...
-Bind the variables @var{var} to the monadic values @var{mval} in
address@hidden, which is a sequence of expressions.  As with the bind
-operator, this can be thought of as ``unpacking'' the raw, non-monadic
-value ``contained'' in @var{mval} and making @var{var} refer to that
-raw, non-monadic value within the scope of the @var{body}.  The form
-(@var{var} -> @var{val}) binds @var{var} to the ``normal'' value
address@hidden, as per @code{let}.  The binding operations occur in sequence
-from left to right.  The last expression of @var{body} must be a monadic
-expression, and its result will become the result of the @code{mlet} or
address@hidden when run in the @var{monad}.
+       @var{body} ...  Bind the variables @var{var} to the monadic values
address@hidden in @var{body}, which is a sequence of expressions.  As with the
+bind operator, this can be thought of as ``unpacking'' the raw, non-monadic
+value ``contained'' in @var{mval} and making @var{var} refer to that raw,
+non-monadic value within the scope of the @var{body}.  The form (@var{var}
+-> @var{val}) binds @var{var} to the ``normal'' value @var{val}, as per
address@hidden  The binding operations occur in sequence from left to right.
+The last expression of @var{body} must be a monadic expression, and its
+result will become the result of the @code{mlet} or @code{mlet*} when run in
+the @var{monad}.
 
 @code{mlet*} is to @code{mlet} what @code{let*} is to @code{let}
 (@pxref{Local Bindings,,, guile, GNU Guile Reference Manual}).
 @end deffn
 
 @deffn {Scheme System} mbegin @var{monad} @var{mexp} ...
-Bind @var{mexp} and the following monadic expressions in sequence,
-returning the result of the last expression.  Every expression in the
-sequence must be a monadic expression.
+Bind @var{mexp} and the following monadic expressions in sequence, returning
+the result of the last expression.  Every expression in the sequence must be
+a monadic expression.
 
-This is akin to @code{mlet}, except that the return values of the
-monadic expressions are ignored.  In that sense, it is analogous to
address@hidden, but applied to monadic expressions.
+This is akin to @code{mlet}, except that the return values of the monadic
+expressions are ignored.  In that sense, it is analogous to @code{begin},
+but applied to monadic expressions.
 @end deffn
 
 @deffn {Scheme System} mwhen @var{condition} @var{mexp0} @var{mexp*} ...
-When @var{condition} is true, evaluate the sequence of monadic
-expressions @address@hidden as in an @code{mbegin}.  When
address@hidden is false, return @code{*unspecified*} in the current
-monad.  Every expression in the sequence must be a monadic expression.
+When @var{condition} is true, evaluate the sequence of monadic expressions
address@hidden@var{mexp*} as in an @code{mbegin}.  When @var{condition} is
+false, return @code{*unspecified*} in the current monad.  Every expression
+in the sequence must be a monadic expression.
 @end deffn
 
 @deffn {Scheme System} munless @var{condition} @var{mexp0} @var{mexp*} ...
-When @var{condition} is false, evaluate the sequence of monadic
-expressions @address@hidden as in an @code{mbegin}.  When
address@hidden is true, return @code{*unspecified*} in the current
-monad.  Every expression in the sequence must be a monadic expression.
+When @var{condition} is false, evaluate the sequence of monadic expressions
address@hidden@var{mexp*} as in an @code{mbegin}.  When @var{condition} is
+true, return @code{*unspecified*} in the current monad.  Every expression in
+the sequence must be a monadic expression.
 @end deffn
 
 @cindex state monad
-The @code{(guix monads)} module provides the @dfn{state monad}, which
-allows an additional value---the state---to be @emph{threaded} through
-monadic procedure calls.
+The @code{(guix monads)} module provides the @dfn{state monad}, which allows
+an additional value---the state---to be @emph{threaded} through monadic
+procedure calls.
 
 @defvr {Scheme Variable} %state-monad
-The state monad.  Procedures in the state monad can access and change
-the state that is threaded.
+The state monad.  Procedures in the state monad can access and change the
+state that is threaded.
 
-Consider the example below.  The @code{square} procedure returns a value
-in the state monad.  It returns the square of its argument, but also
-increments the current state value:
+Consider the example below.  The @code{square} procedure returns a value in
+the state monad.  It returns the square of its argument, but also increments
+the current state value:
 
 @example
 (define (square x)
@@ -5318,13 +5472,13 @@ monadic value.
 @end deffn
 
 @deffn {Monadic Procedure} state-push @var{value}
-Push @var{value} to the current state, which is assumed to be a list,
-and return the previous state as a monadic value.
+Push @var{value} to the current state, which is assumed to be a list, and
+return the previous state as a monadic value.
 @end deffn
 
 @deffn {Monadic Procedure} state-pop
-Pop a value from the current state and return it as a monadic value.
-The state is assumed to be a list.
+Pop a value from the current state and return it as a monadic value.  The
+state is assumed to be a list.
 @end deffn
 
 @deffn {Scheme Procedure} run-with-state @var{mval} address@hidden
@@ -5332,8 +5486,8 @@ Run monadic value @var{mval} starting with @var{state} as 
the initial
 state.  Return two values: the resulting value, and the resulting state.
 @end deffn
 
-The main interface to the store monad, provided by the @code{(guix
-store)} module, is as follows.
+The main interface to the store monad, provided by the @code{(guix store)}
+module, is as follows.
 
 @defvr {Scheme Variable} %store-monad
 The store monad---an alias for @var{%state-monad}.
@@ -5344,31 +5498,31 @@ passing it to the @code{run-with-store} procedure (see 
below.)
 @end defvr
 
 @deffn {Scheme Procedure} run-with-store @var{store} @var{mval} 
[#:guile-for-build] [#:system (%current-system)]
-Run @var{mval}, a monadic value in the store monad, in @var{store}, an
-open store connection.
+Run @var{mval}, a monadic value in the store monad, in @var{store}, an open
+store connection.
 @end deffn
 
 @deffn {Monadic Procedure} text-file @var{name} @var{text} address@hidden
 Return as a monadic value the absolute file name in the store of the file
-containing @var{text}, a string.  @var{references} is a list of store items 
that the
-resulting text file refers to; it defaults to the empty list.
+containing @var{text}, a string.  @var{references} is a list of store items
+that the resulting text file refers to; it defaults to the empty list.
 @end deffn
 
 @deffn {Monadic Procedure} binary-file @var{name} @var{data} address@hidden
 Return as a monadic value the absolute file name in the store of the file
 containing @var{data}, a bytevector.  @var{references} is a list of store
-items that the resulting binary file refers to; it defaults to the empty list.
+items that the resulting binary file refers to; it defaults to the empty
+list.
 @end deffn
 
 @deffn {Monadic Procedure} interned-file @var{file} address@hidden @
-         [#:recursive? #t] [#:select? (const #t)]
-Return the name of @var{file} once interned in the store.  Use
address@hidden as its store name, or the basename of @var{file} if
address@hidden is omitted.
+         [#:recursive? #t] [#:select? (const #t)] Return the name of 
@var{file} once
+interned in the store.  Use @var{name} as its store name, or the basename of
address@hidden if @var{name} is omitted.
 
 When @var{recursive?} is true, the contents of @var{file} are added
-recursively; if @var{file} designates a flat file and @var{recursive?}
-is true, its contents are added, and its permission bits are kept.
+recursively; if @var{file} designates a flat file and @var{recursive?} is
+true, its contents are added, and its permission bits are kept.
 
 When @var{recursive?} is true, call @code{(@var{select?} @var{file}
 @var{stat})} for each directory entry, where @var{file} is the entry's
@@ -5392,62 +5546,56 @@ The @code{(guix packages)} module exports the following 
package-related
 monadic procedures:
 
 @deffn {Monadic Procedure} package-file @var{package} address@hidden @
-       [#:system (%current-system)] [#:target #f] @
-       [#:output "out"]
-Return as a monadic
-value in the absolute file name of @var{file} within the @var{output}
-directory of @var{package}.  When @var{file} is omitted, return the name
-of the @var{output} directory of @var{package}.  When @var{target} is
-true, use it as a cross-compilation target triplet.
+       [#:system (%current-system)] [#:target #f] @ [#:output "out"] Return as 
a
+monadic value in the absolute file name of @var{file} within the
address@hidden directory of @var{package}.  When @var{file} is omitted, return
+the name of the @var{output} directory of @var{package}.  When @var{target}
+is true, use it as a cross-compilation target triplet.
 @end deffn
 
 @deffn {Monadic Procedure} package->derivation @var{package} address@hidden
 @deffnx {Monadic Procedure} package->cross-derivation @var{package} @
-          @var{target} address@hidden
-Monadic version of @code{package-derivation} and
address@hidden (@pxref{Defining Packages}).
+          @var{target} address@hidden Monadic version of 
@code{package-derivation} and
address@hidden (@pxref{Pakete definieren}).
 @end deffn
 
 
address@hidden G-Expressions
address@hidden G-Expressions
address@hidden G-Ausdrücke
address@hidden G-Ausdrücke
 
 @cindex G-expression
 @cindex build code quoting
-So we have ``derivations'', which represent a sequence of build actions
-to be performed to produce an item in the store (@pxref{Derivations}).
-These build actions are performed when asking the daemon to actually
-build the derivations; they are run by the daemon in a container
-(@pxref{Invoking guix-daemon}).
+So we have ``derivations'', which represent a sequence of build actions to
+be performed to produce an item in the store (@pxref{Ableitungen}).  These
+build actions are performed when asking the daemon to actually build the
+derivations; they are run by the daemon in a container (@pxref{Aufruf des 
guix-daemon}).
 
 @cindex strata of code
-It should come as no surprise that we like to write these build actions
-in Scheme.  When we do that, we end up with two @dfn{strata} of Scheme
address@hidden term @dfn{stratum} in this context was coined by
-Manuel Serrano et al.@: in the context of their work on Hop.  Oleg
-Kiselyov, who has written insightful
address@hidden://okmij.org/ftp/meta-programming/#meta-scheme, essays and code
-on this topic}, refers to this kind of code generation as
address@hidden: the ``host code''---code that defines packages, talks
-to the daemon, etc.---and the ``build code''---code that actually
-performs build actions, such as making directories, invoking
address@hidden, etc.
-
-To describe a derivation and its build actions, one typically needs to
-embed build code inside host code.  It boils down to manipulating build
-code as data, and the homoiconicity of Scheme---code has a direct
-representation as data---comes in handy for that.  But we need more than
-the normal @code{quasiquote} mechanism in Scheme to construct build
-expressions.
+It should come as no surprise that we like to write these build actions in
+Scheme.  When we do that, we end up with two @dfn{strata} of Scheme
address@hidden term @dfn{stratum} in this context was coined by Manuel
+Serrano et al.@: in the context of their work on Hop.  Oleg Kiselyov, who
+has written insightful
address@hidden://okmij.org/ftp/meta-programming/#meta-scheme, essays and code on
+this topic}, refers to this kind of code generation as @dfn{staging}.}: the
+``host code''---code that defines packages, talks to the daemon, etc.---and
+the ``build code''---code that actually performs build actions, such as
+making directories, invoking @command{make}, etc.
+
+To describe a derivation and its build actions, one typically needs to embed
+build code inside host code.  It boils down to manipulating build code as
+data, and the homoiconicity of Scheme---code has a direct representation as
+data---comes in handy for that.  But we need more than the normal
address@hidden mechanism in Scheme to construct build expressions.
 
 The @code{(guix gexp)} module implements @dfn{G-expressions}, a form of
-S-expressions adapted to build expressions.  G-expressions, or
address@hidden, consist essentially of three syntactic forms: @code{gexp},
address@hidden, and @code{ungexp-splicing} (or simply: @code{#~},
address@hidden, and @code{#$@@}), which are comparable to
address@hidden, @code{unquote}, and @code{unquote-splicing},
-respectively (@pxref{Expression Syntax, @code{quasiquote},, guile,
-GNU Guile Reference Manual}).  However, there are major differences:
+S-expressions adapted to build expressions.  G-expressions, or @dfn{gexps},
+consist essentially of three syntactic forms: @code{gexp}, @code{ungexp},
+and @code{ungexp-splicing} (or simply: @code{#~}, @code{#$}, and
address@hidden@@}), which are comparable to @code{quasiquote}, @code{unquote}, 
and
address@hidden, respectively (@pxref{Expression Syntax,
address@hidden,, guile, GNU Guile Reference Manual}).  However, there are
+major differences:
 
 @itemize
 @item
@@ -5455,26 +5603,23 @@ Gexps are meant to be written to a file and run or 
manipulated by other
 processes.
 
 @item
-When a high-level object such as a package or derivation is unquoted
-inside a gexp, the result is as if its output file name had been
-introduced.
+When a high-level object such as a package or derivation is unquoted inside
+a gexp, the result is as if its output file name had been introduced.
 
 @item
-Gexps carry information about the packages or derivations they refer to,
-and these dependencies are automatically added as inputs to the build
-processes that use them.
+Gexps carry information about the packages or derivations they refer to, and
+these dependencies are automatically added as inputs to the build processes
+that use them.
 @end itemize
 
 @cindex lowering, of high-level objects in gexps
-This mechanism is not limited to package and derivation
-objects: @dfn{compilers} able to ``lower'' other high-level objects to
-derivations or files in the store can be defined,
-such that these objects can also be inserted
-into gexps.  For example, a useful type of high-level objects that can be
-inserted in a gexp is ``file-like objects'', which make it easy to
-add files to the store and to refer to them in
-derivations and such (see @code{local-file} and @code{plain-file}
-below.)
+This mechanism is not limited to package and derivation objects:
address@hidden able to ``lower'' other high-level objects to derivations or
+files in the store can be defined, such that these objects can also be
+inserted into gexps.  For example, a useful type of high-level objects that
+can be inserted in a gexp is ``file-like objects'', which make it easy to
+add files to the store and to refer to them in derivations and such (see
address@hidden and @code{plain-file} below.)
 
 To illustrate the idea, here is an example of a gexp:
 
@@ -5487,18 +5632,18 @@ To illustrate the idea, here is an example of a gexp:
                "list-files")))
 @end example
 
-This gexp can be passed to @code{gexp->derivation}; we obtain a
-derivation that builds a directory containing exactly one symlink to
+This gexp can be passed to @code{gexp->derivation}; we obtain a derivation
+that builds a directory containing exactly one symlink to
 @file{/gnu/store/@dots{}-coreutils-8.22/bin/ls}:
 
 @example
 (gexp->derivation "the-thing" build-exp)
 @end example
 
-As one would expect, the @code{"/gnu/store/@dots{}-coreutils-8.22"} string is
-substituted to the reference to the @var{coreutils} package in the
-actual build code, and @var{coreutils} is automatically made an input to
-the derivation.  Likewise, @code{#$output} (equivalent to @code{(ungexp
+As one would expect, the @code{"/gnu/store/@dots{}-coreutils-8.22"} string
+is substituted to the reference to the @var{coreutils} package in the actual
+build code, and @var{coreutils} is automatically made an input to the
+derivation.  Likewise, @code{#$output} (equivalent to @code{(ungexp
 output)}) is replaced by a string containing the directory name of the
 output of the derivation.
 
@@ -5506,8 +5651,8 @@ output of the derivation.
 In a cross-compilation context, it is useful to distinguish between
 references to the @emph{native} build of a package---that can run on the
 host---versus references to cross builds of a package.  To that end, the
address@hidden plays the same role as @code{#$}, but is a reference to a
-native package build:
address@hidden plays the same role as @code{#$}, but is a reference to a native
+package build:
 
 @example
 (gexp->derivation "vi"
@@ -5521,16 +5666,16 @@ native package build:
 @end example
 
 @noindent
-In the example above, the native build of @var{coreutils} is used, so
-that @command{ln} can actually run on the host; but then the
-cross-compiled build of @var{emacs} is referenced.
+In the example above, the native build of @var{coreutils} is used, so that
address@hidden can actually run on the host; but then the cross-compiled build
+of @var{emacs} is referenced.
 
 @cindex imported modules, for gexps
 @findex with-imported-modules
 Another gexp feature is @dfn{imported modules}: sometimes you want to be
-able to use certain Guile modules from the ``host environment'' in the
-gexp, so those modules should be imported in the ``build environment''.
-The @code{with-imported-modules} form allows you to express that:
+able to use certain Guile modules from the ``host environment'' in the gexp,
+so those modules should be imported in the ``build environment''.  The
address@hidden form allows you to express that:
 
 @example
 (let ((build (with-imported-modules '((guix build utils))
@@ -5551,12 +5696,12 @@ pulled into the isolated build environment of our gexp, 
such that
 
 @cindex module closure
 @findex source-module-closure
-Usually you want the @emph{closure} of the module to be imported---i.e.,
-the module itself and all the modules it depends on---rather than just
-the module; failing to do that, attempts to use the module will fail
-because of missing dependent modules.  The @code{source-module-closure}
-procedure computes the closure of a module by looking at its source file
-headers, which comes in handy in this case:
+Usually you want the @emph{closure} of the module to be imported---i.e., the
+module itself and all the modules it depends on---rather than just the
+module; failing to do that, attempts to use the module will fail because of
+missing dependent modules.  The @code{source-module-closure} procedure
+computes the closure of a module by looking at its source file headers,
+which comes in handy in this case:
 
 @example
 (use-modules (guix modules))   ;for 'source-module-closure'
@@ -5573,10 +5718,10 @@ headers, which comes in handy in this case:
 
 @cindex extensions, for gexps
 @findex with-extensions
-In the same vein, sometimes you want to import not just pure-Scheme
-modules, but also ``extensions'' such as Guile bindings to C libraries
-or other ``full-blown'' packages.  Say you need the @code{guile-json}
-package available on the build side, here's how you would do it:
+In the same vein, sometimes you want to import not just pure-Scheme modules,
+but also ``extensions'' such as Guile bindings to C libraries or other
+``full-blown'' packages.  Say you need the @code{guile-json} package
+available on the build side, here's how you would do it:
 
 @example
 (use-modules (gnu packages guile))  ;for 'guile-json'
@@ -5592,49 +5737,49 @@ The syntactic form to construct gexps is summarized 
below.
 
 @deffn {Scheme Syntax} address@hidden
 @deffnx {Scheme Syntax} (gexp @var{exp})
-Return a G-expression containing @var{exp}.  @var{exp} may contain one
-or more of the following forms:
+Return a G-expression containing @var{exp}.  @var{exp} may contain one or
+more of the following forms:
 
 @table @code
 @item address@hidden
 @itemx (ungexp @var{obj})
-Introduce a reference to @var{obj}.  @var{obj} may have one of the
-supported types, for example a package or a
-derivation, in which case the @code{ungexp} form is replaced by its
-output file name---e.g., @code{"/gnu/store/@dots{}-coreutils-8.22}.
+Introduce a reference to @var{obj}.  @var{obj} may have one of the supported
+types, for example a package or a derivation, in which case the
address@hidden form is replaced by its output file name---e.g.,
address@hidden"/gnu/store/@dots{}-coreutils-8.22}.
 
-If @var{obj} is a list, it is traversed and references to supported
-objects are substituted similarly.
+If @var{obj} is a list, it is traversed and references to supported objects
+are substituted similarly.
 
-If @var{obj} is another gexp, its contents are inserted and its
-dependencies are added to those of the containing gexp.
+If @var{obj} is another gexp, its contents are inserted and its dependencies
+are added to those of the containing gexp.
 
 If @var{obj} is another kind of object, it is inserted as is.
 
 @item address@hidden:@var{output}
 @itemx (ungexp @var{obj} @var{output})
-This is like the form above, but referring explicitly to the
address@hidden of @var{obj}---this is useful when @var{obj} produces
-multiple outputs (@pxref{Packages with Multiple Outputs}).
+This is like the form above, but referring explicitly to the @var{output} of
address@hidden is useful when @var{obj} produces multiple outputs
+(@pxref{Pakete mit mehreren Ausgaben.}).
 
 @item address@hidden
 @itemx address@hidden:output
 @itemx (ungexp-native @var{obj})
 @itemx (ungexp-native @var{obj} @var{output})
-Same as @code{ungexp}, but produces a reference to the @emph{native}
-build of @var{obj} when used in a cross compilation context.
+Same as @code{ungexp}, but produces a reference to the @emph{native} build
+of @var{obj} when used in a cross compilation context.
 
 @item #$output[:@var{output}]
 @itemx (ungexp output address@hidden)
-Insert a reference to derivation output @var{output}, or to the main
-output when @var{output} is omitted.
+Insert a reference to derivation output @var{output}, or to the main output
+when @var{output} is omitted.
 
 This only makes sense for gexps passed to @code{gexp->derivation}.
 
 @item #$@@@var{lst}
 @itemx (ungexp-splicing @var{lst})
-Like the above, but splices the contents of @var{lst} inside the
-containing list.
+Like the above, but splices the contents of @var{lst} inside the containing
+list.
 
 @item #+@@@var{lst}
 @itemx (ungexp-native-splicing @var{lst})
@@ -5643,17 +5788,17 @@ Like the above, but refers to native builds of the 
objects listed in
 
 @end table
 
-G-expressions created by @code{gexp} or @code{#~} are run-time objects
-of the @code{gexp?} type (see below.)
+G-expressions created by @code{gexp} or @code{#~} are run-time objects of
+the @code{gexp?} type (see below.)
 @end deffn
 
 @deffn {Scheme Syntax} with-imported-modules @var{modules} @address@hidden
-Mark the gexps defined in @address@hidden as requiring @var{modules}
-in their execution environment.
+Mark the gexps defined in @address@hidden as requiring @var{modules} in
+their execution environment.
 
-Each item in @var{modules} can be the name of a module, such as
address@hidden(guix build utils)}, or it can be a module name, followed by an
-arrow, followed by a file-like object:
+Each item in @var{modules} can be the name of a module, such as @code{(guix
+build utils)}, or it can be a module name, followed by an arrow, followed by
+a file-like object:
 
 @example
 `((guix build utils)
@@ -5663,69 +5808,63 @@ arrow, followed by a file-like object:
 @end example
 
 @noindent
-In the example above, the first two modules are taken from the search
-path, and the last one is created from the given file-like object.
+In the example above, the first two modules are taken from the search path,
+and the last one is created from the given file-like object.
 
-This form has @emph{lexical} scope: it has an effect on the gexps
-directly defined in @address@hidden, but not on those defined, say, in
-procedures called from @address@hidden
+This form has @emph{lexical} scope: it has an effect on the gexps directly
+defined in @address@hidden, but not on those defined, say, in procedures
+called from @address@hidden
 @end deffn
 
 @deffn {Scheme Syntax} with-extensions @var{extensions} @address@hidden
-Mark the gexps defined in @address@hidden as requiring
address@hidden in their build and execution environment.
address@hidden is typically a list of package objects such as those
-defined in the @code{(gnu packages guile)} module.
-
-Concretely, the packages listed in @var{extensions} are added to the
-load path while compiling imported modules in @address@hidden; they
-are also added to the load path of the gexp returned by
address@hidden@dots{}.
+Mark the gexps defined in @address@hidden as requiring @var{extensions} in
+their build and execution environment.  @var{extensions} is typically a list
+of package objects such as those defined in the @code{(gnu packages guile)}
+module.
+
+Concretely, the packages listed in @var{extensions} are added to the load
+path while compiling imported modules in @address@hidden; they are also
+added to the load path of the gexp returned by @address@hidden
 @end deffn
 
 @deffn {Scheme Procedure} gexp? @var{obj}
 Return @code{#t} if @var{obj} is a G-expression.
 @end deffn
 
-G-expressions are meant to be written to disk, either as code building
-some derivation, or as plain files in the store.  The monadic procedures
-below allow you to do that (@pxref{The Store Monad}, for more
-information about monads.)
+G-expressions are meant to be written to disk, either as code building some
+derivation, or as plain files in the store.  The monadic procedures below
+allow you to do that (@pxref{Die Store-Monade}, for more information about
+monads.)
 
 @deffn {Monadic Procedure} gexp->derivation @var{name} @var{exp} @
-       [#:system (%current-system)] [#:target #f] [#:graft? #t] @
-       [#:hash #f] [#:hash-algo #f] @
-       [#:recursive? #f] [#:env-vars '()] [#:modules '()] @
-       [#:module-path @var{%load-path}] @
-       [#:effective-version "2.2"] @
-       [#:references-graphs #f] [#:allowed-references #f] @
-       [#:disallowed-references #f] @
-       [#:leaked-env-vars #f] @
-       [#:script-name (string-append @var{name} "-builder")] @
-       [#:deprecation-warnings #f] @
-       [#:local-build? #f] [#:substitutable? #t] [#:guile-for-build #f]
-Return a derivation @var{name} that runs @var{exp} (a gexp) with
address@hidden (a derivation) on @var{system}; @var{exp} is
-stored in a file called @var{script-name}.  When @var{target} is true,
-it is used as the cross-compilation target triplet for packages referred
-to by @var{exp}.
-
address@hidden is deprecated in favor of @code{with-imported-modules}.
-Its meaning is to
-make @var{modules} available in the evaluation context of @var{exp};
address@hidden is a list of names of Guile modules searched in
+       [#:system (%current-system)] [#:target #f] [#:graft? #t] @ [#:hash #f]
+[#:hash-algo #f] @ [#:recursive? #f] [#:env-vars '()] [#:modules '()] @
+[#:module-path @var{%load-path}] @ [#:effective-version "2.2"] @
+[#:references-graphs #f] [#:allowed-references #f] @
+[#:disallowed-references #f] @ [#:leaked-env-vars #f] @ [#:script-name
+(string-append @var{name} "-builder")] @ [#:deprecation-warnings #f] @
+[#:local-build? #f] [#:substitutable? #t] [#:guile-for-build #f] Return a
+derivation @var{name} that runs @var{exp} (a gexp) with
address@hidden (a derivation) on @var{system}; @var{exp} is stored in
+a file called @var{script-name}.  When @var{target} is true, it is used as
+the cross-compilation target triplet for packages referred to by @var{exp}.
+
address@hidden is deprecated in favor of @code{with-imported-modules}.  Its
+meaning is to make @var{modules} available in the evaluation context of
address@hidden; @var{modules} is a list of names of Guile modules searched in
 @var{module-path} to be copied in the store, compiled, and made available in
-the load path during the execution of @var{exp}---e.g., @code{((guix
-build utils) (guix build gnu-build-system))}.
+the load path during the execution of @var{exp}---e.g., @code{((guix build
+utils) (guix build gnu-build-system))}.
 
address@hidden determines the string to use when adding extensions of
address@hidden (see @code{with-extensions}) to the search path---e.g., 
@code{"2.2"}.
address@hidden determines the string to use when adding extensions
+of @var{exp} (see @code{with-extensions}) to the search path---e.g.,
address@hidden"2.2"}.
 
address@hidden determines whether packages referred to by @var{exp} should be 
grafted when
-applicable.
address@hidden determines whether packages referred to by @var{exp} should be
+grafted when applicable.
 
-When @var{references-graphs} is true, it must be a list of tuples of one of the
-following forms:
+When @var{references-graphs} is true, it must be a list of tuples of one of
+the following forms:
 
 @example
 (@var{file-name} @var{package})
@@ -5735,52 +5874,52 @@ following forms:
 (@var{file-name} @var{store-item})
 @end example
 
-The right-hand-side of each element of @var{references-graphs} is 
automatically made
-an input of the build process of @var{exp}.  In the build environment, each
address@hidden contains the reference graph of the corresponding item, in a 
simple
-text format.
+The right-hand-side of each element of @var{references-graphs} is
+automatically made an input of the build process of @var{exp}.  In the build
+environment, each @var{file-name} contains the reference graph of the
+corresponding item, in a simple text format.
 
address@hidden must be either @code{#f} or a list of output names and packages.
-In the latter case, the list denotes store items that the result is allowed to
-refer to.  Any reference to another store item will lead to a build error.
-Similarly for @var{disallowed-references}, which can list items that must not 
be
-referenced by the outputs.
address@hidden must be either @code{#f} or a list of output names
+and packages.  In the latter case, the list denotes store items that the
+result is allowed to refer to.  Any reference to another store item will
+lead to a build error.  Similarly for @var{disallowed-references}, which can
+list items that must not be referenced by the outputs.
 
address@hidden determines whether to show deprecation warnings while
-compiling modules.  It can be @code{#f}, @code{#t}, or @code{'detailed}.
address@hidden determines whether to show deprecation warnings
+while compiling modules.  It can be @code{#f}, @code{#t}, or
address@hidden'detailed}.
 
-The other arguments are as for @code{derivation} (@pxref{Derivations}).
+The other arguments are as for @code{derivation} (@pxref{Ableitungen}).
 @end deffn
 
 @cindex file-like objects
 The @code{local-file}, @code{plain-file}, @code{computed-file},
 @code{program-file}, and @code{scheme-file} procedures below return
address@hidden objects}.  That is, when unquoted in a G-expression,
-these objects lead to a file in the store.  Consider this G-expression:
address@hidden objects}.  That is, when unquoted in a G-expression, these
+objects lead to a file in the store.  Consider this G-expression:
 
 @example
 #~(system* #$(file-append glibc "/sbin/nscd") "-f"
            #$(local-file "/tmp/my-nscd.conf"))
 @end example
 
-The effect here is to ``intern'' @file{/tmp/my-nscd.conf} by copying it
-to the store.  Once expanded, for instance @i{via}
address@hidden>derivation}, the G-expression refers to that copy under
address@hidden/gnu/store}; thus, modifying or removing the file in @file{/tmp}
-does not have any effect on what the G-expression does.
address@hidden can be used similarly; it differs in that the file
-content is directly passed as a string.
+The effect here is to ``intern'' @file{/tmp/my-nscd.conf} by copying it to
+the store.  Once expanded, for instance @i{via} @code{gexp->derivation}, the
+G-expression refers to that copy under @file{/gnu/store}; thus, modifying or
+removing the file in @file{/tmp} does not have any effect on what the
+G-expression does.  @code{plain-file} can be used similarly; it differs in
+that the file content is directly passed as a string.
 
 @deffn {Scheme Procedure} local-file @var{file} address@hidden @
-   [#:recursive? #f] [#:select? (const #t)]
-Return an object representing local file @var{file} to add to the store; this
-object can be used in a gexp.  If @var{file} is a relative file name, it is 
looked
-up relative to the source file where this form appears.  @var{file} will be 
added to
-the store under @var{name}--by default the base name of @var{file}.
+   [#:recursive? #f] [#:select? (const #t)] Return an object representing local
+file @var{file} to add to the store; this object can be used in a gexp.  If
address@hidden is a relative file name, it is looked up relative to the source
+file where this form appears.  @var{file} will be added to the store under
address@hidden default the base name of @var{file}.
 
-When @var{recursive?} is true, the contents of @var{file} are added 
recursively; if @var{file}
-designates a flat file and @var{recursive?} is true, its contents are added, 
and its
-permission bits are kept.
+When @var{recursive?} is true, the contents of @var{file} are added
+recursively; if @var{file} designates a flat file and @var{recursive?} is
+true, its contents are added, and its permission bits are kept.
 
 When @var{recursive?} is true, call @code{(@var{select?} @var{file}
 @var{stat})} for each directory entry, where @var{file} is the entry's
@@ -5788,7 +5927,7 @@ absolute file name and @var{stat} is the result of 
@code{lstat}; exclude
 entries for which @var{select?} does not return true.
 
 This is the declarative counterpart of the @code{interned-file} monadic
-procedure (@pxref{The Store Monad, @code{interned-file}}).
+procedure (@pxref{Die Store-Monade, @code{interned-file}}).
 @end deffn
 
 @deffn {Scheme Procedure} plain-file @var{name} @var{content}
@@ -5799,19 +5938,18 @@ This is the declarative counterpart of @code{text-file}.
 @end deffn
 
 @deffn {Scheme Procedure} computed-file @var{name} @var{gexp} @
-          [#:options '(#:local-build? #t)]
-Return an object representing the store item @var{name}, a file or
-directory computed by @var{gexp}.  @var{options}
+          [#:options '(#:local-build? #t)] Return an object representing the 
store
+item @var{name}, a file or directory computed by @var{gexp}.  @var{options}
 is a list of additional arguments to pass to @code{gexp->derivation}.
 
 This is the declarative counterpart of @code{gexp->derivation}.
 @end deffn
 
 @deffn {Monadic Procedure} gexp->script @var{name} @var{exp} @
-  [#:guile (default-guile)] [#:module-path %load-path]
-Return an executable script @var{name} that runs @var{exp} using
address@hidden, with @var{exp}'s imported modules in its search path.
-Look up @var{exp}'s modules in @var{module-path}.
+  [#:guile (default-guile)] [#:module-path %load-path] Return an executable
+script @var{name} that runs @var{exp} using @var{guile}, with @var{exp}'s
+imported modules in its search path.  Look up @var{exp}'s modules in
address@hidden
 
 The example below builds a script that simply invokes the @command{ls}
 command:
@@ -5824,9 +5962,9 @@ command:
                        "ls"))
 @end example
 
-When ``running'' it through the store (@pxref{The Store Monad,
address@hidden), we obtain a derivation that produces an
-executable file @file{/gnu/store/@dots{}-list-files} along these lines:
+When ``running'' it through the store (@pxref{Die Store-Monade,
address@hidden), we obtain a derivation that produces an executable
+file @file{/gnu/store/@dots{}-list-files} along these lines:
 
 @example
 #!/gnu/store/@dots{}-guile-2.0.11/bin/guile -ds
@@ -5836,29 +5974,26 @@ executable file @file{/gnu/store/@dots{}-list-files} 
along these lines:
 @end deffn
 
 @deffn {Scheme Procedure} program-file @var{name} @var{exp} @
-          [#:guile #f] [#:module-path %load-path]
-Return an object representing the executable store item @var{name} that
-runs @var{gexp}.  @var{guile} is the Guile package used to execute that
-script.  Imported modules of @var{gexp} are looked up in @var{module-path}.
+          [#:guile #f] [#:module-path %load-path] Return an object 
representing the
+executable store item @var{name} that runs @var{gexp}.  @var{guile} is the
+Guile package used to execute that script.  Imported modules of @var{gexp}
+are looked up in @var{module-path}.
 
 This is the declarative counterpart of @code{gexp->script}.
 @end deffn
 
 @deffn {Monadic Procedure} gexp->file @var{name} @var{exp} @
-            [#:set-load-path? #t] [#:module-path %load-path] @
-            [#:splice? #f] @
-            [#:guile (default-guile)]
-Return a derivation that builds a file @var{name} containing @var{exp}.
-When @var{splice?}  is true, @var{exp} is considered to be a list of
-expressions that will be spliced in the resulting file.
-
-When @var{set-load-path?} is true, emit code in the resulting file to
-set @code{%load-path} and @code{%load-compiled-path} to honor
address@hidden's imported modules.  Look up @var{exp}'s modules in
address@hidden
+            [#:set-load-path? #t] [#:module-path %load-path] @ [#:splice? #f] 
@ [#:guile
+(default-guile)] Return a derivation that builds a file @var{name}
+containing @var{exp}.  When @var{splice?} is true, @var{exp} is considered
+to be a list of expressions that will be spliced in the resulting file.
+
+When @var{set-load-path?} is true, emit code in the resulting file to set
address@hidden and @code{%load-compiled-path} to honor @var{exp}'s
+imported modules.  Look up @var{exp}'s modules in @var{module-path}.
 
-The resulting file holds references to all the dependencies of @var{exp}
-or a subset thereof.
+The resulting file holds references to all the dependencies of @var{exp} or
+a subset thereof.
 @end deffn
 
 @deffn {Scheme Procedure} scheme-file @var{name} @var{exp} [#:splice? #f]
@@ -5869,16 +6004,14 @@ This is the declarative counterpart of 
@code{gexp->file}.
 @end deffn
 
 @deffn {Monadic Procedure} text-file* @var{name} @var{text} @dots{}
-Return as a monadic value a derivation that builds a text file
-containing all of @var{text}.  @var{text} may list, in addition to
-strings, objects of any type that can be used in a gexp: packages,
-derivations, local file objects, etc.  The resulting store file holds
-references to all these.
-
-This variant should be preferred over @code{text-file} anytime the file
-to create will reference items from the store.  This is typically the
-case when building a configuration file that embeds store file names,
-like this:
+Return as a monadic value a derivation that builds a text file containing
+all of @var{text}.  @var{text} may list, in addition to strings, objects of
+any type that can be used in a gexp: packages, derivations, local file
+objects, etc.  The resulting store file holds references to all these.
+
+This variant should be preferred over @code{text-file} anytime the file to
+create will reference items from the store.  This is typically the case when
+building a configuration file that embeds store file names, like this:
 
 @example
 (define (profile.sh)
@@ -5895,9 +6028,8 @@ preventing them from being garbage-collected during its 
lifetime.
 @end deffn
 
 @deffn {Scheme Procedure} mixed-text-file @var{name} @var{text} @dots{}
-Return an object representing store file @var{name} containing
address@hidden  @var{text} is a sequence of strings and file-like objects,
-as in:
+Return an object representing store file @var{name} containing @var{text}.
address@hidden is a sequence of strings and file-like objects, as in:
 
 @example
 (mixed-text-file "profile"
@@ -5908,10 +6040,10 @@ This is the declarative counterpart of 
@code{text-file*}.
 @end deffn
 
 @deffn {Scheme Procedure} file-union @var{name} @var{files}
-Return a @code{<computed-file>} that builds a directory containing all of 
@var{files}.
-Each item in @var{files} must be a two-element list where the first element is 
the
-file name to use in the new directory, and the second element is a gexp
-denoting the target file.  Here's an example:
+Return a @code{<computed-file>} that builds a directory containing all of
address@hidden  Each item in @var{files} must be a two-element list where the
+first element is the file name to use in the new directory, and the second
+element is a gexp denoting the target file.  Here's an example:
 
 @example
 (file-union "etc"
@@ -5925,20 +6057,21 @@ This yields an @code{etc} directory containing these 
two files.
 @end deffn
 
 @deffn {Scheme Procedure} directory-union @var{name} @var{things}
-Return a directory that is the union of @var{things}, where @var{things} is a 
list of
-file-like objects denoting directories.  For example:
+Return a directory that is the union of @var{things}, where @var{things} is
+a list of file-like objects denoting directories.  For example:
 
 @example
 (directory-union "guile+emacs" (list guile emacs))
 @end example
 
-yields a directory that is the union of the @code{guile} and @code{emacs} 
packages.
+yields a directory that is the union of the @code{guile} and @code{emacs}
+packages.
 @end deffn
 
 @deffn {Scheme Procedure} file-append @var{obj} @var{suffix} @dots{}
-Return a file-like object that expands to the concatenation of @var{obj}
-and @var{suffix}, where @var{obj} is a lowerable object and each
address@hidden is a string.
+Return a file-like object that expands to the concatenation of @var{obj} and
address@hidden, where @var{obj} is a lowerable object and each @var{suffix} is
+a string.
 
 As an example, consider this gexp:
 
@@ -5957,29 +6090,28 @@ The same effect could be achieved with:
 @end example
 
 There is one difference though: in the @code{file-append} case, the
-resulting script contains the absolute file name as a string, whereas in
-the second case, the resulting script contains a @code{(string-append
address@hidden)} expression to construct the file name @emph{at run time}.
+resulting script contains the absolute file name as a string, whereas in the
+second case, the resulting script contains a @code{(string-append @dots{})}
+expression to construct the file name @emph{at run time}.
 @end deffn
 
 
-Of course, in addition to gexps embedded in ``host'' code, there are
-also modules containing build tools.  To make it clear that they are
-meant to be used in the build stratum, these modules are kept in the
address@hidden(guix build @dots{})} name space.
+Of course, in addition to gexps embedded in ``host'' code, there are also
+modules containing build tools.  To make it clear that they are meant to be
+used in the build stratum, these modules are kept in the @code{(guix build
address@hidden)} name space.
 
 @cindex lowering, of high-level objects in gexps
-Internally, high-level objects are @dfn{lowered}, using their compiler,
-to either derivations or store items.  For instance, lowering a package
-yields a derivation, and lowering a @code{plain-file} yields a store
-item.  This is achieved using the @code{lower-object} monadic procedure.
+Internally, high-level objects are @dfn{lowered}, using their compiler, to
+either derivations or store items.  For instance, lowering a package yields
+a derivation, and lowering a @code{plain-file} yields a store item.  This is
+achieved using the @code{lower-object} monadic procedure.
 
 @deffn {Monadic Procedure} lower-object @var{obj} address@hidden @
-           [#:target #f]
-Return as a value in @var{%store-monad} the derivation or store item
-corresponding to @var{obj} for @var{system}, cross-compiling for
address@hidden if @var{target} is true.  @var{obj} must be an object that
-has an associated gexp compiler, such as a @code{<package>}.
+           [#:target #f] Return as a value in @var{%store-monad} the 
derivation or
+store item corresponding to @var{obj} for @var{system}, cross-compiling for
address@hidden if @var{target} is true.  @var{obj} must be an object that has
+an associated gexp compiler, such as a @code{<package>}.
 @end deffn
 
 @node Invoking guix repl
@@ -5987,10 +6119,11 @@ has an associated gexp compiler, such as a 
@code{<package>}.
 
 @cindex REPL, read-eval-print loop
 The @command{guix repl} command spawns a Guile @dfn{read-eval-print loop}
-(REPL) for interactive programming (@pxref{Using Guile Interactively,,, guile,
-GNU Guile Reference Manual}).  Compared to just launching the @command{guile}
-command, @command{guix repl} guarantees that all the Guix modules and all its
-dependencies are available in the search path.  You can use it this way:
+(REPL) for interactive programming (@pxref{Using Guile Interactively,,,
+guile, GNU Guile Reference Manual}).  Compared to just launching the
address@hidden command, @command{guix repl} guarantees that all the Guix
+modules and all its dependencies are available in the search path.  You can
+use it this way:
 
 @example
 $ guix repl
@@ -6020,7 +6153,7 @@ Spawn a REPL that uses the machine-readable protocol.  
This is the protocol
 that the @code{(guix inferior)} module speaks.
 @end table
 
address@hidden address@hidden
address@hidden address@hidden
 By default, @command{guix repl} reads from standard input and writes to
 standard output.  When this option is passed, it will instead listen for
 connections on @var{endpoint}.  Here are examples of valid options:
@@ -6035,43 +6168,46 @@ Accept connections on the Unix-domain socket 
@file{/tmp/socket}.
 @end table
 
 @c *********************************************************************
address@hidden Utilities
address@hidden Utilities
address@hidden Zubehör
address@hidden Zubehör
 
 This section describes Guix command-line utilities.  Some of them are
 primarily targeted at developers and users who write new package
-definitions, while others are more generally useful.  They complement
-the Scheme programming interface of Guix in a convenient way.
+definitions, while others are more generally useful.  They complement the
+Scheme programming interface of Guix in a convenient way.
 
 @menu
-* Invoking guix build::         Building packages from the command line.
-* Invoking guix edit::          Editing package definitions.
-* Invoking guix download::      Downloading a file and printing its hash.
-* Invoking guix hash::          Computing the cryptographic hash of a file.
-* Invoking guix import::        Importing package definitions.
-* Invoking guix refresh::       Updating package definitions.
-* Invoking guix lint::          Finding errors in package definitions.
-* Invoking guix size::          Profiling disk usage.
-* Invoking guix graph::         Visualizing the graph of packages.
-* Invoking guix environment::   Setting up development environments.
-* Invoking guix publish::       Sharing substitutes.
-* Invoking guix challenge::     Challenging substitute servers.
-* Invoking guix copy::          Copying to and from a remote store.
-* Invoking guix container::     Process isolation.
-* Invoking guix weather::       Assessing substitute availability.
-* Invoking guix processes::     Listing client processes.
+* Aufruf von guix build::    Pakete aus der Befehlszeile heraus erstellen.
+* Aufruf von guix edit::     Paketdefinitionen bearbeiten.
+* Aufruf von guix download::  Herunterladen einer Datei und Ausgabe ihres 
+                                Hashes.
+* Aufruf von guix hash::     Den kryptographischen Hash einer Datei 
+                               berechnen.
+* Aufruf von guix import::   Paketdefinitionen importieren.
+* Aufruf von guix refresh::  Paketdefinitionen aktualisieren.
+* Aufruf von guix lint::     Fehler in Paketdefinitionen finden.
+* Aufruf von guix size::     Plattenverbrauch profilieren.
+* Aufruf von guix graph::    Den Paketgraphen visualisieren.
+* Aufruf von guix environment::  Entwicklungsumgebungen einrichten.
+* Aufruf von guix publish::  Substitute teilen.
+* Aufruf von guix challenge::  Die Substitut-Server anfechten.
+* Aufruf von guix copy::     Mit einem entfernten Store Dateien austauschen.
+* Aufruf von guix container::  Prozesse isolieren.
+* Aufruf von guix weather::  Die Verfügbarkeit von Substituten 
+                               einschätzen.
+* Invoking guix processes::  Listing client processes.
 @end menu
 
address@hidden Invoking guix build
address@hidden Invoking @command{guix build}
address@hidden Aufruf von guix build
address@hidden Aufruf von @command{guix build}
 
 @cindex package building
 @cindex @command{guix build}
-The @command{guix build} command builds packages or derivations and
-their dependencies, and prints the resulting store paths.  Note that it
-does not modify the user's profile---this is the job of the
address@hidden package} command (@pxref{Invoking guix package}).  Thus,
-it is mainly useful for distribution developers.
+The @command{guix build} command builds packages or derivations and their
+dependencies, and prints the resulting store paths.  Note that it does not
+modify the user's profile---this is the job of the @command{guix package}
+command (@pxref{Aufruf von guix package}).  Thus, it is mainly useful for
+distribution developers.
 
 The general syntax is:
 
@@ -6079,9 +6215,9 @@ The general syntax is:
 guix build @var{options} @address@hidden
 @end example
 
-As an example, the following command builds the latest versions of Emacs
-and of Guile, displays their build logs, and finally displays the
-resulting directories:
+As an example, the following command builds the latest versions of Emacs and
+of Guile, displays their build logs, and finally displays the resulting
+directories:
 
 @example
 guix build emacs guile
@@ -6094,12 +6230,11 @@ guix build --quiet --keep-going \
   `guix package -A | cut -f1,2 --output-delimiter=@@`
 @end example
 
address@hidden may be either the name of a package found in
-the software distribution such as @code{coreutils} or
address@hidden@@8.20}, or a derivation such as
address@hidden/gnu/store/@dots{}-coreutils-8.19.drv}.  In the former case, a
-package with the corresponding name (and optionally version) is searched
-for among the GNU distribution modules (@pxref{Package Modules}).
address@hidden may be either the name of a package found in the
+software distribution such as @code{coreutils} or @code{coreutils@@8.20}, or
+a derivation such as @file{/gnu/store/@dots{}-coreutils-8.19.drv}.  In the
+former case, a package with the corresponding name (and optionally version)
+is searched for among the GNU distribution modules (@pxref{Paketmodule}).
 
 Alternatively, the @code{--expression} option may be used to specify a
 Scheme expression that evaluates to a package; this is useful when
@@ -6110,45 +6245,47 @@ There may be zero or more @var{options}.  The available 
options are
 described in the subsections below.
 
 @menu
-* Common Build Options::        Build options for most commands.
-* Package Transformation Options::  Creating variants of packages.
-* Additional Build Options::    Options specific to 'guix build'.
-* Debugging Build Failures::    Real life packaging experience.
+* Gemeinsame Erstellungsoptionen::  Erstellungsoptionen für die meisten 
+                                      Befehle.
+* Paketumwandlungsoptionen::  Varianten von Paketen erzeugen.
+* Zusätzliche Erstellungsoptionen::  Optionen spezifisch für »guix 
+                                        build«.
+* Fehlschläge beim Erstellen untersuchen::  Praxiserfahrung bei der 
+                                               Paketerstellung.
 @end menu
 
address@hidden Common Build Options
address@hidden Common Build Options
address@hidden Gemeinsame Erstellungsoptionen
address@hidden Gemeinsame Erstellungsoptionen
 
 A number of options that control the build process are common to
 @command{guix build} and other commands that can spawn builds, such as
address@hidden package} or @command{guix archive}.  These are the
-following:
address@hidden package} or @command{guix archive}.  These are the following:
 
 @table @code
 
 @item address@hidden
 @itemx -L @var{directory}
 Add @var{directory} to the front of the package module search path
-(@pxref{Package Modules}).
+(@pxref{Paketmodule}).
 
-This allows users to define their own packages and make them visible to
-the command-line tools.
+This allows users to define their own packages and make them visible to the
+command-line tools.
 
 @item --keep-failed
 @itemx -K
 Keep the build tree of failed builds.  Thus, if a build fails, its build
-tree is kept under @file{/tmp}, in a directory whose name is shown at
-the end of the build log.  This is useful when debugging build issues.
address@hidden Build Failures}, for tips and tricks on how to debug
-build issues.
+tree is kept under @file{/tmp}, in a directory whose name is shown at the
+end of the build log.  This is useful when debugging build issues.
address@hidden beim Erstellen untersuchen}, for tips and tricks on how to debug 
build
+issues.
 
 @item --keep-going
 @itemx -k
-Keep going when some of the derivations fail to build; return only once
-all the builds have either completed or failed.
+Keep going when some of the derivations fail to build; return only once all
+the builds have either completed or failed.
 
-The default behavior is to stop as soon as one of the specified
-derivations has failed.
+The default behavior is to stop as soon as one of the specified derivations
+has failed.
 
 @item --dry-run
 @itemx -n
@@ -6156,30 +6293,29 @@ Do not build the derivations.
 
 @anchor{fallback-option}
 @item --fallback
-When substituting a pre-built binary fails, fall back to building
-packages locally (@pxref{Substitution Failure}).
+When substituting a pre-built binary fails, fall back to building packages
+locally (@pxref{Fehler bei der Substitution}).
 
address@hidden address@hidden
address@hidden address@hidden
 @anchor{client-substitute-urls}
-Consider @var{urls} the whitespace-separated list of substitute source
-URLs, overriding the default list of URLs of @command{guix-daemon}
+Consider @var{urls} the whitespace-separated list of substitute source URLs,
+overriding the default list of URLs of @command{guix-daemon}
 (@pxref{daemon-substitute-urls,, @command{guix-daemon} URLs}).
 
-This means that substitutes may be downloaded from @var{urls}, provided
-they are signed by a key authorized by the system administrator
-(@pxref{Substitutes}).
+This means that substitutes may be downloaded from @var{urls}, provided they
+are signed by a key authorized by the system administrator
+(@pxref{Substitute}).
 
-When @var{urls} is the empty string, substitutes are effectively
-disabled.
+When @var{urls} is the empty string, substitutes are effectively disabled.
 
 @item --no-substitutes
-Do not use substitutes for build products.  That is, always build things
-locally instead of allowing downloads of pre-built binaries
-(@pxref{Substitutes}).
+Benutze keine Substitute für Erstellungsergebnisse. Das heißt, dass alle
+Objekte lokal erstellt werden müssen, und kein Herunterladen von vorab
+erstellten Binärdateien erlaubt ist (@pxref{Substitute}).
 
 @item --no-grafts
 Do not ``graft'' packages.  In practice, this means that package updates
-available as grafts are not applied.  @xref{Security Updates}, for more
+available as grafts are not applied.  @xref{Sicherheitsaktualisierungen}, for 
more
 information on grafts.
 
 @item address@hidden
@@ -6189,110 +6325,108 @@ consecutive build results are not bit-for-bit 
identical.
 This is a useful way to detect non-deterministic builds processes.
 Non-deterministic build processes are a problem because they make it
 practically impossible for users to @emph{verify} whether third-party
-binaries are genuine.  @xref{Invoking guix challenge}, for more.
+binaries are genuine.  @xref{Aufruf von guix challenge}, for more.
 
-Note that, currently, the differing build results are not kept around,
-so you will have to manually investigate in case of an error---e.g., by
+Note that, currently, the differing build results are not kept around, so
+you will have to manually investigate in case of an error---e.g., by
 stashing one of the build results with @code{guix archive --export}
-(@pxref{Invoking guix archive}), then rebuilding, and finally comparing
-the two results.
+(@pxref{Aufruf von guix archive}), then rebuilding, and finally comparing the
+two results.
 
 @item --no-build-hook
-Do not attempt to offload builds @i{via} the ``build hook'' of the daemon
-(@pxref{Daemon Offload Setup}).  That is, always build things locally
-instead of offloading builds to remote machines.
+Nicht versuchen, Erstellungen über den »Build-Hook« des Daemons auszulagern
+(@pxref{Auslagern des Daemons einrichten}). Somit wird lokal erstellt, statt
+Erstellungen auf entfernte Maschinen auszulagern.
 
address@hidden address@hidden
-When the build or substitution process remains silent for more than
address@hidden, terminate it and report a build failure.
address@hidden address@hidden
+Wenn der Erstellungs- oder Substitutionsprozess länger als
address@hidden keine Ausgabe erzeugt, wird er abgebrochen und ein
+Fehler beim Erstellen gemeldet.
 
-By default, the daemon's setting is honored (@pxref{Invoking
-guix-daemon, @code{--max-silent-time}}).
+By default, the daemon's setting is honored (@pxref{Aufruf des guix-daemon,
address@hidden).
 
address@hidden address@hidden
-Likewise, when the build or substitution process lasts for more than
address@hidden, terminate it and report a build failure.
address@hidden address@hidden
+Entsprechend wird hier der Erstellungs- oder Substitutionsprozess
+abgebrochen und als Fehlschlag gemeldet, wenn er mehr als
address@hidden dauert.
 
-By default, the daemon's setting is honored (@pxref{Invoking
-guix-daemon, @code{--timeout}}).
+By default, the daemon's setting is honored (@pxref{Aufruf des guix-daemon,
address@hidden).
 
 @item address@hidden
-Use the given verbosity level.  @var{level} must be an integer between 0
-and 5; higher means more verbose output.  Setting a level of 4 or more
-may be helpful when debugging setup issues with the build daemon.
+Use the given verbosity level.  @var{level} must be an integer between 0 and
+5; higher means more verbose output.  Setting a level of 4 or more may be
+helpful when debugging setup issues with the build daemon.
 
 @item address@hidden
 @itemx -c @var{n}
-Allow the use of up to @var{n} CPU cores for the build.  The special
-value @code{0} means to use as many CPU cores as available.
+Allow the use of up to @var{n} CPU cores for the build.  The special value
address@hidden means to use as many CPU cores as available.
 
 @item address@hidden
 @itemx -M @var{n}
-Allow at most @var{n} build jobs in parallel.  @xref{Invoking
-guix-daemon, @code{--max-jobs}}, for details about this option and the
-equivalent @command{guix-daemon} option.
+Allow at most @var{n} build jobs in parallel.  @xref{Aufruf des guix-daemon,
address@hidden, for details about this option and the equivalent
address@hidden option.
 
 @end table
 
-Behind the scenes, @command{guix build} is essentially an interface to
-the @code{package-derivation} procedure of the @code{(guix packages)}
-module, and to the @code{build-derivations} procedure of the @code{(guix
+Behind the scenes, @command{guix build} is essentially an interface to the
address@hidden procedure of the @code{(guix packages)} module,
+and to the @code{build-derivations} procedure of the @code{(guix
 derivations)} module.
 
-In addition to options explicitly passed on the command line,
address@hidden build} and other @command{guix} commands that support
-building honor the @code{GUIX_BUILD_OPTIONS} environment variable.
+In addition to options explicitly passed on the command line, @command{guix
+build} and other @command{guix} commands that support building honor the
address@hidden environment variable.
 
 @defvr {Environment Variable} GUIX_BUILD_OPTIONS
-Users can define this variable to a list of command line options that
-will automatically be used by @command{guix build} and other
address@hidden commands that can perform builds, as in the example
-below:
+Users can define this variable to a list of command line options that will
+automatically be used by @command{guix build} and other @command{guix}
+commands that can perform builds, as in the example below:
 
 @example
 $ export GUIX_BUILD_OPTIONS="--no-substitutes -c 2 -L /foo/bar"
 @end example
 
-These options are parsed independently, and the result is appended to
-the parsed command-line options.
+These options are parsed independently, and the result is appended to the
+parsed command-line options.
 @end defvr
 
 
address@hidden Package Transformation Options
address@hidden Package Transformation Options
address@hidden Paketumwandlungsoptionen
address@hidden Paketumwandlungsoptionen
 
 @cindex package variants
-Another set of command-line options supported by @command{guix build}
-and also @command{guix package} are @dfn{package transformation
-options}.  These are options that make it possible to define @dfn{package
-variants}---for instance, packages built from different source code.
-This is a convenient way to create customized packages on the fly
-without having to type in the definitions of package variants
-(@pxref{Defining Packages}).
+Another set of command-line options supported by @command{guix build} and
+also @command{guix package} are @dfn{package transformation options}.  These
+are options that make it possible to define @dfn{package variants}---for
+instance, packages built from different source code.  This is a convenient
+way to create customized packages on the fly without having to type in the
+definitions of package variants (@pxref{Pakete definieren}).
 
 @table @code
 
 @item address@hidden
 @itemx address@hidden@var{source}
 @itemx address@hidden@@@address@hidden
-Use @var{source} as the source of @var{package}, and @var{version} as
-its version number.
address@hidden must be a file name or a URL, as for @command{guix
-download} (@pxref{Invoking guix download}).
+Use @var{source} as the source of @var{package}, and @var{version} as its
+version number.  @var{source} must be a file name or a URL, as for
address@hidden download} (@pxref{Aufruf von guix download}).
 
-When @var{package} is omitted,
-it is taken to be the package name specified on the
-command line that matches the base of @var{source}---e.g.,
-if @var{source} is @code{/src/guile-2.0.10.tar.gz}, the corresponding
-package is @code{guile}.
+When @var{package} is omitted, it is taken to be the package name specified
+on the command line that matches the base of @var{source}---e.g., if
address@hidden is @code{/src/guile-2.0.10.tar.gz}, the corresponding package
+is @code{guile}.
 
 Likewise, when @var{version} is omitted, the version string is inferred from
 @var{source}; in the previous example, it is @code{2.0.10}.
 
-This option allows users to try out versions of packages other than the
-one provided by the distribution.  The example below downloads
address@hidden from a GNU mirror and uses that as the source for
-the @code{ed} package:
+This option allows users to try out versions of packages other than the one
+provided by the distribution.  The example below downloads
address@hidden from a GNU mirror and uses that as the source for the
address@hidden package:
 
 @example
 guix build ed --with-source=mirror://gnu/ed/ed-1.7.tar.gz
@@ -6313,53 +6447,50 @@ $ guix build guix --with-source=guix@@1.0=./guix
 @end example
 
 @item address@hidden@var{replacement}
-Replace dependency on @var{package} by a dependency on
address@hidden  @var{package} must be a package name, and
address@hidden must be a package specification such as @code{guile}
-or @code{guile@@1.8}.
+Replace dependency on @var{package} by a dependency on @var{replacement}.
address@hidden must be a package name, and @var{replacement} must be a
+package specification such as @code{guile} or @code{guile@@1.8}.
 
-For instance, the following command builds Guix, but replaces its
-dependency on the current stable version of Guile with a dependency on
-the legacy version of Guile, @code{guile@@2.0}:
+For instance, the following command builds Guix, but replaces its dependency
+on the current stable version of Guile with a dependency on the legacy
+version of Guile, @code{guile@@2.0}:
 
 @example
 guix build --with-input=guile=guile@@2.0 guix
 @end example
 
-This is a recursive, deep replacement.  So in this example, both
address@hidden and its dependency @code{guile-json} (which also depends on
address@hidden) get rebuilt against @code{guile@@2.0}.
+This is a recursive, deep replacement.  So in this example, both @code{guix}
+and its dependency @code{guile-json} (which also depends on @code{guile})
+get rebuilt against @code{guile@@2.0}.
 
 This is implemented using the @code{package-input-rewriting} Scheme
-procedure (@pxref{Defining Packages, @code{package-input-rewriting}}).
+procedure (@pxref{Pakete definieren, @code{package-input-rewriting}}).
 
 @item address@hidden@var{replacement}
 This is similar to @code{--with-input} but with an important difference:
-instead of rebuilding the whole dependency chain, @var{replacement} is
-built and then @dfn{grafted} onto the binaries that were initially
-referring to @var{package}.  @xref{Security Updates}, for more
-information on grafts.
+instead of rebuilding the whole dependency chain, @var{replacement} is built
+and then @dfn{grafted} onto the binaries that were initially referring to
address@hidden  @xref{Sicherheitsaktualisierungen}, for more information on 
grafts.
 
-For example, the command below grafts version 3.5.4 of GnuTLS onto Wget
-and all its dependencies, replacing references to the version of GnuTLS
-they currently refer to:
+For example, the command below grafts version 3.5.4 of GnuTLS onto Wget and
+all its dependencies, replacing references to the version of GnuTLS they
+currently refer to:
 
 @example
 guix build --with-graft=gnutls=gnutls@@3.5.4 wget
 @end example
 
-This has the advantage of being much faster than rebuilding everything.
-But there is a caveat: it works if and only if @var{package} and
address@hidden are strictly compatible---for example, if they provide
-a library, the application binary interface (ABI) of those libraries
-must be compatible.  If @var{replacement} is somehow incompatible with
address@hidden, then the resulting package may be unusable.  Use with
-care!
+This has the advantage of being much faster than rebuilding everything.  But
+there is a caveat: it works if and only if @var{package} and
address@hidden are strictly compatible---for example, if they provide a
+library, the application binary interface (ABI) of those libraries must be
+compatible.  If @var{replacement} is somehow incompatible with
address@hidden, then the resulting package may be unusable.  Use with care!
 
 @end table
 
address@hidden Additional Build Options
address@hidden Additional Build Options
address@hidden Zusätzliche Erstellungsoptionen
address@hidden Zusätzliche Erstellungsoptionen
 
 The command-line options presented below are specific to @command{guix
 build}.
@@ -6368,17 +6499,17 @@ build}.
 
 @item --quiet
 @itemx -q
-Build quietly, without displaying the build log.  Upon completion, the
-build log is kept in @file{/var} (or similar) and can always be
-retrieved using the @option{--log-file} option.
+Build quietly, without displaying the build log.  Upon completion, the build
+log is kept in @file{/var} (or similar) and can always be retrieved using
+the @option{--log-file} option.
 
 @item address@hidden
address@hidden -f @var{file}
-Build the package, derivation, or other file-like object that the code within
address@hidden evaluates to (@pxref{G-Expressions, file-like objects}).
address@hidden -f @var{Datei}
+Build the package, derivation, or other file-like object that the code
+within @var{file} evaluates to (@pxref{G-Ausdrücke, file-like objects}).
 
 As an example, @var{file} might contain a package definition like this
-(@pxref{Defining Packages}):
+(@pxref{Pakete definieren}):
 
 @example
 @verbatiminclude package-hello.scm
@@ -6388,16 +6519,15 @@ As an example, @var{file} might contain a package 
definition like this
 @itemx -e @var{expr}
 Build the package or derivation @var{expr} evaluates to.
 
-For example, @var{expr} may be @code{(@@ (gnu packages guile)
-guile-1.8)}, which unambiguously designates this specific variant of
-version 1.8 of Guile.
+For example, @var{expr} may be @code{(@@ (gnu packages guile)  guile-1.8)},
+which unambiguously designates this specific variant of version 1.8 of
+Guile.
 
-Alternatively, @var{expr} may be a G-expression, in which case it is used
-as a build program passed to @code{gexp->derivation}
-(@pxref{G-Expressions}).
+Alternatively, @var{expr} may be a G-expression, in which case it is used as
+a build program passed to @code{gexp->derivation} (@pxref{G-Ausdrücke}).
 
 Lastly, @var{expr} may refer to a zero-argument monadic procedure
-(@pxref{The Store Monad}).  The procedure must return a derivation as a
+(@pxref{Die Store-Monade}).  The procedure must return a derivation as a
 monadic value, which is then passed through @code{run-with-store}.
 
 @item --source
@@ -6406,25 +6536,24 @@ Build the source derivations of the packages, rather 
than the packages
 themselves.
 
 For instance, @code{guix build -S gcc} returns something like
address@hidden/gnu/store/@dots{}-gcc-4.7.2.tar.bz2}, which is the GCC
-source tarball.
address@hidden/gnu/store/@dots{}-gcc-4.7.2.tar.bz2}, which is the GCC source
+tarball.
 
-The returned source tarball is the result of applying any patches and
-code snippets specified in the package @code{origin} (@pxref{Defining
-Packages}).
+The returned source tarball is the result of applying any patches and code
+snippets specified in the package @code{origin} (@pxref{Pakete definieren}).
 
 @item --sources
 Fetch and return the source of @var{package-or-derivation} and all their
-dependencies, recursively.  This is a handy way to obtain a local copy
-of all the source code needed to build @var{packages}, allowing you to
-eventually build them even without network access.  It is an extension
-of the @code{--source} option and can accept one of the following
-optional argument values:
+dependencies, recursively.  This is a handy way to obtain a local copy of
+all the source code needed to build @var{packages}, allowing you to
+eventually build them even without network access.  It is an extension of
+the @code{--source} option and can accept one of the following optional
+argument values:
 
 @table @code
 @item package
-This value causes the @code{--sources} option to behave in the same way
-as the @code{--source} option.
+This value causes the @code{--sources} option to behave in the same way as
+the @code{--source} option.
 
 @item all
 Build the source derivations of all packages, including any source that
@@ -6439,8 +6568,8 @@ The following derivations will be built:
 
 @item transitive
 Build the source derivations of all packages, as well of all transitive
-inputs to the packages.  This can be used e.g. to
-prefetch package source for later offline building.
+inputs to the packages.  This can be used e.g. to prefetch package source
+for later offline building.
 
 @example
 $ guix build --sources=transitive tzdata
@@ -6456,42 +6585,41 @@ The following derivations will be built:
 
 @end table
 
address@hidden address@hidden
address@hidden address@hidden
 @itemx -s @var{system}
-Attempt to build for @var{system}---e.g., @code{i686-linux}---instead of
-the system type of the build host.
+Attempt to build for @var{system}---e.g., @code{i686-linux}---instead of the
+system type of the build host.
 
address@hidden Note
-The @code{--system} flag is for @emph{native} compilation and must not
-be confused with cross-compilation.  See @code{--target} below for
-information on cross-compilation.
address@hidden Anmerkung
+The @code{--system} flag is for @emph{native} compilation and must not be
+confused with cross-compilation.  See @code{--target} below for information
+on cross-compilation.
 @end quotation
 
 An example use of this is on Linux-based systems, which can emulate
-different personalities.  For instance, passing
address@hidden on an @code{x86_64-linux} system or
address@hidden on an @code{aarch64-linux} system allows you
-to build packages in a complete 32-bit environment.
+different personalities.  For instance, passing @code{--system=i686-linux}
+on an @code{x86_64-linux} system or @code{--system=armhf-linux} on an
address@hidden system allows you to build packages in a complete
+32-bit environment.
 
address@hidden Note
address@hidden Anmerkung
 Building for an @code{armhf-linux} system is unconditionally enabled on
 @code{aarch64-linux} machines, although certain aarch64 chipsets do not
 allow for this functionality, notably the ThunderX.
 @end quotation
 
-Similarly, when transparent emulation with QEMU and @code{binfmt_misc}
-is enabled (@pxref{Virtualization Services,
address@hidden), you can build for any system for
-which a QEMU @code{binfmt_misc} handler is installed.
+Similarly, when transparent emulation with QEMU and @code{binfmt_misc} is
+enabled (@pxref{Virtualisierungsdienste, @code{qemu-binfmt-service-type}}),
+you can build for any system for which a QEMU @code{binfmt_misc} handler is
+installed.
 
-Builds for a system other than that of the machine you are using can
-also be offloaded to a remote machine of the right architecture.
address@hidden Offload Setup}, for more information on offloading.
+Builds for a system other than that of the machine you are using can also be
+offloaded to a remote machine of the right architecture.  @xref{Auslagern des 
Daemons einrichten}, for more information on offloading.
 
 @item address@hidden
 @cindex cross-compilation
-Cross-build for @var{triplet}, which must be a valid GNU triplet, such
-as @code{"mips64el-linux-gnu"} (@pxref{Specifying target triplets, GNU
+Cross-build for @var{triplet}, which must be a valid GNU triplet, such as
address@hidden"mips64el-linux-gnu"} (@pxref{Specifying target triplets, GNU
 configuration triplets,, autoconf, Autoconf}).
 
 @anchor{build-check}
@@ -6502,18 +6630,19 @@ Rebuild @var{package-or-derivation}, which are already 
available in the
 store, and raise an error if the build results are not bit-for-bit
 identical.
 
-This mechanism allows you to check whether previously installed
-substitutes are genuine (@pxref{Substitutes}), or whether the build result
-of a package is deterministic.  @xref{Invoking guix challenge}, for more
-background information and tools.
+This mechanism allows you to check whether previously installed substitutes
+are genuine (@pxref{Substitute}), or whether the build result of a package
+is deterministic.  @xref{Aufruf von guix challenge}, for more background
+information and tools.
 
-When used in conjunction with @option{--keep-failed}, the differing
-output is kept in the store, under @file{/gnu/store/@dots{}-check}.
-This makes it easy to look for differences between the two results.
+Wenn dies zusammen mit @option{--keep-failed} benutzt wird, bleiben die sich
+unterscheidenden Ausgaben im Store unter dem Namen
address@hidden/gnu/store/@dots{}-check}. Dadurch können Unterschiede zwischen 
den
+beiden Ergebnissen leicht erkannt werden.
 
 @item --repair
 @cindex repairing store items
address@hidden corruption, recovering from
address@hidden Datenbeschädigung, Behebung
 Attempt to repair the specified store items, if they are corrupt, by
 re-downloading or rebuilding them.
 
@@ -6521,8 +6650,7 @@ This operation is not atomic and thus restricted to 
@code{root}.
 
 @item --derivations
 @itemx -d
-Return the derivation paths, not the output paths, of the given
-packages.
+Return the derivation paths, not the output paths, of the given packages.
 
 @item address@hidden
 @itemx -r @var{file}
@@ -6532,16 +6660,14 @@ Make @var{file} a symlink to the result, and register 
it as a garbage
 collector root.
 
 Consequently, the results of this @command{guix build} invocation are
-protected from garbage collection until @var{file} is removed.  When
-that option is omitted, build results are eligible for garbage
-collection as soon as the build completes.  @xref{Invoking guix gc}, for
-more on GC roots.
+protected from garbage collection until @var{file} is removed.  When that
+option is omitted, build results are eligible for garbage collection as soon
+as the build completes.  @xref{Aufruf von guix gc}, for more on GC roots.
 
 @item --log-file
 @cindex build logs, access
 Return the build log file names or URLs for the given
address@hidden, or raise an error if build logs are
-missing.
address@hidden, or raise an error if build logs are missing.
 
 This works regardless of how packages or derivations are specified.  For
 instance, the following invocations are equivalent:
@@ -6554,11 +6680,11 @@ guix build --log-file -e '(@@ (gnu packages guile) 
guile-2.0)'
 @end example
 
 If a log is unavailable locally, and unless @code{--no-substitutes} is
-passed, the command looks for a corresponding log on one of the
-substitute servers (as specified with @code{--substitute-urls}.)
+passed, the command looks for a corresponding log on one of the substitute
+servers (as specified with @code{--substitute-urls}.)
 
-So for instance, imagine you want to see the build log of GDB on MIPS,
-but you are actually on an @code{x86_64} machine:
+So for instance, imagine you want to see the build log of GDB on MIPS, but
+you are actually on an @code{x86_64} machine:
 
 @example
 $ guix build --log-file gdb -s mips64el-linux
@@ -6568,26 +6694,25 @@ https://hydra.gnu.org/log/@dots{}-gdb-7.10
 You can freely access a huge library of build logs!
 @end table
 
address@hidden Debugging Build Failures
address@hidden Debugging Build Failures
address@hidden Fehlschläge beim Erstellen untersuchen
address@hidden Fehlschläge beim Erstellen untersuchen
 
 @cindex build failures, debugging
-When defining a new package (@pxref{Defining Packages}), you will
-probably find yourself spending some time debugging and tweaking the
-build until it succeeds.  To do that, you need to operate the build
-commands yourself in an environment as close as possible to the one the
-build daemon uses.
+When defining a new package (@pxref{Pakete definieren}), you will probably
+find yourself spending some time debugging and tweaking the build until it
+succeeds.  To do that, you need to operate the build commands yourself in an
+environment as close as possible to the one the build daemon uses.
 
-To that end, the first thing to do is to use the @option{--keep-failed}
-or @option{-K} option of @command{guix build}, which will keep the
-failed build tree in @file{/tmp} or whatever directory you specified as
address@hidden (@pxref{Invoking guix build, @code{--keep-failed}}).
+To that end, the first thing to do is to use the @option{--keep-failed} or
address@hidden option of @command{guix build}, which will keep the failed build
+tree in @file{/tmp} or whatever directory you specified as @code{TMPDIR}
+(@pxref{Aufruf von guix build, @code{--keep-failed}}).
 
-From there on, you can @command{cd} to the failed build tree and source
-the @file{environment-variables} file, which contains all the
-environment variable definitions that were in place when the build
-failed.  So let's say you're debugging a build failure in package
address@hidden; a typical session would look like this:
+From there on, you can @command{cd} to the failed build tree and source the
address@hidden file, which contains all the environment
+variable definitions that were in place when the build failed.  So let's say
+you're debugging a build failure in package @code{foo}; a typical session
+would look like this:
 
 @example
 $ guix build foo -K
@@ -6600,14 +6725,14 @@ $ cd foo-1.2
 Now, you can invoke commands as if you were the daemon (almost) and
 troubleshoot your build process.
 
-Sometimes it happens that, for example, a package's tests pass when you
-run them manually but they fail when the daemon runs them.  This can
-happen because the daemon runs builds in containers where, unlike in our
-environment above, network access is missing, @file{/bin/sh} does not
-exist, etc. (@pxref{Build Environment Setup}).
+Sometimes it happens that, for example, a package's tests pass when you run
+them manually but they fail when the daemon runs them.  This can happen
+because the daemon runs builds in containers where, unlike in our
+environment above, network access is missing, @file{/bin/sh} does not exist,
+etc. (@pxref{Einrichten der Erstellungsumgebung}).
 
-In such cases, you may need to run inspect the build process from within
-a container similar to the one the build daemon creates:
+In such cases, you may need to run inspect the build process from within a
+container similar to the one the build daemon creates:
 
 @example
 $ guix build -K foo
@@ -6619,12 +6744,11 @@ $ guix environment --no-grafts -C foo --ad-hoc strace 
gdb
 @end example
 
 Here, @command{guix environment -C} creates a container and spawns a new
-shell in it (@pxref{Invoking guix environment}).  The @command{--ad-hoc
-strace gdb} part adds the @command{strace} and @command{gdb} commands to
-the container, which would may find handy while debugging.  The
address@hidden option makes sure we get the exact same
-environment, with ungrafted packages (@pxref{Security Updates}, for more
-info on grafts).
+shell in it (@pxref{Aufruf von guix environment}).  The @command{--ad-hoc
+strace gdb} part adds the @command{strace} and @command{gdb} commands to the
+container, which would may find handy while debugging.  The
address@hidden option makes sure we get the exact same environment,
+with ungrafted packages (@pxref{Sicherheitsaktualisierungen}, for more info on 
grafts).
 
 To get closer to a container like that used by the build daemon, we can
 remove @file{/bin/sh}:
@@ -6636,105 +6760,100 @@ remove @file{/bin/sh}:
 (Don't worry, this is harmless: this is all happening in the throw-away
 container created by @command{guix environment}.)
 
-The @command{strace} command is probably not in the search path, but we
-can run:
+The @command{strace} command is probably not in the search path, but we can
+run:
 
 @example
 [env]# $GUIX_ENVIRONMENT/bin/strace -f -o log make check
 @end example
 
-In this way, not only you will have reproduced the environment variables
-the daemon uses, you will also be running the build process in a container
+In this way, not only you will have reproduced the environment variables the
+daemon uses, you will also be running the build process in a container
 similar to the one the daemon uses.
 
 
address@hidden Invoking guix edit
address@hidden Aufruf von guix edit
 @section Invoking @command{guix edit}
 
 @cindex @command{guix edit}
 @cindex package definition, editing
-So many packages, so many source files!  The @command{guix edit} command
-facilitates the life of users and packagers by pointing their editor at
-the source file containing the definition of the specified packages.
-For instance:
+So many packages, so many source files! The @command{guix edit} command
+facilitates the life of users and packagers by pointing their editor at the
+source file containing the definition of the specified packages.  For
+instance:
 
 @example
 guix edit gcc@@4.9 vim
 @end example
 
 @noindent
-launches the program specified in the @code{VISUAL} or in the
address@hidden environment variable to view the recipe of address@hidden
-and that of Vim.
+launches the program specified in the @code{VISUAL} or in the @code{EDITOR}
+environment variable to view the recipe of address@hidden and that of Vim.
 
-If you are using a Guix Git checkout (@pxref{Building from Git}), or
-have created your own packages on @code{GUIX_PACKAGE_PATH}
-(@pxref{Package Modules}), you will be able to edit the package
-recipes.  In other cases, you will be able to examine the read-only recipes
-for packages currently in the store.
+If you are using a Guix Git checkout (@pxref{Erstellung aus dem Git}), or have
+created your own packages on @code{GUIX_PACKAGE_PATH} (@pxref{Paketmodule}), 
you will be able to edit the package recipes.  In other cases,
+you will be able to examine the read-only recipes for packages currently in
+the store.
 
 
address@hidden Invoking guix download
address@hidden Aufruf von guix download
 @section Invoking @command{guix download}
 
 @cindex @command{guix download}
 @cindex downloading package sources
-When writing a package definition, developers typically need to download
-a source tarball, compute its SHA256 hash, and write that
-hash in the package definition (@pxref{Defining Packages}).  The
address@hidden download} tool helps with this task: it downloads a file
-from the given URI, adds it to the store, and prints both its file name
-in the store and its SHA256 hash.
+When writing a package definition, developers typically need to download a
+source tarball, compute its SHA256 hash, and write that hash in the package
+definition (@pxref{Pakete definieren}).  The @command{guix download} tool
+helps with this task: it downloads a file from the given URI, adds it to the
+store, and prints both its file name in the store and its SHA256 hash.
 
 The fact that the downloaded file is added to the store saves bandwidth:
-when the developer eventually tries to build the newly defined package
-with @command{guix build}, the source tarball will not have to be
-downloaded again because it is already in the store.  It is also a
-convenient way to temporarily stash files, which may be deleted
-eventually (@pxref{Invoking guix gc}).
+when the developer eventually tries to build the newly defined package with
address@hidden build}, the source tarball will not have to be downloaded
+again because it is already in the store.  It is also a convenient way to
+temporarily stash files, which may be deleted eventually (@pxref{Aufruf von 
guix gc}).
 
 The @command{guix download} command supports the same URIs as used in
 package definitions.  In particular, it supports @code{mirror://} URIs.
address@hidden URIs (HTTP over TLS) are supported @emph{provided} the
-Guile bindings for GnuTLS are available in the user's environment; when
-they are not available, an error is raised.  @xref{Guile Preparations,
-how to install the GnuTLS bindings for Guile,, gnutls-guile,
-GnuTLS-Guile}, for more information.
address@hidden URIs (HTTP over TLS) are supported @emph{provided} the Guile
+bindings for GnuTLS are available in the user's environment; when they are
+not available, an error is raised.  @xref{Guile Preparations, how to install
+the GnuTLS bindings for Guile,, gnutls-guile, GnuTLS-Guile}, for more
+information.
 
address@hidden download} verifies HTTPS server certificates by loading
-the certificates of X.509 authorities from the directory pointed to by
-the @code{SSL_CERT_DIR} environment variable (@pxref{X.509
-Certificates}), unless @option{--no-check-certificate} is used.
address@hidden download} verifies HTTPS server certificates by loading the
+certificates of X.509 authorities from the directory pointed to by the
address@hidden environment variable (@pxref{X.509-Zertifikate}),
+unless @option{--no-check-certificate} is used.
 
 The following options are available:
 
 @table @code
 @item address@hidden
 @itemx -f @var{fmt}
-Write the hash in the format specified by @var{fmt}.  For more
-information on the valid values for @var{fmt}, @pxref{Invoking guix hash}.
+Write the hash in the format specified by @var{fmt}.  For more information
+on the valid values for @var{fmt}, @pxref{Aufruf von guix hash}.
 
 @item --no-check-certificate
 Do not validate the X.509 certificates of HTTPS servers.
 
-When using this option, you have @emph{absolutely no guarantee} that you
-are communicating with the authentic server responsible for the given
-URL, which makes you vulnerable to ``man-in-the-middle'' attacks.
+When using this option, you have @emph{absolutely no guarantee} that you are
+communicating with the authentic server responsible for the given URL, which
+makes you vulnerable to ``man-in-the-middle'' attacks.
 
 @item address@hidden
 @itemx -o @var{file}
-Save the downloaded file to @var{file} instead of adding it to the
-store.
+Save the downloaded file to @var{file} instead of adding it to the store.
 @end table
 
address@hidden Invoking guix hash
address@hidden Aufruf von guix hash
 @section Invoking @command{guix hash}
 
 @cindex @command{guix hash}
-The @command{guix hash} command computes the SHA256 hash of a file.
-It is primarily a convenience tool for anyone contributing to the
-distribution: it computes the cryptographic hash of a file, which can be
-used in the definition of a package (@pxref{Defining Packages}).
+The @command{guix hash} command computes the SHA256 hash of a file.  It is
+primarily a convenience tool for anyone contributing to the distribution: it
+computes the cryptographic hash of a file, which can be used in the
+definition of a package (@pxref{Pakete definieren}).
 
 The general syntax is:
 
@@ -6755,22 +6874,22 @@ Write the hash in the format specified by @var{fmt}.
 Supported formats: @code{nix-base32}, @code{base32}, @code{base16}
 (@code{hex} and @code{hexadecimal} can be used as well).
 
-If the @option{--format} option is not specified, @command{guix hash}
-will output the hash in @code{nix-base32}.  This representation is used
-in the definitions of packages.
+If the @option{--format} option is not specified, @command{guix hash} will
+output the hash in @code{nix-base32}.  This representation is used in the
+definitions of packages.
 
 @item --recursive
 @itemx -r
 Compute the hash on @var{file} recursively.
 
address@hidden FIXME: Replace xref above with xref to an ``Archive'' section 
when
address@hidden it exists.
 In this case, the hash is computed on an archive containing @var{file},
 including its children if it is a directory.  Some of the metadata of
 @var{file} is part of the archive; for instance, when @var{file} is a
 regular file, the hash is different depending on whether @var{file} is
-executable or not.  Metadata such as time stamps has no impact on the
-hash (@pxref{Invoking guix archive}).
address@hidden FIXME: Replace xref above with xref to an ``Archive'' section 
when
address@hidden it exists.
+executable or not.  Metadata such as time stamps has no impact on the hash
+(@pxref{Aufruf von guix archive}).
 
 @item --exclude-vcs
 @itemx -x
@@ -6779,8 +6898,7 @@ directories (@file{.bzr}, @file{.git}, @file{.hg}, etc.)
 
 @vindex git-fetch
 As an example, here is how you would compute the hash of a Git checkout,
-which is useful when using the @code{git-fetch} method (@pxref{origin
-Reference}):
+which is useful when using the @code{git-fetch} method 
(@pxref{„origin“-Referenz}):
 
 @example
 $ git clone http://example.org/foo.git
@@ -6789,19 +6907,18 @@ $ guix hash -rx .
 @end example
 @end table
 
address@hidden Invoking guix import
address@hidden Aufruf von guix import
 @section Invoking @command{guix import}
 
 @cindex importing packages
 @cindex package import
 @cindex package conversion
 @cindex Invoking @command{guix import}
-The @command{guix import} command is useful for people who would like to
-add a package to the distribution with as little work as
-possible---a legitimate demand.  The command knows of a few
-repositories from which it can ``import'' package metadata.  The result
-is a package definition, or a template thereof, in the format we know
-(@pxref{Defining Packages}).
+The @command{guix import} command is useful for people who would like to add
+a package to the distribution with as little work as possible---a legitimate
+demand.  The command knows of a few repositories from which it can
+``import'' package metadata.  The result is a package definition, or a
+template thereof, in the format we know (@pxref{Pakete definieren}).
 
 The general syntax is:
 
@@ -6809,19 +6926,18 @@ The general syntax is:
 guix import @var{importer} @address@hidden
 @end example
 
address@hidden specifies the source from which to import package
-metadata, and @var{options} specifies a package identifier and other
-options specific to @var{importer}.  Currently, the available
-``importers'' are:
address@hidden specifies the source from which to import package metadata,
+and @var{options} specifies a package identifier and other options specific
+to @var{importer}.  Currently, the available ``importers'' are:
 
 @table @code
 @item gnu
-Import metadata for the given GNU package.  This provides a template
-for the latest version of that GNU package, including the hash of its
-source tarball, and its canonical synopsis and description.
+Import metadata for the given GNU package.  This provides a template for the
+latest version of that GNU package, including the hash of its source
+tarball, and its canonical synopsis and description.
 
-Additional information such as the package dependencies and its
-license needs to be figured out manually.
+Additional information such as the package dependencies and its license
+needs to be figured out manually.
 
 For example, the following command returns a package definition for
 address@hidden:
@@ -6835,17 +6951,17 @@ Specific command-line options are:
 @table @code
 @item address@hidden
 As for @code{guix refresh}, specify the policy to handle missing OpenPGP
-keys when verifying the package signature.  @xref{Invoking guix
-refresh, @code{--key-download}}.
+keys when verifying the package signature.  @xref{Aufruf von guix refresh,
address@hidden
 @end table
 
 @item pypi
 @cindex pypi
 Import metadata from the @uref{https://pypi.python.org/, Python Package
 address@hidden functionality requires Guile-JSON to be installed.
address@hidden  Information is taken from the JSON-formatted
-description available at @code{pypi.python.org} and usually includes all
-the relevant information, including package dependencies.  For maximum
address@hidden  Information is taken from the JSON-formatted
+description available at @code{pypi.python.org} and usually includes all the
+relevant information, including package dependencies.  For maximum
 efficiency, it is recommended to install the @command{unzip} utility, so
 that the importer can unzip Python wheels and gather data from them.
 
@@ -6859,23 +6975,22 @@ guix import pypi itsdangerous
 @table @code
 @item --recursive
 @itemx -r
-Traverse the dependency graph of the given upstream package recursively
-and generate package expressions for all those packages that are not yet
-in Guix.
+Traverse the dependency graph of the given upstream package recursively and
+generate package expressions for all those packages that are not yet in
+Guix.
 @end table
 
 @item gem
 @cindex gem
-Import metadata from @uref{https://rubygems.org/,
address@hidden functionality requires Guile-JSON to be
-installed.  @xref{Requirements}.}.  Information is taken from the
-JSON-formatted description available at @code{rubygems.org} and includes
-most relevant information, including runtime dependencies.  There are
-some caveats, however.  The metadata doesn't distinguish between
-synopses and descriptions, so the same string is used for both fields.
-Additionally, the details of non-Ruby dependencies required to build
-native extensions is unavailable and left as an exercise to the
-packager.
+Import metadata from @uref{https://rubygems.org/, address@hidden
+functionality requires Guile-JSON to be installed.  @xref{Voraussetzungen}.}.
+Information is taken from the JSON-formatted description available at
address@hidden and includes most relevant information, including
+runtime dependencies.  There are some caveats, however.  The metadata
+doesn't distinguish between synopses and descriptions, so the same string is
+used for both fields.  Additionally, the details of non-Ruby dependencies
+required to build native extensions is unavailable and left as an exercise
+to the packager.
 
 The command below imports metadata for the @code{rails} Ruby package:
 
@@ -6886,25 +7001,24 @@ guix import gem rails
 @table @code
 @item --recursive
 @itemx -r
-Traverse the dependency graph of the given upstream package recursively
-and generate package expressions for all those packages that are not yet
-in Guix.
+Traverse the dependency graph of the given upstream package recursively and
+generate package expressions for all those packages that are not yet in
+Guix.
 @end table
 
 @item cpan
 @cindex CPAN
-Import metadata from @uref{https://www.metacpan.org/, address@hidden
-functionality requires Guile-JSON to be installed.
address@hidden
-Information is taken from the JSON-formatted metadata provided through
address@hidden://fastapi.metacpan.org/, MetaCPAN's API} and includes most
-relevant information, such as module dependencies.  License information
-should be checked closely.  If Perl is available in the store, then the
address@hidden utility will be used to filter core modules out of the
-list of dependencies.
+Import metadata from @uref{https://www.metacpan.org/,
address@hidden functionality requires Guile-JSON to be installed.
address@hidden  Information is taken from the JSON-formatted
+metadata provided through @uref{https://fastapi.metacpan.org/, MetaCPAN's
+API} and includes most relevant information, such as module dependencies.
+License information should be checked closely.  If Perl is available in the
+store, then the @code{corelist} utility will be used to filter core modules
+out of the list of dependencies.
 
-The command command below imports metadata for the @code{Acme::Boolean}
-Perl module:
+The command command below imports metadata for the @code{Acme::Boolean} Perl
+module:
 
 @example
 guix import cpan Acme::Boolean
@@ -6913,33 +7027,31 @@ guix import cpan Acme::Boolean
 @item cran
 @cindex CRAN
 @cindex Bioconductor
-Import metadata from @uref{https://cran.r-project.org/, CRAN}, the
-central repository for the @uref{http://r-project.org, address@hidden
-statistical and graphical environment}.
+Import metadata from @uref{https://cran.r-project.org/, CRAN}, the central
+repository for the @uref{http://r-project.org, address@hidden statistical and
+graphical environment}.
 
 Information is extracted from the @code{DESCRIPTION} file of the package.
 
-The command command below imports metadata for the @code{Cairo}
-R package:
+The command command below imports metadata for the @code{Cairo} R package:
 
 @example
 guix import cran Cairo
 @end example
 
-When @code{--recursive} is added, the importer will traverse the
-dependency graph of the given upstream package recursively and generate
-package expressions for all those packages that are not yet in Guix.
+When @code{--recursive} is added, the importer will traverse the dependency
+graph of the given upstream package recursively and generate package
+expressions for all those packages that are not yet in Guix.
 
 When @code{--archive=bioconductor} is added, metadata is imported from
 @uref{https://www.bioconductor.org/, Bioconductor}, a repository of R
-packages for for the analysis and comprehension of high-throughput
-genomic data in bioinformatics.
+packages for for the analysis and comprehension of high-throughput genomic
+data in bioinformatics.
 
 Information is extracted from the @code{DESCRIPTION} file of a package
 published on the web interface of the Bioconductor SVN repository.
 
-The command below imports metadata for the @code{GenomicRanges}
-R package:
+The command below imports metadata for the @code{GenomicRanges} R package:
 
 @example
 guix import cran --archive=bioconductor GenomicRanges
@@ -6948,30 +7060,29 @@ guix import cran --archive=bioconductor GenomicRanges
 @item texlive
 @cindex TeX Live
 @cindex CTAN
-Import metadata from @uref{http://www.ctan.org/, CTAN}, the
-comprehensive TeX archive network for TeX packages that are part of the
+Import metadata from @uref{http://www.ctan.org/, CTAN}, the comprehensive
+TeX archive network for TeX packages that are part of the
 @uref{https://www.tug.org/texlive/, TeX Live distribution}.
 
-Information about the package is obtained through the XML API provided
-by CTAN, while the source code is downloaded from the SVN repository of
-the Tex Live project.  This is done because the CTAN does not keep
-versioned archives.
+Information about the package is obtained through the XML API provided by
+CTAN, while the source code is downloaded from the SVN repository of the Tex
+Live project.  This is done because the CTAN does not keep versioned
+archives.
 
-The command command below imports metadata for the @code{fontspec}
-TeX package:
+The command command below imports metadata for the @code{fontspec} TeX
+package:
 
 @example
 guix import texlive fontspec
 @end example
 
-When @code{--archive=DIRECTORY} is added, the source code is downloaded
-not from the @file{latex} sub-directory of the @file{texmf-dist/source}
-tree in the TeX Live SVN repository, but from the specified sibling
-directory under the same root.
+When @code{--archive=DIRECTORY} is added, the source code is downloaded not
+from the @file{latex} sub-directory of the @file{texmf-dist/source} tree in
+the TeX Live SVN repository, but from the specified sibling directory under
+the same root.
 
-The command below imports metadata for the @code{ifxetex} package from
-CTAN while fetching the sources from the directory
address@hidden/source/generic}:
+The command below imports metadata for the @code{ifxetex} package from CTAN
+while fetching the sources from the directory @file{texmf/source/generic}:
 
 @example
 guix import texlive --archive=generic ifxetex
@@ -6979,10 +7090,9 @@ guix import texlive --archive=generic ifxetex
 
 @item json
 @cindex JSON, import
-Import package metadata from a local JSON address@hidden
-functionality requires Guile-JSON to be installed.
address@hidden  Consider the following example package
-definition in JSON format:
+Import package metadata from a local JSON address@hidden functionality
+requires Guile-JSON to be installed.  @xref{Voraussetzungen}.}.  Consider the
+following example package definition in JSON format:
 
 @example
 @{
@@ -6999,9 +7109,9 @@ definition in JSON format:
 @end example
 
 The field names are the same as for the @code{<package>} record
-(@xref{Defining Packages}).  References to other packages are provided
-as JSON lists of quoted package specification strings such as
address@hidden or @code{guile@@2.0}.
+(@xref{Pakete definieren}).  References to other packages are provided as
+JSON lists of quoted package specification strings such as @code{guile} or
address@hidden@@2.0}.
 
 The importer also supports a more explicit source definition using the
 common fields for @code{<origin>} records:
@@ -7020,8 +7130,8 @@ common fields for @code{<origin>} records:
 @}
 @end example
 
-The command below reads metadata from the JSON file @code{hello.json}
-and outputs a package expression:
+The command below reads metadata from the JSON file @code{hello.json} and
+outputs a package expression:
 
 @example
 guix import json hello.json
@@ -7029,16 +7139,15 @@ guix import json hello.json
 
 @item nix
 Import metadata from a local copy of the source of the
address@hidden://nixos.org/nixpkgs/, Nixpkgs address@hidden
-relies on the @command{nix-instantiate} command of
address@hidden://nixos.org/nix/, Nix}.}.  Package definitions in Nixpkgs are
-typically written in a mixture of Nix-language and Bash code.  This
-command only imports the high-level package structure that is written in
-the Nix language.  It normally includes all the basic fields of a
-package definition.
address@hidden://nixos.org/nixpkgs/, Nixpkgs address@hidden relies
+on the @command{nix-instantiate} command of @uref{http://nixos.org/nix/,
+Nix}.}.  Package definitions in Nixpkgs are typically written in a mixture
+of Nix-language and Bash code.  This command only imports the high-level
+package structure that is written in the Nix language.  It normally includes
+all the basic fields of a package definition.
 
-When importing a GNU package, the synopsis and descriptions are replaced
-by their canonical upstream variant.
+When importing a GNU package, the synopsis and descriptions are replaced by
+their canonical upstream variant.
 
 Usually, you will first need to do:
 
@@ -7050,8 +7159,8 @@ export NIX_REMOTE=daemon
 so that @command{nix-instantiate} does not try to open the Nix database.
 
 As an example, the command below imports the package definition of
-LibreOffice (more precisely, it imports the definition of the package
-bound to the @code{libreoffice} top-level attribute):
+LibreOffice (more precisely, it imports the definition of the package bound
+to the @code{libreoffice} top-level attribute):
 
 @example
 guix import nix ~/path/to/nixpkgs libreoffice
@@ -7075,24 +7184,24 @@ Read a Cabal file from standard input.
 Do not include dependencies required only by the test suites.
 @item address@hidden
 @itemx -e @var{alist}
address@hidden is a Scheme alist defining the environment in which the
-Cabal conditionals are evaluated.  The accepted keys are: @code{os},
address@hidden, @code{impl} and a string representing the name of a flag.
-The value associated with a flag has to be either the symbol
address@hidden or @code{false}.  The value associated with other keys
-has to conform to the Cabal file format definition.  The default value
-associated with the keys @code{os}, @code{arch} and @code{impl} is
address@hidden, @samp{x86_64} and @samp{ghc}, respectively.
address@hidden is a Scheme alist defining the environment in which the Cabal
+conditionals are evaluated.  The accepted keys are: @code{os}, @code{arch},
address@hidden and a string representing the name of a flag.  The value
+associated with a flag has to be either the symbol @code{true} or
address@hidden  The value associated with other keys has to conform to the
+Cabal file format definition.  The default value associated with the keys
address@hidden, @code{arch} and @code{impl} is @samp{linux}, @samp{x86_64} and
address@hidden, respectively.
 @item --recursive
 @itemx -r
-Traverse the dependency graph of the given upstream package recursively
-and generate package expressions for all those packages that are not yet
-in Guix.
+Traverse the dependency graph of the given upstream package recursively and
+generate package expressions for all those packages that are not yet in
+Guix.
 @end table
 
-The command below imports metadata for the latest version of the
address@hidden Haskell package without including test dependencies and
-specifying the value of the flag @samp{network-uri} as @code{false}:
+The command below imports metadata for the latest version of the @code{HTTP}
+Haskell package without including test dependencies and specifying the value
+of the flag @samp{network-uri} as @code{false}:
 
 @example
 guix import hackage -t -e "'((\"network-uri\" . false))" HTTP
@@ -7107,12 +7216,11 @@ guix import hackage mtl@@2.1.3.1
 
 @item stackage
 @cindex stackage
-The @code{stackage} importer is a wrapper around the @code{hackage} one.
-It takes a package name, looks up the package version included in a
-long-term support (LTS) @uref{https://www.stackage.org, Stackage}
-release and uses the @code{hackage} importer to retrieve its metadata.
-Note that it is up to you to select an LTS release compatible with the
-GHC compiler used by Guix.
+The @code{stackage} importer is a wrapper around the @code{hackage} one.  It
+takes a package name, looks up the package version included in a long-term
+support (LTS) @uref{https://www.stackage.org, Stackage} release and uses the
address@hidden importer to retrieve its metadata.  Note that it is up to you
+to select an LTS release compatible with the GHC compiler used by Guix.
 
 Specific command-line options are:
 
@@ -7126,9 +7234,9 @@ Do not include dependencies required only by the test 
suites.
 release is used.
 @item --recursive
 @itemx -r
-Traverse the dependency graph of the given upstream package recursively
-and generate package expressions for all those packages that are not yet
-in Guix.
+Traverse the dependency graph of the given upstream package recursively and
+generate package expressions for all those packages that are not yet in
+Guix.
 @end table
 
 The command below imports metadata for the @code{HTTP} Haskell package
@@ -7140,8 +7248,8 @@ guix import stackage --lts-version=7.18 HTTP
 
 @item elpa
 @cindex elpa
-Import metadata from an Emacs Lisp Package Archive (ELPA) package
-repository (@pxref{Packages,,, emacs, The GNU Emacs Manual}).
+Import metadata from an Emacs Lisp Package Archive (ELPA) package repository
+(@pxref{Packages,,, emacs, The GNU Emacs Manual}).
 
 Specific command-line options are:
 
@@ -7156,11 +7264,10 @@ are:
 @uref{http://elpa.gnu.org/packages, GNU}, selected by the @code{gnu}
 identifier.  This is the default.
 
-Packages from @code{elpa.gnu.org} are signed with one of the keys
-contained in the GnuPG keyring at
address@hidden/emacs/25.1/etc/package-keyring.gpg} (or similar) in the
address@hidden package (@pxref{Package Installation, ELPA package
-signatures,, emacs, The GNU Emacs Manual}).
+Packages from @code{elpa.gnu.org} are signed with one of the keys contained
+in the GnuPG keyring at @file{share/emacs/25.1/etc/package-keyring.gpg} (or
+similar) in the @code{emacs} package (@pxref{Package Installation, ELPA
+package signatures,, emacs, The GNU Emacs Manual}).
 
 @item
 @uref{http://stable.melpa.org/packages, MELPA-Stable}, selected by the
@@ -7173,9 +7280,9 @@ identifier.
 
 @item --recursive
 @itemx -r
-Traverse the dependency graph of the given upstream package recursively
-and generate package expressions for all those packages that are not yet
-in Guix.
+Traverse the dependency graph of the given upstream package recursively and
+generate package expressions for all those packages that are not yet in
+Guix.
 @end table
 
 @item crate
@@ -7191,17 +7298,17 @@ repository used by the OCaml community.
 @end table
 
 The structure of the @command{guix import} code is modular.  It would be
-useful to have more importers for other package formats, and your help
-is welcome here (@pxref{Contributing}).
+useful to have more importers for other package formats, and your help is
+welcome here (@pxref{Mitwirken}).
 
address@hidden Invoking guix refresh
address@hidden Aufruf von guix refresh
 @section Invoking @command{guix refresh}
 
address@hidden @command {guix refresh}
-The primary audience of the @command{guix refresh} command is developers
-of the GNU software distribution.  By default, it reports any packages
-provided by the distribution that are outdated compared to the latest
-upstream version, like this:
address@hidden @command{guix refresh}
+The primary audience of the @command{guix refresh} command is developers of
+the GNU software distribution.  By default, it reports any packages provided
+by the distribution that are outdated compared to the latest upstream
+version, like this:
 
 @example
 $ guix refresh
@@ -7209,8 +7316,8 @@ gnu/packages/gettext.scm:29:13: gettext would be upgraded 
from 0.18.1.1 to 0.18.
 gnu/packages/glib.scm:77:12: glib would be upgraded from 2.34.3 to 2.37.0
 @end example
 
-Alternately, one can specify packages to consider, in which case a
-warning is emitted for packages that lack an updater:
+Alternately, one can specify packages to consider, in which case a warning
+is emitted for packages that lack an updater:
 
 @example
 $ guix refresh coreutils guile guile-ssh
@@ -7218,18 +7325,18 @@ gnu/packages/ssh.scm:205:2: warning: no updater for 
guile-ssh
 gnu/packages/guile.scm:136:12: guile would be upgraded from 2.0.12 to 2.0.13
 @end example
 
address@hidden refresh} browses the upstream repository of each package and 
determines
-the highest version number of the releases therein.  The command
-knows how to update specific types of packages: GNU packages, ELPA
-packages, etc.---see the documentation for @option{--type} below.  There
-are many packages, though, for which it lacks a method to determine
-whether a new upstream release is available.  However, the mechanism is
-extensible, so feel free to get in touch with us to add a new method!
address@hidden refresh} browses the upstream repository of each package and
+determines the highest version number of the releases therein.  The command
+knows how to update specific types of packages: GNU packages, ELPA packages,
+etc.---see the documentation for @option{--type} below.  There are many
+packages, though, for which it lacks a method to determine whether a new
+upstream release is available.  However, the mechanism is extensible, so
+feel free to get in touch with us to add a new method!
 
-Sometimes the upstream name differs from the package name used in Guix,
-and @command{guix refresh} needs a little help.  Most updaters honor the
address@hidden property in package definitions, which can be used
-to that effect:
+Sometimes the upstream name differs from the package name used in Guix, and
address@hidden refresh} needs a little help.  Most updaters honor the
address@hidden property in package definitions, which can be used to
+that effect:
 
 @example
 (define-public network-manager
@@ -7239,16 +7346,16 @@ to that effect:
     (properties '((upstream-name . "NetworkManager")))))
 @end example
 
-When passed @code{--update}, it modifies distribution source files to
-update the version numbers and source tarball hashes of those package
-recipes (@pxref{Defining Packages}).  This is achieved by downloading
-each package's latest source tarball and its associated OpenPGP
-signature, authenticating the downloaded tarball against its signature
-using @command{gpg}, and finally computing its hash.  When the public
-key used to sign the tarball is missing from the user's keyring, an
-attempt is made to automatically retrieve it from a public key server;
-when this is successful, the key is added to the user's keyring; otherwise,
address@hidden refresh} reports an error.
+When passed @code{--update}, it modifies distribution source files to update
+the version numbers and source tarball hashes of those package recipes
+(@pxref{Pakete definieren}).  This is achieved by downloading each package's
+latest source tarball and its associated OpenPGP signature, authenticating
+the downloaded tarball against its signature using @command{gpg}, and
+finally computing its hash.  When the public key used to sign the tarball is
+missing from the user's keyring, an attempt is made to automatically
+retrieve it from a public key server; when this is successful, the key is
+added to the user's keyring; otherwise, @command{guix refresh} reports an
+error.
 
 The following options are supported:
 
@@ -7264,20 +7371,19 @@ This is useful to precisely refer to a package, as in 
this example:
 guix refresh -l -e '(@@@@ (gnu packages commencement) glibc-final)'
 @end example
 
-This command lists the dependents of the ``final'' libc (essentially all
-the packages.)
+This command lists the dependents of the ``final'' libc (essentially all the
+packages.)
 
 @item --update
 @itemx -u
 Update distribution source files (package recipes) in place.  This is
-usually run from a checkout of the Guix source tree (@pxref{Running
-Guix Before It Is Installed}):
+usually run from a checkout of the Guix source tree (@pxref{Guix vor der 
Installation ausführen}):
 
 @example
 $ ./pre-inst-env guix refresh -s non-core -u
 @end example
 
address@hidden Packages}, for more information on package definitions.
address@hidden definieren}, for more information on package definitions.
 
 @item address@hidden
 @itemx -s @var{subset}
@@ -7285,25 +7391,25 @@ Select all the packages in @var{subset}, one of 
@code{core} or
 @code{non-core}.
 
 The @code{core} subset refers to all the packages at the core of the
-distribution---i.e., packages that are used to build ``everything
-else''.  This includes GCC, libc, Binutils, Bash, etc.  Usually,
-changing one of these packages in the distribution entails a rebuild of
-all the others.  Thus, such updates are an inconvenience to users in
-terms of build time or bandwidth used to achieve the upgrade.
+distribution---i.e., packages that are used to build ``everything else''.
+This includes GCC, libc, Binutils, Bash, etc.  Usually, changing one of
+these packages in the distribution entails a rebuild of all the others.
+Thus, such updates are an inconvenience to users in terms of build time or
+bandwidth used to achieve the upgrade.
 
 The @code{non-core} subset refers to the remaining packages.  It is
 typically useful in cases where an update of the core packages would be
 inconvenient.
 
address@hidden address@hidden
address@hidden -m @var{file}
address@hidden address@hidden
address@hidden -m @var{Datei}
 Select all the packages from the manifest in @var{file}. This is useful to
 check if any packages of the user manifest can be updated.
 
 @item address@hidden
 @itemx -t @var{updater}
-Select only packages handled by @var{updater} (may be a comma-separated
-list of updaters).  Currently, @var{updater} may be one of:
+Select only packages handled by @var{updater} (may be a comma-separated list
+of updaters).  Currently, @var{updater} may be one of:
 
 @table @code
 @item gnu
@@ -7321,7 +7427,8 @@ the updater for @uref{http://elpa.gnu.org/, ELPA} 
packages;
 @item cran
 the updater for @uref{https://cran.r-project.org/, CRAN} packages;
 @item bioconductor
-the updater for @uref{https://www.bioconductor.org/, Bioconductor} R packages;
+the updater for @uref{https://www.bioconductor.org/, Bioconductor} R
+packages;
 @item cpan
 the updater for @uref{http://www.cpan.org/, CPAN} packages;
 @item pypi
@@ -7349,22 +7456,21 @@ gnu/packages/emacs.scm:856:13: emacs-auctex would be 
upgraded from 11.88.6 to 11
 
 @end table
 
-In addition, @command{guix refresh} can be passed one or more package
-names, as in this example:
+In addition, @command{guix refresh} can be passed one or more package names,
+as in this example:
 
 @example
 $ ./pre-inst-env guix refresh -u emacs idutils gcc@@4.8
 @end example
 
 @noindent
-The command above specifically updates the @code{emacs} and
address@hidden packages.  The @code{--select} option would have no
-effect in this case.
+The command above specifically updates the @code{emacs} and @code{idutils}
+packages.  The @code{--select} option would have no effect in this case.
 
-When considering whether to upgrade a package, it is sometimes
-convenient to know which packages would be affected by the upgrade and
-should be checked for compatibility.  For this the following option may
-be used when passing @command{guix refresh} one or more package names:
+When considering whether to upgrade a package, it is sometimes convenient to
+know which packages would be affected by the upgrade and should be checked
+for compatibility.  For this the following option may be used when passing
address@hidden refresh} one or more package names:
 
 @table @code
 
@@ -7372,23 +7478,23 @@ be used when passing @command{guix refresh} one or more 
package names:
 @itemx -L
 List available updaters and exit (see @option{--type} above.)
 
-For each updater, display the fraction of packages it covers; at the
-end, display the fraction of packages covered by all these updaters.
+For each updater, display the fraction of packages it covers; at the end,
+display the fraction of packages covered by all these updaters.
 
 @item --list-dependent
 @itemx -l
-List top-level dependent packages that would need to be rebuilt as a
-result of upgrading one or more packages.
+List top-level dependent packages that would need to be rebuilt as a result
+of upgrading one or more packages.
 
address@hidden guix graph, the @code{reverse-package} type of
address@hidden graph}}, for information on how to visualize the list of
-dependents of a package.
address@hidden von guix graph, the @code{reverse-package} type of @command{guix
+graph}}, for information on how to visualize the list of dependents of a
+package.
 
 @end table
 
-Be aware that the @code{--list-dependent} option only
address@hidden the rebuilds that would be required as a result of
-an upgrade.  More rebuilds might be required under some circumstances.
+Be aware that the @code{--list-dependent} option only @emph{approximates}
+the rebuilds that would be required as a result of an upgrade.  More
+rebuilds might be required under some circumstances.
 
 @example
 $ guix refresh --list-dependent flex
@@ -7396,28 +7502,28 @@ Building the following 120 packages would ensure 213 
dependent packages are rebu
 hop@@2.4.0 geiser@@0.4 notmuch@@0.18 mu@@0.9.9.5 cflow@@1.4 idutils@@4.6 
@dots{}
 @end example
 
-The command above lists a set of packages that could be built to check
-for compatibility with an upgraded @code{flex} package.
+The command above lists a set of packages that could be built to check for
+compatibility with an upgraded @code{flex} package.
 
 The following options can be used to customize GnuPG operation:
 
 @table @code
 
 @item address@hidden
-Use @var{command} as the GnuPG 2.x command.  @var{command} is searched
-for in @code{$PATH}.
+Use @var{command} as the GnuPG 2.x command.  @var{command} is searched for
+in @code{$PATH}.
 
 @item address@hidden
 Use @var{file} as the keyring for upstream keys.  @var{file} must be in the
 @dfn{keybox format}.  Keybox files usually have a name ending in @file{.kbx}
 and the address@hidden Guard (GPG) can manipulate these files
-(@pxref{kbxutil, @command{kbxutil},, gnupg, Using the GNU Privacy Guard}, for
-information on a tool to manipulate keybox files).
+(@pxref{kbxutil, @command{kbxutil},, gnupg, Using the GNU Privacy Guard},
+for information on a tool to manipulate keybox files).
 
 When this option is omitted, @command{guix refresh} uses
 @file{~/.config/guix/upstream/trustedkeys.kbx} as the keyring for upstream
-signing keys.  OpenPGP signatures are checked against keys from this keyring;
-missing keys are downloaded to this keyring as well (see
+signing keys.  OpenPGP signatures are checked against keys from this
+keyring; missing keys are downloaded to this keyring as well (see
 @option{--key-download} below.)
 
 You can export keys from your default GPG keyring into a keybox file using
@@ -7438,20 +7544,19 @@ gpg --no-default-keyring --keyring mykeyring.kbx \
 Privacy Guard}, for more information on GPG's @option{--keyring} option.
 
 @item address@hidden
-Handle missing OpenPGP keys according to @var{policy}, which may be one
-of:
+Handle missing OpenPGP keys according to @var{policy}, which may be one of:
 
 @table @code
 @item always
-Always download missing OpenPGP keys from the key server, and add them
-to the user's GnuPG keyring.
+Always download missing OpenPGP keys from the key server, and add them to
+the user's GnuPG keyring.
 
 @item never
 Never try to download missing OpenPGP keys.  Instead just bail out.
 
 @item interactive
-When a package signed with an unknown OpenPGP key is encountered, ask
-the user whether to download it or not.  This is the default behavior.
+When a package signed with an unknown OpenPGP key is encountered, ask the
+user whether to download it or not.  This is the default behavior.
 @end table
 
 @item address@hidden
@@ -7459,28 +7564,27 @@ Use @var{host} as the OpenPGP key server when importing 
a public key.
 
 @end table
 
-The @code{github} updater uses the
address@hidden://developer.github.com/v3/, GitHub API} to query for new
-releases.  When used repeatedly e.g. when refreshing all packages,
-GitHub will eventually refuse to answer any further API requests.  By
-default 60 API requests per hour are allowed, and a full refresh on all
-GitHub packages in Guix requires more than this.  Authentication with
-GitHub through the use of an API token alleviates these limits.  To use
-an API token, set the environment variable @code{GUIX_GITHUB_TOKEN} to a
-token procured from @uref{https://github.com/settings/tokens} or
-otherwise.
+The @code{github} updater uses the @uref{https://developer.github.com/v3/,
+GitHub API} to query for new releases.  When used repeatedly e.g. when
+refreshing all packages, GitHub will eventually refuse to answer any further
+API requests.  By default 60 API requests per hour are allowed, and a full
+refresh on all GitHub packages in Guix requires more than this.
+Authentication with GitHub through the use of an API token alleviates these
+limits.  To use an API token, set the environment variable
address@hidden to a token procured from
address@hidden://github.com/settings/tokens} or otherwise.
 
 
address@hidden Invoking guix lint
address@hidden Aufruf von guix lint
 @section Invoking @command{guix lint}
 
 @cindex @command{guix lint}
 @cindex package, checking for errors
 The @command{guix lint} command is meant to help package developers avoid
-common errors and use a consistent style.  It runs a number of checks on
-a given set of packages in order to find common mistakes in their
-definitions.  Available @dfn{checkers} include (see
address@hidden for a complete list):
+common errors and use a consistent style.  It runs a number of checks on a
+given set of packages in order to find common mistakes in their
+definitions.  Available @dfn{checkers} include (see @code{--list-checkers}
+for a complete list):
 
 @table @code
 @item synopsis
@@ -7496,18 +7600,16 @@ Identify inputs that should most likely be native 
inputs.
 @itemx mirror-url
 @itemx source-file-name
 Probe @code{home-page} and @code{source} URLs and report those that are
-invalid.  Suggest a @code{mirror://} URL when applicable.  Check that
-the source file name is meaningful, e.g. is not
-just a version number or ``git-checkout'', without a declared
address@hidden (@pxref{origin Reference}).
+invalid.  Suggest a @code{mirror://} URL when applicable.  Check that the
+source file name is meaningful, e.g. is not just a version number or
+``git-checkout'', without a declared @code{file-name} 
(@pxref{„origin“-Referenz}).
 
 @item cve
 @cindex security vulnerabilities
 @cindex CVE, Common Vulnerabilities and Exposures
 Report known vulnerabilities found in the Common Vulnerabilities and
 Exposures (CVE) databases of the current and past year
address@hidden://nvd.nist.gov/download.cfm#CVE_FEED, published by the US
-NIST}.
address@hidden://nvd.nist.gov/download.cfm#CVE_FEED, published by the US NIST}.
 
 To view information about a particular vulnerability, visit pages such as:
 
@@ -7523,9 +7625,9 @@ where @code{CVE-YYYY-ABCD} is the CVE identifier---e.g.,
 @code{CVE-2015-7554}.
 
 Package developers can specify in package recipes the
address@hidden://nvd.nist.gov/cpe.cfm,Common Platform Enumeration (CPE)}
-name and version of the package when they differ from the name or version
-that Guix uses, as in this example:
address@hidden://nvd.nist.gov/cpe.cfm,Common Platform Enumeration (CPE)} name
+and version of the package when they differ from the name or version that
+Guix uses, as in this example:
 
 @example
 (package
@@ -7537,10 +7639,10 @@ that Guix uses, as in this example:
 @end example
 
 @c See <http://www.openwall.com/lists/oss-security/2017/03/15/3>.
-Some entries in the CVE database do not specify which version of a
-package they apply to, and would thus ``stick around'' forever.  Package
-developers who found CVE alerts and verified they can be ignored can
-declare them as in this example:
+Some entries in the CVE database do not specify which version of a package
+they apply to, and would thus ``stick around'' forever.  Package developers
+who found CVE alerts and verified they can be ignored can declare them as in
+this example:
 
 @example
 (package
@@ -7554,8 +7656,8 @@ declare them as in this example:
 @end example
 
 @item formatting
-Warn about obvious source code formatting issues: trailing white space,
-use of tabulations, etc.
+Warn about obvious source code formatting issues: trailing white space, use
+of tabulations, etc.
 @end table
 
 The general syntax is:
@@ -7575,29 +7677,27 @@ and exit.
 
 @item --checkers
 @itemx -c
-Only enable the checkers specified in a comma-separated list using the
-names returned by @code{--list-checkers}.
+Only enable the checkers specified in a comma-separated list using the names
+returned by @code{--list-checkers}.
 
 @end table
 
address@hidden Invoking guix size
address@hidden Aufruf von guix size
 @section Invoking @command{guix size}
 
 @cindex size
 @cindex package size
address@hidden closure
address@hidden Abschluss
 @cindex @command{guix size}
-The @command{guix size} command helps package developers profile the
-disk usage of packages.  It is easy to overlook the impact of an
-additional dependency added to a package, or the impact of using a
-single output for a package that could easily be split (@pxref{Packages
-with Multiple Outputs}).  Such are the typical issues that
address@hidden size} can highlight.
-
-The command can be passed one or more package specifications
-such as @code{gcc@@4.8}
-or @code{guile:debug}, or a file name in the store.  Consider this
-example:
+The @command{guix size} command helps package developers profile the disk
+usage of packages.  It is easy to overlook the impact of an additional
+dependency added to a package, or the impact of using a single output for a
+package that could easily be split (@pxref{Pakete mit mehreren Ausgaben.}).  
Such are the typical issues that @command{guix size} can
+highlight.
+
+The command can be passed one or more package specifications such as
address@hidden@@4.8} or @code{guile:debug}, or a file name in the store.
+Consider this example:
 
 @example
 $ guix size coreutils
@@ -7613,40 +7713,39 @@ store item                               total    self
 total: 78.9 MiB
 @end example
 
address@hidden closure
address@hidden Abschluss
 The store items listed here constitute the @dfn{transitive closure} of
-Coreutils---i.e., Coreutils and all its dependencies, recursively---as
-would be returned by:
+Coreutils---i.e., Coreutils and all its dependencies, recursively---as would
+be returned by:
 
 @example
 $ guix gc -R /gnu/store/@dots{}-coreutils-8.23
 @end example
 
 Here the output shows three columns next to store items.  The first column,
-labeled ``total'', shows the size in mebibytes (MiB) of the closure of
-the store item---that is, its own size plus the size of all its
-dependencies.  The next column, labeled ``self'', shows the size of the
-item itself.  The last column shows the ratio of the size of the item
-itself to the space occupied by all the items listed here.
+labeled ``total'', shows the size in mebibytes (MiB) of the closure of the
+store item---that is, its own size plus the size of all its dependencies.
+The next column, labeled ``self'', shows the size of the item itself.  The
+last column shows the ratio of the size of the item itself to the space
+occupied by all the items listed here.
 
 In this example, we see that the closure of Coreutils weighs in at
 address@hidden, most of which is taken by libc and GCC's run-time support
-libraries.  (That libc and GCC's libraries represent a large fraction of
-the closure is not a problem @i{per se} because they are always available
-on the system anyway.)
+libraries.  (That libc and GCC's libraries represent a large fraction of the
+closure is not a problem @i{per se} because they are always available on the
+system anyway.)
 
 When the package(s) passed to @command{guix size} are available in the
 address@hidden precisely, @command{guix size} looks for the
address@hidden variant of the given package(s), as returned by
address@hidden build @var{package} --no-grafts}.  @xref{Security Updates},
-for information on grafts.}, @command{guix size} queries the daemon to 
determine its
-dependencies, and measures its size in the store, similar to @command{du
--ms --apparent-size} (@pxref{du invocation,,, coreutils, GNU
-Coreutils}).
address@hidden variant of the given package(s), as returned by @code{guix
+build @var{package} --no-grafts}.  @xref{Sicherheitsaktualisierungen}, for 
information
+on grafts.}, @command{guix size} queries the daemon to determine its
+dependencies, and measures its size in the store, similar to @command{du -ms
+--apparent-size} (@pxref{du invocation,,, coreutils, GNU Coreutils}).
 
 When the given packages are @emph{not} in the store, @command{guix size}
 reports information based on the available substitutes
-(@pxref{Substitutes}).  This makes it possible it to profile disk usage of
+(@pxref{Substitute}).  This makes it possible it to profile disk usage of
 store items that are not even on disk, only available remotely.
 
 You can also specify several package names:
@@ -7671,9 +7770,9 @@ The available options are:
 
 @table @option
 
address@hidden address@hidden
-Use substitute information from @var{urls}.
address@hidden, the same option for @code{guix build}}.
address@hidden address@hidden
+Use substitute information from @var{urls}.  @xref{client-substitute-urls,
+the same option for @code{guix build}}.
 
 @item address@hidden
 Sort lines according to @var{key}, one of the following options:
@@ -7681,7 +7780,7 @@ Sort lines according to @var{key}, one of the following 
options:
 @table @code
 @item self
 the size of each item (the default);
address@hidden closure
address@hidden Abschluss
 the total size of the item's closure.
 @end table
 
@@ -7690,38 +7789,37 @@ Write a graphical map of disk usage in PNG format to 
@var{file}.
 
 For the example above, the map looks like this:
 
address@hidden/coreutils-size-map,5in,, map of Coreutils disk usage
-produced by @command{guix size}}
address@hidden/coreutils-size-map,5in,, map of Coreutils disk usage produced
+by @command{guix size}}
 
 This option requires that
 @uref{http://wingolog.org/software/guile-charting/, Guile-Charting} be
-installed and visible in Guile's module search path.  When that is not
-the case, @command{guix size} fails as it tries to load it.
+installed and visible in Guile's module search path.  When that is not the
+case, @command{guix size} fails as it tries to load it.
 
address@hidden address@hidden
address@hidden address@hidden
 @itemx -s @var{system}
 Consider packages for @var{system}---e.g., @code{x86_64-linux}.
 
 @end table
 
address@hidden Invoking guix graph
address@hidden Aufruf von guix graph
 @section Invoking @command{guix graph}
 
 @cindex DAG
 @cindex @command{guix graph}
address@hidden package dependencies
-Packages and their dependencies form a @dfn{graph}, specifically a
-directed acyclic graph (DAG).  It can quickly become difficult to have a
-mental model of the package DAG, so the @command{guix graph} command
-provides a visual representation of the DAG.  By default,
address@hidden graph} emits a DAG representation in the input format of
address@hidden://www.graphviz.org/, Graphviz}, so its output can be passed
-directly to the @command{dot} command of Graphviz.  It can also emit an
-HTML page with embedded JavaScript code to display a ``chord diagram''
-in a Web browser, using the @uref{https://d3js.org/, d3.js} library, or
-emit Cypher queries to construct a graph in a graph database supporting
-the @uref{http://www.opencypher.org/, openCypher} query language.
-The general syntax is:
address@hidden Paketabhängigkeiten
+Packages and their dependencies form a @dfn{graph}, specifically a directed
+acyclic graph (DAG).  It can quickly become difficult to have a mental model
+of the package DAG, so the @command{guix graph} command provides a visual
+representation of the DAG.  By default, @command{guix graph} emits a DAG
+representation in the input format of @uref{http://www.graphviz.org/,
+Graphviz}, so its output can be passed directly to the @command{dot} command
+of Graphviz.  It can also emit an HTML page with embedded JavaScript code to
+display a ``chord diagram'' in a Web browser, using the
address@hidden://d3js.org/, d3.js} library, or emit Cypher queries to construct
+a graph in a graph database supporting the @uref{http://www.opencypher.org/,
+openCypher} query language.  The general syntax is:
 
 @example
 guix graph @var{options} @address@hidden
@@ -7741,11 +7839,11 @@ The output looks like this:
 
 Nice little graph, no?
 
-But there is more than one graph!  The one above is concise: it is the
-graph of package objects, omitting implicit inputs such as GCC, libc,
-grep, etc.  It is often useful to have such a concise graph, but
-sometimes one may want to see more details.  @command{guix graph} supports
-several types of graphs, allowing you to choose the level of detail:
+But there is more than one graph! The one above is concise: it is the graph
+of package objects, omitting implicit inputs such as GCC, libc, grep, etc.
+It is often useful to have such a concise graph, but sometimes one may want
+to see more details.  @command{guix graph} supports several types of graphs,
+allowing you to choose the level of detail:
 
 @table @code
 @item package
@@ -7762,9 +7860,9 @@ guix graph --type=reverse-package ocaml
 
 ... yields the graph of packages that depend on OCaml.
 
-Note that for core packages this can yield huge graphs.  If all you want
-is to know the number of packages that depend on a given package, use
address@hidden refresh --list-dependent} (@pxref{Invoking guix refresh,
+Note that for core packages this can yield huge graphs.  If all you want is
+to know the number of packages that depend on a given package, use
address@hidden refresh --list-dependent} (@pxref{Aufruf von guix refresh,
 @option{--list-dependent}}).
 
 @item bag-emerged
@@ -7778,14 +7876,15 @@ guix graph --type=bag-emerged coreutils | dot -Tpdf > 
dag.pdf
 
 ... yields this bigger graph:
 
address@hidden/coreutils-bag-graph,,5in,Detailed dependency graph of the GNU 
Coreutils}
address@hidden/coreutils-bag-graph,,5in,Detailed dependency graph of the GNU
+Coreutils}
 
 At the bottom of the graph, we see all the implicit inputs of
address@hidden (@pxref{Build Systems, @code{gnu-build-system}}).
address@hidden (@pxref{Erstellungssysteme, @code{gnu-build-system}}).
 
 Now, note that the dependencies of these implicit inputs---that is, the
address@hidden dependencies} (@pxref{Bootstrapping})---are not shown
-here, for conciseness.
address@hidden dependencies} (@pxref{Bootstrapping})---are not shown here,
+for conciseness.
 
 @item bag
 Similar to @code{bag-emerged}, but this time including all the bootstrap
@@ -7794,23 +7893,23 @@ dependencies.
 @item bag-with-origins
 Similar to @code{bag}, but also showing origins and their dependencies.
 
address@hidden derivation
-This is the most detailed representation: It shows the DAG of
-derivations (@pxref{Derivations}) and plain store items.  Compared to
-the above representation, many additional nodes are visible, including
-build scripts, patches, Guile modules, etc.
address@hidden Ableitung
+This is the most detailed representation: It shows the DAG of derivations
+(@pxref{Ableitungen}) and plain store items.  Compared to the above
+representation, many additional nodes are visible, including build scripts,
+patches, Guile modules, etc.
 
-For this type of graph, it is also possible to pass a @file{.drv} file
-name instead of a package name, as in:
+For this type of graph, it is also possible to pass a @file{.drv} file name
+instead of a package name, as in:
 
 @example
 guix graph -t derivation `guix system build -d my-config.scm`
 @end example
 
 @item module
-This is the graph of @dfn{package modules} (@pxref{Package Modules}).
-For example, the following command shows the graph for the package
-module that defines the @code{guile} package:
+This is the graph of @dfn{package modules} (@pxref{Paketmodule}).  For
+example, the following command shows the graph for the package module that
+defines the @code{guile} package:
 
 @example
 guix graph -t module guile | dot -Tpdf > module-graph.pdf
@@ -7822,8 +7921,8 @@ following graph type represents the @emph{run-time 
dependencies}:
 
 @table @code
 @item references
-This is the graph of @dfn{references} of a package output, as returned
-by @command{guix gc --references} (@pxref{Invoking guix gc}).
+This is the graph of @dfn{references} of a package output, as returned by
address@hidden gc --references} (@pxref{Aufruf von guix gc}).
 
 If the given package output is not available in the store, @command{guix
 graph} attempts to obtain dependency information from substitutes.
@@ -7838,13 +7937,12 @@ guix graph -t references `readlink -f ~/.guix-profile`
 
 @item referrers
 This is the graph of the @dfn{referrers} of a store item, as returned by
address@hidden gc --referrers} (@pxref{Invoking guix gc}).
address@hidden gc --referrers} (@pxref{Aufruf von guix gc}).
 
-This relies exclusively on local information from your store.  For
-instance, let us suppose that the current Inkscape is available in 10
-profiles on your machine; @command{guix graph -t referrers inkscape}
-will show a graph rooted at Inkscape and with those 10 profiles linked
-to it.
+This relies exclusively on local information from your store.  For instance,
+let us suppose that the current Inkscape is available in 10 profiles on your
+machine; @command{guix graph -t referrers inkscape} will show a graph rooted
+at Inkscape and with those 10 profiles linked to it.
 
 It can help determine what is preventing a store item from being garbage
 collected.
@@ -7856,8 +7954,8 @@ The available options are the following:
 @table @option
 @item address@hidden
 @itemx -t @var{type}
-Produce a graph output of @var{type}, where @var{type} must be one of
-the values listed above.
+Produce a graph output of @var{type}, where @var{type} must be one of the
+values listed above.
 
 @item --list-types
 List the supported graph types.
@@ -7881,27 +7979,27 @@ This is useful to precisely refer to a package, as in 
this example:
 guix graph -e '(@@@@ (gnu packages commencement) gnu-make-final)'
 @end example
 
address@hidden address@hidden
address@hidden address@hidden
 @itemx -s @var{system}
 Display the graph for @var{system}---e.g., @code{i686-linux}.
 
 The package dependency graph is largely architecture-independent, but there
-are some architecture-dependent bits that this option allows you to visualize.
+are some architecture-dependent bits that this option allows you to
+visualize.
 @end table
 
 
address@hidden Invoking guix environment
address@hidden Aufruf von guix environment
 @section Invoking @command{guix environment}
 
 @cindex reproducible build environments
 @cindex development environments
 @cindex @command{guix environment}
 @cindex environment, package build environment
-The purpose of @command{guix environment} is to assist hackers in
-creating reproducible development environments without polluting their
-package profile.  The @command{guix environment} tool takes one or more
-packages, builds all of their inputs, and creates a shell
-environment to use them.
+The purpose of @command{guix environment} is to assist hackers in creating
+reproducible development environments without polluting their package
+profile.  The @command{guix environment} tool takes one or more packages,
+builds all of their inputs, and creates a shell environment to use them.
 
 The general syntax is:
 
@@ -7918,26 +8016,25 @@ guix environment guile
 
 If the needed dependencies are not built yet, @command{guix environment}
 automatically builds them.  The environment of the new shell is an augmented
-version of the environment that @command{guix environment} was run in.
-It contains the necessary search paths for building the given package
-added to the existing environment variables.  To create a ``pure''
-environment, in which the original environment variables have been unset,
-use the @code{--pure} address@hidden sometimes wrongfully augment
-environment variables such as @code{PATH} in their @file{~/.bashrc}
-file.  As a consequence, when @code{guix environment} launches it, Bash
-may read @file{~/.bashrc}, thereby introducing ``impurities'' in these
-environment variables.  It is an error to define such environment
-variables in @file{.bashrc}; instead, they should be defined in
address@hidden, which is sourced only by log-in shells.
address@hidden Startup Files,,, bash, The GNU Bash Reference Manual}, for
-details on Bash start-up files.}.
+version of the environment that @command{guix environment} was run in.  It
+contains the necessary search paths for building the given package added to
+the existing environment variables.  To create a ``pure'' environment, in
+which the original environment variables have been unset, use the
address@hidden address@hidden sometimes wrongfully augment environment
+variables such as @code{PATH} in their @file{~/.bashrc} file.  As a
+consequence, when @code{guix environment} launches it, Bash may read
address@hidden/.bashrc}, thereby introducing ``impurities'' in these environment
+variables.  It is an error to define such environment variables in
address@hidden; instead, they should be defined in @file{.bash_profile},
+which is sourced only by log-in shells.  @xref{Bash Startup Files,,, bash,
+The GNU Bash Reference Manual}, for details on Bash start-up files.}.
 
 @vindex GUIX_ENVIRONMENT
address@hidden environment} defines the @code{GUIX_ENVIRONMENT}
-variable in the shell it spawns; its value is the file name of the
-profile of this environment.  This allows users to, say, define a
-specific prompt for development environments in their @file{.bashrc}
-(@pxref{Bash Startup Files,,, bash, The GNU Bash Reference Manual}):
address@hidden environment} defines the @code{GUIX_ENVIRONMENT} variable in
+the shell it spawns; its value is the file name of the profile of this
+environment.  This allows users to, say, define a specific prompt for
+development environments in their @file{.bashrc} (@pxref{Bash Startup
+Files,,, bash, The GNU Bash Reference Manual}):
 
 @example
 if [ -n "$GUIX_ENVIRONMENT" ]
@@ -7955,57 +8052,56 @@ $ ls "$GUIX_ENVIRONMENT/bin"
 
 Additionally, more than one package may be specified, in which case the
 union of the inputs for the given packages are used.  For example, the
-command below spawns a shell where all of the dependencies of both Guile
-and Emacs are available:
+command below spawns a shell where all of the dependencies of both Guile and
+Emacs are available:
 
 @example
 guix environment guile emacs
 @end example
 
-Sometimes an interactive shell session is not desired.  An arbitrary
-command may be invoked by placing the @code{--} token to separate the
-command from the rest of the arguments:
+Sometimes an interactive shell session is not desired.  An arbitrary command
+may be invoked by placing the @code{--} token to separate the command from
+the rest of the arguments:
 
 @example
 guix environment guile -- make -j4
 @end example
 
-In other situations, it is more convenient to specify the list of
-packages needed in the environment.  For example, the following command
-runs @command{python} from an environment containing address@hidden and
-NumPy:
+In other situations, it is more convenient to specify the list of packages
+needed in the environment.  For example, the following command runs
address@hidden from an environment containing address@hidden and NumPy:
 
 @example
 guix environment --ad-hoc python2-numpy python-2.7 -- python
 @end example
 
 Furthermore, one might want the dependencies of a package and also some
-additional packages that are not build-time or runtime dependencies, but
-are useful when developing nonetheless.  Because of this, the
address@hidden flag is positional.  Packages appearing before
address@hidden are interpreted as packages whose dependencies will be
-added to the environment.  Packages appearing after are interpreted as
-packages that will be added to the environment directly.  For example,
-the following command creates a Guix development environment that
-additionally includes Git and strace:
+additional packages that are not build-time or runtime dependencies, but are
+useful when developing nonetheless.  Because of this, the @code{--ad-hoc}
+flag is positional.  Packages appearing before @code{--ad-hoc} are
+interpreted as packages whose dependencies will be added to the
+environment.  Packages appearing after are interpreted as packages that will
+be added to the environment directly.  For example, the following command
+creates a Guix development environment that additionally includes Git and
+strace:
 
 @example
 guix environment guix --ad-hoc git strace
 @end example
 
-Sometimes it is desirable to isolate the environment as much as
-possible, for maximal purity and reproducibility.  In particular, when
-using Guix on a host distro that is not GuixSD, it is desirable to
-prevent access to @file{/usr/bin} and other system-wide resources from
-the development environment.  For example, the following command spawns
-a Guile REPL in a ``container'' where only the store and the current
-working directory are mounted:
+Sometimes it is desirable to isolate the environment as much as possible,
+for maximal purity and reproducibility.  In particular, when using Guix on a
+host distro that is not GuixSD, it is desirable to prevent access to
address@hidden/usr/bin} and other system-wide resources from the development
+environment.  For example, the following command spawns a Guile REPL in a
+``container'' where only the store and the current working directory are
+mounted:
 
 @example
 guix environment --ad-hoc --container guile -- guile
 @end example
 
address@hidden Note
address@hidden Anmerkung
 The @code{--container} option requires Linux-libre 3.19 or newer.
 @end quotation
 
@@ -8016,22 +8112,22 @@ The available options are summarized below.
 @itemx -r @var{file}
 @cindex persistent environment
 @cindex garbage collector root, for environments
-Make @var{file} a symlink to the profile for this environment, and
-register it as a garbage collector root.
+Make @var{file} a symlink to the profile for this environment, and register
+it as a garbage collector root.
 
 This is useful if you want to protect your environment from garbage
 collection, to make it ``persistent''.
 
 When this option is omitted, the environment is protected from garbage
-collection only for the duration of the @command{guix environment}
-session.  This means that next time you recreate the same environment,
-you could have to rebuild or re-download packages.  @xref{Invoking guix
-gc}, for more on GC roots.
+collection only for the duration of the @command{guix environment} session.
+This means that next time you recreate the same environment, you could have
+to rebuild or re-download packages.  @xref{Aufruf von guix gc}, for more on GC
+roots.
 
 @item address@hidden
 @itemx -e @var{expr}
-Create an environment for the package or list of packages that
address@hidden evaluates to.
+Create an environment for the package or list of packages that @var{expr}
+evaluates to.
 
 For example, running:
 
@@ -8039,8 +8135,8 @@ For example, running:
 guix environment -e '(@@ (gnu packages maths) petsc-openmpi)'
 @end example
 
-starts a shell with the environment for this specific variant of the
-PETSc package.
+starts a shell with the environment for this specific variant of the PETSc
+package.
 
 Running:
 
@@ -8050,8 +8146,8 @@ guix environment --ad-hoc -e '(@@ (gnu) %base-packages)'
 
 starts a shell with all the GuixSD base packages available.
 
-The above commands only use the default output of the given packages.
-To select other outputs, two element tuples can be specified:
+The above commands only use the default output of the given packages.  To
+select other outputs, two element tuples can be specified:
 
 @example
 guix environment --ad-hoc -e '(list (@@ (gnu packages bash) bash) "include")'
@@ -8062,27 +8158,27 @@ guix environment --ad-hoc -e '(list (@@ (gnu packages 
bash) bash) "include")'
 Create an environment for the package or list of packages that the code
 within @var{file} evaluates to.
 
-As an example, @var{file} might contain a definition like this
-(@pxref{Defining Packages}):
+Zum Beispiel könnte die @var{Datei} eine Definition wie diese enthalten
+(@pxref{Pakete definieren}):
 
 @example
 @verbatiminclude environment-gdb.scm
 @end example
 
address@hidden address@hidden
address@hidden -m @var{file}
address@hidden address@hidden
address@hidden -m @var{Datei}
 Create an environment for the packages contained in the manifest object
 returned by the Scheme code in @var{file}.
 
 This is similar to the same-named option in @command{guix package}
-(@pxref{profile-manifest, @option{--manifest}}) and uses the same
-manifest files.
+(@pxref{profile-manifest, @option{--manifest}}) and uses the same manifest
+files.
 
 @item --ad-hoc
-Include all specified packages in the resulting environment, as if an
address@hidden hoc} package were defined with them as inputs.  This option is
-useful for quickly creating an environment without having to write a
-package expression to contain the desired inputs.
+Include all specified packages in the resulting environment, as if an @i{ad
+hoc} package were defined with them as inputs.  This option is useful for
+quickly creating an environment without having to write a package expression
+to contain the desired inputs.
 
 For instance, the command:
 
@@ -8094,26 +8190,25 @@ runs @command{guile} in an environment where Guile and 
Guile-SDL are
 available.
 
 Note that this example implicitly asks for the default output of
address@hidden and @code{guile-sdl}, but it is possible to ask for a
-specific output---e.g., @code{glib:bin} asks for the @code{bin} output
-of @code{glib} (@pxref{Packages with Multiple Outputs}).
address@hidden and @code{guile-sdl}, but it is possible to ask for a specific
+output---e.g., @code{glib:bin} asks for the @code{bin} output of @code{glib}
+(@pxref{Pakete mit mehreren Ausgaben.}).
 
 This option may be composed with the default behavior of @command{guix
-environment}.  Packages appearing before @code{--ad-hoc} are interpreted
-as packages whose dependencies will be added to the environment, the
-default behavior.  Packages appearing after are interpreted as packages
-that will be added to the environment directly.
+environment}.  Packages appearing before @code{--ad-hoc} are interpreted as
+packages whose dependencies will be added to the environment, the default
+behavior.  Packages appearing after are interpreted as packages that will be
+added to the environment directly.
 
 @item --pure
 Unset existing environment variables when building the new environment.
-This has the effect of creating an environment in which search paths
-only contain package inputs.
+This has the effect of creating an environment in which search paths only
+contain package inputs.
 
 @item --search-paths
-Display the environment variable definitions that make up the
-environment.
+Display the environment variable definitions that make up the environment.
 
address@hidden address@hidden
address@hidden address@hidden
 @itemx -s @var{system}
 Attempt to build for @var{system}---e.g., @code{i686-linux}.
 
@@ -8122,11 +8217,11 @@ Attempt to build for @var{system}---e.g., 
@code{i686-linux}.
 @cindex container
 Run @var{command} within an isolated container.  The current working
 directory outside the container is mapped inside the container.
-Additionally, unless overridden with @code{--user}, a dummy home
-directory is created that matches the current user's home directory, and
address@hidden/etc/passwd} is configured accordingly.  The spawned process runs
-as the current user outside the container, but has root privileges in
-the context of the container.
+Additionally, unless overridden with @code{--user}, a dummy home directory
+is created that matches the current user's home directory, and
address@hidden/etc/passwd} is configured accordingly.  The spawned process runs 
as
+the current user outside the container, but has root privileges in the
+context of the container.
 
 @item --network
 @itemx -N
@@ -8136,32 +8231,30 @@ device.
 
 @item --link-profile
 @itemx -P
-For containers, link the environment profile to
address@hidden/.guix-profile} within the container.  This is equivalent to
-running the command @command{ln -s $GUIX_ENVIRONMENT ~/.guix-profile}
-within the container.  Linking will fail and abort the environment if
-the directory already exists, which will certainly be the case if
address@hidden environment} was invoked in the user's home directory.
-
-Certain packages are configured to look in
address@hidden/.guix-profile} for configuration files and data;@footnote{For
-example, the @code{fontconfig} package inspects
address@hidden/.guix-profile/share/fonts} for additional fonts.}
address@hidden allows these programs to behave as expected within
-the environment.
+For containers, link the environment profile to @file{~/.guix-profile}
+within the container.  This is equivalent to running the command @command{ln
+-s $GUIX_ENVIRONMENT ~/.guix-profile} within the container.  Linking will
+fail and abort the environment if the directory already exists, which will
+certainly be the case if @command{guix environment} was invoked in the
+user's home directory.
+
+Certain packages are configured to look in @code{~/.guix-profile} for
+configuration files and data;@footnote{For example, the @code{fontconfig}
+package inspects @file{~/.guix-profile/share/fonts} for additional fonts.}
address@hidden allows these programs to behave as expected within the
+environment.
 
 @item address@hidden
 @itemx -u @var{user}
-For containers, use the username @var{user} in place of the current
-user.  The generated @file{/etc/passwd} entry within the container will
-contain the name @var{user}; the home directory will be
address@hidden/home/USER}; and no user GECOS data will be copied.  @var{user}
-need not exist on the system.
+For containers, use the username @var{user} in place of the current user.
+The generated @file{/etc/passwd} entry within the container will contain the
+name @var{user}; the home directory will be @file{/home/USER}; and no user
+GECOS data will be copied.  @var{user} need not exist on the system.
 
 Additionally, any shared or exposed path (see @code{--share} and
address@hidden respectively) whose target is within the current user's
-home directory will be remapped relative to @file{/home/USER}; this
-includes the automatic mapping of the current working directory.
address@hidden respectively) whose target is within the current user's home
+directory will be remapped relative to @file{/home/USER}; this includes the
+automatic mapping of the current working directory.
 
 @example
 # will expose paths as /home/foo/wd, /home/foo/test, and /home/foo/target
@@ -8171,29 +8264,28 @@ guix environment --container --user=foo \
      --expose=/tmp/target=$HOME/target
 @end example
 
-While this will limit the leaking of user identity through home paths
-and each of the user fields, this is only one useful component of a
-broader privacy/anonymity solution---not one in and of itself.
+While this will limit the leaking of user identity through home paths and
+each of the user fields, this is only one useful component of a broader
+privacy/anonymity solution---not one in and of itself.
 
 @item address@hidden@var{target}]
-For containers, expose the file system @var{source} from the host system
-as the read-only file system @var{target} within the container.  If
+For containers, expose the file system @var{source} from the host system as
+the read-only file system @var{target} within the container.  If
 @var{target} is not specified, @var{source} is used as the target mount
 point in the container.
 
 The example below spawns a Guile REPL in a container in which the user's
-home directory is accessible read-only via the @file{/exchange}
-directory:
+home directory is accessible read-only via the @file{/exchange} directory:
 
 @example
 guix environment --container --expose=$HOME=/exchange --ad-hoc guile -- guile
 @end example
 
 @item address@hidden@var{target}]
-For containers, share the file system @var{source} from the host system
-as the writable file system @var{target} within the container.  If
address@hidden is not specified, @var{source} is used as the target mount
-point in the container.
+For containers, share the file system @var{source} from the host system as
+the writable file system @var{target} within the container.  If @var{target}
+is not specified, @var{source} is used as the target mount point in the
+container.
 
 The example below spawns a Guile REPL in a container in which the user's
 home directory is accessible for both reading and writing via the
@@ -8204,34 +8296,32 @@ guix environment --container --share=$HOME=/exchange 
--ad-hoc guile -- guile
 @end example
 @end table
 
address@hidden environment}
-also supports all of the common build options that @command{guix
-build} supports (@pxref{Common Build Options}).
address@hidden environment} also supports all of the common build options
+that @command{guix build} supports (@pxref{Gemeinsame Erstellungsoptionen}).
 
 
address@hidden Invoking guix publish
address@hidden Aufruf von guix publish
 @section Invoking @command{guix publish}
 
 @cindex @command{guix publish}
 The purpose of @command{guix publish} is to enable users to easily share
 their store with others, who can then use it as a substitute server
-(@pxref{Substitutes}).
+(@pxref{Substitute}).
 
 When @command{guix publish} runs, it spawns an HTTP server which allows
-anyone with network access to obtain substitutes from it.  This means
-that any machine running Guix can also act as if it were a build farm,
-since the HTTP interface is compatible with Hydra, the software behind
-the @code{hydra.gnu.org} build farm.
+anyone with network access to obtain substitutes from it.  This means that
+any machine running Guix can also act as if it were a build farm, since the
+HTTP interface is compatible with Hydra, the software behind the
address@hidden build farm.
 
-For security, each substitute is signed, allowing recipients to check
-their authenticity and integrity (@pxref{Substitutes}).  Because
address@hidden publish} uses the signing key of the system, which is only
-readable by the system administrator, it must be started as root; the
address@hidden option makes it drop root privileges early on.
+For security, each substitute is signed, allowing recipients to check their
+authenticity and integrity (@pxref{Substitute}).  Because @command{guix
+publish} uses the signing key of the system, which is only readable by the
+system administrator, it must be started as root; the @code{--user} option
+makes it drop root privileges early on.
 
 The signing key pair must be generated before @command{guix publish} is
-launched, using @command{guix archive --generate-key} (@pxref{Invoking
-guix archive}).
+launched, using @command{guix archive --generate-key} (@pxref{Aufruf von guix 
archive}).
 
 The general syntax is:
 
@@ -8239,41 +8329,39 @@ The general syntax is:
 guix publish @address@hidden
 @end example
 
-Running @command{guix publish} without any additional arguments will
-spawn an HTTP server on port 8080:
+Running @command{guix publish} without any additional arguments will spawn
+an HTTP server on port 8080:
 
 @example
 guix publish
 @end example
 
-Once a publishing server has been authorized (@pxref{Invoking guix
-archive}), the daemon may download substitutes from it:
+Once a publishing server has been authorized (@pxref{Aufruf von guix 
archive}), the daemon may download substitutes from it:
 
 @example
 guix-daemon --substitute-urls=http://example.org:8080
 @end example
 
 By default, @command{guix publish} compresses archives on the fly as it
-serves them.  This ``on-the-fly'' mode is convenient in that it requires
-no setup and is immediately available.  However, when serving lots of
-clients, we recommend using the @option{--cache} option, which enables
-caching of the archives before they are sent to clients---see below for
-details.  The @command{guix weather} command provides a handy way to
-check what a server provides (@pxref{Invoking guix weather}).
+serves them.  This ``on-the-fly'' mode is convenient in that it requires no
+setup and is immediately available.  However, when serving lots of clients,
+we recommend using the @option{--cache} option, which enables caching of the
+archives before they are sent to clients---see below for details.  The
address@hidden weather} command provides a handy way to check what a server
+provides (@pxref{Aufruf von guix weather}).
 
-As a bonus, @command{guix publish} also serves as a content-addressed
-mirror for source files referenced in @code{origin} records
-(@pxref{origin Reference}).  For instance, assuming @command{guix
-publish} is running on @code{example.org}, the following URL returns the
-raw @file{hello-2.10.tar.gz} file with the given SHA256 hash
-(represented in @code{nix-base32} format, @pxref{Invoking guix hash}):
+As a bonus, @command{guix publish} also serves as a content-addressed mirror
+for source files referenced in @code{origin} records 
(@pxref{„origin“-Referenz}).  For instance, assuming @command{guix publish} is 
running on
address@hidden, the following URL returns the raw
address@hidden file with the given SHA256 hash (represented in
address@hidden format, @pxref{Aufruf von guix hash}):
 
 @example
 http://example.org/file/hello-2.10.tar.gz/sha256/address@hidden
 @end example
 
-Obviously, these URLs only work for files that are in the store; in
-other cases, they return 404 (``Not Found'').
+Obviously, these URLs only work for files that are in the store; in other
+cases, they return 404 (``Not Found'').
 
 @cindex build logs, publication
 Build logs are available from @code{/log} URLs like:
@@ -8283,13 +8371,13 @@ http://example.org/log/address@hidden
 @end example
 
 @noindent
-When @command{guix-daemon} is configured to save compressed build logs,
-as is the case by default (@pxref{Invoking guix-daemon}), @code{/log}
-URLs return the compressed log as-is, with an appropriate
address@hidden and/or @code{Content-Encoding} header.  We recommend
-running @command{guix-daemon} with @code{--log-compression=gzip} since
-Web browsers can automatically decompress it, which is not the case with
-bzip2 compression.
+When @command{guix-daemon} is configured to save compressed build logs, as
+is the case by default (@pxref{Aufruf des guix-daemon}), @code{/log} URLs
+return the compressed log as-is, with an appropriate @code{Content-Type}
+and/or @code{Content-Encoding} header.  We recommend running
address@hidden with @code{--log-compression=gzip} since Web browsers
+can automatically decompress it, which is not the case with bzip2
+compression.
 
 The following options are available:
 
@@ -8299,13 +8387,13 @@ The following options are available:
 Listen for HTTP requests on @var{port}.
 
 @item address@hidden
-Listen on the network interface for @var{host}.  The default is to
-accept connections from any interface.
+Listen on the network interface for @var{host}.  The default is to accept
+connections from any interface.
 
 @item address@hidden
 @itemx -u @var{user}
-Change privileges to @var{user} as soon as possible---i.e., once the
-server socket is open and the signing key has been read.
+Change privileges to @var{user} as soon as possible---i.e., once the server
+socket is open and the signing key has been read.
 
 @item address@hidden
 @itemx -C address@hidden
@@ -8314,42 +8402,40 @@ disable compression.  The range 1 to 9 corresponds to 
different gzip
 compression levels: 1 is the fastest, and 9 is the best (CPU-intensive).
 The default is 3.
 
-Unless @option{--cache} is used, compression occurs on the fly and
-the compressed streams are not
-cached.  Thus, to reduce load on the machine that runs @command{guix
-publish}, it may be a good idea to choose a low compression level, to
-run @command{guix publish} behind a caching proxy, or to use
address@hidden  Using @option{--cache} has the advantage that it
-allows @command{guix publish} to add @code{Content-Length} HTTP header
-to its responses.
+Unless @option{--cache} is used, compression occurs on the fly and the
+compressed streams are not cached.  Thus, to reduce load on the machine that
+runs @command{guix publish}, it may be a good idea to choose a low
+compression level, to run @command{guix publish} behind a caching proxy, or
+to use @option{--cache}.  Using @option{--cache} has the advantage that it
+allows @command{guix publish} to add @code{Content-Length} HTTP header to
+its responses.
 
 @item address@hidden
 @itemx -c @var{directory}
-Cache archives and meta-data (@code{.narinfo} URLs) to @var{directory}
-and only serve archives that are in cache.
+Cache archives and meta-data (@code{.narinfo} URLs) to @var{directory} and
+only serve archives that are in cache.
 
-When this option is omitted, archives and meta-data are created
-on-the-fly.  This can reduce the available bandwidth, especially when
-compression is enabled, since this may become CPU-bound.  Another
-drawback of the default mode is that the length of archives is not known
-in advance, so @command{guix publish} does not add a
address@hidden HTTP header to its responses, which in turn
-prevents clients from knowing the amount of data being downloaded.
+When this option is omitted, archives and meta-data are created on-the-fly.
+This can reduce the available bandwidth, especially when compression is
+enabled, since this may become CPU-bound.  Another drawback of the default
+mode is that the length of archives is not known in advance, so
address@hidden publish} does not add a @code{Content-Length} HTTP header to
+its responses, which in turn prevents clients from knowing the amount of
+data being downloaded.
 
 Conversely, when @option{--cache} is used, the first request for a store
-item (@i{via} a @code{.narinfo} URL) returns 404 and triggers a
-background process to @dfn{bake} the archive---computing its
address@hidden and compressing the archive, if needed.  Once the
-archive is cached in @var{directory}, subsequent requests succeed and
-are served directly from the cache, which guarantees that clients get
-the best possible bandwidth.
+item (@i{via} a @code{.narinfo} URL) returns 404 and triggers a background
+process to @dfn{bake} the archive---computing its @code{.narinfo} and
+compressing the archive, if needed.  Once the archive is cached in
address@hidden, subsequent requests succeed and are served directly from
+the cache, which guarantees that clients get the best possible bandwidth.
 
 The ``baking'' process is performed by worker threads.  By default, one
 thread per CPU core is created, but this can be customized.  See
 @option{--workers} below.
 
-When @option{--ttl} is used, cached entries are automatically deleted
-when they have expired.
+When @option{--ttl} is used, cached entries are automatically deleted when
+they have expired.
 
 @item address@hidden
 When @option{--cache} is used, request the allocation of @var{N} worker
@@ -8361,45 +8447,44 @@ Produce @code{Cache-Control} HTTP headers that 
advertise a time-to-live
 days, @code{1m} means 1 month, and so on.
 
 This allows the user's Guix to keep substitute information in cache for
address@hidden  However, note that @code{guix publish} does not itself
-guarantee that the store items it provides will indeed remain available
-for as long as @var{ttl}.
address@hidden  However, note that @code{guix publish} does not itself guarantee
+that the store items it provides will indeed remain available for as long as
address@hidden
 
-Additionally, when @option{--cache} is used, cached entries that have
-not been accessed for @var{ttl} and that no longer have a corresponding
-item in the store, may be deleted.
+Additionally, when @option{--cache} is used, cached entries that have not
+been accessed for @var{ttl} and that no longer have a corresponding item in
+the store, may be deleted.
 
 @item address@hidden
-Use @var{path} as the prefix for the URLs of ``nar'' files
-(@pxref{Invoking guix archive, normalized archives}).
+Use @var{path} as the prefix for the URLs of ``nar'' files (@pxref{Aufruf von 
guix archive, normalized archives}).
 
 By default, nars are served at a URL such as
address@hidden/nar/gzip/@dots{}-coreutils-8.25}.  This option allows you to
-change the @code{/nar} part to @var{path}.
address@hidden/nar/gzip/@dots{}-coreutils-8.25}.  This option allows you to 
change
+the @code{/nar} part to @var{path}.
 
 @item address@hidden
 @itemx address@hidden
-Use the specific @var{file}s as the public/private key pair used to sign
-the store items being published.
-
-The files must correspond to the same key pair (the private key is used
-for signing and the public key is merely advertised in the signature
-metadata).  They must contain keys in the canonical s-expression format
-as produced by @command{guix archive --generate-key} (@pxref{Invoking
-guix archive}).  By default, @file{/etc/guix/signing-key.pub} and
+Use the specific @var{file}s as the public/private key pair used to sign the
+store items being published.
+
+The files must correspond to the same key pair (the private key is used for
+signing and the public key is merely advertised in the signature metadata).
+They must contain keys in the canonical s-expression format as produced by
address@hidden archive --generate-key} (@pxref{Aufruf von guix archive}).  By
+default, @file{/etc/guix/signing-key.pub} and
 @file{/etc/guix/signing-key.sec} are used.
 
 @item address@hidden
 @itemx -r address@hidden
-Spawn a Guile REPL server (@pxref{REPL Servers,,, guile, GNU Guile
-Reference Manual}) on @var{port} (37146 by default).  This is used
-primarily for debugging a running @command{guix publish} server.
+Spawn a Guile REPL server (@pxref{REPL Servers,,, guile, GNU Guile Reference
+Manual}) on @var{port} (37146 by default).  This is used primarily for
+debugging a running @command{guix publish} server.
 @end table
 
 Enabling @command{guix publish} on a GuixSD system is a one-liner: just
-instantiate a @code{guix-publish-service-type} service in the @code{services} 
field
-of the @code{operating-system} declaration (@pxref{guix-publish-service-type,
address@hidden).
+instantiate a @code{guix-publish-service-type} service in the
address@hidden field of the @code{operating-system} declaration
+(@pxref{guix-publish-service-type, @code{guix-publish-service-type}}).
 
 If you are instead running Guix on a ``foreign distro'', follow these
 instructions:”
@@ -8415,7 +8500,7 @@ If your host distro uses the systemd init system:
 @end example
 
 @item
-If your host distro uses the Upstart init system:
+Wenn Ihre Wirts-Distribution als »init«-System Upstart verwendet:
 
 @example
 # ln -s ~root/.guix-profile/lib/upstart/system/guix-publish.conf /etc/init/
@@ -8426,34 +8511,32 @@ If your host distro uses the Upstart init system:
 Otherwise, proceed similarly with your distro's init system.
 @end itemize
 
address@hidden Invoking guix challenge
address@hidden Aufruf von guix challenge
 @section Invoking @command{guix challenge}
 
address@hidden reproducible builds
address@hidden Reproduzierbare Erstellungen
 @cindex verifiable builds
 @cindex @command{guix challenge}
 @cindex challenge
-Do the binaries provided by this server really correspond to the source
-code it claims to build?  Is a package build process deterministic?
-These are the questions the @command{guix challenge} command attempts to
-answer.
+Do the binaries provided by this server really correspond to the source code
+it claims to build? Is a package build process deterministic? These are the
+questions the @command{guix challenge} command attempts to answer.
 
 The former is obviously an important question: Before using a substitute
-server (@pxref{Substitutes}), one had better @emph{verify} that it
-provides the right binaries, and thus @emph{challenge} it.  The latter
-is what enables the former: If package builds are deterministic, then
-independent builds of the package should yield the exact same result,
-bit for bit; if a server provides a binary different from the one
-obtained locally, it may be either corrupt or malicious.
-
-We know that the hash that shows up in @file{/gnu/store} file names is
-the hash of all the inputs of the process that built the file or
+server (@pxref{Substitute}), one had better @emph{verify} that it provides
+the right binaries, and thus @emph{challenge} it.  The latter is what
+enables the former: If package builds are deterministic, then independent
+builds of the package should yield the exact same result, bit for bit; if a
+server provides a binary different from the one obtained locally, it may be
+either corrupt or malicious.
+
+We know that the hash that shows up in @file{/gnu/store} file names is the
+hash of all the inputs of the process that built the file or
 directory---compilers, libraries, build scripts,
-etc. (@pxref{Introduction}).  Assuming deterministic build processes,
-one store file name should map to exactly one build output.
address@hidden challenge} checks whether there is, indeed, a single
-mapping by comparing the build outputs of several independent builds of
-any given store item.
+etc. (@pxref{Einführung}).  Assuming deterministic build processes, one
+store file name should map to exactly one build output.  @command{guix
+challenge} checks whether there is, indeed, a single mapping by comparing
+the build outputs of several independent builds of any given store item.
 
 The command output looks like this:
 
@@ -8483,26 +8566,25 @@ updating list of substitutes from 
'https://guix.example.org'... 100.0%
 @end smallexample
 
 @noindent
-In this example, @command{guix challenge} first scans the store to
-determine the set of locally-built derivations---as opposed to store
-items that were downloaded from a substitute server---and then queries
-all the substitute servers.  It then reports those store items for which
-the servers obtained a result different from the local build.
+In this example, @command{guix challenge} first scans the store to determine
+the set of locally-built derivations---as opposed to store items that were
+downloaded from a substitute server---and then queries all the substitute
+servers.  It then reports those store items for which the servers obtained a
+result different from the local build.
 
 @cindex non-determinism, in package builds
 As an example, @code{guix.example.org} always gets a different answer.
 Conversely, @code{hydra.gnu.org} agrees with local builds, except in the
 case of Git.  This might indicate that the build process of Git is
-non-deterministic, meaning that its output varies as a function of
-various things that Guix does not fully control, in spite of building
-packages in isolated environments (@pxref{Features}).  Most common
-sources of non-determinism include the addition of timestamps in build
-results, the inclusion of random numbers, and directory listings sorted
-by inode number.  See @uref{https://reproducible-builds.org/docs/}, for
-more information.
+non-deterministic, meaning that its output varies as a function of various
+things that Guix does not fully control, in spite of building packages in
+isolated environments (@pxref{Funktionalitäten}).  Most common sources of
+non-determinism include the addition of timestamps in build results, the
+inclusion of random numbers, and directory listings sorted by inode number.
+See @uref{https://reproducible-builds.org/docs/}, for more information.
 
 To find out what is wrong with this Git binary, we can do something along
-these lines (@pxref{Invoking guix archive}):
+these lines (@pxref{Aufruf von guix archive}):
 
 @example
 $ wget -q -O - https://hydra.gnu.org/nar/@dots{}-git-2.5.0 \
@@ -8510,33 +8592,31 @@ $ wget -q -O - 
https://hydra.gnu.org/nar/@dots{}-git-2.5.0 \
 $ diff -ur --no-dereference /gnu/store/@dots{}-git.2.5.0 /tmp/git
 @end example
 
-This command shows the difference between the files resulting from the
-local build, and the files resulting from the build on
address@hidden (@pxref{Overview, Comparing and Merging Files,,
-diffutils, Comparing and Merging Files}).  The @command{diff} command
-works great for text files.  When binary files differ, a better option
-is @uref{https://diffoscope.org/, Diffoscope}, a tool that helps
-visualize differences for all kinds of files.
+This command shows the difference between the files resulting from the local
+build, and the files resulting from the build on @code{hydra.gnu.org}
+(@pxref{Overview, Comparing and Merging Files,, diffutils, Comparing and
+Merging Files}).  The @command{diff} command works great for text files.
+When binary files differ, a better option is @uref{https://diffoscope.org/,
+Diffoscope}, a tool that helps visualize differences for all kinds of files.
 
 Once you have done that work, you can tell whether the differences are due
-to a non-deterministic build process or to a malicious server.  We try
-hard to remove sources of non-determinism in packages to make it easier
-to verify substitutes, but of course, this is a process that
-involves not just Guix, but a large part of the free software community.
-In the meantime, @command{guix challenge} is one tool to help address
-the problem.
+to a non-deterministic build process or to a malicious server.  We try hard
+to remove sources of non-determinism in packages to make it easier to verify
+substitutes, but of course, this is a process that involves not just Guix,
+but a large part of the free software community.  In the meantime,
address@hidden challenge} is one tool to help address the problem.
 
-If you are writing packages for Guix, you are encouraged to check
-whether @code{hydra.gnu.org} and other substitute servers obtain the
-same build result as you did with:
+If you are writing packages for Guix, you are encouraged to check whether
address@hidden and other substitute servers obtain the same build
+result as you did with:
 
 @example
 $ guix challenge @var{package}
 @end example
 
 @noindent
-where @var{package} is a package specification such as
address@hidden@@2.0} or @code{glibc:debug}.
+where @var{package} is a package specification such as @code{guile@@2.0} or
address@hidden:debug}.
 
 The general syntax is:
 
@@ -8544,38 +8624,37 @@ The general syntax is:
 guix challenge @var{options} address@hidden@dots{}]
 @end example
 
-When a difference is found between the hash of a locally-built item and
-that of a server-provided substitute, or among substitutes provided by
-different servers, the command displays it as in the example above and
-its exit code is 2 (other non-zero exit codes denote other kinds of
-errors.)
+When a difference is found between the hash of a locally-built item and that
+of a server-provided substitute, or among substitutes provided by different
+servers, the command displays it as in the example above and its exit code
+is 2 (other non-zero exit codes denote other kinds of errors.)
 
 The one option that matters is:
 
 @table @code
 
address@hidden address@hidden
-Consider @var{urls} the whitespace-separated list of substitute source
-URLs to compare to.
address@hidden address@hidden
+Consider @var{urls} the whitespace-separated list of substitute source URLs
+to compare to.
 
 @item --verbose
 @itemx -v
-Show details about matches (identical contents) in addition to
-information about mismatches.
+Show details about matches (identical contents) in addition to information
+about mismatches.
 
 @end table
 
address@hidden Invoking guix copy
address@hidden Aufruf von guix copy
 @section Invoking @command{guix copy}
 
 @cindex copy, of store items, over SSH
 @cindex SSH, copy of store items
 @cindex sharing store items across machines
 @cindex transferring store items across machines
-The @command{guix copy} command copies items from the store of one
-machine to that of another machine over a secure shell (SSH)
+The @command{guix copy} command copies items from the store of one machine
+to that of another machine over a secure shell (SSH)
 address@hidden command is available only when Guile-SSH was
-found.  @xref{Requirements}, for details.}.  For example, the following
+found.  @xref{Voraussetzungen}, for details.}.  For example, the following
 command copies the @code{coreutils} package, the user's profile, and all
 their dependencies over to @var{host}, logged in as @var{user}:
 
@@ -8584,8 +8663,8 @@ guix copy address@hidden@@@var{host} \
           coreutils `readlink -f ~/.guix-profile`
 @end example
 
-If some of the items to be copied are already present on @var{host},
-they are not actually sent.
+If some of the items to be copied are already present on @var{host}, they
+are not actually sent.
 
 The command below retrieves @code{libreoffice} and @code{gimp} from
 @var{host}, assuming they are available there:
@@ -8599,10 +8678,10 @@ compatible with OpenSSH: it honors 
@file{~/.ssh/known_hosts} and
 @file{~/.ssh/config}, and uses the SSH agent for authentication.
 
 The key used to sign items that are sent must be accepted by the remote
-machine.  Likewise, the key used by the remote machine to sign items you
-are retrieving must be in @file{/etc/guix/acl} so it is accepted by your
-own daemon.  @xref{Invoking guix archive}, for more information about
-store item authentication.
+machine.  Likewise, the key used by the remote machine to sign items you are
+retrieving must be in @file{/etc/guix/acl} so it is accepted by your own
+daemon.  @xref{Aufruf von guix archive}, for more information about store item
+authentication.
 
 The general syntax is:
 
@@ -8615,33 +8694,31 @@ You must always specify one of the following options:
 @table @code
 @item address@hidden
 @itemx address@hidden
-Specify the host to send to or receive from.  @var{spec} must be an SSH
-spec such as @code{example.org}, @code{charlie@@example.org}, or
+Specify the host to send to or receive from.  @var{spec} must be an SSH spec
+such as @code{example.org}, @code{charlie@@example.org}, or
 @code{charlie@@example.org:2222}.
 @end table
 
-The @var{items} can be either package names, such as @code{gimp}, or
-store items, such as @file{/gnu/store/@dots{}-idutils-4.6}.
+The @var{items} can be either package names, such as @code{gimp}, or store
+items, such as @file{/gnu/store/@dots{}-idutils-4.6}.
 
-When specifying the name of a package to send, it is first built if
-needed, unless @option{--dry-run} was specified.  Common build options
-are supported (@pxref{Common Build Options}).
+When specifying the name of a package to send, it is first built if needed,
+unless @option{--dry-run} was specified.  Common build options are supported
+(@pxref{Gemeinsame Erstellungsoptionen}).
 
 
address@hidden Invoking guix container
address@hidden Aufruf von guix container
 @section Invoking @command{guix container}
 @cindex container
 @cindex @command{guix container}
address@hidden Note
-As of version @value{VERSION}, this tool is experimental.  The interface
-is subject to radical change in the future.
address@hidden Anmerkung
+As of version @value{VERSION}, this tool is experimental.  The interface is
+subject to radical change in the future.
 @end quotation
 
-The purpose of @command{guix container} is to manipulate processes
-running within an isolated environment, commonly known as a
-``container'', typically created by the @command{guix environment}
-(@pxref{Invoking guix environment}) and @command{guix system container}
-(@pxref{Invoking guix system}) commands.
+The purpose of @command{guix container} is to manipulate processes running
+within an isolated environment, commonly known as a ``container'', typically
+created by the @command{guix environment} (@pxref{Aufruf von guix 
environment}) and @command{guix system container} (@pxref{Aufruf von guix 
system}) commands.
 
 The general syntax is:
 
@@ -8664,14 +8741,14 @@ The syntax is:
 guix container exec @var{pid} @var{program} @address@hidden
 @end example
 
address@hidden specifies the process ID of the running container.
address@hidden specifies an executable file name within the root file
-system of the container.  @var{arguments} are the additional options that
-will be passed to @var{program}.
address@hidden specifies the process ID of the running container.  @var{program}
+specifies an executable file name within the root file system of the
+container.  @var{arguments} are the additional options that will be passed
+to @var{program}.
 
-The following command launches an interactive login shell inside a
-GuixSD container, started by @command{guix system container}, and whose
-process ID is 9001:
+The following command launches an interactive login shell inside a GuixSD
+container, started by @command{guix system container}, and whose process ID
+is 9001:
 
 @example
 guix container exec 9001 /run/current-system/profile/bin/bash --login
@@ -8682,16 +8759,15 @@ must be PID 1 of the container or one of its child 
processes.
 
 @end table
 
address@hidden Invoking guix weather
address@hidden Aufruf von guix weather
 @section Invoking @command{guix weather}
 
-Occasionally you're grumpy because substitutes are lacking and you end
-up building packages by yourself (@pxref{Substitutes}).  The
address@hidden weather} command reports on substitute availability on the
-specified servers so you can have an idea of whether you'll be grumpy
-today.  It can sometimes be useful info as a user, but it is primarily
-useful to people running @command{guix publish} (@pxref{Invoking guix
-publish}).
+Occasionally you're grumpy because substitutes are lacking and you end up
+building packages by yourself (@pxref{Substitute}).  The @command{guix
+weather} command reports on substitute availability on the specified servers
+so you can have an idea of whether you'll be grumpy today.  It can sometimes
+be useful info as a user, but it is primarily useful to people running
address@hidden publish} (@pxref{Aufruf von guix publish}).
 
 @cindex statistics, for substitutes
 @cindex availability of substitutes
@@ -8724,51 +8800,51 @@ https://guix.example.org
 
 @cindex continuous integration, statistics
 As you can see, it reports the fraction of all the packages for which
-substitutes are available on the server---regardless of whether
-substitutes are enabled, and regardless of whether this server's signing
-key is authorized.  It also reports the size of the compressed archives
-(``nars'') provided by the server, the size the corresponding store
-items occupy in the store (assuming deduplication is turned off), and
-the server's throughput.  The second part gives continuous integration
-(CI) statistics, if the server supports it.
+substitutes are available on the server---regardless of whether substitutes
+are enabled, and regardless of whether this server's signing key is
+authorized.  It also reports the size of the compressed archives (``nars'')
+provided by the server, the size the corresponding store items occupy in the
+store (assuming deduplication is turned off), and the server's throughput.
+The second part gives continuous integration (CI) statistics, if the server
+supports it.
 
 To achieve that, @command{guix weather} queries over HTTP(S) meta-data
 (@dfn{narinfos}) for all the relevant store items.  Like @command{guix
-challenge}, it ignores signatures on those substitutes, which is
-innocuous since the command only gathers statistics and cannot install
-those substitutes.
+challenge}, it ignores signatures on those substitutes, which is innocuous
+since the command only gathers statistics and cannot install those
+substitutes.
 
 Among other things, it is possible to query specific system types and
 specific package sets.  The available options are listed below.
 
 @table @code
address@hidden address@hidden
address@hidden is the space-separated list of substitute server URLs to
-query.  When this option is omitted, the default set of substitute
-servers is queried.
address@hidden address@hidden
address@hidden is the space-separated list of substitute server URLs to query.
+When this option is omitted, the default set of substitute servers is
+queried.
 
address@hidden address@hidden
address@hidden address@hidden
 @itemx -s @var{system}
 Query substitutes for @var{system}---e.g., @code{aarch64-linux}.  This
 option can be repeated, in which case @command{guix weather} will query
 substitutes for several system types.
 
address@hidden address@hidden
address@hidden address@hidden
 Instead of querying substitutes for all the packages, only ask for those
-specified in @var{file}.  @var{file} must contain a @dfn{manifest}, as
-with the @code{-m} option of @command{guix package} (@pxref{Invoking
-guix package}).
+specified in @var{file}.  @var{file} must contain a @dfn{manifest}, as with
+the @code{-m} option of @command{guix package} (@pxref{Aufruf von guix 
package}).
 @end table
 
 @node Invoking guix processes
 @section Invoking @command{guix processes}
 
 The @command{guix processes} command can be useful to developers and system
-administrators, especially on multi-user machines and on build farms: it lists
-the current sessions (connections to the daemon), as well as information about
-the processes address@hidden sessions, when @command{guix-daemon} is
-started with @option{--listen} specifying a TCP endpoint, are @emph{not}
-listed.}.  Here's an example of the information it returns:
+administrators, especially on multi-user machines and on build farms: it
+lists the current sessions (connections to the daemon), as well as
+information about the processes address@hidden sessions, when
address@hidden is started with @option{--listen} specifying a TCP
+endpoint, are @emph{not} listed.}.  Here's an example of the information it
+returns:
 
 @example
 $ sudo guix processes
@@ -8792,22 +8868,22 @@ ChildProcess: 27793: guix offload x86_64-linux 7200 1 
28800
 @end example
 
 In this example we see that @command{guix-daemon} has three clients:
address@hidden environment}, @command{guix publish}, and the Cuirass continuous
-integration tool; their process identifier (PID) is given by the
address@hidden environment}, @command{guix publish}, and the Cuirass
+continuous integration tool; their process identifier (PID) is given by the
 @code{ClientPID} field.  The @code{SessionPID} field gives the PID of the
 @command{guix-daemon} sub-process of this particular session.
 
-The @code{LockHeld} fields show which store items are currently locked by this
-session, which corresponds to store items being built or substituted (the
address@hidden field is not displayed when @command{guix processes} is not
-running as root.)  Last, by looking at the @code{ChildProcess} field, we
-understand that these three builds are being offloaded (@pxref{Daemon Offload
-Setup}).
+The @code{LockHeld} fields show which store items are currently locked by
+this session, which corresponds to store items being built or substituted
+(the @code{LockHeld} field is not displayed when @command{guix processes} is
+not running as root.)  Last, by looking at the @code{ChildProcess} field, we
+understand that these three builds are being offloaded (@pxref{Auslagern des 
Daemons einrichten}).
 
 The output is in Recutils format so we can use the handy @command{recsel}
 command to select sessions of interest (@pxref{Selection Expressions,,,
-recutils, GNU recutils manual}).  As an example, the command shows the command
-line and PID of the client that triggered the build of a Perl package:
+recutils, GNU recutils manual}).  As an example, the command shows the
+command line and PID of the client that triggered the build of a Perl
+package:
 
 @example
 $ sudo guix processes | \
@@ -8817,26 +8893,25 @@ ClientCommand: cuirass --cache-directory 
/var/cache/cuirass @dots{}
 @end example
 
 @c *********************************************************************
address@hidden GNU Distribution
address@hidden GNU Distribution
address@hidden GNU-Distribution
address@hidden GNU-Distribution
 
 @cindex Guix System Distribution
 @cindex GuixSD
-Guix comes with a distribution of the GNU system consisting entirely of
-free address@hidden term ``free'' here refers to the
address@hidden://www.gnu.org/philosophy/free-sw.html,freedom provided to
-users of that software}.}.  The
-distribution can be installed on its own (@pxref{System Installation}),
-but it is also possible to install Guix as a package manager on top of
-an installed GNU/Linux system (@pxref{Installation}).  To distinguish
-between the two, we refer to the standalone distribution as the Guix
-System Distribution, or GuixSD.
+Guix comes with a distribution of the GNU system consisting entirely of free
address@hidden term ``free'' here refers to the
address@hidden://www.gnu.org/philosophy/free-sw.html,freedom provided to users 
of
+that software}.}.  The distribution can be installed on its own
+(@pxref{Systeminstallation}), but it is also possible to install Guix as a
+package manager on top of an installed GNU/Linux system
+(@pxref{Installation}).  To distinguish between the two, we refer to the
+standalone distribution as the Guix System Distribution, or GuixSD.
 
 The distribution provides core GNU packages such as GNU libc, GCC, and
-Binutils, as well as many GNU and non-GNU applications.  The complete
-list of available packages can be browsed
address@hidden://www.gnu.org/software/guix/packages,on-line} or by
-running @command{guix package} (@pxref{Invoking guix package}):
+Binutils, as well as many GNU and non-GNU applications.  The complete list
+of available packages can be browsed
address@hidden://www.gnu.org/software/guix/packages,on-line} or by running
address@hidden package} (@pxref{Aufruf von guix package}):
 
 @example
 guix package --list-available
@@ -8844,8 +8919,8 @@ guix package --list-available
 
 Our goal is to provide a practical 100% free software distribution of
 Linux-based and other variants of GNU, with a focus on the promotion and
-tight integration of GNU components, and an emphasis on programs and
-tools that help users exert that freedom.
+tight integration of GNU components, and an emphasis on programs and tools
+that help users exert that freedom.
 
 Packages are currently available on the following platforms:
 
@@ -8858,18 +8933,17 @@ Intel/AMD @code{x86_64} architecture, Linux-Libre 
kernel;
 Intel 32-bit architecture (IA32), Linux-Libre kernel;
 
 @item armhf-linux
-ARMv7-A architecture with hard float, Thumb-2 and NEON,
-using the EABI hard-float application binary interface (ABI),
-and Linux-Libre kernel.
+ARMv7-A architecture with hard float, Thumb-2 and NEON, using the EABI
+hard-float application binary interface (ABI), and Linux-Libre kernel.
 
 @item aarch64-linux
 little-endian 64-bit ARMv8-A processors, Linux-Libre kernel.  This is
 currently in an experimental stage, with limited support.
address@hidden, for how to help!
address@hidden, for how to help!
 
 @item mips64el-linux
-little-endian 64-bit MIPS processors, specifically the Loongson series,
-n32 ABI, and Linux-Libre kernel.
+little-endian 64-bit MIPS processors, specifically the Loongson series, n32
+ABI, and Linux-Libre kernel.
 
 @end table
 
@@ -8877,41 +8951,42 @@ GuixSD itself is currently only available on 
@code{i686} and @code{x86_64}.
 
 @noindent
 For information on porting to other architectures or kernels,
address@hidden
address@hidden
 
 @menu
-* System Installation::         Installing the whole operating system.
-* System Configuration::        Configuring the operating system.
-* Documentation::               Browsing software user manuals.
-* Installing Debugging Files::  Feeding the debugger.
-* Security Updates::            Deploying security fixes quickly.
-* Package Modules::             Packages from the programmer's viewpoint.
-* Packaging Guidelines::        Growing the distribution.
-* Bootstrapping::               GNU/Linux built from scratch.
-* Porting::                     Targeting another platform or kernel.
+* Systeminstallation::       Das ganze Betriebssystem installieren.
+* Systemkonfiguration::      Das Betriebssystem konfigurieren.
+* Dokumentation::            Wie man Nutzerhandbücher von Software liest.
+* Dateien zur Fehlersuche installieren::  Womit man seinen Debugger 
+                                            füttert.
+* Sicherheitsaktualisierungen::  Sicherheits-Patches schnell einspielen.
+* Paketmodule::              Pakete aus Sicht des Programmierers.
+* Paketrichtlinien::         Die Distribution wachsen lassen.
+* Bootstrapping::            GNU/Linux von Grund auf selbst erstellen.
+* Portierung::               Guix auf andere Plattformen und Kernels 
+                               bringen.
 @end menu
 
-Building this distribution is a cooperative effort, and you are invited
-to join!  @xref{Contributing}, for information about how you can help.
+Building this distribution is a cooperative effort, and you are invited to
+join! @xref{Mitwirken}, for information about how you can help.
 
address@hidden System Installation
address@hidden System Installation
address@hidden Systeminstallation
address@hidden Systeminstallation
 
 @cindex installing GuixSD
 @cindex Guix System Distribution
 This section explains how to install the Guix System Distribution (GuixSD)
-on a machine.  The Guix package manager can
-also be installed on top of a running GNU/Linux system,
address@hidden
+on a machine.  The Guix package manager can also be installed on top of a
+running GNU/Linux system, @pxref{Installation}.
 
 @ifinfo
address@hidden Note
address@hidden Anmerkung
 @c This paragraph is for people reading this from tty2 of the
 @c installation image.
-You are reading this documentation with an Info reader.  For details on
-how to use it, hit the @key{RET} key (``return'' or ``enter'') on the
-link that follows: @pxref{Top, Info reader,, info-stnd, Stand-alone GNU
-Info}.  Hit @kbd{l} afterwards to come back here.
+You are reading this documentation with an Info reader.  For details on how
+to use it, hit the @key{RET} key (``return'' or ``enter'') on the link that
+follows: @pxref{Top, Info reader,, info-stnd, Stand-alone GNU Info}.  Hit
address@hidden afterwards to come back here.
 
 Alternately, run @command{info info} in another tty to keep the manual
 available.
@@ -8919,27 +8994,28 @@ available.
 @end ifinfo
 
 @menu
-* Limitations::                 What you can expect.
-* Hardware Considerations::     Supported hardware.
-* USB Stick and DVD Installation::  Preparing the installation medium.
-* Preparing for Installation::  Networking, partitioning, etc.
-* Proceeding with the Installation::  The real thing.
-* Installing GuixSD in a VM::   GuixSD playground.
-* Building the Installation Image::  How this comes to be.
+* Einschränkungen::         Was Sie erwarten dürfen.
+* Hardware-Überlegungen::   Unterstützte Hardware.
+* Installation von USB-Stick oder DVD::  Das Installationsmedium 
+                                           vorbereiten.
+* Vor der Installation::     Netzwerkanbindung, Partitionierung etc.
+* Fortfahren mit der Installation::  Die Hauptsache.
+* GuixSD in einer VM installieren::  Ein GuixSD-Spielplatz.
+* Ein Abbild zur Installation erstellen::  Wie ein solches entsteht.
 @end menu
 
address@hidden Limitations
address@hidden Limitations
address@hidden Einschränkungen
address@hidden Einschränkungen
 
-As of version @value{VERSION}, the Guix System Distribution (GuixSD) is
-not production-ready.  It may contain bugs and lack important
-features.  Thus, if you are looking for a stable production system that
-respects your freedom as a computer user, a good solution at this point
-is to consider @url{http://www.gnu.org/distros/free-distros.html, one of
-the more established GNU/Linux distributions}.  We hope you can soon switch
-to the GuixSD without fear, of course.  In the meantime, you can
-also keep using your distribution and try out the package manager on top
-of it (@pxref{Installation}).
+As of version @value{VERSION}, the Guix System Distribution (GuixSD) is not
+production-ready.  It may contain bugs and lack important features.  Thus,
+if you are looking for a stable production system that respects your freedom
+as a computer user, a good solution at this point is to consider
address@hidden://www.gnu.org/distros/free-distros.html, one of the more
+established GNU/Linux distributions}.  We hope you can soon switch to the
+GuixSD without fear, of course.  In the meantime, you can also keep using
+your distribution and try out the package manager on top of it
+(@pxref{Installation}).
 
 Before you proceed with the installation, be aware of the following
 noteworthy limitations applicable to version @value{VERSION}:
@@ -8947,71 +9023,70 @@ noteworthy limitations applicable to version 
@value{VERSION}:
 @itemize
 @item
 The installation process does not include a graphical user interface and
-requires familiarity with GNU/Linux (see the following subsections to
-get a feel of what that means.)
+requires familiarity with GNU/Linux (see the following subsections to get a
+feel of what that means.)
 
 @item
 Support for the Logical Volume Manager (LVM) is missing.
 
 @item
-More and more system services are provided (@pxref{Services}), but some
-may be missing.
+More and more system services are provided (@pxref{Dienste}), but some may
+be missing.
 
 @item
-More than 7,500 packages are available, but you might
-occasionally find that a useful package is missing.
+More than 7,500 packages are available, but you might occasionally find that
+a useful package is missing.
 
 @item
-GNOME, Xfce, LXDE, and Enlightenment are available (@pxref{Desktop Services}),
-as well as a number of X11 window managers.  However, some graphical
-applications may be missing, as well as KDE.
+GNOME, Xfce, LXDE, and Enlightenment are available (@pxref{Desktop-Dienste}), 
as well as a number of X11 window managers.  However, some
+graphical applications may be missing, as well as KDE.
 @end itemize
 
-You have been warned!  But more than a disclaimer, this is an invitation
-to report issues (and success stories!), and to join us in improving it.
address@hidden, for more info.
+You have been warned! But more than a disclaimer, this is an invitation to
+report issues (and success stories!), and to join us in improving it.
address@hidden, for more info.
 
 
address@hidden Hardware Considerations
address@hidden Hardware Considerations
address@hidden Hardware-Überlegungen
address@hidden Hardware-Überlegungen
 
 @cindex hardware support on GuixSD
 address@hidden focuses on respecting the user's computing freedom.  It
 builds around the kernel Linux-libre, which means that only hardware for
-which free software drivers and firmware exist is supported.  Nowadays,
-a wide range of off-the-shelf hardware is supported on
-GNU/Linux-libre---from keyboards to graphics cards to scanners and
-Ethernet controllers.  Unfortunately, there are still areas where
-hardware vendors deny users control over their own computing, and such
-hardware is not supported on GuixSD.
+which free software drivers and firmware exist is supported.  Nowadays, a
+wide range of off-the-shelf hardware is supported on GNU/Linux-libre---from
+keyboards to graphics cards to scanners and Ethernet controllers.
+Unfortunately, there are still areas where hardware vendors deny users
+control over their own computing, and such hardware is not supported on
+GuixSD.
 
 @cindex WiFi, hardware support
 One of the main areas where free drivers or firmware are lacking is WiFi
 devices.  WiFi devices known to work include those using Atheros chips
 (AR9271 and AR7010), which corresponds to the @code{ath9k} Linux-libre
-driver, and those using Broadcom/AirForce chips (BCM43xx with
-Wireless-Core Revision 5), which corresponds to the @code{b43-open}
-Linux-libre driver.  Free firmware exists for both and is available
-out-of-the-box on GuixSD, as part of @var{%base-firmware}
-(@pxref{operating-system Reference, @code{firmware}}).
+driver, and those using Broadcom/AirForce chips (BCM43xx with Wireless-Core
+Revision 5), which corresponds to the @code{b43-open} Linux-libre driver.
+Free firmware exists for both and is available out-of-the-box on GuixSD, as
+part of @var{%base-firmware} (@pxref{„operating-system“-Referenz,
address@hidden).
 
 @cindex RYF, Respects Your Freedom
 The @uref{https://www.fsf.org/, Free Software Foundation} runs
 @uref{https://www.fsf.org/ryf, @dfn{Respects Your Freedom}} (RYF), a
-certification program for hardware products that respect your freedom
-and your privacy and ensure that you have control over your device.  We
+certification program for hardware products that respect your freedom and
+your privacy and ensure that you have control over your device.  We
 encourage you to check the list of RYF-certified devices.
 
-Another useful resource is the @uref{https://www.h-node.org/, H-Node}
-web site.  It contains a catalog of hardware devices with information
-about their support in GNU/Linux.
+Another useful resource is the @uref{https://www.h-node.org/, H-Node} web
+site.  It contains a catalog of hardware devices with information about
+their support in GNU/Linux.
 
 
address@hidden USB Stick and DVD Installation
address@hidden USB Stick and DVD Installation
address@hidden Installation von USB-Stick oder DVD
address@hidden Installation von USB-Stick oder DVD
 
-An ISO-9660 installation image that can be written to a USB stick or
-burnt to a DVD can be downloaded from
+An ISO-9660 installation image that can be written to a USB stick or burnt
+to a DVD can be downloaded from
 @indicateurl{https://alpha.gnu.org/gnu/guix/address@hidden@var{system}.iso.xz},
 where @var{system} is one of:
 
@@ -9032,19 +9107,20 @@ $ wget 
https://alpha.gnu.org/gnu/guix/address@hidden@var{system
 $ gpg --verify address@hidden@var{system}.iso.xz.sig
 @end example
 
-If that command fails because you do not have the required public key,
-then run this command to import it:
+Falls dieser Befehl fehlschlägt, weil Sie nicht über den nötigen
+öffentlichen Schlüssel verfügen, können Sie ihn mit diesem Befehl
+importieren:
 
 @example
 $ gpg --keyserver pgp.mit.edu --recv-keys @value{OPENPGP-SIGNING-KEY-ID}
 @end example
 
 @noindent
-and rerun the @code{gpg --verify} command.
 @c end duplication
+und den Befehl @code{gpg --verify} erneut ausführen.
 
-This image contains the tools necessary for an installation.
-It is meant to be copied @emph{as is} to a large-enough USB stick or DVD.
+This image contains the tools necessary for an installation.  It is meant to
+be copied @emph{as is} to a large-enough USB stick or DVD.
 
 @unnumberedsubsubsec Copying to a USB Stick
 
@@ -9084,9 +9160,9 @@ xz -d address@hidden@var{system}.iso.xz
 @end example
 
 @item
-Insert a blank DVD into your machine, and determine
-its device name.  Assuming that the DVD drive is known as @file{/dev/srX},
-copy the image with:
+Insert a blank DVD into your machine, and determine its device name.
+Assuming that the DVD drive is known as @file{/dev/srX}, copy the image
+with:
 
 @example
 growisofs -dvd-compat -Z /dev/address@hidden
@@ -9097,50 +9173,50 @@ Access to @file{/dev/srX} usually requires root 
privileges.
 
 @unnumberedsubsubsec Booting
 
-Once this is done, you should be able to reboot the system and boot from
-the USB stick or DVD.  The latter usually requires you to get in the
-BIOS or UEFI boot menu, where you can choose to boot from the USB stick.
+Once this is done, you should be able to reboot the system and boot from the
+USB stick or DVD.  The latter usually requires you to get in the BIOS or
+UEFI boot menu, where you can choose to boot from the USB stick.
 
address@hidden GuixSD in a VM}, if, instead, you would like to install
address@hidden in einer VM installieren}, if, instead, you would like to install
 GuixSD in a virtual machine (VM).
 
 
address@hidden Preparing for Installation
address@hidden Preparing for Installation
address@hidden Vor der Installation
address@hidden Vor der Installation
 
-Once you have successfully booted your computer using the installation medium,
-you should end up with a root prompt.  Several console TTYs are configured
-and can be used to run commands as root.  TTY2 shows this documentation,
-browsable using the Info reader commands (@pxref{Top,,, info-stnd,
-Stand-alone GNU Info}).  The installation system runs the GPM mouse
-daemon, which allows you to select text with the left mouse button and
+Once you have successfully booted your computer using the installation
+medium, you should end up with a root prompt.  Several console TTYs are
+configured and can be used to run commands as root.  TTY2 shows this
+documentation, browsable using the Info reader commands (@pxref{Top,,,
+info-stnd, Stand-alone GNU Info}).  The installation system runs the GPM
+mouse daemon, which allows you to select text with the left mouse button and
 to paste it with the middle button.
 
address@hidden Note
address@hidden Anmerkung
 Installation requires access to the Internet so that any missing
 dependencies of your system configuration can be downloaded.  See the
 ``Networking'' section below.
 @end quotation
 
 The installation system includes many common tools needed for this task.
-But it is also a full-blown GuixSD system, which means that you can
-install additional packages, should you need it, using @command{guix
-package} (@pxref{Invoking guix package}).
+But it is also a full-blown GuixSD system, which means that you can install
+additional packages, should you need it, using @command{guix package}
+(@pxref{Aufruf von guix package}).
 
 @subsubsection Keyboard Layout
 
 @cindex keyboard layout
-The installation image uses the US qwerty keyboard layout.  If you want
-to change it, you can use the @command{loadkeys} command.  For example,
-the following command selects the Dvorak keyboard layout:
+The installation image uses the US qwerty keyboard layout.  If you want to
+change it, you can use the @command{loadkeys} command.  For example, the
+following command selects the Dvorak keyboard layout:
 
 @example
 loadkeys dvorak
 @end example
 
-See the files under @file{/run/current-system/profile/share/keymaps} for
-a list of available keyboard layouts.  Run @command{man loadkeys} for
-more information.
+See the files under @file{/run/current-system/profile/share/keymaps} for a
+list of available keyboard layouts.  Run @command{man loadkeys} for more
+information.
 
 @subsubsection Networking
 
@@ -9159,9 +9235,9 @@ ip a
 
 @c 
http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_id.c#n20
 Wired interfaces have a name starting with @samp{e}; for example, the
-interface corresponding to the first on-board Ethernet controller is
-called @samp{eno1}.  Wireless interfaces have a name starting with
address@hidden, like @samp{w1p2s0}.
+interface corresponding to the first on-board Ethernet controller is called
address@hidden  Wireless interfaces have a name starting with @samp{w}, like
address@hidden
 
 @table @asis
 @item Wired connection
@@ -9175,18 +9251,17 @@ ifconfig @var{interface} up
 @item Wireless connection
 @cindex wireless
 @cindex WiFi
-To configure wireless networking, you can create a configuration file
-for the @command{wpa_supplicant} configuration tool (its location is not
-important) using one of the available text editors such as
address@hidden:
+To configure wireless networking, you can create a configuration file for
+the @command{wpa_supplicant} configuration tool (its location is not
+important) using one of the available text editors such as @command{nano}:
 
 @example
 nano wpa_supplicant.conf
 @end example
 
-As an example, the following stanza can go to this file and will work
-for many wireless networks, provided you give the actual SSID and
-passphrase for the network you are connecting to:
+As an example, the following stanza can go to this file and will work for
+many wireless networks, provided you give the actual SSID and passphrase for
+the network you are connecting to:
 
 @example
 address@hidden
@@ -9196,9 +9271,9 @@ address@hidden
 @}
 @end example
 
-Start the wireless service and run it in the background with the
-following command (substitute @var{interface} with the name of the
-network interface you want to use):
+Start the wireless service and run it in the background with the following
+command (substitute @var{interface} with the name of the network interface
+you want to use):
 
 @example
 wpa_supplicant -c wpa_supplicant.conf -i @var{interface} -B
@@ -9221,12 +9296,12 @@ Try to ping a server to see if networking is up and 
running:
 ping -c 3 gnu.org
 @end example
 
-Setting up network access is almost always a requirement because the
-image does not contain all the software and tools that may be needed.
+Setting up network access is almost always a requirement because the image
+does not contain all the software and tools that may be needed.
 
 @cindex installing over SSH
-If you want to, you can continue the installation remotely by starting
-an SSH server:
+If you want to, you can continue the installation remotely by starting an
+SSH server:
 
 @example
 herd start ssh-daemon
@@ -9237,13 +9312,13 @@ OpenSSH public key authentication before logging in.
 
 @subsubsection Disk Partitioning
 
-Unless this has already been done, the next step is to partition, and
-then format the target partition(s).
+Unless this has already been done, the next step is to partition, and then
+format the target partition(s).
 
-The installation image includes several partitioning tools, including
-Parted (@pxref{Overview,,, parted, GNU Parted User Manual}),
address@hidden, and @command{cfdisk}.  Run it and set up your disk with
-the partition layout you want:
+The installation image includes several partitioning tools, including Parted
+(@pxref{Overview,,, parted, GNU Parted User Manual}), @command{fdisk}, and
address@hidden  Run it and set up your disk with the partition layout you
+want:
 
 @example
 cfdisk
@@ -9251,60 +9326,59 @@ cfdisk
 
 If your disk uses the GUID Partition Table (GPT) format and you plan to
 install BIOS-based GRUB (which is the default), make sure a BIOS Boot
-Partition is available (@pxref{BIOS installation,,, grub, GNU GRUB
-manual}).
+Partition is available (@pxref{BIOS installation,,, grub, GNU GRUB manual}).
 
 @cindex EFI, installation
 @cindex UEFI, installation
 @cindex ESP, EFI system partition
-If you instead wish to use EFI-based GRUB, a FAT32 @dfn{EFI System Partition}
-(ESP) is required.  This partition should be mounted at @file{/boot/efi} and
-must have the @code{esp} flag set.  E.g., for @command{parted}:
+If you instead wish to use EFI-based GRUB, a FAT32 @dfn{EFI System
+Partition} (ESP) is required.  This partition should be mounted at
address@hidden/boot/efi} and must have the @code{esp} flag set.  E.g., for
address@hidden:
 
 @example
 parted /dev/sda set 1 esp on
 @end example
 
address@hidden Note
address@hidden Anmerkung
 @vindex grub-bootloader
 @vindex grub-efi-bootloader
-Unsure whether to use EFI- or BIOS-based GRUB?  If the directory
+Unsure whether to use EFI- or BIOS-based GRUB? If the directory
 @file{/sys/firmware/efi} exists in the installation image, then you should
 probably perform an EFI installation, using @code{grub-efi-bootloader}.
 Otherwise you should use the BIOS-based GRUB, known as
address@hidden  @xref{Bootloader Configuration}, for more info on
address@hidden  @xref{Bootloader-Konfiguration}, for more info on
 bootloaders.
 @end quotation
 
 Once you are done partitioning the target hard disk drive, you have to
-create a file system on the relevant partition(s)@footnote{Currently
-GuixSD only supports ext4 and btrfs file systems.  In particular, code
-that reads file system UUIDs and labels only works for these file system
-types.}.  For the ESP, if you have one and assuming it is
address@hidden/dev/sda1}, run:
+create a file system on the relevant partition(s)@footnote{Currently GuixSD
+only supports ext4 and btrfs file systems.  In particular, code that reads
+file system UUIDs and labels only works for these file system types.}.  For
+the ESP, if you have one and assuming it is @file{/dev/sda1}, run:
 
 @example
 mkfs.fat -F32 /dev/sda1
 @end example
 
-Preferably, assign file systems a label so that you can easily and
-reliably refer to them in @code{file-system} declarations (@pxref{File
-Systems}).  This is typically done using the @code{-L} option of
address@hidden and related commands.  So, assuming the target root
-partition lives at @file{/dev/sda2}, a file system with the label
address@hidden can be created with:
+Preferably, assign file systems a label so that you can easily and reliably
+refer to them in @code{file-system} declarations (@pxref{Dateisysteme}).
+This is typically done using the @code{-L} option of @command{mkfs.ext4} and
+related commands.  So, assuming the target root partition lives at
address@hidden/dev/sda2}, a file system with the label @code{my-root} can be 
created
+with:
 
 @example
 mkfs.ext4 -L my-root /dev/sda2
 @end example
 
 @cindex encrypted disk
-If you are instead planning to encrypt the root partition, you can use
-the Cryptsetup/LUKS utilities to do that (see @inlinefmtifelse{html,
+If you are instead planning to encrypt the root partition, you can use the
+Cryptsetup/LUKS utilities to do that (see @inlinefmtifelse{html,
 @uref{https://linux.die.net/man/8/cryptsetup, @code{man cryptsetup}},
address@hidden cryptsetup}} for more information.)  Assuming you want to
-store the root partition on @file{/dev/sda2}, the command sequence would
-be along these lines:
address@hidden cryptsetup}} for more information.)  Assuming you want to store
+the root partition on @file{/dev/sda2}, the command sequence would be along
+these lines:
 
 @example
 cryptsetup luksFormat /dev/sda2
@@ -9312,35 +9386,35 @@ cryptsetup open --type luks /dev/sda2 my-partition
 mkfs.ext4 -L my-root /dev/mapper/my-partition
 @end example
 
-Once that is done, mount the target file system under @file{/mnt}
-with a command like (again, assuming @code{my-root} is the label of the
-root file system):
+Once that is done, mount the target file system under @file{/mnt} with a
+command like (again, assuming @code{my-root} is the label of the root file
+system):
 
 @example
 mount LABEL=my-root /mnt
 @end example
 
-Also mount any other file systems you would like to use on the target
-system relative to this path.  If you have @file{/boot} on a separate
-partition for example, mount it at @file{/mnt/boot} now so it is found
-by @code{guix system init} afterwards.
+Also mount any other file systems you would like to use on the target system
+relative to this path.  If you have @file{/boot} on a separate partition for
+example, mount it at @file{/mnt/boot} now so it is found by @code{guix
+system init} afterwards.
 
 Finally, if you plan to use one or more swap partitions (@pxref{Memory
-Concepts, swap space,, libc, The GNU C Library Reference Manual}), make
-sure to initialize them with @command{mkswap}.  Assuming you have one
-swap partition on @file{/dev/sda3}, you would run:
+Concepts, swap space,, libc, The GNU C Library Reference Manual}), make sure
+to initialize them with @command{mkswap}.  Assuming you have one swap
+partition on @file{/dev/sda3}, you would run:
 
 @example
 mkswap /dev/sda3
 swapon /dev/sda3
 @end example
 
-Alternatively, you may use a swap file.  For example, assuming that in
-the new system you want to use the file @file{/swapfile} as a swap file,
-you would address@hidden example will work for many types of file
-systems (e.g., ext4).  However, for copy-on-write file systems (e.g.,
-btrfs), the required steps may be different.  For details, see the
-manual pages for @command{mkswap} and @command{swapon}.}:
+Alternatively, you may use a swap file.  For example, assuming that in the
+new system you want to use the file @file{/swapfile} as a swap file, you
+would address@hidden example will work for many types of file systems
+(e.g., ext4).  However, for copy-on-write file systems (e.g., btrfs), the
+required steps may be different.  For details, see the manual pages for
address@hidden and @command{swapon}.}:
 
 @example
 # This is 10 GiB of swap space.  Adjust "count" to change the size.
@@ -9351,15 +9425,15 @@ mkswap /mnt/swapfile
 swapon /mnt/swapfile
 @end example
 
-Note that if you have encrypted the root partition and created a swap
-file in its file system as described above, then the encryption also
-protects the swap file, just like any other file in that file system.
+Note that if you have encrypted the root partition and created a swap file
+in its file system as described above, then the encryption also protects the
+swap file, just like any other file in that file system.
 
address@hidden Proceeding with the Installation
address@hidden Proceeding with the Installation
address@hidden Fortfahren mit der Installation
address@hidden Fortfahren mit der Installation
 
-With the target partitions ready and the target root mounted on
address@hidden/mnt}, we're ready to go.  First, run:
+With the target partitions ready and the target root mounted on @file{/mnt},
+we're ready to go.  First, run:
 
 @example
 herd start cow-store /mnt
@@ -9371,23 +9445,21 @@ rather than kept in memory.  This is necessary because 
the first phase of
 the @command{guix system init} command (see below) entails downloads or
 builds to @file{/gnu/store} which, initially, is an in-memory file system.
 
-Next, you have to edit a file and
-provide the declaration of the operating system to be installed.  To
-that end, the installation system comes with three text editors.  We
-recommend GNU nano (@pxref{Top,,, nano, GNU nano Manual}), which
-supports syntax highlighting and parentheses matching; other editors
-include GNU Zile (an Emacs clone), and
-nvi (a clone of the original BSD @command{vi} editor).
-We strongly recommend storing that file on the target root file system, say,
-as @file{/mnt/etc/config.scm}.  Failing to do that, you will have lost your
-configuration file once you have rebooted into the newly-installed system.
-
address@hidden the Configuration System}, for an overview of the
-configuration file.  The example configurations discussed in that
-section are available under @file{/etc/configuration} in the
-installation image.  Thus, to get started with a system configuration
-providing a graphical display server (a ``desktop'' system), you can run
-something along these lines:
+Next, you have to edit a file and provide the declaration of the operating
+system to be installed.  To that end, the installation system comes with
+three text editors.  We recommend GNU nano (@pxref{Top,,, nano, GNU nano
+Manual}), which supports syntax highlighting and parentheses matching; other
+editors include GNU Zile (an Emacs clone), and nvi (a clone of the original
+BSD @command{vi} editor).  We strongly recommend storing that file on the
+target root file system, say, as @file{/mnt/etc/config.scm}.  Failing to do
+that, you will have lost your configuration file once you have rebooted into
+the newly-installed system.
+
address@hidden Konfigurationssystems nutzen}, for an overview of the 
configuration
+file.  The example configurations discussed in that section are available
+under @file{/etc/configuration} in the installation image.  Thus, to get
+started with a system configuration providing a graphical display server (a
+``desktop'' system), you can run something along these lines:
 
 @example
 # mkdir /mnt/etc
@@ -9395,80 +9467,79 @@ something along these lines:
 # nano /mnt/etc/config.scm
 @end example
 
-You should pay attention to what your configuration file contains, and
-in particular:
+You should pay attention to what your configuration file contains, and in
+particular:
 
 @itemize
 @item
-Make sure the @code{bootloader-configuration} form refers to the target
-you want to install GRUB on.  It should mention @code{grub-bootloader} if
-you are installing GRUB in the legacy way, or @code{grub-efi-bootloader}
-for newer UEFI systems.  For legacy systems, the @code{target} field
-names a device, like @code{/dev/sda}; for UEFI systems it names a path
-to a mounted EFI partition, like @code{/boot/efi}, and do make sure the
-path is actually mounted.
+Make sure the @code{bootloader-configuration} form refers to the target you
+want to install GRUB on.  It should mention @code{grub-bootloader} if you
+are installing GRUB in the legacy way, or @code{grub-efi-bootloader} for
+newer UEFI systems.  For legacy systems, the @code{target} field names a
+device, like @code{/dev/sda}; for UEFI systems it names a path to a mounted
+EFI partition, like @code{/boot/efi}, and do make sure the path is actually
+mounted.
 
 @item
 Be sure that your file system labels match the value of their respective
address@hidden fields in your @code{file-system} configuration, assuming
-your @code{file-system} configuration uses the @code{file-system-label}
-procedure in its @code{device} field.
address@hidden fields in your @code{file-system} configuration, assuming your
address@hidden configuration uses the @code{file-system-label} procedure
+in its @code{device} field.
 
 @item
 If there are encrypted or RAID partitions, make sure to add a
address@hidden field to describe them (@pxref{Mapped Devices}).
address@hidden field to describe them (@pxref{Abgebildete Geräte}).
 @end itemize
 
-Once you are done preparing the configuration file, the new system must
-be initialized (remember that the target root file system is mounted
-under @file{/mnt}):
+Once you are done preparing the configuration file, the new system must be
+initialized (remember that the target root file system is mounted under
address@hidden/mnt}):
 
 @example
 guix system init /mnt/etc/config.scm /mnt
 @end example
 
 @noindent
-This copies all the necessary files and installs GRUB on
address@hidden/dev/sdX}, unless you pass the @option{--no-bootloader} option.  
For
-more information, @pxref{Invoking guix system}.  This command may trigger
-downloads or builds of missing packages, which can take some time.
+This copies all the necessary files and installs GRUB on @file{/dev/sdX},
+unless you pass the @option{--no-bootloader} option.  For more information,
address@hidden von guix system}.  This command may trigger downloads or builds
+of missing packages, which can take some time.
 
 Once that command has completed---and hopefully succeeded!---you can run
address@hidden and boot into the new system.  The @code{root} password
-in the new system is initially empty; other users' passwords need to be
-initialized by running the @command{passwd} command as @code{root},
-unless your configuration specifies otherwise
-(@pxref{user-account-password, user account passwords}).
address@hidden and boot into the new system.  The @code{root} password in
+the new system is initially empty; other users' passwords need to be
+initialized by running the @command{passwd} command as @code{root}, unless
+your configuration specifies otherwise (@pxref{user-account-password, user
+account passwords}).
 
 @cindex upgrading GuixSD
 From then on, you can update GuixSD whenever you want by running
address@hidden pull} as @code{root} (@pxref{Invoking guix pull}), and
-then running @command{guix system reconfigure} to build a new system
-generation with the latest packages and services (@pxref{Invoking guix
-system}).  We recommend doing that regularly so that your system
-includes the latest security updates (@pxref{Security Updates}).
address@hidden pull} as @code{root} (@pxref{Aufruf von guix pull}), and then
+running @command{guix system reconfigure} to build a new system generation
+with the latest packages and services (@pxref{Aufruf von guix system}).  We
+recommend doing that regularly so that your system includes the latest
+security updates (@pxref{Sicherheitsaktualisierungen}).
 
 Join us on @code{#guix} on the Freenode IRC network or on
address@hidden@@gnu.org} to share your experience---good or not so
-good.
address@hidden@@gnu.org} to share your experience---good or not so good.
 
address@hidden Installing GuixSD in a VM
address@hidden GuixSD in einer VM installieren
 @subsection Installing GuixSD in a Virtual Machine
 
 @cindex virtual machine, GuixSD installation
 @cindex virtual private server (VPS)
 @cindex VPS (virtual private server)
-If you'd like to install GuixSD in a virtual machine (VM) or on a
-virtual private server (VPS) rather than on your beloved machine, this
-section is for you.
+If you'd like to install GuixSD in a virtual machine (VM) or on a virtual
+private server (VPS) rather than on your beloved machine, this section is
+for you.
 
-To boot a @uref{http://qemu.org/,QEMU} VM for installing GuixSD in a
-disk image, follow these steps:
+To boot a @uref{http://qemu.org/,QEMU} VM for installing GuixSD in a disk
+image, follow these steps:
 
 @enumerate
 @item
-First, retrieve and decompress the GuixSD installation image as
-described previously (@pxref{USB Stick and DVD Installation}).
+First, retrieve and decompress the GuixSD installation image as described
+previously (@pxref{Installation von USB-Stick oder DVD}).
 
 @item
 Create a disk image that will hold the installed system.  To make a
@@ -9478,8 +9549,8 @@ qcow2-formatted disk image, use the @command{qemu-img} 
command:
 qemu-img create -f qcow2 guixsd.img 50G
 @end example
 
-The resulting file will be much smaller than 50 GB (typically less than
-1 MB), but it will grow as the virtualized storage device is filled up.
+The resulting file will be much smaller than 50 GB (typically less than 1
+MB), but it will grow as the virtualized storage device is filled up.
 
 @item
 Boot the USB installation image in an VM:
@@ -9493,21 +9564,19 @@ qemu-system-x86_64 -m 1024 -smp 1 \
 
 The ordering of the drives matters.
 
-In the VM console, quickly press the @kbd{F12} key to enter the boot
-menu.  Then press the @kbd{2} key and the @kbd{RET} key to validate your
-selection.
+In the VM console, quickly press the @kbd{F12} key to enter the boot menu.
+Then press the @kbd{2} key and the @kbd{RET} key to validate your selection.
 
 @item
 You're now root in the VM, proceed with the installation process.
address@hidden for Installation}, and follow the instructions.
address@hidden der Installation}, and follow the instructions.
 @end enumerate
 
 Once installation is complete, you can boot the system that's on your
address@hidden image.  @xref{Running GuixSD in a VM}, for how to do
-that.
address@hidden image.  @xref{GuixSD in einer VM starten}, for how to do that.
 
address@hidden Building the Installation Image
address@hidden Building the Installation Image
address@hidden Ein Abbild zur Installation erstellen
address@hidden Ein Abbild zur Installation erstellen
 
 @cindex installation image
 The installation image described above was built using the @command{guix
@@ -9517,90 +9586,94 @@ system} command, specifically:
 guix system disk-image gnu/system/install.scm
 @end example
 
-Have a look at @file{gnu/system/install.scm} in the source tree,
-and see also @ref{Invoking guix system} for more information
-about the installation image.
+Have a look at @file{gnu/system/install.scm} in the source tree, and see
+also @ref{Aufruf von guix system} for more information about the installation
+image.
 
 @subsection Building the Installation Image for ARM Boards
 
 Many ARM boards require a specific variant of the
 @uref{http://www.denx.de/wiki/U-Boot/, U-Boot} bootloader.
 
-If you build a disk image and the bootloader is not available otherwise
-(on another boot drive etc), it's advisable to build an image that
-includes the bootloader, specifically:
+If you build a disk image and the bootloader is not available otherwise (on
+another boot drive etc), it's advisable to build an image that includes the
+bootloader, specifically:
 
 @example
 guix system disk-image --system=armhf-linux -e '((@@ (gnu system install) 
os-with-u-boot) (@@ (gnu system install) installation-os) 
"A20-OLinuXino-Lime2")'
 @end example
 
address@hidden is the name of the board.  If you specify an invalid
-board, a list of possible boards will be printed.
address@hidden is the name of the board.  If you specify an
+invalid board, a list of possible boards will be printed.
 
address@hidden System Configuration
address@hidden System Configuration
address@hidden Systemkonfiguration
address@hidden Systemkonfiguration
 
 @cindex system configuration
-The Guix System Distribution supports a consistent whole-system configuration
-mechanism.  By that we mean that all aspects of the global system
-configuration---such as the available system services, timezone and
-locale settings, user accounts---are declared in a single place.  Such
-a @dfn{system configuration} can be @dfn{instantiated}---i.e., effected.
+The Guix System Distribution supports a consistent whole-system
+configuration mechanism.  By that we mean that all aspects of the global
+system configuration---such as the available system services, timezone and
+locale settings, user accounts---are declared in a single place.  Such a
address@hidden configuration} can be @dfn{instantiated}---i.e., effected.
 
-One of the advantages of putting all the system configuration under the
-control of Guix is that it supports transactional system upgrades, and
-makes it possible to roll back to a previous system instantiation,
-should something go wrong with the new one (@pxref{Features}).  Another
-advantage is that it makes it easy to replicate the exact same configuration
-across different machines, or at different points in time, without
-having to resort to additional administration tools layered on top of
-the own tools of the system.
 @c Yes, we're talking of Puppet, Chef, & co. here.  ↑
+One of the advantages of putting all the system configuration under the
+control of Guix is that it supports transactional system upgrades, and makes
+it possible to roll back to a previous system instantiation, should
+something go wrong with the new one (@pxref{Funktionalitäten}).  Another 
advantage
+is that it makes it easy to replicate the exact same configuration across
+different machines, or at different points in time, without having to resort
+to additional administration tools layered on top of the own tools of the
+system.
 
 This section describes this mechanism.  First we focus on the system
 administrator's viewpoint---explaining how the system is configured and
-instantiated.  Then we show how this mechanism can be extended, for
-instance to support new system services.
+instantiated.  Then we show how this mechanism can be extended, for instance
+to support new system services.
 
 @menu
-* Using the Configuration System::  Customizing your GNU system.
-* operating-system Reference::  Detail of operating-system declarations.
-* File Systems::                Configuring file system mounts.
-* Mapped Devices::              Block device extra processing.
-* User Accounts::               Specifying user accounts.
-* Locales::                     Language and cultural convention settings.
-* Services::                    Specifying system services.
-* Setuid Programs::             Programs running with root privileges.
-* X.509 Certificates::          Authenticating HTTPS servers.
-* Name Service Switch::         Configuring libc's name service switch.
-* Initial RAM Disk::            Linux-Libre bootstrapping.
-* Bootloader Configuration::    Configuring the boot loader.
-* Invoking guix system::        Instantiating a system configuration.
-* Running GuixSD in a VM::      How to run GuixSD in a virtual machine.
-* Defining Services::           Adding new service definitions.
+* Das Konfigurationssystems nutzen::  Ihr GNU-System anpassen
+* „operating-system“-Referenz::  Details der 
+                                       Betriebssystem-Deklarationen.
+* Dateisysteme::             Die Dateisystemeinbindungen konfigurieren.
+* Abgebildete Geräte::      Zusatzverarbeitungsschritte für blockbasierte 
+                               Geräte.
+* Benutzerkonten::           Benutzerkonten festlegen.
+* Locales::                  Sprach- und kulturelle 
+                               Konventionseinstellungen.
+* Dienste::                  Systemdienste festlegen.
+* Setuid-Programme::         Programme mit Administratorrechten ausführen
+* X.509-Zertifikate::        HTTPS-Server authentifizieren.
+* Name Service Switch::      Den Name Service Switch von libc konfigurieren.
+* Initiale RAM-Disk::        Linux-libre hochfahren.
+* Bootloader-Konfiguration::  Den Bootloader konfigurieren.
+* Aufruf von guix system::   Instanzierung einer Systemkonfiguration
+* GuixSD in einer VM starten::  Wie man GuixSD in einer virtuellen Maschine 
+                                  startet.
+* Dienste definieren::       Neue Dienstdefinitionen hinzufügen.
 @end menu
 
address@hidden Using the Configuration System
address@hidden Using the Configuration System
address@hidden Das Konfigurationssystems nutzen
address@hidden Das Konfigurationssystems nutzen
 
-The operating system is configured by providing an
address@hidden declaration in a file that can then be passed to
-the @command{guix system} command (@pxref{Invoking guix system}).  A
-simple setup, with the default system services, the default Linux-Libre
-kernel, initial RAM disk, and boot loader looks like this:
+The operating system is configured by providing an @code{operating-system}
+declaration in a file that can then be passed to the @command{guix system}
+command (@pxref{Aufruf von guix system}).  A simple setup, with the default
+system services, the default Linux-Libre kernel, initial RAM disk, and boot
+loader looks like this:
 
 @findex operating-system
 @lisp
 @include os-config-bare-bones.texi
 @end lisp
 
-This example should be self-describing.  Some of the fields defined
-above, such as @code{host-name} and @code{bootloader}, are mandatory.
-Others, such as @code{packages} and @code{services}, can be omitted, in
-which case they get a default value.
+This example should be self-describing.  Some of the fields defined above,
+such as @code{host-name} and @code{bootloader}, are mandatory.  Others, such
+as @code{packages} and @code{services}, can be omitted, in which case they
+get a default value.
 
 Below we discuss the effect of some of the most important fields
-(@pxref{operating-system Reference}, for details about all the available
+(@pxref{„operating-system“-Referenz}, for details about all the available
 fields), and how to @dfn{instantiate} the operating system using
 @command{guix system}.
 
@@ -9612,9 +9685,10 @@ fields), and how to @dfn{instantiate} the operating 
system using
 @cindex EFI boot
 The @code{bootloader} field describes the method that will be used to boot
 your system.  Machines based on Intel processors can boot in ``legacy'' BIOS
-mode, as in the example above.  However, more recent machines rely instead on
-the @dfn{Unified Extensible Firmware Interface} (UEFI) to boot.  In that case,
-the @code{bootloader} field should contain something along these lines:
+mode, as in the example above.  However, more recent machines rely instead
+on the @dfn{Unified Extensible Firmware Interface} (UEFI) to boot.  In that
+case, the @code{bootloader} field should contain something along these
+lines:
 
 @example
 (bootloader-configuration
@@ -9622,23 +9696,21 @@ the @code{bootloader} field should contain something 
along these lines:
   (target "/boot/efi"))
 @end example
 
address@hidden Configuration}, for more information on the available
address@hidden, for more information on the available
 configuration options.
 
 @unnumberedsubsubsec Globally-Visible Packages
 
 @vindex %base-packages
-The @code{packages} field lists packages that will be globally visible
-on the system, for all user accounts---i.e., in every user's @code{PATH}
-environment variable---in addition to the per-user profiles
-(@pxref{Invoking guix package}).  The @var{%base-packages} variable
-provides all the tools one would expect for basic user and administrator
-tasks---including the GNU Core Utilities, the GNU Networking Utilities,
-the GNU Zile lightweight text editor, @command{find}, @command{grep},
-etc.  The example above adds address@hidden and OpenSSH to those,
-taken from the @code{(gnu packages screen)} and @code{(gnu packages ssh)}
-modules (@pxref{Package Modules}).  The
address@hidden(list package output)} syntax can be used to add a specific output
+The @code{packages} field lists packages that will be globally visible on
+the system, for all user accounts---i.e., in every user's @code{PATH}
+environment variable---in addition to the per-user profiles (@pxref{Aufruf von 
guix package}).  The @var{%base-packages} variable provides all the tools
+one would expect for basic user and administrator tasks---including the GNU
+Core Utilities, the GNU Networking Utilities, the GNU Zile lightweight text
+editor, @command{find}, @command{grep}, etc.  The example above adds
address@hidden and OpenSSH to those, taken from the @code{(gnu packages
+screen)} and @code{(gnu packages ssh)} modules (@pxref{Paketmodule}).
+The @code{(list package output)} syntax can be used to add a specific output
 of a package:
 
 @lisp
@@ -9652,14 +9724,13 @@ of a package:
 @end lisp
 
 @findex specification->package
-Referring to packages by variable name, like @code{bind} above, has
-the advantage of being unambiguous; it also allows typos and such to be
+Referring to packages by variable name, like @code{bind} above, has the
+advantage of being unambiguous; it also allows typos and such to be
 diagnosed right away as ``unbound variables''.  The downside is that one
 needs to know which module defines which package, and to augment the
address@hidden line accordingly.  To avoid that, one can use
-the @code{specification->package} procedure of the @code{(gnu packages)}
-module, which returns the best package for a given name or name and
-version:
address@hidden line accordingly.  To avoid that, one can use the
address@hidden>package} procedure of the @code{(gnu packages)} module,
+which returns the best package for a given name or name and version:
 
 @lisp
 (use-modules (gnu packages))
@@ -9675,26 +9746,24 @@ version:
 
 @cindex services
 @vindex %base-services
-The @code{services} field lists @dfn{system services} to be made
-available when the system starts (@pxref{Services}).
-The @code{operating-system} declaration above specifies that, in
-addition to the basic services, we want the @command{lshd} secure shell
-daemon listening on port 2222 (@pxref{Networking Services,
address@hidden).  Under the hood,
address@hidden arranges so that @code{lshd} is started with the
-right command-line options, possibly with supporting configuration files
-generated as needed (@pxref{Defining Services}).
+The @code{services} field lists @dfn{system services} to be made available
+when the system starts (@pxref{Dienste}).  The @code{operating-system}
+declaration above specifies that, in addition to the basic services, we want
+the @command{lshd} secure shell daemon listening on port 2222
+(@pxref{Netzwerkdienste, @code{lsh-service}}).  Under the hood,
address@hidden arranges so that @code{lshd} is started with the right
+command-line options, possibly with supporting configuration files generated
+as needed (@pxref{Dienste definieren}).
 
 @cindex customization, of services
 @findex modify-services
 Occasionally, instead of using the base services as is, you will want to
-customize them.  To do this, use @code{modify-services} (@pxref{Service
-Reference, @code{modify-services}}) to modify the list.
+customize them.  To do this, use @code{modify-services} 
(@pxref{Service-Referenz, @code{modify-services}}) to modify the list.
 
-For example, suppose you want to modify @code{guix-daemon} and Mingetty
-(the console log-in) in the @var{%base-services} list (@pxref{Base
-Services, @code{%base-services}}).  To do that, you can write the
-following in your operating system declaration:
+For example, suppose you want to modify @code{guix-daemon} and Mingetty (the
+console log-in) in the @var{%base-services} list (@pxref{Basisdienste,
address@hidden).  To do that, you can write the following in your
+operating system declaration:
 
 @lisp
 (define %my-services
@@ -9718,44 +9787,44 @@ This changes the configuration---i.e., the service 
parameters---of the
 @code{guix-service-type} instance, and that of all the
 @code{mingetty-service-type} instances in the @var{%base-services} list.
 Observe how this is accomplished: first, we arrange for the original
-configuration to be bound to the identifier @code{config} in the
address@hidden, and then we write the @var{body} so that it evaluates to the
-desired configuration.  In particular, notice how we use @code{inherit}
-to create a new configuration which has the same values as the old
-configuration, but with a few modifications.
+configuration to be bound to the identifier @code{config} in the @var{body},
+and then we write the @var{body} so that it evaluates to the desired
+configuration.  In particular, notice how we use @code{inherit} to create a
+new configuration which has the same values as the old configuration, but
+with a few modifications.
 
 @cindex encrypted disk
-The configuration for a typical ``desktop'' usage, with an encrypted
-root partition, the X11 display
-server, GNOME and Xfce (users can choose which of these desktop
-environments to use at the log-in screen by pressing @kbd{F1}), network
-management, power management, and more, would look like this:
+The configuration for a typical ``desktop'' usage, with an encrypted root
+partition, the X11 display server, GNOME and Xfce (users can choose which of
+these desktop environments to use at the log-in screen by pressing
address@hidden), network management, power management, and more, would look like
+this:
 
 @lisp
 @include os-config-desktop.texi
 @end lisp
 
-A graphical system with a choice of lightweight window managers
-instead of full-blown desktop environments would look like this:
+A graphical system with a choice of lightweight window managers instead of
+full-blown desktop environments would look like this:
 
 @lisp
 @include os-config-lightweight-desktop.texi
 @end lisp
 
 This example refers to the @file{/boot/efi} file system by its UUID,
address@hidden  Replace this UUID with the right UUID on your system,
-as returned by the @command{blkid} command.
address@hidden  Replace this UUID with the right UUID on your system, as
+returned by the @command{blkid} command.
 
address@hidden Services}, for the exact list of services provided by
address@hidden  @xref{X.509 Certificates}, for background
address@hidden, for the exact list of services provided by
address@hidden  @xref{X.509-Zertifikate}, for background
 information about the @code{nss-certs} package that is used here.
 
-Again, @var{%desktop-services} is just a list of service objects.  If
-you want to remove services from there, you can do so using the
-procedures for list filtering (@pxref{SRFI-1 Filtering and
-Partitioning,,, guile, GNU Guile Reference Manual}).  For instance, the
-following expression returns a list that contains all the services in
address@hidden minus the Avahi service:
+Again, @var{%desktop-services} is just a list of service objects.  If you
+want to remove services from there, you can do so using the procedures for
+list filtering (@pxref{SRFI-1 Filtering and Partitioning,,, guile, GNU Guile
+Reference Manual}).  For instance, the following expression returns a list
+that contains all the services in @var{%desktop-services} minus the Avahi
+service:
 
 @example
 (remove (lambda (service)
@@ -9765,68 +9834,63 @@ following expression returns a list that contains all 
the services in
 
 @unnumberedsubsubsec Instantiating the System
 
-Assuming the @code{operating-system} declaration
-is stored in the @file{my-system-config.scm}
-file, the @command{guix system reconfigure my-system-config.scm} command
-instantiates that configuration, and makes it the default GRUB boot
-entry (@pxref{Invoking guix system}).
+Assuming the @code{operating-system} declaration is stored in the
address@hidden file, the @command{guix system reconfigure
+my-system-config.scm} command instantiates that configuration, and makes it
+the default GRUB boot entry (@pxref{Aufruf von guix system}).
 
-The normal way to change the system configuration is by updating this
-file and re-running @command{guix system reconfigure}.  One should never
-have to touch files in @file{/etc} or to run commands that modify the
-system state such as @command{useradd} or @command{grub-install}.  In
-fact, you must avoid that since that would not only void your warranty
-but also prevent you from rolling back to previous versions of your
-system, should you ever need to.
+The normal way to change the system configuration is by updating this file
+and re-running @command{guix system reconfigure}.  One should never have to
+touch files in @file{/etc} or to run commands that modify the system state
+such as @command{useradd} or @command{grub-install}.  In fact, you must
+avoid that since that would not only void your warranty but also prevent you
+from rolling back to previous versions of your system, should you ever need
+to.
 
 @cindex roll-back, of the operating system
-Speaking of roll-back, each time you run @command{guix system
-reconfigure}, a new @dfn{generation} of the system is created---without
-modifying or deleting previous generations.  Old system generations get
-an entry in the bootloader boot menu, allowing you to boot them in case
-something went wrong with the latest generation.  Reassuring, no?  The
address@hidden system list-generations} command lists the system
-generations available on disk.  It is also possible to roll back the
-system via the commands @command{guix system roll-back} and
address@hidden system switch-generation}.
+Speaking of roll-back, each time you run @command{guix system reconfigure},
+a new @dfn{generation} of the system is created---without modifying or
+deleting previous generations.  Old system generations get an entry in the
+bootloader boot menu, allowing you to boot them in case something went wrong
+with the latest generation.  Reassuring, no? The @command{guix system
+list-generations} command lists the system generations available on disk.
+It is also possible to roll back the system via the commands @command{guix
+system roll-back} and @command{guix system switch-generation}.
 
 Although the @command{guix system reconfigure} command will not modify
 previous generations, you must take care when the current generation is not
-the latest (e.g., after invoking @command{guix system roll-back}), since
-the operation might overwrite a later generation (@pxref{Invoking guix
-system}).
+the latest (e.g., after invoking @command{guix system roll-back}), since the
+operation might overwrite a later generation (@pxref{Aufruf von guix system}).
 
 @unnumberedsubsubsec The Programming Interface
 
-At the Scheme level, the bulk of an @code{operating-system} declaration
-is instantiated with the following monadic procedure (@pxref{The Store
-Monad}):
+At the Scheme level, the bulk of an @code{operating-system} declaration is
+instantiated with the following monadic procedure (@pxref{Die Store-Monade}):
 
 @deffn {Monadic Procedure} operating-system-derivation os
-Return a derivation that builds @var{os}, an @code{operating-system}
-object (@pxref{Derivations}).
+Return a derivation that builds @var{os}, an @code{operating-system} object
+(@pxref{Ableitungen}).
 
-The output of the derivation is a single directory that refers to all
-the packages, configuration files, and other supporting files needed to
+The output of the derivation is a single directory that refers to all the
+packages, configuration files, and other supporting files needed to
 instantiate @var{os}.
 @end deffn
 
-This procedure is provided by the @code{(gnu system)} module.  Along
-with @code{(gnu services)} (@pxref{Services}), this module contains the
-guts of GuixSD.  Make sure to visit it!
+This procedure is provided by the @code{(gnu system)} module.  Along with
address@hidden(gnu services)} (@pxref{Dienste}), this module contains the guts 
of
+GuixSD.  Make sure to visit it!
 
 
address@hidden operating-system Reference
address@hidden „operating-system“-Referenz
 @subsection @code{operating-system} Reference
 
-This section summarizes all the options available in
address@hidden declarations (@pxref{Using the Configuration
-System}).
+This section summarizes all the options available in @code{operating-system}
+declarations (@pxref{Das Konfigurationssystems nutzen}).
 
 @deftp {Data Type} operating-system
-This is the data type representing an operating system configuration.
-By that, we mean all the global system configuration, not per-user
-configuration (@pxref{Using the Configuration System}).
+This is the data type representing an operating system configuration.  By
+that, we mean all the global system configuration, not per-user
+configuration (@pxref{Das Konfigurationssystems nutzen}).
 
 @table @asis
 @item @code{kernel} (default: @var{linux-libre})
@@ -9835,68 +9899,67 @@ only the Linux-libre kernel is supported.  In the 
future, it will be
 possible to use the address@hidden
 
 @item @code{kernel-arguments} (default: @code{'()})
-List of strings or gexps representing additional arguments to pass on
-the command-line of the kernel---e.g., @code{("console=ttyS0")}.
+List of strings or gexps representing additional arguments to pass on the
+command-line of the kernel---e.g., @code{("console=ttyS0")}.
 
 @item @code{bootloader}
-The system bootloader configuration object.  @xref{Bootloader Configuration}.
+The system bootloader configuration object.  @xref{Bootloader-Konfiguration}.
 
 @item @code{initrd-modules} (default: @code{%base-initrd-modules})
 @cindex initrd
 @cindex initial RAM disk
-The list of Linux kernel modules that need to be available in the
-initial RAM disk.  @xref{Initial RAM Disk}.
+The list of Linux kernel modules that need to be available in the initial
+RAM disk.  @xref{Initiale RAM-Disk}.
 
 @item @code{initrd} (default: @code{base-initrd})
-A monadic procedure that returns an initial RAM disk for the Linux
-kernel.  This field is provided to support low-level customization and
-should rarely be needed for casual use.  @xref{Initial RAM Disk}.
+A monadic procedure that returns an initial RAM disk for the Linux kernel.
+This field is provided to support low-level customization and should rarely
+be needed for casual use.  @xref{Initiale RAM-Disk}.
 
 @item @code{firmware} (default: @var{%base-firmware})
 @cindex firmware
 List of firmware packages loadable by the operating system kernel.
 
-The default includes firmware needed for Atheros- and Broadcom-based
-WiFi devices (Linux-libre modules @code{ath9k} and @code{b43-open},
-respectively).  @xref{Hardware Considerations}, for more info on
-supported hardware.
+The default includes firmware needed for Atheros- and Broadcom-based WiFi
+devices (Linux-libre modules @code{ath9k} and @code{b43-open},
+respectively).  @xref{Hardware-Überlegungen}, for more info on supported
+hardware.
 
 @item @code{host-name}
 The host name.
 
 @item @code{hosts-file}
 @cindex hosts file
-A file-like object (@pxref{G-Expressions, file-like objects}) for use as
address@hidden/etc/hosts} (@pxref{Host Names,,, libc, The GNU C Library
-Reference Manual}).  The default is a file with entries for
address@hidden and @var{host-name}.
+A file-like object (@pxref{G-Ausdrücke, file-like objects}) for use as
address@hidden/etc/hosts} (@pxref{Host Names,,, libc, The GNU C Library 
Reference
+Manual}).  The default is a file with entries for @code{localhost} and
address@hidden
 
 @item @code{mapped-devices} (default: @code{'()})
-A list of mapped devices.  @xref{Mapped Devices}.
+A list of mapped devices.  @xref{Abgebildete Geräte}.
 
 @item @code{file-systems}
-A list of file systems.  @xref{File Systems}.
+A list of file systems.  @xref{Dateisysteme}.
 
 @item @code{swap-devices} (default: @code{'()})
 @cindex swap devices
-A list of strings identifying devices or files to be used for ``swap
-space'' (@pxref{Memory Concepts,,, libc, The GNU C Library Reference
-Manual}).  For example, @code{'("/dev/sda3")} or @code{'("/swapfile")}.
-It is possible to specify a swap file in a file system on a mapped
-device, provided that the necessary device mapping and file system are
-also specified.  @xref{Mapped Devices} and @ref{File Systems}.
+A list of strings identifying devices or files to be used for ``swap space''
+(@pxref{Memory Concepts,,, libc, The GNU C Library Reference Manual}).  For
+example, @code{'("/dev/sda3")} or @code{'("/swapfile")}.  It is possible to
+specify a swap file in a file system on a mapped device, provided that the
+necessary device mapping and file system are also specified.  
@xref{Abgebildete Geräte} and @ref{Dateisysteme}.
 
 @item @code{users} (default: @code{%base-user-accounts})
 @itemx @code{groups} (default: @var{%base-groups})
-List of user accounts and groups.  @xref{User Accounts}.
+List of user accounts and groups.  @xref{Benutzerkonten}.
 
-If the @code{users} list lacks a user account with address@hidden, a
-``root'' account with address@hidden is automatically added.
+If the @code{users} list lacks a user account with address@hidden, a ``root''
+account with address@hidden is automatically added.
 
 @item @code{skeletons} (default: @code{(default-skeletons)})
-A list target file name/file-like object tuples (@pxref{G-Expressions,
-file-like objects}).  These are the skeleton files that will be added to
-the home directory of newly-created user accounts.
+A list target file name/file-like object tuples (@pxref{G-Ausdrücke,
+file-like objects}).  These are the skeleton files that will be added to the
+home directory of newly-created user accounts.
 
 For instance, a valid value may look like this:
 
@@ -9912,31 +9975,30 @@ A string denoting the contents of the @file{/etc/issue} 
file, which is
 displayed when users log in on a text console.
 
 @item @code{packages} (default: @var{%base-packages})
-The set of packages installed in the global profile, which is accessible
-at @file{/run/current-system/profile}.
+The set of packages installed in the global profile, which is accessible at
address@hidden/run/current-system/profile}.
 
-The default set includes core utilities and it is good practice to
-install non-core utilities in user profiles (@pxref{Invoking guix
-package}).
+The default set includes core utilities and it is good practice to install
+non-core utilities in user profiles (@pxref{Aufruf von guix package}).
 
 @item @code{timezone}
 A timezone identifying string---e.g., @code{"Europe/Paris"}.
 
-You can run the @command{tzselect} command to find out which timezone
-string corresponds to your region.  Choosing an invalid timezone name
-causes @command{guix system} to fail.
+You can run the @command{tzselect} command to find out which timezone string
+corresponds to your region.  Choosing an invalid timezone name causes
address@hidden system} to fail.
 
 @item @code{locale} (default: @code{"en_US.utf8"})
 The name of the default locale (@pxref{Locale Names,,, libc, The GNU C
 Library Reference Manual}).  @xref{Locales}, for more information.
 
 @item @code{locale-definitions} (default: @var{%default-locale-definitions})
-The list of locale definitions to be compiled and that may be used at
-run time.  @xref{Locales}.
+The list of locale definitions to be compiled and that may be used at run
+time.  @xref{Locales}.
 
 @item @code{locale-libcs} (default: @code{(list @var{glibc})})
-The list of address@hidden packages whose locale data and tools are used
-to build the locale definitions.  @xref{Locales}, for compatibility
+The list of address@hidden packages whose locale data and tools are used to
+build the locale definitions.  @xref{Locales}, for compatibility
 considerations that justify this option.
 
 @item @code{name-service-switch} (default: @var{%default-nss})
@@ -9945,38 +10007,36 @@ Configuration of the libc name service switch (NSS)---a
 details.
 
 @item @code{services} (default: @var{%base-services})
-A list of service objects denoting system services.  @xref{Services}.
+A list of service objects denoting system services.  @xref{Dienste}.
 
 @item @code{pam-services} (default: @code{(base-pam-services)})
 @cindex PAM
 @cindex pluggable authentication modules
-Linux @dfn{pluggable authentication module} (PAM) services.
 @c FIXME: Add xref to PAM services section.
+Linux @dfn{pluggable authentication module} (PAM) services.
 
 @item @code{setuid-programs} (default: @var{%setuid-programs})
-List of string-valued G-expressions denoting setuid programs.
address@hidden Programs}.
+List of string-valued G-expressions denoting setuid programs.  
@xref{Setuid-Programme}.
 
 @item @code{sudoers-file} (default: @var{%sudoers-specification})
 @cindex sudoers file
 The contents of the @file{/etc/sudoers} file as a file-like object
-(@pxref{G-Expressions, @code{local-file} and @code{plain-file}}).
+(@pxref{G-Ausdrücke, @code{local-file} and @code{plain-file}}).
 
 This file specifies which users can use the @command{sudo} command, what
-they are allowed to do, and what privileges they may gain.  The default
-is that only @code{root} and members of the @code{wheel} group may use
+they are allowed to do, and what privileges they may gain.  The default is
+that only @code{root} and members of the @code{wheel} group may use
 @code{sudo}.
 
 @end table
 @end deftp
 
address@hidden File Systems
address@hidden File Systems
address@hidden Dateisysteme
address@hidden Dateisysteme
 
 The list of file systems to be mounted is specified in the
address@hidden field of the operating system declaration
-(@pxref{Using the Configuration System}).  Each file system is declared
-using the @code{file-system} form, like this:
address@hidden field of the operating system declaration (@pxref{Das 
Konfigurationssystems nutzen}).  Each file system is declared using the
address@hidden form, like this:
 
 @example
 (file-system
@@ -9989,8 +10049,8 @@ As usual, some of the fields are mandatory---those shown 
in the example
 above---while others can be omitted.  These are described below.
 
 @deftp {Data Type} file-system
-Objects of this type represent file systems to be mounted.  They
-contain the following members:
+Objects of this type represent file systems to be mounted.  They contain the
+following members:
 
 @table @asis
 @item @code{type}
@@ -10003,19 +10063,18 @@ This designates the place where the file system is to 
be mounted.
 @item @code{device}
 This names the ``source'' of the file system.  It can be one of three
 things: a file system label, a file system UUID, or the name of a
address@hidden/dev} node.  Labels and UUIDs offer a way to refer to file
-systems without having to hard-code their actual device
address@hidden that, while it is tempting to use
address@hidden/dev/disk/by-uuid} and similar device names to achieve the same
-result, this is not recommended: These special device nodes are created
-by the udev daemon and may be unavailable at the time the device is
-mounted.}.
address@hidden/dev} node.  Labels and UUIDs offer a way to refer to file systems
+without having to hard-code their actual device address@hidden that,
+while it is tempting to use @file{/dev/disk/by-uuid} and similar device
+names to achieve the same result, this is not recommended: These special
+device nodes are created by the udev daemon and may be unavailable at the
+time the device is mounted.}.
 
 @findex file-system-label
-File system labels are created using the @code{file-system-label}
-procedure, UUIDs are created using @code{uuid}, and @file{/dev} node are
-plain strings.  Here's an example of a file system referred to by its
-label, as shown by the @command{e2label} command:
+File system labels are created using the @code{file-system-label} procedure,
+UUIDs are created using @code{uuid}, and @file{/dev} node are plain
+strings.  Here's an example of a file system referred to by its label, as
+shown by the @command{e2label} command:
 
 @example
 (file-system
@@ -10028,10 +10087,10 @@ label, as shown by the @command{e2label} command:
 UUIDs are converted from their string representation (as shown by the
 @command{tune2fs -l} command) using the @code{uuid} address@hidden
 @code{uuid} form expects 16-byte UUIDs as defined in
address@hidden://tools.ietf.org/html/rfc4122, address@hidden  This is the
-form of UUID used by the ext2 family of file systems and others, but it
-is different from ``UUIDs'' found in FAT file systems, for instance.},
-like this:
address@hidden://tools.ietf.org/html/rfc4122, address@hidden  This is the form
+of UUID used by the ext2 family of file systems and others, but it is
+different from ``UUIDs'' found in FAT file systems, for instance.}, like
+this:
 
 @example
 (file-system
@@ -10040,33 +10099,31 @@ like this:
   (device (uuid "4dab5feb-d176-45de-b287-9b0a6e4c01cb")))
 @end example
 
-When the source of a file system is a mapped device (@pxref{Mapped
-Devices}), its @code{device} field @emph{must} refer to the mapped
-device name---e.g., @file{"/dev/mapper/root-partition"}.
-This is required so that
+When the source of a file system is a mapped device (@pxref{Abgebildete 
Geräte}), its @code{device} field @emph{must} refer to the mapped device
+name---e.g., @file{"/dev/mapper/root-partition"}.  This is required so that
 the system knows that mounting the file system depends on having the
 corresponding device mapping established.
 
 @item @code{flags} (default: @code{'()})
-This is a list of symbols denoting mount flags.  Recognized flags
-include @code{read-only}, @code{bind-mount}, @code{no-dev} (disallow
-access to special files), @code{no-suid} (ignore setuid and setgid
-bits), and @code{no-exec} (disallow program execution.)
+This is a list of symbols denoting mount flags.  Recognized flags include
address@hidden, @code{bind-mount}, @code{no-dev} (disallow access to
+special files), @code{no-suid} (ignore setuid and setgid bits), and
address@hidden (disallow program execution.)
 
 @item @code{options} (default: @code{#f})
 This is either @code{#f}, or a string denoting mount options.
 
 @item @code{mount?} (default: @code{#t})
-This value indicates whether to automatically mount the file system when
-the system is brought up.  When set to @code{#f}, the file system gets
-an entry in @file{/etc/fstab} (read by the @command{mount} command) but
-is not automatically mounted.
+This value indicates whether to automatically mount the file system when the
+system is brought up.  When set to @code{#f}, the file system gets an entry
+in @file{/etc/fstab} (read by the @command{mount} command) but is not
+automatically mounted.
 
 @item @code{needed-for-boot?} (default: @code{#f})
 This Boolean value indicates whether the file system is needed when
-booting.  If that is true, then the file system is mounted when the
-initial RAM disk (initrd) is loaded.  This is always the case, for
-instance, for the root file system.
+booting.  If that is true, then the file system is mounted when the initial
+RAM disk (initrd) is loaded.  This is always the case, for instance, for the
+root file system.
 
 @item @code{check?} (default: @code{#t})
 This Boolean indicates whether the file system needs to be checked for
@@ -10077,47 +10134,43 @@ When true, the mount point is created if it does not 
exist yet.
 
 @item @code{dependencies} (default: @code{'()})
 This is a list of @code{<file-system>} or @code{<mapped-device>} objects
-representing file systems that must be mounted or mapped devices that
-must be opened before (and unmounted or closed after) this one.
+representing file systems that must be mounted or mapped devices that must
+be opened before (and unmounted or closed after) this one.
 
-As an example, consider a hierarchy of mounts: @file{/sys/fs/cgroup} is
-a dependency of @file{/sys/fs/cgroup/cpu} and
address@hidden/sys/fs/cgroup/memory}.
+As an example, consider a hierarchy of mounts: @file{/sys/fs/cgroup} is a
+dependency of @file{/sys/fs/cgroup/cpu} and @file{/sys/fs/cgroup/memory}.
 
 Another example is a file system that depends on a mapped device, for
-example for an encrypted partition (@pxref{Mapped Devices}).
+example for an encrypted partition (@pxref{Abgebildete Geräte}).
 @end table
 @end deftp
 
-The @code{(gnu system file-systems)} exports the following useful
-variables.
+The @code{(gnu system file-systems)} exports the following useful variables.
 
 @defvr {Scheme Variable} %base-file-systems
-These are essential file systems that are required on normal systems,
-such as @var{%pseudo-terminal-file-system} and @var{%immutable-store} (see
-below.)  Operating system declarations should always contain at least
-these.
+These are essential file systems that are required on normal systems, such
+as @var{%pseudo-terminal-file-system} and @var{%immutable-store} (see
+below.)  Operating system declarations should always contain at least these.
 @end defvr
 
 @defvr {Scheme Variable} %pseudo-terminal-file-system
 This is the file system to be mounted as @file{/dev/pts}.  It supports
address@hidden created @i{via} @code{openpty} and similar
-functions (@pxref{Pseudo-Terminals,,, libc, The GNU C Library Reference
-Manual}).  Pseudo-terminals are used by terminal emulators such as
address@hidden
address@hidden created @i{via} @code{openpty} and similar functions
+(@pxref{Pseudo-Terminals,,, libc, The GNU C Library Reference Manual}).
+Pseudo-terminals are used by terminal emulators such as @command{xterm}.
 @end defvr
 
 @defvr {Scheme Variable} %shared-memory-file-system
-This file system is mounted as @file{/dev/shm} and is used to support
-memory sharing across processes (@pxref{Memory-mapped I/O,
address@hidden,, libc, The GNU C Library Reference Manual}).
+This file system is mounted as @file{/dev/shm} and is used to support memory
+sharing across processes (@pxref{Memory-mapped I/O, @code{shm_open},, libc,
+The GNU C Library Reference Manual}).
 @end defvr
 
 @defvr {Scheme Variable} %immutable-store
-This file system performs a read-only ``bind mount'' of
address@hidden/gnu/store}, making it read-only for all the users including
address@hidden  This prevents against accidental modification by software
-running as @code{root} or by system administrators.
+This file system performs a read-only ``bind mount'' of @file{/gnu/store},
+making it read-only for all the users including @code{root}.  This prevents
+against accidental modification by software running as @code{root} or by
+system administrators.
 
 The daemon itself is still able to write to the store: it remounts it
 read-write in its own ``name space.''
@@ -10130,54 +10183,53 @@ executable file types to be delegated to user space.  
This requires the
 @end defvr
 
 @defvr {Scheme Variable} %fuse-control-file-system
-The @code{fusectl} file system, which allows unprivileged users to mount
-and unmount user-space FUSE file systems.  This requires the
address@hidden kernel module to be loaded.
+The @code{fusectl} file system, which allows unprivileged users to mount and
+unmount user-space FUSE file systems.  This requires the @code{fuse.ko}
+kernel module to be loaded.
 @end defvr
 
address@hidden Mapped Devices
address@hidden Mapped Devices
address@hidden Abgebildete Geräte
address@hidden Abgebildete Geräte
 
 @cindex device mapping
 @cindex mapped devices
-The Linux kernel has a notion of @dfn{device mapping}: a block device,
-such as a hard disk partition, can be @dfn{mapped} into another device,
-usually in @code{/dev/mapper/},
-with additional processing over the data that flows through
address@hidden that the address@hidden makes no difference between the
-concept of a ``mapped device'' and that of a file system: both boil down
-to @emph{translating} input/output operations made on a file to
-operations on its backing store.  Thus, the Hurd implements mapped
-devices, like file systems, using the generic @dfn{translator} mechanism
-(@pxref{Translators,,, hurd, The GNU Hurd Reference Manual}).}.  A
-typical example is encryption device mapping: all writes to the mapped
-device are encrypted, and all reads are deciphered, transparently.
-Guix extends this notion by considering any device or set of devices that
-are @dfn{transformed} in some way to create a new device; for instance,
-RAID devices are obtained by @dfn{assembling} several other devices, such
-as hard disks or partitions, into a new one that behaves as one partition.
-Other examples, not yet implemented, are LVM logical volumes.
-
-Mapped devices are declared using the @code{mapped-device} form,
-defined as follows; for examples, see below.
+The Linux kernel has a notion of @dfn{device mapping}: a block device, such
+as a hard disk partition, can be @dfn{mapped} into another device, usually
+in @code{/dev/mapper/}, with additional processing over the data that flows
+through address@hidden that the address@hidden makes no difference between
+the concept of a ``mapped device'' and that of a file system: both boil down
+to @emph{translating} input/output operations made on a file to operations
+on its backing store.  Thus, the Hurd implements mapped devices, like file
+systems, using the generic @dfn{translator} mechanism (@pxref{Translators,,,
+hurd, The GNU Hurd Reference Manual}).}.  A typical example is encryption
+device mapping: all writes to the mapped device are encrypted, and all reads
+are deciphered, transparently.  Guix extends this notion by considering any
+device or set of devices that are @dfn{transformed} in some way to create a
+new device; for instance, RAID devices are obtained by @dfn{assembling}
+several other devices, such as hard disks or partitions, into a new one that
+behaves as one partition.  Other examples, not yet implemented, are LVM
+logical volumes.
+
+Mapped devices are declared using the @code{mapped-device} form, defined as
+follows; for examples, see below.
 
 @deftp {Data Type} mapped-device
-Objects of this type represent device mappings that will be made when
-the system boots up.
+Objects of this type represent device mappings that will be made when the
+system boots up.
 
 @table @code
 @item source
-This is either a string specifying the name of the block device to be mapped,
-such as @code{"/dev/sda3"}, or a list of such strings when several devices
-need to be assembled for creating a new one.
+This is either a string specifying the name of the block device to be
+mapped, such as @code{"/dev/sda3"}, or a list of such strings when several
+devices need to be assembled for creating a new one.
 
 @item target
-This string specifies the name of the resulting mapped device.  For
-kernel mappers such as encrypted devices of type @code{luks-device-mapping},
-specifying @code{"my-partition"} leads to the creation of
-the @code{"/dev/mapper/my-partition"} device.
-For RAID devices of type @code{raid-device-mapping}, the full device name
-such as @code{"/dev/md0"} needs to be given.
+This string specifies the name of the resulting mapped device.  For kernel
+mappers such as encrypted devices of type @code{luks-device-mapping},
+specifying @code{"my-partition"} leads to the creation of the
address@hidden"/dev/mapper/my-partition"} device.  For RAID devices of type
address@hidden, the full device name such as @code{"/dev/md0"}
+needs to be given.
 
 @item type
 This must be a @code{mapped-device-kind} object, which specifies how
@@ -10203,10 +10255,9 @@ for RAID-4, RAID-5 or RAID-6, or @code{raid10} for 
RAID-10.
 The following example specifies a mapping from @file{/dev/sda3} to
 @file{/dev/mapper/home} using LUKS---the
 @url{https://gitlab.com/cryptsetup/cryptsetup,Linux Unified Key Setup}, a
-standard mechanism for disk encryption.
-The @file{/dev/mapper/home}
-device can then be used as the @code{device} of a @code{file-system}
-declaration (@pxref{File Systems}).
+standard mechanism for disk encryption.  The @file{/dev/mapper/home} device
+can then be used as the @code{device} of a @code{file-system} declaration
+(@pxref{Dateisysteme}).
 
 @example
 (mapped-device
@@ -10215,9 +10266,8 @@ declaration (@pxref{File Systems}).
   (type luks-device-mapping))
 @end example
 
-Alternatively, to become independent of device numbering, one may obtain
-the LUKS UUID (@dfn{unique identifier}) of the source device by a
-command like:
+Alternatively, to become independent of device numbering, one may obtain the
+LUKS UUID (@dfn{unique identifier}) of the source device by a command like:
 
 @example
 cryptsetup luksUUID /dev/sda3
@@ -10234,10 +10284,9 @@ and use it as follows:
 
 @cindex swap encryption
 It is also desirable to encrypt swap space, since swap space may contain
-sensitive data.  One way to accomplish that is to use a swap file in a
-file system on a device mapped via LUKS encryption.  In this way, the
-swap file is encrypted because the entire device is encrypted.
address@hidden for Installation,,Disk Partitioning}, for an example.
+sensitive data.  One way to accomplish that is to use a swap file in a file
+system on a device mapped via LUKS encryption.  In this way, the swap file
+is encrypted because the entire device is encrypted.  @xref{Vor der 
Installation,,Disk Partitioning}, for an example.
 
 A RAID device formed of the partitions @file{/dev/sda1} and @file{/dev/sdb1}
 may be declared as follows:
@@ -10250,14 +10299,13 @@ may be declared as follows:
 @end example
 
 The @file{/dev/md0} device can then be used as the @code{device} of a
address@hidden declaration (@pxref{File Systems}).
-Note that the RAID level need not be given; it is chosen during the
-initial creation and formatting of the RAID device and is determined
-automatically later.
address@hidden declaration (@pxref{Dateisysteme}).  Note that the RAID
+level need not be given; it is chosen during the initial creation and
+formatting of the RAID device and is determined automatically later.
 
 
address@hidden User Accounts
address@hidden User Accounts
address@hidden Benutzerkonten
address@hidden Benutzerkonten
 
 @cindex users
 @cindex accounts
@@ -10278,17 +10326,17 @@ User accounts and groups are entirely managed through 
the
   (home-directory "/home/alice"))
 @end example
 
-When booting or upon completion of @command{guix system reconfigure},
-the system ensures that only the user accounts and groups specified in
-the @code{operating-system} declaration exist, and with the specified
+When booting or upon completion of @command{guix system reconfigure}, the
+system ensures that only the user accounts and groups specified in the
address@hidden declaration exist, and with the specified
 properties.  Thus, account or group creations or modifications made by
 directly invoking commands such as @command{useradd} are lost upon
-reconfiguration or reboot.  This ensures that the system remains exactly
-as declared.
+reconfiguration or reboot.  This ensures that the system remains exactly as
+declared.
 
 @deftp {Data Type} user-account
-Objects of this type represent user accounts.  The following members may
-be specified:
+Objects of this type represent user accounts.  The following members may be
+specified:
 
 @table @asis
 @item @code{name}
@@ -10296,17 +10344,17 @@ The name of the user account.
 
 @item @code{group}
 @cindex groups
-This is the name (a string) or identifier (a number) of the user group
-this account belongs to.
+This is the name (a string) or identifier (a number) of the user group this
+account belongs to.
 
 @item @code{supplementary-groups} (default: @code{'()})
-Optionally, this can be defined as a list of group names that this
-account belongs to.
+Optionally, this can be defined as a list of group names that this account
+belongs to.
 
 @item @code{uid} (default: @code{#f})
 This is the user ID for this account (a number), or @code{#f}.  In the
-latter case, a number is automatically chosen by the system when the
-account is created.
+latter case, a number is automatically chosen by the system when the account
+is created.
 
 @item @code{comment} (default: @code{""})
 A comment about the account, such as the account owner's full name.
@@ -10315,31 +10363,30 @@ A comment about the account, such as the account 
owner's full name.
 This is the name of the home directory for the account.
 
 @item @code{create-home-directory?} (default: @code{#t})
-Indicates whether the home directory of this account should be created
-if it does not exist yet.
+Indicates whether the home directory of this account should be created if it
+does not exist yet.
 
 @item @code{shell} (default: Bash)
-This is a G-expression denoting the file name of a program to be used as
-the shell (@pxref{G-Expressions}).
+This is a G-expression denoting the file name of a program to be used as the
+shell (@pxref{G-Ausdrücke}).
 
 @item @code{system?} (default: @code{#f})
-This Boolean value indicates whether the account is a ``system''
-account.  System accounts are sometimes treated specially; for instance,
-graphical login managers do not list them.
+This Boolean value indicates whether the account is a ``system'' account.
+System accounts are sometimes treated specially; for instance, graphical
+login managers do not list them.
 
 @anchor{user-account-password}
 @item @code{password} (default: @code{#f})
-You would normally leave this field to @code{#f}, initialize user
-passwords as @code{root} with the @command{passwd} command, and then let
-users change it with @command{passwd}.  Passwords set with
address@hidden are of course preserved across reboot and
-reconfiguration.
-
-If you @emph{do} want to have a preset password for an account, then
-this field must contain the encrypted password, as a string.
address@hidden,,, libc, The GNU C Library Reference Manual}, for more 
information
-on password encryption, and @ref{Encryption,,, guile, GNU Guile Reference
-Manual}, for information on Guile's @code{crypt} procedure.
+You would normally leave this field to @code{#f}, initialize user passwords
+as @code{root} with the @command{passwd} command, and then let users change
+it with @command{passwd}.  Passwords set with @command{passwd} are of course
+preserved across reboot and reconfiguration.
+
+If you @emph{do} want to have a preset password for an account, then this
+field must contain the encrypted password, as a string.  @xref{crypt,,,
+libc, The GNU C Library Reference Manual}, for more information on password
+encryption, and @ref{Encryption,,, guile, GNU Guile Reference Manual}, for
+information on Guile's @code{crypt} procedure.
 
 @end table
 @end deftp
@@ -10367,57 +10414,56 @@ This Boolean value indicates whether the group is a 
``system'' group.
 System groups have low numerical IDs.
 
 @item @code{password} (default: @code{#f})
-What, user groups can have a password?  Well, apparently yes.  Unless
+What, user groups can have a password? Well, apparently yes.  Unless
 @code{#f}, this field specifies the password of the group.
 
 @end table
 @end deftp
 
-For convenience, a variable lists all the basic user groups one may
-expect:
+For convenience, a variable lists all the basic user groups one may expect:
 
 @defvr {Scheme Variable} %base-groups
-This is the list of basic user groups that users and/or packages expect
-to be present on the system.  This includes groups such as ``root'',
-``wheel'', and ``users'', as well as groups used to control access to
-specific devices such as ``audio'', ``disk'', and ``cdrom''.
+This is the list of basic user groups that users and/or packages expect to
+be present on the system.  This includes groups such as ``root'', ``wheel'',
+and ``users'', as well as groups used to control access to specific devices
+such as ``audio'', ``disk'', and ``cdrom''.
 @end defvr
 
 @defvr {Scheme Variable} %base-user-accounts
-This is the list of basic system accounts that programs may expect to
-find on a GNU/Linux system, such as the ``nobody'' account.
+This is the list of basic system accounts that programs may expect to find
+on a GNU/Linux system, such as the ``nobody'' account.
 
-Note that the ``root'' account is not included here.  It is a
-special-case and is automatically added whether or not it is specified.
+Note that the ``root'' account is not included here.  It is a special-case
+and is automatically added whether or not it is specified.
 @end defvr
 
 @node Locales
 @subsection Locales
 
 @cindex locale
-A @dfn{locale} defines cultural conventions for a particular language
-and region of the world (@pxref{Locales,,, libc, The GNU C Library
-Reference Manual}).  Each locale has a name that typically has the form
+A @dfn{locale} defines cultural conventions for a particular language and
+region of the world (@pxref{Locales,,, libc, The GNU C Library Reference
+Manual}).  Each locale has a name that typically has the form
 @address@hidden@address@hidden,
 @code{fr_LU.utf8} designates the locale for the French language, with
 cultural conventions from Luxembourg, and using the UTF-8 encoding.
 
 @cindex locale definition
-Usually, you will want to specify the default locale for the machine
-using the @code{locale} field of the @code{operating-system} declaration
-(@pxref{operating-system Reference, @code{locale}}).
+Usually, you will want to specify the default locale for the machine using
+the @code{locale} field of the @code{operating-system} declaration
+(@pxref{„operating-system“-Referenz, @code{locale}}).
 
-The selected locale is automatically added to the @dfn{locale
-definitions} known to the system if needed, with its codeset inferred
-from its name---e.g., @code{bo_CN.utf8} will be assumed to use the
address@hidden codeset.  Additional locale definitions can be specified in
-the @code{locale-definitions} slot of @code{operating-system}---this is
-useful, for instance, if the codeset could not be inferred from the
-locale name.  The default set of locale definitions includes some widely
-used locales, but not all the available locales, in order to save space.
+The selected locale is automatically added to the @dfn{locale definitions}
+known to the system if needed, with its codeset inferred from its
+name---e.g., @code{bo_CN.utf8} will be assumed to use the @code{UTF-8}
+codeset.  Additional locale definitions can be specified in the
address@hidden slot of @code{operating-system}---this is useful,
+for instance, if the codeset could not be inferred from the locale name.
+The default set of locale definitions includes some widely used locales, but
+not all the available locales, in order to save space.
 
-For instance, to add the North Frisian locale for Germany, the value of
-that field may be:
+For instance, to add the North Frisian locale for Germany, the value of that
+field may be:
 
 @example
 (cons (locale-definition
@@ -10425,8 +10471,8 @@ that field may be:
       %default-locale-definitions)
 @end example
 
-Likewise, to save space, one might want @code{locale-definitions} to
-list only the locales that are actually used, as in:
+Likewise, to save space, one might want @code{locale-definitions} to list
+only the locales that are actually used, as in:
 
 @example
 (list (locale-definition
@@ -10436,11 +10482,11 @@ list only the locales that are actually used, as in:
 
 @vindex LOCPATH
 The compiled locale definitions are available at
address@hidden/run/current-system/locale/X.Y}, where @code{X.Y} is the libc
-version, which is the default location where the address@hidden provided
-by Guix looks for locale data.  This can be overridden using the
address@hidden environment variable (@pxref{locales-and-locpath,
address@hidden and locale packages}).
address@hidden/run/current-system/locale/X.Y}, where @code{X.Y} is the libc 
version,
+which is the default location where the address@hidden provided by Guix looks
+for locale data.  This can be overridden using the @code{LOCPATH}
+environment variable (@pxref{locales-and-locpath, @code{LOCPATH} and locale
+packages}).
 
 The @code{locale-definition} form is provided by the @code{(gnu system
 locale)} module.  Details are given below.
@@ -10460,63 +10506,58 @@ The name of the source for that locale.  This is 
typically the
 
 @item @code{charset} (default: @code{"UTF-8"})
 The ``character set'' or ``code set'' for that locale,
address@hidden://www.iana.org/assignments/character-sets, as defined by
-IANA}.
address@hidden://www.iana.org/assignments/character-sets, as defined by IANA}.
 
 @end table
 @end deftp
 
 @defvr {Scheme Variable} %default-locale-definitions
-A list of commonly used UTF-8 locales, used as the default
-value of the @code{locale-definitions} field of @code{operating-system}
-declarations.
+A list of commonly used UTF-8 locales, used as the default value of the
address@hidden field of @code{operating-system} declarations.
 
 @cindex locale name
 @cindex normalized codeset in locale names
-These locale definitions use the @dfn{normalized codeset} for the part
-that follows the dot in the name (@pxref{Using gettextized software,
-normalized codeset,, libc, The GNU C Library Reference Manual}).  So for
-instance it has @code{uk_UA.utf8} but @emph{not}, say,
address@hidden
+These locale definitions use the @dfn{normalized codeset} for the part that
+follows the dot in the name (@pxref{Using gettextized software, normalized
+codeset,, libc, The GNU C Library Reference Manual}).  So for instance it
+has @code{uk_UA.utf8} but @emph{not}, say, @code{uk_UA.UTF-8}.
 @end defvr
 
 @subsubsection Locale Data Compatibility Considerations
 
 @cindex incompatibility, of locale data
address@hidden declarations provide a @code{locale-libcs} field
-to specify the address@hidden packages that are used to compile locale
-declarations (@pxref{operating-system Reference}).  ``Why would I
-care?'', you may ask.  Well, it turns out that the binary format of
-locale data is occasionally incompatible from one libc version to
-another.
address@hidden declarations provide a @code{locale-libcs} field to
+specify the address@hidden packages that are used to compile locale
+declarations (@pxref{„operating-system“-Referenz}).  ``Why would I care?'',
+you may ask.  Well, it turns out that the binary format of locale data is
+occasionally incompatible from one libc version to another.
 
 @c See <https://sourceware.org/ml/libc-alpha/2015-09/msg00575.html>
 @c and <https://lists.gnu.org/archive/html/guix-devel/2015-08/msg00737.html>.
-For instance, a program linked against libc version 2.21 is unable to
-read locale data produced with libc 2.22; worse, that program
address@hidden instead of simply ignoring the incompatible locale
address@hidden 2.23 and later of address@hidden will simply skip
-the incompatible locale data, which is already an improvement.}.
-Similarly, a program linked against libc 2.22 can read most, but not
-all, of the locale data from libc 2.21 (specifically, @code{LC_COLLATE}
-data is incompatible); thus calls to @code{setlocale} may fail, but
-programs will not abort.
+For instance, a program linked against libc version 2.21 is unable to read
+locale data produced with libc 2.22; worse, that program @emph{aborts}
+instead of simply ignoring the incompatible locale address@hidden
+2.23 and later of address@hidden will simply skip the incompatible locale
+data, which is already an improvement.}.  Similarly, a program linked
+against libc 2.22 can read most, but not all, of the locale data from libc
+2.21 (specifically, @code{LC_COLLATE} data is incompatible); thus calls to
address@hidden may fail, but programs will not abort.
 
 The ``problem'' in GuixSD is that users have a lot of freedom: They can
-choose whether and when to upgrade software in their profiles, and might
-be using a libc version different from the one the system administrator
-used to build the system-wide locale data.
+choose whether and when to upgrade software in their profiles, and might be
+using a libc version different from the one the system administrator used to
+build the system-wide locale data.
 
-Fortunately, unprivileged users can also install their own locale data
-and define @var{GUIX_LOCPATH} accordingly (@pxref{locales-and-locpath,
+Fortunately, unprivileged users can also install their own locale data and
+define @var{GUIX_LOCPATH} accordingly (@pxref{locales-and-locpath,
 @code{GUIX_LOCPATH} and locale packages}).
 
 Still, it is best if the system-wide locale data at
 @file{/run/current-system/locale} is built for all the libc versions
-actually in use on the system, so that all the programs can access
-it---this is especially crucial on a multi-user system.  To do that, the
-administrator can specify several libc packages in the
address@hidden field of @code{operating-system}:
+actually in use on the system, so that all the programs can access it---this
+is especially crucial on a multi-user system.  To do that, the administrator
+can specify several libc packages in the @code{locale-libcs} field of
address@hidden:
 
 @example
 (use-package-modules base)
@@ -10526,27 +10567,25 @@ administrator can specify several libc packages in the
   (locale-libcs (list glibc-2.21 (canonical-package glibc))))
 @end example
 
-This example would lead to a system containing locale definitions for
-both libc 2.21 and the current version of libc in
+This example would lead to a system containing locale definitions for both
+libc 2.21 and the current version of libc in
 @file{/run/current-system/locale}.
 
 
address@hidden Services
address@hidden Services
address@hidden Dienste
address@hidden Dienste
 
 @cindex system services
 An important part of preparing an @code{operating-system} declaration is
-listing @dfn{system services} and their configuration (@pxref{Using the
-Configuration System}).  System services are typically daemons launched
-when the system boots, or other actions needed at that time---e.g.,
-configuring network access.
+listing @dfn{system services} and their configuration (@pxref{Das 
Konfigurationssystems nutzen}).  System services are typically daemons launched 
when
+the system boots, or other actions needed at that time---e.g., configuring
+network access.
 
-GuixSD has a broad definition of ``service'' (@pxref{Service
-Composition}), but many services are managed by the address@hidden
-(@pxref{Shepherd Services}).  On a running system, the @command{herd}
-command allows you to list the available services, show their status,
-start and stop them, or do other specific operations (@pxref{Jump
-Start,,, shepherd, The GNU Shepherd Manual}).  For example:
+GuixSD has a broad definition of ``service'' (@pxref{Dienstkompositionen}),
+but many services are managed by the address@hidden 
(@pxref{Shepherd-Dienste}).  On a running system, the @command{herd} command 
allows you to
+list the available services, show their status, start and stop them, or do
+other specific operations (@pxref{Jump Start,,, shepherd, The GNU Shepherd
+Manual}).  For example:
 
 @example
 # herd status
@@ -10561,9 +10600,9 @@ service:
 Run libc's name service cache daemon (nscd).
 @end example
 
-The @command{start}, @command{stop}, and @command{restart} sub-commands
-have the effect you would expect.  For instance, the commands below stop
-the nscd service and restart the Xorg display server:
+The @command{start}, @command{stop}, and @command{restart} sub-commands have
+the effect you would expect.  For instance, the commands below stop the nscd
+service and restart the Xorg display server:
 
 @example
 # herd stop nscd
@@ -10573,57 +10612,54 @@ Service xorg-server has been stopped.
 Service xorg-server has been started.
 @end example
 
-The following sections document the available services, starting with
-the core services, that may be used in an @code{operating-system}
-declaration.
+The following sections document the available services, starting with the
+core services, that may be used in an @code{operating-system} declaration.
 
 @menu
-* Base Services::               Essential system services.
-* Scheduled Job Execution::     The mcron service.
-* Log Rotation::                The rottlog service.
-* Networking Services::         Network setup, SSH daemon, etc.
-* X Window::                    Graphical display.
-* Printing Services::           Local and remote printer support.
-* Desktop Services::            D-Bus and desktop services.
-* Sound Services::              ALSA and Pulseaudio services.
-* Database Services::           SQL databases, key-value stores, etc.
-* Mail Services::               IMAP, POP3, SMTP, and all that.
-* Messaging Services::          Messaging services.
-* Telephony Services::          Telephony services.
-* Monitoring Services::         Monitoring services.
-* Kerberos Services::           Kerberos services.
-* Web Services::                Web servers.
-* Certificate Services::        TLS certificates via Let's Encrypt.
-* DNS Services::                DNS daemons.
-* VPN Services::                VPN daemons.
-* Network File System::         NFS related services.
-* Continuous Integration::      The Cuirass service.
-* Power Management Services::   Extending battery life.
-* Audio Services::              The MPD.
-* Virtualization Services::     Virtualization services.
-* Version Control Services::    Providing remote access to Git repositories.
-* Game Services::               Game servers.
-* Miscellaneous Services::      Other services.
+* Basisdienste::             Essenzielle Systemdienste
+* Geplante Auftragsausführung::  Der mcron-Dienst.
+* Log-Rotation::             Der rottlog-Dienst.
+* Netzwerkdienste::          Netzwerkeinrichtung, SSH-Daemon etc.
+* X Window::                 Graphische Anzeige.
+* Druckdienste::             Unterstützung für lokale und entfernte 
+                               Drucker.
+* Desktop-Dienste::          D-Bus- und Desktop-Dienste.
+* Tondienste::               Dienste für ALSA und Pulseaudio.
+* Datenbankdienste::         SQL-Datenbanken, Schlüssel-Wert-Speicher etc.
+* Mail-Dienste::             IMAP, POP3, SMTP und so weiter.
+* Kurznachrichtendienste::   Dienste für Kurznachrichten.
+* Telefondienste::           Telefoniedienste.
+* Überwachungsdienste::     Dienste zur Systemüberwachung.
+* Kerberos-Dienste::         Kerberos-Dienste.
+* Web-Dienste::              Web-Server.
+* Zertifikatsdienste::       TLS-Zertifikate via Let’s Encrypt.
+* DNS-Dienste::              DNS-Daemons.
+* VPN-Dienste::              VPN-Daemons.
+* Network File System::      Dienste mit Bezug zum Netzwerkdateisystem.
+* Kontinuierliche Integration::  Der Cuirass-Dienst
+* Power Management Services::  Extending battery life.
+* Audio-Dienste::            Der MPD.
+* Virtualisierungsdienste::  Dienste für virtuelle Maschinen.
+* Versionskontrolldienste::  Entfernten Zugang zu Git-Repositorys bieten.
+* Spieldienste::             Spielserver.
+* Verschiedene Dienste::     Andere Dienste.
 @end menu
 
address@hidden Base Services
address@hidden Base Services
address@hidden Basisdienste
address@hidden Basisdienste
 
 The @code{(gnu services base)} module provides definitions for the basic
-services that one expects from the system.  The services exported by
-this module are listed below.
+services that one expects from the system.  The services exported by this
+module are listed below.
 
 @defvr {Scheme Variable} %base-services
-This variable contains a list of basic services (@pxref{Service Types
-and Services}, for more information on service objects) one would
-expect from the system: a login service (mingetty) on each tty, syslogd,
-the libc name service cache daemon (nscd), the udev device manager, and
-more.
+This variable contains a list of basic services (@pxref{Diensttypen und 
Dienste}, for more information on service objects) one would expect from
+the system: a login service (mingetty) on each tty, syslogd, the libc name
+service cache daemon (nscd), the udev device manager, and more.
 
 This is the default value of the @code{services} field of
address@hidden declarations.  Usually, when customizing a
-system, you will want to append services to @var{%base-services}, like
-this:
address@hidden declarations.  Usually, when customizing a system,
+you will want to append services to @var{%base-services}, like this:
 
 @example
 (cons* (avahi-service) (lsh-service) %base-services)
@@ -10631,12 +10667,12 @@ this:
 @end defvr
 
 @defvr {Scheme Variable} special-files-service-type
-This is the service that sets up ``special files'' such as
address@hidden/bin/sh}; an instance of it is part of @code{%base-services}.
+This is the service that sets up ``special files'' such as @file{/bin/sh};
+an instance of it is part of @code{%base-services}.
 
-The value associated with @code{special-files-service-type} services
-must be a list of tuples where the first element is the ``special file''
-and the second element is its target.  By default it is:
+The value associated with @code{special-files-service-type} services must be
+a list of tuples where the first element is the ``special file'' and the
+second element is its target.  By default it is:
 
 @cindex @file{/bin/sh}
 @cindex @file{sh}, in @file{/bin}
@@ -10646,8 +10682,8 @@ and the second element is its target.  By default it is:
 
 @cindex @file{/usr/bin/env}
 @cindex @file{env}, in @file{/usr/bin}
-If you want to add, say, @code{/usr/bin/env} to your system, you can
-change it to:
+If you want to add, say, @code{/usr/bin/env} to your system, you can change
+it to:
 
 @example
 `(("/bin/sh" ,(file-append @var{bash} "/bin/sh"))
@@ -10655,18 +10691,15 @@ change it to:
 @end example
 
 Since this is part of @code{%base-services}, you can use
address@hidden to customize the set of special files
-(@pxref{Service Reference, @code{modify-services}}).  But the simple way
-to add a special file is @i{via} the @code{extra-special-file} procedure
-(see below.)
address@hidden to customize the set of special files (@pxref{Service-Referenz, 
@code{modify-services}}).  But the simple way to add a special
+file is @i{via} the @code{extra-special-file} procedure (see below.)
 @end defvr
 
 @deffn {Scheme Procedure} extra-special-file @var{file} @var{target}
 Use @var{target} as the ``special file'' @var{file}.
 
-For example, adding the following lines to the @code{services} field of
-your operating system declaration leads to a @file{/usr/bin/env}
-symlink:
+For example, adding the following lines to the @code{services} field of your
+operating system declaration leads to a @file{/usr/bin/env} symlink:
 
 @example
 (extra-special-file "/usr/bin/env"
@@ -10702,8 +10735,8 @@ the 'root' account has just been created.
 
 @deffn {Scheme Procedure} mingetty-service @var{config}
 Return a service to run mingetty according to @var{config}, a
address@hidden<mingetty-configuration>} object, which specifies the tty to run, 
among
-other things.
address@hidden<mingetty-configuration>} object, which specifies the tty to run,
+among other things.
 @end deffn
 
 @deftp {Data Type} mingetty-configuration
@@ -10716,18 +10749,18 @@ provides the default implementation of virtual 
console log-in.
 The name of the console this Mingetty runs on---e.g., @code{"tty1"}.
 
 @item @code{auto-login} (default: @code{#f})
-When true, this field must be a string denoting the user name under
-which the system automatically logs in.  When it is @code{#f}, a
-user name and password must be entered to log in.
+When true, this field must be a string denoting the user name under which
+the system automatically logs in.  When it is @code{#f}, a user name and
+password must be entered to log in.
 
 @item @code{login-program} (default: @code{#f})
-This must be either @code{#f}, in which case the default log-in program
-is used (@command{login} from the Shadow tool suite), or a gexp denoting
-the name of the log-in program.
+This must be either @code{#f}, in which case the default log-in program is
+used (@command{login} from the Shadow tool suite), or a gexp denoting the
+name of the log-in program.
 
 @item @code{login-pause?} (default: @code{#f})
-When set to @code{#t} in conjunction with @var{auto-login}, the user
-will have to press a key before the log-in shell is launched.
+When set to @code{#t} in conjunction with @var{auto-login}, the user will
+have to press a key before the log-in shell is launched.
 
 @item @code{mingetty} (default: @var{mingetty})
 The Mingetty package to use.
@@ -10737,49 +10770,47 @@ The Mingetty package to use.
 
 @deffn {Scheme Procedure} agetty-service @var{config}
 Return a service to run agetty according to @var{config}, an
address@hidden<agetty-configuration>} object, which specifies the tty to run,
-among other things.
address@hidden<agetty-configuration>} object, which specifies the tty to run, 
among
+other things.
 @end deffn
 
 @deftp {Data Type} agetty-configuration
 This is the data type representing the configuration of agetty, which
-implements virtual and serial console log-in.  See the @code{agetty(8)}
-man page for more information.
+implements virtual and serial console log-in.  See the @code{agetty(8)} man
+page for more information.
 
 @table @asis
 
 @item @code{tty}
 The name of the console this agetty runs on, as a string---e.g.,
address@hidden"ttyS0"}. This argument is optional, it will default to
-a reasonable default serial port used by the kernel Linux.
address@hidden"ttyS0"}. This argument is optional, it will default to a 
reasonable
+default serial port used by the kernel Linux.
 
 For this, if there is a value for an option @code{agetty.tty} in the kernel
-command line, agetty will extract the device name of the serial port
-from it and use that.
+command line, agetty will extract the device name of the serial port from it
+and use that.
 
 If not and if there is a value for an option @code{console} with a tty in
-the Linux command line, agetty will extract the device name of the
-serial port from it and use that.
+the Linux command line, agetty will extract the device name of the serial
+port from it and use that.
 
-In both cases, agetty will leave the other serial device settings
-(baud rate etc.) alone---in the hope that Linux pinned them to the
-correct values.
+In both cases, agetty will leave the other serial device settings (baud rate
+etc.) alone---in the hope that Linux pinned them to the correct values.
 
 @item @code{baud-rate} (default: @code{#f})
 A string containing a comma-separated list of one or more baud rates, in
 descending order.
 
 @item @code{term} (default: @code{#f})
-A string containing the value used for the @code{TERM} environment
-variable.
+A string containing the value used for the @code{TERM} environment variable.
 
 @item @code{eight-bits?} (default: @code{#f})
-When @code{#t}, the tty is assumed to be 8-bit clean, and parity detection is
-disabled.
+When @code{#t}, the tty is assumed to be 8-bit clean, and parity detection
+is disabled.
 
 @item @code{auto-login} (default: @code{#f})
-When passed a login name, as a string, the specified user will be logged
-in automatically without prompting for their login name or password.
+When passed a login name, as a string, the specified user will be logged in
+automatically without prompting for their login name or password.
 
 @item @code{no-reset?} (default: @code{#f})
 When @code{#t}, don't reset terminal cflags (control modes).
@@ -10790,42 +10821,41 @@ into the @file{/var/run/utmpx} file.
 
 @item @code{remote?} (default: @code{#f})
 When set to @code{#t} in conjunction with @var{host}, this will add an
address@hidden fakehost option to the command line of the login program
-specified in @var{login-program}.
address@hidden fakehost option to the command line of the login program 
specified
+in @var{login-program}.
 
 @item @code{flow-control?} (default: @code{#f})
 When set to @code{#t}, enable hardware (RTS/CTS) flow control.
 
 @item @code{no-issue?} (default: @code{#f})
-When set to @code{#t}, the contents of the @file{/etc/issue} file will
-not be displayed before presenting the login prompt.
+When set to @code{#t}, the contents of the @file{/etc/issue} file will not
+be displayed before presenting the login prompt.
 
 @item @code{init-string} (default: @code{#f})
-This accepts a string that will be sent to the tty or modem before
-sending anything else.  It can be used to initialize a modem.
+This accepts a string that will be sent to the tty or modem before sending
+anything else.  It can be used to initialize a modem.
 
 @item @code{no-clear?} (default: @code{#f})
-When set to @code{#t}, agetty will not clear the screen before showing
-the login prompt.
+When set to @code{#t}, agetty will not clear the screen before showing the
+login prompt.
 
 @item @code{login-program} (default: (file-append shadow "/bin/login"))
-This must be either a gexp denoting the name of a log-in program, or
-unset, in which case the default value is the @command{login} from the
-Shadow tool suite.
+This must be either a gexp denoting the name of a log-in program, or unset,
+in which case the default value is the @command{login} from the Shadow tool
+suite.
 
 @item @code{local-line} (default: @code{#f})
 Control the CLOCAL line flag.  This accepts one of three symbols as
-arguments, @code{'auto}, @code{'always}, or @code{'never}. If @code{#f},
-the default value chosen by agetty is @code{'auto}.
+arguments, @code{'auto}, @code{'always}, or @code{'never}. If @code{#f}, the
+default value chosen by agetty is @code{'auto}.
 
 @item @code{extract-baud?} (default: @code{#f})
-When set to @code{#t}, instruct agetty to try to extract the baud rate
-from the status messages produced by certain types of modems.
+When set to @code{#t}, instruct agetty to try to extract the baud rate from
+the status messages produced by certain types of modems.
 
 @item @code{skip-login?} (default: @code{#f})
-When set to @code{#t}, do not prompt the user for a login name.  This
-can be used with @var{login-program} field to use non-standard login
-systems.
+When set to @code{#t}, do not prompt the user for a login name.  This can be
+used with @var{login-program} field to use non-standard login systems.
 
 @item @code{no-newline?} (default: @code{#f})
 When set to @code{#t}, do not print a newline before printing the
@@ -10833,10 +10863,10 @@ When set to @code{#t}, do not print a newline before 
printing the
 
 @c Is this dangerous only when used with login-program, or always?
 @item @code{login-options} (default: @code{#f})
-This option accepts a string containing options that are passed to the
-login program.  When used with the @var{login-program}, be aware that a
-malicious user could try to enter a login name containing embedded
-options that could be parsed by the login program.
+This option accepts a string containing options that are passed to the login
+program.  When used with the @var{login-program}, be aware that a malicious
+user could try to enter a login name containing embedded options that could
+be parsed by the login program.
 
 @item @code{login-pause} (default: @code{#f})
 When set to @code{#t}, wait for any key before showing the login prompt.
@@ -10852,34 +10882,31 @@ Use the Linux system call @code{vhangup} to do a 
virtual hangup of the
 specified terminal.
 
 @item @code{keep-baud?} (default: @code{#f})
-When set to @code{#t}, try to keep the existing baud rate.  The baud
-rates from @var{baud-rate} are used when agetty receives a @key{BREAK}
-character.
+When set to @code{#t}, try to keep the existing baud rate.  The baud rates
+from @var{baud-rate} are used when agetty receives a @key{BREAK} character.
 
 @item @code{timeout} (default: @code{#f})
-When set to an integer value, terminate if no user name could be read
-within @var{timeout} seconds.
+When set to an integer value, terminate if no user name could be read within
address@hidden seconds.
 
 @item @code{detect-case?} (default: @code{#f})
 When set to @code{#t}, turn on support for detecting an uppercase-only
-terminal.  This setting will detect a login name containing only
-uppercase letters as indicating an uppercase-only terminal and turn on
-some upper-to-lower case conversions.  Note that this will not support
-Unicode characters.
+terminal.  This setting will detect a login name containing only uppercase
+letters as indicating an uppercase-only terminal and turn on some
+upper-to-lower case conversions.  Note that this will not support Unicode
+characters.
 
 @item @code{wait-cr?} (default: @code{#f})
-When set to @code{#t}, wait for the user or modem to send a
-carriage-return or linefeed character before displaying
address@hidden/etc/issue} or login prompt.  This is typically used with the
address@hidden option.
+When set to @code{#t}, wait for the user or modem to send a carriage-return
+or linefeed character before displaying @file{/etc/issue} or login prompt.
+This is typically used with the @var{init-string} option.
 
 @item @code{no-hints?} (default: @code{#f})
-When set to @code{#t}, do not print hints about Num, Caps, and Scroll
-locks.
+When set to @code{#t}, do not print hints about Num, Caps, and Scroll locks.
 
 @item @code{no-hostname?} (default: @code{#f})
-By default, the hostname is printed.  When this option is set to
address@hidden, no hostname will be shown at all.
+By default, the hostname is printed.  When this option is set to @code{#t},
+no hostname will be shown at all.
 
 @item @code{long-hostname?} (default: @code{#f})
 By default, the hostname is only printed until the first dot.  When this
@@ -10891,17 +10918,17 @@ This option accepts a string of additional characters 
that should be
 interpreted as backspace when the user types their login name.
 
 @item @code{kill-characters} (default: @code{#f})
-This option accepts a string that should be interpreted to mean "ignore
-all previous characters" (also called a "kill" character) when the types
-their login name.
+This option accepts a string that should be interpreted to mean "ignore all
+previous characters" (also called a "kill" character) when the types their
+login name.
 
 @item @code{chdir} (default: @code{#f})
-This option accepts, as a string, a directory path that will be changed
-to before login.
+This option accepts, as a string, a directory path that will be changed to
+before login.
 
 @item @code{delay} (default: @code{#f})
-This options accepts, as an integer, the number of seconds to sleep
-before opening the tty and displaying the login prompt.
+This options accepts, as an integer, the number of seconds to sleep before
+opening the tty and displaying the login prompt.
 
 @item @code{nice} (default: @code{#f})
 This option accepts, as an integer, the nice value with which to run the
@@ -10915,9 +10942,10 @@ command-line arguments to @command{agetty} as a list 
of strings.
 @end deftp
 
 @deffn {Scheme Procedure} kmscon-service-type @var{config}
-Return a service to run 
@uref{https://www.freedesktop.org/wiki/Software/kmscon,kmscon}
-according to @var{config}, a @code{<kmscon-configuration>} object, which
-specifies the tty to run, among other things.
+Return a service to run
address@hidden://www.freedesktop.org/wiki/Software/kmscon,kmscon} according to
address@hidden, a @code{<kmscon-configuration>} object, which specifies the
+tty to run, among other things.
 @end deffn
 
 @deftp {Data Type} kmscon-configuration
@@ -10930,8 +10958,8 @@ implements virtual console log-in.
 The name of the console this Kmscon runs on---e.g., @code{"tty1"}.
 
 @item @code{login-program} (default: @code{#~(string-append #$shadow 
"/bin/login")})
-A gexp denoting the name of the log-in program. The default log-in program is
address@hidden from the Shadow tool suite.
+A gexp denoting the name of the log-in program. The default log-in program
+is @command{login} from the Shadow tool suite.
 
 @item @code{login-arguments} (default: @code{'("-p")})
 A list of arguments to pass to @command{login}.
@@ -10948,15 +10976,14 @@ The Kmscon package to use.
 @cindex name service cache daemon
 @cindex nscd
 @deffn {Scheme Procedure} nscd-service address@hidden [#:glibc glibc] @
-                [#:name-services '()]
-Return a service that runs the libc name service cache daemon (nscd) with the
-given @var{config}---an @code{<nscd-configuration>} object.  @xref{Name
-Service Switch}, for an example.
+                [#:name-services '()] Return a service that runs the libc name 
service cache
+daemon (nscd) with the given @var{config}---an @code{<nscd-configuration>}
+object.  @xref{Name Service Switch}, for an example.
 @end deffn
 
 @defvr {Scheme Variable} %nscd-default-configuration
-This is the default @code{<nscd-configuration>} value (see below) used
-by @code{nscd-service}.  It uses the caches defined by
+This is the default @code{<nscd-configuration>} value (see below) used by
address@hidden  It uses the caches defined by
 @var{%nscd-default-caches}; see below.
 @end defvr
 
@@ -10967,8 +10994,8 @@ configuration.
 @table @asis
 
 @item @code{name-services} (default: @code{'()})
-List of packages denoting @dfn{name services} that must be visible to
-the nscd---e.g., @code{(list @var{nss-mdns})}.
+List of packages denoting @dfn{name services} that must be visible to the
+nscd---e.g., @code{(list @var{nss-mdns})}.
 
 @item @code{glibc} (default: @var{glibc})
 Package object denoting the GNU C Library providing the @command{nscd}
@@ -10983,8 +11010,7 @@ Integer denoting the debugging levels.  Higher numbers 
mean that more
 debugging output is logged.
 
 @item @code{caches} (default: @var{%nscd-default-caches})
-List of @code{<nscd-cache>} objects denoting things to be cached; see
-below.
+List of @code{<nscd-cache>} objects denoting things to be cached; see below.
 
 @end table
 @end deftp
@@ -10995,10 +11021,10 @@ Data type representing a cache database of nscd and 
its parameters.
 @table @asis
 
 @item @code{database}
-This is a symbol representing the name of the database to be cached.
-Valid values are @code{passwd}, @code{group}, @code{hosts}, and
address@hidden, which designate the corresponding NSS database
-(@pxref{NSS Basics,,, libc, The GNU C Library Reference Manual}).
+This is a symbol representing the name of the database to be cached.  Valid
+values are @code{passwd}, @code{group}, @code{hosts}, and @code{services},
+which designate the corresponding NSS database (@pxref{NSS Basics,,, libc,
+The GNU C Library Reference Manual}).
 
 @item @code{positive-time-to-live}
 @itemx @code{negative-time-to-live} (default: @code{20})
@@ -11006,12 +11032,11 @@ A number representing the number of seconds during 
which a positive or
 negative lookup result remains in cache.
 
 @item @code{check-files?} (default: @code{#t})
-Whether to check for updates of the files corresponding to
address@hidden
+Whether to check for updates of the files corresponding to @var{database}.
 
 For instance, when @var{database} is @code{hosts}, setting this flag
-instructs nscd to check for updates in @file{/etc/hosts} and to take
-them into account.
+instructs nscd to check for updates in @file{/etc/hosts} and to take them
+into account.
 
 @item @code{persistent?} (default: @code{#t})
 Whether the cache should be stored persistently on disk.
@@ -11060,20 +11085,20 @@ The syslog configuration file to use.
 @deffn {Scheme Procedure} syslog-service @var{config}
 Return a service that runs a syslog daemon according to @var{config}.
 
address@hidden invocation,,, inetutils, GNU Inetutils}, for more
-information on the configuration file syntax.
address@hidden invocation,,, inetutils, GNU Inetutils}, for more information
+on the configuration file syntax.
 @end deffn
 
 @defvr {Scheme Variable} guix-service-type
 This is the type of the service that runs the build daemon,
address@hidden (@pxref{Invoking guix-daemon}).  Its value must be a
address@hidden (@pxref{Aufruf des guix-daemon}).  Its value must be a
 @code{guix-configuration} record as described below.
 @end defvr
 
 @anchor{guix-configuration-type}
 @deftp {Data Type} guix-configuration
 This data type represents the configuration of the Guix build daemon.
address@hidden guix-daemon}, for more information.
address@hidden des guix-daemon}, for more information.
 
 @table @asis
 @item @code{guix} (default: @var{guix})
@@ -11086,16 +11111,16 @@ Name of the group for build user accounts.
 Number of build user accounts to create.
 
 @item @code{authorize-key?} (default: @code{#t})
address@hidden substitutes, authorization thereof
address@hidden Substitute, deren Autorisierung
 Whether to authorize the substitute keys listed in
 @code{authorized-keys}---by default that of @code{hydra.gnu.org}
-(@pxref{Substitutes}).
+(@pxref{Substitute}).
 
 @vindex %default-authorized-guix-keys
 @item @code{authorized-keys} (default: @var{%default-authorized-guix-keys})
 The list of authorized key files for archive imports, as a list of
-string-valued gexps (@pxref{Invoking guix archive}).  By default, it
-contains that of @code{hydra.gnu.org} (@pxref{Substitutes}).
+string-valued gexps (@pxref{Aufruf von guix archive}).  By default, it
+contains that of @code{hydra.gnu.org} (@pxref{Substitute}).
 
 @item @code{use-substitutes?} (default: @code{#t})
 Whether to use substitutes.
@@ -11117,8 +11142,8 @@ The type of compression used for build logs---one of 
@code{gzip},
 List of extra command-line options for @command{guix-daemon}.
 
 @item @code{log-file} (default: @code{"/var/log/guix-daemon.log"})
-File where @command{guix-daemon}'s standard output and standard error
-are written.
+File where @command{guix-daemon}'s standard output and standard error are
+written.
 
 @item @code{http-proxy} (default: @code{#f})
 The HTTP proxy used for downloading fixed-output derivations and
@@ -11131,18 +11156,18 @@ A directory path where the @command{guix-daemon} will 
perform builds.
 @end deftp
 
 @deffn {Scheme Procedure} udev-service [#:udev @var{eudev} #:rules @code{'()}]
-Run @var{udev}, which populates the @file{/dev} directory dynamically.
-udev rules can be provided as a list of files through the @var{rules}
-variable.  The procedures @var{udev-rule} and @var{file->udev-rule} from
address@hidden(gnu services base)} simplify the creation of such rule files.
+Run @var{udev}, which populates the @file{/dev} directory dynamically.  udev
+rules can be provided as a list of files through the @var{rules} variable.
+The procedures @var{udev-rule} and @var{file->udev-rule} from @code{(gnu
+services base)} simplify the creation of such rule files.
 
 @deffn {Scheme Procedure} udev-rule address@hidden @var{contents}]
-Return a udev-rule file named @var{file-name} containing the rules
-defined by the @var{contents} literal.
+Return a udev-rule file named @var{file-name} containing the rules defined
+by the @var{contents} literal.
 
-In the following example, a rule for a USB device is defined to be
-stored in the file @file{90-usb-thing.rules}.  The rule runs a script
-upon detecting a USB device with a given product identifier.
+In the following example, a rule for a USB device is defined to be stored in
+the file @file{90-usb-thing.rules}.  The rule runs a script upon detecting a
+USB device with a given product identifier.
 
 @example
 (define %example-udev-rule
@@ -11168,8 +11193,8 @@ Here we show how the default @var{udev-service} can be 
extended with it.
 @end example
 
 @deffn {Scheme Procedure} file->udev-rule address@hidden @var{file}]
-Return a udev file named @var{file-name} containing the rules defined
-within @var{file}, a file-like object.
+Return a udev file named @var{file-name} containing the rules defined within
address@hidden, a file-like object.
 
 The following example showcases how we can use an existing rule file.
 
@@ -11198,14 +11223,14 @@ order to extend the udev rules with the definitions 
found under their
 @var{android-udev-rules} package which exists in Guix in the @code{(gnu
 packages android)} module.
 
-The following example shows how to use the @var{android-udev-rules}
-package so that the Android tool @command{adb} can detect devices
-without root privileges.  It also details how to create the
address@hidden group, which is required for the proper functioning of
-the rules defined within the @var{android-udev-rules} package.  To
-create such a group, we must define it both as part of the
address@hidden of our @var{user-account} declaration, as
-well as in the @var{groups} field of the @var{operating-system} record.
+The following example shows how to use the @var{android-udev-rules} package
+so that the Android tool @command{adb} can detect devices without root
+privileges.  It also details how to create the @code{adbusers} group, which
+is required for the proper functioning of the rules defined within the
address@hidden package.  To create such a group, we must define it
+both as part of the @var{supplementary-groups} of our @var{user-account}
+declaration, as well as in the @var{groups} field of the
address@hidden record.
 
 @example
 (use-modules (gnu packages android)  ;for android-udev-rules
@@ -11244,8 +11269,8 @@ readable.
 
 @defvr {Scheme Variable} %random-seed-file
 This is the name of the file where some random bytes are saved by
address@hidden to seed @file{/dev/urandom} when rebooting.
-It defaults to @file{/var/lib/random-seed}.
address@hidden to seed @file{/dev/urandom} when rebooting.  It
+defaults to @file{/var/lib/random-seed}.
 @end defvr
 
 @cindex keymap
@@ -11260,8 +11285,8 @@ keymap, which can be done like this:
 (console-keymap-service "dvorak")
 @end example
 
-Or, for example, for a Swedish keyboard, you may need to combine
-the following keymaps:
+Or, for example, for a Swedish keyboard, you may need to combine the
+following keymaps:
 @example
 (console-keymap-service "se-lat6" "se-fi-lat6")
 @end example
@@ -11276,11 +11301,11 @@ See @code{man loadkeys} for details.
 @defvr {Scheme Variable} gpm-service-type
 This is the type of the service that runs GPM, the @dfn{general-purpose
 mouse daemon}, which provides mouse support to the Linux console.  GPM
-allows users to use the mouse in the console, notably to select, copy,
-and paste text.
+allows users to use the mouse in the console, notably to select, copy, and
+paste text.
 
-The value for services of this type must be a @code{gpm-configuration}
-(see below).  This service is not part of @var{%base-services}.
+The value for services of this type must be a @code{gpm-configuration} (see
+below).  This service is not part of @var{%base-services}.
 @end defvr
 
 @deftp {Data Type} gpm-configuration
@@ -11288,10 +11313,9 @@ Data type representing the configuration of GPM.
 
 @table @asis
 @item @code{options} (default: @code{%default-gpm-options})
-Command-line options passed to @command{gpm}.  The default set of
-options instruct @command{gpm} to listen to mouse events on
address@hidden/dev/input/mice}.  @xref{Command Line,,, gpm, gpm manual}, for
-more information.
+Command-line options passed to @command{gpm}.  The default set of options
+instruct @command{gpm} to listen to mouse events on @file{/dev/input/mice}.
address@hidden Line,,, gpm, gpm manual}, for more information.
 
 @item @code{gpm} (default: @code{gpm})
 The GPM package to use.
@@ -11301,18 +11325,15 @@ The GPM package to use.
 
 @anchor{guix-publish-service-type}
 @deffn {Scheme Variable} guix-publish-service-type
-This is the service type for @command{guix publish} (@pxref{Invoking
-guix publish}).  Its value must be a @code{guix-configuration}
-object, as described below.
+This is the service type for @command{guix publish} (@pxref{Aufruf von guix 
publish}).  Its value must be a @code{guix-configuration} object, as
+described below.
 
 This assumes that @file{/etc/guix} already contains a signing key pair as
-created by @command{guix archive --generate-key} (@pxref{Invoking guix
-archive}).  If that is not the case, the service will fail to start.
+created by @command{guix archive --generate-key} (@pxref{Aufruf von guix 
archive}).  If that is not the case, the service will fail to start.
 @end deffn
 
 @deftp {Data Type} guix-publish-configuration
-Data type representing the configuration of the @code{guix publish}
-service.
+Data type representing the configuration of the @code{guix publish} service.
 
 @table @asis
 @item @code{guix} (default: @code{guix})
@@ -11322,43 +11343,41 @@ The Guix package to use.
 The TCP port to listen for connections.
 
 @item @code{host} (default: @code{"localhost"})
-The host (and thus, network interface) to listen to.  Use
address@hidden"0.0.0.0"} to listen on all the network interfaces.
+The host (and thus, network interface) to listen to.  Use @code{"0.0.0.0"}
+to listen on all the network interfaces.
 
address@hidden @code{compression-level} (default: @code{3})
address@hidden @code{compression-level} (Vorgabe: @code{3})
 The gzip compression level at which substitutes are compressed.  Use
 @code{0} to disable compression altogether, and @code{9} to get the best
 compression ratio at the expense of increased CPU usage.
 
 @item @code{nar-path} (default: @code{"nar"})
-The URL path at which ``nars'' can be fetched.  @xref{Invoking guix
-publish, @code{--nar-path}}, for details.
+The URL path at which ``nars'' can be fetched.  @xref{Aufruf von guix publish,
address@hidden, for details.
 
 @item @code{cache} (default: @code{#f})
 When it is @code{#f}, disable caching and instead generate archives on
 demand.  Otherwise, this should be the name of a directory---e.g.,
 @code{"/var/cache/guix/publish"}---where @command{guix publish} caches
-archives and meta-data ready to be sent.  @xref{Invoking guix publish,
+archives and meta-data ready to be sent.  @xref{Aufruf von guix publish,
 @option{--cache}}, for more information on the tradeoffs involved.
 
 @item @code{workers} (default: @code{#f})
 When it is an integer, this is the number of worker threads used for
-caching; when @code{#f}, the number of processors is used.
address@hidden guix publish, @option{--workers}}, for more information.
+caching; when @code{#f}, the number of processors is used.  @xref{Aufruf von 
guix publish, @option{--workers}}, for more information.
 
 @item @code{ttl} (default: @code{#f})
-When it is an integer, this denotes the @dfn{time-to-live} in seconds
-of the published archives.  @xref{Invoking guix publish, @option{--ttl}},
-for more information.
+When it is an integer, this denotes the @dfn{time-to-live} in seconds of the
+published archives.  @xref{Aufruf von guix publish, @option{--ttl}}, for more
+information.
 @end table
 @end deftp
 
 @anchor{rngd-service}
 @deffn {Scheme Procedure} rngd-service [#:rng-tools @var{rng-tools}] @
-            [#:device "/dev/hwrng"]
-Return a service that runs the @command{rngd} program from @var{rng-tools}
-to add @var{device} to the kernel's entropy pool.  The service will fail if
address@hidden does not exist.
+            [#:device "/dev/hwrng"] Return a service that runs the 
@command{rngd}
+program from @var{rng-tools} to add @var{device} to the kernel's entropy
+pool.  The service will fail if @var{device} does not exist.
 @end deffn
 
 @anchor{pam-limits-service}
@@ -11372,11 +11391,11 @@ to add @var{device} to the kernel's entropy pool.  
The service will fail if
 Return a service that installs a configuration file for the
 @uref{http://linux-pam.org/Linux-PAM-html/sag-pam_limits.html,
 @code{pam_limits} module}.  The procedure optionally takes a list of
address@hidden values, which can be used to specify
address@hidden limits and nice priority limits to user sessions.
address@hidden values, which can be used to specify @code{ulimit}
+limits and nice priority limits to user sessions.
 
-The following limits definition sets two hard and soft limits for all
-login sessions of users in the @code{realtime} group:
+The following limits definition sets two hard and soft limits for all login
+sessions of users in the @code{realtime} group:
 
 @example
 (pam-limits-service
@@ -11385,32 +11404,31 @@ login sessions of users in the @code{realtime} group:
   (pam-limits-entry "@@realtime" 'both 'memlock 'unlimited)))
 @end example
 
-The first entry increases the maximum realtime priority for
-non-privileged processes; the second entry lifts any restriction of the
-maximum address space that can be locked in memory.  These settings are
-commonly used for real-time audio systems.
+The first entry increases the maximum realtime priority for non-privileged
+processes; the second entry lifts any restriction of the maximum address
+space that can be locked in memory.  These settings are commonly used for
+real-time audio systems.
 @end deffn
 
address@hidden Scheduled Job Execution
address@hidden Scheduled Job Execution
address@hidden Geplante Auftragsausführung
address@hidden Geplante Auftragsausführung
 
 @cindex cron
 @cindex mcron
 @cindex scheduling jobs
 The @code{(gnu services mcron)} module provides an interface to
 address@hidden, a daemon to run jobs at scheduled times (@pxref{Top,,,
-mcron, address@hidden).  address@hidden is similar to the traditional
-Unix @command{cron} daemon; the main difference is that it is
-implemented in Guile Scheme, which provides a lot of flexibility when
-specifying the scheduling of jobs and their actions.
+mcron, address@hidden).  address@hidden is similar to the traditional Unix
address@hidden daemon; the main difference is that it is implemented in
+Guile Scheme, which provides a lot of flexibility when specifying the
+scheduling of jobs and their actions.
 
 The example below defines an operating system that runs the
address@hidden (@pxref{Invoking updatedb,,, find, Finding Files})
-and the @command{guix gc} commands (@pxref{Invoking guix gc}) daily, as
-well as the @command{mkid} command on behalf of an unprivileged user
-(@pxref{mkid invocation,,, idutils, ID Database Utilities}).  It uses
-gexps to introduce job definitions that are passed to mcron
-(@pxref{G-Expressions}).
address@hidden (@pxref{Invoking updatedb,,, find, Finding Files})  and
+the @command{guix gc} commands (@pxref{Aufruf von guix gc}) daily, as well as
+the @command{mkid} command on behalf of an unprivileged user (@pxref{mkid
+invocation,,, idutils, ID Database Utilities}).  It uses gexps to introduce
+job definitions that are passed to mcron (@pxref{G-Ausdrücke}).
 
 @lisp
 (use-modules (guix) (gnu) (gnu services mcron))
@@ -11446,20 +11464,20 @@ gexps to introduce job definitions that are passed to 
mcron
                   %base-services)))
 @end lisp
 
address@hidden Syntax, mcron job specifications,, mcron, address@hidden,
-for more information on mcron job specifications.  Below is the
-reference of the mcron service.
address@hidden Syntax, mcron job specifications,, mcron, address@hidden, for
+more information on mcron job specifications.  Below is the reference of the
+mcron service.
 
-On a running system, you can use the @code{schedule} action of the service to
-visualize the mcron jobs that will be executed next:
+On a running system, you can use the @code{schedule} action of the service
+to visualize the mcron jobs that will be executed next:
 
 @example
 # herd schedule mcron
 @end example
 
 @noindent
-The example above lists the next five tasks that will be executed, but you can
-also specify the number of tasks to display:
+The example above lists the next five tasks that will be executed, but you
+can also specify the number of tasks to display:
 
 @example
 # herd schedule mcron 10
@@ -11480,10 +11498,10 @@ This is a shorthand for:
 This is the type of the @code{mcron} service, whose value is an
 @code{mcron-configuration} object.
 
-This service type can be the target of a service extension that provides
-it additional job specifications (@pxref{Service Composition}).  In
-other words, it is possible to define services that provide additional
-mcron jobs to run.
+This service type can be the target of a service extension that provides it
+additional job specifications (@pxref{Dienstkompositionen}).  In other
+words, it is possible to define services that provide additional mcron jobs
+to run.
 @end defvr
 
 @deftp {Data Type} mcron-configuration
@@ -11494,24 +11512,24 @@ Data type representing the configuration of mcron.
 The mcron package to use.
 
 @item @code{jobs}
-This is a list of gexps (@pxref{G-Expressions}), where each gexp
-corresponds to an mcron job specification (@pxref{Syntax, mcron job
-specifications,, mcron, address@hidden).
+This is a list of gexps (@pxref{G-Ausdrücke}), where each gexp corresponds
+to an mcron job specification (@pxref{Syntax, mcron job specifications,,
+mcron, address@hidden).
 @end table
 @end deftp
 
 
address@hidden Log Rotation
address@hidden Log Rotation
address@hidden Log-Rotation
address@hidden Log-Rotation
 
 @cindex rottlog
 @cindex log rotation
 @cindex logging
-Log files such as those found in @file{/var/log} tend to grow endlessly,
-so it's a good idea to @dfn{rotate} them once in a while---i.e., archive
-their contents in separate files, possibly compressed.  The @code{(gnu
-services admin)} module provides an interface to address@hidden, a
-log rotation tool (@pxref{Top,,, rottlog, GNU Rot[t]log Manual}).
+Log files such as those found in @file{/var/log} tend to grow endlessly, so
+it's a good idea to @dfn{rotate} them once in a while---i.e., archive their
+contents in separate files, possibly compressed.  The @code{(gnu services
+admin)} module provides an interface to address@hidden, a log rotation
+tool (@pxref{Top,,, rottlog, GNU Rot[t]log Manual}).
 
 The example below defines an operating system that provides log rotation
 with the default settings, for commonly encountered log files.
@@ -11531,11 +11549,11 @@ with the default settings, for commonly encountered 
log files.
 This is the type of the Rottlog service, whose value is a
 @code{rottlog-configuration} object.
 
-Other services can extend this one with new @code{log-rotation} objects
-(see below), thereby augmenting the set of files to be rotated.
+Other services can extend this one with new @code{log-rotation} objects (see
+below), thereby augmenting the set of files to be rotated.
 
-This service type can define mcron jobs (@pxref{Scheduled Job
-Execution}) to run the rottlog service.
+This service type can define mcron jobs (@pxref{Geplante Auftragsausführung}) 
to
+run the rottlog service.
 @end defvr
 
 @deftp {Data Type} rottlog-configuration
@@ -11554,7 +11572,7 @@ A list of @code{log-rotation} objects as defined below.
 
 @item @code{jobs}
 This is a list of gexps where each gexp corresponds to an mcron job
-specification (@pxref{Scheduled Job Execution}).
+specification (@pxref{Geplante Auftragsausführung}).
 @end table
 @end deftp
 
@@ -11562,8 +11580,8 @@ specification (@pxref{Scheduled Job Execution}).
 Data type representing the rotation of a group of log files.
 
 Taking an example from the Rottlog manual (@pxref{Period Related File
-Examples,,, rottlog, GNU Rot[t]log Manual}), a log rotation might be
-defined like this:
+Examples,,, rottlog, GNU Rot[t]log Manual}), a log rotation might be defined
+like this:
 
 @example
 (log-rotation
@@ -11594,8 +11612,8 @@ Either @code{#f} or a gexp to execute once the rotation 
has completed.
 @end deftp
 
 @defvr {Scheme Variable} %default-rotations
-Specifies weekly rotation of @var{%rotated-files} and
-a couple of other files.
+Specifies weekly rotation of @var{%rotated-files} and a couple of other
+files.
 @end defvr
 
 @defvr {Scheme Variable} %rotated-files
@@ -11603,23 +11621,23 @@ The list of syslog-controlled files to be rotated.  
By default it is:
 @code{'("/var/log/messages" "/var/log/secure")}.
 @end defvr
 
address@hidden Networking Services
address@hidden Networking Services
address@hidden Netzwerkdienste
address@hidden Netzwerkdienste
 
 The @code{(gnu services networking)} module provides services to configure
 the network interface.
 
 @cindex DHCP, networking service
 @defvr {Scheme Variable} dhcp-client-service-type
-This is the type of services that run @var{dhcp}, a Dynamic Host Configuration
-Protocol (DHCP) client, on all the non-loopback network interfaces.  Its value
-is the DHCP client package to use, @code{isc-dhcp} by default.
+This is the type of services that run @var{dhcp}, a Dynamic Host
+Configuration Protocol (DHCP) client, on all the non-loopback network
+interfaces.  Its value is the DHCP client package to use, @code{isc-dhcp} by
+default.
 @end defvr
 
 @deffn {Scheme Procedure} dhcpd-service-type
-This type defines a service that runs a DHCP daemon.  To create a
-service of this type, you must supply a @code{<dhcpd-configuration>}.
-For example:
+This type defines a service that runs a DHCP daemon.  To create a service of
+this type, you must supply a @code{<dhcpd-configuration>}.  For example:
 
 @example
 (service dhcpd-service-type
@@ -11633,52 +11651,50 @@ For example:
 @table @asis
 @item @code{package} (default: @code{isc-dhcp})
 The package that provides the DHCP daemon.  This package is expected to
-provide the daemon at @file{sbin/dhcpd} relative to its output
-directory.  The default package is the
address@hidden://www.isc.org/products/DHCP, ISC's DHCP server}.
+provide the daemon at @file{sbin/dhcpd} relative to its output directory.
+The default package is the @uref{http://www.isc.org/products/DHCP, ISC's
+DHCP server}.
 @item @code{config-file} (default: @code{#f})
 The configuration file to use.  This is required.  It will be passed to
 @code{dhcpd} via its @code{-cf} option.  This may be any ``file-like''
-object (@pxref{G-Expressions, file-like objects}).  See @code{man
+object (@pxref{G-Ausdrücke, file-like objects}).  See @code{man
 dhcpd.conf} for details on the configuration file syntax.
 @item @code{version} (default: @code{"4"})
 The DHCP version to use.  The ISC DHCP server supports the values ``4'',
-``6'', and ``4o6''.  These correspond to the @code{dhcpd} program
-options @code{-4}, @code{-6}, and @code{-4o6}.  See @code{man dhcpd} for
-details.
+``6'', and ``4o6''.  These correspond to the @code{dhcpd} program options
address@hidden, @code{-6}, and @code{-4o6}.  See @code{man dhcpd} for details.
 @item @code{run-directory} (default: @code{"/run/dhcpd"})
-The run directory to use.  At service activation time, this directory
-will be created if it does not exist.
+The run directory to use.  At service activation time, this directory will
+be created if it does not exist.
 @item @code{pid-file} (default: @code{"/run/dhcpd/dhcpd.pid"})
 The PID file to use.  This corresponds to the @code{-pf} option of
 @code{dhcpd}.  See @code{man dhcpd} for details.
 @item @code{interfaces} (default: @code{'()})
 The names of the network interfaces on which dhcpd should listen for
 broadcasts.  If this list is not empty, then its elements (which must be
-strings) will be appended to the @code{dhcpd} invocation when starting
-the daemon.  It may not be necessary to explicitly specify any
-interfaces here; see @code{man dhcpd} for details.
+strings) will be appended to the @code{dhcpd} invocation when starting the
+daemon.  It may not be necessary to explicitly specify any interfaces here;
+see @code{man dhcpd} for details.
 @end table
 @end deftp
 
 @defvr {Scheme Variable} static-networking-service-type
-This is the type for statically-configured network interfaces.
 @c TODO Document <static-networking> data structures.
+This is the type for statically-configured network interfaces.
 @end defvr
 
 @deffn {Scheme Procedure} static-networking-service @var{interface} @var{ip} @
-       [#:netmask #f] [#:gateway #f] [#:name-servers @code{'()}] @
-       [#:requirement @code{'(udev)}]
-Return a service that starts @var{interface} with address @var{ip}.  If
address@hidden is true, use it as the network mask.  If @var{gateway} is true,
-it must be a string specifying the default network gateway.  @var{requirement}
-can be used to declare a dependency on another service before configuring the
-interface.
-
-This procedure can be called several times, one for each network
-interface of interest.  Behind the scenes what it does is extend
address@hidden with additional network interfaces
-to handle.
+       [#:netmask #f] [#:gateway #f] [#:name-servers @code{'()}] @ 
[#:requirement
address@hidden'(udev)}] Return a service that starts @var{interface} with 
address
address@hidden  If @var{netmask} is true, use it as the network mask.  If
address@hidden is true, it must be a string specifying the default network
+gateway.  @var{requirement} can be used to declare a dependency on another
+service before configuring the interface.
+
+This procedure can be called several times, one for each network interface
+of interest.  Behind the scenes what it does is extend
address@hidden with additional network interfaces to
+handle.
 
 For example:
 
@@ -11699,8 +11715,8 @@ management daemon that aims to simplify wired and 
wireless networking.
 
 This service adds the @var{wicd} package to the global profile, providing
 several commands to interact with the daemon and configure networking:
address@hidden, a graphical user interface, and the @command{wicd-cli}
-and @command{wicd-curses} user interfaces.
address@hidden, a graphical user interface, and the
address@hidden and @command{wicd-curses} user interfaces.
 @end deffn
 
 @cindex ModemManager
@@ -11711,8 +11727,7 @@ This is the service type for the
 service. The value for this service type is a
 @code{modem-manager-configuration} record.
 
-This service is part of @code{%desktop-services} (@pxref{Desktop
-Services}).
+This service is part of @code{%desktop-services} (@pxref{Desktop-Dienste}).
 @end defvr
 
 @deftp {Data Type} modem-manager-configuration
@@ -11733,8 +11748,7 @@ This is the service type for the
 service. The value for this service type is a
 @code{network-manager-configuration} record.
 
-This service is part of @code{%desktop-services} (@pxref{Desktop
-Services}).
+This service is part of @code{%desktop-services} (@pxref{Desktop-Dienste}).
 @end defvr
 
 @deftp {Data Type} network-manager-configuration
@@ -11754,29 +11768,28 @@ NetworkManager will update @code{resolv.conf} to 
reflect the nameservers
 provided by currently active connections.
 
 @item dnsmasq
-NetworkManager will run @code{dnsmasq} as a local caching nameserver,
-using a "split DNS" configuration if you are connected to a VPN, and
-then update @code{resolv.conf} to point to the local nameserver.
+NetworkManager will run @code{dnsmasq} as a local caching nameserver, using
+a "split DNS" configuration if you are connected to a VPN, and then update
address@hidden to point to the local nameserver.
 
 @item none
 NetworkManager will not modify @code{resolv.conf}.
 @end table
 
 @item @code{vpn-plugins} (default: @code{'()})
-This is the list of available plugins for virtual private networks
-(VPNs).  An example of this is the @code{network-manager-openvpn}
-package, which allows NetworkManager to manage VPNs @i{via} OpenVPN.
+This is the list of available plugins for virtual private networks (VPNs).
+An example of this is the @code{network-manager-openvpn} package, which
+allows NetworkManager to manage VPNs @i{via} OpenVPN.
 
 @end table
 @end deftp
 
 @cindex Connman
 @deffn {Scheme Variable} connman-service-type
-This is the service type to run @url{https://01.org/connman,Connman},
-a network connection manager.
+This is the service type to run @url{https://01.org/connman,Connman}, a
+network connection manager.
 
-Its value must be an
address@hidden record as in this example:
+Its value must be an @code{connman-configuration} record as in this example:
 
 @example
 (service connman-service-type
@@ -11822,8 +11835,8 @@ Whether to listen for requests on D-Bus.
 Where to store the PID file.
 
 @item @code{interface} (default: @code{#f})
-If this is set, it must specify the name of a network interface that
-WPA supplicant will control.
+If this is set, it must specify the name of a network interface that WPA
+supplicant will control.
 
 @item @code{config-file} (default: @code{#f})
 Optional configuration file to use.
@@ -11838,8 +11851,8 @@ List of additional command-line arguments to pass to 
the daemon.
 This is the service type to set up an iptables configuration. iptables is a
 packet filtering framework supported by the Linux kernel.  This service
 supports configuring iptables for both IPv4 and IPv6.  A simple example
-configuration rejecting all incoming connections except those to the ssh port
-22 is shown below.
+configuration rejecting all incoming connections except those to the ssh
+port 22 is shown below.
 
 @lisp
 (service iptables-service-type
@@ -11872,11 +11885,11 @@ The iptables package that provides 
@code{iptables-restore} and
 @code{ip6tables-restore}.
 @item @code{ipv4-rules} (default: @code{%iptables-accept-all-rules})
 The iptables rules to use.  It will be passed to @code{iptables-restore}.
-This may be any ``file-like'' object (@pxref{G-Expressions, file-like
+This may be any ``file-like'' object (@pxref{G-Ausdrücke, file-like
 objects}).
 @item @code{ipv6-rules} (default: @code{%iptables-accept-all-rules})
 The ip6tables rules to use.  It will be passed to @code{ip6tables-restore}.
-This may be any ``file-like'' object (@pxref{G-Expressions, file-like
+This may be any ``file-like'' object (@pxref{G-Ausdrücke, file-like
 objects}).
 @end table
 @end deftp
@@ -11885,11 +11898,11 @@ objects}).
 @cindex real time clock
 @defvr {Scheme Variable} ntp-service-type
 This is the type of the service running the the @uref{http://www.ntp.org,
-Network Time Protocol (NTP)} daemon, @command{ntpd}.  The daemon will keep the
-system clock synchronized with that of the specified NTP servers.
+Network Time Protocol (NTP)} daemon, @command{ntpd}.  The daemon will keep
+the system clock synchronized with that of the specified NTP servers.
 
-The value of this service is an @code{ntpd-configuration} object, as described
-below.
+The value of this service is an @code{ntpd-configuration} object, as
+described below.
 @end defvr
 
 @deftp {Data Type} ntp-configuration
@@ -11910,15 +11923,15 @@ The NTP package to use.
 @end deftp
 
 @defvr {Scheme Variable} %ntp-servers
-List of host names used as the default NTP servers.  These are servers of the
address@hidden://www.ntppool.org/en/, NTP Pool Project}.
+List of host names used as the default NTP servers.  These are servers of
+the @uref{https://www.ntppool.org/en/, NTP Pool Project}.
 @end defvr
 
 @cindex OpenNTPD
 @deffn {Scheme Procedure} openntpd-service-type
-Run the @command{ntpd}, the Network Time Protocol (NTP) daemon, as implemented
-by @uref{http://www.openntpd.org, OpenNTPD}.  The daemon will keep the system
-clock synchronized with that of the given servers.
+Run the @command{ntpd}, the Network Time Protocol (NTP) daemon, as
+implemented by @uref{http://www.openntpd.org, OpenNTPD}.  The daemon will
+keep the system clock synchronized with that of the given servers.
 
 @example
 (service
@@ -11943,24 +11956,25 @@ A list of local IP addresses or hostnames the ntpd 
daemon should listen on.
 A list of local IP address the ntpd daemon should use for outgoing queries.
 @item @code{sensor} (default: @code{'()})
 Specify a list of timedelta sensor devices ntpd should use.  @code{ntpd}
-will listen to each sensor that acutally exists and ignore non-existant ones.
-See @uref{https://man.openbsd.org/ntpd.conf, upstream documentation} for more
-information.
+will listen to each sensor that acutally exists and ignore non-existant
+ones.  See @uref{https://man.openbsd.org/ntpd.conf, upstream documentation}
+for more information.
 @item @code{server} (default: @var{%ntp-servers})
-Specify a list of IP addresses or hostnames of NTP servers to synchronize to.
+Specify a list of IP addresses or hostnames of NTP servers to synchronize
+to.
 @item @code{servers} (default: @code{'()})
 Specify a list of IP addresses or hostnames of NTP pools to synchronize to.
 @item @code{constraint-from} (default: @code{'()})
address@hidden can be configured to query the ‘Date’ from trusted HTTPS servers 
via TLS.
-This time information is not used for precision but acts as an authenticated
-constraint, thereby reducing the impact of unauthenticated NTP
-man-in-the-middle attacks.
-Specify a list of URLs, IP addresses or hostnames of HTTPS servers to provide
-a constraint.
address@hidden can be configured to query the ‘Date’ from trusted HTTPS servers
+via TLS.  This time information is not used for precision but acts as an
+authenticated constraint, thereby reducing the impact of unauthenticated NTP
+man-in-the-middle attacks.  Specify a list of URLs, IP addresses or
+hostnames of HTTPS servers to provide a constraint.
 @item @code{constraints-from} (default: @code{'()})
-As with constraint from, specify a list of URLs, IP addresses or hostnames of
-HTTPS servers to provide a constraint.  Should the hostname resolve to multiple
-IP addresses, @code{ntpd} will calculate a median constraint from all of them.
+As with constraint from, specify a list of URLs, IP addresses or hostnames
+of HTTPS servers to provide a constraint.  Should the hostname resolve to
+multiple IP addresses, @code{ntpd} will calculate a median constraint from
+all of them.
 @item @code{allow-large-adjustment?} (default: @code{#f})
 Determines if @code{ntpd} is allowed to make an initial adjustment of more
 than 180 seconds.
@@ -11969,16 +11983,16 @@ than 180 seconds.
 
 @cindex inetd
 @deffn {Scheme variable} inetd-service-type
-This service runs the @command{inetd} (@pxref{inetd invocation,,,
-inetutils, GNU Inetutils}) daemon.  @command{inetd} listens for
-connections on internet sockets, and lazily starts the specified server
-program when a connection is made on one of these sockets.
+This service runs the @command{inetd} (@pxref{inetd invocation,,, inetutils,
+GNU Inetutils}) daemon.  @command{inetd} listens for connections on internet
+sockets, and lazily starts the specified server program when a connection is
+made on one of these sockets.
 
 The value of this service is an @code{inetd-configuration} object.  The
 following example configures the @command{inetd} daemon to provide the
-built-in @command{echo} service, as well as an smtp service which
-forwards smtp traffic over ssh to a server @code{smtp-server} behind a
-gateway @code{hostname}:
+built-in @command{echo} service, as well as an smtp service which forwards
+smtp traffic over ssh to a server @code{smtp-server} behind a gateway
address@hidden:
 
 @example
 (service
@@ -12015,22 +12029,21 @@ Data type representing the configuration of 
@command{inetd}.
 The @command{inetd} executable to use.
 
 @item @code{entries} (default: @code{'()})
-A list of @command{inetd} service entries.  Each entry should be created
-by the @code{inetd-entry} constructor.
+A list of @command{inetd} service entries.  Each entry should be created by
+the @code{inetd-entry} constructor.
 @end table
 @end deftp
 
 @deftp {Data Type} inetd-entry
-Data type representing an entry in the @command{inetd} configuration.
-Each entry corresponds to a socket where @command{inetd} will listen for
+Data type representing an entry in the @command{inetd} configuration.  Each
+entry corresponds to a socket where @command{inetd} will listen for
 requests.
 
 @table @asis
address@hidden @code{node} (default: @code{#f})
-Optional string, a comma-separated list of local addresses
address@hidden should use when listening for this service.
address@hidden file,,, inetutils, GNU Inetutils} for a complete
-description of all options.
address@hidden @code{node} (Vorgabe: @code{#f})
+Optional string, a comma-separated list of local addresses @command{inetd}
+should use when listening for this service.  @xref{Configuration file,,,
+inetutils, GNU Inetutils} for a complete description of all options.
 @item @code{name}
 A string, the name must correspond to an entry in @code{/etc/services}.
 @item @code{socket-type}
@@ -12038,26 +12051,26 @@ One of @code{'stream}, @code{'dgram}, @code{'raw}, 
@code{'rdm} or
 @code{'seqpacket}.
 @item @code{protocol}
 A string, must correspond to an entry in @code{/etc/protocols}.
address@hidden @code{wait?} (default: @code{#t})
-Whether @command{inetd} should wait for the server to exit before
-listening to new service requests.
address@hidden @code{wait?} (Vorgabe: @code{#t})
+Whether @command{inetd} should wait for the server to exit before listening
+to new service requests.
 @item @code{user}
-A string containing the user (and, optionally, group) name of the user
-as whom the server should run.  The group name can be specified in a
-suffix, separated by a colon or period, i.e. @code{"user"},
address@hidden"user:group"} or @code{"user.group"}.
+A string containing the user (and, optionally, group) name of the user as
+whom the server should run.  The group name can be specified in a suffix,
+separated by a colon or period, i.e. @code{"user"}, @code{"user:group"} or
address@hidden"user.group"}.
 @item @code{program} (default: @code{"internal"})
-The server program which will serve the requests, or @code{"internal"}
-if @command{inetd} should use a built-in service.
+The server program which will serve the requests, or @code{"internal"} if
address@hidden should use a built-in service.
 @item @code{arguments} (default: @code{'()})
 A list strings or file-like objects, which are the server program's
-arguments, starting with the zeroth argument, i.e. the name of the
-program itself.  For @command{inetd}'s internal services, this entry
-must be @code{'()} or @code{'("internal")}.
+arguments, starting with the zeroth argument, i.e. the name of the program
+itself.  For @command{inetd}'s internal services, this entry must be
address@hidden'()} or @code{'("internal")}.
 @end table
 
address@hidden file,,, inetutils, GNU Inetutils} for a more
-detailed discussion of each configuration field.
address@hidden file,,, inetutils, GNU Inetutils} for a more detailed
+discussion of each configuration field.
 @end deftp
 
 @cindex Tor
@@ -12070,25 +12083,25 @@ Tor} anonymous networking daemon.  The service is 
configured using a
 @end defvr
 
 @deffn {Scheme Procedure} tor-service address@hidden [#:tor @var{tor}]
-This procedure is deprecated and will be removed in a future release.  Return
-a service of the @code{tor-service-type} type.  @var{config-file} and
+This procedure is deprecated and will be removed in a future release.
+Return a service of the @code{tor-service-type} type.  @var{config-file} and
 @var{tor} have the same meaning as in @code{<tor-configuration>}.
 @end deffn
 
 @deftp {Data Type} tor-configuration
 @table @asis
 @item @code{tor} (default: @code{tor})
-The package that provides the Tor daemon.  This package is expected to provide
-the daemon at @file{bin/tor} relative to its output directory.  The default
-package is the @uref{https://www.torproject.org, Tor Project's}
+The package that provides the Tor daemon.  This package is expected to
+provide the daemon at @file{bin/tor} relative to its output directory.  The
+default package is the @uref{https://www.torproject.org, Tor Project's}
 implementation.
 
 @item @code{config-file} (default: @code{(plain-file "empty" "")})
-The configuration file to use.  It will be appended to a default configuration
-file, and the final configuration file will be passed to @code{tor} via its
address@hidden option.  This may be any ``file-like'' object 
(@pxref{G-Expressions,
-file-like objects}).  See @code{man tor} for details on the configuration file
-syntax.
+The configuration file to use.  It will be appended to a default
+configuration file, and the final configuration file will be passed to
address@hidden via its @code{-f} option.  This may be any ``file-like'' object
+(@pxref{G-Ausdrücke, file-like objects}).  See @code{man tor} for details
+on the configuration file syntax.
 
 @item @code{hidden-services} (default: @code{'()})
 The list of @code{<hidden-service>} records to use.  For any hidden service
@@ -12099,11 +12112,11 @@ may conveniently create @code{<hidden-service>} 
records using the
 
 @item @code{socks-socket-type} (default: @code{'tcp})
 The default socket type that Tor should use for its SOCKS socket.  This must
-be either @code{'tcp} or @code{'unix}.  If it is @code{'tcp}, then by default
-Tor will listen on TCP port 9050 on the loopback interface (i.e., localhost).
-If it is @code{'unix}, then Tor will listen on the UNIX domain socket
address@hidden/var/run/tor/socks-sock}, which will be made writable by members 
of the
address@hidden group.
+be either @code{'tcp} or @code{'unix}.  If it is @code{'tcp}, then by
+default Tor will listen on TCP port 9050 on the loopback interface (i.e.,
+localhost).  If it is @code{'unix}, then Tor will listen on the UNIX domain
+socket @file{/var/run/tor/socks-sock}, which will be made writable by
+members of the @code{tor} group.
 
 If you want to customize the SOCKS socket in more detail, leave
 @code{socks-socket-type} at its default value of @code{'tcp} and use
@@ -12122,22 +12135,21 @@ Define a new Tor @dfn{hidden service} called 
@var{name} and implementing
    (80 "127.0.0.1:8080"))
 @end example
 
-In this example, port 22 of the hidden service is mapped to local port 22, and
-port 80 is mapped to local port 8080.
+In this example, port 22 of the hidden service is mapped to local port 22,
+and port 80 is mapped to local port 8080.
 
-This creates a @file{/var/lib/tor/hidden-services/@var{name}} directory, where
-the @file{hostname} file contains the @code{.onion} host name for the hidden
-service.
+This creates a @file{/var/lib/tor/hidden-services/@var{name}} directory,
+where the @file{hostname} file contains the @code{.onion} host name for the
+hidden service.
 
-See @uref{https://www.torproject.org/docs/tor-hidden-service.html.en, the Tor
-project's documentation} for more information.
+See @uref{https://www.torproject.org/docs/tor-hidden-service.html.en, the
+Tor project's documentation} for more information.
 @end deffn
 
 The @code{(gnu services rsync)} module provides the following services:
 
-You might want an rsync daemon if you have files that you want available
-so anyone (or just yourself) can download existing files or upload new
-files.
+You might want an rsync daemon if you have files that you want available so
+anyone (or just yourself) can download existing files or upload new files.
 
 @deffn {Scheme Variable} rsync-service-type
 This is the type for the @uref{https://rsync.samba.org, rsync} rsync daemon,
@@ -12208,18 +12220,17 @@ Furthermore, @code{(gnu services ssh)} provides the 
following services.
 
 @deffn {Scheme Procedure} lsh-service [#:host-key "/etc/lsh/host-key"] @
        [#:daemonic? #t] [#:interfaces '()] [#:port-number 22] @
-       [#:allow-empty-passwords? #f] [#:root-login? #f] @
-       [#:syslog-output? #t] [#:x11-forwarding? #t] @
-       [#:tcp/ip-forwarding? #t] [#:password-authentication? #t] @
-       [#:public-key-authentication? #t] [#:initialize? #t]
-Run the @command{lshd} program from @var{lsh} to listen on port 
@var{port-number}.
address@hidden must designate a file containing the host key, and readable
-only by root.
+[#:allow-empty-passwords? #f] [#:root-login? #f] @ [#:syslog-output? #t]
+[#:x11-forwarding? #t] @ [#:tcp/ip-forwarding? #t]
+[#:password-authentication? #t] @ [#:public-key-authentication? #t]
+[#:initialize? #t] Run the @command{lshd} program from @var{lsh} to listen
+on port @var{port-number}.  @var{host-key} must designate a file containing
+the host key, and readable only by root.
 
 When @var{daemonic?} is true, @command{lshd} will detach from the
 controlling terminal and log its output to syslogd, unless one sets
address@hidden to false.  Obviously, it also makes lsh-service
-depend on existence of syslogd service.  When @var{pid-file?} is true,
address@hidden to false.  Obviously, it also makes lsh-service depend
+on existence of syslogd service.  When @var{pid-file?} is true,
 @command{lshd} writes its PID to the file called @var{pid-file}.
 
 When @var{initialize?} is true, automatically create the seed and host key
@@ -12227,9 +12238,9 @@ upon service activation if they do not exist yet.  This 
may take long and
 require interaction.
 
 When @var{initialize?} is false, it is up to the user to initialize the
-randomness generator (@pxref{lsh-make-seed,,, lsh, LSH Manual}), and to create
-a key pair with the private key stored in file @var{host-key} (@pxref{lshd
-basics,,, lsh, LSH Manual}).
+randomness generator (@pxref{lsh-make-seed,,, lsh, LSH Manual}), and to
+create a key pair with the private key stored in file @var{host-key}
+(@pxref{lshd basics,,, lsh, LSH Manual}).
 
 When @var{interfaces} is empty, lshd listens for connections on all the
 network interfaces; otherwise, @var{interfaces} must be a list of host names
@@ -12245,9 +12256,9 @@ The other options should be self-descriptive.
 @cindex SSH
 @cindex SSH server
 @deffn {Scheme Variable} openssh-service-type
-This is the type for the @uref{http://www.openssh.org, OpenSSH} secure
-shell daemon, @command{sshd}.  Its value must be an
address@hidden record as in this example:
+This is the type for the @uref{http://www.openssh.org, OpenSSH} secure shell
+daemon, @command{sshd}.  Its value must be an @code{openssh-configuration}
+record as in this example:
 
 @example
 (service openssh-service-type
@@ -12261,8 +12272,7 @@ shell daemon, @command{sshd}.  Its value must be an
 
 See below for details about @code{openssh-configuration}.
 
-This service can be extended with extra authorized keys, as in this
-example:
+This service can be extended with extra authorized keys, as in this example:
 
 @example
 (service-extension openssh-service-type
@@ -12283,29 +12293,27 @@ TCP port on which @command{sshd} listens for incoming 
connections.
 
 @item @code{permit-root-login} (default: @code{#f})
 This field determines whether and when to allow logins as root.  If
address@hidden, root logins are disallowed; if @code{#t}, they are allowed.
-If it's the symbol @code{'without-password}, then root logins are
-permitted but not with password-based authentication.
address@hidden, root logins are disallowed; if @code{#t}, they are allowed.  If
+it's the symbol @code{'without-password}, then root logins are permitted but
+not with password-based authentication.
 
 @item @code{allow-empty-passwords?} (default: @code{#f})
-When true, users with empty passwords may log in.  When false, they may
-not.
+When true, users with empty passwords may log in.  When false, they may not.
 
 @item @code{password-authentication?} (default: @code{#t})
 When true, users may log in with their password.  When false, they have
 other authentication methods.
 
 @item @code{public-key-authentication?} (default: @code{#t})
-When true, users may log in using public key authentication.  When
-false, users have to use other authentication method.
+When true, users may log in using public key authentication.  When false,
+users have to use other authentication method.
 
-Authorized public keys are stored in @file{~/.ssh/authorized_keys}.
-This is used only by protocol version 2.
+Authorized public keys are stored in @file{~/.ssh/authorized_keys}.  This is
+used only by protocol version 2.
 
 @item @code{x11-forwarding?} (default: @code{#f})
-When true, forwarding of X11 graphical client connections is
-enabled---in other words, @command{ssh} options @option{-X} and
address@hidden will work.
+When true, forwarding of X11 graphical client connections is enabled---in
+other words, @command{ssh} options @option{-X} and @option{-Y} will work.
 
 @item @code{allow-agent-forwarding?} (default: @code{#t})
 Whether to allow agent forwarding.
@@ -12321,30 +12329,30 @@ Specifies whether challenge response authentication 
is allowed (e.g. via
 PAM).
 
 @item @code{use-pam?} (default: @code{#t})
-Enables the Pluggable Authentication Module interface.  If set to
address@hidden, this will enable PAM authentication using
+Enables the Pluggable Authentication Module interface.  If set to @code{#t},
+this will enable PAM authentication using
 @code{challenge-response-authentication?} and
 @code{password-authentication?}, in addition to PAM account and session
 module processing for all authentication types.
 
-Because PAM challenge response authentication usually serves an
-equivalent role to password authentication, you should disable either
+Because PAM challenge response authentication usually serves an equivalent
+role to password authentication, you should disable either
 @code{challenge-response-authentication?} or
 @code{password-authentication?}.
 
 @item @code{print-last-log?} (default: @code{#t})
-Specifies whether @command{sshd} should print the date and time of the
-last user login when a user logs in interactively.
+Specifies whether @command{sshd} should print the date and time of the last
+user login when a user logs in interactively.
 
 @item @code{subsystems} (default: @code{'(("sftp" "internal-sftp"))})
 Configures external subsystems (e.g. file transfer daemon).
 
-This is a list of two-element lists, each of which containing the
-subsystem name and a command (with optional arguments) to execute upon
-subsystem request.
+This is a list of two-element lists, each of which containing the subsystem
+name and a command (with optional arguments) to execute upon subsystem
+request.
 
-The command @command{internal-sftp} implements an in-process SFTP
-server.  Alternately, one can specify the @command{sftp-server} command:
+The command @command{internal-sftp} implements an in-process SFTP server.
+Alternately, one can specify the @command{sftp-server} command:
 @example
 (service openssh-service-type
          (openssh-configuration
@@ -12358,10 +12366,10 @@ List of strings describing which environment 
variables may be exported.
 Each string gets on its own line.  See the @code{AcceptEnv} option in
 @code{man sshd_config}.
 
-This example allows ssh-clients to export the @code{COLORTERM} variable.
-It is set by terminal emulators, which support colors.  You can use it in
-your shell's ressource file to enable colors for the prompt and commands
-if this variable is set.
+This example allows ssh-clients to export the @code{COLORTERM} variable.  It
+is set by terminal emulators, which support colors.  You can use it in your
+shell's ressource file to enable colors for the prompt and commands if this
+variable is set.
 
 @example
 (service openssh-service-type
@@ -12407,8 +12415,8 @@ Run the 
@uref{https://matt.ucc.asn.au/dropbear/dropbear.html,Dropbear SSH
 daemon} with the given @var{config}, a @code{<dropbear-configuration>}
 object.
 
-For example, to specify a Dropbear service listening on port 1234, add
-this call to the operating system's @code{services} field:
+For example, to specify a Dropbear service listening on port 1234, add this
+call to the operating system's @code{services} field:
 
 @example
 (dropbear-service (dropbear-configuration
@@ -12444,14 +12452,14 @@ Whether to enable password-based authentication.
 @end deftp
 
 @defvr {Scheme Variable} %facebook-host-aliases
-This variable contains a string for use in @file{/etc/hosts}
-(@pxref{Host Names,,, libc, The GNU C Library Reference Manual}).  Each
-line contains a entry that maps a known server name of the Facebook
-on-line service---e.g., @code{www.facebook.com}---to the local
address@hidden or its IPv6 equivalent, @code{::1}.
+This variable contains a string for use in @file{/etc/hosts} (@pxref{Host
+Names,,, libc, The GNU C Library Reference Manual}).  Each line contains a
+entry that maps a known server name of the Facebook on-line service---e.g.,
address@hidden the local address@hidden or its IPv6
+equivalent, @code{::1}.
 
 This variable is typically used in the @code{hosts-file} field of an
address@hidden declaration (@pxref{operating-system Reference,
address@hidden declaration (@pxref{„operating-system“-Referenz,
 @file{/etc/hosts}}):
 
 @example
@@ -12468,42 +12476,39 @@ This variable is typically used in the 
@code{hosts-file} field of an
                                %facebook-host-aliases))))
 @end example
 
-This mechanism can prevent programs running locally, such as Web
-browsers, from accessing Facebook.
+This mechanism can prevent programs running locally, such as Web browsers,
+from accessing Facebook.
 @end defvr
 
 The @code{(gnu services avahi)} provides the following definition.
 
 @deffn {Scheme Procedure} avahi-service [#:avahi @var{avahi}] @
-          [#:host-name #f] [#:publish? #t] [#:ipv4? #t] @
-          [#:ipv6? #t] [#:wide-area? #f] @
-          [#:domains-to-browse '()] [#:debug? #f]
-Return a service that runs @command{avahi-daemon}, a system-wide
-mDNS/DNS-SD responder that allows for service discovery and
-"zero-configuration" host name lookups (see @uref{http://avahi.org/}), and
-extends the name service cache daemon (nscd) so that it can resolve
address@hidden host names using
address@hidden://0pointer.de/lennart/projects/nss-mdns/, nss-mdns}.  
Additionally,
-add the @var{avahi} package to the system profile so that commands such as
address@hidden are directly usable.
+          [#:host-name #f] [#:publish? #t] [#:ipv4? #t] @ [#:ipv6? #t] 
[#:wide-area?
+#f] @ [#:domains-to-browse '()] [#:debug? #f] Return a service that runs
address@hidden, a system-wide mDNS/DNS-SD responder that allows for
+service discovery and "zero-configuration" host name lookups (see
address@hidden://avahi.org/}), and extends the name service cache daemon (nscd)
+so that it can resolve @code{.local} host names using
address@hidden://0pointer.de/lennart/projects/nss-mdns/, nss-mdns}.
+Additionally, add the @var{avahi} package to the system profile so that
+commands such as @command{avahi-browse} are directly usable.
 
 If @var{host-name} is different from @code{#f}, use that as the host name to
 publish for this machine; otherwise, use the machine's actual host name.
 
-When @var{publish?} is true, publishing of host names and services is allowed;
-in particular, avahi-daemon will publish the machine's host name and IP
-address via mDNS on the local network.
+When @var{publish?} is true, publishing of host names and services is
+allowed; in particular, avahi-daemon will publish the machine's host name
+and IP address via mDNS on the local network.
 
 When @var{wide-area?} is true, DNS-SD over unicast DNS is enabled.
 
-Boolean values @var{ipv4?} and @var{ipv6?} determine whether to use IPv4/IPv6
-sockets.
+Boolean values @var{ipv4?} and @var{ipv6?} determine whether to use
+IPv4/IPv6 sockets.
 @end deffn
 
 @deffn {Scheme Variable} openvswitch-service-type
 This is the type of the @uref{http://www.openvswitch.org, Open vSwitch}
-service, whose value should be an @code{openvswitch-configuration}
-object.
+service, whose value should be an @code{openvswitch-configuration} object.
 @end deffn
 
 @deftp {Data Type} openvswitch-configuration
@@ -12524,16 +12529,16 @@ Package object of the Open vSwitch.
 @cindex X11
 @cindex X Window System
 @cindex login manager
-Support for the X Window graphical display system---specifically
-Xorg---is provided by the @code{(gnu services xorg)} module.  Note that
-there is no @code{xorg-service} procedure.  Instead, the X server is
-started by the @dfn{login manager}, by default SLiM.
+Support for the X Window graphical display system---specifically Xorg---is
+provided by the @code{(gnu services xorg)} module.  Note that there is no
address@hidden procedure.  Instead, the X server is started by the
address@hidden manager}, by default SLiM.
 
 @cindex window manager
-To use X11, you must install at least one @dfn{window manager}---for
-example the @code{windowmaker} or @code{openbox} packages---preferably
-by adding it to the @code{packages} field of your operating system
-definition (@pxref{operating-system Reference, system-wide packages}).
+To use X11, you must install at least one @dfn{window manager}---for example
+the @code{windowmaker} or @code{openbox} packages---preferably by adding it
+to the @code{packages} field of your operating system definition
+(@pxref{„operating-system“-Referenz, system-wide packages}).
 
 @defvr {Scheme Variable} slim-service-type
 This is the type for the SLiM graphical login manager for X11.
@@ -12542,14 +12547,14 @@ This is the type for the SLiM graphical login manager 
for X11.
 @cindex X11 session types
 SLiM looks for @dfn{session types} described by the @file{.desktop} files in
 @file{/run/current-system/profile/share/xsessions} and allows users to
-choose a session from the log-in screen using @kbd{F1}.  Packages such
-as @code{xfce}, @code{sawfish}, and @code{ratpoison} provide
address@hidden files; adding them to the system-wide set of packages
-automatically makes them available at the log-in screen.
+choose a session from the log-in screen using @kbd{F1}.  Packages such as
address@hidden, @code{sawfish}, and @code{ratpoison} provide @file{.desktop}
+files; adding them to the system-wide set of packages automatically makes
+them available at the log-in screen.
 
 In addition, @file{~/.xsession} files are honored.  When available,
address@hidden/.xsession} must be an executable that starts a window manager
-and/or other X clients.
address@hidden/.xsession} must be an executable that starts a window manager 
and/or
+other X clients.
 @end defvr
 
 @deftp {Data Type} slim-configuration
@@ -12574,11 +12579,11 @@ The graphical theme to use and its name.
 If true, this must be the name of the executable to start as the default
 session---e.g., @code{(file-append windowmaker "/bin/windowmaker")}.
 
-If false, a session described by one of the available @file{.desktop}
-files in @code{/run/current-system/profile} and @code{~/.guix-profile}
-will be used.
+If false, a session described by one of the available @file{.desktop} files
+in @code{/run/current-system/profile} and @code{~/.guix-profile} will be
+used.
 
address@hidden Note
address@hidden Anmerkung
 You must install at least one window manager in the system profile or in
 your user profile.  Failing to do that, if @code{auto-login-session} is
 false, you will be unable to log in.
@@ -12591,8 +12596,7 @@ The command used to start the X11 graphical server.
 The XAuth package to use.
 
 @item @code{shepherd} (default: @code{shepherd})
-The Shepherd package used when invoking @command{halt} and
address@hidden
+The Shepherd package used when invoking @command{halt} and @command{reboot}.
 
 @item @code{sessreg} (default: @code{sessreg})
 The sessreg package used in order to register the session.
@@ -12613,8 +12617,8 @@ This is the data type representing the sddm service 
configuration.
 
 @table @asis
 @item @code{display-server} (default: "x11")
-Select display server to use for the greeter. Valid values are "x11"
-or "wayland".
+Select display server to use for the greeter. Valid values are "x11" or
+"wayland".
 
 @item @code{numlock} (default: "on")
 Valid values are "on", "off" or "none".
@@ -12714,41 +12718,38 @@ type @code{<sddm-configuration>}.
 @end deffn
 
 @deffn {Scheme Procedure} xorg-start-command [#:guile] @
-  [#:modules %default-xorg-modules] @
-  [#:fonts %default-xorg-fonts] @
-  [#:configuration-file (xorg-configuration-file @dots{})] @
-  [#:xorg-server @var{xorg-server}]
-Return a @code{startx} script in which @var{modules}, a list of X module
-packages, and @var{fonts}, a list of X font directories, are available.  See
address@hidden for more details on the arguments.  The result should be
-used in place of @code{startx}.
+  [#:modules %default-xorg-modules] @ [#:fonts %default-xorg-fonts] @
+[#:configuration-file (xorg-configuration-file @dots{})] @ [#:xorg-server
address@hidden Return a @code{startx} script in which @var{modules}, a
+list of X module packages, and @var{fonts}, a list of X font directories,
+are available.  See @code{xorg-wrapper} for more details on the arguments.
+The result should be used in place of @code{startx}.
 
 Usually the X server is started by a login manager.
 @end deffn
 
 @deffn {Scheme Procedure} xorg-configuration-file @
-  [#:modules %default-xorg-modules] @
-  [#:fonts %default-xorg-fonts] @
-  [#:drivers '()] [#:resolutions '()] [#:extra-config '()]
-Return a configuration file for the Xorg server containing search paths for
-all the common drivers.
+  [#:modules %default-xorg-modules] @ [#:fonts %default-xorg-fonts] @
+[#:drivers '()] [#:resolutions '()] [#:extra-config '()] Return a
+configuration file for the Xorg server containing search paths for all the
+common drivers.
 
 @var{modules} must be a list of @dfn{module packages} loaded by the Xorg
-server---e.g., @code{xf86-video-vesa}, @code{xf86-input-keyboard}, and so on.
address@hidden must be a list of font directories to add to the server's
+server---e.g., @code{xf86-video-vesa}, @code{xf86-input-keyboard}, and so
+on.  @var{fonts} must be a list of font directories to add to the server's
 @dfn{font path}.
 
 @var{drivers} must be either the empty list, in which case Xorg chooses a
-graphics driver automatically, or a list of driver names that will be tried in
-this order---e.g., @code{("modesetting" "vesa")}.
+graphics driver automatically, or a list of driver names that will be tried
+in this order---e.g., @code{("modesetting" "vesa")}.
 
 Likewise, when @var{resolutions} is the empty list, Xorg chooses an
 appropriate screen resolution; otherwise, it must be a list of
 resolutions---e.g., @code{((1024 768) (640 480))}.
 
 Last, @var{extra-config} is a list of strings or objects appended to the
-configuration file.  It is used to pass extra text to be
-added verbatim to the configuration file.
+configuration file.  It is used to pass extra text to be added verbatim to
+the configuration file.
 
 @cindex keymap
 @cindex keyboard layout
@@ -12780,13 +12781,13 @@ EndSection")
                      (list bepo-evdev)))))))))
 @end example
 
-The @code{MatchIsKeyboard} line specifies that we only apply the configuration
-to keyboards.  Without this line, other devices such as touchpad may not work
-correctly because they will be attached to the wrong driver.  In this example,
-the user typically used @code{setxkbmap fr bepo} to set their favorite keymap
-once logged in.  The first argument corresponds to the layout, while the second
-argument corresponds to the variant.  The @code{xkb_variant} line can be 
omitted
-to select the default variant.
+The @code{MatchIsKeyboard} line specifies that we only apply the
+configuration to keyboards.  Without this line, other devices such as
+touchpad may not work correctly because they will be attached to the wrong
+driver.  In this example, the user typically used @code{setxkbmap fr bepo}
+to set their favorite keymap once logged in.  The first argument corresponds
+to the layout, while the second argument corresponds to the variant.  The
address@hidden line can be omitted to select the default variant.
 @end deffn
 
 @deffn {Scheme Procedure} screen-locker-service @var{package} address@hidden
@@ -12802,18 +12803,17 @@ makes the good ol' XlockMore usable.
 @end deffn
 
 
address@hidden Printing Services
address@hidden Printing Services
address@hidden Druckdienste
address@hidden Druckdienste
 
 @cindex printer support with CUPS
-The @code{(gnu services cups)} module provides a Guix service definition
-for the CUPS printing service.  To add printer support to a GuixSD
-system, add a @code{cups-service} to the operating system definition:
+The @code{(gnu services cups)} module provides a Guix service definition for
+the CUPS printing service.  To add printer support to a GuixSD system, add a
address@hidden to the operating system definition:
 
 @deffn {Scheme Variable} cups-service-type
 The service type for the CUPS print server.  Its value should be a valid
-CUPS configuration (see below).  To use the default settings, simply
-write:
+CUPS configuration (see below).  To use the default settings, simply write:
 @example
 (service cups-service-type)
 @end example
@@ -12821,16 +12821,16 @@ write:
 
 The CUPS configuration controls the basic things about your CUPS
 installation: what interfaces it listens on, what to do if a print job
-fails, how much logging to do, and so on.  To actually add a printer,
-you have to visit the @url{http://localhost:631} URL, or use a tool such
-as GNOME's printer configuration services.  By default, configuring a
-CUPS service will generate a self-signed certificate if needed, for
-secure connections to the print server.
+fails, how much logging to do, and so on.  To actually add a printer, you
+have to visit the @url{http://localhost:631} URL, or use a tool such as
+GNOME's printer configuration services.  By default, configuring a CUPS
+service will generate a self-signed certificate if needed, for secure
+connections to the print server.
 
-Suppose you want to enable the Web interface of CUPS and also add
-support for Epson printers @i{via} the @code{escpr} package and for HP
-printers @i{via} the @code{hplip-minimal} package.  You can do that directly,
-like this (you need to use the @code{(gnu packages cups)} module):
+Suppose you want to enable the Web interface of CUPS and also add support
+for Epson printers @i{via} the @code{escpr} package and for HP printers
address@hidden the @code{hplip-minimal} package.  You can do that directly, like
+this (you need to use the @code{(gnu packages cups)} module):
 
 @example
 (service cups-service-type
@@ -12844,12 +12844,12 @@ Note: If you wish to use the Qt5 based GUI which 
comes with the hplip
 package then it is suggested that you install the @code{hplip} package,
 either in your OS configuration file or as your user.
 
-The available configuration parameters follow.  Each parameter
-definition is preceded by its type; for example, @samp{string-list foo}
-indicates that the @code{foo} parameter should be specified as a list of
-strings.  There is also a way to specify the configuration as a string,
-if you have an old @code{cupsd.conf} file that you want to port over
-from some other system; see the end for more details.
+The available configuration parameters follow.  Each parameter definition is
+preceded by its type; for example, @samp{string-list foo} indicates that the
address@hidden parameter should be specified as a list of strings.  There is
+also a way to specify the configuration as a string, if you have an old
address@hidden file that you want to port over from some other system;
+see the end for more details.
 
 @c The following documentation was initially generated by
 @c (generate-documentation) in (gnu services cups).  Manually maintained
@@ -12881,9 +12881,9 @@ Defines the access log filename.  Specifying a blank 
filename disables
 access log generation.  The value @code{stderr} causes log entries to be
 sent to the standard error file when the scheduler is running in the
 foreground, or to the system log daemon when run in the background.  The
-value @code{syslog} causes log entries to be sent to the system log
-daemon.  The server name may be included in filenames using the string
address@hidden, as in @code{/var/log/cups/%s-access_log}.
+value @code{syslog} causes log entries to be sent to the system log daemon.
+The server name may be included in filenames using the string @code{%s}, as
+in @code{/var/log/cups/%s-access_log}.
 
 Defaults to @samp{"/var/log/cups/access_log"}.
 @end deftypevr
@@ -12898,30 +12898,30 @@ Defaults to @samp{"/var/cache/cups"}.
 Specifies the permissions for all configuration files that the scheduler
 writes.
 
-Note that the permissions for the printers.conf file are currently
-masked to only allow access from the scheduler user (typically root).
-This is done because printer device URIs sometimes contain sensitive
-authentication information that should not be generally known on the
-system.  There is no way to disable this security feature.
+Note that the permissions for the printers.conf file are currently masked to
+only allow access from the scheduler user (typically root).  This is done
+because printer device URIs sometimes contain sensitive authentication
+information that should not be generally known on the system.  There is no
+way to disable this security feature.
 
 Defaults to @samp{"0640"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} log-location error-log
-Defines the error log filename.  Specifying a blank filename disables
-access log generation.  The value @code{stderr} causes log entries to be
-sent to the standard error file when the scheduler is running in the
-foreground, or to the system log daemon when run in the background.  The
-value @code{syslog} causes log entries to be sent to the system log
-daemon.  The server name may be included in filenames using the string
address@hidden, as in @code{/var/log/cups/%s-error_log}.
+Defines the error log filename.  Specifying a blank filename disables access
+log generation.  The value @code{stderr} causes log entries to be sent to
+the standard error file when the scheduler is running in the foreground, or
+to the system log daemon when run in the background.  The value
address@hidden causes log entries to be sent to the system log daemon.  The
+server name may be included in filenames using the string @code{%s}, as in
address@hidden/var/log/cups/%s-error_log}.
 
 Defaults to @samp{"/var/log/cups/error_log"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string fatal-errors
-Specifies which errors are fatal, causing the scheduler to exit.  The
-kind strings are:
+Specifies which errors are fatal, causing the scheduler to exit.  The kind
+strings are:
 
 @table @code
 @item none
@@ -12931,22 +12931,22 @@ No errors are fatal.
 All of the errors below are fatal.
 
 @item browse
-Browsing initialization errors are fatal, for example failed connections
-to the DNS-SD daemon.
+Browsing initialization errors are fatal, for example failed connections to
+the DNS-SD daemon.
 
 @item config
 Configuration file syntax errors are fatal.
 
 @item listen
-Listen or Port errors are fatal, except for IPv6 failures on the
-loopback or @code{any} addresses.
+Listen or Port errors are fatal, except for IPv6 failures on the loopback or
address@hidden addresses.
 
 @item log
 Log file creation or write errors are fatal.
 
 @item permissions
-Bad startup file permissions are fatal, for example shared TLS
-certificate and key files with world-read permissions.
+Bad startup file permissions are fatal, for example shared TLS certificate
+and key files with world-read permissions.
 @end table
 
 Defaults to @samp{"all -browse"}.
@@ -12973,20 +12973,20 @@ Defaults to @samp{"0644"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} log-location page-log
-Defines the page log filename.  Specifying a blank filename disables
-access log generation.  The value @code{stderr} causes log entries to be
-sent to the standard error file when the scheduler is running in the
-foreground, or to the system log daemon when run in the background.  The
-value @code{syslog} causes log entries to be sent to the system log
-daemon.  The server name may be included in filenames using the string
address@hidden, as in @code{/var/log/cups/%s-page_log}.
+Defines the page log filename.  Specifying a blank filename disables access
+log generation.  The value @code{stderr} causes log entries to be sent to
+the standard error file when the scheduler is running in the foreground, or
+to the system log daemon when run in the background.  The value
address@hidden causes log entries to be sent to the system log daemon.  The
+server name may be included in filenames using the string @code{%s}, as in
address@hidden/var/log/cups/%s-page_log}.
 
 Defaults to @samp{"/var/log/cups/page_log"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string remote-root
-Specifies the username that is associated with unauthenticated accesses
-by clients claiming to be the root user.  The default is @code{remroot}.
+Specifies the username that is associated with unauthenticated accesses by
+clients claiming to be the root user.  The default is @code{remroot}.
 
 Defaults to @samp{"remroot"}.
 @end deftypevr
@@ -12999,19 +12999,18 @@ Defaults to @samp{"/var/spool/cups"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} sandboxing sandboxing
-Specifies the level of security sandboxing that is applied to print
-filters, backends, and other child processes of the scheduler; either
address@hidden or @code{strict}.  This directive is currently only
-used/supported on macOS.
+Specifies the level of security sandboxing that is applied to print filters,
+backends, and other child processes of the scheduler; either @code{relaxed}
+or @code{strict}.  This directive is currently only used/supported on macOS.
 
 Defaults to @samp{strict}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-name server-keychain
-Specifies the location of TLS certificates and private keys.  CUPS will
-look for public and private keys in this directory: a @code{.crt} files
-for PEM-encoded certificates and corresponding @code{.key} files for
-PEM-encoded private keys.
+Specifies the location of TLS certificates and private keys.  CUPS will look
+for public and private keys in this directory: a @code{.crt} files for
+PEM-encoded certificates and corresponding @code{.key} files for PEM-encoded
+private keys.
 
 Defaults to @samp{"/etc/cups/ssl"}.
 @end deftypevr
@@ -13023,8 +13022,8 @@ Defaults to @samp{"/etc/cups"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean sync-on-close?
-Specifies whether the scheduler calls fsync(2) after writing
-configuration or state files.
+Specifies whether the scheduler calls fsync(2) after writing configuration
+or state files.
 
 Defaults to @samp{#f}.
 @end deftypevr
@@ -13040,20 +13039,19 @@ Defaults to @samp{"/var/spool/cups/tmp"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string user
-Specifies the user name or ID that is used when running external
-programs.
+Specifies the user name or ID that is used when running external programs.
 
 Defaults to @samp{"lp"}.
 @end deftypevr
 @end deftypevr
 
 @deftypevr address@hidden parameter} access-log-level access-log-level
-Specifies the logging level for the AccessLog file.  The @code{config}
-level logs when printers and classes are added, deleted, or modified and
-when configuration files are accessed or updated.  The @code{actions}
-level logs when print jobs are submitted, held, released, modified, or
-canceled, and any of the conditions for @code{config}.  The @code{all}
-level logs all requests.
+Specifies the logging level for the AccessLog file.  The @code{config} level
+logs when printers and classes are added, deleted, or modified and when
+configuration files are accessed or updated.  The @code{actions} level logs
+when print jobs are submitted, held, released, modified, or canceled, and
+any of the conditions for @code{config}.  The @code{all} level logs all
+requests.
 
 Defaults to @samp{actions}.
 @end deftypevr
@@ -13084,10 +13082,10 @@ Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string classification
-Specifies the security classification of the server.  Any valid banner
-name can be used, including "classified", "confidential", "secret",
-"topsecret", and "unclassified", or the banner can be omitted to disable
-secure printing functions.
+Specifies the security classification of the server.  Any valid banner name
+can be used, including "classified", "confidential", "secret", "topsecret",
+and "unclassified", or the banner can be omitted to disable secure printing
+functions.
 
 Defaults to @samp{""}.
 @end deftypevr
@@ -13118,10 +13116,10 @@ Defaults to @samp{"en"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string default-paper-size
-Specifies the default paper size for new print queues.  @samp{"Auto"}
-uses a locale-specific default, while @samp{"None"} specifies there is
-no default paper size.  Specific size names are typically
address@hidden"Letter"} or @samp{"A4"}.
+Specifies the default paper size for new print queues.  @samp{"Auto"} uses a
+locale-specific default, while @samp{"None"} specifies there is no default
+paper size.  Specific size names are typically @samp{"Letter"} or
address@hidden"A4"}.
 
 Defaults to @samp{"Auto"}.
 @end deftypevr
@@ -13148,30 +13146,29 @@ Defaults to @samp{30}.
 
 @deftypevr address@hidden parameter} error-policy error-policy
 Specifies what to do when an error occurs.  Possible values are
address@hidden, which will discard the failed print job;
address@hidden, which will retry the job at a later time;
address@hidden, which retries the failed job immediately; and
address@hidden, which stops the printer.
address@hidden, which will discard the failed print job; @code{retry-job},
+which will retry the job at a later time; @code{retry-this-job}, which
+retries the failed job immediately; and @code{stop-printer}, which stops the
+printer.
 
 Defaults to @samp{stop-printer}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer filter-limit
-Specifies the maximum cost of filters that are run concurrently, which
-can be used to minimize disk, memory, and CPU resource problems.  A
-limit of 0 disables filter limiting.  An average print to a
-non-PostScript printer needs a filter limit of about 200.  A PostScript
-printer needs about half that (100).  Setting the limit below these
-thresholds will effectively limit the scheduler to printing a single job
-at any time.
+Specifies the maximum cost of filters that are run concurrently, which can
+be used to minimize disk, memory, and CPU resource problems.  A limit of 0
+disables filter limiting.  An average print to a non-PostScript printer
+needs a filter limit of about 200.  A PostScript printer needs about half
+that (100).  Setting the limit below these thresholds will effectively limit
+the scheduler to printing a single job at any time.
 
 Defaults to @samp{0}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer filter-nice
-Specifies the scheduling priority of filters that are run to print a
-job.  The nice value ranges from 0, the highest priority, to 19, the
-lowest priority.
+Specifies the scheduling priority of filters that are run to print a job.
+The nice value ranges from 0, the highest priority, to 19, the lowest
+priority.
 
 Defaults to @samp{0}.
 @end deftypevr
@@ -13180,9 +13177,9 @@ Defaults to @samp{0}.
 Specifies whether to do reverse lookups on connecting clients.  The
 @code{double} setting causes @code{cupsd} to verify that the hostname
 resolved from the address matches one of the addresses returned for that
-hostname.  Double lookups also prevent clients with unregistered
-addresses from connecting to your server.  Only set this option to
address@hidden or @code{double} if absolutely required.
+hostname.  Double lookups also prevent clients with unregistered addresses
+from connecting to your server.  Only set this option to @code{#t} or
address@hidden if absolutely required.
 
 Defaults to @samp{#f}.
 @end deftypevr
@@ -13196,18 +13193,16 @@ Defaults to @samp{30}.
 
 @deftypevr address@hidden parameter} non-negative-integer job-retry-interval
 Specifies the interval between retries of jobs in seconds.  This is
-typically used for fax queues but can also be used with normal print
-queues whose error policy is @code{retry-job} or
address@hidden
+typically used for fax queues but can also be used with normal print queues
+whose error policy is @code{retry-job} or @code{retry-current-job}.
 
 Defaults to @samp{30}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer job-retry-limit
-Specifies the number of retries that are done for jobs.  This is
-typically used for fax queues but can also be used with normal print
-queues whose error policy is @code{retry-job} or
address@hidden
+Specifies the number of retries that are done for jobs.  This is typically
+used for fax queues but can also be used with normal print queues whose
+error policy is @code{retry-job} or @code{retry-current-job}.
 
 Defaults to @samp{5}.
 @end deftypevr
@@ -13232,21 +13227,20 @@ Defaults to @samp{0}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} multiline-string-list listen
-Listens on the specified interfaces for connections.  Valid values are
-of the form @var{address}:@var{port}, where @var{address} is either an
-IPv6 address enclosed in brackets, an IPv4 address, or @code{*} to
-indicate all addresses.  Values can also be file names of local UNIX
-domain sockets.  The Listen directive is similar to the Port directive
-but allows you to restrict access to specific interfaces or networks.
+Listens on the specified interfaces for connections.  Valid values are of
+the form @var{address}:@var{port}, where @var{address} is either an IPv6
+address enclosed in brackets, an IPv4 address, or @code{*} to indicate all
+addresses.  Values can also be file names of local UNIX domain sockets.  The
+Listen directive is similar to the Port directive but allows you to restrict
+access to specific interfaces or networks.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer listen-back-log
 Specifies the number of pending connections that will be allowed.  This
 normally only affects very busy servers that have reached the MaxClients
 limit, but can also be triggered by large numbers of simultaneous
-connections.  When the limit is reached, the operating system will
-refuse additional connections until the scheduler can accept the pending
-ones.
+connections.  When the limit is reached, the operating system will refuse
+additional connections until the scheduler can accept the pending ones.
 
 Defaults to @samp{128}.
 @end deftypevr
@@ -13288,8 +13282,8 @@ Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} access-control-list access-controls
-Access control directives, as a list of strings.  Each string should be
-one directive, such as "Order allow,deny".
+Access control directives, as a list of strings.  Each string should be one
+directive, such as "Order allow,deny".
 
 Defaults to @samp{()}.
 @end deftypevr
@@ -13297,16 +13291,16 @@ Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer log-debug-history
-Specifies the number of debugging messages that are retained for logging
-if an error occurs in a print job.  Debug messages are logged regardless
-of the LogLevel setting.
+Specifies the number of debugging messages that are retained for logging if
+an error occurs in a print job.  Debug messages are logged regardless of the
+LogLevel setting.
 
 Defaults to @samp{100}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} log-level log-level
-Specifies the level of logging for the ErrorLog file.  The value
address@hidden stops all logging while @code{debug2} logs everything.
+Specifies the level of logging for the ErrorLog file.  The value @code{none}
+stops all logging while @code{debug2} logs everything.
 
 Defaults to @samp{info}.
 @end deftypevr
@@ -13319,37 +13313,36 @@ Defaults to @samp{standard}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer max-clients
-Specifies the maximum number of simultaneous clients that are allowed by
-the scheduler.
+Specifies the maximum number of simultaneous clients that are allowed by the
+scheduler.
 
 Defaults to @samp{100}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer max-clients-per-host
-Specifies the maximum number of simultaneous clients that are allowed
-from a single address.
+Specifies the maximum number of simultaneous clients that are allowed from a
+single address.
 
 Defaults to @samp{100}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer max-copies
-Specifies the maximum number of copies that a user can print of each
-job.
+Specifies the maximum number of copies that a user can print of each job.
 
 Defaults to @samp{9999}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer max-hold-time
-Specifies the maximum time a job may remain in the @code{indefinite}
-hold state before it is canceled.  A value of 0 disables cancellation of
-held jobs.
+Specifies the maximum time a job may remain in the @code{indefinite} hold
+state before it is canceled.  A value of 0 disables cancellation of held
+jobs.
 
 Defaults to @samp{0}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer max-jobs
-Specifies the maximum number of simultaneous jobs that are allowed.  Set
-to 0 to allow an unlimited number of jobs.
+Specifies the maximum number of simultaneous jobs that are allowed.  Set to
+0 to allow an unlimited number of jobs.
 
 Defaults to @samp{500}.
 @end deftypevr
@@ -13369,8 +13362,8 @@ Defaults to @samp{0}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer max-job-time
-Specifies the maximum time a job may take to print before it is
-canceled, in seconds.  Set to 0 to disable cancellation of "stuck" jobs.
+Specifies the maximum time a job may take to print before it is canceled, in
+seconds.  Set to 0 to disable cancellation of "stuck" jobs.
 
 Defaults to @samp{10800}.
 @end deftypevr
@@ -13383,17 +13376,17 @@ Defaults to @samp{1048576}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer 
multiple-operation-timeout
-Specifies the maximum amount of time to allow between files in a
-multiple file print job, in seconds.
+Specifies the maximum amount of time to allow between files in a multiple
+file print job, in seconds.
 
 Defaults to @samp{300}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string page-log-format
 Specifies the format of PageLog lines.  Sequences beginning with percent
-(@samp{%}) characters are replaced with the corresponding information,
-while all other characters are copied literally.  The following percent
-sequences are recognized:
+(@samp{%}) characters are replaced with the corresponding information, while
+all other characters are copied literally.  The following percent sequences
+are recognized:
 
 @table @samp
 @item %%
@@ -13421,17 +13414,16 @@ insert the printer name
 insert the username
 @end table
 
-A value of the empty string disables page logging.  The string @code{%p
-%u %j %T %P %C address@hidden@} address@hidden@}
address@hidden@} address@hidden@} address@hidden@}} creates a page log with the
-standard items.
+A value of the empty string disables page logging.  The string @code{%p %u
+%j %T %P %C address@hidden@} address@hidden@} address@hidden@}
address@hidden@} address@hidden@}} creates a page log with the standard items.
 
 Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} environment-variables 
environment-variables
-Passes the specified environment variable(s) to child processes; a list
-of strings.
+Passes the specified environment variable(s) to child processes; a list of
+strings.
 
 Defaults to @samp{()}.
 @end deftypevr
@@ -13446,15 +13438,15 @@ Name of the policy.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string job-private-access
-Specifies an access list for a job's private values.  @code{@@ACL} maps
-to the printer's requesting-user-name-allowed or
-requesting-user-name-denied values.  @code{@@OWNER} maps to the job's
-owner.  @code{@@SYSTEM} maps to the groups listed for the
address@hidden field of the @code{files-config} configuration,
-which is reified into the @code{cups-files.conf(5)} file.  Other
-possible elements of the access list include specific user names, and
address@hidden@@@var{group}} to indicate members of a specific group.  The
-access list may also be simply @code{all} or @code{default}.
+Specifies an access list for a job's private values.  @code{@@ACL} maps to
+the printer's requesting-user-name-allowed or requesting-user-name-denied
+values.  @code{@@OWNER} maps to the job's owner.  @code{@@SYSTEM} maps to
+the groups listed for the @code{system-group} field of the
address@hidden configuration, which is reified into the
address@hidden(5)} file.  Other possible elements of the access list
+include specific user names, and @code{@@@var{group}} to indicate members of
+a specific group.  The access list may also be simply @code{all} or
address@hidden
 
 Defaults to @samp{"@@OWNER @@SYSTEM"}.
 @end deftypevr
@@ -13468,15 +13460,15 @@ job-originating-user-name phone"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string subscription-private-access
-Specifies an access list for a subscription's private values.
address@hidden@@ACL} maps to the printer's requesting-user-name-allowed or
+Specifies an access list for a subscription's private values.  @code{@@ACL}
+maps to the printer's requesting-user-name-allowed or
 requesting-user-name-denied values.  @code{@@OWNER} maps to the job's
 owner.  @code{@@SYSTEM} maps to the groups listed for the
address@hidden field of the @code{files-config} configuration,
-which is reified into the @code{cups-files.conf(5)} file.  Other
-possible elements of the access list include specific user names, and
address@hidden@@@var{group}} to indicate members of a specific group.  The
-access list may also be simply @code{all} or @code{default}.
address@hidden field of the @code{files-config} configuration, which is
+reified into the @code{cups-files.conf(5)} file.  Other possible elements of
+the access list include specific user names, and @code{@@@var{group}} to
+indicate members of a specific group.  The access list may also be simply
address@hidden or @code{default}.
 
 Defaults to @samp{"@@OWNER @@SYSTEM"}.
 @end deftypevr
@@ -13498,32 +13490,32 @@ Defaults to @samp{()}.
 
 @deftypevr address@hidden parameter} boolean-or-non-negative-integer 
preserve-job-files
 Specifies whether job files (documents) are preserved after a job is
-printed.  If a numeric value is specified, job files are preserved for
-the indicated number of seconds after printing.  Otherwise a boolean
-value applies indefinitely.
+printed.  If a numeric value is specified, job files are preserved for the
+indicated number of seconds after printing.  Otherwise a boolean value
+applies indefinitely.
 
 Defaults to @samp{86400}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean-or-non-negative-integer 
preserve-job-history
-Specifies whether the job history is preserved after a job is printed.
-If a numeric value is specified, the job history is preserved for the
-indicated number of seconds after printing.  If @code{#t}, the job
-history is preserved until the MaxJobs limit is reached.
+Specifies whether the job history is preserved after a job is printed.  If a
+numeric value is specified, the job history is preserved for the indicated
+number of seconds after printing.  If @code{#t}, the job history is
+preserved until the MaxJobs limit is reached.
 
 Defaults to @samp{#t}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer reload-timeout
-Specifies the amount of time to wait for job completion before
-restarting the scheduler.
+Specifies the amount of time to wait for job completion before restarting
+the scheduler.
 
 Defaults to @samp{30}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string rip-cache
-Specifies the maximum amount of memory to use when converting documents
-into bitmaps for a printer.
+Specifies the maximum amount of memory to use when converting documents into
+bitmaps for a printer.
 
 Defaults to @samp{"128m"}.
 @end deftypevr
@@ -13539,9 +13531,8 @@ The ServerAlias directive is used for HTTP Host header 
validation when
 clients connect to the scheduler from external interfaces.  Using the
 special name @code{*} can expose your system to known browser-based DNS
 rebinding attacks, even when accessing sites through a firewall.  If the
-auto-discovery of alternate names does not work, we recommend listing
-each alternate name with a ServerAlias directive instead of using
address@hidden
+auto-discovery of alternate names does not work, we recommend listing each
+alternate name with a ServerAlias directive instead of using @code{*}.
 
 Defaults to @samp{*}.
 @end deftypevr
@@ -13557,9 +13548,9 @@ Specifies what information is included in the Server 
header of HTTP
 responses.  @code{None} disables the Server header.  @code{ProductOnly}
 reports @code{CUPS}.  @code{Major} reports @code{CUPS 2}.  @code{Minor}
 reports @code{CUPS 2.0}.  @code{Minimal} reports @code{CUPS 2.0.0}.
address@hidden reports @code{CUPS 2.0.0 (@var{uname})} where @var{uname} is
-the output of the @code{uname} command.  @code{Full} reports @code{CUPS
-2.0.0 (@var{uname}) IPP/2.0}.
address@hidden reports @code{CUPS 2.0.0 (@var{uname})} where @var{uname} is the
+output of the @code{uname} command.  @code{Full} reports @code{CUPS 2.0.0
+(@var{uname}) IPP/2.0}.
 
 Defaults to @samp{Minimal}.
 @end deftypevr
@@ -13571,28 +13562,28 @@ Defaults to @samp{"variable value"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} multiline-string-list ssl-listen
-Listens on the specified interfaces for encrypted connections.  Valid
-values are of the form @var{address}:@var{port}, where @var{address} is
-either an IPv6 address enclosed in brackets, an IPv4 address, or
address@hidden to indicate all addresses.
+Listens on the specified interfaces for encrypted connections.  Valid values
+are of the form @var{address}:@var{port}, where @var{address} is either an
+IPv6 address enclosed in brackets, an IPv4 address, or @code{*} to indicate
+all addresses.
 
 Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} ssl-options ssl-options
-Sets encryption options.  By default, CUPS only supports encryption
-using TLS v1.0 or higher using known secure cipher suites.  The
address@hidden option enables the 128-bit RC4 cipher suites, which are
-required for some older clients that do not implement newer ones.  The
address@hidden option enables SSL v3.0, which is required for some
-older clients that do not support TLS v1.0.
+Sets encryption options.  By default, CUPS only supports encryption using
+TLS v1.0 or higher using known secure cipher suites.  The @code{AllowRC4}
+option enables the 128-bit RC4 cipher suites, which are required for some
+older clients that do not implement newer ones.  The @code{AllowSSL3} option
+enables SSL v3.0, which is required for some older clients that do not
+support TLS v1.0.
 
 Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean strict-conformance?
-Specifies whether the scheduler requires clients to strictly adhere to
-the IPP specifications.
+Specifies whether the scheduler requires clients to strictly adhere to the
+IPP specifications.
 
 Defaults to @samp{#f}.
 @end deftypevr
@@ -13610,8 +13601,8 @@ Specifies whether the web interface is enabled.
 Defaults to @samp{#f}.
 @end deftypevr
 
-At this point you're probably thinking ``oh dear, Guix manual, I like
-you but you can stop already with the configuration options''.  Indeed.
+At this point you're probably thinking ``oh dear, Guix manual, I like you
+but you can stop already with the configuration options''.  Indeed.
 However, one more point: it could be that you have an existing
 @code{cupsd.conf} that you want to use.  In that case, you can pass an
 @code{opaque-cups-configuration} as the configuration of a
@@ -13632,8 +13623,7 @@ The contents of the @code{cups-files.conf} file, as a 
string.
 @end deftypevr
 
 For example, if your @code{cupsd.conf} and @code{cups-files.conf} are in
-strings of the same name, you could instantiate a CUPS service like
-this:
+strings of the same name, you could instantiate a CUPS service like this:
 
 @example
 (service cups-service-type
@@ -13643,87 +13633,84 @@ this:
 @end example
 
 
address@hidden Desktop Services
address@hidden Desktop Services
address@hidden Desktop-Dienste
address@hidden Desktop-Dienste
 
-The @code{(gnu services desktop)} module provides services that are
-usually useful in the context of a ``desktop'' setup---that is, on a
-machine running a graphical display server, possibly with graphical user
-interfaces, etc.  It also defines services that provide specific desktop
-environments like GNOME, XFCE or MATE.
+The @code{(gnu services desktop)} module provides services that are usually
+useful in the context of a ``desktop'' setup---that is, on a machine running
+a graphical display server, possibly with graphical user interfaces, etc.
+It also defines services that provide specific desktop environments like
+GNOME, XFCE or MATE.
 
 To simplify things, the module defines a variable containing the set of
 services that users typically expect on a machine with a graphical
 environment and networking:
 
 @defvr {Scheme Variable} %desktop-services
-This is a list of services that builds upon @var{%base-services} and
-adds or adjusts services for a typical ``desktop'' setup.
+This is a list of services that builds upon @var{%base-services} and adds or
+adjusts services for a typical ``desktop'' setup.
 
 In particular, it adds a graphical login manager (@pxref{X Window,
 @code{slim-service}}), screen lockers, a network management tool
-(@pxref{Networking Services, @code{network-manager-service-type}}), energy and 
color
-management services, the @code{elogind} login and seat manager, the
-Polkit privilege service, the GeoClue location service, the
-AccountsService daemon that allows authorized users change system
-passwords, an NTP client (@pxref{Networking Services}), the Avahi
-daemon, and has the name service switch service configured to be able to
-use @code{nss-mdns} (@pxref{Name Service Switch, mDNS}).
+(@pxref{Netzwerkdienste, @code{network-manager-service-type}}), energy
+and color management services, the @code{elogind} login and seat manager,
+the Polkit privilege service, the GeoClue location service, the
+AccountsService daemon that allows authorized users change system passwords,
+an NTP client (@pxref{Netzwerkdienste}), the Avahi daemon, and has the
+name service switch service configured to be able to use @code{nss-mdns}
+(@pxref{Name Service Switch, mDNS}).
 @end defvr
 
 The @var{%desktop-services} variable can be used as the @code{services}
-field of an @code{operating-system} declaration (@pxref{operating-system
-Reference, @code{services}}).
-
-Additionally, the @code{gnome-desktop-service},
address@hidden, @code{mate-desktop-service} and
address@hidden procedures can add GNOME, XFCE, MATE
-and/or Enlightenment to a system.  To ``add GNOME'' means that system-level
-services like the backlight adjustment helpers and the power management
-utilities are added to the system, extending @code{polkit} and @code{dbus}
-appropriately, allowing GNOME to operate with elevated privileges on a
-limited number of special-purpose system interfaces.  Additionally,
-adding a service made by @code{gnome-desktop-service} adds the GNOME
-metapackage to the system profile.  Likewise, adding the XFCE service
-not only adds the @code{xfce} metapackage to the system profile, but it
-also gives the Thunar file manager the ability to open a ``root-mode''
-file management window, if the user authenticates using the
-administrator's password via the standard polkit graphical interface.
-To ``add MATE'' means that @code{polkit} and @code{dbus} are extended
-appropriately, allowing MATE to operate with elevated privileges on a
-limited number of special-purpose system interfaces.  Additionally,
-adding a service made by @code{mate-desktop-service} adds the MATE
-metapackage to the system profile.  ``Adding ENLIGHTENMENT'' means that
address@hidden is extended appropriately, and several of Enlightenment's 
binaries
-are set as setuid, allowing Enlightenment's screen locker and other
-functionality to work as expetected.
-
-The desktop environments in Guix use the Xorg display server by
-default.  If you'd like to use the newer display server protocol
-called Wayland, you need to use the @code{sddm-service} instead of the
address@hidden for the graphical login manager.  You should then
-select the ``GNOME (Wayland)'' session in SDDM.  Alternatively you can
-also try starting GNOME on Wayland manually from a TTY with the
-command ``XDG_SESSION_TYPE=wayland exec dbus-run-session
-gnome-session``.  Currently only GNOME has support for Wayland.
+field of an @code{operating-system} declaration 
(@pxref{„operating-system“-Referenz, @code{services}}).
+
+Additionally, the @code{gnome-desktop-service}, @code{xfce-desktop-service},
address@hidden and @code{enlightenment-desktop-service-type}
+procedures can add GNOME, XFCE, MATE and/or Enlightenment to a system.  To
+``add GNOME'' means that system-level services like the backlight adjustment
+helpers and the power management utilities are added to the system,
+extending @code{polkit} and @code{dbus} appropriately, allowing GNOME to
+operate with elevated privileges on a limited number of special-purpose
+system interfaces.  Additionally, adding a service made by
address@hidden adds the GNOME metapackage to the system
+profile.  Likewise, adding the XFCE service not only adds the @code{xfce}
+metapackage to the system profile, but it also gives the Thunar file manager
+the ability to open a ``root-mode'' file management window, if the user
+authenticates using the administrator's password via the standard polkit
+graphical interface.  To ``add MATE'' means that @code{polkit} and
address@hidden are extended appropriately, allowing MATE to operate with
+elevated privileges on a limited number of special-purpose system
+interfaces.  Additionally, adding a service made by
address@hidden adds the MATE metapackage to the system
+profile.  ``Adding ENLIGHTENMENT'' means that @code{dbus} is extended
+appropriately, and several of Enlightenment's binaries are set as setuid,
+allowing Enlightenment's screen locker and other functionality to work as
+expetected.
+
+The desktop environments in Guix use the Xorg display server by default.  If
+you'd like to use the newer display server protocol called Wayland, you need
+to use the @code{sddm-service} instead of the @code{slim-service} for the
+graphical login manager.  You should then select the ``GNOME (Wayland)''
+session in SDDM.  Alternatively you can also try starting GNOME on Wayland
+manually from a TTY with the command ``XDG_SESSION_TYPE=wayland exec
+dbus-run-session gnome-session``.  Currently only GNOME has support for
+Wayland.
 
 @deffn {Scheme Procedure} gnome-desktop-service
-Return a service that adds the @code{gnome} package to the system
-profile, and extends polkit with the actions from
address@hidden
+Return a service that adds the @code{gnome} package to the system profile,
+and extends polkit with the actions from @code{gnome-settings-daemon}.
 @end deffn
 
 @deffn {Scheme Procedure} xfce-desktop-service
 Return a service that adds the @code{xfce} package to the system profile,
-and extends polkit with the ability for @code{thunar} to manipulate the
-file system as root from within a user session, after the user has
-authenticated with the administrator's password.
+and extends polkit with the ability for @code{thunar} to manipulate the file
+system as root from within a user session, after the user has authenticated
+with the administrator's password.
 @end deffn
 
 @deffn {Scheme Procedure} mate-desktop-service
-Return a service that adds the @code{mate} package to the system
-profile, and extends polkit with the actions from
address@hidden
+Return a service that adds the @code{mate} package to the system profile,
+and extends polkit with the actions from @code{mate-settings-daemon}.
 @end deffn
 
 @deffn {Scheme Procedure} enlightenment-desktop-service-type
@@ -13739,8 +13726,8 @@ The enlightenment package to use.
 @end deftp
 
 Because the GNOME, XFCE and MATE desktop services pull in so many packages,
-the default @code{%desktop-services} variable doesn't include any of
-them by default.  To add GNOME, XFCE or MATE, just @code{cons} them onto
+the default @code{%desktop-services} variable doesn't include any of them by
+default.  To add GNOME, XFCE or MATE, just @code{cons} them onto
 @code{%desktop-services} in the @code{services} field of your
 @code{operating-system}:
 
@@ -13760,8 +13747,8 @@ These desktop environments will then be available as 
options in the
 graphical login window.
 
 The actual service definitions included in @code{%desktop-services} and
-provided by @code{(gnu services dbus)} and @code{(gnu services desktop)}
-are described below.
+provided by @code{(gnu services dbus)} and @code{(gnu services desktop)} are
+described below.
 
 @deffn {Scheme Procedure} dbus-service [#:dbus @var{dbus}] [#:services '()]
 Return a service that runs the ``system bus'', using @var{dbus}, with
@@ -13772,26 +13759,26 @@ facility.  Its system bus is used to allow system 
services to communicate
 and to be notified of system-wide events.
 
 @var{services} must be a list of packages that provide an
address@hidden/dbus-1/system.d} directory containing additional D-Bus 
configuration
-and policy files.  For example, to allow avahi-daemon to use the system bus,
address@hidden must be equal to @code{(list avahi)}.
address@hidden/dbus-1/system.d} directory containing additional D-Bus
+configuration and policy files.  For example, to allow avahi-daemon to use
+the system bus, @var{services} must be equal to @code{(list avahi)}.
 @end deffn
 
 @deffn {Scheme Procedure} elogind-service [#:config @var{config}]
-Return a service that runs the @code{elogind} login and
-seat management daemon.  @uref{https://github.com/elogind/elogind,
-Elogind} exposes a D-Bus interface that can be used to know which users
-are logged in, know what kind of sessions they have open, suspend the
-system, inhibit system suspend, reboot the system, and other tasks.
-
-Elogind handles most system-level power events for a computer, for
-example suspending the system when a lid is closed, or shutting it down
-when the power button is pressed.
-
-The @var{config} keyword argument specifies the configuration for
-elogind, and should be the result of an @code{(elogind-configuration
-(@var{parameter} @var{value})...)} invocation.  Available parameters and
-their default values are:
+Return a service that runs the @code{elogind} login and seat management
+daemon.  @uref{https://github.com/elogind/elogind, Elogind} exposes a D-Bus
+interface that can be used to know which users are logged in, know what kind
+of sessions they have open, suspend the system, inhibit system suspend,
+reboot the system, and other tasks.
+
+Elogind handles most system-level power events for a computer, for example
+suspending the system when a lid is closed, or shutting it down when the
+power button is pressed.
+
+The @var{config} keyword argument specifies the configuration for elogind,
+and should be the result of an @code{(elogind-configuration (@var{parameter}
address@hidden)...)} invocation.  Available parameters and their default values
+are:
 
 @table @code
 @item kill-user-processes?
@@ -13848,11 +13835,11 @@ their default values are:
 @end deffn
 
 @deffn {Scheme Procedure} accountsservice-service @
-       [#:accountsservice @var{accountsservice}]
-Return a service that runs AccountsService, a system service that can
-list available accounts, change their passwords, and so on.
-AccountsService integrates with PolicyKit to enable unprivileged users
-to acquire the capability to modify their system configuration.
+       [#:accountsservice @var{accountsservice}] Return a service that runs
+AccountsService, a system service that can list available accounts, change
+their passwords, and so on.  AccountsService integrates with PolicyKit to
+enable unprivileged users to acquire the capability to modify their system
+configuration.
 @uref{https://www.freedesktop.org/wiki/Software/AccountsService/, the
 accountsservice web site} for more information.
 
@@ -13861,33 +13848,26 @@ package to expose as a service.
 @end deffn
 
 @deffn {Scheme Procedure} polkit-service @
-                         [#:polkit @var{polkit}]
-Return a service that runs the
+                         [#:polkit @var{polkit}] Return a service that runs the
 @uref{http://www.freedesktop.org/wiki/Software/polkit/, Polkit privilege
 management service}, which allows system administrators to grant access to
-privileged operations in a structured way.  By querying the Polkit service, a
-privileged system component can know when it should grant additional
-capabilities to ordinary users.  For example, an ordinary user can be granted
-the capability to suspend the system if the user is logged in locally.
+privileged operations in a structured way.  By querying the Polkit service,
+a privileged system component can know when it should grant additional
+capabilities to ordinary users.  For example, an ordinary user can be
+granted the capability to suspend the system if the user is logged in
+locally.
 @end deffn
 
 @deffn {Scheme Procedure} upower-service [#:upower @var{upower}] @
-                         [#:watts-up-pro? #f] @
-                         [#:poll-batteries? #t] @
-                         [#:ignore-lid? #f] @
-                         [#:use-percentage-for-policy? #f] @
-                         [#:percentage-low 10] @
-                         [#:percentage-critical 3] @
-                         [#:percentage-action 2] @
-                         [#:time-low 1200] @
-                         [#:time-critical 300] @
-                         [#:time-action 120] @
-                         [#:critical-power-action 'hybrid-sleep]
-Return a service that runs @uref{http://upower.freedesktop.org/,
address@hidden, a system-wide monitor for power consumption and battery
-levels, with the given configuration settings.  It implements the
address@hidden D-Bus interface, and is notably used by
-GNOME.
+                         [#:watts-up-pro? #f] @ [#:poll-batteries? #t] @ 
[#:ignore-lid? #f] @
+[#:use-percentage-for-policy? #f] @ [#:percentage-low 10] @
+[#:percentage-critical 3] @ [#:percentage-action 2] @ [#:time-low 1200] @
+[#:time-critical 300] @ [#:time-action 120] @ [#:critical-power-action
+'hybrid-sleep] Return a service that runs
address@hidden://upower.freedesktop.org/, @command{upowerd}}, a system-wide
+monitor for power consumption and battery levels, with the given
+configuration settings.  It implements the @code{org.freedesktop.UPower}
+D-Bus interface, and is notably used by GNOME.
 @end deffn
 
 @deffn {Scheme Procedure} udisks-service [#:udisks @var{udisks}]
@@ -13900,59 +13880,56 @@ include the @command{udisksctl} command, part of 
UDisks, and GNOME Disks.
 @deffn {Scheme Procedure} colord-service [#:colord @var{colord}]
 Return a service that runs @command{colord}, a system service with a D-Bus
 interface to manage the color profiles of input and output devices such as
-screens and scanners.  It is notably used by the GNOME Color Manager graphical
-tool.  See @uref{http://www.freedesktop.org/software/colord/, the colord web
-site} for more information.
+screens and scanners.  It is notably used by the GNOME Color Manager
+graphical tool.  See @uref{http://www.freedesktop.org/software/colord/, the
+colord web site} for more information.
 @end deffn
 
 @deffn {Scheme Procedure} geoclue-application name [#:allowed? #t] [#:system? 
#f] [#:users '()]
-Return a configuration allowing an application to access GeoClue
-location data.  @var{name} is the Desktop ID of the application, without
-the @code{.desktop} part.  If @var{allowed?} is true, the application
-will have access to location information by default.  The boolean
address@hidden  value indicates whether an application is a system component
-or not.  Finally @var{users} is a list of UIDs of all users for which
-this application is allowed location info access.  An empty users list
-means that all users are allowed.
+Return a configuration allowing an application to access GeoClue location
+data.  @var{name} is the Desktop ID of the application, without the
address@hidden part.  If @var{allowed?} is true, the application will have
+access to location information by default.  The boolean @var{system?} value
+indicates whether an application is a system component or not.  Finally
address@hidden is a list of UIDs of all users for which this application is
+allowed location info access.  An empty users list means that all users are
+allowed.
 @end deffn
 
 @defvr {Scheme Variable} %standard-geoclue-applications
-The standard list of well-known GeoClue application configurations,
-granting authority to the GNOME date-and-time utility to ask for the
-current location in order to set the time zone, and allowing the
-IceCat and Epiphany web browsers to request location information.
-IceCat and Epiphany both query the user before allowing a web page to
-know the user's location.
+The standard list of well-known GeoClue application configurations, granting
+authority to the GNOME date-and-time utility to ask for the current location
+in order to set the time zone, and allowing the IceCat and Epiphany web
+browsers to request location information.  IceCat and Epiphany both query
+the user before allowing a web page to know the user's location.
 @end defvr
 
 @deffn {Scheme Procedure} geoclue-service [#:colord @var{colord}] @
-                         [#:whitelist '()] @
-                         [#:wifi-geolocation-url 
"https://location.services.mozilla.com/v1/geolocate?key=geoclue";] @
-                         [#:submit-data? #f]
-                         [#:wifi-submission-url 
"https://location.services.mozilla.com/v1/submit?key=geoclue";] @
-                         [#:submission-nick "geoclue"] @
-                         [#:applications %standard-geoclue-applications]
-Return a service that runs the GeoClue location service.  This service
-provides a D-Bus interface to allow applications to request access to a
-user's physical location, and optionally to add information to online
-location databases.  See
address@hidden://wiki.freedesktop.org/www/Software/GeoClue/, the GeoClue
-web site} for more information.
+                         [#:whitelist '()] @ [#:wifi-geolocation-url
+"https://location.services.mozilla.com/v1/geolocate?key=geoclue";] @
+[#:submit-data? #f] [#:wifi-submission-url
+"https://location.services.mozilla.com/v1/submit?key=geoclue";] @
+[#:submission-nick "geoclue"] @ [#:applications
+%standard-geoclue-applications] Return a service that runs the GeoClue
+location service.  This service provides a D-Bus interface to allow
+applications to request access to a user's physical location, and optionally
+to add information to online location databases.  See
address@hidden://wiki.freedesktop.org/www/Software/GeoClue/, the GeoClue web
+site} for more information.
 @end deffn
 
 @deffn {Scheme Procedure} bluetooth-service [#:bluez @var{bluez}] @
-       address@hidden:auto-enable? #f}]
-Return a service that runs the @command{bluetoothd} daemon, which
-manages all the Bluetooth devices and provides a number of D-Bus
-interfaces.  When AUTO-ENABLE? is true, the bluetooth controller is
-powered automatically at boot, which can be useful when using a
-bluetooth keyboard or mouse.
+       address@hidden:auto-enable? #f}] Return a service that runs the 
@command{bluetoothd}
+daemon, which manages all the Bluetooth devices and provides a number of
+D-Bus interfaces.  When AUTO-ENABLE? is true, the bluetooth controller is
+powered automatically at boot, which can be useful when using a bluetooth
+keyboard or mouse.
 
 Users need to be in the @code{lp} group to access the D-Bus service.
 @end deffn
 
address@hidden Sound Services
address@hidden Sound Services
address@hidden Tondienste
address@hidden Tondienste
 
 @cindex sound support
 @cindex ALSA
@@ -13963,10 +13940,10 @@ Advanced Linux Sound Architecture (ALSA) system, 
which making PulseAudio the
 preferred ALSA output driver.
 
 @deffn {Scheme Variable} alsa-service-type
-This is the type for the @uref{https://alsa-project.org/, Advanced Linux Sound
-Architecture} (ALSA) system, which generates the @file{/etc/asound.conf}
-configuration file.  The value for this type is a @command{alsa-configuration}
-record as in this example:
+This is the type for the @uref{https://alsa-project.org/, Advanced Linux
+Sound Architecture} (ALSA) system, which generates the
address@hidden/etc/asound.conf} configuration file.  The value for this type is 
a
address@hidden record as in this example:
 
 @example
 (service alsa-service-type)
@@ -13986,9 +13963,9 @@ Data type representing the configuration for 
@code{alsa-service}.
 Whether ALSA applications should transparently be made to use the
 @uref{http://www.pulseaudio.org/, PulseAudio} sound server.
 
-Using PulseAudio allows you to run several sound-producing applications
-at the same time and to individual control them @i{via}
address@hidden, among other things.
+Using PulseAudio allows you to run several sound-producing applications at
+the same time and to individual control them @i{via} @command{pavucontrol},
+among other things.
 
 @item @code{extra-options} (default: @var{""})
 String to append to the @file{/etc/asound.conf} file.
@@ -13996,8 +13973,8 @@ String to append to the @file{/etc/asound.conf} file.
 @end table
 @end deftp
 
-Individual users who want to override the system configuration of ALSA can do
-it with the @file{~/.asoundrc} file:
+Individual users who want to override the system configuration of ALSA can
+do it with the @file{~/.asoundrc} file:
 
 @example
 # In guix, we have to specify the absolute path for plugins.
@@ -14032,27 +14009,27 @@ See 
@uref{https://www.alsa-project.org/main/index.php/Asoundrc} for the
 details.
 
 
address@hidden Database Services
address@hidden Database Services
address@hidden Datenbankdienste
address@hidden Datenbankdienste
 
 @cindex database
 @cindex SQL
 The @code{(gnu services databases)} module provides the following services.
 
 @deffn {Scheme Procedure} postgresql-service [#:postgresql postgresql] @
-       [#:config-file] [#:data-directory ``/var/lib/postgresql/data''] @
-       [#:port 5432] [#:locale ``en_US.utf8'']
-Return a service that runs @var{postgresql}, the PostgreSQL database
-server.
-
-The PostgreSQL daemon loads its runtime configuration from @var{config-file},
-creates a database cluster with @var{locale} as the default
-locale, stored in @var{data-directory}.  It then listens on @var{port}.
+       [#:config-file] [#:data-directory ``/var/lib/postgresql/data''] @ 
[#:port
+5432] [#:locale ``en_US.utf8''] Return a service that runs @var{postgresql},
+the PostgreSQL database server.
+
+The PostgreSQL daemon loads its runtime configuration from
address@hidden, creates a database cluster with @var{locale} as the
+default locale, stored in @var{data-directory}.  It then listens on
address@hidden
 @end deffn
 
 @deffn {Scheme Procedure} mysql-service [#:config (mysql-configuration)]
-Return a service that runs @command{mysqld}, the MySQL or MariaDB
-database server.
+Return a service that runs @command{mysqld}, the MySQL or MariaDB database
+server.
 
 The optional @var{config} argument specifies the configuration for
 @command{mysqld}, which should be a @code{<mysql-configuration>} object.
@@ -14063,8 +14040,8 @@ Data type representing the configuration of 
@var{mysql-service}.
 
 @table @asis
 @item @code{mysql} (default: @var{mariadb})
-Package object of the MySQL database server, can be either @var{mariadb}
-or @var{mysql}.
+Package object of the MySQL database server, can be either @var{mariadb} or
address@hidden
 
 For MySQL, a temporary root password will be displayed at activation time.
 For MariaDB, the root password is empty.
@@ -14075,9 +14052,9 @@ TCP port on which the database server listens for 
incoming connections.
 @end deftp
 
 @defvr {Scheme Variable} memcached-service-type
-This is the service type for the @uref{https://memcached.org/,
-Memcached} service, which provides a distributed in memory cache.  The
-value for the service type is a @code{memcached-configuration} object.
+This is the service type for the @uref{https://memcached.org/, Memcached}
+service, which provides a distributed in memory cache.  The value for the
+service type is a @code{memcached-configuration} object.
 @end defvr
 
 @example
@@ -14107,8 +14084,8 @@ Additional command line options to pass to 
@code{memcached}.
 @end deftp
 
 @defvr {Scheme Variable} mongodb-service-type
-This is the service type for @uref{https://www.mongodb.com/, MongoDB}.
-The value for the service type is a @code{mongodb-configuration} object.
+This is the service type for @uref{https://www.mongodb.com/, MongoDB}.  The
+value for the service type is a @code{mongodb-configuration} object.
 @end defvr
 
 @example
@@ -14126,15 +14103,15 @@ The MongoDB package to use.
 The configuration file for MongoDB.
 
 @item @code{data-directory} (default: @code{"/var/lib/mongodb"})
-This value is used to create the directory, so that it exists and is
-owned by the mongodb user.  It should match the data-directory which
-MongoDB is configured to use through the configuration file.
+This value is used to create the directory, so that it exists and is owned
+by the mongodb user.  It should match the data-directory which MongoDB is
+configured to use through the configuration file.
 @end table
 @end deftp
 
 @defvr {Scheme Variable} redis-service-type
-This is the service type for the @uref{https://redis.io/, Redis}
-key/value store, whose value is a @code{redis-configuration} object.
+This is the service type for the @uref{https://redis.io/, Redis} key/value
+store, whose value is a @code{redis-configuration} object.
 @end defvr
 
 @deftp {Data Type} redis-configuration
@@ -14148,23 +14125,23 @@ The Redis package to use.
 Network interface on which to listen.
 
 @item @code{port} (default: @code{6379})
-Port on which to accept connections on, a value of 0 will disable
-listening on a TCP socket.
+Port on which to accept connections on, a value of 0 will disable listening
+on a TCP socket.
 
 @item @code{working-directory} (default: @code{"/var/lib/redis"})
 Directory in which to store the database and related files.
 @end table
 @end deftp
 
address@hidden Mail Services
address@hidden Mail Services
address@hidden Mail-Dienste
address@hidden Mail-Dienste
 
 @cindex mail
 @cindex email
-The @code{(gnu services mail)} module provides Guix service definitions
-for email services: IMAP, POP3, and LMTP servers, as well as mail
-transport agents (MTAs).  Lots of acronyms!  These services are detailed
-in the subsections below.
+The @code{(gnu services mail)} module provides Guix service definitions for
+email services: IMAP, POP3, and LMTP servers, as well as mail transport
+agents (MTAs).  Lots of acronyms! These services are detailed in the
+subsections below.
 
 @subsubheading Dovecot Service
 
@@ -14173,16 +14150,16 @@ Return a service that runs the Dovecot IMAP/POP3/LMTP 
mail server.
 @end deffn
 
 By default, Dovecot does not need much configuration; the default
-configuration object created by @code{(dovecot-configuration)} will
-suffice if your mail is delivered to @code{~/Maildir}.  A self-signed
-certificate will be generated for TLS-protected connections, though
-Dovecot will also listen on cleartext ports by default.  There are a
-number of options, though, which mail administrators might need to change,
-and as is the case with other services, Guix allows the system
-administrator to specify these parameters via a uniform Scheme interface.
+configuration object created by @code{(dovecot-configuration)} will suffice
+if your mail is delivered to @code{~/Maildir}.  A self-signed certificate
+will be generated for TLS-protected connections, though Dovecot will also
+listen on cleartext ports by default.  There are a number of options,
+though, which mail administrators might need to change, and as is the case
+with other services, Guix allows the system administrator to specify these
+parameters via a uniform Scheme interface.
 
-For example, to specify that mail is located at @code{maildir~/.mail},
-one would instantiate the Dovecot service like this:
+For example, to specify that mail is located at @code{maildir~/.mail}, one
+would instantiate the Dovecot service like this:
 
 @example
 (dovecot-service #:config
@@ -14190,12 +14167,12 @@ one would instantiate the Dovecot service like this:
                   (mail-location "maildir:~/.mail")))
 @end example
 
-The available configuration parameters follow.  Each parameter
-definition is preceded by its type; for example, @samp{string-list foo}
-indicates that the @code{foo} parameter should be specified as a list of
-strings.  There is also a way to specify the configuration as a string,
-if you have an old @code{dovecot.conf} file that you want to port over
-from some other system; see the end for more details.
+The available configuration parameters follow.  Each parameter definition is
+preceded by its type; for example, @samp{string-list foo} indicates that the
address@hidden parameter should be specified as a list of strings.  There is
+also a way to specify the configuration as a string, if you have an old
address@hidden file that you want to port over from some other system;
+see the end for more details.
 
 @c The following documentation was initially generated by
 @c (generate-documentation) in (gnu services mail).  Manually maintained
@@ -14212,11 +14189,11 @@ The dovecot package.
 @end deftypevr
 
 @deftypevr address@hidden parameter} comma-separated-string-list listen
-A list of IPs or hosts where to listen for connections.  @samp{*}
-listens on all IPv4 interfaces, @samp{::} listens on all IPv6
-interfaces.  If you want to specify non-default ports or anything more
-complex, customize the address and port fields of the
address@hidden of the specific services you are interested in.
+A list of IPs or hosts where to listen for connections.  @samp{*} listens on
+all IPv4 interfaces, @samp{::} listens on all IPv6 interfaces.  If you want
+to specify non-default ports or anything more complex, customize the address
+and port fields of the @samp{inet-listener} of the specific services you are
+interested in.
 @end deftypevr
 
 @deftypevr address@hidden parameter} protocol-configuration-list protocols
@@ -14230,9 +14207,9 @@ The name of the protocol.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-socket-path
-UNIX socket path to the master authentication server to find users.
-This is used by imap (for shared users) and lda.
-It defaults to @samp{"/var/run/dovecot/auth-userdb"}.
+UNIX socket path to the master authentication server to find users.  This is
+used by imap (for shared users) and lda.  It defaults to
address@hidden"/var/run/dovecot/auth-userdb"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list mail-plugins
@@ -14240,9 +14217,8 @@ Space separated list of plugins to load.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer 
mail-max-userip-connections
-Maximum number of IMAP connections allowed for a user from each IP
-address.  NOTE: The username is compared case-sensitively.
-Defaults to @samp{10}.
+Maximum number of IMAP connections allowed for a user from each IP address.
+NOTE: The username is compared case-sensitively.  Defaults to @samp{10}.
 @end deftypevr
 
 @end deftypevr
@@ -14255,17 +14231,16 @@ List of services to enable.  Available services 
include @samp{imap},
 Available @code{service-configuration} fields are:
 
 @deftypevr address@hidden parameter} string kind
-The service kind.  Valid values include @code{director},
address@hidden, @code{pop3-login}, @code{lmtp}, @code{imap},
address@hidden, @code{auth}, @code{auth-worker}, @code{dict},
address@hidden, @code{quota-warning}, or anything else.
+The service kind.  Valid values include @code{director}, @code{imap-login},
address@hidden, @code{lmtp}, @code{imap}, @code{pop3}, @code{auth},
address@hidden, @code{dict}, @code{tcpwrap}, @code{quota-warning}, or
+anything else.
 @end deftypevr
 
 @deftypevr address@hidden parameter} listener-configuration-list listeners
 Listeners for the service.  A listener is either a
 @code{unix-listener-configuration}, a @code{fifo-listener-configuration}, or
-an @code{inet-listener-configuration}.
-Defaults to @samp{()}.
+an @code{inet-listener-configuration}.  Defaults to @samp{()}.
 
 Available @code{unix-listener-configuration} fields are:
 
@@ -14275,18 +14250,15 @@ the section name.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mode
-The access mode for the socket.
-Defaults to @samp{"0600"}.
+The access mode for the socket.  Defaults to @samp{"0600"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string user
-The user to own the socket.
-Defaults to @samp{""}.
+The user to own the socket.  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string group
-The group to own the socket.
-Defaults to @samp{""}.
+The group to own the socket.  Defaults to @samp{""}.
 @end deftypevr
 
 
@@ -14298,18 +14270,15 @@ the section name.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mode
-The access mode for the socket.
-Defaults to @samp{"0600"}.
+The access mode for the socket.  Defaults to @samp{"0600"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string user
-The user to own the socket.
-Defaults to @samp{""}.
+The user to own the socket.  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string group
-The group to own the socket.
-Defaults to @samp{""}.
+The group to own the socket.  Defaults to @samp{""}.
 @end deftypevr
 
 
@@ -14320,8 +14289,8 @@ The protocol to listen for.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string address
-The address on which to listen, or empty for all addresses.
-Defaults to @samp{""}.
+The address on which to listen, or empty for all addresses.  Defaults to
address@hidden""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer port
@@ -14330,41 +14299,37 @@ The port on which to listen.
 
 @deftypevr address@hidden parameter} boolean ssl?
 Whether to use SSL for this service; @samp{yes}, @samp{no}, or
address@hidden
-Defaults to @samp{#t}.
address@hidden  Defaults to @samp{#t}.
 @end deftypevr
 
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer service-count
-Number of connections to handle before starting a new process.
-Typically the only useful values are 0 (unlimited) or 1.  1 is more
-secure, but 0 is faster.  <doc/wiki/LoginProcess.txt>.
-Defaults to @samp{1}.
+Number of connections to handle before starting a new process.  Typically
+the only useful values are 0 (unlimited) or 1.  1 is more secure, but 0 is
+faster.  <doc/wiki/LoginProcess.txt>.  Defaults to @samp{1}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer process-min-avail
-Number of processes to always keep waiting for more connections.
-Defaults to @samp{0}.
+Number of processes to always keep waiting for more connections.  Defaults
+to @samp{0}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer vsz-limit
-If you set @samp{service-count 0}, you probably need to grow
-this.
-Defaults to @samp{256000000}.
+If you set @samp{service-count 0}, you probably need to grow this.  Defaults
+to @samp{256000000}.
 @end deftypevr
 
 @end deftypevr
 
 @deftypevr address@hidden parameter} dict-configuration dict
-Dict configuration, as created by the @code{dict-configuration}
-constructor.
+Dict configuration, as created by the @code{dict-configuration} constructor.
 
 Available @code{dict-configuration} fields are:
 
 @deftypevr address@hidden parameter} free-form-fields entries
-A list of key-value pairs that this dict should hold.
-Defaults to @samp{()}.
+A list of key-value pairs that this dict should hold.  Defaults to
address@hidden()}.
 @end deftypevr
 
 @end deftypevr
@@ -14376,15 +14341,14 @@ A list of passdb configurations, each one created by 
the
 Available @code{passdb-configuration} fields are:
 
 @deftypevr address@hidden parameter} string driver
-The driver that the passdb should use.  Valid values include
address@hidden, @samp{passwd}, @samp{shadow}, @samp{bsdauth}, and
address@hidden
-Defaults to @samp{"pam"}.
+The driver that the passdb should use.  Valid values include @samp{pam},
address@hidden, @samp{shadow}, @samp{bsdauth}, and @samp{static}.  Defaults
+to @samp{"pam"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list args
-Space separated list of arguments to the passdb driver.
-Defaults to @samp{""}.
+Space separated list of arguments to the passdb driver.  Defaults to
address@hidden""}.
 @end deftypevr
 
 @end deftypevr
@@ -14396,19 +14360,17 @@ List of userdb configurations, each one created by the
 Available @code{userdb-configuration} fields are:
 
 @deftypevr address@hidden parameter} string driver
-The driver that the userdb should use.  Valid values include
address@hidden and @samp{static}.
-Defaults to @samp{"passwd"}.
+The driver that the userdb should use.  Valid values include @samp{passwd}
+and @samp{static}.  Defaults to @samp{"passwd"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list args
-Space separated list of arguments to the userdb driver.
-Defaults to @samp{""}.
+Space separated list of arguments to the userdb driver.  Defaults to
address@hidden""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} free-form-args override-fields
-Override fields from passwd.
-Defaults to @samp{()}.
+Override fields from passwd.  Defaults to @samp{()}.
 @end deftypevr
 
 @end deftypevr
@@ -14429,64 +14391,56 @@ Name for this namespace.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string type
-Namespace type: @samp{private}, @samp{shared} or @samp{public}.
-Defaults to @samp{"private"}.
+Namespace type: @samp{private}, @samp{shared} or @samp{public}.  Defaults to
address@hidden"private"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string separator
-Hierarchy separator to use. You should use the same separator for
-all namespaces or some clients get confused.  @samp{/} is usually a good
-one.  The default however depends on the underlying mail storage
-format.
-Defaults to @samp{""}.
+Hierarchy separator to use. You should use the same separator for all
+namespaces or some clients get confused.  @samp{/} is usually a good one.
+The default however depends on the underlying mail storage format.  Defaults
+to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string prefix
-Prefix required to access this namespace.  This needs to be
-different for all namespaces. For example @samp{Public/}.
-Defaults to @samp{""}.
+Prefix required to access this namespace.  This needs to be different for
+all namespaces. For example @samp{Public/}.  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string location
 Physical location of the mailbox. This is in the same format as
-mail_location, which is also the default for it.
-Defaults to @samp{""}.
+mail_location, which is also the default for it.  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean inbox?
-There can be only one INBOX, and this setting defines which
-namespace has it.
-Defaults to @samp{#f}.
+There can be only one INBOX, and this setting defines which namespace has
+it.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean hidden?
 If namespace is hidden, it's not advertised to clients via NAMESPACE
-extension. You'll most likely also want to set @samp{list? #f}.  This is mostly
-useful when converting from another server with different namespaces
+extension. You'll most likely also want to set @samp{list? #f}.  This is
+mostly useful when converting from another server with different namespaces
 which you want to deprecate but still keep working.  For example you can
-create hidden namespaces with prefixes @samp{~/mail/}, @samp{~%u/mail/}
-and @samp{mail/}.
-Defaults to @samp{#f}.
+create hidden namespaces with prefixes @samp{~/mail/}, @samp{~%u/mail/} and
address@hidden/}.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean list?
-Show the mailboxes under this namespace with the LIST command. This
-makes the namespace visible for clients that do not support the NAMESPACE
+Show the mailboxes under this namespace with the LIST command. This makes
+the namespace visible for clients that do not support the NAMESPACE
 extension.  The special @code{children} value lists child mailboxes, but
-hides the namespace prefix.
-Defaults to @samp{#t}.
+hides the namespace prefix.  Defaults to @samp{#t}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean subscriptions?
-Namespace handles its own subscriptions.  If set to @code{#f}, the
-parent namespace handles them.  The empty prefix should always have this
-as @code{#t}).
-Defaults to @samp{#t}.
+Namespace handles its own subscriptions.  If set to @code{#f}, the parent
+namespace handles them.  The empty prefix should always have this as
address@hidden).  Defaults to @samp{#t}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} mailbox-configuration-list mailboxes
-List of predefined mailboxes in this namespace.
-Defaults to @samp{()}.
+List of predefined mailboxes in this namespace.  Defaults to @samp{()}.
 
 Available @code{mailbox-configuration} fields are:
 
@@ -14495,16 +14449,14 @@ Name for this mailbox.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auto
address@hidden will automatically create this mailbox.
address@hidden will both create and subscribe to the mailbox.
-Defaults to @samp{"no"}.
address@hidden will automatically create this mailbox.  @samp{subscribe} will
+both create and subscribe to the mailbox.  Defaults to @samp{"no"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list special-use
-List of IMAP @code{SPECIAL-USE} attributes as specified by RFC 6154.
-Valid values are @code{\All}, @code{\Archive}, @code{\Drafts},
address@hidden, @code{\Junk}, @code{\Sent}, and @code{\Trash}.
-Defaults to @samp{()}.
+List of IMAP @code{SPECIAL-USE} attributes as specified by RFC 6154.  Valid
+values are @code{\All}, @code{\Archive}, @code{\Drafts}, @code{\Flagged},
address@hidden, @code{\Sent}, and @code{\Trash}.  Defaults to @samp{()}.
 @end deftypevr
 
 @end deftypevr
@@ -14512,323 +14464,283 @@ Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-name base-dir
-Base directory where to store runtime data.
-Defaults to @samp{"/var/run/dovecot/"}.
+Base directory where to store runtime data.  Defaults to
address@hidden"/var/run/dovecot/"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string login-greeting
-Greeting message for clients.
-Defaults to @samp{"Dovecot ready."}.
+Greeting message for clients.  Defaults to @samp{"Dovecot ready."}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list 
login-trusted-networks
-List of trusted network ranges.  Connections from these IPs are
-allowed to override their IP addresses and ports (for logging and for
-authentication checks).  @samp{disable-plaintext-auth} is also ignored
-for these networks.  Typically you would specify your IMAP proxy servers
-here.
-Defaults to @samp{()}.
+List of trusted network ranges.  Connections from these IPs are allowed to
+override their IP addresses and ports (for logging and for authentication
+checks).  @samp{disable-plaintext-auth} is also ignored for these networks.
+Typically you would specify your IMAP proxy servers here.  Defaults to
address@hidden()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list 
login-access-sockets
-List of login access check sockets (e.g. tcpwrap).
-Defaults to @samp{()}.
+List of login access check sockets (e.g. tcpwrap).  Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean verbose-proctitle?
-Show more verbose process titles (in ps).  Currently shows user name
-and IP address.  Useful for seeing who is actually using the IMAP
-processes (e.g. shared mailboxes or if the same uid is used for multiple
-accounts).
+Show more verbose process titles (in ps).  Currently shows user name and IP
+address.  Useful for seeing who is actually using the IMAP processes
+(e.g. shared mailboxes or if the same uid is used for multiple accounts).
 Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean shutdown-clients?
 Should all processes be killed when Dovecot master process shuts down.
-Setting this to @code{#f} means that Dovecot can be upgraded without
-forcing existing client connections to close (although that could also
-be a problem if the upgrade is e.g. due to a security fix).
-Defaults to @samp{#t}.
+Setting this to @code{#f} means that Dovecot can be upgraded without forcing
+existing client connections to close (although that could also be a problem
+if the upgrade is e.g. due to a security fix).  Defaults to @samp{#t}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer doveadm-worker-count
-If non-zero, run mail commands via this many connections to doveadm
-server, instead of running them directly in the same process.
-Defaults to @samp{0}.
+If non-zero, run mail commands via this many connections to doveadm server,
+instead of running them directly in the same process.  Defaults to @samp{0}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string doveadm-socket-path
-UNIX socket or host:port used for connecting to doveadm server.
-Defaults to @samp{"doveadm-server"}.
+UNIX socket or host:port used for connecting to doveadm server.  Defaults to
address@hidden"doveadm-server"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list 
import-environment
-List of environment variables that are preserved on Dovecot startup
-and passed down to all of its child processes.  You can also give
-key=value pairs to always set specific settings.
+List of environment variables that are preserved on Dovecot startup and
+passed down to all of its child processes.  You can also give key=value
+pairs to always set specific settings.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean disable-plaintext-auth?
-Disable LOGIN command and all other plaintext authentications unless
-SSL/TLS is used (LOGINDISABLED capability).  Note that if the remote IP
-matches the local IP (i.e. you're connecting from the same computer),
-the connection is considered secure and plaintext authentication is
-allowed.  See also ssl=required setting.
-Defaults to @samp{#t}.
+Disable LOGIN command and all other plaintext authentications unless SSL/TLS
+is used (LOGINDISABLED capability).  Note that if the remote IP matches the
+local IP (i.e. you're connecting from the same computer), the connection is
+considered secure and plaintext authentication is allowed.  See also
+ssl=required setting.  Defaults to @samp{#t}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer auth-cache-size
 Authentication cache size (e.g. @samp{#e10e6}).  0 means it's disabled.
-Note that bsdauth, PAM and vpopmail require @samp{cache-key} to be set
-for caching to be used.
-Defaults to @samp{0}.
+Note that bsdauth, PAM and vpopmail require @samp{cache-key} to be set for
+caching to be used.  Defaults to @samp{0}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-cache-ttl
-Time to live for cached data.  After TTL expires the cached record
-is no longer used, *except* if the main database lookup returns internal
-failure.  We also try to handle password changes automatically: If
-user's previous authentication was successful, but this one wasn't, the
-cache isn't used.  For now this works only with plaintext
-authentication.
-Defaults to @samp{"1 hour"}.
+Time to live for cached data.  After TTL expires the cached record is no
+longer used, *except* if the main database lookup returns internal failure.
+We also try to handle password changes automatically: If user's previous
+authentication was successful, but this one wasn't, the cache isn't used.
+For now this works only with plaintext authentication.  Defaults to @samp{"1
+hour"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-cache-negative-ttl
-TTL for negative hits (user not found, password mismatch).
-0 disables caching them completely.
-Defaults to @samp{"1 hour"}.
+TTL for negative hits (user not found, password mismatch).  0 disables
+caching them completely.  Defaults to @samp{"1 hour"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list auth-realms
-List of realms for SASL authentication mechanisms that need them.
-You can leave it empty if you don't want to support multiple realms.
-Many clients simply use the first one listed here, so keep the default
-realm first.
+List of realms for SASL authentication mechanisms that need them.  You can
+leave it empty if you don't want to support multiple realms.  Many clients
+simply use the first one listed here, so keep the default realm first.
 Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-default-realm
-Default realm/domain to use if none was specified.  This is used for
-both SASL realms and appending @@domain to username in plaintext
-logins.
+Default realm/domain to use if none was specified.  This is used for both
+SASL realms and appending @@domain to username in plaintext logins.
 Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-username-chars
-List of allowed characters in username.  If the user-given username
-contains a character not listed in here, the login automatically fails.
-This is just an extra check to make sure user can't exploit any
-potential quote escaping vulnerabilities with SQL/LDAP databases.  If
-you want to allow all characters, set this value to empty.
-Defaults to 
@samp{"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@@"}.
+List of allowed characters in username.  If the user-given username contains
+a character not listed in here, the login automatically fails.  This is just
+an extra check to make sure user can't exploit any potential quote escaping
+vulnerabilities with SQL/LDAP databases.  If you want to allow all
+characters, set this value to empty.  Defaults to
address@hidden"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@@"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-username-translation
-Username character translations before it's looked up from
-databases.  The value contains series of from -> to characters.  For
-example @samp{#@@/@@} means that @samp{#} and @samp{/} characters are
-translated to @samp{@@}.
+Username character translations before it's looked up from databases.  The
+value contains series of from -> to characters.  For example @samp{#@@/@@}
+means that @samp{#} and @samp{/} characters are translated to @samp{@@}.
 Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-username-format
-Username formatting before it's looked up from databases.  You can
-use the standard variables here, e.g. %Lu would lowercase the username,
-%n would drop away the domain if it was given, or @samp{%n-AT-%d} would
-change the @samp{@@} into @samp{-AT-}.  This translation is done after
address@hidden changes.
-Defaults to @samp{"%Lu"}.
+Username formatting before it's looked up from databases.  You can use the
+standard variables here, e.g. %Lu would lowercase the username, %n would
+drop away the domain if it was given, or @samp{%n-AT-%d} would change the
address@hidden@@} into @samp{-AT-}.  This translation is done after
address@hidden changes.  Defaults to @samp{"%Lu"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-master-user-separator
 If you want to allow master users to log in by specifying the master
-username within the normal username string (i.e. not using SASL
-mechanism's support for it), you can specify the separator character
-here.  The format is then <username><separator><master username>.
-UW-IMAP uses @samp{*} as the separator, so that could be a good
-choice.
-Defaults to @samp{""}.
+username within the normal username string (i.e. not using SASL mechanism's
+support for it), you can specify the separator character here.  The format
+is then <username><separator><master username>.  UW-IMAP uses @samp{*} as
+the separator, so that could be a good choice.  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-anonymous-username
-Username to use for users logging in with ANONYMOUS SASL
-mechanism.
+Username to use for users logging in with ANONYMOUS SASL mechanism.
 Defaults to @samp{"anonymous"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer auth-worker-max-count
-Maximum number of dovecot-auth worker processes.  They're used to
-execute blocking passdb and userdb queries (e.g. MySQL and PAM).
-They're automatically created and destroyed as needed.
-Defaults to @samp{30}.
+Maximum number of dovecot-auth worker processes.  They're used to execute
+blocking passdb and userdb queries (e.g. MySQL and PAM).  They're
+automatically created and destroyed as needed.  Defaults to @samp{30}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-gssapi-hostname
-Host name to use in GSSAPI principal names.  The default is to use
-the name returned by gethostname().  Use @samp{$ALL} (with quotes) to
-allow all keytab entries.
-Defaults to @samp{""}.
+Host name to use in GSSAPI principal names.  The default is to use the name
+returned by gethostname().  Use @samp{$ALL} (with quotes) to allow all
+keytab entries.  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-krb5-keytab
-Kerberos keytab to use for the GSSAPI mechanism.  Will use the
-system default (usually @file{/etc/krb5.keytab}) if not specified.  You may
-need to change the auth service to run as root to be able to read this
-file.
+Kerberos keytab to use for the GSSAPI mechanism.  Will use the system
+default (usually @file{/etc/krb5.keytab}) if not specified.  You may need to
+change the auth service to run as root to be able to read this file.
 Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean auth-use-winbind?
-Do NTLM and GSS-SPNEGO authentication using Samba's winbind daemon
-and @samp{ntlm-auth} helper.
-<doc/wiki/Authentication/Mechanisms/Winbind.txt>.
+Do NTLM and GSS-SPNEGO authentication using Samba's winbind daemon and
address@hidden helper.  <doc/wiki/Authentication/Mechanisms/Winbind.txt>.
 Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-name auth-winbind-helper-path
-Path for Samba's @samp{ntlm-auth} helper binary.
-Defaults to @samp{"/usr/bin/ntlm_auth"}.
+Path for Samba's @samp{ntlm-auth} helper binary.  Defaults to
address@hidden"/usr/bin/ntlm_auth"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string auth-failure-delay
-Time to delay before replying to failed authentications.
-Defaults to @samp{"2 secs"}.
+Time to delay before replying to failed authentications.  Defaults to
address@hidden"2 secs"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean auth-ssl-require-client-cert?
-Require a valid SSL client certificate or the authentication
-fails.
+Require a valid SSL client certificate or the authentication fails.
 Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean auth-ssl-username-from-cert?
 Take the username from client's SSL certificate, using
 @code{X509_NAME_get_text_by_NID()} which returns the subject's DN's
-CommonName.
-Defaults to @samp{#f}.
+CommonName.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list 
auth-mechanisms
 List of wanted authentication mechanisms.  Supported mechanisms are:
address@hidden, @samp{login}, @samp{digest-md5}, @samp{cram-md5},
address@hidden, @samp{rpa}, @samp{apop}, @samp{anonymous}, @samp{gssapi},
address@hidden, @samp{skey}, and @samp{gss-spnego}.  NOTE: See also
address@hidden, @samp{login}, @samp{digest-md5}, @samp{cram-md5}, @samp{ntlm},
address@hidden, @samp{apop}, @samp{anonymous}, @samp{gssapi}, @samp{otp},
address@hidden, and @samp{gss-spnego}.  NOTE: See also
 @samp{disable-plaintext-auth} setting.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list 
director-servers
-List of IPs or hostnames to all director servers, including ourself.
-Ports can be specified as ip:port.  The default port is the same as what
-director service's @samp{inet-listener} is using.
-Defaults to @samp{()}.
+List of IPs or hostnames to all director servers, including ourself.  Ports
+can be specified as ip:port.  The default port is the same as what director
+service's @samp{inet-listener} is using.  Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list 
director-mail-servers
-List of IPs or hostnames to all backend mail servers.  Ranges are
-allowed too, like 10.0.0.10-10.0.0.30.
-Defaults to @samp{()}.
+List of IPs or hostnames to all backend mail servers.  Ranges are allowed
+too, like 10.0.0.10-10.0.0.30.  Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string director-user-expire
-How long to redirect users to a specific server after it no longer
-has any connections.
-Defaults to @samp{"15 min"}.
+How long to redirect users to a specific server after it no longer has any
+connections.  Defaults to @samp{"15 min"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string director-username-hash
-How the username is translated before being hashed.  Useful values
-include %Ln if user can log in with or without @@domain, %Ld if mailboxes
-are shared within domain.
-Defaults to @samp{"%Lu"}.
+How the username is translated before being hashed.  Useful values include
+%Ln if user can log in with or without @@domain, %Ld if mailboxes are shared
+within domain.  Defaults to @samp{"%Lu"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string log-path
 Log file to use for error messages.  @samp{syslog} logs to syslog,
address@hidden/dev/stderr} logs to stderr.
-Defaults to @samp{"syslog"}.
address@hidden/dev/stderr} logs to stderr.  Defaults to @samp{"syslog"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string info-log-path
-Log file to use for informational messages.  Defaults to
address@hidden
+Log file to use for informational messages.  Defaults to @samp{log-path}.
 Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string debug-log-path
-Log file to use for debug messages.  Defaults to
address@hidden
+Log file to use for debug messages.  Defaults to @samp{info-log-path}.
 Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string syslog-facility
-Syslog facility to use if you're logging to syslog.  Usually if you
-don't want to use @samp{mail}, you'll use local0..local7.  Also other
-standard facilities are supported.
-Defaults to @samp{"mail"}.
+Syslog facility to use if you're logging to syslog.  Usually if you don't
+want to use @samp{mail}, you'll use local0..local7.  Also other standard
+facilities are supported.  Defaults to @samp{"mail"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean auth-verbose?
-Log unsuccessful authentication attempts and the reasons why they
-failed.
+Log unsuccessful authentication attempts and the reasons why they failed.
 Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean auth-verbose-passwords?
-In case of password mismatches, log the attempted password.  Valid
-values are no, plain and sha1.  sha1 can be useful for detecting brute
-force password attempts vs.  user simply trying the same password over
-and over again.  You can also truncate the value to n chars by appending
-":n" (e.g. sha1:6).
-Defaults to @samp{#f}.
+In case of password mismatches, log the attempted password.  Valid values
+are no, plain and sha1.  sha1 can be useful for detecting brute force
+password attempts vs.  user simply trying the same password over and over
+again.  You can also truncate the value to n chars by appending ":n"
+(e.g. sha1:6).  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean auth-debug?
-Even more verbose logging for debugging purposes.  Shows for example
-SQL queries.
-Defaults to @samp{#f}.
+Even more verbose logging for debugging purposes.  Shows for example SQL
+queries.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean auth-debug-passwords?
-In case of password mismatches, log the passwords and used scheme so
-the problem can be debugged.  Enabling this also enables
address@hidden
+In case of password mismatches, log the passwords and used scheme so the
+problem can be debugged.  Enabling this also enables @samp{auth-debug}.
 Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mail-debug?
-Enable mail process debugging.  This can help you figure out why
-Dovecot isn't finding your mails.
-Defaults to @samp{#f}.
+Enable mail process debugging.  This can help you figure out why Dovecot
+isn't finding your mails.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean verbose-ssl?
-Show protocol level SSL errors.
-Defaults to @samp{#f}.
+Show protocol level SSL errors.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string log-timestamp
-Prefix for each line written to log file.  % codes are in
-strftime(3) format.
-Defaults to @samp{"\"%b %d %H:%M:%S \""}.
+Prefix for each line written to log file.  % codes are in strftime(3)
+format.  Defaults to @samp{"\"%b %d %H:%M:%S \""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list 
login-log-format-elements
-List of elements we want to log.  The elements which have a
-non-empty variable value are joined together to form a comma-separated
-string.
+List of elements we want to log.  The elements which have a non-empty
+variable value are joined together to form a comma-separated string.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string login-log-format
-Login log format.  %s contains @samp{login-log-format-elements}
-string, %$ contains the data we want to log.
-Defaults to @samp{"%$: %s"}.
+Login log format.  %s contains @samp{login-log-format-elements} string, %$
+contains the data we want to log.  Defaults to @samp{"%$: %s"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mail-log-prefix
-Log prefix for mail processes.  See doc/wiki/Variables.txt for list
-of possible variables you can use.
-Defaults to @samp{"\"%s(%u)<address@hidden@}><address@hidden@}>: \""}.
+Log prefix for mail processes.  See doc/wiki/Variables.txt for list of
+possible variables you can use.  Defaults to
address@hidden"\"%s(%u)<address@hidden@}><address@hidden@}>: \""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string deliver-log-format
@@ -14851,16 +14763,15 @@ Defaults to @samp{"msgid=%m: %$"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mail-location
-Location for users' mailboxes.  The default is empty, which means
-that Dovecot tries to find the mailboxes automatically.  This won't work
-if the user doesn't yet have any mail, so you should explicitly tell
-Dovecot the full location.
+Location for users' mailboxes.  The default is empty, which means that
+Dovecot tries to find the mailboxes automatically.  This won't work if the
+user doesn't yet have any mail, so you should explicitly tell Dovecot the
+full location.
 
-If you're using mbox, giving a path to the INBOX
-file (e.g. /var/mail/%u) isn't enough.  You'll also need to tell Dovecot
-where the other mailboxes are kept.  This is called the "root mail
-directory", and it must be the first path given in the
address@hidden setting.
+If you're using mbox, giving a path to the INBOX file (e.g. /var/mail/%u)
+isn't enough.  You'll also need to tell Dovecot where the other mailboxes
+are kept.  This is called the "root mail directory", and it must be the
+first path given in the @samp{mail-location} setting.
 
 There are a few special variables you can use, eg.:
 
@@ -14885,10 +14796,9 @@ Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mail-uid
-System user and group used to access mails.  If you use multiple,
-userdb can override these by returning uid or gid fields.  You can use
-either numbers or names.  <doc/wiki/UserIds.txt>.
-Defaults to @samp{""}.
+System user and group used to access mails.  If you use multiple, userdb can
+override these by returning uid or gid fields.  You can use either numbers
+or names.  <doc/wiki/UserIds.txt>.  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mail-gid
@@ -14897,42 +14807,37 @@ Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mail-privileged-group
-Group to enable temporarily for privileged operations.  Currently
-this is used only with INBOX when either its initial creation or
-dotlocking fails.  Typically this is set to "mail" to give access to
-/var/mail.
-Defaults to @samp{""}.
+Group to enable temporarily for privileged operations.  Currently this is
+used only with INBOX when either its initial creation or dotlocking fails.
+Typically this is set to "mail" to give access to /var/mail.  Defaults to
address@hidden""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mail-access-groups
-Grant access to these supplementary groups for mail processes.
-Typically these are used to set up access to shared mailboxes.  Note
-that it may be dangerous to set these if users can create
-symlinks (e.g. if "mail" group is set here, ln -s /var/mail ~/mail/var
-could allow a user to delete others' mailboxes, or ln -s
-/secret/shared/box ~/mail/mybox would allow reading it).
-Defaults to @samp{""}.
+Grant access to these supplementary groups for mail processes.  Typically
+these are used to set up access to shared mailboxes.  Note that it may be
+dangerous to set these if users can create symlinks (e.g. if "mail" group is
+set here, ln -s /var/mail ~/mail/var could allow a user to delete others'
+mailboxes, or ln -s /secret/shared/box ~/mail/mybox would allow reading
+it).  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mail-full-filesystem-access?
-Allow full file system access to clients.  There's no access checks
-other than what the operating system does for the active UID/GID.  It
-works with both maildir and mboxes, allowing you to prefix mailboxes
-names with e.g. /path/ or ~user/.
-Defaults to @samp{#f}.
+Allow full file system access to clients.  There's no access checks other
+than what the operating system does for the active UID/GID.  It works with
+both maildir and mboxes, allowing you to prefix mailboxes names with
+e.g. /path/ or ~user/.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mmap-disable?
-Don't use mmap() at all.  This is required if you store indexes to
-shared file systems (NFS or clustered file system).
-Defaults to @samp{#f}.
+Don't use mmap() at all.  This is required if you store indexes to shared
+file systems (NFS or clustered file system).  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean dotlock-use-excl?
-Rely on @samp{O_EXCL} to work when creating dotlock files.  NFS
-supports @samp{O_EXCL} since version 3, so this should be safe to use
-nowadays by default.
-Defaults to @samp{#t}.
+Rely on @samp{O_EXCL} to work when creating dotlock files.  NFS supports
address@hidden since version 3, so this should be safe to use nowadays by
+default.  Defaults to @samp{#t}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mail-fsync
@@ -14949,38 +14854,34 @@ Defaults to @samp{"optimized"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mail-nfs-storage?
-Mail storage exists in NFS.  Set this to yes to make Dovecot flush
-NFS caches whenever needed.  If you're using only a single mail server
-this isn't needed.
-Defaults to @samp{#f}.
+Mail storage exists in NFS.  Set this to yes to make Dovecot flush NFS
+caches whenever needed.  If you're using only a single mail server this
+isn't needed.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mail-nfs-index?
 Mail index files also exist in NFS.  Setting this to yes requires
address@hidden #t} and @samp{fsync-disable? #f}.
-Defaults to @samp{#f}.
address@hidden #t} and @samp{fsync-disable? #f}.  Defaults to
address@hidden
 @end deftypevr
 
 @deftypevr address@hidden parameter} string lock-method
-Locking method for index files.  Alternatives are fcntl, flock and
-dotlock.  Dotlocking uses some tricks which may create more disk I/O
-than other locking methods.  NFS users: flock doesn't work, remember to
-change @samp{mmap-disable}.
-Defaults to @samp{"fcntl"}.
+Locking method for index files.  Alternatives are fcntl, flock and dotlock.
+Dotlocking uses some tricks which may create more disk I/O than other
+locking methods.  NFS users: flock doesn't work, remember to change
address@hidden  Defaults to @samp{"fcntl"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-name mail-temp-dir
-Directory in which LDA/LMTP temporarily stores incoming mails >128
-kB.
+Directory in which LDA/LMTP temporarily stores incoming mails >128 kB.
 Defaults to @samp{"/tmp"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer first-valid-uid
-Valid UID range for users.  This is mostly to make sure that users can't
-log in as daemons or other system users.  Note that denying root logins is
+Valid UID range for users.  This is mostly to make sure that users can't log
+in as daemons or other system users.  Note that denying root logins is
 hardcoded to dovecot binary and can't be done even if @samp{first-valid-uid}
-is set to 0.
-Defaults to @samp{500}.
+is set to 0.  Defaults to @samp{500}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer last-valid-uid
@@ -14991,8 +14892,7 @@ Defaults to @samp{0}.
 @deftypevr address@hidden parameter} non-negative-integer first-valid-gid
 Valid GID range for users.  Users having non-valid GID as primary group ID
 aren't allowed to log in.  If user belongs to supplementary groups with
-non-valid GIDs, those groups are not set.
-Defaults to @samp{1}.
+non-valid GIDs, those groups are not set.  Defaults to @samp{1}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer last-valid-gid
@@ -15001,109 +14901,97 @@ Defaults to @samp{0}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer 
mail-max-keyword-length
-Maximum allowed length for mail keyword name.  It's only forced when
-trying to create new keywords.
-Defaults to @samp{50}.
+Maximum allowed length for mail keyword name.  It's only forced when trying
+to create new keywords.  Defaults to @samp{50}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} colon-separated-file-name-list 
valid-chroot-dirs
-List of directories under which chrooting is allowed for mail
-processes (i.e. /var/mail will allow chrooting to /var/mail/foo/bar
-too).  This setting doesn't affect @samp{login-chroot}
address@hidden or auth chroot settings.  If this setting is empty,
-"/./" in home dirs are ignored.  WARNING: Never add directories here
-which local users can modify, that may lead to root exploit.  Usually
-this should be done only if you don't allow shell access for users.
-<doc/wiki/Chrooting.txt>.
-Defaults to @samp{()}.
+List of directories under which chrooting is allowed for mail processes
+(i.e. /var/mail will allow chrooting to /var/mail/foo/bar too).  This
+setting doesn't affect @samp{login-chroot} @samp{mail-chroot} or auth chroot
+settings.  If this setting is empty, "/./" in home dirs are ignored.
+WARNING: Never add directories here which local users can modify, that may
+lead to root exploit.  Usually this should be done only if you don't allow
+shell access for users.  <doc/wiki/Chrooting.txt>.  Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mail-chroot
-Default chroot directory for mail processes.  This can be overridden
-for specific users in user database by giving /./ in user's home
-directory (e.g. /home/./user chroots into /home).  Note that usually
-there is no real need to do chrooting, Dovecot doesn't allow users to
-access files outside their mail directory anyway.  If your home
-directories are prefixed with the chroot directory, append "/." to
address@hidden  <doc/wiki/Chrooting.txt>.
-Defaults to @samp{""}.
+Default chroot directory for mail processes.  This can be overridden for
+specific users in user database by giving /./ in user's home directory
+(e.g. /home/./user chroots into /home).  Note that usually there is no real
+need to do chrooting, Dovecot doesn't allow users to access files outside
+their mail directory anyway.  If your home directories are prefixed with the
+chroot directory, append "/." to @samp{mail-chroot}.
+<doc/wiki/Chrooting.txt>.  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-name auth-socket-path
-UNIX socket path to master authentication server to find users.
-This is used by imap (for shared users) and lda.
-Defaults to @samp{"/var/run/dovecot/auth-userdb"}.
+UNIX socket path to master authentication server to find users.  This is
+used by imap (for shared users) and lda.  Defaults to
address@hidden"/var/run/dovecot/auth-userdb"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-name mail-plugin-dir
-Directory where to look up mail plugins.
-Defaults to @samp{"/usr/lib/dovecot"}.
+Directory where to look up mail plugins.  Defaults to
address@hidden"/usr/lib/dovecot"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list mail-plugins
-List of plugins to load for all services.  Plugins specific to IMAP,
-LDA, etc. are added to this list in their own .conf files.
-Defaults to @samp{()}.
+List of plugins to load for all services.  Plugins specific to IMAP, LDA,
+etc. are added to this list in their own .conf files.  Defaults to
address@hidden()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer 
mail-cache-min-mail-count
-The minimum number of mails in a mailbox before updates are done to
-cache file.  This allows optimizing Dovecot's behavior to do less disk
-writes at the cost of more disk reads.
-Defaults to @samp{0}.
+The minimum number of mails in a mailbox before updates are done to cache
+file.  This allows optimizing Dovecot's behavior to do less disk writes at
+the cost of more disk reads.  Defaults to @samp{0}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mailbox-idle-check-interval
-When IDLE command is running, mailbox is checked once in a while to
-see if there are any new mails or other changes.  This setting defines
-the minimum time to wait between those checks.  Dovecot can also use
-dnotify, inotify and kqueue to find out immediately when changes
-occur.
-Defaults to @samp{"30 secs"}.
+When IDLE command is running, mailbox is checked once in a while to see if
+there are any new mails or other changes.  This setting defines the minimum
+time to wait between those checks.  Dovecot can also use dnotify, inotify
+and kqueue to find out immediately when changes occur.  Defaults to
address@hidden"30 secs"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mail-save-crlf?
-Save mails with CR+LF instead of plain LF.  This makes sending those
-mails take less CPU, especially with sendfile() syscall with Linux and
-FreeBSD.  But it also creates a bit more disk I/O which may just make it
-slower.  Also note that if other software reads the mboxes/maildirs,
-they may handle the extra CRs wrong and cause problems.
-Defaults to @samp{#f}.
+Save mails with CR+LF instead of plain LF.  This makes sending those mails
+take less CPU, especially with sendfile() syscall with Linux and FreeBSD.
+But it also creates a bit more disk I/O which may just make it slower.  Also
+note that if other software reads the mboxes/maildirs, they may handle the
+extra CRs wrong and cause problems.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean maildir-stat-dirs?
-By default LIST command returns all entries in maildir beginning
-with a dot.  Enabling this option makes Dovecot return only entries
-which are directories.  This is done by stat()ing each entry, so it
-causes more disk I/O.
- (For systems setting struct @samp{dirent->d_type} this check is free
-and it's done always regardless of this setting).
-Defaults to @samp{#f}.
+By default LIST command returns all entries in maildir beginning with a
+dot.  Enabling this option makes Dovecot return only entries which are
+directories.  This is done by stat()ing each entry, so it causes more disk
+I/O.  (For systems setting struct @samp{dirent->d_type} this check is free
+and it's done always regardless of this setting).  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean maildir-copy-with-hardlinks?
-When copying a message, do it with hard links whenever possible.
-This makes the performance much better, and it's unlikely to have any
-side effects.
+When copying a message, do it with hard links whenever possible.  This makes
+the performance much better, and it's unlikely to have any side effects.
 Defaults to @samp{#t}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean maildir-very-dirty-syncs?
-Assume Dovecot is the only MUA accessing Maildir: Scan cur/
-directory only when its mtime changes unexpectedly or when we can't find
-the mail otherwise.
-Defaults to @samp{#f}.
+Assume Dovecot is the only MUA accessing Maildir: Scan cur/ directory only
+when its mtime changes unexpectedly or when we can't find the mail
+otherwise.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list 
mbox-read-locks
-Which locking methods to use for locking mbox.  There are four
-available:
+Which locking methods to use for locking mbox.  There are four available:
 
 @table @code
 @item dotlock
-Create <mailbox>.lock file.  This is the oldest and most NFS-safe
-solution.  If you want to use /var/mail/ like directory, the users will
-need write access to that directory.
+Create <mailbox>.lock file.  This is the oldest and most NFS-safe solution.
+If you want to use /var/mail/ like directory, the users will need write
+access to that directory.
 @item dotlock-try
 Same as dotlock, but if it fails because of permissions or because there
 isn't enough disk space, just skip it.
@@ -15126,74 +15014,66 @@ them simultaneously.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mbox-lock-timeout
-Maximum time to wait for lock (all of them) before aborting.
-Defaults to @samp{"5 mins"}.
+Maximum time to wait for lock (all of them) before aborting.  Defaults to
address@hidden"5 mins"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mbox-dotlock-change-timeout
-If dotlock exists but the mailbox isn't modified in any way,
-override the lock file after this much time.
-Defaults to @samp{"2 mins"}.
+If dotlock exists but the mailbox isn't modified in any way, override the
+lock file after this much time.  Defaults to @samp{"2 mins"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mbox-dirty-syncs?
-When mbox changes unexpectedly we have to fully read it to find out
-what changed.  If the mbox is large this can take a long time.  Since
-the change is usually just a newly appended mail, it'd be faster to
-simply read the new mails.  If this setting is enabled, Dovecot does
-this but still safely fallbacks to re-reading the whole mbox file
-whenever something in mbox isn't how it's expected to be.  The only real
-downside to this setting is that if some other MUA changes message
-flags, Dovecot doesn't notice it immediately.  Note that a full sync is
-done with SELECT, EXAMINE, EXPUNGE and CHECK commands.
-Defaults to @samp{#t}.
+When mbox changes unexpectedly we have to fully read it to find out what
+changed.  If the mbox is large this can take a long time.  Since the change
+is usually just a newly appended mail, it'd be faster to simply read the new
+mails.  If this setting is enabled, Dovecot does this but still safely
+fallbacks to re-reading the whole mbox file whenever something in mbox isn't
+how it's expected to be.  The only real downside to this setting is that if
+some other MUA changes message flags, Dovecot doesn't notice it
+immediately.  Note that a full sync is done with SELECT, EXAMINE, EXPUNGE
+and CHECK commands.  Defaults to @samp{#t}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mbox-very-dirty-syncs?
 Like @samp{mbox-dirty-syncs}, but don't do full syncs even with SELECT,
-EXAMINE, EXPUNGE or CHECK commands.  If this is set,
address@hidden is ignored.
-Defaults to @samp{#f}.
+EXAMINE, EXPUNGE or CHECK commands.  If this is set, @samp{mbox-dirty-syncs}
+is ignored.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mbox-lazy-writes?
-Delay writing mbox headers until doing a full write sync (EXPUNGE
-and CHECK commands and when closing the mailbox).  This is especially
-useful for POP3 where clients often delete all mails.  The downside is
-that our changes aren't immediately visible to other MUAs.
-Defaults to @samp{#t}.
+Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK
+commands and when closing the mailbox).  This is especially useful for POP3
+where clients often delete all mails.  The downside is that our changes
+aren't immediately visible to other MUAs.  Defaults to @samp{#t}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer mbox-min-index-size
-If mbox size is smaller than this (e.g. 100k), don't write index
-files.  If an index file already exists it's still read, just not
-updated.
-Defaults to @samp{0}.
+If mbox size is smaller than this (e.g. 100k), don't write index files.  If
+an index file already exists it's still read, just not updated.  Defaults to
address@hidden
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer mdbox-rotate-size
-Maximum dbox file size until it's rotated.
-Defaults to @samp{10000000}.
+Maximum dbox file size until it's rotated.  Defaults to @samp{10000000}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mdbox-rotate-interval
-Maximum dbox file age until it's rotated.  Typically in days.  Day
-begins from midnight, so 1d = today, 2d = yesterday, etc.  0 = check
-disabled.
+Maximum dbox file age until it's rotated.  Typically in days.  Day begins
+from midnight, so 1d = today, 2d = yesterday, etc.  0 = check disabled.
 Defaults to @samp{"1d"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean mdbox-preallocate-space?
 When creating new mdbox files, immediately preallocate their size to
address@hidden  This setting currently works only in Linux
-with some file systems (ext4, xfs).
-Defaults to @samp{#f}.
address@hidden  This setting currently works only in Linux with
+some file systems (ext4, xfs).  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string mail-attachment-dir
-sdbox and mdbox support saving mail attachments to external files,
-which also allows single instance storage for them.  Other backends
-don't support this for now.
+sdbox and mdbox support saving mail attachments to external files, which
+also allows single instance storage for them.  Other backends don't support
+this for now.
 
 WARNING: This feature hasn't been tested much yet.  Use at your own risk.
 
@@ -15202,9 +15082,8 @@ Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer 
mail-attachment-min-size
-Attachments smaller than this aren't saved externally.  It's also
-possible to write a plugin to disable saving specific attachments
-externally.
+Attachments smaller than this aren't saved externally.  It's also possible
+to write a plugin to disable saving specific attachments externally.
 Defaults to @samp{128000}.
 @end deftypevr
 
@@ -15225,8 +15104,8 @@ Defaults to @samp{"sis posix"}.
 Hash format to use in attachment filenames.  You can add any text and
 variables: @address@hidden@}}, @address@hidden@}}, @address@hidden@}},
 @address@hidden@}}, @address@hidden@}}, @address@hidden@}}.  Variables can be
-truncated, e.g. @address@hidden:address@hidden returns only first 80 bits.
-Defaults to @samp{"address@hidden@}"}.
+truncated, e.g. @address@hidden:address@hidden returns only first 80 bits.  
Defaults
+to @samp{"address@hidden@}"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer default-process-limit
@@ -15240,130 +15119,116 @@ Defaults to @samp{1000}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer default-vsz-limit
-Default VSZ (virtual memory size) limit for service processes.
-This is mainly intended to catch and kill processes that leak memory
-before they eat up everything.
-Defaults to @samp{256000000}.
+Default VSZ (virtual memory size) limit for service processes.  This is
+mainly intended to catch and kill processes that leak memory before they eat
+up everything.  Defaults to @samp{256000000}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string default-login-user
 Login user is internally used by login processes.  This is the most
-untrusted user in Dovecot system.  It shouldn't have access to anything
-at all.
-Defaults to @samp{"dovenull"}.
+untrusted user in Dovecot system.  It shouldn't have access to anything at
+all.  Defaults to @samp{"dovenull"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string default-internal-user
-Internal user is used by unprivileged processes.  It should be
-separate from login user, so that login processes can't disturb other
-processes.
-Defaults to @samp{"dovecot"}.
+Internal user is used by unprivileged processes.  It should be separate from
+login user, so that login processes can't disturb other processes.  Defaults
+to @samp{"dovecot"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string ssl?
-SSL/TLS support: yes, no, required.  <doc/wiki/SSL.txt>.
-Defaults to @samp{"required"}.
+SSL/TLS support: yes, no, required.  <doc/wiki/SSL.txt>.  Defaults to
address@hidden"required"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string ssl-cert
-PEM encoded X.509 SSL/TLS certificate (public key).
-Defaults to @samp{"</etc/dovecot/default.pem"}.
+PEM encoded X.509 SSL/TLS certificate (public key).  Defaults to
address@hidden"</etc/dovecot/default.pem"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string ssl-key
-PEM encoded SSL/TLS private key.  The key is opened before
-dropping root privileges, so keep the key file unreadable by anyone but
-root.
-Defaults to @samp{"</etc/dovecot/private/default.pem"}.
+PEM encoded SSL/TLS private key.  The key is opened before dropping root
+privileges, so keep the key file unreadable by anyone but root.  Defaults to
address@hidden"</etc/dovecot/private/default.pem"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string ssl-key-password
-If key file is password protected, give the password here.
-Alternatively give it when starting dovecot with -p parameter.  Since
-this file is often world-readable, you may want to place this setting
-instead to a different.
+If key file is password protected, give the password here.  Alternatively
+give it when starting dovecot with -p parameter.  Since this file is often
+world-readable, you may want to place this setting instead to a different.
 Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string ssl-ca
-PEM encoded trusted certificate authority.  Set this only if you
-intend to use @samp{ssl-verify-client-cert? #t}.  The file should
-contain the CA certificate(s) followed by the matching
-CRL(s).  (e.g. @samp{ssl-ca </etc/ssl/certs/ca.pem}).
-Defaults to @samp{""}.
+PEM encoded trusted certificate authority.  Set this only if you intend to
+use @samp{ssl-verify-client-cert? #t}.  The file should contain the CA
+certificate(s) followed by the matching CRL(s).  (e.g. @samp{ssl-ca
+</etc/ssl/certs/ca.pem}).  Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean ssl-require-crl?
-Require that CRL check succeeds for client certificates.
-Defaults to @samp{#t}.
+Require that CRL check succeeds for client certificates.  Defaults to
address@hidden
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean ssl-verify-client-cert?
-Request client to send a certificate.  If you also want to require
-it, set @samp{auth-ssl-require-client-cert? #t} in auth section.
-Defaults to @samp{#f}.
+Request client to send a certificate.  If you also want to require it, set
address@hidden #t} in auth section.  Defaults to
address@hidden
 @end deftypevr
 
 @deftypevr address@hidden parameter} string ssl-cert-username-field
 Which field from certificate to use for username.  commonName and
 x500UniqueIdentifier are the usual choices.  You'll also need to set
address@hidden #t}.
-Defaults to @samp{"commonName"}.
address@hidden #t}.  Defaults to @samp{"commonName"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string ssl-min-protocol
-Minimum SSL protocol version to accept.
-Defaults to @samp{"TLSv1"}.
+Minimum SSL protocol version to accept.  Defaults to @samp{"TLSv1"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string ssl-cipher-list
-SSL ciphers to use.
-Defaults to 
@samp{"ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@@STRENGTH"}.
+SSL ciphers to use.  Defaults to
address@hidden"ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@@STRENGTH"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string ssl-crypto-device
-SSL crypto device to use, for valid values run "openssl engine".
-Defaults to @samp{""}.
+SSL crypto device to use, for valid values run "openssl engine".  Defaults
+to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string postmaster-address
-Address to use when sending rejection mails.
-%d expands to recipient domain.
-Defaults to @samp{"postmaster@@%d"}.
+Address to use when sending rejection mails.  %d expands to recipient
+domain.  Defaults to @samp{"postmaster@@%d"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string hostname
-Hostname to use in various parts of sent mails (e.g. in Message-Id)
-and in LMTP replies.  Default is the system's real hostname@@domain.
-Defaults to @samp{""}.
+Hostname to use in various parts of sent mails (e.g. in Message-Id)  and in
+LMTP replies.  Default is the system's real hostname@@domain.  Defaults to
address@hidden""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean quota-full-tempfail?
-If user is over quota, return with temporary failure instead of
-bouncing the mail.
-Defaults to @samp{#f}.
+If user is over quota, return with temporary failure instead of bouncing the
+mail.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-name sendmail-path
-Binary to use for sending mails.
-Defaults to @samp{"/usr/sbin/sendmail"}.
+Binary to use for sending mails.  Defaults to @samp{"/usr/sbin/sendmail"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string submission-host
-If non-empty, send mails via this SMTP host[:port] instead of
-sendmail.
+If non-empty, send mails via this SMTP host[:port] instead of sendmail.
 Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string rejection-subject
-Subject: header to use for rejection mails.  You can use the same
-variables as for @samp{rejection-reason} below.
-Defaults to @samp{"Rejected: %s"}.
+Subject: header to use for rejection mails.  You can use the same variables
+as for @samp{rejection-reason} below.  Defaults to @samp{"Rejected: %s"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string rejection-reason
-Human readable error message for rejection mails.  You can use
-variables:
+Human readable error message for rejection mails.  You can use variables:
 
 @table @code
 @item %n
@@ -15379,37 +15244,32 @@ Defaults to @samp{"Your message to <%t> was 
automatically rejected:%n%r"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string recipient-delimiter
-Delimiter character between local-part and detail in email
-address.
+Delimiter character between local-part and detail in email address.
 Defaults to @samp{"+"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string lda-original-recipient-header
-Header where the original recipient address (SMTP's RCPT TO:
-address) is taken from if not available elsewhere.  With dovecot-lda -a
-parameter overrides this.  A commonly used header for this is
-X-Original-To.
-Defaults to @samp{""}.
+Header where the original recipient address (SMTP's RCPT TO: address) is
+taken from if not available elsewhere.  With dovecot-lda -a parameter
+overrides this.  A commonly used header for this is X-Original-To.  Defaults
+to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean lda-mailbox-autocreate?
-Should saving a mail to a nonexistent mailbox automatically create
-it?.
+Should saving a mail to a nonexistent mailbox automatically create it?.
 Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean lda-mailbox-autosubscribe?
-Should automatically created mailboxes be also automatically
-subscribed?.
+Should automatically created mailboxes be also automatically subscribed?.
 Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer imap-max-line-length
-Maximum IMAP command line length.  Some clients generate very long
-command lines with huge mailboxes, so you may need to raise this if you
-get "Too long argument" or "IMAP command line too large" errors
-often.
-Defaults to @samp{64000}.
+Maximum IMAP command line length.  Some clients generate very long command
+lines with huge mailboxes, so you may need to raise this if you get "Too
+long argument" or "IMAP command line too large" errors often.  Defaults to
address@hidden
 @end deftypevr
 
 @deftypevr address@hidden parameter} string imap-logout-format
@@ -15420,33 +15280,34 @@ total number of bytes read from client
 @item %o
 total number of bytes sent to client.
 @end table
-See @file{doc/wiki/Variables.txt} for a list of all the variables you can use.
-Defaults to @samp{"in=%i out=%o address@hidden@} address@hidden@} 
address@hidden@} address@hidden@} address@hidden@} address@hidden@} 
address@hidden@}"}.
+See @file{doc/wiki/Variables.txt} for a list of all the variables you can
+use.  Defaults to @samp{"in=%i out=%o address@hidden@}
address@hidden@} address@hidden@} address@hidden@}
address@hidden@} address@hidden@}
address@hidden@}"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string imap-capability
-Override the IMAP CAPABILITY response.  If the value begins with '+',
-add the given capabilities on top of the defaults (e.g. +XFOO XBAR).
-Defaults to @samp{""}.
+Override the IMAP CAPABILITY response.  If the value begins with '+', add
+the given capabilities on top of the defaults (e.g. +XFOO XBAR).  Defaults
+to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string imap-idle-notify-interval
-How long to wait between "OK Still here" notifications when client
-is IDLEing.
-Defaults to @samp{"2 mins"}.
+How long to wait between "OK Still here" notifications when client is
+IDLEing.  Defaults to @samp{"2 mins"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string imap-id-send
-ID field names and values to send to clients.  Using * as the value
-makes Dovecot use the default value.  The following fields have default
-values currently: name, version, os, os-version, support-url,
-support-email.
+ID field names and values to send to clients.  Using * as the value makes
+Dovecot use the default value.  The following fields have default values
+currently: name, version, os, os-version, support-url, support-email.
 Defaults to @samp{""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string imap-id-log
-ID fields sent by client to log.  * means everything.
-Defaults to @samp{""}.
+ID fields sent by client to log.  * means everything.  Defaults to
address@hidden""}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} space-separated-string-list 
imap-client-workarounds
@@ -15455,42 +15316,41 @@ Workarounds for various client bugs:
 @table @code
 @item delay-newmail
 Send EXISTS/RECENT new mail notifications only when replying to NOOP and
-CHECK commands.  Some clients ignore them otherwise, for example OSX
-Mail (<v2.1).  Outlook Express breaks more badly though, without this it
-may show user "Message no longer in server" errors.  Note that OE6
-still breaks even with this workaround if synchronization is set to
-"Headers Only".
+CHECK commands.  Some clients ignore them otherwise, for example OSX Mail
+(<v2.1).  Outlook Express breaks more badly though, without this it may show
+user "Message no longer in server" errors.  Note that OE6 still breaks even
+with this workaround if synchronization is set to "Headers Only".
 
 @item tb-extra-mailbox-sep
-Thunderbird gets somehow confused with LAYOUT=fs (mbox and dbox) and
-adds extra @samp{/} suffixes to mailbox names.  This option causes Dovecot to
+Thunderbird gets somehow confused with LAYOUT=fs (mbox and dbox) and adds
+extra @samp{/} suffixes to mailbox names.  This option causes Dovecot to
 ignore the extra @samp{/} instead of treating it as invalid mailbox name.
 
 @item tb-lsub-flags
-Show \Noselect flags for LSUB replies with LAYOUT=fs (e.g. mbox).
-This makes Thunderbird realize they aren't selectable and show them
-greyed out, instead of only later giving "not selectable" popup error.
+Show \Noselect flags for LSUB replies with LAYOUT=fs (e.g. mbox).  This
+makes Thunderbird realize they aren't selectable and show them greyed out,
+instead of only later giving "not selectable" popup error.
 @end table
 Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string imap-urlauth-host
-Host allowed in URLAUTH URLs sent by client.  "*" allows all.
-Defaults to @samp{""}.
+Host allowed in URLAUTH URLs sent by client.  "*" allows all.  Defaults to
address@hidden""}.
 @end deftypevr
 
 
-Whew!  Lots of configuration options.  The nice thing about it though is
-that GuixSD has a complete interface to Dovecot's configuration
-language.  This allows not only a nice way to declare configurations,
-but also offers reflective capabilities as well: users can write code to
-inspect and transform configurations from within Scheme.
+Whew! Lots of configuration options.  The nice thing about it though is that
+GuixSD has a complete interface to Dovecot's configuration language.  This
+allows not only a nice way to declare configurations, but also offers
+reflective capabilities as well: users can write code to inspect and
+transform configurations from within Scheme.
 
-However, it could be that you just want to get a @code{dovecot.conf} up
-and running.  In that case, you can pass an
address@hidden as the @code{#:config} parameter to
address@hidden  As its name indicates, an opaque configuration
-does not have easy reflective capabilities.
+However, it could be that you just want to get a @code{dovecot.conf} up and
+running.  In that case, you can pass an @code{opaque-dovecot-configuration}
+as the @code{#:config} parameter to @code{dovecot-service}.  As its name
+indicates, an opaque configuration does not have easy reflective
+capabilities.
 
 Available @code{opaque-dovecot-configuration} fields are:
 
@@ -15502,8 +15362,8 @@ The dovecot package.
 The contents of the @code{dovecot.conf}, as a string.
 @end deftypevr
 
-For example, if your @code{dovecot.conf} is just the empty string, you
-could instantiate a dovecot service like this:
+For example, if your @code{dovecot.conf} is just the empty string, you could
+instantiate a dovecot service like this:
 
 @example
 (dovecot-service #:config
@@ -15514,9 +15374,9 @@ could instantiate a dovecot service like this:
 @subsubheading OpenSMTPD Service
 
 @deffn {Scheme Variable} opensmtpd-service-type
-This is the type of the @uref{https://www.opensmtpd.org, OpenSMTPD}
-service, whose value should be an @code{opensmtpd-configuration} object
-as in this example:
+This is the type of the @uref{https://www.opensmtpd.org, OpenSMTPD} service,
+whose value should be an @code{opensmtpd-configuration} object as in this
+example:
 
 @example
 (service opensmtpd-service-type
@@ -15533,10 +15393,10 @@ Data type representing the configuration of opensmtpd.
 Package object of the OpenSMTPD SMTP server.
 
 @item @code{config-file} (default: @var{%default-opensmtpd-file})
-File-like object of the OpenSMTPD configuration file to use.  By default
-it listens on the loopback network interface, and allows for mail from
-users and daemons on the local machine, as well as permitting email to
-remote servers.  Run @command{man smtpd.conf} for more information.
+File-like object of the OpenSMTPD configuration file to use.  By default it
+listens on the loopback network interface, and allows for mail from users
+and daemons on the local machine, as well as permitting email to remote
+servers.  Run @command{man smtpd.conf} for more information.
 
 @end table
 @end deftp
@@ -15548,9 +15408,9 @@ remote servers.  Run @command{man smtpd.conf} for more 
information.
 @cindex SMTP
 
 @deffn {Scheme Variable} exim-service-type
-This is the type of the @uref{https://exim.org, Exim} mail transfer
-agent (MTA), whose value should be an @code{exim-configuration} object
-as in this example:
+This is the type of the @uref{https://exim.org, Exim} mail transfer agent
+(MTA), whose value should be an @code{exim-configuration} object as in this
+example:
 
 @example
 (service exim-service-type
@@ -15572,10 +15432,9 @@ Package object of the Exim server.
 
 @item @code{config-file} (default: @code{#f})
 File-like object of the Exim configuration file to use. If its value is
address@hidden then use the default configuration file from the package
-provided in @code{package}. The resulting configuration file is loaded
-after setting the @code{exim_user} and @code{exim_group} configuration
-variables.
address@hidden then use the default configuration file from the package provided
+in @code{package}. The resulting configuration file is loaded after setting
+the @code{exim_user} and @code{exim_group} configuration variables.
 
 @end table
 @end deftp
@@ -15602,20 +15461,20 @@ system. Each entry is of the form @code{(alias 
addresses ...)}, with
 @code{alias} specifying the local alias and @code{addresses} specifying
 where to deliver this user's mail.
 
-The aliases aren't required to exist as users on the local system. In
-the above example, there doesn't need to be a @code{postmaster} entry in
-the @code{operating-system}'s @code{user-accounts} in order to deliver
-the @code{postmaster} mail to @code{bob} (which subsequently would
-deliver mail to @code{bob@@example.com} and @code{bob@@example2.com}).
+The aliases aren't required to exist as users on the local system. In the
+above example, there doesn't need to be a @code{postmaster} entry in the
address@hidden's @code{user-accounts} in order to deliver the
address@hidden mail to @code{bob} (which subsequently would deliver mail
+to @code{bob@@example.com} and @code{bob@@example2.com}).
 
address@hidden Messaging Services
address@hidden Messaging Services
address@hidden Kurznachrichtendienste
address@hidden Kurznachrichtendienste
 
 @cindex messaging
 @cindex jabber
 @cindex XMPP
-The @code{(gnu services messaging)} module provides Guix service
-definitions for messaging services: currently only Prosody is supported.
+The @code{(gnu services messaging)} module provides Guix service definitions
+for messaging services: currently only Prosody is supported.
 
 @subsubheading Prosody Service
 
@@ -15648,8 +15507,8 @@ By default, Prosody does not need much configuration.  
Only one
 @code{virtualhosts} field is needed: it specifies the domain you wish
 Prosody to serve.
 
-You can perform various sanity checks on the generated configuration
-with the @code{prosodyctl check} command.
+You can perform various sanity checks on the generated configuration with
+the @code{prosodyctl check} command.
 
 Prosodyctl will also help you to import certificates from the
 @code{letsencrypt} directory so that the @code{prosody} user can access
@@ -15659,18 +15518,18 @@ them.  See @url{https://prosody.im/doc/letsencrypt}.
 prosodyctl --root cert import /etc/letsencrypt/live
 @end example
 
-The available configuration parameters follow.  Each parameter
-definition is preceded by its type; for example, @samp{string-list foo}
-indicates that the @code{foo} parameter should be specified as a list of
-strings.  Types starting with @code{maybe-} denote parameters that won't
-show up in @code{prosody.cfg.lua} when their value is @code{'disabled}.
+The available configuration parameters follow.  Each parameter definition is
+preceded by its type; for example, @samp{string-list foo} indicates that the
address@hidden parameter should be specified as a list of strings.  Types
+starting with @code{maybe-} denote parameters that won't show up in
address@hidden when their value is @code{'disabled}.
 
-There is also a way to specify the configuration as a string, if you
-have an old @code{prosody.cfg.lua} file that you want to port over from
-some other system; see the end for more details.
+There is also a way to specify the configuration as a string, if you have an
+old @code{prosody.cfg.lua} file that you want to port over from some other
+system; see the end for more details.
 
 The @code{file-object} type designates either a file-like object
-(@pxref{G-Expressions, file-like objects}) or a file name.
+(@pxref{G-Ausdrücke, file-like objects}) or a file name.
 
 @c The following documentation was initially generated by
 @c (generate-documentation) in (gnu services messaging).  Manually maintained
@@ -15688,67 +15547,65 @@ The Prosody package.
 
 @deftypevr address@hidden parameter} file-name data-path
 Location of the Prosody data storage directory.  See
address@hidden://prosody.im/doc/configure}.
-Defaults to @samp{"/var/lib/prosody"}.
address@hidden://prosody.im/doc/configure}.  Defaults to
address@hidden"/var/lib/prosody"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-object-list plugin-paths
-Additional plugin directories.  They are searched in all the specified
-paths in order.  See @url{https://prosody.im/doc/plugins_directory}.
-Defaults to @samp{()}.
+Additional plugin directories.  They are searched in all the specified paths
+in order.  See @url{https://prosody.im/doc/plugins_directory}.  Defaults to
address@hidden()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-name certificates
 Every virtual host and component needs a certificate so that clients and
 servers can securely verify its identity.  Prosody will automatically load
-certificates/keys from the directory specified here.
-Defaults to @samp{"/etc/prosody/certs"}.
+certificates/keys from the directory specified here.  Defaults to
address@hidden"/etc/prosody/certs"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string-list admins
 This is a list of accounts that are admins for the server.  Note that you
-must create the accounts separately.  See @url{https://prosody.im/doc/admins} 
and
address@hidden://prosody.im/doc/creating_accounts}.
-Example: @code{(admins '("user1@@example.com" "user2@@example.net"))}
-Defaults to @samp{()}.
+must create the accounts separately.  See
address@hidden://prosody.im/doc/admins} and
address@hidden://prosody.im/doc/creating_accounts}.  Example: @code{(admins
+'("user1@@example.com" "user2@@example.net"))} Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean use-libevent?
 Enable use of libevent for better performance under high load.  See
address@hidden://prosody.im/doc/libevent}.
-Defaults to @samp{#f}.
address@hidden://prosody.im/doc/libevent}.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} module-list modules-enabled
 This is the list of modules Prosody will load on startup.  It looks for
address@hidden in the plugins folder, so make sure that exists too.
-Documentation on modules can be found at:
address@hidden://prosody.im/doc/modules}.
-Defaults to @samp{("roster" "saslauth" "tls" "dialback" "disco" "carbons" 
"private" "blocklist" "vcard" "version" "uptime" "time" "ping" "pep" "register" 
"admin_adhoc")}.
address@hidden in the plugins folder, so make sure that exists
+too.  Documentation on modules can be found at:
address@hidden://prosody.im/doc/modules}.  Defaults to @samp{("roster"
+"saslauth" "tls" "dialback" "disco" "carbons" "private" "blocklist" "vcard"
+"version" "uptime" "time" "ping" "pep" "register" "admin_adhoc")}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string-list modules-disabled
address@hidden"offline"}, @samp{"c2s"} and @samp{"s2s"} are auto-loaded, but
-should you want to disable them then add them to this list.
-Defaults to @samp{()}.
address@hidden"offline"}, @samp{"c2s"} and @samp{"s2s"} are auto-loaded, but 
should
+you want to disable them then add them to this list.  Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} file-object groups-file
 Path to a text file where the shared groups are defined.  If this path is
 empty then @samp{mod_groups} does nothing.  See
address@hidden://prosody.im/doc/modules/mod_groups}.
-Defaults to @samp{"/var/lib/prosody/sharedgroups.txt"}.
address@hidden://prosody.im/doc/modules/mod_groups}.  Defaults to
address@hidden"/var/lib/prosody/sharedgroups.txt"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean allow-registration?
 Disable account creation by default, for security.  See
address@hidden://prosody.im/doc/creating_accounts}.
-Defaults to @samp{#f}.
address@hidden://prosody.im/doc/creating_accounts}.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} maybe-ssl-configuration ssl
-These are the SSL/TLS-related settings.  Most of them are disabled so to
-use Prosody's defaults.  If you do not completely understand these options, do
+These are the SSL/TLS-related settings.  Most of them are disabled so to use
+Prosody's defaults.  If you do not completely understand these options, do
 not add them to your config, it is easy to lower the security of your server
 using them.  See @url{https://prosody.im/doc/advanced_ssl_config}.
 
@@ -15768,8 +15625,8 @@ Path to your certificate file.
 
 @deftypevr address@hidden parameter} file-object capath
 Path to directory containing root certificates that you wish Prosody to
-trust when verifying the certificates of remote servers.
-Defaults to @samp{"/etc/ssl/certs"}.
+trust when verifying the certificates of remote servers.  Defaults to
address@hidden"/etc/ssl/certs"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} maybe-file-object cafile
@@ -15784,8 +15641,8 @@ A list of verification options (these mostly map to 
OpenSSL's
 
 @deftypevr address@hidden parameter} maybe-string-list options
 A list of general options relating to SSL/TLS.  These map to OpenSSL's
address@hidden()}.  For a full list of options available in LuaSec, see the
-LuaSec source.
address@hidden()}.  For a full list of options available in LuaSec, see
+the LuaSec source.
 @end deftypevr
 
 @deftypevr address@hidden parameter} maybe-non-negative-integer depth
@@ -15800,8 +15657,8 @@ clients, and in what order.
 
 @deftypevr address@hidden parameter} maybe-file-name dhparam
 A path to a file containing parameters for Diffie-Hellman key exchange.  You
-can create such a file with:
address@hidden dhparam -out /etc/prosody/certs/dh-2048.pem 2048}
+can create such a file with: @code{openssl dhparam -out
+/etc/prosody/certs/dh-2048.pem 2048}
 @end deftypevr
 
 @deftypevr address@hidden parameter} maybe-string curve
@@ -15821,58 +15678,53 @@ Password for encrypted private keys.
 
 @deftypevr address@hidden parameter} boolean c2s-require-encryption?
 Whether to force all client-to-server connections to be encrypted or not.
-See @url{https://prosody.im/doc/modules/mod_tls}.
-Defaults to @samp{#f}.
+See @url{https://prosody.im/doc/modules/mod_tls}.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string-list disable-sasl-mechanisms
 Set of mechanisms that will never be offered.  See
address@hidden://prosody.im/doc/modules/mod_saslauth}.
-Defaults to @samp{("DIGEST-MD5")}.
address@hidden://prosody.im/doc/modules/mod_saslauth}.  Defaults to
address@hidden("DIGEST-MD5")}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean s2s-require-encryption?
 Whether to force all server-to-server connections to be encrypted or not.
-See @url{https://prosody.im/doc/modules/mod_tls}.
-Defaults to @samp{#f}.
+See @url{https://prosody.im/doc/modules/mod_tls}.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} boolean s2s-secure-auth?
-Whether to require encryption and certificate authentication.  This
-provides ideal security, but requires servers you communicate with to support
+Whether to require encryption and certificate authentication.  This provides
+ideal security, but requires servers you communicate with to support
 encryption AND present valid, trusted certificates.  See
address@hidden://prosody.im/doc/s2s#security}.
-Defaults to @samp{#f}.
address@hidden://prosody.im/doc/s2s#security}.  Defaults to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string-list s2s-insecure-domains
 Many servers don't support encryption or have invalid or self-signed
 certificates.  You can list domains here that will not be required to
 authenticate using certificates.  They will be authenticated using DNS.  See
address@hidden://prosody.im/doc/s2s#security}.
-Defaults to @samp{()}.
address@hidden://prosody.im/doc/s2s#security}.  Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string-list s2s-secure-domains
 Even if you leave @code{s2s-secure-auth?} disabled, you can still require
 valid certificates for some domains by specifying a list here.  See
address@hidden://prosody.im/doc/s2s#security}.
-Defaults to @samp{()}.
address@hidden://prosody.im/doc/s2s#security}.  Defaults to @samp{()}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string authentication
 Select the authentication backend to use.  The default provider stores
-passwords in plaintext and uses Prosody's configured data storage to store the
-authentication data.  If you do not trust your server please see
address@hidden://prosody.im/doc/modules/mod_auth_internal_hashed} for 
information
-about using the hashed backend.  See also
address@hidden://prosody.im/doc/authentication}
-Defaults to @samp{"internal_plain"}.
+passwords in plaintext and uses Prosody's configured data storage to store
+the authentication data.  If you do not trust your server please see
address@hidden://prosody.im/doc/modules/mod_auth_internal_hashed} for
+information about using the hashed backend.  See also
address@hidden://prosody.im/doc/authentication} Defaults to
address@hidden"internal_plain"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} maybe-string log
-Set logging options.  Advanced logging configuration is not yet supported
-by the GuixSD Prosody Service.  See @url{https://prosody.im/doc/logging}.
+Set logging options.  Advanced logging configuration is not yet supported by
+the GuixSD Prosody Service.  See @url{https://prosody.im/doc/logging}.
 Defaults to @samp{"*syslog"}.
 @end deftypevr
 
@@ -15886,8 +15738,8 @@ Maximum allowed size of the HTTP body (in bytes).
 @end deftypevr
 
 @deftypevr address@hidden parameter} maybe-string http-external-url
-Some modules expose their own URL in various ways.  This URL is built
-from the protocol, host and port used.  If Prosody sits behind a proxy, the
+Some modules expose their own URL in various ways.  This URL is built from
+the protocol, host and port used.  If Prosody sits behind a proxy, the
 public URL will be @code{http-external-url} instead.  See
 @url{https://prosody.im/doc/http#external_url}.
 @end deftypevr
@@ -15896,19 +15748,27 @@ public URL will be @code{http-external-url} instead.  
See
 A host in Prosody is a domain on which user accounts can be created.  For
 example if you want your users to have addresses like
 @samp{"john.smith@@example.com"} then you need to add a host
address@hidden"example.com"}.  All options in this list will apply only to this 
host.
address@hidden"example.com"}.  All options in this list will apply only to this
+host.
 
-Note: the name "virtual" host is used in configuration to avoid confusion with
-the actual physical host that Prosody is installed on.  A single Prosody
-instance can serve many domains, each one defined as a VirtualHost entry in
-Prosody's configuration.  Conversely a server that hosts a single domain would
-have just one VirtualHost entry.
+Note: the name "virtual" host is used in configuration to avoid confusion
+with the actual physical host that Prosody is installed on.  A single
+Prosody instance can serve many domains, each one defined as a VirtualHost
+entry in Prosody's configuration.  Conversely a server that hosts a single
+domain would have just one VirtualHost entry.
 
 See @url{https://prosody.im/doc/configure#virtual_host_settings}.
 
 Available @code{virtualhost-configuration} fields are:
 
-all these @code{prosody-configuration} fields: @code{admins}, 
@code{use-libevent?}, @code{modules-enabled}, @code{modules-disabled}, 
@code{groups-file}, @code{allow-registration?}, @code{ssl}, 
@code{c2s-require-encryption?}, @code{disable-sasl-mechanisms}, 
@code{s2s-require-encryption?}, @code{s2s-secure-auth?}, 
@code{s2s-insecure-domains}, @code{s2s-secure-domains}, @code{authentication}, 
@code{log}, @code{http-max-content-size}, @code{http-external-url}, 
@code{raw-content}, plus:
+all these @code{prosody-configuration} fields: @code{admins},
address@hidden, @code{modules-enabled}, @code{modules-disabled},
address@hidden, @code{allow-registration?}, @code{ssl},
address@hidden, @code{disable-sasl-mechanisms},
address@hidden, @code{s2s-secure-auth?},
address@hidden, @code{s2s-secure-domains},
address@hidden, @code{log}, @code{http-max-content-size},
address@hidden, @code{raw-content}, plus:
 @deftypevr address@hidden parameter} string domain
 Domain you wish Prosody to serve.
 @end deftypevr
@@ -15921,16 +15781,22 @@ usually on a subdomain of the main server (such as
 @samp{"mycomponent.example.com"}).  Example components might be chatroom
 servers, user directories, or gateways to other protocols.
 
-Internal components are implemented with Prosody-specific plugins.  To add an
-internal component, you simply fill the hostname field, and the plugin you wish
-to use for the component.
+Internal components are implemented with Prosody-specific plugins.  To add
+an internal component, you simply fill the hostname field, and the plugin
+you wish to use for the component.
 
-See @url{https://prosody.im/doc/components}.
-Defaults to @samp{()}.
+See @url{https://prosody.im/doc/components}.  Defaults to @samp{()}.
 
 Available @code{int-component-configuration} fields are:
 
-all these @code{prosody-configuration} fields: @code{admins}, 
@code{use-libevent?}, @code{modules-enabled}, @code{modules-disabled}, 
@code{groups-file}, @code{allow-registration?}, @code{ssl}, 
@code{c2s-require-encryption?}, @code{disable-sasl-mechanisms}, 
@code{s2s-require-encryption?}, @code{s2s-secure-auth?}, 
@code{s2s-insecure-domains}, @code{s2s-secure-domains}, @code{authentication}, 
@code{log}, @code{http-max-content-size}, @code{http-external-url}, 
@code{raw-content}, plus:
+all these @code{prosody-configuration} fields: @code{admins},
address@hidden, @code{modules-enabled}, @code{modules-disabled},
address@hidden, @code{allow-registration?}, @code{ssl},
address@hidden, @code{disable-sasl-mechanisms},
address@hidden, @code{s2s-secure-auth?},
address@hidden, @code{s2s-secure-domains},
address@hidden, @code{log}, @code{http-max-content-size},
address@hidden, @code{raw-content}, plus:
 @deftypevr address@hidden parameter} string hostname
 Hostname of the component.
 @end deftypevr
@@ -15940,35 +15806,35 @@ Plugin you wish to use for the component.
 @end deftypevr
 
 @deftypevr address@hidden parameter} maybe-mod-muc-configuration mod-muc
-Multi-user chat (MUC) is Prosody's module for allowing you to create
-hosted chatrooms/conferences for XMPP users.
+Multi-user chat (MUC) is Prosody's module for allowing you to create hosted
+chatrooms/conferences for XMPP users.
 
-General information on setting up and using multi-user chatrooms can be found
-in the "Chatrooms" documentation (@url{https://prosody.im/doc/chatrooms}),
-which you should read if you are new to XMPP chatrooms.
+General information on setting up and using multi-user chatrooms can be
+found in the "Chatrooms" documentation
+(@url{https://prosody.im/doc/chatrooms}), which you should read if you are
+new to XMPP chatrooms.
 
 See also @url{https://prosody.im/doc/modules/mod_muc}.
 
 Available @code{mod-muc-configuration} fields are:
 
 @deftypevr address@hidden parameter} string name
-The name to return in service discovery responses.
-Defaults to @samp{"Prosody Chatrooms"}.
+The name to return in service discovery responses.  Defaults to
address@hidden"Prosody Chatrooms"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string-or-boolean restrict-room-creation
 If @samp{#t}, this will only allow admins to create new chatrooms.
 Otherwise anyone can create a room.  The value @samp{"local"} restricts room
-creation to users on the service's parent domain.  E.g. 
@samp{user@@example.com}
-can create rooms on @samp{rooms.example.com}.  The value @samp{"admin"}
-restricts to service administrators only.
-Defaults to @samp{#f}.
+creation to users on the service's parent domain.
+E.g. @samp{user@@example.com} can create rooms on @samp{rooms.example.com}.
+The value @samp{"admin"} restricts to service administrators only.  Defaults
+to @samp{#f}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer max-history-messages
 Maximum number of history messages that will be sent to the member that has
-just joined the room.
-Defaults to @samp{20}.
+just joined the room.  Defaults to @samp{20}.
 @end deftypevr
 
 @end deftypevr
@@ -15976,14 +15842,20 @@ Defaults to @samp{20}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} ext-component-configuration-list 
ext-components
-External components use XEP-0114, which most standalone components
-support.  To add an external component, you simply fill the hostname field.  
See
address@hidden://prosody.im/doc/components}.
-Defaults to @samp{()}.
+External components use XEP-0114, which most standalone components support.
+To add an external component, you simply fill the hostname field.  See
address@hidden://prosody.im/doc/components}.  Defaults to @samp{()}.
 
 Available @code{ext-component-configuration} fields are:
 
-all these @code{prosody-configuration} fields: @code{admins}, 
@code{use-libevent?}, @code{modules-enabled}, @code{modules-disabled}, 
@code{groups-file}, @code{allow-registration?}, @code{ssl}, 
@code{c2s-require-encryption?}, @code{disable-sasl-mechanisms}, 
@code{s2s-require-encryption?}, @code{s2s-secure-auth?}, 
@code{s2s-insecure-domains}, @code{s2s-secure-domains}, @code{authentication}, 
@code{log}, @code{http-max-content-size}, @code{http-external-url}, 
@code{raw-content}, plus:
+all these @code{prosody-configuration} fields: @code{admins},
address@hidden, @code{modules-enabled}, @code{modules-disabled},
address@hidden, @code{allow-registration?}, @code{ssl},
address@hidden, @code{disable-sasl-mechanisms},
address@hidden, @code{s2s-secure-auth?},
address@hidden, @code{s2s-secure-domains},
address@hidden, @code{log}, @code{http-max-content-size},
address@hidden, @code{raw-content}, plus:
 @deftypevr address@hidden parameter} string component-secret
 Password which the component will use to log in.
 @end deftypevr
@@ -15995,24 +15867,23 @@ Hostname of the component.
 @end deftypevr
 
 @deftypevr address@hidden parameter} non-negative-integer-list component-ports
-Port(s) Prosody listens on for component connections.
-Defaults to @samp{(5347)}.
+Port(s) Prosody listens on for component connections.  Defaults to
address@hidden(5347)}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} string component-interface
-Interface Prosody listens on for component connections.
-Defaults to @samp{"127.0.0.1"}.
+Interface Prosody listens on for component connections.  Defaults to
address@hidden"127.0.0.1"}.
 @end deftypevr
 
 @deftypevr address@hidden parameter} maybe-raw-content raw-content
 Raw content that will be added to the configuration file.
 @end deftypevr
 
-It could be that you just want to get a @code{prosody.cfg.lua}
-up and running.  In that case, you can pass an
address@hidden record as the value of
address@hidden  As its name indicates, an opaque configuration
-does not have easy reflective capabilities.
+It could be that you just want to get a @code{prosody.cfg.lua} up and
+running.  In that case, you can pass an @code{opaque-prosody-configuration}
+record as the value of @code{prosody-service-type}.  As its name indicates,
+an opaque configuration does not have easy reflective capabilities.
 Available @code{opaque-prosody-configuration} fields are:
 
 @deftypevr address@hidden parameter} package prosody
@@ -16023,8 +15894,8 @@ The prosody package.
 The contents of the @code{prosody.cfg.lua} to use.
 @end deftypevr
 
-For example, if your @code{prosody.cfg.lua} is just the empty
-string, you could instantiate a prosody service like this:
+For example, if your @code{prosody.cfg.lua} is just the empty string, you
+could instantiate a prosody service like this:
 
 @example
 (service prosody-service-type
@@ -16038,13 +15909,12 @@ string, you could instantiate a prosody service like 
this:
 
 @cindex IRC (Internet Relay Chat)
 @cindex IRC gateway
address@hidden://bitlbee.org,BitlBee} is a gateway that provides an IRC
-interface to a variety of messaging protocols such as XMPP.
address@hidden://bitlbee.org,BitlBee} is a gateway that provides an IRC 
interface
+to a variety of messaging protocols such as XMPP.
 
 @defvr {Scheme Variable} bitlbee-service-type
 This is the service type for the @url{http://bitlbee.org,BitlBee} IRC
-gateway daemon.  Its value is a @code{bitlbee-configuration} (see
-below).
+gateway daemon.  Its value is a @code{bitlbee-configuration} (see below).
 
 To have BitlBee listen on port 6667 on localhost, add this line to your
 services:
@@ -16060,12 +15930,12 @@ This is the configuration for BitlBee, with the 
following fields:
 @table @asis
 @item @code{interface} (default: @code{"127.0.0.1"})
 @itemx @code{port} (default: @code{6667})
-Listen on the network interface corresponding to the IP address
-specified in @var{interface}, on @var{port}.
+Listen on the network interface corresponding to the IP address specified in
address@hidden, on @var{port}.
 
-When @var{interface} is @code{127.0.0.1}, only local clients can
-connect; when it is @code{0.0.0.0}, connections can come from any
-networking interface.
+When @var{interface} is @code{127.0.0.1}, only local clients can connect;
+when it is @code{0.0.0.0}, connections can come from any networking
+interface.
 
 @item @code{package} (default: @code{bitlbee})
 The BitlBee package to use.
@@ -16079,18 +15949,17 @@ Configuration snippet added as-is to the BitlBee 
configuration file.
 @end deftp
 
 
address@hidden Telephony Services
address@hidden Telephony Services
address@hidden Telefondienste
address@hidden Telefondienste
 
 @cindex Murmur (VoIP server)
 @cindex VoIP server
-This section describes how to set up and run a Murmur server.  Murmur is
-the server of the @uref{https://mumble.info, Mumble} voice-over-IP
-(VoIP) suite.
+This section describes how to set up and run a Murmur server.  Murmur is the
+server of the @uref{https://mumble.info, Mumble} voice-over-IP (VoIP) suite.
 
 @deftp {Data Type} murmur-configuration
-The service type for the Murmur server.  An example configuration can
-look like this:
+The service type for the Murmur server.  An example configuration can look
+like this:
 
 @example
 (service murmur-service-type
@@ -16102,17 +15971,16 @@ look like this:
           (ssl-key "/etc/letsencrypt/live/mumble.example.com/privkey.pem")))
 @end example
 
-After reconfiguring your system, you can manually set the murmur 
@code{SuperUser}
-password with the command that is printed during the activation phase.
+After reconfiguring your system, you can manually set the murmur
address@hidden password with the command that is printed during the
+activation phase.
 
-It is recommended to register a normal Mumble user account
-and grant it admin or moderator rights.
-You can use the @code{mumble} client to
-login as new normal user, register yourself, and log out.
-For the next step login with the name @code{SuperUser} use
-the @code{SuperUser} password that you set previously,
-and grant your newly registered mumble user administrator or moderator
-rights and create some channels.
+It is recommended to register a normal Mumble user account and grant it
+admin or moderator rights.  You can use the @code{mumble} client to login as
+new normal user, register yourself, and log out.  For the next step login
+with the name @code{SuperUser} use the @code{SuperUser} password that you
+set previously, and grant your newly registered mumble user administrator or
+moderator rights and create some channels.
 
 Available @code{murmur-configuration} fields are:
 
@@ -16142,33 +16010,34 @@ Maximum of users that can be connected to the server 
at once.
 Maximum voice traffic a user can send per second.
 
 @item @code{database-file} (default: @code{"/var/lib/murmur/db.sqlite"})
-File name of the sqlite database.
-The service's user will become the owner of the directory.
+File name of the sqlite database.  The service's user will become the owner
+of the directory.
 
 @item @code{log-file} (default: @code{"/var/log/murmur/murmur.log"})
-File name of the log file.
-The service's user will become the owner of the directory.
+File name of the log file.  The service's user will become the owner of the
+directory.
 
 @item @code{autoban-attempts} (default: @code{10})
-Maximum number of logins a user can make in @code{autoban-timeframe}
-without getting auto banned for @code{autoban-time}.
+Maximum number of logins a user can make in @code{autoban-timeframe} without
+getting auto banned for @code{autoban-time}.
 
 @item @code{autoban-timeframe} (default: @code{120})
 Timeframe for autoban in seconds.
 
 @item @code{autoban-time} (default: @code{300})
-Amount of time in seconds for which a client gets banned
-when violating the autoban limits.
+Amount of time in seconds for which a client gets banned when violating the
+autoban limits.
 
 @item @code{opus-threshold} (default: @code{100})
-Percentage of clients that need to support opus
-before switching over to opus audio codec.
+Percentage of clients that need to support opus before switching over to
+opus audio codec.
 
 @item @code{channel-nesting-limit} (default: @code{10})
 How deep channels can be nested at maximum.
 
 @item @code{channelname-regex} (default: @code{#f})
-A string in from of a Qt regular expression that channel names must conform to.
+A string in from of a Qt regular expression that channel names must conform
+to.
 
 @item @code{username-regex} (default: @code{#f})
 A string in from of a Qt regular expression that user names must conform to.
@@ -16181,14 +16050,16 @@ Maximum size in bytes that a user can send in one 
image message.
 
 @item @code{cert-required?} (default: @code{#f})
 If it is set to @code{#t} clients that use weak password authentification
-will not be accepted. Users must have completed the certificate wizard to join.
+will not be accepted. Users must have completed the certificate wizard to
+join.
 
 @item @code{remember-channel?} (defualt @code{#f})
-Should murmur remember the last channel each user was in when they disconnected
-and put them into the remembered channel when they rejoin.
+Should murmur remember the last channel each user was in when they
+disconnected and put them into the remembered channel when they rejoin.
 
 @item @code{allow-html?} (default: @code{#f})
-Should html be allowed in text messages, user comments, and channel 
descriptions.
+Should html be allowed in text messages, user comments, and channel
+descriptions.
 
 @item @code{allow-ping?} (default: @code{#f})
 Setting to true exposes the current user count, the maximum user count, and
@@ -16198,15 +16069,16 @@ Mumble client, this information is shown in the 
Connect dialog.
 Disabling this setting will prevent public listing of the server.
 
 @item @code{bonjour?} (default: @code{#f})
-Should the server advertise itself in the local network through the bonjour 
protocol.
+Should the server advertise itself in the local network through the bonjour
+protocol.
 
 @item @code{send-version?} (default: @code{#f})
 Should the murmur server version be exposed in ping requests.
 
 @item @code{log-days} (default: @code{31})
-Murmur also stores logs in the database, which are accessible via RPC.
-The default is 31 days of months, but you can set this setting to 0 to keep 
logs forever,
-or -1 to disable logging to the database.
+Murmur also stores logs in the database, which are accessible via RPC.  The
+default is 31 days of months, but you can set this setting to 0 to keep logs
+forever, or -1 to disable logging to the database.
 
 @item @code{obfuscate-ips?} (default @code{#t})
 Should logged ips be obfuscated to protect the privacy of users.
@@ -16224,35 +16096,37 @@ Filepath to the ssl private key used for encrypted 
connections.
 @end example
 
 @item @code{ssl-dh-params} (default: @code{#f})
-File name of a PEM-encoded file with Diffie-Hellman parameters
-for the SSL/TLS encryption.  Alternatively you set it to
address@hidden"@@ffdhe2048"}, @code{"@@ffdhe3072"}, @code{"@@ffdhe4096"}, 
@code{"@@ffdhe6144"}
-or @code{"@@ffdhe8192"} to use bundled parameters from RFC 7919.
+File name of a PEM-encoded file with Diffie-Hellman parameters for the
+SSL/TLS encryption.  Alternatively you set it to @code{"@@ffdhe2048"},
address@hidden"@@ffdhe3072"}, @code{"@@ffdhe4096"}, @code{"@@ffdhe6144"} or
address@hidden"@@ffdhe8192"} to use bundled parameters from RFC 7919.
 
 @item @code{ssl-ciphers} (default: @code{#f})
-The @code{ssl-ciphers} option chooses the cipher suites to make available for 
use
-in SSL/TLS.
+The @code{ssl-ciphers} option chooses the cipher suites to make available
+for use in SSL/TLS.
 
 This option is specified using
 @uref{https://www.openssl.org/docs/apps/ciphers.html#CIPHER-LIST-FORMAT,
 OpenSSL cipher list notation}.
 
-It is recommended that you try your cipher string using 'openssl ciphers 
<string>'
-before setting it here, to get a feel for which cipher suites you will get.
-After setting this option, it is recommend that you inspect your Murmur log
-to ensure that Murmur is using the cipher suites that you expected it to.
+It is recommended that you try your cipher string using 'openssl ciphers
+<string>' before setting it here, to get a feel for which cipher suites you
+will get.  After setting this option, it is recommend that you inspect your
+Murmur log to ensure that Murmur is using the cipher suites that you
+expected it to.
 
 Note: Changing this option may impact the backwards compatibility of your
-Murmur server, and can remove the ability for older Mumble clients to be able
-to connect to it.
+Murmur server, and can remove the ability for older Mumble clients to be
+able to connect to it.
 
 @item @code{public-registration} (default: @code{#f})
-Must be a @code{<murmur-public-registration-configuration>} record or 
@code{#f}.
+Must be a @code{<murmur-public-registration-configuration>} record or
address@hidden
 
 You can optionally register your server in the public server list that the
address@hidden client shows on startup.
-You cannot register your server if you have set a @code{server-password},
-or set @code{allow-ping} to @code{#f}.
address@hidden client shows on startup.  You cannot register your server if
+you have set a @code{server-password}, or set @code{allow-ping} to
address@hidden
 
 It might take a few hours until it shows up in the public list.
 
@@ -16266,41 +16140,41 @@ Configuration for public registration of a murmur 
service.
 
 @table @asis
 @item @code{name}
-This is a display name for your server. Not to be confused with the hostname.
+This is a display name for your server. Not to be confused with the
+hostname.
 
 @item @code{password}
-A password to identify your registration.
-Subsequent updates will need the same password. Don't lose your password.
+A password to identify your registration.  Subsequent updates will need the
+same password. Don't lose your password.
 
 @item @code{url}
-This should be a @code{http://} or @code{https://} link to your web
-site.
+This should be a @code{http://} or @code{https://} link to your web site.
 
 @item @code{hostname} (default: @code{#f})
-By default your server will be listed by its IP address.
-If it is set your server will be linked by this host name instead.
+By default your server will be listed by its IP address.  If it is set your
+server will be linked by this host name instead.
 @end table
 @end deftp
 
 
 
address@hidden Monitoring Services
address@hidden Monitoring Services
address@hidden Überwachungsdienste
address@hidden Überwachungsdienste
 
 @subsubheading Tailon Service
 
 @uref{https://tailon.readthedocs.io/, Tailon} is a web application for
 viewing and searching log files.
 
-The following example will configure the service with default values.
-By default, Tailon can be accessed on port 8080 (@code{http://localhost:8080}).
+The following example will configure the service with default values.  By
+default, Tailon can be accessed on port 8080 (@code{http://localhost:8080}).
 
 @example
 (service tailon-service-type)
 @end example
 
-The following example customises more of the Tailon configuration,
-adding @command{sed} to the list of allowed commands.
+The following example customises more of the Tailon configuration, adding
address@hidden to the list of allowed commands.
 
 @example
 (service tailon-service-type
@@ -16312,17 +16186,17 @@ adding @command{sed} to the list of allowed commands.
 
 
 @deftp {Data Type} tailon-configuration
-Data type representing the configuration of Tailon.
-This type has the following parameters:
+Data type representing the configuration of Tailon.  This type has the
+following parameters:
 
 @table @asis
 @item @code{config-file} (default: @code{(tailon-configuration-file)})
 The configuration file to use for Tailon. This can be set to a
 @dfn{tailon-configuration-file} record value, or any gexp
-(@pxref{G-Expressions}).
+(@pxref{G-Ausdrücke}).
 
-For example, to instead use a local file, the @code{local-file} function
-can be used:
+For example, to instead use a local file, the @code{local-file} function can
+be used:
 
 @example
 (service tailon-service-type
@@ -16337,15 +16211,14 @@ The tailon package to use.
 @end deftp
 
 @deftp {Data Type} tailon-configuration-file
-Data type representing the configuration options for Tailon.
-This type has the following parameters:
+Data type representing the configuration options for Tailon.  This type has
+the following parameters:
 
 @table @asis
 @item @code{files} (default: @code{(list "/var/log")})
-List of files to display. The list can include strings for a single file
-or directory, or a list, where the first item is the name of a
-subsection, and the remaining items are the files or directories in that
-subsection.
+List of files to display. The list can include strings for a single file or
+directory, or a list, where the first item is the name of a subsection, and
+the remaining items are the files or directories in that subsection.
 
 @item @code{bind} (default: @code{"localhost:8080"})
 Address and port to which Tailon should bind on.
@@ -16370,19 +16243,18 @@ Set @code{debug?} to @code{#t} to show debug messages.
 
 @item @code{wrap-lines} (default: @code{#t})
 Initial line wrapping state in the web interface. Set to @code{#t} to
-initially wrap lines (the default), or to @code{#f} to initially not
-wrap lines.
+initially wrap lines (the default), or to @code{#f} to initially not wrap
+lines.
 
 @item @code{http-auth} (default: @code{#f})
-HTTP authentication type to use. Set to @code{#f} to disable
-authentication (the default). Supported values are @code{"digest"} or
address@hidden"basic"}.
+HTTP authentication type to use. Set to @code{#f} to disable authentication
+(the default). Supported values are @code{"digest"} or @code{"basic"}.
 
 @item @code{users} (default: @code{#f})
 If HTTP authentication is enabled (see @code{http-auth}), access will be
-restricted to the credentials provided here. To configure users, use a
-list of pairs, where the first element of the pair is the username, and
-the 2nd element of the pair is the password.
+restricted to the credentials provided here. To configure users, use a list
+of pairs, where the first element of the pair is the username, and the 2nd
+element of the pair is the password.
 
 @example
 (tailon-configuration-file
@@ -16401,10 +16273,9 @@ Darkstat is a packet sniffer that captures network 
traffic, calculates
 statistics about usage, and serves reports over HTTP.
 
 @defvar {Scheme Variable} darkstat-service-type
-This is the service type for the
address@hidden://unix4lyfe.org/darkstat/, darkstat}
-service,  its value must be a @code{darkstat-configuration} record as in
-this example:
+This is the service type for the @uref{https://unix4lyfe.org/darkstat/,
+darkstat} service, its value must be a @code{darkstat-configuration} record
+as in this example:
 
 @example
 (service darkstat-service-type
@@ -16430,8 +16301,8 @@ Bind the web interface to the specified port.
 Bind the web interface to the specified address.
 
 @item @code{base} (default: @code{"/"})
-Specify the path of the base URL.  This can be useful if
address@hidden is accessed via a reverse proxy.
+Specify the path of the base URL.  This can be useful if @command{darkstat}
+is accessed via a reverse proxy.
 
 @end table
 @end deftp
@@ -16439,16 +16310,16 @@ Specify the path of the base URL.  This can be useful 
if
 @subsubheading Prometheus Node Exporter Service
 
 @cindex prometheus-node-exporter
-The Prometheus ``node exporter'' makes hardware and operating system statistics
-provided by the Linux kernel available for the Prometheus monitoring system.
-This service should be deployed on all physical nodes and virtual machines,
-where monitoring these statistics is desirable.
+The Prometheus ``node exporter'' makes hardware and operating system
+statistics provided by the Linux kernel available for the Prometheus
+monitoring system.  This service should be deployed on all physical nodes
+and virtual machines, where monitoring these statistics is desirable.
 
 @defvar {Scheme variable} prometheus-node-exporter-service-type
 This is the service type for the
address@hidden://github.com/prometheus/node_exporter/, prometheus-node-exporter}
-service, its value must be a @code{prometheus-node-exporter-configuration}
-record as in this example:
address@hidden://github.com/prometheus/node_exporter/,
+prometheus-node-exporter} service, its value must be a
address@hidden record as in this example:
 
 @example
 (service prometheus-node-exporter-service-type
@@ -16470,24 +16341,23 @@ Bind the web interface to the specified address.
 @end table
 @end deftp
 
address@hidden Kerberos Services
address@hidden Kerberos Services
address@hidden Kerberos-Dienste
address@hidden Kerberos-Dienste
 @cindex Kerberos
 
-The @code{(gnu services kerberos)} module provides services relating to
-the authentication protocol @dfn{Kerberos}.
+The @code{(gnu services kerberos)} module provides services relating to the
+authentication protocol @dfn{Kerberos}.
 
 @subsubheading Krb5 Service
 
-Programs using a Kerberos client library normally
-expect a configuration file in @file{/etc/krb5.conf}.
-This service generates such a file from a definition provided in the
-operating system declaration.
-It does not cause any daemon to be started.
+Programs using a Kerberos client library normally expect a configuration
+file in @file{/etc/krb5.conf}.  This service generates such a file from a
+definition provided in the operating system declaration.  It does not cause
+any daemon to be started.
 
-No ``keytab'' files are provided by this service---you must explicitly create 
them.
-This service is known to work with the MIT client library, @code{mit-krb5}.
-Other implementations have not been tested.
+No ``keytab'' files are provided by this service---you must explicitly
+create them.  This service is known to work with the MIT client library,
address@hidden  Other implementations have not been tested.
 
 @defvr {Scheme Variable} krb5-service-type
 A service type for Kerberos 5 clients.
@@ -16522,8 +16392,8 @@ specified by clients;
 @end itemize
 
 The @code{krb5-realm} and @code{krb5-configuration} types have many fields.
-Only the most commonly used ones are described here.
-For a full list, and more detailed explanation of each, see the MIT
+Only the most commonly used ones are described here.  For a full list, and
+more detailed explanation of each, see the MIT
 
@uref{http://web.mit.edu/kerberos/krb5-devel/doc/admin/conf_files/krb5_conf.html,,krb5.conf}
 documentation.
 
@@ -16532,17 +16402,17 @@ documentation.
 @cindex realm, kerberos
 @table @asis
 @item @code{name}
-This field is a string identifying the name of the realm.
-A common convention is to use the fully qualified DNS name of your 
organization,
+This field is a string identifying the name of the realm.  A common
+convention is to use the fully qualified DNS name of your organization,
 converted to upper case.
 
 @item @code{admin-server}
-This field is a string identifying the host where the administration server is
-running.
+This field is a string identifying the host where the administration server
+is running.
 
 @item @code{kdc}
-This field is a string identifying the key distribution center
-for the realm.
+This field is a string identifying the key distribution center for the
+realm.
 @end table
 @end deftp
 
@@ -16550,22 +16420,19 @@ for the realm.
 
 @table @asis
 @item @code{allow-weak-crypto?} (default: @code{#f})
-If this flag is @code{#t} then services which only offer encryption algorithms
-known to be weak will be accepted.
+If this flag is @code{#t} then services which only offer encryption
+algorithms known to be weak will be accepted.
 
 @item @code{default-realm} (default: @code{#f})
-This field should be a string identifying the default Kerberos
-realm for the client.
-You should set this field to the name of your Kerberos realm.
-If this value is @code{#f}
-then a realm must be specified with every Kerberos principal when invoking 
programs
-such as @command{kinit}.
+This field should be a string identifying the default Kerberos realm for the
+client.  You should set this field to the name of your Kerberos realm.  If
+this value is @code{#f} then a realm must be specified with every Kerberos
+principal when invoking programs such as @command{kinit}.
 
 @item @code{realms}
-This should be a non-empty list of @code{krb5-realm} objects, which clients may
-access.
-Normally, one of them will have a @code{name} field matching the 
@code{default-realm}
-field.
+This should be a non-empty list of @code{krb5-realm} objects, which clients
+may access.  Normally, one of them will have a @code{name} field matching
+the @code{default-realm} field.
 @end table
 @end deftp
 
@@ -16574,36 +16441,36 @@ field.
 @cindex pam-krb5
 
 The @code{pam-krb5} service allows for login authentication and password
-management via Kerberos.
-You will need this service if you want PAM enabled applications to authenticate
-users using Kerberos.
+management via Kerberos.  You will need this service if you want PAM enabled
+applications to authenticate users using Kerberos.
 
 @defvr {Scheme Variable} pam-krb5-service-type
 A service type for the Kerberos 5 PAM module.
 @end defvr
 
 @deftp {Data Type} pam-krb5-configuration
-Data type representing the configuration of the Kerberos 5 PAM module
-This type has the following parameters:
+Data type representing the configuration of the Kerberos 5 PAM module This
+type has the following parameters:
 @table @asis
 @item @code{pam-krb5} (default: @code{pam-krb5})
 The pam-krb5 package to use.
 
 @item @code{minimum-uid} (default: @code{1000})
-The smallest user ID for which Kerberos authentications should be attempted.
-Local accounts with lower values will silently fail to authenticate.
+The smallest user ID for which Kerberos authentications should be
+attempted.  Local accounts with lower values will silently fail to
+authenticate.
 @end table
 @end deftp
 
 
address@hidden Web Services
address@hidden Web Services
address@hidden Web-Dienste
address@hidden Web-Dienste
 
 @cindex web
 @cindex www
 @cindex HTTP
-The @code{(gnu services web)} module provides the Apache HTTP Server,
-the nginx web server, and also a fastcgi wrapper daemon.
+The @code{(gnu services web)} module provides the Apache HTTP Server, the
+nginx web server, and also a fastcgi wrapper daemon.
 
 @subsubheading Apache HTTP Server
 
@@ -16623,8 +16490,8 @@ A simple example configuration is given below.
                (document-root "/srv/http/www.example.com")))))
 @end example
 
-Other services can also extend the @code{httpd-service-type} to add to
-the configuration.
+Other services can also extend the @code{httpd-service-type} to add to the
+configuration.
 
 @example
 (simple-service 'my-extra-server httpd-service-type
@@ -16638,8 +16505,8 @@ the configuration.
 @end deffn
 
 The details for the @code{httpd-configuration}, @code{httpd-module},
address@hidden and @code{httpd-virtualhost} record types are
-given below.
address@hidden and @code{httpd-virtualhost} record types are given
+below.
 
 @deffn {Data Type} httpd-configuration
 This data type represents the configuration for the httpd service.
@@ -16652,10 +16519,10 @@ The httpd package to use.
 The pid file used by the shepherd-service.
 
 @item @code{config} (default: @code{(httpd-config-file)})
-The configuration file to use with the httpd service. The default value
-is a @code{httpd-config-file} record, but this can also be a different
-G-expression that generates a file, for example a @code{plain-file}. A
-file outside of the store can also be specified through a string.
+The configuration file to use with the httpd service. The default value is a
address@hidden record, but this can also be a different
+G-expression that generates a file, for example a @code{plain-file}. A file
+outside of the store can also be specified through a string.
 
 @end table
 @end deffn
@@ -16669,9 +16536,8 @@ The name of the module.
 
 @item @code{file}
 The file for the module. This can be relative to the httpd package being
-used, the absolute location of a file, or a G-expression for a file
-within the store, for example @code{(file-append mod-wsgi
-"/modules/mod_wsgi.so")}.
+used, the absolute location of a file, or a G-expression for a file within
+the store, for example @code{(file-append mod-wsgi "/modules/mod_wsgi.so")}.
 
 @end table
 @end deffn
@@ -16716,31 +16582,28 @@ For example, in order to handle requests for PHP 
files, you can use Apache’s
 
 @item @code{server-root} (default: @code{httpd})
 The @code{ServerRoot} in the configuration file, defaults to the httpd
-package. Directives including @code{Include} and @code{LoadModule} are
-taken as relative to the server root.
+package. Directives including @code{Include} and @code{LoadModule} are taken
+as relative to the server root.
 
 @item @code{server-name} (default: @code{#f})
-The @code{ServerName} in the configuration file, used to specify the
-request scheme, hostname and port that the server uses to identify
-itself.
+The @code{ServerName} in the configuration file, used to specify the request
+scheme, hostname and port that the server uses to identify itself.
 
-This doesn't need to be set in the server config, and can be specifyed
-in virtual hosts. The default is @code{#f} to not specify a
address@hidden
+This doesn't need to be set in the server config, and can be specifyed in
+virtual hosts. The default is @code{#f} to not specify a @code{ServerName}.
 
 @item @code{document-root} (default: @code{"/srv/http"})
 The @code{DocumentRoot} from which files will be served.
 
 @item @code{listen} (default: @code{'("80")})
-The list of values for the @code{Listen} directives in the config
-file. The value should be a list of strings, when each string can
-specify the port number to listen on, and optionally the IP address and
-protocol to use.
+The list of values for the @code{Listen} directives in the config file. The
+value should be a list of strings, when each string can specify the port
+number to listen on, and optionally the IP address and protocol to use.
 
 @item @code{pid-file} (default: @code{"/var/run/httpd"})
-The @code{PidFile} to use. This should match the @code{pid-file} set in
-the @code{httpd-configuration} so that the Shepherd service is
-configured correctly.
+The @code{PidFile} to use. This should match the @code{pid-file} set in the
address@hidden so that the Shepherd service is configured
+correctly.
 
 @item @code{error-log} (default: @code{"/var/log/httpd/error_log"})
 The @code{ErrorLog} to which the server will log errors.
@@ -16752,17 +16615,17 @@ The @code{User} which the server will answer requests 
as.
 The @code{Group} which the server will answer requests as.
 
 @item @code{extra-config} (default: @code{(list "TypesConfig 
etc/httpd/mime.types")})
-A flat list of strings and G-expressions which will be added to the end
-of the configuration file.
+A flat list of strings and G-expressions which will be added to the end of
+the configuration file.
 
-Any values which the service is extended with will be appended to this
-list.
+Any values which the service is extended with will be appended to this list.
 
 @end table
 @end deffn
 
 @deffn {Data Type} httpd-virtualhost
-This data type represents a virtualhost configuration block for the httpd 
service.
+This data type represents a virtualhost configuration block for the httpd
+service.
 
 These should be added to the extra-config for the httpd-service.
 
@@ -16781,8 +16644,8 @@ These should be added to the extra-config for the 
httpd-service.
 The addresses and ports for the @code{VirtualHost} directive.
 
 @item @code{contents}
-The contents of the @code{VirtualHost} directive, this should be a list
-of strings and G-expressions.
+The contents of the @code{VirtualHost} directive, this should be a list of
+strings and G-expressions.
 
 @end table
 @end deffn
@@ -16790,8 +16653,8 @@ of strings and G-expressions.
 @subsubheading NGINX
 
 @deffn {Scheme Variable} nginx-service-type
-Service type for the @uref{https://nginx.org/,NGinx} web server.  The
-value for this service type is a @code{<nginx-configuration>} record.
+Service type for the @uref{https://nginx.org/,NGinx} web server.  The value
+for this service type is a @code{<nginx-configuration>} record.
 
 A simple example configuration is given below.
 
@@ -16804,9 +16667,9 @@ A simple example configuration is given below.
                      (root "/srv/http/www.example.com"))))))
 @end example
 
-In addition to adding server blocks to the service configuration
-directly, this service can be extended by other services to add server
-blocks, as in this example:
+In addition to adding server blocks to the service configuration directly,
+this service can be extended by other services to add server blocks, as in
+this example:
 
 @example
 (simple-service 'my-extra-server nginx-service-type
@@ -16816,19 +16679,19 @@ blocks, as in this example:
 @end example
 @end deffn
 
-At startup, @command{nginx} has not yet read its configuration file, so
-it uses a default file to log error messages.  If it fails to load its
+At startup, @command{nginx} has not yet read its configuration file, so it
+uses a default file to log error messages.  If it fails to load its
 configuration file, that is where error messages are logged.  After the
 configuration file is loaded, the default error log file changes as per
 configuration.  In our case, startup error messages can be found in
 @file{/var/run/nginx/logs/error.log}, and after configuration in
address@hidden/var/log/nginx/error.log}.  The second location can be changed
-with the @var{log-directory} configuration option.
address@hidden/var/log/nginx/error.log}.  The second location can be changed 
with
+the @var{log-directory} configuration option.
 
 @deffn {Data Type} nginx-configuration
-This data type represents the configuration for NGinx. Some
-configuration can be done through this and the other provided record
-types, or alternatively, a config file can be provided.
+This data type represents the configuration for NGinx. Some configuration
+can be done through this and the other provided record types, or
+alternatively, a config file can be provided.
 
 @table @asis
 @item @code{nginx} (default: @code{nginx})
@@ -16842,13 +16705,11 @@ The directory in which NGinx will create a pid file, 
and write temporary
 files.
 
 @item @code{server-blocks} (default: @code{'()})
-A list of @dfn{server blocks} to create in the generated configuration
-file, the elements should be of type
address@hidden<nginx-server-configuration>}.
+A list of @dfn{server blocks} to create in the generated configuration file,
+the elements should be of type @code{<nginx-server-configuration>}.
 
-The following example would setup NGinx to serve @code{www.example.com}
-from the @code{/srv/http/www.example.com} directory, without using
-HTTPS.
+The following example would setup NGinx to serve @code{www.example.com} from
+the @code{/srv/http/www.example.com} directory, without using HTTPS.
 @example
 (service nginx-service-type
          (nginx-configuration
@@ -16860,15 +16721,13 @@ HTTPS.
 
 @item @code{upstream-blocks} (default: @code{'()})
 A list of @dfn{upstream blocks} to create in the generated configuration
-file, the elements should be of type
address@hidden<nginx-upstream-configuration>}.
+file, the elements should be of type @code{<nginx-upstream-configuration>}.
 
-Configuring upstreams through the @code{upstream-blocks} can be useful
-when combined with @code{locations} in the
address@hidden<nginx-server-configuration>} records.  The following example
-creates a server configuration with one location configuration, that
-will proxy requests to a upstream configuration, which will handle
-requests with two servers.
+Configuring upstreams through the @code{upstream-blocks} can be useful when
+combined with @code{locations} in the @code{<nginx-server-configuration>}
+records.  The following example creates a server configuration with one
+location configuration, that will proxy requests to a upstream
+configuration, which will handle requests with two servers.
 
 @example
 (service
@@ -16894,16 +16753,16 @@ requests with two servers.
 If a configuration @var{file} is provided, this will be used, rather than
 generating a configuration file from the provided @code{log-directory},
 @code{run-directory}, @code{server-blocks} and @code{upstream-blocks}.  For
-proper operation, these arguments should match what is in @var{file} to ensure
-that the directories are created when the service is activated.
+proper operation, these arguments should match what is in @var{file} to
+ensure that the directories are created when the service is activated.
 
-This can be useful if you have an existing configuration file, or it's
-not possible to do what is required through the other parts of the
+This can be useful if you have an existing configuration file, or it's not
+possible to do what is required through the other parts of the
 nginx-configuration record.
 
 @item @code{server-names-hash-bucket-size} (default: @code{#f})
-Bucket size for the server names hash tables, defaults to @code{#f} to
-use the size of the processors cache line.
+Bucket size for the server names hash tables, defaults to @code{#f} to use
+the size of the processors cache line.
 
 @item @code{server-names-hash-bucket-max-size} (default: @code{#f})
 Maximum bucket size for the server names hash tables.
@@ -16916,47 +16775,47 @@ valued G-expression.
 @end deffn
 
 @deftp {Data Type} nginx-server-configuration
-Data type representing the configuration of an nginx server block.
-This type has the following parameters:
+Data type representing the configuration of an nginx server block.  This
+type has the following parameters:
 
 @table @asis
 @item @code{listen} (default: @code{'("80" "443 ssl")})
-Each @code{listen} directive sets the address and port for IP, or the
-path for a UNIX-domain socket on which the server will accept requests.
-Both address and port, or only address or only port can be specified.
-An address may also be a hostname, for example:
+Each @code{listen} directive sets the address and port for IP, or the path
+for a UNIX-domain socket on which the server will accept requests.  Both
+address and port, or only address or only port can be specified.  An address
+may also be a hostname, for example:
 
 @example
 '("127.0.0.1:8000" "127.0.0.1" "8000" "*:8000" "localhost:8000")
 @end example
 
 @item @code{server-name} (default: @code{(list 'default)})
-A list of server names this server represents. @code{'default} represents the
-default server for connections matching no other server.
+A list of server names this server represents. @code{'default} represents
+the default server for connections matching no other server.
 
 @item @code{root} (default: @code{"/srv/http"})
 Root of the website nginx will serve.
 
 @item @code{locations} (default: @code{'()})
 A list of @dfn{nginx-location-configuration} or
address@hidden records to use within this
-server block.
address@hidden records to use within this server
+block.
 
 @item @code{index} (default: @code{(list "index.html")})
-Index files to look for when clients ask for a directory.  If it cannot be 
found,
-Nginx will send the list of files in the directory.
+Index files to look for when clients ask for a directory.  If it cannot be
+found, Nginx will send the list of files in the directory.
 
 @item @code{try-files} (default: @code{'()})
 A list of files whose existence is checked in the specified order.
 @code{nginx} will use the first file it finds to process the request.
 
 @item @code{ssl-certificate} (default: @code{#f})
-Where to find the certificate for secure connections.  Set it to @code{#f} if
-you don't have a certificate or you don't want to use HTTPS.
+Where to find the certificate for secure connections.  Set it to @code{#f}
+if you don't have a certificate or you don't want to use HTTPS.
 
 @item @code{ssl-certificate-key} (default: @code{#f})
-Where to find the private key for secure connections.  Set it to @code{#f} if
-you don't have a key or you don't want to use HTTPS.
+Where to find the private key for secure connections.  Set it to @code{#f}
+if you don't have a key or you don't want to use HTTPS.
 
 @item @code{server-tokens?} (default: @code{#f})
 Whether the server should add its configuration to response.
@@ -16968,8 +16827,8 @@ A list of raw lines added to the server block.
 @end deftp
 
 @deftp {Data Type} nginx-upstream-configuration
-Data type representing the configuration of an nginx @code{upstream}
-block.  This type has the following parameters:
+Data type representing the configuration of an nginx @code{upstream} block.
+This type has the following parameters:
 
 @table @asis
 @item @code{name}
@@ -16979,16 +16838,15 @@ Name for this group of servers.
 Specify the addresses of the servers in the group.  The address can be
 specified as a IP address (e.g. @samp{127.0.0.1}), domain name
 (e.g. @samp{backend1.example.com}) or a path to a UNIX socket using the
-prefix @samp{unix:}.  For addresses using an IP address or domain name,
-the default port is 80, and a different port can be specified
-explicitly.
+prefix @samp{unix:}.  For addresses using an IP address or domain name, the
+default port is 80, and a different port can be specified explicitly.
 
 @end table
 @end deftp
 
 @deftp {Data Type} nginx-location-configuration
-Data type representing the configuration of an nginx @code{location}
-block.  This type has the following parameters:
+Data type representing the configuration of an nginx @code{location} block.
+This type has the following parameters:
 
 @table @asis
 @item @code{uri}
@@ -16997,20 +16855,18 @@ URI which this location block matches.
 @anchor{nginx-location-configuration body}
 @item @code{body}
 Body of the location block, specified as a list of strings. This can contain
-many
-configuration directives.  For example, to pass requests to a upstream
-server group defined using an @code{nginx-upstream-configuration} block,
-the following directive would be specified in the body @samp{(list "proxy_pass
+many configuration directives.  For example, to pass requests to a upstream
+server group defined using an @code{nginx-upstream-configuration} block, the
+following directive would be specified in the body @samp{(list "proxy_pass
 http://upstream-name;";)}.
 
 @end table
 @end deftp
 
 @deftp {Data Type} nginx-named-location-configuration
-Data type representing the configuration of an nginx named location
-block.  Named location blocks are used for request redirection, and not
-used for regular request processing.  This type has the following
-parameters:
+Data type representing the configuration of an nginx named location block.
+Named location blocks are used for request redirection, and not used for
+regular request processing.  This type has the following parameters:
 
 @table @asis
 @item @code{name}
@@ -17019,26 +16875,26 @@ Name to identify this location block.
 @item @code{body}
 @xref{nginx-location-configuration body}, as the body for named location
 blocks can be used in a similar way to the
address@hidden body}.  One restriction is that the
-body of a named location block cannot contain location blocks.
address@hidden body}.  One restriction is that the body
+of a named location block cannot contain location blocks.
 
 @end table
 @end deftp
 
 @subsubheading Varnish Cache
 @cindex Varnish
-Varnish is a fast cache server that sits in between web applications
-and end users.  It proxies requests from clients and caches the
-accessed URLs such that multiple requests for the same resource only
-creates one request to the back-end.
+Varnish is a fast cache server that sits in between web applications and end
+users.  It proxies requests from clients and caches the accessed URLs such
+that multiple requests for the same resource only creates one request to the
+back-end.
 
 @defvr {Scheme Variable} varnish-service-type
 Service type for the Varnish daemon.
 @end defvr
 
 @deftp {Data Type} varnish-configuration
-Data type representing the @code{varnish} service configuration.
-This type has the following parameters:
+Data type representing the @code{varnish} service configuration.  This type
+has the following parameters:
 
 @table @asis
 @item @code{package} (default: @code{varnish})
@@ -17046,9 +16902,9 @@ The Varnish package to use.
 
 @item @code{name} (default: @code{"default"})
 A name for this Varnish instance.  Varnish will create a directory in
address@hidden/var/varnish/} with this name and keep temporary files there.  If
-the name starts with a forward slash, it is interpreted as an absolute
-directory name.
address@hidden/var/varnish/} with this name and keep temporary files there.  If 
the
+name starts with a forward slash, it is interpreted as an absolute directory
+name.
 
 Pass the @code{-n} argument to other Varnish programs to connect to the
 named instance, e.g. @command{varnishncsa -n default}.
@@ -17057,14 +16913,14 @@ named instance, e.g. @command{varnishncsa -n default}.
 The backend to use.  This option has no effect if @code{vcl} is set.
 
 @item @code{vcl} (default: #f)
-The @dfn{VCL} (Varnish Configuration Language) program to run.  If this
-is @code{#f}, Varnish will proxy @code{backend} using the default
-configuration.  Otherwise this must be a file-like object with valid
-VCL syntax.
+The @dfn{VCL} (Varnish Configuration Language) program to run.  If this is
address@hidden, Varnish will proxy @code{backend} using the default
+configuration.  Otherwise this must be a file-like object with valid VCL
+syntax.
 
 @c Varnish does not support HTTPS, so keep this URL to avoid confusion.
-For example, to mirror @url{http://www.gnu.org,www.gnu.org} with VCL you
-can do something along these lines:
+For example, to mirror @url{http://www.gnu.org,www.gnu.org} with VCL you can
+do something along these lines:
 
 @example
 (define %gnu-mirror
@@ -17086,8 +16942,8 @@ The configuration of an already running Varnish 
instance can be inspected
 and changed using the @command{varnishadm} program.
 
 Consult the @url{https://varnish-cache.org/docs/,Varnish User Guide} and
address@hidden://book.varnish-software.com/4.0/,Varnish Book} for
-comprehensive documentation on Varnish and its configuration language.
address@hidden://book.varnish-software.com/4.0/,Varnish Book} for comprehensive
+documentation on Varnish and its configuration language.
 
 @item @code{listen} (default: @code{'("localhost:80")})
 List of addresses Varnish will listen on.
@@ -17109,17 +16965,16 @@ Additional arguments to pass to the 
@command{varnishd} process.
 @cindex fcgiwrap
 FastCGI is an interface between the front-end and the back-end of a web
 service.  It is a somewhat legacy facility; new web services should
-generally just talk HTTP between the front-end and the back-end.
-However there are a number of back-end services such as PHP or the
-optimized HTTP Git repository access that use FastCGI, so we have
-support for it in Guix.
+generally just talk HTTP between the front-end and the back-end.  However
+there are a number of back-end services such as PHP or the optimized HTTP
+Git repository access that use FastCGI, so we have support for it in Guix.
 
 To use FastCGI, you configure the front-end web server (e.g., nginx) to
-dispatch some subset of its requests to the fastcgi backend, which
-listens on a local TCP or UNIX socket.  There is an intermediary
address@hidden program that sits between the actual backend process and
-the web server.  The front-end indicates which backend program to run,
-passing that information to the @code{fcgiwrap} process.
+dispatch some subset of its requests to the fastcgi backend, which listens
+on a local TCP or UNIX socket.  There is an intermediary @code{fcgiwrap}
+program that sits between the actual backend process and the web server.
+The front-end indicates which backend program to run, passing that
+information to the @code{fcgiwrap} process.
 
 @defvr {Scheme Variable} fcgiwrap-service-type
 A service type for the @code{fcgiwrap} FastCGI proxy.
@@ -17133,31 +16988,30 @@ This type has the following parameters:
 The fcgiwrap package to use.
 
 @item @code{socket} (default: @code{tcp:127.0.0.1:9000})
-The socket on which the @code{fcgiwrap} process should listen, as a
-string.  Valid @var{socket} values include
address@hidden:@var{/path/to/unix/socket}},
+The socket on which the @code{fcgiwrap} process should listen, as a string.
+Valid @var{socket} values include @code{unix:@var{/path/to/unix/socket}},
 @code{tcp:@var{dot.ted.qu.ad}:@var{port}} and
 @code{tcp6:address@hidden:port}.
 
 @item @code{user} (default: @code{fcgiwrap})
 @itemx @code{group} (default: @code{fcgiwrap})
-The user and group names, as strings, under which to run the
address@hidden process.  The @code{fastcgi} service will ensure that if
-the user asks for the specific user or group names @code{fcgiwrap} that
-the corresponding user and/or group is present on the system.
+The user and group names, as strings, under which to run the @code{fcgiwrap}
+process.  The @code{fastcgi} service will ensure that if the user asks for
+the specific user or group names @code{fcgiwrap} that the corresponding user
+and/or group is present on the system.
 
 It is possible to configure a FastCGI-backed web service to pass HTTP
-authentication information from the front-end to the back-end, and to
-allow @code{fcgiwrap} to run the back-end process as a corresponding
-local user.  To enable this capability on the back-end., run
address@hidden as the @code{root} user and group.  Note that this
-capability also has to be configured on the front-end as well.
+authentication information from the front-end to the back-end, and to allow
address@hidden to run the back-end process as a corresponding local user.
+To enable this capability on the back-end., run @code{fcgiwrap} as the
address@hidden user and group.  Note that this capability also has to be
+configured on the front-end as well.
 @end table
 @end deftp
 
 @cindex php-fpm
-PHP-FPM (FastCGI Process Manager) is an alternative PHP FastCGI implementation
-with some additional features useful for sites of any size.
+PHP-FPM (FastCGI Process Manager) is an alternative PHP FastCGI
+implementation with some additional features useful for sites of any size.
 
 These features include:
 @itemize @bullet
@@ -17205,36 +17059,35 @@ User who can speak to the php-fpm socket.
 @item @code{socket-group} (default: @code{php-fpm})
 Group that can speak to the php-fpm socket.
 @item @code{pid-file} (default: @code{(string-append "/var/run/php" 
(version-major (package-version php)) "-fpm.pid")})
-The process id of the php-fpm process is written to this file
-once the service has started.
+The process id of the php-fpm process is written to this file once the
+service has started.
 @item @code{log-file} (default: @code{(string-append "/var/log/php" 
(version-major (package-version php)) "-fpm.log")})
 Log for the php-fpm master process.
 @item @code{process-manager} (default: 
@code{(php-fpm-dynamic-process-manager-configuration)})
-Detailed settings for the php-fpm process manager.
-Must be either:
+Detailed settings for the php-fpm process manager.  Must be either:
 @table @asis
 @item @code{<php-fpm-dynamic-process-manager-configuration>}
 @item @code{<php-fpm-static-process-manager-configuration>}
 @item @code{<php-fpm-on-demand-process-manager-configuration>}
 @end table
 @item @code{display-errors} (default @code{#f})
-Determines whether php errors and warning should be sent to clients
-and displayed in their browsers.
-This is useful for local php development, but a security risk for public sites,
-as error messages can reveal passwords and personal data.
+Determines whether php errors and warning should be sent to clients and
+displayed in their browsers.  This is useful for local php development, but
+a security risk for public sites, as error messages can reveal passwords and
+personal data.
 @item @code{workers-logfile} (default @code{(string-append "/var/log/php" 
(version-major (package-version php)) "-fpm.www.log")})
-This file will log the @code{stderr} outputs of php worker processes.
-Can be set to @code{#f} to disable logging.
+This file will log the @code{stderr} outputs of php worker processes.  Can
+be set to @code{#f} to disable logging.
 @item @code{file} (default @code{#f})
-An optional override of the whole configuration.
-You can use the @code{mixed-text-file} function or an absolute filepath for it.
+An optional override of the whole configuration.  You can use the
address@hidden function or an absolute filepath for it.
 @end table
 @end deftp
 
 @deftp {Data type} php-fpm-dynamic-process-manager-configuration
 Data Type for the @code{dynamic} php-fpm process manager.  With the
address@hidden process manager, spare worker processes are kept around
-based on it's configured limits.
address@hidden process manager, spare worker processes are kept around based
+on it's configured limits.
 @table @asis
 @item @code{max-children} (default: @code{5})
 Maximum of worker processes.
@@ -17249,8 +17102,8 @@ How many spare worker processes should be kept around 
at maximum.
 
 @deftp {Data type} php-fpm-static-process-manager-configuration
 Data Type for the @code{static} php-fpm process manager.  With the
address@hidden process manager, an unchanging number of worker processes
-are created.
address@hidden process manager, an unchanging number of worker processes are
+created.
 @table @asis
 @item @code{max-children} (default: @code{5})
 Maximum of worker processes.
@@ -17271,11 +17124,9 @@ The time in seconds after which a process with no 
requests is killed.
 
 
 @deffn {Scheme Procedure} nginx-php-fpm-location @
-       [#:nginx-package nginx] @
-       [socket (string-append "/var/run/php" @
-                              (version-major (package-version php)) @
-                              "-fpm.sock")]
-A helper function to quickly add php to an @code{nginx-server-configuration}.
+       [#:nginx-package nginx] @ [socket (string-append "/var/run/php" @
+(version-major (package-version php)) @ "-fpm.sock")] A helper function to
+quickly add php to an @code{nginx-server-configuration}.
 @end deffn
 
 A simple services setup for nginx with php can look like this:
@@ -17295,18 +17146,18 @@ A simple services setup for nginx with php can look 
like this:
 @end example
 
 @cindex cat-avatar-generator
-The cat avatar generator is a simple service to demonstrate the use of php-fpm
-in @code{Nginx}.  It is used to generate cat avatar from a seed, for instance
-the hash of a user's email address.
+The cat avatar generator is a simple service to demonstrate the use of
+php-fpm in @code{Nginx}.  It is used to generate cat avatar from a seed, for
+instance the hash of a user's email address.
 
 @deffn {Scheme Procedure} cat-avatar-generator-serice @
-       [#:cache-dir "/var/cache/cat-avatar-generator"] @
-       [#:package cat-avatar-generator] @
-       [#:configuration (nginx-server-configuration)]
-Returns an nginx-server-configuration that inherits @code{configuration}.  It
-extends the nginx configuration to add a server block that serves 
@code{package},
-a version of cat-avatar-generator.  During execution, cat-avatar-generator will
-be able to use @code{cache-dir} as its cache directory.
+       [#:cache-dir "/var/cache/cat-avatar-generator"] @ [#:package
+cat-avatar-generator] @ [#:configuration (nginx-server-configuration)]
+Returns an nginx-server-configuration that inherits @code{configuration}.
+It extends the nginx configuration to add a server block that serves
address@hidden, a version of cat-avatar-generator.  During execution,
+cat-avatar-generator will be able to use @code{cache-dir} as its cache
+directory.
 @end deffn
 
 A simple setup for cat-avatar-generator can look like this:
@@ -17322,10 +17173,9 @@ A simple setup for cat-avatar-generator can look like 
this:
 @subsubheading Hpcguix-web
 
 @cindex hpcguix-web
-The @uref{hpcguix-web, https://github.com/UMCUGenetics/hpcguix-web/}
-program is a customizable web interface to browse Guix packages,
-initially designed for users of high-performance computing (HPC)
-clusters.
+The @uref{hpcguix-web, https://github.com/UMCUGenetics/hpcguix-web/} program
+is a customizable web interface to browse Guix packages, initially designed
+for users of high-performance computing (HPC)  clusters.
 
 @defvr {Scheme Variable} hpcguix-web-service-type
 The service type for @code{hpcguix-web}.
@@ -17336,7 +17186,7 @@ Data type for the hpcguix-web service configuration.
 
 @table @asis
 @item @code{specs}
-A gexp (@pxref{G-Expressions}) specifying the hpcguix-web service
+A gexp (@pxref{G-Ausdrücke}) specifying the hpcguix-web service
 configuration.  The main items available in this spec are:
 
 @table @asis
@@ -17359,8 +17209,8 @@ Additional entry in page @code{menu}.
 List of channels from which the package list is built (@pxref{Channels}).
 
 @item @code{package-list-expiration} (default: @code{(* 12 3600)})
-The expiration time, in seconds, after which the package list is rebuilt from
-the latest instances of the given channels.
+The expiration time, in seconds, after which the package list is rebuilt
+from the latest instances of the given channels.
 @end table
 
 See the hpcguix-web repository for a
@@ -17384,63 +17234,59 @@ A typical hpcguix-web service declaration looks like 
this:
                 (menu '(("/about" "ABOUT"))))))))
 @end example
 
address@hidden Note
-The hpcguix-web service periodically updates the package list it publishes by
-pulling channels from Git.  To that end, it needs to access X.509 certificates
-so that it can authenticate Git servers when communicating over HTTPS, and it
-assumes that @file{/etc/ssl/certs} contains those certificates.
address@hidden Anmerkung
+The hpcguix-web service periodically updates the package list it publishes
+by pulling channels from Git.  To that end, it needs to access X.509
+certificates so that it can authenticate Git servers when communicating over
+HTTPS, and it assumes that @file{/etc/ssl/certs} contains those
+certificates.
 
-Thus, make sure to add @code{nss-certs} or another certificate package to the
address@hidden field of your configuration.  @ref{X.509 Certificates}, for
-more information on X.509 certificates.
+Thus, make sure to add @code{nss-certs} or another certificate package to
+the @code{packages} field of your configuration.  @ref{X.509-Zertifikate},
+for more information on X.509 certificates.
 @end quotation
 
address@hidden Certificate Services
address@hidden Certificate Services
address@hidden Zertifikatsdienste
address@hidden Zertifikatsdienste
 
 @cindex Web
 @cindex HTTP, HTTPS
 @cindex Let's Encrypt
 @cindex TLS certificates
-The @code{(gnu services certbot)} module provides a service to
-automatically obtain a valid TLS certificate from the Let's Encrypt
-certificate authority.  These certificates can then be used to serve
-content securely over HTTPS or other TLS-based protocols, with the
-knowledge that the client will be able to verify the server's
-authenticity.
-
address@hidden://letsencrypt.org/, Let's Encrypt} provides the
address@hidden tool to automate the certification process.  This tool
-first securely generates a key on the server.  It then makes a request
-to the Let's Encrypt certificate authority (CA) to sign the key.  The CA
-checks that the request originates from the host in question by using a
-challenge-response protocol, requiring the server to provide its
-response over HTTP.  If that protocol completes successfully, the CA
-signs the key, resulting in a certificate.  That certificate is valid
-for a limited period of time, and therefore to continue to provide TLS
-services, the server needs to periodically ask the CA to renew its
-signature.
-
-The certbot service automates this process: the initial key
-generation, the initial certification request to the Let's Encrypt
-service, the web server challenge/response integration, writing the
-certificate to disk, the automated periodic renewals, and the deployment
-tasks associated with the renewal (e.g. reloading services, copying keys
-with different permissions).
-
-Certbot is run twice a day, at a random minute within the hour.  It
-won't do anything until your certificates are due for renewal or
-revoked, but running it regularly would give your service a chance of
-staying online in case a Let's Encrypt-initiated revocation happened for
-some reason.
-
-By using this service, you agree to the ACME Subscriber Agreement, which
-can be found there:
address@hidden://acme-v01.api.letsencrypt.org/directory}.
+The @code{(gnu services certbot)} module provides a service to automatically
+obtain a valid TLS certificate from the Let's Encrypt certificate
+authority.  These certificates can then be used to serve content securely
+over HTTPS or other TLS-based protocols, with the knowledge that the client
+will be able to verify the server's authenticity.
+
address@hidden://letsencrypt.org/, Let's Encrypt} provides the @code{certbot}
+tool to automate the certification process.  This tool first securely
+generates a key on the server.  It then makes a request to the Let's Encrypt
+certificate authority (CA) to sign the key.  The CA checks that the request
+originates from the host in question by using a challenge-response protocol,
+requiring the server to provide its response over HTTP.  If that protocol
+completes successfully, the CA signs the key, resulting in a certificate.
+That certificate is valid for a limited period of time, and therefore to
+continue to provide TLS services, the server needs to periodically ask the
+CA to renew its signature.
+
+The certbot service automates this process: the initial key generation, the
+initial certification request to the Let's Encrypt service, the web server
+challenge/response integration, writing the certificate to disk, the
+automated periodic renewals, and the deployment tasks associated with the
+renewal (e.g. reloading services, copying keys with different permissions).
+
+Certbot is run twice a day, at a random minute within the hour.  It won't do
+anything until your certificates are due for renewal or revoked, but running
+it regularly would give your service a chance of staying online in case a
+Let's Encrypt-initiated revocation happened for some reason.
+
+By using this service, you agree to the ACME Subscriber Agreement, which can
+be found there: @url{https://acme-v01.api.letsencrypt.org/directory}.
 
 @defvr {Scheme Variable} certbot-service-type
-A service type for the @code{certbot} Let's Encrypt client.  Its value
-must be a @code{certbot-configuration} record as in this example:
+A service type for the @code{certbot} Let's Encrypt client.  Its value must
+be a @code{certbot-configuration} record as in this example:
 
 @example
 (define %nginx-deploy-hook
@@ -17478,8 +17324,8 @@ files.
 
 @item @code{certificates} (default: @code{()})
 A list of @code{certificates-configuration}s for which to generate
-certificates and request signatures.  Each certificate has a @code{name}
-and several @code{domains}.
+certificates and request signatures.  Each certificate has a @code{name} and
+several @code{domains}.
 
 @item @code{email}
 Mandatory email used for registration, recovery contact, and important
@@ -17490,17 +17336,14 @@ Size of the RSA key.
 
 @item @code{default-location} (default: @i{see below})
 The default @code{nginx-location-configuration}.  Because @code{certbot}
-needs to be able to serve challenges and responses, it needs to be able
-to run a web server.  It does so by extending the @code{nginx} web
-service with an @code{nginx-server-configuration} listening on the
address@hidden on port 80, and which has a
address@hidden for the @code{/.well-known/} URI
-path subspace used by Let's Encrypt.  @xref{Web Services}, for more on
-these nginx configuration data types.
-
-Requests to other URL paths will be matched by the
address@hidden, which if present is added to all
address@hidden
+needs to be able to serve challenges and responses, it needs to be able to
+run a web server.  It does so by extending the @code{nginx} web service with
+an @code{nginx-server-configuration} listening on the @var{domains} on port
+80, and which has a @code{nginx-location-configuration} for the
address@hidden/.well-known/} URI path subspace used by Let's Encrypt.  
@xref{Web-Dienste}, for more on these nginx configuration data types.
+
+Requests to other URL paths will be matched by the @code{default-location},
+which if present is added to all @code{nginx-server-configuration}s.
 
 By default, the @code{default-location} will issue a redirect from
 @code{http://@var{domain}/...} to @code{https://@var{domain}/...}, leaving
@@ -17511,52 +17354,52 @@ Pass @code{#f} to not issue a default location.
 @end deftp
 
 @deftp {Data Type} certificate-configuration
-Data type representing the configuration of a certificate.
-This type has the following parameters:
+Data type representing the configuration of a certificate.  This type has
+the following parameters:
 
 @table @asis
 @item @code{name} (default: @i{see below})
-This name is used by Certbot for housekeeping and in file paths; it
-doesn't affect the content of the certificate itself.  To see
-certificate names, run @code{certbot certificates}.
+This name is used by Certbot for housekeeping and in file paths; it doesn't
+affect the content of the certificate itself.  To see certificate names, run
address@hidden certificates}.
 
 Its default is the first provided domain.
 
 @item @code{domains} (default: @code{()})
-The first domain provided will be the subject CN of the certificate, and
-all domains will be Subject Alternative Names on the certificate.
+The first domain provided will be the subject CN of the certificate, and all
+domains will be Subject Alternative Names on the certificate.
 
 @item @code{deploy-hook} (default: @code{#f})
-Command to be run in a shell once for each successfully issued
-certificate.  For this command, the shell variable
address@hidden will point to the config live subdirectory (for
-example, @samp{"/etc/letsencrypt/live/example.com"}) containing the new
-certificates and keys; the shell variable @code{$RENEWED_DOMAINS} will
-contain a space-delimited list of renewed certificate domains (for
-example, @samp{"example.com www.example.com"}.
+Command to be run in a shell once for each successfully issued certificate.
+For this command, the shell variable @code{$RENEWED_LINEAGE} will point to
+the config live subdirectory (for example,
address@hidden"/etc/letsencrypt/live/example.com"}) containing the new 
certificates
+and keys; the shell variable @code{$RENEWED_DOMAINS} will contain a
+space-delimited list of renewed certificate domains (for example,
address@hidden"example.com www.example.com"}.
 
 @end table
 @end deftp
 
 For each @code{certificate-configuration}, the certificate is saved to
address@hidden/etc/letsencrypt/live/@var{name}/fullchain.pem} and the key is
-saved to @code{/etc/letsencrypt/live/@var{name}/privkey.pem}.
address@hidden DNS Services
address@hidden DNS Services