[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [gnunet-texinfo] branch master updated (ea9421b -> 75c085d)
From: |
gnunet |
Subject: |
[GNUnet-SVN] [gnunet-texinfo] branch master updated (ea9421b -> 75c085d) |
Date: |
Thu, 18 May 2017 14:03:37 +0200 |
This is an automated email from the git hooks/post-receive script.
ng0 pushed a change to branch master
in repository gnunet-texinfo.
from ea9421b add bugtickets to README
new 9fe554e a few errors fixed
new 75c085d the menuing or the philosofy part works. Not so for the
installation part
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
developer.texi | 76 +++++++++++++++++++++++++++----------------------------
gnunet.texi | 5 ++++
installation.texi | 44 ++++++++++++++++++--------------
user.texi | 8 +++---
4 files changed, 72 insertions(+), 61 deletions(-)
diff --git a/developer.texi b/developer.texi
index 40c96ec..13a1eba 100644
--- a/developer.texi
+++ b/developer.texi
@@ -43,8 +43,8 @@ however, few people would want to read this site if 99% of it
was
advertisements for bogus websites.
@c ***************************************************************************
address@hidden Introduction
address@hidden Introduction
address@hidden DevelperIntroduction
address@hidden DeveloperIntroduction
This developer handbook is intended as first introduction to GNUnet for new
developers that want to extend the GNUnet framework. After the introduction,
@@ -2749,8 +2749,8 @@ that are going to run.@
@end table
@c ***************************************************************************
address@hidden Availability
address@hidden Availability
address@hidden Availability2
address@hidden Availability2
@c %**end of header
As mentioned before, one of the features provided by ARM is starting services
@@ -3049,7 +3049,7 @@ in 0.7.x and 0.8.x) in more detail and gives some
benchmarking results. The
performance results presented are quite old and maybe outdated at this point.
@itemize @bullet
@item Why use SMTP for a peer-to-peer transport?
address@hidden How does it work?
address@hidden SMTPHow does it work?
@item How do I configure my peer?
@item How do I test if it works?
@item How fast is it?
@@ -3232,7 +3232,7 @@ is still in the testing stage so don't expect it to work
perfectly. If you
have any questions or problems just post them here or ask on the IRC channel.
@itemize @bullet
@item What do I need to use the Bluetooth plugin transport?
address@hidden How does it work?
address@hidden BluetoothHow does it work?
@item What possible errors should I be aware of?
@item How do I configure my peer?
@item How can I test it?
@@ -3261,8 +3261,8 @@ installed and that your device is on and in a
discoverable mode. The Windows
Bluetooth Stack supports only the RFCOMM protocol so we cannot turn on your
device programatically!
address@hidden How does it work?
address@hidden How does it work?
address@hidden How does it work2?
address@hidden How does it work2?
@c %**end of header
The Bluetooth transport plugin uses virtually the same code as the WLAN plugin
@@ -3325,8 +3325,8 @@ device and to send some particular commands to it.
@item @code{hcidump} : could be used for low level debugging
@end itemize
address@hidden How do I configure my peer?
address@hidden How do I configure my peer?
address@hidden How do I configure my peer2?
address@hidden How do I configure my peer2?
@c %**end of header
On Linux, you just have to be sure that the interface name corresponds to the
@@ -3813,8 +3813,8 @@ re-established, the applications will be receive matching
connect events.
This section describes the protocol between an application using the CORE
service (the client) and the CORE service process itself.
address@hidden Setup
address@hidden Setup
address@hidden Setup2
address@hidden Setup2
@c %**end of header
When a client connects to the CORE service, it first sends a
@@ -4289,8 +4289,8 @@ standard deviation value, not only the average (in
particular, if the standard
veriation is very high, the average maybe meaningless: the network size is
changing rapidly).
address@hidden Examples
address@hidden Examples
address@hidden Examples2
address@hidden Examples2
@c %**end of header
Let's close with a couple examples.
@@ -4455,8 +4455,8 @@ gossip
@item automatically learn about hostlist servers from the gossip of other peers
@end itemize
address@hidden Limitations
address@hidden Limitations
address@hidden Limitations2
address@hidden Limitations2
@c %**end of header
The HOSTLIST daemon does not:
@@ -4929,8 +4929,8 @@ subsystems tend to need to store per-peer information in
persistent way. To not
duplicate this functionality we plan to provide a PEERSTORE service providing
this functionality
address@hidden Features
address@hidden Features
address@hidden Features2
address@hidden Features2
@c %**end of header
@itemize @bullet
@@ -4940,15 +4940,15 @@ this functionality
@item Differentiation between public and friend-only HELLO
@end itemize
address@hidden Limitations
address@hidden Limitations
address@hidden Limitations3
address@hidden Limitations3
@itemize @bullet
@item Does not perform HELLO validation
@end itemize
address@hidden Peer Information
address@hidden Peer Information
address@hidden DeveloperPeer Information
address@hidden DeveloperPeer Information
@c %**end of header
The PEERINFO subsystem stores these information in the form of HELLO messages
@@ -5082,8 +5082,8 @@ operation allowing to cancel the operation with the
respective cancel function
you can iterate over all information stored with PEERINFO or you can tell
PEERINFO to notify if new peer information are available.
address@hidden Obtaining Information
address@hidden Obtaining Information
address@hidden Obtaining Information2
address@hidden Obtaining Information2
@c %**end of header
To iterate over information in PEERINFO you use @code{GNUNET_PEERINFO_iterate}.
@@ -5343,8 +5343,8 @@ are created by sending the
@code{GNUNET_SERVICE_SET_CREATE} message over a new
client connection. Multiple operations for one set are multiplexed over one
client connection, using a request id supplied by the client.
address@hidden Listeners
address@hidden Listeners
address@hidden Listeners2
address@hidden Listeners2
@c %**end of header
Each listener also requires a seperate client connection. By sending the
@@ -5620,8 +5620,8 @@ are used for registering the watch.
@node The STATISTICS Client-Service Protocol
@c %**end of header
address@hidden Statistics retrieval
address@hidden Statistics retrieval
address@hidden Statistics retrieval2
address@hidden Statistics retrieval2
@c %**end of header
To retrieve statistics, the client transmits a message of type
@@ -5777,8 +5777,8 @@ new block plugins --- it does the minimal work by
implementing a plugin that
performs no validation at all. The respective @strong{Makefile.am} shows how to
build and install a block plugin.
address@hidden Conclusion
address@hidden Conclusion
address@hidden Conclusion2
address@hidden Conclusion2
@c %**end of header
In conclusion, GNUnet subsystems that want to use the DHT need to define a
@@ -5978,8 +5978,8 @@ estimate, the selection of the peers maybe randomized or
by proximity to the
key. Furthermore, requests include a set of peers that a request has already
traversed; those peers are also excluded from the selection.
address@hidden PUTting data into the DHT
address@hidden PUTting data into the DHT
address@hidden PUTting data into the DHT2
address@hidden PUTting data into the DHT2
@c %**end of header
To PUT data into the DHT, the service sends a @code{struct PeerPutMessage} of
@@ -5996,8 +5996,8 @@ previous hop; however, the path should not include the
identity of the previous
hop and the receiver should append the identity of the sender to the path, not
its own identity (this is done to reduce bandwidth).
address@hidden GETting data from the DHT
address@hidden GETting data from the DHT
address@hidden GETting data from the DHT2
address@hidden GETting data from the DHT2
@c %**end of header
A peer can search the DHT by sending @code{struct PeerGetMessage}s of type
@@ -6423,8 +6423,8 @@ The NAMECACHE plugin API consists of two functions,
@code{cache_block} to store
a block in the database, and @code{lookup_block} to lookup a block in the
database.
address@hidden Lookup
address@hidden Lookup
address@hidden Lookup2
address@hidden Lookup2
@c %**end of header
The @code{lookup_block} function is expected to return at most one block to the
@@ -6432,8 +6432,8 @@ iterator, and return @code{GNUNET_NO} if there were no
non-expired results. If
there are multiple non-expired results in the cache, the lookup is supposed to
return the result with the largest expiration time.
address@hidden Store
address@hidden Store
address@hidden Store2
address@hidden Store2
@c %**end of header
The @code{cache_block} function is expected to try to store the block in the
diff --git a/gnunet.texi b/gnunet.texi
index 92d0f1e..a77d57d 100644
--- a/gnunet.texi
+++ b/gnunet.texi
@@ -84,6 +84,11 @@ Philosophy
* Backup of Identities and Egos::
* Revocation::
+Installation
+
+* Dependencies::
+* External dependencies::
+
@end detailmenu
@end menu
diff --git a/installation.texi b/installation.texi
index f2af005..9862e24 100644
--- a/installation.texi
+++ b/installation.texi
@@ -19,6 +19,12 @@ profile ID number included. We will then relax these
restrictions on your
account. We're sorry for this inconvenience; however, few people would want to
read this site if 99% of it was advertisements for bogus websites.
address@hidden
+* Dependencies
+* External dependencies
+* Internal dependencies
address@hidden menu
+
@node Dependencies
@chapter Dependencies
@c %**end of header
@@ -27,7 +33,7 @@ This document lists the various known dependencies for GNUnet
0.10.x.
Suggestions for missing dependencies or wrong version numbers are welcome.
@node External dependencies
address@hidden External depencies
address@hidden External dependencies
@c %**end of header
These packages must be installed before a typical GNUnet installation
@@ -933,8 +939,8 @@ sources, and finally compiling and installing the
libraries:@
For this, simply follow the generic installation instructions from
here.
address@hidden But wait, there is more!
address@hidden But wait, there is more!
address@hidden But wait there is more!
address@hidden But wait there is more!
So far, we installed all of the packages and dependencies required to ensure
that all of GNUnet would be built. However, while for example the plugins to
@@ -1154,8 +1160,8 @@ you might simply already have some of the necessary
packages installed. Thus,
it is suggested that you simply install the desktop environment of your choice
before beginning with the instructions.
address@hidden Update
address@hidden Update
address@hidden Update2
address@hidden Update2
After any installation, you should begin by running@
@code{@
@@ -1167,8 +1173,8 @@ to indicate that you need to type in this command as
"root" (or prefix with
"sudo"), whereas "$" is used to indicate typing in a command as a normal
user.
address@hidden Installing Packages
address@hidden Installing Packages
address@hidden Installing Packages2
address@hidden Installing Packages2
We begin by installing a few Debian packages from stable:@
@example
@@ -1184,8 +1190,8 @@ We begin by installing a few Debian packages from stable:@
libmicrohttpd-dev
@end example
address@hidden Installing Dependencies from Source
address@hidden Installing Dependencies from Source
address@hidden Installing Dependencies from Source2
address@hidden Installing Dependencies from Source2
Yes, we said we start with a Debian 8 "stable" system, but because Debian
linked GnuTLS without support for DANE, we need to compile a few things, in
@@ -1215,14 +1221,14 @@ sources, and finally compiling and installing the
libraries:@
$ make ; sudo make install; cd ..@
}
address@hidden Installing GNUnet from Source
address@hidden Installing GNUnet from Source
address@hidden Installing GNUnet from Source2
address@hidden Installing GNUnet from Source2
For this, simply follow the generic installation instructions from@
here.
address@hidden But wait, there is more!
address@hidden But wait, there is more!
address@hidden But wait (again) there is more!
address@hidden But wait (again) there is more!
So far, we installed all of the packages and dependencies required to ensure
that all of GNUnet would be built. However, while for example the plugins to
@@ -2976,8 +2982,8 @@ settings. Just specify the interface to use:@
@node User Manual for the wlan transport plugin
@subsubsection User Manual for the wlan transport plugin
address@hidden Introduction
address@hidden Introduction
address@hidden Introduction2
address@hidden Introduction2
The wlan transport plugin enables GNUnet to send and to receive data on a wlan
interface. It has not to be connected to a wlan network as long as sender and
@@ -2985,8 +2991,8 @@ receiver are on the same channel. This enables you to get
connection to the
GNUnet where no internet access is possible, for example while catastrophes or
when censorship cuts you off the internet.
address@hidden Requirements
address@hidden Requirements
address@hidden Requirements2
address@hidden Requirements2
@itemize @bullet
@@ -3492,8 +3498,8 @@ Note that the proxy uses libcurl. Make sure your version
of libcurl uses GnuTLS
and NOT OpenSSL. The proxy will not work with libcurl compiled against
OpenSSL.
address@hidden Testing
address@hidden Testing
address@hidden Testing2
address@hidden Testing2
Now for testing purposes we can create some records in our zone to test the SSL
functionality of the proxy:@
diff --git a/user.texi b/user.texi
index 04dc210..89f5a60 100644
--- a/user.texi
+++ b/user.texi
@@ -8,8 +8,8 @@ outside of the scope of this tutorial. Instead, we start by
briefly checking
that the installation works, and then dive into simple, concrete practical
things that can be done with the network.
address@hidden Introduction
address@hidden Introduction
address@hidden UserIntroduction
address@hidden UserIntroduction
This book documents how to use the various Peer-to-Peer applications of the
GNUnet system. As GNUnet evolves, we will add new chapters for the various
@@ -510,8 +510,8 @@ automatically create the necessary records in the
respective zone.
@section First steps: Using the GNUnet VPN
@c %**end of header
address@hidden Preliminaries
address@hidden Preliminaries
address@hidden Preliminaries2
address@hidden Preliminaries2
@c %**end of header
To test the GNUnet VPN, we should first run a web server. The easiest way to do
--
To stop receiving notification emails like this one, please contact
address@hidden
- [GNUnet-SVN] [gnunet-texinfo] branch master updated (ea9421b -> 75c085d),
gnunet <=