diff options
Diffstat (limited to 'README')
-rw-r--r-- | README | 18 |
1 files changed, 9 insertions, 9 deletions
@@ -182,7 +182,7 @@ Recommended software for developer tools: | |||
182 | you, open a bug so that we can get a more portable | 182 | you, open a bug so that we can get a more portable |
183 | fix in. | 183 | fix in. |
184 | 184 | ||
185 | [*4] We are commited to portable tools and solutions | 185 | [*4] We are committed to portable tools and solutions |
186 | where possible. New scripts should be Posix sh | 186 | where possible. New scripts should be Posix sh |
187 | compatible, current and older scripts are | 187 | compatible, current and older scripts are |
188 | in the process of being rewritten to comply | 188 | in the process of being rewritten to comply |
@@ -213,7 +213,7 @@ For a correct functionality depending on the host OS, you need | |||
213 | to run the equivalent of these steps after installation. | 213 | to run the equivalent of these steps after installation. |
214 | Replace $(DESTDIR)$(libexecdir) with the appropriate paths, | 214 | Replace $(DESTDIR)$(libexecdir) with the appropriate paths, |
215 | for example /usr/local/lib/gnunet/libexec/. Note that this | 215 | for example /usr/local/lib/gnunet/libexec/. Note that this |
216 | obviously must be run as priviledged user. | 216 | obviously must be run as privileged user. |
217 | 217 | ||
218 | chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-vpn | 218 | chown root:root $(DESTDIR)$(libexecdir)/gnunet-helper-vpn |
219 | chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-vpn | 219 | chmod u+s $(DESTDIR)$(libexecdir)/gnunet-helper-vpn |
@@ -289,8 +289,8 @@ Building GNUnet from source | |||
289 | 289 | ||
290 | IMPORTANT: You can read further notes about compilation from source in | 290 | IMPORTANT: You can read further notes about compilation from source in |
291 | the handbook under doc/handbook/, which includes notes about specific | 291 | the handbook under doc/handbook/, which includes notes about specific |
292 | requirements for operating systems aswell. If you are a package | 292 | requirements for operating systems as well. If you are a package |
293 | mantainer for an Operating System we invite you to add your notes if | 293 | maintainer for an Operating System we invite you to add your notes if |
294 | you feel it is necessary and can not be covered in your Operating | 294 | you feel it is necessary and can not be covered in your Operating |
295 | System's documentation. | 295 | System's documentation. |
296 | 296 | ||
@@ -338,7 +338,7 @@ in 'contrib/services' or by running: | |||
338 | 338 | ||
339 | 339 | ||
340 | Note that you must read paragraph "Notes on setuid", which documents steps you | 340 | Note that you must read paragraph "Notes on setuid", which documents steps you |
341 | have to follow after the installation, as a priviledged user. We require some | 341 | have to follow after the installation, as a privileged user. We require some |
342 | binaries to be setuid. The most portable approach across all supported | 342 | binaries to be setuid. The most portable approach across all supported |
343 | platforms and targets is to let this be handled manually. | 343 | platforms and targets is to let this be handled manually. |
344 | The installation will work if you do not run these steps as root, but some | 344 | The installation will work if you do not run these steps as root, but some |
@@ -376,7 +376,7 @@ $GNUNET_PREFIX you might have specified, as those libraries must be in | |||
376 | your packaging script to miss those plugins, so you might need to do some | 376 | your packaging script to miss those plugins, so you might need to do some |
377 | additional manual work to include those libraries in your binary package(s). | 377 | additional manual work to include those libraries in your binary package(s). |
378 | Similarly, if you want to use the GNUnet Name System and did NOT run | 378 | Similarly, if you want to use the GNUnet Name System and did NOT run |
379 | GNUnet's 'make install' process with priviledged rights, the libraries will be | 379 | GNUnet's 'make install' process with privileged rights, the libraries will be |
380 | installed to "$GNUNET_PREFIX" and you will have to move them to "/lib/" | 380 | installed to "$GNUNET_PREFIX" and you will have to move them to "/lib/" |
381 | manually. | 381 | manually. |
382 | 382 | ||
@@ -443,7 +443,7 @@ GNUnet by periodically executing | |||
443 | $ cat $SERVICEHOME/data/hosts/* > the_file | 443 | $ cat $SERVICEHOME/data/hosts/* > the_file |
444 | 444 | ||
445 | and offering 'the_file' via your web server. Alternatively, you can | 445 | and offering 'the_file' via your web server. Alternatively, you can |
446 | run the build-in web server by adding '-p' to the OPTIONS value | 446 | run the built-in web server by adding '-p' to the OPTIONS value |
447 | in the "hostlist" section of gnunet.conf and opening the respective | 447 | in the "hostlist" section of gnunet.conf and opening the respective |
448 | HTTPPORT to the public. | 448 | HTTPPORT to the public. |
449 | 449 | ||
@@ -495,7 +495,7 @@ https://bugs.gnunet.org/ or our bugs mailinglist. | |||
495 | Please make sure to run the script "contrib/scripts/gnunet-bugreport" | 495 | Please make sure to run the script "contrib/scripts/gnunet-bugreport" |
496 | and include the output with your bug reports. More about how to | 496 | and include the output with your bug reports. More about how to |
497 | report bugs can be found in the GNUnet FAQ on the webpage. Submit | 497 | report bugs can be found in the GNUnet FAQ on the webpage. Submit |
498 | patches via E-Mail to gnunet-developers@gnu.org, formated with | 498 | patches via E-Mail to gnunet-developers@gnu.org, formatted with |
499 | `git format-patch`. | 499 | `git format-patch`. |
500 | 500 | ||
501 | In order to run the unit tests by hand (instead of using "make check"), | 501 | In order to run the unit tests by hand (instead of using "make check"), |
@@ -540,7 +540,7 @@ Then set in the HTTP section of gnunet.conf the "ADVERTISED_PORT" to | |||
540 | "ADVERTISED_PORT" to "443" and "PORT" to 4433. | 540 | "ADVERTISED_PORT" to "443" and "PORT" to 4433. |
541 | 541 | ||
542 | You can do the same trick for the TCP and UDP transports if you want | 542 | You can do the same trick for the TCP and UDP transports if you want |
543 | to map them to a priviledged port (from the point of view of the | 543 | to map them to a privileged port (from the point of view of the |
544 | network). However, we are not aware of this providing any advantages | 544 | network). However, we are not aware of this providing any advantages |
545 | at this point. | 545 | at this point. |
546 | 546 | ||