diff options
Diffstat (limited to 'doc/handbook/chapters/installation.texi')
-rw-r--r-- | doc/handbook/chapters/installation.texi | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/handbook/chapters/installation.texi b/doc/handbook/chapters/installation.texi index 40a23e738..ad939b5b7 100644 --- a/doc/handbook/chapters/installation.texi +++ b/doc/handbook/chapters/installation.texi | |||
@@ -171,7 +171,7 @@ group. In addition the group @code{gnunetdns} may be needed (see below). | |||
171 | 171 | ||
172 | Create user @code{gnunet} who is member of the group @code{gnunet} | 172 | Create user @code{gnunet} who is member of the group @code{gnunet} |
173 | (automatically created) and specify a home directory where the GNUnet | 173 | (automatically created) and specify a home directory where the GNUnet |
174 | services will store persistant data such as information about peers. | 174 | services will store persistent data such as information about peers. |
175 | @example | 175 | @example |
176 | $ sudo useradd --system --home-dir /var/lib/gnunet --create-home gnunet | 176 | $ sudo useradd --system --home-dir /var/lib/gnunet --create-home gnunet |
177 | @end example | 177 | @end example |
@@ -431,7 +431,7 @@ For the @emph{multi-user setup} first the system services need to be started | |||
431 | as the system user, i.e. the user @code{gnunet} needs to execute | 431 | as the system user, i.e. the user @code{gnunet} needs to execute |
432 | @code{gnunet-arm -s}. This should be done by the system's init system. | 432 | @code{gnunet-arm -s}. This should be done by the system's init system. |
433 | Then the user who wants to start GNUnet applications has to run | 433 | Then the user who wants to start GNUnet applications has to run |
434 | @code{gnunet-arm -s} too. It is recommented to automate this, e.g. using | 434 | @code{gnunet-arm -s} too. It is recommended to automate this, e.g. using |
435 | the user's crontab. | 435 | the user's crontab. |
436 | 436 | ||
437 | @node gnunet-gtk | 437 | @node gnunet-gtk |
@@ -1369,7 +1369,7 @@ proxy forwards the HTTP request he receives with a certain URL to another | |||
1369 | webserver, here a GNUnet peer. | 1369 | webserver, here a GNUnet peer. |
1370 | 1370 | ||
1371 | So if you have a running Apache or nginx webserver you can configure it to | 1371 | So if you have a running Apache or nginx webserver you can configure it to |
1372 | be a GNUnet reverse proxy. Especially if you have a well-known webiste | 1372 | be a GNUnet reverse proxy. Especially if you have a well-known website |
1373 | this improves censorship resistance since it looks as normal surfing | 1373 | this improves censorship resistance since it looks as normal surfing |
1374 | behaviour. | 1374 | behaviour. |
1375 | 1375 | ||
@@ -2175,7 +2175,7 @@ Sane defaults should exist in your | |||
2175 | you could simply start without any configuration. If you want to | 2175 | you could simply start without any configuration. If you want to |
2176 | configure your peer later, you need to stop it before invoking the | 2176 | configure your peer later, you need to stop it before invoking the |
2177 | @code{gnunet-setup} tool to customize further and to test your | 2177 | @code{gnunet-setup} tool to customize further and to test your |
2178 | configuration (@code{gnunet-setup} has build-in test functions). | 2178 | configuration (@code{gnunet-setup} has built-in test functions). |
2179 | 2179 | ||
2180 | The most important option you might have to still set by hand is in | 2180 | The most important option you might have to still set by hand is in |
2181 | [PATHS]. Here, you use the option "GNUNET_HOME" to specify the path where | 2181 | [PATHS]. Here, you use the option "GNUNET_HOME" to specify the path where |