Index of current-users for November, 2016


FromSubject
11/01/2016
Chavdar IvanovRe: /etc/rc.d/mountall in -current
NetBSD source updatedaily CVS update output
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build failure
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build success
11/02/2016
NetBSD source updatedaily CVS update output
Andreas GustafssonRe: ffs_newvnode: inode has non zero blocks
Re: ffs_newvnode: inode has non zero blocks
Andreas GustafssonRe: ffs_newvnode: inode has non zero blocks
Re: ffs_newvnode: inode has non zero blocks
Andreas GustafssonRe: ffs_newvnode: inode has non zero blocks
=?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?=Re: ffs_newvnode: inode has non zero blocks
11/03/2016
NetBSD source updatedaily CVS update output
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build failure
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build success
11/04/2016
NetBSD source updatedaily CVS update output
Andreas GustafssonRe: ffs_newvnode: inode has non zero blocks
Paul GoyetteHeads up! (if you're running a modular kernel)
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build failure
11/05/2016
NetBSD source updatedaily CVS update output
11/06/2016
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build success
NetBSD source updatedaily CVS update output
Nicolas Jolywait4(2) do not fail with WNOHANG if there is no child
Robert ElzRe: wait4(2) do not fail with WNOHANG if there is no child
Nicolas JolyRe: wait4(2) do not fail with WNOHANG if there is no child
Nicolas JolyRe: wait4(2) do not fail with WNOHANG if there is no child
Robert ElzRe: wait4(2) do not fail with WNOHANG if there is no child
Andreas GustafssonRe: ffs_newvnode: inode has non zero blocks
Lenovo T410, enabling C3 state works perfect
Robert ElzRe: wait4(2) do not fail with WNOHANG if there is no child
Kamil RytarowskiRe: wait4(2) do not fail with WNOHANG if there is no child
Kamil RytarowskiRe: wait4(2) do not fail with WNOHANG if there is no child
NetBSD Test FixtureAutomated report: NetBSD-current/i386 test failure
Robert ElzRe: wait4(2) do not fail with WNOHANG if there is no child
Kamil RytarowskiRe: wait4(2) do not fail with WNOHANG if there is no child
Nicolas JolyRe: wait4(2) do not fail with WNOHANG if there is no child
KIYOHARA TakashiSolidRun Cubox
Re: Lenovo T410, enabling C3 state works perfect
Robert ElzRe: wait4(2) do not fail with WNOHANG if there is no child
Kamil RytarowskiRe: wait4(2) do not fail with WNOHANG if there is no child
Robert ElzRe: wait4(2) do not fail with WNOHANG if there is no child
Robert ElzRe: wait4(2) do not fail with WNOHANG if there is no child
Re: Lenovo T410, enabling C3 state works perfect
Paul GoyetteRe: Automated report: NetBSD-current/i386 test failure
11/07/2016
John D. BakerRe: Booting HP pavilion dv2000 laptop
NetBSD source updatedaily CVS update output
TCP on IPv6 when IPV6_USE_MIN_MTU is set
seeman doyRe: Automated report: NetBSD-current/i386 build success
Christos ZoulasRe: Automated report: NetBSD-current/i386 build success
Thomas Klausner7.99.42/Nov 2 panic: kernel diagnostic assertion "l->l_md.md_gc_ptp == NULL" failed
Andreas GustafssonRe: ffs_newvnode: inode has non zero blocks
Re: 7.99.42/Nov 2 panic: kernel diagnostic assertion "l->l_md.md_gc_ptp == NULL" failed
Andreas GustafssonRe: ffs_newvnode: inode has non zero blocks
Thomas KlausnerRe: 7.99.42/Nov 2 panic: kernel diagnostic assertion "l->l_md.md_gc_ptp == NULL" failed
11/08/2016
NetBSD source updatedaily CVS update output
Masanobu SAITOHRe: wm WOL not working anymore
=?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?=Re: ffs_newvnode: inode has non zero blocks
Christos ZoulasRe: ffs_newvnode: inode has non zero blocks
Mr.Gwon Tae YoungPlease read my attachment,let us make use of this opportunity.
=?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?=Re: ffs_newvnode: inode has non zero blocks
11/09/2016
Robert ElzRe: wait4(2) do not fail with WNOHANG if there is no child
NetBSD source updatedaily CVS update output
Nicolas JolyRe: wait4(2) do not fail with WNOHANG if there is no child
11/10/2016
NetBSD source updatedaily CVS update output
Re: Lenovo T410, enabling C3 state works perfect
11/11/2016
NetBSD source updatedaily CVS update output
Nicolas JolyRemaining time for clock_nanosleep(2) & TIMER_ABSTIME
Christos ZoulasRe: Remaining time for clock_nanosleep(2) & TIMER_ABSTIME
Weird results from nmap
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build failure
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build success
11/12/2016
NetBSD source updatedaily CVS update output
Paul GoyetteUnable to build tools from netbsd-6-0 branch on 7.99.36/7.99.42
Paul GoyetteRe: Unable to build tools from netbsd-6-0 branch on 7.99.36/7.99.42
Paul GoyetteRe: Unable to build tools from netbsd-6-0 branch on 7.99.36/7.99.42
Martin HusemannRe: Weird results from nmap
Re: Weird results from nmap
scole_mailacpica-20160930 and stdarg.h
11/13/2016
NetBSD Test FixtureAutomated report: NetBSD-current/i386 test failure
NetBSD source updatedaily CVS update output
Martin HusemannRe: acpica-20160930 and stdarg.h
11/14/2016
NetBSD source updatedaily CVS update output
Manuel BouyerNetBSD and CH340 usb/serial
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build failure
11/15/2016
NetBSD source updatedaily CVS update output
Thomas Klausnerhow to write paxctl MPROTECT-safe JIT code?
Joerg SonnenbergerRe: how to write paxctl MPROTECT-safe JIT code?
Thomas KlausnerRe: how to write paxctl MPROTECT-safe JIT code?
Joerg SonnenbergerRe: how to write paxctl MPROTECT-safe JIT code?
Paul GoyetteRe: how to write paxctl MPROTECT-safe JIT code?
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build success
Joerg SonnenbergerRe: how to write paxctl MPROTECT-safe JIT code?
11/16/2016
NetBSD source updatedaily CVS update output
Paul GoyetteHeads up - i386 port currently broken - possibly others
Paul GoyetteRe: Heads up - i386 port currently broken - possibly others
11/17/2016
NetBSD source updatedaily CVS update output
NetBSD Test FixtureAutomated report: NetBSD-current/i386 test failure
Tom Ivar Helbekkmoin_cksum: out of data
Paul GoyetteRe: Automated report: NetBSD-current/i386 test failure
11/18/2016
Paul GoyetteRe: Automated report: NetBSD-current/i386 test failure
NetBSD source updatedaily CVS update output
Nicolas Jolyfstat(2) fails on AF_LINK socket descriptor
configure vlan-if jumbo mtu crashs kernel
Joerg SonnenbergerRe: configure vlan-if jumbo mtu crashs kernel
Christos ZoulasRe: fstat(2) fails on AF_LINK socket descriptor
11/19/2016
NetBSD source updatedaily CVS update output
Re: configure vlan-if jumbo mtu crashs kernel
11/20/2016
NetBSD source updatedaily CVS update output
Paul GoyetteMan page errors for rpcgen(1)
Paul GoyetteRe: Man page errors for rpcgen(1)
11/21/2016
NetBSD source updatedaily CVS update output
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build failure
NetBSD Test FixtureAutomated report: NetBSD-current/i386 build success
11/22/2016
Tom Ivar HelbekkmoRe: in_cksum: out of data
NetBSD source updatedaily CVS update output
11/23/2016
NetBSD source updatedaily CVS update output
11/24/2016
NetBSD source updatedaily CVS update output
Tom Ivar HelbekkmoRe: in_cksum: out of data
Christos ZoulasRe: in_cksum: out of data
Tom Ivar HelbekkmoRe: in_cksum: out of data
Christos ZoulasRe: in_cksum: out of data
Tom Ivar HelbekkmoRe: in_cksum: out of data
11/25/2016
NetBSD source updatedaily CVS update output
Tom Ivar HelbekkmoRe: in_cksum: out of data
11/26/2016
NetBSD source updatedaily CVS update output
Jarle GreipslandRe: wm devices don't work under current amd64
11/27/2016
NetBSD source updatedaily CVS update output
11/28/2016
NetBSD source updatedaily CVS update output
Masanobu SAITOHRe: wm devices don't work under current amd64
Joerg SonnenbergerWoboq-based code browser for AMD64 GENERIC and XEN3DOMU
scole_mailx11 build fails for ia64
11/29/2016
NetBSD source updatedaily CVS update output
Jun Ebiharai386 on VirturalBox boot failed
11/30/2016
Valery UshakovRe: i386 on VirturalBox boot failed
Jun EbiharaRe: i386 on VirturalBox boot failed
NetBSD source updatedaily CVS update output
Valery UshakovRe: i386 on VirturalBox boot failed
Valery UshakovRe: i386 on VirturalBox boot failed