Differences

This shows you the differences between two versions of the page.

--- usb-devices:onerng [2020/06/16 19:00] – [Create a 10M file] chuck
+++ usb-devices:onerng [2020/06/16 19:29] (current) – [Installing software] chuck
@@ Line 44: / Line 44: @@
 You can (and should) verify what I typed here at the Official Site:
 http://onerng.info/onerng/
+----
 ====rng-tools service====
@@ Line 363: / Line 365: @@
 ----
-===entropy_avail===
+====entropy_avail====
-You can check the amount of entropy available by reading the file ''%%/proc/sys/kernel/random/entropy_avail%%''. I created a oneliner to monitor it while I ran the above tests:
+You can check the amount of entropy available by reading the file ''%%/proc/sys/kernel/random/entropy_avail%%''.
+<WRAP announcement green>
+Here's a oneliner I wrote to monitor it from another terminal while I ran the above tests:
 <code>
 while true; do cat /proc/sys/kernel/random/entropy_avail; sleep 1; done
 </code>
+</WRAP>
-I noticed that while idle and with the OneRNG plugged in, the value stayed above 2500 and would climb past 3000 if left alone for a while. The max value can be found in ''%%/proc/sys/kernel/random/poolsize%%'' (where mine is set at 4096).
+I noticed that while idle and with the OneRNG plugged in, the value stayed above 2500 and would climb well past 3000 if left alone for a while. The max value can be found in ''%%/proc/sys/kernel/random/poolsize%%'' (where mine is set at 4096).
   * When running from ''%%/dev/random%%'', the **entropy_available** quickly depletes until the task is finished.
-    * With the OneRNG plugged in, it instantly regenerates to above 2000.
+    * When the OneRNG **is** plugged in, it instantly regenerates to above 2000 once the task is finished.
-    * Without the OneRNG plugged in, it slowly starts rising.
+    * When the OneRNG ** is not** plugged in, it slowly starts rising once the task is finished.
   * When running from ''%%/dev/ttyACM0%%'', the **entropy_available** seems to stay the same while creating the 10M file.
   * When running from ''%%/dev/urandom%%'', the **entropy_available** seems to stay the same while creating the 10M file.