[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [gnunet-texinfo] branch master updated: installation. more
|
From: |
gnunet |
|
Subject: |
[GNUnet-SVN] [gnunet-texinfo] branch master updated: installation. more chapters |
|
Date: |
Mon, 27 Mar 2017 17:17:11 +0200 |
This is an automated email from the git hooks/post-receive script.
ng0 pushed a commit to branch master
in repository gnunet-texinfo.
The following commit(s) were added to refs/heads/master by this push:
new 075fdff installation. more chapters
075fdff is described below
commit 075fdff7c362e5b1733f279108b5524c98bc2c94
Author: ng0 <address@hidden>
AuthorDate: Fri Feb 17 16:58:20 2017 +0000
installation. more chapters
---
installation.texi | 806 +++++++++++++++++++++++++-----------------------------
1 file changed, 365 insertions(+), 441 deletions(-)
diff --git a/installation.texi b/installation.texi
index 70e1f4d..2b069b9 100644
--- a/installation.texi
+++ b/installation.texi
@@ -1591,7 +1591,8 @@ make install@
Done!
address@hidden Basic Installation for Fedora/PlanetLab nodes running Fedora 8 .
address@hidden Basic Installation for Fedora/PlanetLab nodes running Fedora 8 .
address@hidden Basic Installation for Fedora/PlanetLab nodes running Fedora 8 .
@c %**end of header
@node Top
@@ -1602,14 +1603,17 @@ Done!
GNUnet installation on Fedora 8/Planetlab nodes can be done as following:
1. Install the build tools to build GNUnet@
address@hidden@
- sudo yum -y -t --nogpgcheck install gcc make automake autoconf gettext-devel
texinfo zlib-devel subversion@
-}
address@hidden
+sudo yum -y -t --nogpgcheck install gcc make automake autoconf gettext-devel \
+texinfo zlib-devel subversion@
address@hidden example
2. Install the GNUnet dependencies@
address@hidden@
- sudo yum -y -t --nogpgcheck install gnutls-devel gnutls-devel libgcrypt-devel
sqlite-devel postgresql-devel mysql-devel libgsf-devel libvorbis-devel
libidn-devel@
-}
address@hidden
+sudo yum -y -t --nogpgcheck install gnutls-devel gnutls-devel libgcrypt-devel \
+sqlite-devel postgresql-devel mysql-devel libgsf-devel libvorbis-devel \
+libidn-devel
address@hidden example
3. Install outdated dependencies from source@
libtool@
@@ -1725,36 +1729,27 @@ libmicrohttpd@
}
7. Install GNUnet from svn@
address@hidden@
address@hidden
export LD_LIBRARY_PATH=/usr/local/lib@
svn co https://gnunet.org/svn/gnunet@
cd gnunet@
libtoolize@
./bootstrap@
- ./configure --prefix=$GNUNET_PREFIX --with-extractor=/usr/local
--with-curl=/usr/local --with-mysql=/usr/lib/mysql --enable-logging=verbose@
+ ./configure --prefix=$GNUNET_PREFIX --with-extractor=/usr/local \
+ --with-curl=/usr/local --with-mysql=/usr/lib/mysql --enable-logging=verbose@
make install@
-}
address@hidden example
Done!
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
address@hidden Build instructions for Gentoo
address@hidden %**end of header
-
address@hidden Top
-
address@hidden Build instructions for Gentoo
address@hidden Build instructions for Gentoo
This page describes how to install GNUnet 0.9 on Gentoo.
-Since the GNUnet 0.9 ebuilds are not in the official portage tree yet, we need
to add them to the local portage overlay. All the commands below should be
executed as root.
+Since the GNUnet 0.9 ebuilds are not in the official portage tree yet, we need
+to add them to the local portage overlay. All the commands below should be
+executed as root.
Specify your local portage directory in the /etc/make.conf, for example:@
@code{$ echo 'PORTDIR_OVERLAY="/usr/local/portage"' >> /etc/make.conf}
@@ -1762,7 +1757,8 @@ Specify your local portage directory in the
/etc/make.conf, for example:@
Create directories for the ebuilds:@
@code{$ mkdir -p /usr/local/portage/media-libs/libextractor
/usr/local/portage/net-p2p/gnunet/files}
-Download the latest ebuilds, init and config files from here and put them into
respective directories:@
+Download the latest ebuilds, init and config files from here and put them into
+respective directories:@
@code{$ cp libextractor-0.6.2.ebuild
/usr/local/portage/media-libs/libextractor@
$ cp gnunet-0.9.2.ebuild /usr/local/portage/net-p2p/gnunet@
$ cp gnunet-0.9.2.conf gnunet-0.9.2.confd gnunet-0.9.2.initd
/usr/local/portage/net-p2p/gnunet/files}
@@ -1773,7 +1769,8 @@ Generate Manifest files for the ebuilds:@
$ cd /usr/local/portage/media-libs/libextractor@
$ ebuild libextractor-0.6.2.ebuild digest}
-Unmask GNUnet and dependencies in the /etc/portage/package.keywords. For
example, if you use x86-64 architecture, add the following lines:@
+Unmask GNUnet and dependencies in the /etc/portage/package.keywords. For
+example, if you use x86-64 architecture, add the following lines:@
@code{net-p2p/gnunet ~amd64@
media-libs/libextractor ~amd64@
net-libs/libmicrohttpd ~amd64@
@@ -1786,72 +1783,42 @@ Now everything is ready to install GNUnet:@
@code{$ emerge -av gnunet}
Use /etc/init.d/gnunet to start/stop GNUnet.
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
address@hidden Building GLPK for MinGW
address@hidden %**end of header
-
address@hidden Top
-
-
address@hidden @bullet
-
address@hidden
-Matthias Wachs's blog
-
address@hidden
-
address@hidden itemize
address@hidden Building GLPK for MinGW
address@hidden Building GLPK for MinGW
+GNUnet now requires the GNU Linear Programming Kit (GLPK). Since there's is no
+package you can install with @code{mingw-get} you have to compile it from
+source:
-GNUnet now requires the GNU Linear Programming Kit (GLPK). Since there's is no
package you can install with @code{mingw-get} you have to compile it from
source:
@itemize @bullet
-
@item
Download the latest version from http://ftp.gnu.org/gnu/glpk/
@item
Unzip it using your favourite unzipper@
- In the MSYS shell:
+In the MSYS shell:
@item
- change to the respective directory
+change to the respective directory
@item
@code{./configure '--build=i686-pc-mingw32'}
@item
- run @code{make install check }
+run @code{make install check }
-MinGW does not automatically detect the correct buildtype so you have to
specify it manually
+MinGW does not automatically detect the correct buildtype so you have to
+specify it manually
@end itemize
address@hidden Compiling libgnurl for GNUnet: cannot find data type for
curl_off_t.
address@hidden %**end of header
address@hidden Top
address@hidden Compiling libgnurl for GNUnet: cannot find data type for
curl_off_t.
address@hidden Compiling libgnurl for GNUnet: cannot find data type for
curl_off_t.
-Language English
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
address@hidden itemize
-
-
-If you have to compile libgnurl from source since the version included in your
distribution is to old you perhaps get an error message while running the
@code{configure} script:
+If you have to compile libgnurl from source since the version included in your
+distribution is to old you perhaps get an error message while running the
address@hidden script:
@code{@
$ configure@
@@ -1862,7 +1829,9 @@ If you have to compile libgnurl from source since the
version included in your d
configure: error: cannot find data type for curl_off_t.@
}
-If you have to compile libgnurl from source since the version included in your
distribution is to old, you perhaps get an error message while running the
@code{configure} script:
+If you have to compile libgnurl from source since the version included in your
+distribution is to old, you perhaps get an error message while running the
address@hidden script:
@code{@
$ configure@
@@ -1877,12 +1846,10 @@ Solution:
Before running the configure script, set:
address@hidden"-I. -I$BUILD_ROOT/include" address@hidden GUI build instructions
for Ubuntu 12.04 using Subversion
address@hidden %**end of header
-
address@hidden Top
-
address@hidden"-I. -I$BUILD_ROOT/include" }
address@hidden GUI build instructions for Ubuntu 12.04 using Subversion
address@hidden GUI build instructions for Ubuntu 12.04 using Subversion
After installing GNUnet you can continue installing the GNUnet GUI tools:
@@ -1892,7 +1859,9 @@ First, install the required dependencies:
$ sudo apt-get install libgladeui-dev libqrencode-dev@
}
-Please ensure that the GNUnet shared libraries can be found by the linker. If
you installed GNUnet libraries in a non standard path (say
GNUNET_PREFIX=/usr/local/lib/), you can
+Please ensure that the GNUnet shared libraries can be found by the linker. If
+you installed GNUnet libraries in a non standard path (say
+GNUNET_PREFIX=/usr/local/lib/), you can
@itemize @bullet
@@ -1913,44 +1882,44 @@ Now you can checkout and compile the GNUnet GUI tools@
$ ./configure --prefix=$GNUNET_PREFIX/.. --with-gnunet=$GNUNET_PREFIX/..@
$ make install@
}
address@hidden @bullet
-
-
address@hidden
-
address@hidden itemize
address@hidden Installation with gnunet-update
address@hidden %**end of header
-
address@hidden Top
address@hidden Installation with gnunet-update
address@hidden Installation with gnunet-update
+gnunet-update project is an effort to introduce updates to GNUnet
+installations. An interesting to-be-implemented-feature of gnunet-update is
+that these updates are propagated through GNUnet's peer-to-peer network. More
+information about gnunet-update can be found at
+https://gnunet.org/svn/gnunet-update/README.
-gnunet-update project is an effort to introduce updates to GNUnet
installations. An interesting to-be-implemented-feature of gnunet-update is
that these updates are propagated through GNUnet's peer-to-peer network. More
information about gnunet-update can be found at
https://gnunet.org/svn/gnunet-update/README.
+While the project is still under development, we have implemented the following
+features which we believe may be helpful for users and we would like them to be
+tested:
-While the project is still under development, we have implemented the
following features which we believe may be helpful for users and we would like
them to be tested:
@itemize @bullet
-
@item
-Packaging GNUnet installation along with its run-time dependencies into update
packages
+Packaging GNUnet installation along with its run-time dependencies into update
+packages
@item
Installing update packages into compatible hosts
@item
-Updating an existing installation (which had been installed by gnunet-update)
to a newer one
+Updating an existing installation (which had been installed by gnunet-update)
+to a newer one
@end itemize
+The above said features of gnunet-update are currently available for testing on
+GNU/Linux systems.
-The above said features of gnunet-update are currently available for testing
on GNU/Linux systems.
-
-The following is a guide to help you get started with gnunet-update. It shows
you how to install the testing binary packages of GNUnet 0.9.1 we have at
https://gnunet.org/install/
+The following is a guide to help you get started with gnunet-update. It shows
+you how to install the testing binary packages of GNUnet 0.9.1 we have at
+https://gnunet.org/install/
gnunet-update needs the following:
address@hidden @bullet
-
address@hidden @bullet
@item
python ( 2.6 or above)
@@ -1967,12 +1936,17 @@ Checkout gnunet-update:@
$ svn checkout -r24905 https://gnunet.org/svn/gnunet-update@
}
-For security reasons, all packages released for gnunet-update from us are
signed with the key at https://gnunet.org/install/key.txt You would need to
import this key into your gpg key ring. gnunet-update uses this key to verify
the integrity of the packages it installs@
+For security reasons, all packages released for gnunet-update from us are
+signed with the key at https://gnunet.org/install/key.txt You would need to
+import this key into your gpg key ring. gnunet-update uses this key to verify
+the integrity of the packages it installs@
@code{@
$ gpg --recv-keys 7C613D78@
}
-Download the packages relevant to your architecture (currently I have access
to GNU/Linux machines on x86_64 and i686, so only two for now, hopefully more
later) from https://gnunet.org/install/.
+Download the packages relevant to your architecture (currently I have access to
+GNU/Linux machines on x86_64 and i686, so only two for now, hopefully more
+later) from https://gnunet.org/install/.
To install the downloaded package into the directory /foo:
@@ -1980,38 +1954,35 @@ To install the downloaded package into the directory
/foo:
gnunet-update/bin/gnunet-update install downloaded/package /foo@
}
-The installer reports the directories into which shared libraries and
dependencies have been installed. You may need to add the reported shared
library installation paths to LD_LIBRARY_PATH before you start running any
installed binaries.
-
-Please report bugs at https://gnunet.org/bugs/ under the project
'gnunet-update'.
address@hidden @bullet
-
-
address@hidden
+The installer reports the directories into which shared libraries and
+dependencies have been installed. You may need to add the reported shared
+library installation paths to LD_LIBRARY_PATH before you start running any
+installed binaries.
+Please report bugs at https://gnunet.org/bugs/ under the project
+'gnunet-update'.
address@hidden
-Español
address@hidden itemize
address@hidden Instructions for Microsoft Windows Platforms (Old)
address@hidden %**end of header
address@hidden Instructions for Microsoft Windows Platforms (Old)
address@hidden Instructions for Microsoft Windows Platforms (Old)
address@hidden Top
+This document is a DEPRECATED installation guide for gnunet on windows. It will
+not work for recent gnunet versions, but maybe it will be of some use if
+problems arise.
+ The Windows build uses a UNIX emulator for Windows,
+ @uref{http://www.mingw.org/, MinGW}, to build the executable modules. These
+ modules run natively on Windows and do not require additional emulation
+ software besides the usual dependencies.
+ GNUnet development is mostly done under Linux and especially SVN checkouts may
+ not build out of the box. We regret any inconvenience, and if you have
+ problems, please report them.
- This document is a DEPRECATED installation guide for gnunet on windows. It
will not work for recent gnunet versions, but maybe it will be of some use if
problems arise.
-
- The Windows build uses a UNIX emulator for Windows,
@uref{http://www.mingw.org/, MinGW}, to build the executable modules. These
modules run natively on Windows and do not require additional emulation
software besides the usual dependencies.
-
- GNUnet development is mostly done under Linux and especially SVN checkouts
may not build out of the box. We regret any inconvenience, and if you have
problems, please report them. @settitle Hardware and OS requirements
address@hidden %**end of header
-
address@hidden Top
-
address@hidden Hardware and OS requirements
address@hidden Hardware and OS requirements
@itemize @bullet
-
@item
Pentium II or equivalent processor, 350 MHz or better
@@ -2024,26 +1995,25 @@ Pentium II or equivalent processor, 350 MHz or better
@item
Windows 2000 or Windows XP are recommended
@end itemize
address@hidden Software installation
address@hidden %**end of header
-
address@hidden Top
address@hidden Software installation
address@hidden Software installation
@itemize @bullet
-
@item
@strong{Compression software}@
@
- The software packages GNUnet depends on are usually compressed using UNIX
tools like tar, gzip and bzip2.@
- If you do not already have an utility that is able to extract such archives,
get @uref{http://www.7-zip.org/, 7-Zip}.
+ The software packages GNUnet depends on are usually compressed using UNIX
+ tools like tar, gzip and bzip2.@ If you do not already have an utility that is
+ able to extract such archives, get @uref{http://www.7-zip.org/, 7-Zip}.
@item
@strong{UNIX environment}@
@
-EThe MinGW project provides the compiler toolchain that is used to build
GNUnet.@
- Get the following packages from
@uref{http://sourceforge.net/projects/mingw/files/, the MinGW project}:
+The MinGW project provides the compiler toolchain that is used to build
+GNUnet.@ Get the following packages from
address@hidden://sourceforge.net/projects/mingw/files/, the MinGW project}:
@itemize @bullet
@@ -2095,7 +2065,8 @@ Install MSYS (to c:\mingw, for example.)@
address@hidden use spaces in the pathname (c:\program files\mingw).
@item
-Install MinGW runtime, utilities and GCC to a subdirectory (to c:\mingw\mingw,
for example)
+Install MinGW runtime, utilities and GCC to a subdirectory (to c:\mingw\mingw,
+for example)
@item
Install the Development Kit to the MSYS directory (c:\mingw)
@@ -2103,21 +2074,26 @@ Install the Development Kit to the MSYS directory
(c:\mingw)
@item
Create a batch file bash.bat in your MSYS directory with the files:@
address@hidden address@hidden example
address@hidden
+bin\sh.exe --login
address@hidden example
This batch file opens a shell which is used to invoke the build processes..@
- MinGWâ²s standard shell (msys.bat) is not suitable because it opens a
separate console window@
- On Vista, bash.bat needs to be run as administrator.
+MinGW's standard shell (msys.bat) is not suitable because it opens a separate
+console window@ On Vista, bash.bat needs to be run as administrator.
@item
Start bash.sh and rename (c:\mingw\mingw\)lib\libstdc++.la to avoid problems:@
address@hidden /usr/mingw/lib/libstdc++.la /usr/mingw/lib/address@hidden example
address@hidden
+mv /usr/mingw/lib/libstdc++.la /usr/mingw/lib/libstdc++.la.broken
address@hidden example
@item
-Unpack the Windows API to the MinGW directory (c:\mingw\mingw\) and remove the
declaration of DATADIR from (c:\mingw\mingw\)include\objidl.h (lines 55-58)
+Unpack the Windows API to the MinGW directory (c:\mingw\mingw\) and remove the
+declaration of DATADIR from (c:\mingw\mingw\)include\objidl.h (lines 55-58)
@item
Unpack autoconf, automake to the MSYS directory (c:\mingw)
@@ -2130,14 +2106,15 @@ Install all other packages to the MinGW directory
(c:\mingw\mingw\)
@item
@strong{GNU Libtool}@
@
- GNU Libtool is required to use shared libraries.@
+GNU Libtool is required to use shared libraries.@
@
- Get the prebuilt package from here and unpack it to the MinGW directory
(c:\mingw)
+Get the prebuilt package from here and unpack it to the MinGW directory
+(c:\mingw)
@item
@strong{Pthreads}@
@
- GNUnet uses the portable POSIX thread library for multi-threading..@
+GNUnet uses the portable POSIX thread library for multi-threading..@
@itemize @bullet
@@ -2157,9 +2134,9 @@ Download all header files from
@uref{ftp://sources.redhat.com/pub/pthreads-win32
@strong{GNU MP@
}@
@
- GNUnet uses the GNU Multiple Precision library for special cryptographic
operations.@
+GNUnet uses the GNU Multiple Precision library for special cryptographic
operations.@
@
- Get the GMP binary package from the
@uref{http://sourceforge.net/projects/mingwrep/, MinGW repository} and unpack
it to the MinGW directory (c:\mingw\mingw)
+Get the GMP binary package from the
@uref{http://sourceforge.net/projects/mingwrep/, MinGW repository} and unpack
it to the MinGW directory (c:\mingw\mingw)
@item
@strong{GNU Gettext}@
@@ -2201,7 +2178,9 @@ Download all header files from
@uref{ftp://sources.redhat.com/pub/pthreads-win32
@item
Get the patches from @uref{http://bugs.mysql.com/bug.php?id=8906&files=1, Bug
#8906} and @uref{http://bugs.mysql.com/bug.php?id=8872&files=1, Bug #8872} (the
latter is only required for MySQL
address@hidden -p 0 @end example
address@hidden
+patch -p 0
address@hidden example
@item
@@ -2210,7 +2189,8 @@ Download all header files from
@uref{ftp://sources.redhat.com/pub/pthreads-win32
@item
Change to lib\ and create an import library:@
address@hidden --input-def ../include/libmySQL.def --dllname libmysql.dll
address@hidden
+dlltool --input-def ../include/libmySQL.def --dllname libmysql.dll
--output-lib libmysqlclient.a -k
@end example
@@ -2292,16 +2272,14 @@ Download all header files from
@uref{ftp://sources.redhat.com/pub/pthreads-win32
@
Download
@uref{http://www.gnunet.org/libextractor/download/win/exiv2-0.18.2.zip, Exiv2}
and unpack it to the MSYS directory (c:\mingw)
@end itemize
address@hidden Building libextractor and GNUnet
address@hidden %**end of header
-
address@hidden Top
-
address@hidden Building libextractor and GNUnet
address@hidden Building libextractor and GNUnet
- Before you compile libextractor or GNUnet, be sure to set@
- PKG_CONFIG_PATH:
address@hidden PKG_CONFIG_PATH=/mingw/lib/pkgconfig
+Before you compile libextractor or GNUnet, be sure to set@
+PKG_CONFIG_PATH:
address@hidden
+export PKG_CONFIG_PATH=/mingw/lib/pkgconfig
@end example
@@ -2309,81 +2287,56 @@ Download all header files from
@uref{ftp://sources.redhat.com/pub/pthreads-win32
By default, all modules that are created in this way contain debug
information and are quite large.@
To compile release versions (small and fast) set the variable CFLAGS:
address@hidden CFLAGS='-O2 -march=pentium -fomit-frame-pointer'
address@hidden
+export CFLAGS='-O2 -march=pentium -fomit-frame-pointer'
./configure --prefix=$HOME --with-extractor=$HOME
@end example
address@hidden Installer
address@hidden %**end of header
-
address@hidden Top
-
address@hidden Installer
address@hidden Installer
The GNUnet installer is made with @uref{http://nsis.sourceforge.net/, NSIS}@
- The installer script is located in contrib\win in the GNUnet source tree.
@settitle Source
address@hidden %**end of header
-
address@hidden Top
-
-
-
- The sources of all dependencies are available here.
address@hidden @bullet
+ The installer script is located in contrib\win in the GNUnet source tree.
address@hidden Source
address@hidden Source
address@hidden
+The sources of all dependencies are available here.
address@hidden Portable GNUnet
address@hidden Portable GNUnet
address@hidden
-Español
address@hidden itemize
address@hidden Portable GNUnet
address@hidden %**end of header
+Quick instructions on how to use the most recent GNUnet on most GNU/Linux
+distributions
address@hidden Top
-
-
-
-Quick instructions on how to use the most recent GNUnet on most GNU/Linux
distributions
-
-Currently this has only been tested on Ubuntu 12.04, 12.10, 13.04, Debian and
CentOS 6, but it should work on almost any GNU/Linux distribution. More
in-detail information can be found in the handbook.
address@hidden @bullet
+Currently this has only been tested on Ubuntu 12.04, 12.10, 13.04, Debian and
+CentOS 6, but it should work on almost any GNU/Linux distribution. More
+in-detail information can be found in the handbook.
address@hidden Prerequisites
address@hidden Prerequisites
address@hidden
address@hidden Prerequisites
address@hidden %**end of header
-
address@hidden Top
-
-
-
-Open a terminal and paste this line into it to install all required tools
needed:@
+Open a terminal and paste this line into it to install all required tools
+needed:@
@code{sudo apt-get install python-gpgme subversion}
address@hidden
address@hidden Download & set up gnunet-update
address@hidden %**end of header
address@hidden Download & set up gnunet-update
address@hidden Download & set up gnunet-update
address@hidden Top
-
-
-
-The following command will download a working version of gnunet-update with
the subversion tool and import the public key which is needed for
authentication:@
address@hidden@
- svn checkout -r24905 https://gnunet.org/svn/gnunet-update ~/gnunet-update &&
cd ~/gnunet-update@
- gpg --keyserver "hkp://keys.gnupg.net" --recv-keys 7C613D78@
-}
-
address@hidden
address@hidden Install GNUnet
address@hidden %**end of header
-
address@hidden Top
+The following command will download a working version of gnunet-update with the
+subversion tool and import the public key which is needed for authentication:@
address@hidden
+svn checkout -r24905 https://gnunet.org/svn/gnunet-update ~/gnunet-update &&
+cd ~/gnunet-update
+gpg --keyserver "hkp://keys.gnupg.net" --recv-keys 7C613D78
address@hidden example
address@hidden Install GNUnet
address@hidden Install GNUnet
-Download and install GNUnet binaries which can be found here and set library
paths:@
+Download and install GNUnet binaries which can be found here and set library
+paths:@
@code{@
wget -P /tmp https://gnunet.org/install/packs/gnunet-0.9.4-`uname -m`.tgz@
./bin/gnunet-update install /tmp/gnunet-0.9*.tgz ~@
@@ -2391,160 +2344,151 @@ Download and install GNUnet binaries which can be
found here and set library pat
echo -e "address@hidden@}/address@hidden@}/lib/gnunet-deps" | sudo tee
/etc/ld.so.conf.d/gnunet.conf > /dev/null@
sudo ldconfig@
}@
- You may need to re-login once after executing these last commands
address@hidden itemize
-
-
-That's it, GNUnet is installed in your home directory now. GNUnet can be
configured and afterwards started by executing@
address@hidden address@hidden Graphical interface
address@hidden %**end of header
-
address@hidden Top
-
-
-If you also would like to use gnunet-gtk and gnunet-setup (highly recommended
for beginners), do:
-
address@hidden -P /tmp
https://gnunet.org/install/packs/gnunet-0.9.4-gtk-0.9.4-`uname -m`.tgz@
- sh ~/gnunet-update/bin/gnunet-update install /tmp/gnunet-*gtk*.tgz ~@
- sudo ldconfig}@
- Now you can run @code{gnunet-setup} for easy configuration of your GNUnet
peer.
address@hidden @bullet
+You may need to re-login once after executing these last commands
+That's it, GNUnet is installed in your home directory now. GNUnet can be
+configured and afterwards started by executing@
address@hidden -s}
address@hidden
address@hidden Graphical interface
address@hidden Graphical interface
address@hidden itemize
address@hidden Configuring your peer
address@hidden %**end of header
-
address@hidden Top
+If you also would like to use gnunet-gtk and gnunet-setup (highly recommended
+for beginners), do:
address@hidden
+wget -P /tmp https://gnunet.org/install/packs/gnunet-0.9.4-gtk-0.9.4-`uname
-m`.tgz@
+sh ~/gnunet-update/bin/gnunet-update install /tmp/gnunet-*gtk*.tgz ~@
+sudo ldconfig
address@hidden example
+Now you can run @code{gnunet-setup} for easy configuration of your GNUnet peer.
address@hidden Configuring your peer
address@hidden Configuring your peer
This chapter will describe the various configuration options in GNUnet.
-The easiest way to configure your peer is to use the gnunet-setup tool.
gnunet-setup is part of the gnunet-gtk download. You might have to install it
separately.
+The easiest way to configure your peer is to use the gnunet-setup tool.
+gnunet-setup is part of the gnunet-gtk download. You might have to install it
+separately.
-Many of the specific sections from this chapter actually are linked from
within gnunet-setup to help you while using the setup tool.
+Many of the specific sections from this chapter actually are linked from within
+gnunet-setup to help you while using the setup tool.
-While you can also configure your peer by editing the configuration file by
hand, this is not recommended for anyone except for developers.
address@hidden @bullet
+While you can also configure your peer by editing the configuration file by
+hand, this is not recommended for anyone except for developers.
address@hidden Configuring the Friend-to-Friend (F2F) mode
address@hidden Configuring the Friend-to-Friend (F2F) mode
address@hidden
+GNUnet knows three basic modes of operation. In standard "peer-to-peer" mode,
+your peer will connect to any peer. In the pure "friend-to-friend" mode, your
+peer will ONLY connect to peers from a list of friends specified in the
+configuration. Finally, in mixed mode, GNUnet will only connect to arbitrary
+peers if it has at least a specified number of connections to friends.
-
address@hidden
-Español
-
address@hidden
-Français
address@hidden itemize
address@hidden Configuring the Friend-to-Friend (F2F) mode
address@hidden %**end of header
-
address@hidden Top
-
-
-
-GNUnet knows three basic modes of operation. In standard "peer-to-peer" mode,
your peer will connect to any peer. In the pure "friend-to-friend" mode, your
peer will ONLY connect to peers from a list of friends specified in the
configuration. Finally, in mixed mode, GNUnet will only connect to arbitrary
peers if it has at least a specified number of connections to friends.
-
-When configuring any of the F2F modes, you first need to create a file with
the peer identities of your friends. Ask your friends to run
+When configuring any of the F2F modes, you first need to create a file with the
+peer identities of your friends. Ask your friends to run
$ gnunet-peerinfo -sq
-The output of this command needs to be added to your friends file, which is
simply a plain text file with one line per friend with the output from the
above command.
-
-You then specify the location of your friends file in the "FRIENDS" option of
the "topology" section.
-
-Once you have created the friends file, you can tell GNUnet to only connect to
your friends by setting the "FRIENDS-ONLY" option (again in the "topology"
section) to YES.
-
-If you want to run in mixed-mode, set "FRIENDS-ONLY" to NO and configure a
minimum number of friends to have (before connecting to arbitrary peers) under
the "MINIMUM-FRIENDS" option.
-
-If you want to operate in normal P2P-only mode, simply set "MINIMUM-FRIENDS"
to zero and "FRIENDS_ONLY" to NO. This is the default.
address@hidden @bullet
-
+The output of this command needs to be added to your friends file, which is
+simply a plain text file with one line per friend with the output from the
+above command.
address@hidden
-
-
address@hidden
-Español
+You then specify the location of your friends file in the "FRIENDS" option of
+the "topology" section.
address@hidden
-Français
address@hidden itemize
address@hidden Configuring the hostlist to bootstrap
address@hidden %**end of header
+Once you have created the friends file, you can tell GNUnet to only connect to
+your friends by setting the "FRIENDS-ONLY" option (again in the "topology"
+section) to YES.
address@hidden Top
+If you want to run in mixed-mode, set "FRIENDS-ONLY" to NO and configure a
+minimum number of friends to have (before connecting to arbitrary peers) under
+the "MINIMUM-FRIENDS" option.
+If you want to operate in normal P2P-only mode, simply set "MINIMUM-FRIENDS" to
+zero and "FRIENDS_ONLY" to NO. This is the default.
address@hidden Configuring the hostlist to bootstrap
address@hidden Configuring the hostlist to bootstrap
-After installing the software you need to get connected to the GNUnet network.
The configuration file included in your download is already configured to
connect you to the GNUnet network. In this section the relevant configuration
settings are explained.
+After installing the software you need to get connected to the GNUnet network.
+The configuration file included in your download is already configured to
+connect you to the GNUnet network. In this section the relevant configuration
+settings are explained.
-To get an initial connection to the GNUnet network and to get to know peers
already connected to the network you can use the so called bootstrap servers.
These servers can give you a list of peers connected to the network. To use
these bootstrap servers you have to configure the hostlist daemon to activate
bootstrapping.
+To get an initial connection to the GNUnet network and to get to know peers
+already connected to the network you can use the so called bootstrap servers.
+These servers can give you a list of peers connected to the network. To use
+these bootstrap servers you have to configure the hostlist daemon to activate
+bootstrapping.
-To activate bootstrapping edit your configuration file and edit the
@code{[hostlist]}-section. You have to set the argument "-b" in the options
line:
address@hidden
+To activate bootstrapping edit your configuration file and edit the
address@hidden You have to set the argument "-b" in the options
+line:
address@hidden
+[hostlist]
OPTIONS = -b
@end example
-
-Additionally you have to specify which server you want to use. The default
bootstrapping server is "@uref{http://v10.gnunet.org/hostlist,
http://v10.gnunet.org/hostlist}";. [^] To set the server you have to edit the
line "SERVERS" in the hostlist section. To use the default server you should
set the lines to
address@hidden = http://v10.gnunet.org/hostlist [^]
+Additionally you have to specify which server you want to use. The default
+bootstrapping server is "@uref{http://v10.gnunet.org/hostlist,
+http://v10.gnunet.org/hostlist}";. [^] To set the server you have to edit the
+line "SERVERS" in the hostlist section. To use the default server you should
+set the lines to
address@hidden
+SERVERS = http://v10.gnunet.org/hostlist [^]
@end example
To use bootstrapping your configuration file should include these lines:
address@hidden
address@hidden
+[hostlist]
OPTIONS = -b
SERVERS = http://v10.gnunet.org/hostlist [^]
@end example
-Besides using bootstrap servers you can configure your GNUnet peer to recieve
hostlist advertisements. Peers offering hostlists to other peers can send
advertisement messages to peers that connect to them. If you configure your
peer to receive these messages, your peer can download these lists and connect
to the peers included. These lists are persistent, which means that they are
saved to your hard disk regularly and are loaded during startup.
+Besides using bootstrap servers you can configure your GNUnet peer to recieve
+hostlist advertisements. Peers offering hostlists to other peers can send
+advertisement messages to peers that connect to them. If you configure your
+peer to receive these messages, your peer can download these lists and connect
+to the peers included. These lists are persistent, which means that they are
+saved to your hard disk regularly and are loaded during startup.
-To activate hostlist learning you have to add the "-e" switch to the OPTIONS
line in the hostlist section:
address@hidden
+To activate hostlist learning you have to add the "-e" switch to the OPTIONS
+line in the hostlist section:
address@hidden
+[hostlist]
OPTIONS = -b -e
@end example
-Furthermore you can specify in which file the lists are saved. To save the
lists in the file "hostlists.file" just add the line:
address@hidden = hostlists.file
+Furthermore you can specify in which file the lists are saved. To save the
+lists in the file "hostlists.file" just add the line:
address@hidden
+HOSTLISTFILE = hostlists.file
@end example
-Best practice is to activate both bootstrapping and hostlist learning. So your
configuration file should include these lines:
address@hidden
+Best practice is to activate both bootstrapping and hostlist learning. So your
+configuration file should include these lines:
address@hidden
+[hostlist]
OPTIONS = -b -e
HTTPPORT = 8080
SERVERS = http://v10.gnunet.org/hostlist [^]
HOSTLISTFILE = $SERVICEHOME/hostlists.file
@end example
address@hidden @bullet
address@hidden Configuration of the HOSTLIST proxy settings
address@hidden Configuration of the HOSTLIST proxy settings
-
address@hidden
-
-
address@hidden
-Español
-
address@hidden
-Français
address@hidden itemize
address@hidden Configuration of the HOSTLIST proxy settings
address@hidden %**end of header
-
address@hidden Top
-
-
-
-The hostlist client can be configured to use a proxy to connect to the
hostlist server. This functionality can be configured in the configuration file
directly or using the gnunet-setup tool.
+The hostlist client can be configured to use a proxy to connect to the hostlist
+server. This functionality can be configured in the configuration file directly
+or using the gnunet-setup tool.
The hostlist client supports the following proxy types at the moment:
@itemize @bullet
@@ -2558,16 +2502,23 @@ SOCKS 4/4a/5/5 with hostname
@end itemize
-In addition authentication at the proxy with username and password can be
configured.
+In addition authentication at the proxy with username and password can be
+configured.
-To configure proxy support for the hostlist client in the gnunet-setup tool,
select the "hostlist" tab and select the appropriate proxy type. The hostname
or IP address (including port if required) has to be entered in the "Proxy
hostname" textbox. If required, enter username and password in the "Proxy
username" and "Proxy password" boxes. Be aware that these information will be
stored in the configuration in plain text.
+To configure proxy support for the hostlist client in the gnunet-setup tool,
+select the "hostlist" tab and select the appropriate proxy type. The hostname
+or IP address (including port if required) has to be entered in the "Proxy
+hostname" textbox. If required, enter username and password in the "Proxy
+username" and "Proxy password" boxes. Be aware that these information will be
+stored in the configuration in plain text.
-To configure these options directly in the configuration, you can configure
the following settings in the @code{[hostlist]} section of the configuration:@
address@hidden@
+To configure these options directly in the configuration, you can configure the
+following settings in the @code{[hostlist]} section of the configuration:@
address@hidden
# Type of proxy server,@
# Valid values: HTTP, HTTP_1_0, SOCKS4, SOCKS5, SOCKS4A, SOCKS5_HOSTNAME@
# Default: HTTP@
- # PROXY_TYPE = HTTP}
+ # PROXY_TYPE = HTTP
# Hostname or IP of proxy server@
# PROXY =@
@@ -2575,141 +2526,122 @@ To configure these options directly in the
configuration, you can configure the
# PROXY_USERNAME =@
# User password for proxy server@
# PROXY_PASSWORD =@
address@hidden example
address@hidden @bullet
-
-
address@hidden
-
address@hidden itemize
address@hidden Configuring your peer to provide a hostlist
address@hidden %**end of header
-
address@hidden Top
-
address@hidden Configuring your peer to provide a hostlist
address@hidden Configuring your peer to provide a hostlist
+If you operate a peer permanently connected to GNUnet you can configure your
+peer to act as a hostlist server, providing other peers the list of peers known
+to him.
-If you operate a peer permanently connected to GNUnet you can configure your
peer to act as a hostlist server, providing other peers the list of peers known
to him.
+Yor server can act as a bootstrap server and peers needing to obtain a list of
+peers can contact him to download this list. To download this hostlist the peer
+uses HTTP. For this reason you have to build your peer with libcurl and
+microhttpd support. How you build your peer with this options can be found
+here: https://gnunet.org/generic_installation
-Yor server can act as a bootstrap server and peers needing to obtain a list of
peers can contact him to download this list. To download this hostlist the peer
uses HTTP. For this reason you have to build your peer with libcurl and
microhttpd support. How you build your peer with this options can be found
here: https://gnunet.org/generic_installation
+To configure your peer to act as a bootstrap server you have to add the "-p"
+option to OPTIONS in the [hostlist] section of your configuration file. Besides
+that you have to specify a port number for the http server. In conclusion you
+have to add the following lines:
-To configure your peer to act as a bootstrap server you have to add the "-p"
option to OPTIONS in the [hostlist] section of your configuration file. Besides
that you have to specify a port number for the http server. In conclusion you
have to add the following lines:
address@hidden
address@hidden
+[hostlist]
HTTPPORT = 12980
OPTIONS = -p
@end example
-If your peer acts as a bootstrap server other peers should know about that.
You can advertise the hostlist your are providing to other peers. Peers
connecting to your peer will get a message containing an advertisement for your
hostlist and the URL where it can be downloaded. If this peer is in learning
mode, it will test the hostlist and, in the case it can obtain the list
successfully, it will save it for bootstrapping.
+If your peer acts as a bootstrap server other peers should know about that. You
+can advertise the hostlist your are providing to other peers. Peers connecting
+to your peer will get a message containing an advertisement for your hostlist
+and the URL where it can be downloaded. If this peer is in learning mode, it
+will test the hostlist and, in the case it can obtain the list successfully, it
+will save it for bootstrapping.
-To activate hostlist advertisement on your peer, you have to set the following
lines in your configuration file:
address@hidden
+To activate hostlist advertisement on your peer, you have to set the following
+lines in your configuration file:
address@hidden
+[hostlist]
EXTERNAL_DNS_NAME = example.org
HTTPPORT = 12981
OPTIONS = -p -a
@end example
-With this configuration your peer will a act as a bootstrap server and
advertise this hostlist to other peers connecting to him. The URL used to
download the list will be @address@hidden://example.org:12981/,
http://example.org:12981/}}.
+With this configuration your peer will a act as a bootstrap server and
+advertise this hostlist to other peers connecting to him. The URL used to
+download the list will be @address@hidden://example.org:12981/,
+http://example.org:12981/}}.
Please notice:
@itemize @bullet
@item
-The hostlist is not human readable, so you should not try to download it using
your webbrowser. Just point your GNUnet peer to the address!
+The hostlist is not human readable, so you should not try to download it using
+your webbrowser. Just point your GNUnet peer to the address!
@item
Advertising without providing a hostlist does not make sense and will not work.
@end itemize
address@hidden @bullet
-
address@hidden Configuring the datastore
address@hidden Configuring the datastore
address@hidden
+The datastore is what GNUnet uses to for long-term storage of file-sharing
+data. Note that long-term does not mean 'forever' since content does have an
+expiration date, and of course storage space is finite (and hence sometimes
+content may have to be discarded).
+Use the "QUOTA" option to specify how many bytes of storage space you are
+willing to dedicate to GNUnet.
address@hidden
-Español
-
address@hidden
-Français
address@hidden itemize
address@hidden Configuring the datastore
address@hidden %**end of header
-
address@hidden Top
-
-
-
-The datastore is what GNUnet uses to for long-term storage of file-sharing
data. Note that long-term does not mean 'forever' since content does have an
expiration date, and of course storage space is finite (and hence sometimes
content may have to be discarded).
-
-Use the "QUOTA" option to specify how many bytes of storage space you are
willing to dedicate to GNUnet.
-
-In addition to specifying the maximum space GNUnet is allowed to use for the
datastore, you need to specify which database GNUnet should use to do so.
Currently, you have the choice between sqLite, MySQL and Postgres.
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Español
-
address@hidden
-Français
address@hidden itemize
address@hidden Configuring the MySQL database
address@hidden %**end of header
-
address@hidden Top
-
+In addition to specifying the maximum space GNUnet is allowed to use for the
+datastore, you need to specify which database GNUnet should use to do so.
+Currently, you have the choice between sqLite, MySQL and Postgres.
address@hidden Configuring the MySQL database
address@hidden Configuring the MySQL database
This section describes how to setup the MySQL database for GNUnet.
-Note that the mysql plugin does NOT work with mysql before 4.1 since we need
prepared statements. We are generally testing the code against MySQL 5.1 at
this address@hidden Reasons for using MySQL
address@hidden %**end of header
-
address@hidden Top
-
+Note that the mysql plugin does NOT work with mysql before 4.1 since we need
+prepared statements. We are generally testing the code against MySQL 5.1 at
+this address@hidden Reasons for using MySQL
@itemize @bullet
-
@item
-On up-to-date hardware where mysql can be used comfortably, this@
- module will have better performance than the other database choices
(according to our tests).
+On up-to-date hardware where mysql can be used comfortably, this@ module will
+have better performance than the other database choices (according to our
+tests).
address@hidden
-Its often possible to recover the mysql database from internal
inconsistencies. Some of the other databases do not support repair.
address@hidden Its often possible to recover the mysql database from internal
+inconsistencies. Some of the other databases do not support repair.
@end itemize
address@hidden Reasons for not using MySQL
address@hidden %**end of header
-
address@hidden Top
address@hidden Reasons for not using MySQL
address@hidden Reasons for not using MySQL
@itemize @bullet
-
@item
Memory usage (likely not an issue if you have more than 1 GB)
@item
Complex manual setup
@end itemize
address@hidden Setup Instructions
address@hidden %**end of header
-
address@hidden Top
address@hidden Setup Instructions
address@hidden Setup Instructions
@itemize @bullet
-
@item
-In @code{gnunet.conf} set in section "DATASTORE" the value for "DATABASE" to
"mysql".
+In @code{gnunet.conf} set in section "DATASTORE" the value for "DATABASE" to
+"mysql".
@item
Access mysql as root:@
@@ -2731,25 +2663,26 @@ FLUSH PRIVILEGES;
@item
In the $HOME directory of $USER, create a ".my.cnf" file with the following
lines@
address@hidden [client]
- user=$USER
- password=$the_password_you_like
- @end example
address@hidden
+[client]
+user=$USER
+password=$the_password_you_like
address@hidden example
@end itemize
- Thats it. Note that @code{.my.cnf} file is a slight security risk unless its
on@
- a safe partition. The $HOME/.my.cnf can of course be a symbolic@
- link. Luckily $USER has only priviledges to mess up GNUnet's tables, which
should be pretty address@hidden Testing
address@hidden %**end of header
+ Thats it. Note that @code{.my.cnf} file is a slight security risk unless its
+ on@ a safe partition. The $HOME/.my.cnf can of course be a symbolic@ link.
+ Luckily $USER has only priviledges to mess up GNUnet's tables, which should be
+ pretty harmless.
address@hidden Testing
address@hidden Testing
address@hidden Top
-
-
-
-You should briefly try if the database connection works. First, login as
$USER. Then use:
address@hidden mysql -u $USER
+You should briefly try if the database connection works. First, login as $USER.
+Then use:
address@hidden
+$ mysql -u $USER
mysql> use gnunet;
@end example
@@ -2759,45 +2692,36 @@ If you get the message "Database changed" it probably
works.
If you get "ERROR 2002: Can't connect to local MySQL server@
through socket '/tmp/mysql.sock' (2)" it may be resolvable by@
"ln -s /var/run/mysqld/mysqld.sock /tmp/mysql.sock"@
- so there may be some additional trouble depending on your mysql
address@hidden Performance Tuning
address@hidden %**end of header
-
address@hidden Top
-
-
+ so there may be some additional trouble depending on your mysql setup.
address@hidden Performance Tuning
address@hidden Performance Tuning
For GNUnet, you probably want to set the option
address@hidden = 0
address@hidden
+innodb_flush_log_at_trx_commit = 0
@end example
+for a rather dramatic boost in MySQL performance. However, this reduces the
+"safety" of your database as with this options you may loose transactions
+during a power outage. While this is totally harmless for GNUnet, the option
+applies to all applications using MySQL. So you should set it if (and only if)
+GNUnet is the only application on your system using address@hidden Setup for
+running Testcases
-for a rather dramatic boost in MySQL performance. However, this reduces the
"safety" of your database as with this options you may loose transactions
during a power outage. While this is totally harmless for GNUnet, the option
applies to all applications using MySQL. So you should set it if (and only if)
GNUnet is the only application on your system using address@hidden Setup for
running Testcases
address@hidden %**end of header
-
address@hidden Top
-
-
-
-If you want to run the testcases, you must create a second database
"gnunetcheck" with the same username and password. This database will then be
used for testing ("make check").
address@hidden @bullet
-
-
address@hidden
-
-
address@hidden
-Français
address@hidden itemize
address@hidden Configuring the Postgres database
address@hidden %**end of header
-
address@hidden Top
-
+If you want to run the testcases, you must create a second database
+"gnunetcheck" with the same username and password. This database will then be
+used for testing ("make check").
address@hidden Configuring the Postgres database
address@hidden Configuring the Postgres database
This text describes how to setup the Postgres database for GNUnet.
-This Postgres plugin was developed for Postgres 8.3 but might work for earlier
versions as address@hidden Reasons to use Postgres
+This Postgres plugin was developed for Postgres 8.3 but might work for earlier
+versions as well.
+
address@hidden Reasons to use Postgres
address@hidden Reasons to use Postgres
@c %**end of header
@node Top
--
To stop receiving notification emails like this one, please contact
address@hidden
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [gnunet-texinfo] branch master updated: installation. more chapters,
gnunet <=