On Friday 11 March 2005 18:34, Marcos D. Marado Torres wrote: > Greetings, > > I convinced a friend few minutes ago to try GNUnet (in Linux). > After downloading it, unpacking it, ./configure, make and make install, the > problems started: /etc/gnunet.conf wasn't there, the gnunet.conf created in > his ~/.gnunet/ didn't have lot of fields (like INTERFACE or GNUNETD_HOME), > and soon he said "bah, this isn't working yet!" and just quit'd on the idea > of trying GNUnet. > > Shouldn't we try to make GNUnet instalation and configuration more > user-friendly?
Well, it sounds to me like you just messed up the two config files. If a configuration file is needed and does not exist, the respective GNUnet binary will create one. However, if you create a configuration file for clients and then force the server to use it with -c, that won't work. Also, if you run gnunetd as an ordinary user, it will not be able to generate /etc/gnunetd.conf or access /var. Those are simple permission issues that arise from the fact that we use different users for gnunetd and the UIs. I don't think we can easily fix that. However, if you really just want a simple way to get GNUnet running, why don't you use one of the binary packages? I've tried the debian package, and it is really nice in that it pretty much does all of the setup for you. Also, making things more user-friendly is always easier said than done. Do you have any concrete suggestions? Christian _______________________________________________ GNUnet-developers mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnunet-developers
