Hi,
I’ve stumbled upon this too with recently upgraded machine (to NetBSD 8.0_BETA
(GENERIC.201803261630Z))
Kernel RNG “5887 68 5” runs test FAILURE: too many runs of 1 1s (2691 >=2685)
cprng 5887 68 5: failed statistical RNG test
The difference here is that the machine also loses network
> On 6 Sep 2016, at 18:14, Richard PALO <rich...@netbsd.org> wrote:
>
> Le 24/02/15 08:19, Fredrik Pettai a écrit :
>> Hi,
>>
>> I noted that mDNSResponder name resolution stopped working on 7.99.4 (built
>> 4 feb)
>>
>> -bash-
Hi,
Well, due to the recent ntp vulnerabilities (and previous ntp bugs
vulnerabilities), running ntpd chrooted seems like a sane default.
So, isn't it time that NetBSD gets 'echo ntpd_chrootdir=/var/chroot/ntpd/“
/etc/rc.conf.d/ntpd’ ?
This has been working fine on the stable branches AFAIK.
On 27 Dec 2014, at 08:15 , Michael van Elst mlel...@serpens.de wrote:
pet...@nordu.net (Fredrik Pettai) writes:
So, isn't it time that NetBSD gets 'echo ntpd_chrootdir=/var/chroot/ntpd/“
/etc/rc.conf.d/ntpd’ ?
Dec 27 04:08:41 netbsd-7_BETA ntpd[6375]: giving up resolving host
0
(Recent) netbsd-7 version of cpuctl will returns (null) if you feed it with a
non-existing parameter:
-bash-4.3$ cpuctl foo
cpuctl: unknown command ``(null)''
It used to say:
-bash-4.3$ cpuctl foo
cpuctl: unknown command ``foo’’
/P
That said: whatever became of backward compatibility and ABI
adherence? Is there a good reason why a compiler change and
mixing object modules from different gcc versions can trigger
this panic? I would have thought the answer to that would be
no, but I'm willing to be educated...
Another
On Oct 27, 2014, at 19:59 , Fredrik Pettai pet...@nordu.net wrote:
That said: whatever became of backward compatibility and ABI
adherence? Is there a good reason why a compiler change and
mixing object modules from different gcc versions can trigger
this panic? I would have thought
On Oct 26, 2014, at 12:41 , Havard Eidnes h...@uninett.no wrote:
Hi,
I updated my netbsd-7 amd64 testing machine yesterday at around
11:17 local time (to a local mirror which may lag 4 hours behind
anoncvs), and this time I got a panic, transcribed via paper:
panic: kernel diagnostic
On Apr 16, 2014, at 02:55 , Christos Zoulas chris...@astron.com wrote:
In article 904e4050-cc44-494d-9b9d-c13004a12...@baaz.fr,
Jean-Yves Moulin j...@baaz.fr wrote:
Hi,
Sorry if this is not the right list. I prefer to post here before
posting to dovecot mailing list.
So, on a 6.99.40
On Jan 18, 2014, at 10:59 , Jukka Ruohonen jruoho...@iki.fi wrote:
On Fri, Jan 17, 2014 at 03:14:03PM +0100, Fredrik Pettai wrote:
Hi,
I noticed that the NetBSD 6.99(.28) kernel output is complaining more that
the older 6.1.x
Most notable are these messages:
Unrelated, but can you test
My mistake from yesterdays import of zless, I've added it back in…
(my build.sh release didn't complain, strangely enough)
/P
On Nov 13, 2013, at 05:56 , Paul Goyette p...@whooppee.com wrote:
This is also failing in amd64 ...
On Tue, 12 Nov 2013, Paul Goyette wrote:
With sources
11 matches
Mail list logo
