From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 0/2] haveged: systemd service: move earlier in startup
Date: Mon, 20 Jan 2020 23:57:02 +0100 [thread overview]
Message-ID: <1579561024-27501-1-git-send-email-apr@cn-eng.de> (raw)
On a device with defective HW RNG here, it takes quite long until
the bootup is finished, as kernel random is not seeded. Leading
to blockings for anything needing /dev/random.
As kind of a workaround (until I fixed the HW RNG driver), I pulled
in haveged. To work as expected, I needed to move haveged startup
in systemd to a more earlier point.
This patch series is probably NOT for inclusion to PTXdist mainline.
In a first step, haveged should be updated to the latest 1.9.8 release.
Also, all of this here is NOT really tested or well thought out.
It just works for me (tm).
I send it, in case somebody else has the same trouble to workaround.
Andreas Pretzsch (2):
haveged: systemd service: import haveged.service from haveged 1.9.2
source
haveged: systemd service: move from multi-user.target to
sysinit.target
projectroot/usr/lib/systemd/system/haveged.service | 12 ++++++++++++
rules/haveged.make | 4 ++--
2 files changed, 14 insertions(+), 2 deletions(-)
create mode 100644 projectroot/usr/lib/systemd/system/haveged.service
--
2.19.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2020-01-20 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 22:57 Andreas Pretzsch [this message]
2020-01-20 22:57 ` [ptxdist] [PATCH 1/2] haveged: systemd service: import haveged.service from haveged 1.9.2 source Andreas Pretzsch
2020-01-20 22:57 ` [ptxdist] [PATCH 2/2] haveged: systemd service: move from multi-user.target to sysinit.target Andreas Pretzsch
2020-01-24 17:25 ` Michael Olbrich
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1579561024-27501-1-git-send-email-apr@cn-eng.de \
--to=apr@cn-eng.de \
--cc=ptxdist@pengutronix.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox