Mark Kettenis wrote:
> > Date: Sat, 28 Sep 2019 17:10:00 +0100
> > From: Stuart Henderson
> >
> > sysctl hw includes sensors data, and often serial numbers / VM uuids
> > that aren't included directly in dmesg. would it be worth mixing this
> > into /dev/random at boot like we do for dmesg, is
> Date: Sat, 28 Sep 2019 18:20:27 +0200 (CEST)
> From: Mark Kettenis
>
> > Date: Sat, 28 Sep 2019 17:10:00 +0100
> > From: Stuart Henderson
> >
> > sysctl hw includes sensors data, and often serial numbers / VM uuids
> > that aren't included directly in dmesg. would it be worth mixing this
> >
> Date: Sat, 28 Sep 2019 17:10:00 +0100
> From: Stuart Henderson
>
> sysctl hw includes sensors data, and often serial numbers / VM uuids
> that aren't included directly in dmesg. would it be worth mixing this
> into /dev/random at boot like we do for dmesg, is there any downside?
Not sure this
Hah! Yeah sure why not!
Stuart Henderson wrote:
> sysctl hw includes sensors data, and often serial numbers / VM uuids
> that aren't included directly in dmesg. would it be worth mixing this
> into /dev/random at boot like we do for dmesg, is there any downside?
>
> Index: rc
> ===
sysctl hw includes sensors data, and often serial numbers / VM uuids
that aren't included directly in dmesg. would it be worth mixing this
into /dev/random at boot like we do for dmesg, is there any downside?
Index: rc
===
RCS file: /
Committed, thanks!
On Wed, Sep 25, 2019 at 09:45:41AM -0700, Josh Elsasser wrote:
> I came across some code which uses __clear_cache() from
> libgcc/libcompiler_rt on 32-bit arm. Currently that just falls through
> to abort(), but enabling the existing sysarch() code works for me.
>
> diff --git
