[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] r23726 - gnunet
From: |
gnunet |
Subject: |
[GNUnet-SVN] r23726 - gnunet |
Date: |
Sun, 9 Sep 2012 17:09:52 +0200 |
Author: grothoff
Date: 2012-09-09 17:09:52 +0200 (Sun, 09 Sep 2012)
New Revision: 23726
Modified:
gnunet/configure.ac
Log:
-update configure info
Modified: gnunet/configure.ac
===================================================================
--- gnunet/configure.ac 2012-09-09 14:20:50 UTC (rev 23725)
+++ gnunet/configure.ac 2012-09-09 15:09:52 UTC (rev 23726)
@@ -1187,26 +1187,21 @@
AC_MSG_NOTICE([********************************************
-You can compile GNUnet with
+Please make sure that you have created a user and group 'gnunet'
+and additionally a group 'gnunetdns'. Then, you can compile GNUnet
+with
make
-now. After that, run (if necessary as 'root')
+After that, run (if necessary as 'root')
make install
-to install everything. You may want to create a new user account
-to run the GNUnet service:
- adduser gnunet
-You also need to create an configuration file that should
-specify the path where GNUnet should store data. For example,
-you could store in "/etc/gnunet.conf" the following lines:
-
-[[PATHS]]
-SERVICEHOME = /var/lib/gnunet
-DEFAULTCONFIG = /etc/gnunet.conf
-
-Now, in order to start your peer, run as the 'gnunet' user
+to install everything.
+Then, in order to start your peer, run as the 'gnunet' user
+ mkdir $HOME/.gnunet/
+ touch $HOME/.gnunet/gnunet.conf
gnunet-arm -s
-Each GNUnet user should also create an (at least initially) empty
-configuration file:
+Each GNUnet user should also be added to the 'gnunet' group (may
+require fresh login to come into effect) and create an (at least
+initially) empty configuration file:
mkdir $HOME/.gnunet/
touch $HOME/.gnunet/gnunet.conf
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] r23726 - gnunet,
gnunet <=