* Using git (NOTE: 1.1 GiB as of 2019-03-09):
git clone https://git.gnunet.org/bibliography.git
* Using Drupal:
- https://old.gnunet.org/bibliography
+ https://bib.gnunet.org/
The Drupal access will be replaced by a new interface to our
bibliography in the foreseeable future.
Since now activating DEBUG automatically makes it VERBOSE and activates
@strong{all} debug messages by default, you probably want to use the
-@uref{https://old.gnunet.org/logging, https://old.gnunet.org/logging}
+@uref{https://docs.gnunet.org/#Logging, https://docs.gnunet.org/#Logging}
functionality to filter only relevant messages.
A suitable configuration could be:
Detailed installation instructions for
various operating systems and a detailed list of all
dependencies can be found on our website at
-@uref{https://old.gnunet.org/installation} and in our
+@uref{https://docs.gnunet.org/#Installation} and in our
Reference Documentation (GNUnet Handbook).
Please read this tutorial carefully since every single step is
environmental variable. The @code{DEBUG} level is only available if
@command{--enable-logging=verbose} was used when running
@command{configure}. More details about logging can be found under
-@uref{https://old.gnunet.org/logging}.
+@uref{https://docs.gnunet.org/#Logging}.
You should also probably enable the creation of core files, by setting
@code{ulimit}, and echo'ing @code{1} into