From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: 23605@debbugs.gnu.org
Subject: bug#23605: /dev/urandom not seeded across reboots
Date: Sat, 28 May 2016 15:57:06 +0200 [thread overview]
Message-ID: <878tyumgjx.fsf@gnu.org> (raw)
In-Reply-To: <20160526164707.GA11671@jasmine> (Leo Famulari's message of "Thu, 26 May 2016 12:47:07 -0400")
Leo Famulari <leo@famulari.name> 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’.
next prev parent reply other threads:[~2016-05-28 13:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 17:58 bug#23605: /dev/urandom not seeded across reboots Leo Famulari
2016-05-24 7:05 ` Taylan Ulrich Bayırlı/Kammer
2016-05-24 16:16 ` Leo Famulari
2016-05-24 16:26 ` Thompson, David
2016-05-24 17:23 ` Leo Famulari
2016-05-24 17:29 ` Thompson, David
2016-05-25 21:53 ` Ludovic Courtès
2016-05-24 12:24 ` Ludovic Courtès
2016-05-25 16:38 ` Leo Famulari
2016-05-25 16:54 ` Ludovic Courtès
2016-05-26 16:47 ` Leo Famulari
2016-05-28 13:57 ` Ludovic Courtès [this message]
2016-05-28 18:05 ` Leo Famulari
2016-05-28 18:10 ` Leo Famulari
2016-05-28 18:26 ` Leo Famulari
2016-05-28 20:41 ` Leo Famulari
2016-05-28 20:53 ` Ludovic Courtès
2016-05-29 0:00 ` Leo Famulari
2016-05-29 0:04 ` Leo Famulari
2016-05-29 20:23 ` Ludovic Courtès
2016-05-28 1:12 ` Leo Famulari
2016-05-28 13:51 ` Ludovic Courtès
2016-05-28 1:05 ` Leo Famulari
2016-05-28 1:11 ` Ben Woodcroft
2016-05-28 1:45 ` Leo Famulari
2016-05-28 9:40 ` Ben Woodcroft
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878tyumgjx.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=23605@debbugs.gnu.org \
--cc=leo@famulari.name \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).