[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23605: /dev/urandom not seeded across reboots
From: |
Ludovic Courtès |
Subject: |
bug#23605: /dev/urandom not seeded across reboots |
Date: |
Sat, 28 May 2016 15:57:06 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Leo Famulari <address@hidden> skribis:
> 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)
[...]
> 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 ()>
[...]
> +(define (urandom-seed-shepherd-service)
[...]
> +(define urandom-seed-service-type
> + (service-type (name 'urandom-seed)
> + (extensions
> + (list (service-extension shepherd-root-service-type
> + urandom-seed-shepherd-service)
Service extension procedures are called with one argument, which is the
service’s value (info "(guix) Service Reference").
Usually, the service’s value is a configuration object, but in this
case, the service’s value doesn’t matter, so you could simply write:
(define (urandom-seed-shepherd-service _)
…)
> + ;; Add urandom-seed to the system profile
> + (service-extension profile-service-type list)))))
The ‘profile-service-type’ represents the system profile, i.e.,
/run/current-system/profile. Extending it means adding a package to
it.
But here, IIUC, there’s no package to be added to the profile, so you
should just remove it.
Last round and we’re done! :-)
Thanks for persevering, and sorry it’s not easier. Maybe you’ll have
ideas on how to improve the manual and/or the API?
Ludo’.
- bug#23605: /dev/urandom not seeded across reboots, (continued)
bug#23605: /dev/urandom not seeded across reboots, Ludovic Courtès, 2016/05/24
- bug#23605: /dev/urandom not seeded across reboots, Leo Famulari, 2016/05/25
- bug#23605: /dev/urandom not seeded across reboots, Ludovic Courtès, 2016/05/25
- bug#23605: /dev/urandom not seeded across reboots, Leo Famulari, 2016/05/26
- bug#23605: /dev/urandom not seeded across reboots,
Ludovic Courtès <=
- bug#23605: /dev/urandom not seeded across reboots, Leo Famulari, 2016/05/28
- bug#23605: /dev/urandom not seeded across reboots, Leo Famulari, 2016/05/28
- bug#23605: /dev/urandom not seeded across reboots, Leo Famulari, 2016/05/28
- bug#23605: /dev/urandom not seeded across reboots, Leo Famulari, 2016/05/28
- bug#23605: /dev/urandom not seeded across reboots, Ludovic Courtès, 2016/05/28
- bug#23605: /dev/urandom not seeded across reboots, Leo Famulari, 2016/05/28
- bug#23605: /dev/urandom not seeded across reboots, Leo Famulari, 2016/05/28
- bug#23605: /dev/urandom not seeded across reboots, Ludovic Courtès, 2016/05/29
bug#23605: /dev/urandom not seeded across reboots, Leo Famulari, 2016/05/27