Date: Sat, 7 Sep 2013 17:27:19 -0700 From: Adrian Chadd <adrian@freebsd.org> To: Mark R V Murray <mark@grondar.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, Ian Lepore <ian@freebsd.org> Subject: Re: random(4) update causes mips compile fail | mips boot fail Message-ID: <CAJ-VmomUcgVckLreOgJAeCd0Sx1Yw3ggaUrVtO2RZnm4chmn1A@mail.gmail.com> In-Reply-To: <82260B0E-E2CF-4D7B-B1E2-EEFAF25BD090@grondar.org> References: <1378572186.1588.5.camel@localhost> <24DB010A-F374-491B-9203-FDDD7EA14A51@grondar.org> <1378579011.1588.16.camel@localhost> <9240BEF1-2791-4D58-A422-08AEF1CD306C@grondar.org> <1378586316.1111.524.camel@revolution.hippie.lan> <82260B0E-E2CF-4D7B-B1E2-EEFAF25BD090@grondar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[snip] ok. So I can work around this for these MIPS AP images by echoing something into /dev/random ? -adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmomUcgVckLreOgJAeCd0Sx1Yw3ggaUrVtO2RZnm4chmn1A>