daily CVS update output

2017-04-10 Thread NetBSD source update
Updating src tree: P src/distrib/sets/lists/man/mi P src/distrib/sets/lists/misc/mi P src/distrib/utils/embedded/conf/armv7.conf P src/doc/3RDPARTY P src/doc/CHANGES P src/etc/mtree/NetBSD.dist.base P src/external/bsd/bc/bin/Makefile P src/external/bsd/bc/dist/bc.y P

Automated report: NetBSD-current/i386 build success

2017-04-10 Thread NetBSD Test Fixture
The NetBSD-current/i386 build is working again. The following commits were made between the last failed build and the successful build: 2017.04.11.01.22.13 christos src/distrib/sets/lists/misc/mi,v 1.204 Log files can be found at:

Re: kern/52056: mount -u / causes a kernel assertion

2017-04-10 Thread Rhialto
On Sat 11 Mar 2017 at 08:00:54 +0700, Robert Elz wrote: > Given all that, the best might be to basically copy the FreeBSD setup, > though I think I would prefer if > > mount -u > > with no command line options at all (which currently means mount rw, > and disable any other mount options

Automated report: NetBSD-current/i386 build failure

2017-04-10 Thread NetBSD Test Fixture
This is an automatically generated notice of a NetBSD-current/i386 build failure. The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host, using sources from CVS date 2017.04.10.16.45.57. An extract from the build.sh output follows: obsolete_stand fix: postinstall fixes passed:

Re: file corruption

2017-04-10 Thread Patrick Welche
On Fri, Apr 07, 2017 at 06:50:29PM +0100, Patrick Welche wrote: > On Fri, Apr 07, 2017 at 10:42:20AM -0400, Ian D. Leroux wrote: > > On Wed, Apr 5, 2017, at 08:01, Patrick Welche wrote: > > > It seems something recentish broke FFS, and WAPBL is blameless... > > > > I won't be much use to you, but

Re: npf bug(?)

2017-04-10 Thread Christos Zoulas
On Apr 9, 10:53pm, 6b...@6bone.informatik.uni-leipzig.de (6b...@6bone.informatik.uni-leipzig.de) wrote: -- Subject: Re: npf bug(?) | On Sun, 9 Apr 2017, Christos Zoulas wrote: | | > Perhaps you get a lot of dup fragments? netstat -s should show you the | > stack's reassembly and fragment stats.