From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 1c72742bca7e8e5e6151c77481e9110f6b8a1cf4
Date: Sun, 02 Feb 2014 12:51:25 +0100 [thread overview]
Message-ID: <20140202115135.3F73F21070@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 1c72742bca7e8e5e6151c77481e9110f6b8a1cf4 (commit)
from c924c7d1d19da6863ec6de9352c1d6d50f35502f (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 1c72742bca7e8e5e6151c77481e9110f6b8a1cf4
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Feb 2 12:50:22 2014 +0100
krng: use kernel entropy if no random-seed is stored.
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/init.d/random | 3 +++
1 file changed, 3 insertions(+)
Difference in files:
diff --git a/src/initscripts/init.d/random b/src/initscripts/init.d/random
index 26c64e3..7159b53 100644
--- a/src/initscripts/init.d/random
+++ b/src/initscripts/init.d/random
@@ -13,6 +13,9 @@ case "$1" in
boot_mesg "Initializing kernel random number generator..."
if [ -f /var/tmp/random-seed ]; then
/bin/cat /var/tmp/random-seed >/dev/urandom
+ else
+ /bin/dd if=/dev/random of=/dev/urandom \
+ count=1 &>/dev/null
fi
/bin/dd if=/dev/urandom of=/var/tmp/random-seed \
count=1 &>/dev/null
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-02-02 11:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140202115135.3F73F21070@argus.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/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