[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#23605: /dev/urandom not seeded across reboots

From: Leo Famulari
Subject: bug#23605: /dev/urandom not seeded across reboots
Date: Thu, 26 May 2016 12:47:07 -0400
User-agent: Mutt/1.6.0 (2016-04-01)

On Wed, May 25, 2016 at 06:54:58PM +0200, Ludovic Courtès wrote:
> Yes, it’s:
>   (service TYPE VALUE)
> but I think there’s no meaningful value for this service, so you could
> do:
>   (service urandom-seed-service-type #f)

I'm struggling to make this work. Do I need to alter the definition of
urandom-seed-shepherd-service to accept the boolean?

With the attached diff, building a VM fails like this (full backtrace

 573: 2 [loop #<<service> type: # parameters: ()>]
In srfi/srfi-1.scm:
 578: 1 [map #<procedure 519cc20 at gnu/services.scm:562:4 (service)> (# # # # 
In gnu/services/base.scm:
1217: 0 [urandom-seed-shepherd-service #f]

gnu/services/base.scm:1217:0: In procedure urandom-seed-shepherd-service:
gnu/services/base.scm:1217:0: Wrong number of arguments to #<procedure 
urandom-seed-shepherd-service ()>

> Sounds like you’re pretty much there!  :-)

Almost, I hope! Thanks for your help :)

Attachment: backtrace
Description: Text document

Attachment: urandom-seed-service.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]