aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorng0 <ng0@n0.is>2018-02-03 11:42:57 +0000
committerng0 <ng0@n0.is>2018-02-03 11:42:57 +0000
commitc6bb28c5180f9230badf3e02e48a2d2b1039ac72 (patch)
treec35350d0668ea847a3db4c1a49d747107d0c58b1 /doc
parent13a7c80d9f8f7daeedac6bc3361fee0aa658d68a (diff)
downloadgnunet-c6bb28c5180f9230badf3e02e48a2d2b1039ac72.tar.gz
gnunet-c6bb28c5180f9230badf3e02e48a2d2b1039ac72.zip
simple -> uncomplicated
Diffstat (limited to 'doc')
-rw-r--r--doc/documentation/chapters/user.texi22
1 files changed, 12 insertions, 10 deletions
diff --git a/doc/documentation/chapters/user.texi b/doc/documentation/chapters/user.texi
index 6ec7ef3ea..998ba37eb 100644
--- a/doc/documentation/chapters/user.texi
+++ b/doc/documentation/chapters/user.texi
@@ -430,8 +430,8 @@ You can now go back to the shell running @code{gnunet-bcd} and press
430@c %**end of header 430@c %**end of header
431 431
432Next, you should try resolving your own GNS records. 432Next, you should try resolving your own GNS records.
433The simplest method is to do this by explicitly resolving 433The method we found to be the most uncomplicated is to do this
434using @code{gnunet-gns}. In the shell, type: 434by explicitly resolving using @code{gnunet-gns}. In the shell, type:
435 435
436@example 436@example
437$ gnunet-gns -u test.gnu # what follows is the reply 437$ gnunet-gns -u test.gnu # what follows is the reply
@@ -1495,17 +1495,19 @@ $ gnunet-identity -C "new_zone"
1495 1495
1496@noindent 1496@noindent
1497Now you can add (or edit, or remove) records in your GNS zone using the 1497Now you can add (or edit, or remove) records in your GNS zone using the
1498gnunet-setup GUI or using the gnunet-namestore command-line tool. 1498@command{gnunet-setup} GUI or using the @command{gnunet-namestore}
1499command-line tool.
1499In either case, your records will be stored in an SQL database under 1500In either case, your records will be stored in an SQL database under
1500control of the gnunet-service-namestore. Note that if multiple users 1501control of the @command{gnunet-service-namestore}.
1501use one peer, the namestore database will include the combined records 1502Note that if multiple users use one peer, the namestore database will
1502of all users. However, users will not be able to see each other's records 1503include the combined records of all users.
1504However, users will not be able to see each other's records
1503if they are marked as private. 1505if they are marked as private.
1504 1506
1505To provide a simple example for editing your own zone, suppose you 1507To provide a short example for editing your own zone, suppose you
1506have your own web server with IP 1.2.3.4. Then you can put an 1508have your own web server with the IP @code{1.2.3.4}. Then you can put an
1507A record (A records in DNS are for IPv4 IP addresses) into your 1509@code{A} record (@code{A} records in DNS are for IPv4 IP addresses)
1508local zone using the command: 1510into your local zone using the command:
1509 1511
1510@example 1512@example
1511$ gnunet-namestore -z master-zone -a -n www -t A -V 1.2.3.4 -e never 1513$ gnunet-namestore -z master-zone -a -n www -t A -V 1.2.3.4 -e never