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 configuratio
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 no
Christian Grothoff writes:
> 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.
For completeness and not targeting just users, wouldn't it make
sense to have all options in the system? If you say it's not
On 04/02/2016 05:51 PM, Nils Gillmann wrote:
> Christian Grothoff writes:
>
>> 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.
>
> For completeness and not targeting just users, wouldn't it make
> s
> I don't think it make sense to integrate 'testbed', as that's really for
> experiments by researchers and never a system service.
It might be useful if you want to run your experiments on lots of Guix nodes.
> Most of the "interesting" options you can also manipulate via
> 'gnunet-setup', but
tg(x) <*@tg-x.net> writes:
>> I don't think it make sense to integrate 'testbed', as that's really for
>> experiments by researchers and never a system service.
>
> It might be useful if you want to run your experiments on lots of Guix nodes.
I think I leave that to extend for others, currently m
