diff options
author | ng0 <ng0@n0.is> | 2018-02-03 11:42:57 +0000 |
---|---|---|
committer | ng0 <ng0@n0.is> | 2018-02-03 11:42:57 +0000 |
commit | c6bb28c5180f9230badf3e02e48a2d2b1039ac72 (patch) | |
tree | c35350d0668ea847a3db4c1a49d747107d0c58b1 /doc/documentation | |
parent | 13a7c80d9f8f7daeedac6bc3361fee0aa658d68a (diff) | |
download | gnunet-c6bb28c5180f9230badf3e02e48a2d2b1039ac72.tar.gz gnunet-c6bb28c5180f9230badf3e02e48a2d2b1039ac72.zip |
simple -> uncomplicated
Diffstat (limited to 'doc/documentation')
-rw-r--r-- | doc/documentation/chapters/user.texi | 22 |
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 | ||
432 | Next, you should try resolving your own GNS records. | 432 | Next, you should try resolving your own GNS records. |
433 | The simplest method is to do this by explicitly resolving | 433 | The method we found to be the most uncomplicated is to do this |
434 | using @code{gnunet-gns}. In the shell, type: | 434 | by 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 |
1497 | Now you can add (or edit, or remove) records in your GNS zone using the | 1497 | Now you can add (or edit, or remove) records in your GNS zone using the |
1498 | gnunet-setup GUI or using the gnunet-namestore command-line tool. | 1498 | @command{gnunet-setup} GUI or using the @command{gnunet-namestore} |
1499 | command-line tool. | ||
1499 | In either case, your records will be stored in an SQL database under | 1500 | In either case, your records will be stored in an SQL database under |
1500 | control of the gnunet-service-namestore. Note that if multiple users | 1501 | control of the @command{gnunet-service-namestore}. |
1501 | use one peer, the namestore database will include the combined records | 1502 | Note that if multiple users use one peer, the namestore database will |
1502 | of all users. However, users will not be able to see each other's records | 1503 | include the combined records of all users. |
1504 | However, users will not be able to see each other's records | ||
1503 | if they are marked as private. | 1505 | if they are marked as private. |
1504 | 1506 | ||
1505 | To provide a simple example for editing your own zone, suppose you | 1507 | To provide a short example for editing your own zone, suppose you |
1506 | have your own web server with IP 1.2.3.4. Then you can put an | 1508 | have your own web server with the IP @code{1.2.3.4}. Then you can put an |
1507 | A 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) |
1508 | local zone using the command: | 1510 | into 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 |