Hi Nils, I don't think it make sense to integrate 'testbed', as that's really for experiments by researchers and never a system service.
I think / hope all relevant configuration options are reasonably documented in the conf.d/-files, and AFAIK there are none that are mutually exclusive in any non-obvious way (obvious way: TCP port won't be useful if you don't enable TCP). Most of the "interesting" options you can also manipulate via 'gnunet-setup', but that largely raises the question of how to enable such a tool the Guix-way. We also plan/hope/want to have a well-working option "gnunet-setup -a" (maybe to be moved to gnunet-nat") for automatic configuration of the networking options. The option exists, how well it works is another question (eternal work-in-progress). If you have any specific questions, please don't hesitate to ask! Happy hacking! -Christian On 04/02/2016 01:22 PM, Nils Gillmann wrote: > I am currently in the planning stages of writing a system service > for GuixSD. > With system service I mean that it will be able to start a > service through our init system, shepperd, and be able to define > the complete gnunet configuration through the file which handles > the complete system configuration (often called config.scm or > system.scm). > > Before I test out every possible functionality I currently can't > test, are there config options which disable each other which are > maybe not so good documented in the conf.d/ files? > > I plan to integrate over time: testbed, user, server (purely > functional exit node and similar things). >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ GNUnet-developers mailing list GNUnet-developers@gnu.org https://lists.gnu.org/mailman/listinfo/gnunet-developers