| Age | Commit message (Collapse) | Author |
|---|
|
Now it appears to be sufficiently good at producing a distinct seed at
each boot without using a /etc/seed file. Previously it did not do this.
Of course this is nowhere near cryptographically secure but randomness
does assist with things such as kmalloc.
|
|
|
|
This is mainly done to test for uninitlalized memory and find bugs
faster. Therefore it does not need to be cryptographically secure or
perfectly uniform. Xoshiro256++ seems like a good fit.
|
|
|
|
This is to allow both the kernel and the userland to share certain
header files and to make the folder structure a bit more clear.
|
