Recent changes to this wiki:

State the list is to be added to modules.conf. Clearing up any ambiguity that it
is only a listing from /stand/$MACHINE/$VERSION/modules.
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	22 Mar 2017 15:56:53 -0000	1.16
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	22 Mar 2017 16:04:46 -0000	1.17
@@ -48,6 +48,8 @@
 A Distribution needs to be built with the options `MKDTRACE=yes` and `MKCTF=yes`, this is taken care of automatically and doesn't need to be specified manually. The list of platforms it is applied to automatically is set in `src/share/mk/bsd.own.mk`
 
 Set the system to load the solaris and dtrace related modules in `/etc/modules.conf`, for a list of available modules, see `/stand/$MACHINE/$VERSION/modules/`
+
+For example, add the following to `/etc/modules.conf` (the file may not exist already on a system):
     
     solaris
     dtrace

Add new line to fix formatting.
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	22 Mar 2017 15:43:09 -0000	1.15
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	22 Mar 2017 15:56:53 -0000	1.16
@@ -42,6 +42,7 @@
     options         MODULAR
 
 Optionally:
+
     options         INSECURE   # permit modules to loaded from user space once system has gone multiuser and securelevel has been raised.
 
 A Distribution needs to be built with the options `MKDTRACE=yes` and `MKCTF=yes`, this is taken care of automatically and doesn't need to be specified manually. The list of platforms it is applied to automatically is set in `src/share/mk/bsd.own.mk`

Link to Brendan Gregg's DTrace one lines & FreeBSD articles.
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	22 Mar 2017 15:33:08 -0000	1.14
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	22 Mar 2017 15:43:09 -0000	1.15
@@ -1,4 +1,5 @@
-DTrace is a Dynamic Tracing framework developed by Sun and ported to NetBSD. It enables extensive instrumentation of the kernel and user space. See the [DTrace Community Page](http://dtrace.org) for more information. Also see [DTrace Introduction](http://dtrace.org/guide/preface.html). 
+DTrace is a Dynamic Tracing framework developed by Sun and ported to NetBSD. It enables extensive instrumentation of the kernel and user space. See the [DTrace Community Page](http://dtrace.org) for more information.
+Also see [DTrace Introduction](http://dtrace.org/guide/preface.html), Brendan Gregg's [DTrace one liners](http://www.brendangregg.com/DTrace/dtrace_oneliners.txt) and his notes for [DTrace on FreeBSD](https://wiki.freebsd.org/DTrace/).
 
 # Current status
 

List earm* rather than specific boards in evbarm port.
Add more providers to the list.
Note the INSECURE option is not mandatory and explain why it might be desired.
MKDTRACE & MKCTF build options are handled automatically now, direct reader to where that's controlled if the list needs to be extended.
Direct reader to use modules.conf and how they can find which modules are available on their system.
Replace instructions for creating a device node manually with a note that it is created automatically
Remove whitespace.
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	28 Nov 2015 19:23:12 -0000	1.13
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	22 Mar 2017 15:33:08 -0000	1.14
@@ -7,15 +7,16 @@
 DTrace is a work-in-progress effort and it is for x86 systems and some arm boards.
 
 * i386 and amd64
-* evbarm
-    * BEAGLEBONE and SHEEVAPLUG
+* earm* (evbarm and armv4 based ports (armv4 side requires further testing but system is built with CTF)
 
 ## Supported providers
 
 * SDT: Statically Defined Tracing
 * FBT: Function Boundary Tracing
-
-You can currently run a hello world DScript. 
+* Lockstat: Kernel Lock Statistics
+* Profile: Time based interrupt event source for Profiling
+* Syscall: System Calls
+* Syscall Linux (32bit & 64 bit): System calls via the Linux binary emulation layer
 
 ## TODO for netbsd-7
 
@@ -36,29 +37,26 @@
 
 You need the following options in your kernel: 
     
-    options         INSECURE
     options         KDTRACE_HOOKS   # kernel DTrace hooks
     options         MODULAR
-    
 
-You also need to build distribution with the options `MKDTRACE=yes` and `MKCTF=yes`.
+Optionally:
+    options         INSECURE   # permit modules to loaded from user space once system has gone multiuser and securelevel has been raised.
 
-##  Running hello world 
+A Distribution needs to be built with the options `MKDTRACE=yes` and `MKCTF=yes`, this is taken care of automatically and doesn't need to be specified manually. The list of platforms it is applied to automatically is set in `src/share/mk/bsd.own.mk`
 
-Load the solaris and dtrace modules, and the SDT (Statically Defined Tracing) and FBT (Function Boundary Tracing) modules: 
-    
-    modload solaris
-    modload dtrace
-    modload dtrace_sdt
-    modload dtrace_fbt
+Set the system to load the solaris and dtrace related modules in `/etc/modules.conf`, for a list of available modules, see `/stand/$MACHINE/$VERSION/modules/`
     
-
-Make the dtrace device node: 
+    solaris
+    dtrace
+    dtrace_sdt
+    dtrace_fbt
+    dtrace_lockstat
+    dtrace_profile
+    dtrace_syscall
     
-    cd /dev
-    sh MAKEDEV dtrace
+A `dtrace` device node is created automatically in `/dev/dtrace` when the modules are loaded into place.
     
-
 List the dtrace probes 
     
     dtrace -l
@@ -81,10 +79,9 @@
         .
     29140       proc                                                     lwp_start
     29141       proc                                                     lwp_exit
-    
 
-  
 
+##  Running hello world 
 
 Put the following into the file hello.d:
     

7.1
Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/ports.mdwn	26 Oct 2016 20:10:21 -0000	1.11
+++ wikisrc/ports.mdwn	15 Mar 2017 08:29:15 -0000	1.12
@@ -20,14 +20,14 @@
 
 [[!table data="""
 Port		|CPU		|Machines						|Latest Release
-[[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[evbarm]]	|arm		|ARM evaluation boards					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[evbmips]]	|mips		|MIPS-based evaluation boards				|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[evbppc]]	|powerpc	|PowerPC-based evaluation boards			|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[hpcarm]]	|arm		|StrongARM based Windows CE PDA machines		|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[i386]]	|i386		|32-bit x86-family generic machines ("PC clones")	|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[sparc64]]	|sparc		|Sun UltraSPARC (64-bit)				|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[xen]]		|i386, x86_64	|Xen Virtual Machine Monitor				|[7.0.2](http://www.netbsd.org/releases/formal-7/)
+[[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[evbarm]]	|arm		|ARM evaluation boards					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[evbmips]]	|mips		|MIPS-based evaluation boards				|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[evbppc]]	|powerpc	|PowerPC-based evaluation boards			|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[hpcarm]]	|arm		|StrongARM based Windows CE PDA machines		|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[i386]]	|i386		|32-bit x86-family generic machines ("PC clones")	|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[sparc64]]	|sparc		|Sun UltraSPARC (64-bit)				|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[xen]]		|i386, x86_64	|Xen Virtual Machine Monitor				|[7.1](http://www.netbsd.org/releases/formal-7/)
 """]]
 
 
@@ -44,55 +44,55 @@
 
 [[!table data="""
 Port		|CPU		|Machines								|Latest Release
-[[acorn32]]	|arm		|Acorn RiscPC/A7000/NC and compatibles					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[algor]]	|mips		|Algorithmics MIPS evaluation boards					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[alpha]]	|alpha		|Digital Alpha (64-bit)							|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[amiga]]	|m68k		|Commodore Amiga, MacroSystem DraCo					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[amigappc]]	|powerpc	|PowerPC-based Amiga boards						|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[arc]]		|mips		|Machines following the Advanced RISC Computing spec			|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[atari]]	|m68k		|Atari TT030, Falcon, Hades						|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[bebox]]	|powerpc	|Be Inc's BeBox								|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[cats]]	|arm		|Chalice Technology's Strong Arm evaluation board			|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[cesfic]]	|m68k		|CES's FIC8234 VME processor board					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[cobalt]]	|mips		|Cobalt Networks' Microservers						|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[dreamcast]]	|[[sh3]]	|Sega Dreamcast game console						|[7.0.2](http://www.netbsd.org/releases/formal-7/)
+[[acorn32]]	|arm		|Acorn RiscPC/A7000/NC and compatibles					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[algor]]	|mips		|Algorithmics MIPS evaluation boards					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[alpha]]	|alpha		|Digital Alpha (64-bit)							|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[amiga]]	|m68k		|Commodore Amiga, MacroSystem DraCo					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[amigappc]]	|powerpc	|PowerPC-based Amiga boards						|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[arc]]		|mips		|Machines following the Advanced RISC Computing spec			|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[atari]]	|m68k		|Atari TT030, Falcon, Hades						|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[bebox]]	|powerpc	|Be Inc's BeBox								|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[cats]]	|arm		|Chalice Technology's Strong Arm evaluation board			|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[cesfic]]	|m68k		|CES's FIC8234 VME processor board					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[cobalt]]	|mips		|Cobalt Networks' Microservers						|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[dreamcast]]	|[[sh3]]	|Sega Dreamcast game console						|[7.1](http://www.netbsd.org/releases/formal-7/)
 [[epoc32]]	|arm		|32bit PSION EPOC PDA							|none
-[[emips]]	|mips		|Machines based on "Extensible MIPS"					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[evbsh3]]	|[[sh3]]	|Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs	|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[ews4800mips]]	|mips		|NEC's MIPS based EWS4800 workstations					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[hp300]]	|m68k		|Hewlett-Packard 9000/300 and 400 series				|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[hppa]]	|hppa		|Hewlett-Packard 9000/700 series					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[hpcmips]]	|mips		|MIPS based Windows CE PDA machines					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[hpcsh]]	|[[sh3]]	|Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines		|[7.0.2](http://www.netbsd.org/releases/formal-7/)
+[[emips]]	|mips		|Machines based on "Extensible MIPS"					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[evbsh3]]	|[[sh3]]	|Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs	|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[ews4800mips]]	|mips		|NEC's MIPS based EWS4800 workstations					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[hp300]]	|m68k		|Hewlett-Packard 9000/300 and 400 series				|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[hppa]]	|hppa		|Hewlett-Packard 9000/700 series					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[hpcmips]]	|mips		|MIPS based Windows CE PDA machines					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[hpcsh]]	|[[sh3]]	|Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines		|[7.1](http://www.netbsd.org/releases/formal-7/)
 [[ia64]]	|itanium	|Itanium family of processors						|none
-[[ibmnws]]	|powerpc	|IBM Network Station Series 1000					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[iyonix]]	|arm		|Iyonix ARM pc								|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[landisk]]	|[[sh3]]	|SH4 based NAS appliances by I-O DATA					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[luna68k]]	|m68k		|OMRON Tateisi Electronics' LUNA series					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[mac68k]]	|m68k		|Apple Macintosh							|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[macppc]]	|powerpc	|Apple Power Macintosh and clones					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[mipsco]]	|mips		|Mips family of workstations and servers				|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[mmeye]]	|[[sh3]]	|Brains' mmEye Multi Media Server					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[mvme68k]]	|m68k		|Motorola MVME 68k SBCs							|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[mvmeppc]]	|powerpc	|Motorola MVME PowerPC SBCs						|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[netwinder]]	|arm		|StrongARM based NetWinder machines					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[news68k]]	|arm		|Sony's m68k based "NET WORK STATION" series				|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[newsmips]]	|mips		|Sony's MIPS based "NET WORK STATION" series				|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[next68k]]	|m68k		|NeXT 68k 'black' hardware						|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[ofppc]]	|powerpc	|Generic OpenFirmware compliant PowerPC machines			|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[pmax]]	|mips		|Digital MIPS-based DECstations and DECsystems				|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[prep]]	|powerpc	|PReP (PowerPC Reference Platform) and CHRP machines			|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[rs6000]]	|powerpc	|MCA-based IBM RS/6000 workstations					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[sandpoint]]	|powerpc	|Motorola Sandpoint reference platform					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[sbmips]]	|mips		|Broadcom SiByte evaluation boards					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[sgimips]]	|mips		|Silicon Graphics' MIPS-based workstations				|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[shark]]	|arm		|Digital DNARD ("shark")						|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[sparc]]	|sparc		|Sun SPARC (32-bit)							|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[sun2]]	|m68k		|Sun 2									|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[sun3]]	|m68k		|Sun 3 and 3x								|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[vax]]		|vax		|Digital VAX								|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[x68k]]	|m68k		|Sharp X680x0 series							|[7.0.2](http://www.netbsd.org/releases/formal-7/)
-[[zaurus]]	|arm		|Sharp C7x0/C860/C1000/C3x00 series PDA					|[7.0.2](http://www.netbsd.org/releases/formal-7/)
+[[ibmnws]]	|powerpc	|IBM Network Station Series 1000					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[iyonix]]	|arm		|Iyonix ARM pc								|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[landisk]]	|[[sh3]]	|SH4 based NAS appliances by I-O DATA					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[luna68k]]	|m68k		|OMRON Tateisi Electronics' LUNA series					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[mac68k]]	|m68k		|Apple Macintosh							|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[macppc]]	|powerpc	|Apple Power Macintosh and clones					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[mipsco]]	|mips		|Mips family of workstations and servers				|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[mmeye]]	|[[sh3]]	|Brains' mmEye Multi Media Server					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[mvme68k]]	|m68k		|Motorola MVME 68k SBCs							|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[mvmeppc]]	|powerpc	|Motorola MVME PowerPC SBCs						|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[netwinder]]	|arm		|StrongARM based NetWinder machines					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[news68k]]	|arm		|Sony's m68k based "NET WORK STATION" series				|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[newsmips]]	|mips		|Sony's MIPS based "NET WORK STATION" series				|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[next68k]]	|m68k		|NeXT 68k 'black' hardware						|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[ofppc]]	|powerpc	|Generic OpenFirmware compliant PowerPC machines			|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[pmax]]	|mips		|Digital MIPS-based DECstations and DECsystems				|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[prep]]	|powerpc	|PReP (PowerPC Reference Platform) and CHRP machines			|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[rs6000]]	|powerpc	|MCA-based IBM RS/6000 workstations					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[sandpoint]]	|powerpc	|Motorola Sandpoint reference platform					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[sbmips]]	|mips		|Broadcom SiByte evaluation boards					|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[sgimips]]	|mips		|Silicon Graphics' MIPS-based workstations				|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[shark]]	|arm		|Digital DNARD ("shark")						|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[sparc]]	|sparc		|Sun SPARC (32-bit)							|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[sun2]]	|m68k		|Sun 2									|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[sun3]]	|m68k		|Sun 3 and 3x								|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[vax]]		|vax		|Digital VAX								|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[x68k]]	|m68k		|Sharp X680x0 series							|[7.1](http://www.netbsd.org/releases/formal-7/)
+[[zaurus]]	|arm		|Sharp C7x0/C860/C1000/C3x00 series PDA					|[7.1](http://www.netbsd.org/releases/formal-7/)
 """]]
 
 
Index: wikisrc/ports/acorn26.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn26.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/ports/acorn26.mdwn	26 Oct 2016 20:16:33 -0000	1.11
+++ wikisrc/ports/acorn26.mdwn	15 Mar 2017 08:29:15 -0000	1.12
@@ -1,6 +1,6 @@
 [[!template id=port
 port="acorn26"
-cur_rel="7.0.2"
+cur_rel="7.1"
 future_rel="8.0"
 pkg_rel="6.1"
 changes_cur="7.0"
Index: wikisrc/ports/acorn32.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn32.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/ports/acorn32.mdwn	26 Oct 2016 20:16:33 -0000	1.13
+++ wikisrc/ports/acorn32.mdwn	15 Mar 2017 08:29:15 -0000	1.14
@@ -1,6 +1,6 @@
 [[!template id=port
 port="acorn32"
-cur_rel="7.0.2"
+cur_rel="7.1"
 future_rel="8.0"
 pkg_rel="6.1"
 changes_cur="7.0"
Index: wikisrc/ports/algor.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/algor.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/ports/algor.mdwn	13 Jan 2017 16:06:02 -0000	1.12
+++ wikisrc/ports/algor.mdwn	15 Mar 2017 08:29:15 -0000	1.13
@@ -1,6 +1,6 @@
 [[!template id=port
 port="algor"
-cur_rel="7.0.2"
+cur_rel="7.1"
 future_rel="8.0"
 pkg_rel="6.0"
 changes_cur="7.0"
Index: wikisrc/ports/alpha.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/alpha.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/ports/alpha.mdwn	26 Oct 2016 20:16:33 -0000	1.11
+++ wikisrc/ports/alpha.mdwn	15 Mar 2017 08:29:15 -0000	1.12
@@ -1,6 +1,6 @@
 [[!template id=port
 port="alpha"
-cur_rel="7.0.2"
+cur_rel="7.1"
 pkg_rel="7.0"
 future_rel="8.0"
 changes_cur="7.0"
Index: wikisrc/ports/amd64.mdwn
===================================================================

(Diff truncated)
Move AsiaBSDCon 2017 to past events
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- wikisrc/events.mdwn	21 Feb 2017 09:01:23 -0000	1.43
+++ wikisrc/events.mdwn	13 Mar 2017 10:33:49 -0000	1.44
@@ -7,19 +7,6 @@
 
 Future Events
 -------------
-### `Mar 2017` - AsiaBSDCon 2017
-
-*March 9 - 12, Tokyo University of Science, Tokyo, Japan*
-
-[AsiaBSDCon](https://2017.asiabsdcon.org/) is a
-conference for users and developers on BSD based systems.
-The conference is for anyone developing, deploying and using systems
-based on FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Darwin, and MacOS X.
-AsiaBSDCon is a technical conference and aims to collect the best
-technical papers and presentations available to ensure that the latest
-developments in our open source community are shared with the widest
-possible audience.
-
 ### `Jun 2017` - BSDCAN 2017, Ottawa, Canada
 
 *June 7 - 10, Ottawa, Canada*
@@ -47,6 +34,19 @@
 
 Past Events
 -----------
+### `Mar 2017` - AsiaBSDCon 2017
+
+*March 9 - 12, Tokyo University of Science, Tokyo, Japan*
+
+[AsiaBSDCon](https://2017.asiabsdcon.org/) was a
+conference for users and developers on BSD based systems.
+The conference was for anyone developing, deploying and using systems
+based on FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Darwin, and MacOS X.
+AsiaBSDCon was a technical conference and aimed to collect the best
+technical papers and presentations available to ensure that the latest
+developments in our open source community were shared with the widest
+possible audience.
+
 
 ### `Feb 2017` - FOSDEM 2017 Brussels, Belgium
 

Add maekawa@
Index: wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	9 Mar 2017 02:00:28 -0000	1.9
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	10 Mar 2017 00:04:12 -0000	1.10
@@ -12,6 +12,7 @@
 [[!table data="""
 First Last | `login@` | comment(s)
 Abhinav Upadhyay | `abhinav` |
+Masahide MAEKAWA | `maekawa` |
 Masanobu SAITOH | `msaitoh` |
 William J. Coldwell | `billc` |
 Makoto Fujiwara | `mef` |

Update Kazuya Goda's presentation.
Index: wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	9 Mar 2017 02:22:53 -0000	1.8
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	9 Mar 2017 08:33:13 -0000	1.9
@@ -22,7 +22,7 @@
 Name						|Title								|Time		|Notes
 Makoto Fujiwara(mef@n.o)                        |[check-update](http://www.ki.nu/~makoto/mef/20170310/) -- pkgsrc freshness --  | 10-15 minutes    |
 Makoto Fujiwara(mef@n.o)                        |How-To-Update pkg of my machine -- my peculiar way --          | 10-15 minutes    |
-Kazuya Goda                                     |TBD (OpenFlow switch, rump)					| 20 minutes       |
+Kazuya Goda                                     |What's the best practice for implementation of rumpclient?	| 20 minutes       |
 Abhinav Upadhyay                                |TBD (Updates on man-k.org)					| 10-15 minutes    |
 Abhinav Upadhyay                                |TBD (new implementation for spell(1))				| 15-20 minutes    |
 """]]

Added a comment: I'll join after OSC2017tokyospring.
--- /dev/null	2017-03-09 07:16:00.000000000 +0000
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF/comment_1_cc0bea24bebbae74140352791b7263d4._comment	2017-03-09 07:16:48.000000000 +0000
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="jun"
+ subject="I'll join after OSC2017tokyospring."
+ date="2017-03-09T07:16:30Z"
+ content="""
+docs:
+http://www.soum.co.jp/~jun/OSC2017tokyospring.pdf
+http://www.soum.co.jp/~jun/asiabsdcon2017.pdf
+"""]]

blymn wrote that it's been done, but didn't say who, assume himself
Index: wikisrc/projects/project/live-upgrade.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/live-upgrade.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/live-upgrade.mdwn	20 Feb 2015 17:12:46 -0000	1.5
+++ wikisrc/projects/project/live-upgrade.mdwn	9 Mar 2017 06:35:39 -0000	1.6
@@ -9,6 +9,9 @@
 mentors="""
 [Brett Lymn](mailto:blymn@NetBSD.org)
 """
+done_by="""
+[Brett Lymn](mailto:blymn@NetBSD.org)
+"""
 
 category="userland"
 difficulty="easy"

Add venue info.
Index: wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	8 Mar 2017 04:42:42 -0000	1.7
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	9 Mar 2017 02:22:53 -0000	1.8
@@ -7,11 +7,15 @@
 * Let's run a ~~Net~~BSD BoF on AsiaBSDCon2017.
 * All BSD speakers are welcome (No AsiaBSDCon registration is required).
 Please contact to jun@ or msaitoh@ if you'd like to give a talk.
-* Day 2: IIJ 2017/3/10(Friday)
+* Day & time: 2017/3/10(Friday)
   * 19:00-21:30(JST)
   * 10:00-12:30(UTC)
   * 05:00-07:30(EST)
   * 02:00-04:30(PST)
+* Venue:
+  * IIJ meeting room on 13th floor. [Iidabashi Grand Bloom, 2-10-2 Fujimi, Chiyoda-ku, Tokyo.](http://www.iij.ad.jp/en/company/about/map/head-office.html)
+  * [Route from the Morito Memorial Hall to Iidabashi Grand Bloom](https://goo.gl/maps/4ZgD8UX7UL12)
+  * There is a Reception desk on the second floor. Take a name tag of guest from a stuff. Wait to open a security gate by a staff. Take a evelator to 13th floor. When you leave, DON'T FORGET TO RETURN YOUR NAME TAG.
 * Live streaming URL: [https://www.youtube.com/watch?v=WflkqTU5BvQ](https://www.youtube.com/watch?v=WflkqTU5BvQ)
 
 [[!table data="""

Add info about Room B.
Index: wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	8 Mar 2017 04:24:21 -0000	1.8
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	9 Mar 2017 02:00:28 -0000	1.9
@@ -5,7 +5,7 @@
 
 * The NetBSD developer summit at AsiaBSDCon 2017 will be held on Friday,
 14:00-17:00(JST) 05:00-08:00(UTC). (TBD)
-* ROOM B
+* ROOM B. It's on the second floor of the conference venue. (no eating or drinking)
 
 ## Planning to attend?
 

Add Live streaming URL.
Index: wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	8 Mar 2017 03:31:16 -0000	1.6
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	8 Mar 2017 04:42:42 -0000	1.7
@@ -12,7 +12,7 @@
   * 10:00-12:30(UTC)
   * 05:00-07:30(EST)
   * 02:00-04:30(PST)
-* Live streaming URL: TBD
+* Live streaming URL: [https://www.youtube.com/watch?v=WflkqTU5BvQ](https://www.youtube.com/watch?v=WflkqTU5BvQ)
 
 [[!table data="""
 Name						|Title								|Time		|Notes

- Change meeting time (14:00-17:00(JST) 05:00-08:00(UTC)(TBD))
- Room B
- s/WIP session/Project Updates Session/
Index: wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	8 Mar 2017 00:34:06 -0000	1.7
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	8 Mar 2017 04:24:21 -0000	1.8
@@ -4,8 +4,8 @@
 ## Details
 
 * The NetBSD developer summit at AsiaBSDCon 2017 will be held on Friday,
-10:00-16:30(JST) 01:00-07:30(UTC). (TBD)
-* ROOM XXX
+14:00-17:00(JST) 05:00-08:00(UTC). (TBD)
+* ROOM B
 
 ## Planning to attend?
 
@@ -36,6 +36,6 @@
 """]]
 
 ## Discussions
-* about WIP session's presentation.
+* about Project Updates Session's presentation.
 
 ## Varia

Add two talks by abhinav@
Index: wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	7 Mar 2017 15:15:06 -0000	1.5
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	8 Mar 2017 03:31:16 -0000	1.6
@@ -16,9 +16,11 @@
 
 [[!table data="""
 Name						|Title								|Time		|Notes
-Makoto Fujiwara(mef@n.o)                        |[check-update](http://www.ki.nu/~makoto/mef/20170310/) -- pkgsrc freshness --                            | 10-15 minutes    |
+Makoto Fujiwara(mef@n.o)                        |[check-update](http://www.ki.nu/~makoto/mef/20170310/) -- pkgsrc freshness --  | 10-15 minutes    |
 Makoto Fujiwara(mef@n.o)                        |How-To-Update pkg of my machine -- my peculiar way --          | 10-15 minutes    |
 Kazuya Goda                                     |TBD (OpenFlow switch, rump)					| 20 minutes       |
+Abhinav Upadhyay                                |TBD (Updates on man-k.org)					| 10-15 minutes    |
+Abhinav Upadhyay                                |TBD (new implementation for spell(1))				| 15-20 minutes    |
 """]]
 
 # Dinner

Add me
Index: wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	7 Mar 2017 07:09:31 -0000	1.6
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	8 Mar 2017 00:34:06 -0000	1.7
@@ -22,6 +22,7 @@
 Kimihiro NONAKA | `nonaka` |
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |
+Bernd Ernesti | `veego` |
 """]]
 
 

Adding link to mef material
Index: wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	3 Mar 2017 13:46:45 -0000	1.4
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	7 Mar 2017 15:15:06 -0000	1.5
@@ -16,7 +16,7 @@
 
 [[!table data="""
 Name						|Title								|Time		|Notes
-Makoto Fujiwara(mef@n.o)                        |check-update -- pkgsrc freshness --                            | 10-15 minutes    |
+Makoto Fujiwara(mef@n.o)                        |[check-update](http://www.ki.nu/~makoto/mef/20170310/) -- pkgsrc freshness --                            | 10-15 minutes    |
 Makoto Fujiwara(mef@n.o)                        |How-To-Update pkg of my machine -- my peculiar way --          | 10-15 minutes    |
 Kazuya Goda                                     |TBD (OpenFlow switch, rump)					| 20 minutes       |
 """]]

add some people
Index: wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	6 Mar 2017 01:41:37 -0000	1.5
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	7 Mar 2017 07:09:31 -0000	1.6
@@ -17,6 +17,11 @@
 Makoto Fujiwara | `mef` |
 Rin Okuyama | `rin` |
 Pierre Pronchery | `khorben` |
+Hikaru Abe | `hikaru` | join later
+Kengo Nakahara | `knakahara` |
+Kimihiro NONAKA | `nonaka` |
+Ryota Ozaki | `ozaki-r` |
+Ryo Shimizu | `ryo` |
 """]]
 
 

Add libudev-dev.
Index: wikisrc/pkgsrc/how_to_use_pkgsrc_on_linux.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/how_to_use_pkgsrc_on_linux.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/pkgsrc/how_to_use_pkgsrc_on_linux.mdwn	6 Mar 2017 21:55:47 -0000	1.7
+++ wikisrc/pkgsrc/how_to_use_pkgsrc_on_linux.mdwn	6 Mar 2017 22:05:53 -0000	1.8
@@ -18,6 +18,7 @@
 * libncurses-devel
 * zlib and zlib-devel
 * openssl-devel (optional but required for some packages) 
+* libudev-dev (optional but required for some packages)
 
 The names may vary, depending on what Linux distribution you are using. Also be mindful of the platform you are using (eg. i686 vs. x86_64 - some have different pre-required packages). Also note that some very basic tools such as file, patch, sed, and others are required, as well.
 

Switch link to use cdn for README.Linux.
Switch lable for documentation to pkgsrc guide.
Correct packages name for ncurses headers on Debian.
Typo.
Index: wikisrc/pkgsrc/how_to_use_pkgsrc_on_linux.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/how_to_use_pkgsrc_on_linux.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/pkgsrc/how_to_use_pkgsrc_on_linux.mdwn	8 Feb 2013 05:22:47 -0000	1.6
+++ wikisrc/pkgsrc/how_to_use_pkgsrc_on_linux.mdwn	6 Mar 2017 21:55:47 -0000	1.7
@@ -6,9 +6,10 @@
 
 #See
 
-[Documentation](http://www.netbsd.org/docs/pkgsrc/)
-[Linux-specific documentation](http://www.netbsd.org/docs/pkgsrc/platforms.html#linux)
-[README.Linux](ftp://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Linux)
+[README.Linux](http://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/bootstrap/README.Linux)
+
+[pkgsrc guide](http://www.netbsd.org/docs/pkgsrc/)
+
 #Software requirements
 
 Before you can use pkgsrc, you may need a few packages installed on your Linux system upfront.
@@ -61,4 +62,4 @@
 
 Then install the libncurses-dev package
 
-On an RPM based system this might be via 'yum install ncurses-devel', and on a debia/ubuntu system 'apt-get install ncurses5-dev' 
+On an RPM based system this might be via 'yum install ncurses-devel', and on a Debian/Ubuntu system 'apt-get install libncurses5-dev' 

Add myself
Index: wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	4 Mar 2017 05:56:10 -0000	1.4
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	6 Mar 2017 01:41:37 -0000	1.5
@@ -16,6 +16,7 @@
 William J. Coldwell | `billc` |
 Makoto Fujiwara | `mef` |
 Rin Okuyama | `rin` |
+Pierre Pronchery | `khorben` |
 """]]
 
 

Document checkmirrors.pl update procedure
Index: wikisrc/releng/release-prep.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/release-prep.mdwn,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- wikisrc/releng/release-prep.mdwn	21 Jun 2016 16:14:36 -0000	1.35
+++ wikisrc/releng/release-prep.mdwn	4 Mar 2017 16:20:17 -0000	1.36
@@ -165,7 +165,10 @@
 
 16. Update <code>/pub/NetBSD/README</code> to mention the new release
 
-17. Announce the release on netbsd-announce@ and the blog.
+17. Update <code>localsrc/admin/mirrors/checkmirrors.pl</code> `$oldest` and
+    `$latest` variables as needed
+
+18. Announce the release on netbsd-announce@ and the blog.
 
 ============ 
 

Add rin@ as NetBSD summit attendee
Index: wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	3 Mar 2017 06:31:54 -0000	1.3
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	4 Mar 2017 05:56:10 -0000	1.4
@@ -15,6 +15,7 @@
 Masanobu SAITOH | `msaitoh` |
 William J. Coldwell | `billc` |
 Makoto Fujiwara | `mef` |
+Rin Okuyama | `rin` |
 """]]
 
 

For NetBSD BoF in AsiaBSDCon 2017, no AsiaBSDCon registration is required.
Index: wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	3 Mar 2017 09:44:21 -0000	1.3
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	3 Mar 2017 13:46:45 -0000	1.4
@@ -5,7 +5,8 @@
 # ~~Net~~BSD BoF 2017
 ------------------------------------------------------
 * Let's run a ~~Net~~BSD BoF on AsiaBSDCon2017.
-* All BSD speakers are welcome. Please contact to jun@ or msaitoh@ if you'd like to give a talk.
+* All BSD speakers are welcome (No AsiaBSDCon registration is required).
+Please contact to jun@ or msaitoh@ if you'd like to give a talk.
 * Day 2: IIJ 2017/3/10(Friday)
   * 19:00-21:30(JST)
   * 10:00-12:30(UTC)

Add Kazuya Goda's presentation (TBD (OpenFlow switch, rump)).
Index: wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	3 Mar 2017 07:14:52 -0000	1.2
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	3 Mar 2017 09:44:21 -0000	1.3
@@ -17,6 +17,7 @@
 Name						|Title								|Time		|Notes
 Makoto Fujiwara(mef@n.o)                        |check-update -- pkgsrc freshness --                            | 10-15 minutes    |
 Makoto Fujiwara(mef@n.o)                        |How-To-Update pkg of my machine -- my peculiar way --          | 10-15 minutes    |
+Kazuya Goda                                     |TBD (OpenFlow switch, rump)					| 20 minutes       |
 """]]
 
 # Dinner

Add mef@'s two presentations.
Index: wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	13 Feb 2017 06:29:54 -0000	1.1
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	3 Mar 2017 07:14:52 -0000	1.2
@@ -15,7 +15,8 @@
 
 [[!table data="""
 Name						|Title								|Time		|Notes
-XXX                                             |YYY                                                            | ZZ minutes    |
+Makoto Fujiwara(mef@n.o)                        |check-update -- pkgsrc freshness --                            | 10-15 minutes    |
+Makoto Fujiwara(mef@n.o)                        |How-To-Update pkg of my machine -- my peculiar way --          | 10-15 minutes    |
 """]]
 
 # Dinner

Extend self introduction to 10 minutes for person who will be the first time
to attend AsiaBSDCon's NetBSD developer summit.
Index: wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	3 Mar 2017 06:25:31 -0000	1.2
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	3 Mar 2017 06:31:54 -0000	1.3
@@ -22,7 +22,7 @@
 
 [[!table data="""
 Speaker  |Title
-`all` | Self introduction (5minutes in each person)
+`all` | Self introduction (5 minutes in each person (10 minutes for new person)).
 `msaitoh@` | Annual summary of IIJ's work.
 `login@` |_Very Interesting Thing_
 """]]

Add some people
Index: wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	13 Feb 2017 06:29:54 -0000	1.1
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	3 Mar 2017 06:25:31 -0000	1.2
@@ -11,7 +11,10 @@
 
 [[!table data="""
 First Last | `login@` | comment(s)
+Abhinav Upadhyay | `abhinav` |
 Masanobu SAITOH | `msaitoh` |
+William J. Coldwell | `billc` |
+Makoto Fujiwara | `mef` |
 """]]
 
 

Use pkg template to refer to misc/py-anita
Index: wikisrc/projects/project/performance_regress.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/performance_regress.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/performance_regress.mdwn	1 Mar 2017 11:07:43 -0000	1.2
+++ wikisrc/projects/project/performance_regress.mdwn	1 Mar 2017 11:10:13 -0000	1.3
@@ -25,6 +25,7 @@
 > Insert good performance testsuite examples here
 
 It would be nice to easily test commits between particular dates. Automated
-runs could be implemented with the help of py-anita.
+runs could be implemented with the help of
+[[!template id=pkg category="misc" name="py-anita"]].
 """
 ]]

Fix markdown syntax (lists needs to stay in their paragraph (with a newline
before and after it))
Index: wikisrc/projects/project/performance_regress.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/performance_regress.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/performance_regress.mdwn	1 Mar 2017 01:45:54 -0000	1.1
+++ wikisrc/projects/project/performance_regress.mdwn	1 Mar 2017 11:07:43 -0000	1.2
@@ -17,6 +17,7 @@
 systems so we can identify points for improvement.
 
 It would be good to test for specific cases as well, such as:
+
  * Network operation with a packet filter in use
  * Typical disk workload
  * Performance of a multi-threaded program

mwdn->mdwn
--- /dev/null	2017-03-01 01:41:23.000000000 +0000
+++ wikisrc/projects/project/performance_regress.mdwn	2017-03-01 01:46:08.000000000 +0000
@@ -0,0 +1,29 @@
+[[!template id=project
+
+title="Performance regression testing"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+category="userland"
+difficulty="easy"
+
+description="""
+Subtle changes in NetBSD may carry a significant performance penalty.
+Having a realistic performance test for various areas will allow us to
+find offending commits.
+Ideally, it would be possible to run the same tests on other operating
+systems so we can identify points for improvement.
+
+It would be good to test for specific cases as well, such as:
+ * Network operation with a packet filter in use
+ * Typical disk workload
+ * Performance of a multi-threaded program
+
+> Insert good performance testsuite examples here
+
+It would be nice to easily test commits between particular dates. Automated
+runs could be implemented with the help of py-anita.
+"""
+]]
--- wikisrc/projects/project/performance_regress.mwdn	2017-03-01 01:46:08.000000000 +0000
+++ /dev/null	2017-03-01 01:41:23.000000000 +0000
@@ -1,29 +0,0 @@
-[[!template id=project
-
-title="Performance regression testing"
-
-contact="""
-[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
-"""
-
-category="userland"
-difficulty="easy"
-
-description="""
-Subtle changes in NetBSD may carry a significant performance penalty.
-Having a realistic performance test for various areas will allow us to
-find offending commits.
-Ideally, it would be possible to run the same tests on other operating
-systems so we can identify points for improvement.
-
-It would be good to test for specific cases as well, such as:
- * Network operation with a packet filter in use
- * Typical disk workload
- * Performance of a multi-threaded program
-
-> Insert good performance testsuite examples here
-
-It would be nice to easily test commits between particular dates. Automated
-runs could be implemented with the help of py-anita.
-"""
-]]

Add project idea for performance regress testing.
I think it's appropriate for GSoC.
--- /dev/null	2017-03-01 01:41:23.000000000 +0000
+++ wikisrc/projects/project/performance_regress.mwdn	2017-03-01 01:42:20.000000000 +0000
@@ -0,0 +1,29 @@
+[[!template id=project
+
+title="Performance regression testing"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+category="userland"
+difficulty="easy"
+
+description="""
+Subtle changes in NetBSD may carry a significant performance penalty.
+Having a realistic performance test for various areas will allow us to
+find offending commits.
+Ideally, it would be possible to run the same tests on other operating
+systems so we can identify points for improvement.
+
+It would be good to test for specific cases as well, such as:
+ * Network operation with a packet filter in use
+ * Typical disk workload
+ * Performance of a multi-threaded program
+
+> Insert good performance testsuite examples here
+
+It would be nice to easily test commits between particular dates. Automated
+runs could be implemented with the help of py-anita.
+"""
+]]

Remove myself from the mentor list.
Index: wikisrc/projects/project/anita-vms.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/anita-vms.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/anita-vms.mdwn	8 Sep 2014 17:13:34 -0000	1.4
+++ wikisrc/projects/project/anita-vms.mdwn	28 Feb 2017 18:13:42 -0000	1.5
@@ -7,7 +7,6 @@
 """
 
 mentors="""
-[Andreas Gustafsson](mailto:gson@NetBSD.org)
 """
 
 category="userland"

Link to the pkg_comp 2.x tutorials and leave the pkg_comp 1.x instructions
as they currently are.
Index: wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn	12 Feb 2017 10:51:54 -0000	1.6
+++ wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn	23 Feb 2017 23:30:51 -0000	1.7
@@ -6,7 +6,15 @@
 
 Under *pkgsrc/pkgtools* you will find a great utility called *pkg_comp*. This script permits to handle packages manipulation in a *chroot*ed environment, thus keeping your real packages safe from any mistakes.
 
-Let's install *pkg_comp*
+For *pkg_comp* 2.x, located under *pkgsrc/pkgtools/pkg_comp*, follow these tutorials:
+
+* [Introducing pkg_comp 2.0 (and sandboxctl 1.0)](http://julio.meroh.net/2017/02/introducing-pkg_comp-2.0.html)
+* [Keeping NetBSD up-to-date with pkg_comp 2.0](http://julio.meroh.net/2017/02/pkg_comp-2.0-tutorial-netbsd.html)
+* [Easy pkgsrc on macOS with pkg_comp 2.0](http://julio.meroh.net/2017/02/pkg_comp-2.0-tutorial-macos.html)
+
+For *pkg_comp* 1.x, located under *pkgsrc/pkgtools/pkg_comp1*, continue reading this page.
+
+Let's install *pkg_comp 1.x*:
 
 	# cd /usr/pkgsrc/pkgtools/pkg_comp1
 	# make install clean

Instead of referring to FreeBSD and OpenBSD ports add a reference to
wip/chromium package and its TODO file.
Index: wikisrc/projects/project/pkgsrc-chromium.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc-chromium.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/pkgsrc-chromium.mdwn	15 Feb 2016 22:57:22 -0000	1.3
+++ wikisrc/projects/project/pkgsrc-chromium.mdwn	23 Feb 2017 15:31:02 -0000	1.4
@@ -16,9 +16,9 @@
 [Chromium web browser](http://www.chromium.org/Home) is open source
 edition of Google Chrome.
 
-A good starting point can be the www/chromium package available in
-[FreeBSD Ports](https://svnweb.freebsd.org/ports/head/www/chromium/)
-and
-[OpenBSD Ports](http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/chromium/).
+Currently Chromium is present in [pkgsrc-wip](https://www.pkgsrc.org/wip/) as
+[[!template id=pkg category="wip" name="chromium"]]. Please see
+[wip/chromium/TODO](https://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git;a=blob_plain;f=chromium/TODO;hb=HEAD)
+for a TODO list about it.
 """
 ]]

Added a comment: NetBrowser
--- /dev/null	2017-02-23 05:10:01.000000000 +0000
+++ wikisrc/projects/project/pkgsrc-chromium/comment_1_934e3961b6ab5d13d8897ab49bdfbb38._comment	2017-02-23 05:11:28.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/GQ5YrGI3hZzMZ82jtEJdgIUwv3AqDstcTZQWjI0tt4DUcuMbpLZ49C7A7RrcesICn1WQf1g-#01938"
+ nickname="jaypatelani"
+ subject="NetBrowser"
+ date="2017-02-23T05:11:12Z"
+ content="""
+Community might take https://github.com/conformal/xombrero?files=1 and make NetBrowser.
+"""]]

Added a comment: Lumina DE
--- /dev/null	2017-02-23 05:00:36.000000000 +0000
+++ wikisrc/projects/project/desktop-infrastructure/comment_2_a3ac0c57d5235df43377e255b387b1f1._comment	2017-02-23 05:07:54.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/GQ5YrGI3hZzMZ82jtEJdgIUwv3AqDstcTZQWjI0tt4DUcuMbpLZ49C7A7RrcesICn1WQf1g-#01938"
+ nickname="jaypatelani"
+ subject="Lumina DE"
+ date="2017-02-23T05:07:39Z"
+ content="""
+Agreed. And Lumina doesn't rely on dbus.
+"""]]

Sort future events by ascending order similarly to htdocs/gallery/events.xml
(this will hopefully help in order to not miss any next NetBSD related events!)
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- wikisrc/events.mdwn	21 Feb 2017 08:57:52 -0000	1.42
+++ wikisrc/events.mdwn	21 Feb 2017 09:01:23 -0000	1.43
@@ -7,17 +7,18 @@
 
 Future Events
 -------------
-### `Sep 2017 - EuroBSDCon 2017 Paris, France` ###
+### `Mar 2017` - AsiaBSDCon 2017
 
-*September 21 - 24, 2017, Paris, France*
+*March 9 - 12, Tokyo University of Science, Tokyo, Japan*
 
-[EuroBSDCon](https://2017.eurobsdcon.org/) is the premier European
-conference on the open source BSD operating systems attracting
-about 250 highly skilled engineering professionals, software
-developers, computer science students and professors, and users
-from all over Europe and other parts of the world. The goal of
-EuroBSDcon is to exchange knowledge about the BSD operating systems,
-facilitate coordination and cooperation among users and developers.
+[AsiaBSDCon](https://2017.asiabsdcon.org/) is a
+conference for users and developers on BSD based systems.
+The conference is for anyone developing, deploying and using systems
+based on FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Darwin, and MacOS X.
+AsiaBSDCon is a technical conference and aims to collect the best
+technical papers and presentations available to ensure that the latest
+developments in our open source community are shared with the widest
+possible audience.
 
 ### `Jun 2017` - BSDCAN 2017, Ottawa, Canada
 
@@ -31,18 +32,17 @@
 [website](https://www.bsdcan.org/2017/)
 for details.
 
-### `Mar 2017` - AsiaBSDCon 2017
+### `Sep 2017 - EuroBSDCon 2017 Paris, France`
 
-*March 9 - 12, Tokyo University of Science, Tokyo, Japan*
+*September 21 - 24, 2017, Paris, France*
 
-[AsiaBSDCon](https://2017.asiabsdcon.org/) is a
-conference for users and developers on BSD based systems.
-The conference is for anyone developing, deploying and using systems
-based on FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Darwin, and MacOS X.
-AsiaBSDCon is a technical conference and aims to collect the best
-technical papers and presentations available to ensure that the latest
-developments in our open source community are shared with the widest
-possible audience.
+[EuroBSDCon](https://2017.eurobsdcon.org/) is the premier European
+conference on the open source BSD operating systems attracting
+about 250 highly skilled engineering professionals, software
+developers, computer science students and professors, and users
+from all over Europe and other parts of the world. The goal of
+EuroBSDcon is to exchange knowledge about the BSD operating systems,
+facilitate coordination and cooperation among users and developers.
 
 
 Past Events

Add EuroBSDCon 2017
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- wikisrc/events.mdwn	6 Feb 2017 09:40:08 -0000	1.41
+++ wikisrc/events.mdwn	21 Feb 2017 08:57:52 -0000	1.42
@@ -7,6 +7,18 @@
 
 Future Events
 -------------
+### `Sep 2017 - EuroBSDCon 2017 Paris, France` ###
+
+*September 21 - 24, 2017, Paris, France*
+
+[EuroBSDCon](https://2017.eurobsdcon.org/) is the premier European
+conference on the open source BSD operating systems attracting
+about 250 highly skilled engineering professionals, software
+developers, computer science students and professors, and users
+from all over Europe and other parts of the world. The goal of
+EuroBSDcon is to exchange knowledge about the BSD operating systems,
+facilitate coordination and cooperation among users and developers.
+
 ### `Jun 2017` - BSDCAN 2017, Ottawa, Canada
 
 *June 7 - 10, Ottawa, Canada*

Added a comment: /boot.cfg entry
--- /dev/null	2017-02-20 02:30:02.000000000 +0000
+++ wikisrc/tutorials/how_to_set_up_a_xen_dom0/comment_3_4869b54ac386c98c7ef8a6d3159d2315._comment	2017-02-20 02:31:10.000000000 +0000
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="schnoebe"
+ subject="/boot.cfg entry"
+ date="2017-02-20T02:30:54Z"
+ content="""
+I can't imagine the specified /boot.cfg entry, with a path going into /usr/pkg/... can really be found by boot.  All previous tutorials and how-to's specify copying .../xen*-kernel/xen.gz into the root directory.
+
+The number of users having problems following the advice on the boot.cfg entry suggests that /boot can't traverse the directory tree deep enough to find xen.gz, even assuming /usr/pkg is on the same filesystem as /.
+"""]]

Hopefully it's really fixed now...
Index: wikisrc/projects/project/valgrind.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/valgrind.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/project/valgrind.mdwn	19 Feb 2017 15:45:51 -0000	1.6
+++ wikisrc/projects/project/valgrind.mdwn	19 Feb 2017 15:47:17 -0000	1.7
@@ -14,7 +14,7 @@
 leakage.
 
 See also <http://valgrind.org> and
-[http://vg4nbsd.berlios.de](http://web.archive.org/web/20131216184750/http://vg4nbsd.berlios.de/]
+[http://vg4nbsd.berlios.de](http://web.archive.org/web/20131216184750/http://vg4nbsd.berlios.de/)
 for work in progress.
 """
 ]]

fix url archive link
Index: wikisrc/projects/project/valgrind.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/valgrind.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/valgrind.mdwn	15 Feb 2016 22:48:55 -0000	1.5
+++ wikisrc/projects/project/valgrind.mdwn	19 Feb 2017 15:45:51 -0000	1.6
@@ -14,7 +14,7 @@
 leakage.
 
 See also <http://valgrind.org> and
-[http://web.archive.org/web/20131216184750/http://vg4nbsd.berlios.de/](http://vg4nbsd.berlios.de)
+[http://vg4nbsd.berlios.de](http://web.archive.org/web/20131216184750/http://vg4nbsd.berlios.de/]
 for work in progress.
 """
 ]]

make the security warning bold
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:15:16 -0000	1.5
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:18:51 -0000	1.6
@@ -26,8 +26,7 @@
 
 5. ASan can be wrong about which function is faulting, if we're talking about functions internal to the library. Running it on a separate file or in GDB can be helpful. Worth trying if the failure doesn't make sense.
 
-Important note: ASan should not be run on production systems. [It can pose a
-security risk](http://www.openwall.com/lists/oss-security/2016/02/17/9).
+**Important note: ASan should not be run on production systems. [It can pose a security risk](http://www.openwall.com/lists/oss-security/2016/02/17/9).**
 
 ## Coverity ##
 

More markdown.
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:10:22 -0000	1.4
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:15:16 -0000	1.5
@@ -51,7 +51,7 @@
 - Library or other code you know well already
 - Drivers for hardware you actually own and can test
 
-Future ideas:
+## Future ideas: ##
 
 - GCC could be told to add ASan flags for all shared objects, making it easier to build world with those flags
 - We could run all of NetBSD with ASan for some real world tests.

oops, made the markdown worse.
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:08:58 -0000	1.3
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:10:22 -0000	1.4
@@ -44,6 +44,7 @@
 
 Some suggestions for things to focus on, as there are many defects
 reported:
+
 - Setuid programs
 - Anything kernel
 - Stuff that runs as root

More improve markdown. Mention that it can be wrong about the offending
function and that it's possible to run it in GDB.
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:06:15 -0000	1.2
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:08:58 -0000	1.3
@@ -2,31 +2,29 @@
 
 ## Address Sanitizer (+UBsan) (preliminary) ##
 
-ASan reports memory violations, and detects many off-by-ones. It seems
-to produce very high quality reports.
+ASan reports memory violations, and detects many off-by-ones. It seems to produce very high quality reports.
 
-It only needs to be compiled on the resulting binary[1]. It cannot compile
-static objects so requires some fiddling with makefiles to disable those.
+It only needs to be compiled on the resulting binary[1]. It cannot compile static objects so requires some fiddling with makefiles to disable those.
 
 I've been running it on netbsd tests in the following manner[2]:
 
     cd /usr/src/tests/lib/libc
     env USETOOLS=never MK_SSP=no HAVE_SSP=no CFLAGS="-fno-omit-frame-pointer -O0 -g -ggdb -U_FORTIFY_SOURCE -fsanitize=address -fsanitize=undefined" LDFLAGS="-lasan -lubsan" make -j20
 
-    env ASAN_OPTIONS=alloc_dealloc_mismatch=0 LD_PRELOAD="/usr/lib/libasan.so /usr/lib/libubsan.so" atf-run
+    env ASAN_OPTIONS=alloc_dealloc_mismatch=0 LD_PRELOAD="/usr/lib/libasan.so /usr/lib/libubsan.so" atf-run # [3]
 
-    sysctl -w security.pax.aslr.enabled=0 # [3]
+    sysctl -w security.pax.aslr.enabled=0 # [4]
 
 1. Seems like this is a cause of worse reports, as in-library functions
 are not intercepted.
 
 2. Not even close to canonical commands, should probably be improved.
 
-3. To workaround "Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly". An alternative is to LD_PRELOAD and LD_LIBRARY_PATH an entirely separate libc, ld.elf_so, etc.
+3. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself triggers a bug. Should have a look at it so this option doesn't need to be disabled.
 
-4. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself
-    triggers a bug. Should have a look at it so this option doesn't
-    need to be disabled.
+4. To workaround "Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly". An alternative is to LD_PRELOAD and LD_LIBRARY_PATH an entirely separate libc, ld.elf_so, etc.
+
+5. ASan can be wrong about which function is faulting, if we're talking about functions internal to the library. Running it on a separate file or in GDB can be helpful. Worth trying if the failure doesn't make sense.
 
 Important note: ASan should not be run on production systems. [It can pose a
 security risk](http://www.openwall.com/lists/oss-security/2016/02/17/9).

Improve markdown, mention conflict with ASLR.
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:01:14 -0000	1.1
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:06:15 -0000	1.2
@@ -15,12 +15,16 @@
 
     env ASAN_OPTIONS=alloc_dealloc_mismatch=0 LD_PRELOAD="/usr/lib/libasan.so /usr/lib/libubsan.so" atf-run
 
+    sysctl -w security.pax.aslr.enabled=0 # [3]
+
 1. Seems like this is a cause of worse reports, as in-library functions
 are not intercepted.
 
 2. Not even close to canonical commands, should probably be improved.
 
-3. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself
+3. To workaround "Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly". An alternative is to LD_PRELOAD and LD_LIBRARY_PATH an entirely separate libc, ld.elf_so, etc.
+
+4. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself
     triggers a bug. Should have a look at it so this option doesn't
     need to be disabled.
 
@@ -42,19 +46,15 @@
 
 Some suggestions for things to focus on, as there are many defects
 reported:
-
 - Setuid programs
 - Anything kernel
 - Stuff that runs as root
-
 - Library or other code you know well already
 - Drivers for hardware you actually own and can test
 
 Future ideas:
 
-- GCC could be told to add ASan flags for all shared objects, making
-  it easier to build world with those flags
+- GCC could be told to add ASan flags for all shared objects, making it easier to build world with those flags
 - We could run all of NetBSD with ASan for some real world tests.
-- ASan for kernel? (subr_kmem.c has some flags which do some of the
-  work, could it do more?)
+- ASan for kernel? (subr_kmem.c has some flags which do some of the work, could it do more?)
 - Fuzzers are cool.

Some info on how I've been using asan and coverity
(Not sure if this is sane markdown)
--- /dev/null	2017-02-16 00:00:33.000000000 +0000
+++ wikisrc/users/maya.mdwn	2017-02-16 00:01:28.000000000 +0000
@@ -0,0 +1,60 @@
+# Tips for using analyzers on NetBSD #
+
+## Address Sanitizer (+UBsan) (preliminary) ##
+
+ASan reports memory violations, and detects many off-by-ones. It seems
+to produce very high quality reports.
+
+It only needs to be compiled on the resulting binary[1]. It cannot compile
+static objects so requires some fiddling with makefiles to disable those.
+
+I've been running it on netbsd tests in the following manner[2]:
+
+    cd /usr/src/tests/lib/libc
+    env USETOOLS=never MK_SSP=no HAVE_SSP=no CFLAGS="-fno-omit-frame-pointer -O0 -g -ggdb -U_FORTIFY_SOURCE -fsanitize=address -fsanitize=undefined" LDFLAGS="-lasan -lubsan" make -j20
+
+    env ASAN_OPTIONS=alloc_dealloc_mismatch=0 LD_PRELOAD="/usr/lib/libasan.so /usr/lib/libubsan.so" atf-run
+
+1. Seems like this is a cause of worse reports, as in-library functions
+are not intercepted.
+
+2. Not even close to canonical commands, should probably be improved.
+
+3. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself
+    triggers a bug. Should have a look at it so this option doesn't
+    need to be disabled.
+
+Important note: ASan should not be run on production systems. [It can pose a
+security risk](http://www.openwall.com/lists/oss-security/2016/02/17/9).
+
+## Coverity ##
+
+Coverity is a static analyzer.
+
+You can see a part of its output in coverity-updates@, and a lot more
+if you go to the website (sign up with your netbsd email or poke someone
+for access).
+
+A lot of the reports are about strncpy/strcpy or in code that belongs
+to GCC (in the case of userland), you can tackle this by limiting
+results to a particular directory (click the folder icon). You can
+also sort by issue.
+
+Some suggestions for things to focus on, as there are many defects
+reported:
+
+- Setuid programs
+- Anything kernel
+- Stuff that runs as root
+
+- Library or other code you know well already
+- Drivers for hardware you actually own and can test
+
+Future ideas:
+
+- GCC could be told to add ASan flags for all shared objects, making
+  it easier to build world with those flags
+- We could run all of NetBSD with ASan for some real world tests.
+- ASan for kernel? (subr_kmem.c has some flags which do some of the
+  work, could it do more?)
+- Fuzzers are cool.

AsiaBSDCon 2017 NetBSD develoer summit and BoF.
--- /dev/null	2017-02-13 06:30:02.000000000 +0000
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	2017-02-13 06:30:10.000000000 +0000
@@ -0,0 +1,22 @@
+<!-- we are supposed to use all lowercase letters in the link, so set a proper title for the page: -->
+[[!meta title="AsiaBSDCon 2017 NetBSD BoF"]]
+
+
+# ~~Net~~BSD BoF 2017
+------------------------------------------------------
+* Let's run a ~~Net~~BSD BoF on AsiaBSDCon2017.
+* All BSD speakers are welcome. Please contact to jun@ or msaitoh@ if you'd like to give a talk.
+* Day 2: IIJ 2017/3/10(Friday)
+  * 19:00-21:30(JST)
+  * 10:00-12:30(UTC)
+  * 05:00-07:30(EST)
+  * 02:00-04:30(PST)
+* Live streaming URL: TBD
+
+[[!table data="""
+Name						|Title								|Time		|Notes
+XXX                                             |YYY                                                            | ZZ minutes    |
+"""]]
+
+# Dinner
+* After the BoF, we usually go to a bar or a restaurant near the venue.
--- /dev/null	2017-02-13 06:30:02.000000000 +0000
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	2017-02-13 06:30:10.000000000 +0000
@@ -0,0 +1,30 @@
+<!-- we are supposed to use all lowercase letters in the link, so set a proper title for the page: -->
+[[!meta title="AsiaBSDCon 2017 NetBSD Summit"]]
+
+## Details
+
+* The NetBSD developer summit at AsiaBSDCon 2017 will be held on Friday,
+10:00-16:30(JST) 01:00-07:30(UTC). (TBD)
+* ROOM XXX
+
+## Planning to attend?
+
+[[!table data="""
+First Last | `login@` | comment(s)
+Masanobu SAITOH | `msaitoh` |
+"""]]
+
+
+## Planning to present something?
+
+[[!table data="""
+Speaker  |Title
+`all` | Self introduction (5minutes in each person)
+`msaitoh@` | Annual summary of IIJ's work.
+`login@` |_Very Interesting Thing_
+"""]]
+
+## Discussions
+* about WIP session's presentation.
+
+## Varia

This tutorial is for pkg_comp 1.x, so refert to pkgtools/pkg_comp1.
Index: wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn	19 Jul 2014 04:03:21 -0000	1.5
+++ wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn	12 Feb 2017 10:51:54 -0000	1.6
@@ -8,7 +8,7 @@
 
 Let's install *pkg_comp*
 
-	# cd /usr/pkgsrc/pkgtools/pkg_comp
+	# cd /usr/pkgsrc/pkgtools/pkg_comp1
 	# make install clean
 
 Once done, we will create the *chroot*ed environment:

Mention future work in sysinst(8)
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:08:32 -0000	1.13
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:10:53 -0000	1.14
@@ -76,6 +76,8 @@
 
 It is also possible to boot a Xen DOM0 system with root filesystem encryption. However, Xen-enabled NetBSD kernels currently do not support loading modules at boot-time. The memory disk has to be placed directly inside the kernel instead (with [[!template id=man name="mdconfig" section="8"]] or a new kernel configuration).
 
+It should really be possible to install NetBSD this way with [[!template id=man name="sysinst" section="8"]]. Unfortunately this is not supported yet.
+
 References
 ----------
 

Clarify where cgdroot.kmod gets built
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:02:28 -0000	1.12
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:08:32 -0000	1.13
@@ -65,6 +65,8 @@
 src/distrib/amd64/kmod-cgdroot$ /path/to/tooldir/bin/nbmake-amd64
 """]]
 
+It will be found in `/path/to/objdir/distrib/amd64/kmod-cgdroot/cgdroot.kmod`.
+
 Caveats
 -------
 

s/eg/e.g./
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:00:40 -0000	1.11
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:02:28 -0000	1.12
@@ -70,7 +70,7 @@
 
 The biggest (known) issue with this setup occurs when firmware needs to be loaded early in the boot process (such as graphics drivers for the console). At the moment they need to be provided as part of the memory disk. Some network interfaces, of which some wireless devices in particular, also require loading firmware to work properly.
 
-This setup is not entirely safe against physical attacks. An attacker can modify the boot process to store the passphrase for later retrieval, or insert a backdoor while booting. To defend against such attacks, the bootloader, kernel and ramdisk all need to be signed and their integrity checked before booting (eg with [[!template id=man name="tpm" section="4"]]). Alternatively, it is possible to boot from a removable medium (eg USB stick), which can be protected against tampering attacks (eg secure storage, read-only volume...).
+This setup is not entirely safe against physical attacks. An attacker can modify the boot process to store the passphrase for later retrieval, or insert a backdoor while booting. To defend against such attacks, the bootloader, kernel and ramdisk all need to be signed and their integrity checked before booting (e.g. with [[!template id=man name="tpm" section="4"]]). Alternatively, it is possible to boot from a removable medium (e.g. USB stick), which can be protected against tampering attacks (e.g. secure storage, read-only volume...).
 
 It is also possible to boot a Xen DOM0 system with root filesystem encryption. However, Xen-enabled NetBSD kernels currently do not support loading modules at boot-time. The memory disk has to be placed directly inside the kernel instead (with [[!template id=man name="mdconfig" section="8"]] or a new kernel configuration).
 

Fix a link
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:55:36 -0000	1.10
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:00:40 -0000	1.11
@@ -29,7 +29,7 @@
 Obtaining the kernel module
 ---------------------------
 
-The `cgdroot.kmod` kernel module is part of the regular NetBSD releases since NetBSD 7.0. It can be found in the `<arch>/installation/miniroot` folder from the release. For instance, for the amd64 architecture on the German mirror for the 7.0.1 release, download it at (ftp://ftp.de.netbsd.org/pub/NetBSD/NetBSD-7.0.1/amd64/installation/miniroot/cgdroot.kmod).
+The `cgdroot.kmod` kernel module is part of the regular NetBSD releases since NetBSD 7.0. It can be found in the `<arch>/installation/miniroot` folder from the release. For instance, for the amd64 architecture on the German mirror for the 7.0.1 release, download it at [ftp.de.netbsd.org/pub/NetBSD/NetBSD-7.0.1/amd64/installation/miniroot/cgdroot.kmod](ftp://ftp.de.netbsd.org/pub/NetBSD/NetBSD-7.0.1/amd64/installation/miniroot/cgdroot.kmod).
 
 Configuring the kernel module
 -----------------------------

Link to the NetBSD Guide
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:54:56 -0000	1.9
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:55:36 -0000	1.10
@@ -5,6 +5,8 @@
 
 The mechanism described here still requires one unencrypted partition to boot from (typically `wd0a`). Full disk encryption would make it more difficult for an attacker to modify the unencrypted part of the disk to plant a backdoor. With only partial encryption, the original [[!template id=man name="cgdconfig" section="8"]] binary may be modified to send the passphrase away, allowing an attacker with a disk dump to recover the data.
 
+The NetBSD Guide contains [an entire section about CGD][2].
+
 The boot process
 ----------------
 
@@ -76,5 +78,7 @@
 ----------
 
 * [Full Disk Encryption with cgd (well, almost)][1]
+* [The cryptographic device driver (CGD)][2]
 
 [1]: https://mail-index.netbsd.org/current-users/2013/03/21/msg022311.html "Full Disk Encryption with cgd (well, almost)"
+[2]: http://www.netbsd.org/docs/guide/en/chap-cgd.html "The cryptographic device driver (CGD)"

Wording
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:42:44 -0000	1.8
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:54:56 -0000	1.9
@@ -3,16 +3,14 @@
 
 It is possible to run NetBSD with [complete root filesystem encryption][1], thanks to the `cgdroot.kmod` kernel module. It really is a memory disk (also knows as RAM disk) that is expected to be loaded in the kernel while booting. It is named after CGD, the "cryptographic device driver", which implements encryption for storage in the NetBSD kernel.
 
-Full disk encryption makes it more difficult for an attacker to modify the unencrypted part of the disk to plant a backdoor. With only partial encryption, the original [[!template id=man name="cgdconfig" section="8"]] binary may be modified to send the passphrase away, allowing an attacker with a disk dump to recover the data.
-
-The mechanism described here still requires one unencrypted partition to boot from (typically `wd0a`).
+The mechanism described here still requires one unencrypted partition to boot from (typically `wd0a`). Full disk encryption would make it more difficult for an attacker to modify the unencrypted part of the disk to plant a backdoor. With only partial encryption, the original [[!template id=man name="cgdconfig" section="8"]] binary may be modified to send the passphrase away, allowing an attacker with a disk dump to recover the data.
 
 The boot process
 ----------------
 
-Instead of booting normally the GENERIC kernel and using the root filesystem, a kernel module is loaded at boot-time containing a memory disk. This minimal filesystem image is then considered the actual root filesystem.
+Instead of booting the GENERIC kernel normally and using the root filesystem directly as usual, a special kernel module containing a memory disk is loaded at boot-time. This minimal filesystem image will then be the actual root filesystem, where the decryption process takes place.
 
-The boot partition on disk only needs to contain:
+The boot partition on disk needs to contain:
 
 * [[!template id=man name="boot" section="8"]], the second-stage bootloader
 * [[!template id=man name="boot.cfg" section="5"]], the configuration file for the bootloader (optional)

Try to clarify a bit more
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/security/cgdroot.mdwn	22 Jun 2016 09:08:50 -0000	1.7
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:42:44 -0000	1.8
@@ -1,7 +1,7 @@
 Root filesystem encryption
 ==========================
 
-It is possible to run NetBSD with [complete root filesystem encryption][1], thanks to the `cgdroot.kmod` kernel module. It really is a memory disk (also knows as RAM disk) that is expected to be loaded in the kernel while booting.
+It is possible to run NetBSD with [complete root filesystem encryption][1], thanks to the `cgdroot.kmod` kernel module. It really is a memory disk (also knows as RAM disk) that is expected to be loaded in the kernel while booting. It is named after CGD, the "cryptographic device driver", which implements encryption for storage in the NetBSD kernel.
 
 Full disk encryption makes it more difficult for an attacker to modify the unencrypted part of the disk to plant a backdoor. With only partial encryption, the original [[!template id=man name="cgdconfig" section="8"]] binary may be modified to send the passphrase away, allowing an attacker with a disk dump to recover the data.
 
@@ -18,7 +18,8 @@
 * [[!template id=man name="boot.cfg" section="5"]], the configuration file for the bootloader (optional)
 * a GENERIC kernel
 * the `cgdroot.kmod` kernel module
-* configuration and encryption key for the encrypted volume to start from (`cgd.conf`)
+* the configuration file for CGD, `cgd.conf`
+* the encryption key for the volume to start from, named after its partition (like `wd0f`)
 
 Once loaded the memory disk mounts the `wd0a` partition onto `/etc/cgd`, and asks for the encryption passphrase as usual (with [[!template id=man name="cgdconfig" section="8"]]). If successful, the `cgd0a` volume configured is mounted on `/altroot`, and [[!template id=man name="init" section="8"]] is told via [[!template id=man name="sysctl" section="7"]] to chroot into this volume before actually booting. The system then starts normally.
 

This was basically done for GSoC last year.
Index: wikisrc/projects/project/u-boot-pkgsrc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/u-boot-pkgsrc.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/u-boot-pkgsrc.mdwn	20 Feb 2015 16:38:57 -0000	1.2
+++ wikisrc/projects/project/u-boot-pkgsrc.mdwn	9 Feb 2017 15:43:39 -0000	1.3
@@ -13,6 +13,7 @@
 category="userland"
 difficulty="medium"
 duration="3 months"
+done_by="Joe Davis"
 
 description="""
 The U-Boot bootloader is being used by an increasing number of devices, including lots which run NetBSD.

Remove pkg_comp rewrite project proposal.
I have finally done this myself and should publish the new tool within the
next few weeks, so I don't want to waste potential GSoC students reading
this proposal.
Members: 
	projects/project/rewrite-pkg_comp.mdwn:1.3->1.4(DEAD) 

--- wikisrc/projects/project/rewrite-pkg_comp.mdwn	2017-02-09 15:19:44.000000000 +0000
+++ /dev/null	2017-02-09 15:16:00.000000000 +0000
@@ -1,37 +0,0 @@
-[[!template id=project
-
-title="Rewrite pkg_comp with portability as a major goal"
-
-contact="""
-[tech-pkg](mailto:tech-pkg@NetBSD.org)
-"""
-
-mentors="""
-[Julio Merino](mailto:jmmv@NetBSD.org), [Aleksej Saushev](mailto:asau@NetBSD.org)
-"""
-
-category="pkgsrc"
-difficulty="medium"
-duration="3 months"
-
-description="""
-pkg_comp is a shell script that allows building packages inside a sandbox in an automated manner. The goal is to allow the user to build packages in a controller manner and to provide a simple mechanism to build packages for a host running a specific NetBSD release (e.g building packages for NetBSD 5.x while running NetBSD-current).
-
-The [current version](http://www.netbsd.org/contrib/soc-projects.html) of pkg_comp is written as a pretty big shell script that has grown out of control. It is hard to maintain and hard to extend. And, more importantly, it is not portable at all.
-
-The goal of this project is to rewrite pkg_comp from scratch with portability being the main goal: it has to be possible to use the script in different Unix variants (including Mac OS X).
-
-The language of choice for the reimplementation will be Python. The code will be hosted outside of pkgsrc to be able to distribute it as a standalone tool.
-
-The following milestones should be accomplished:
-
-* Implement a "sandbox" library with an interface to programmatically create and manage a sandboxed file system. The structure of the sandbox has to be configurable through a template, and templates have to be provided for a few systems. The sandbox itself will be constructed either by unpacking tarballs with the system contents (such as the NetBSD distfiles), by null-mounting directories of the host file system, or both.
-* Implement a command-line frontend utility for the "sandbox" library. This tool is completely unaware of pkgsrc but will be really nice to have (and trivial to write, as all the juicy bits are in the library). Will be useful as part of server administration, as it will allow isolating services in a fairly easy manner.
-* Implement the "pkg_comp" application, building it on top of the "sandbox" module. It has to provide most of the current functionality, if not all. More specifically, these are a must: unattended builds of a predefined set of packages and use of libkver to override the system version.
-* Implement detailed unit tests for the modules and integration tests for the front-end tools. At this point, the former will most likely be implemented using JUnit and the latter will be implemented using ATF.
-
-As part of this project, the student will get familiar with pkgsrc, construction of sandboxes for different operating systems, unit testing, ATF and Python.
-"""
-]]
-
-[[!tag gsoc]]

Move FOSDEM 2017 to Past Events
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- wikisrc/events.mdwn	26 Dec 2016 16:24:57 -0000	1.40
+++ wikisrc/events.mdwn	6 Feb 2017 09:40:08 -0000	1.41
@@ -32,17 +32,21 @@
 developments in our open source community are shared with the widest
 possible audience.
 
+
+Past Events
+-----------
+
 ### `Feb 2017` - FOSDEM 2017 Brussels, Belgium
 
 *February 4 - 5, Brussels, Belgium*
 
-[FOSDEM](https://fosdem.org/2017/) is a
+[FOSDEM](https://fosdem.org/2017/) was a
 free event for software developers to meet, share ideas
 and collaborate. Every year, thousands of developers of
 free and open source software from all over the world gather
 at the event in Brussels.
 
-There is a special developer's room reserved for BSD licensed
+There was a special developer's room reserved for BSD licensed
 operating systems and their talks.
 
 Please see
@@ -50,9 +54,6 @@
 for details.
 
 
-Past Events
------------
-
 ### `Sep 2016` - EuroBSDCon 2016 Belgrade, Serbia
 
 *September 22 - 25, 2016, Belgrade Serbia*

Added a comment: Lots of useful info regarding NetBSD on RPI collected by Jun Ebihara
--- /dev/null	2017-02-04 20:33:38.000000000 +0000
+++ wikisrc/ports/evbarm/raspberry_pi/comment_19_82864947fcb8737650f36e90ed1ed9b8._comment	2017-02-04 20:35:44.000000000 +0000
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UM0fy451yPQ9iZSVKjtjNcPifA--#1f032"
+ nickname="Fredrik Pettai"
+ subject="Lots of useful info regarding NetBSD on RPI collected by Jun Ebihara"
+ date="2017-02-04T20:35:28Z"
+ content="""
+See Jun Ebihara's GitHub page where lots of stuff regarding NetBSD on RPI is collected:
+<https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README>
+"""]]

Fix broken links
Index: wikisrc/ports/sh3.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sh3.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/ports/sh3.mdwn	22 May 2015 02:41:35 -0000	1.4
+++ wikisrc/ports/sh3.mdwn	28 Jan 2017 05:06:59 -0000	1.5
@@ -17,9 +17,9 @@
     -   [7709A evaluation
         board](http://www.computex.co.jp/products/board/board.htm#7709a)
         ([Computex](http://www.computex.co.jp/))
-    -   [T-SH7706LAN](http://web.kyoto-inet.or.jp/people/takagaki/T-SH7706/T-SH7706.htm)
+    -   [T-SH7706LAN](http://www.itrinity.jp/products/tac_board/sh7706lan/sh7706_spec.html)
         ([TAC Inc.](http://www.tacinc.jp/))
-    -   [T-SH7706LSR](http://www.tacinc.jp/T-SH7706/T-SH7706LSR.htm)
+    -   [T-SH7706LSR](http://tacinc.jp/products/sh3-linux/t-7706lsr)
         ([TAC Inc.](http://www.tacinc.jp/))
 
 -   [NetBSD/evbsh3](../evbsh3/): SH4 chip evaluation boards

Make command invocation as block
Index: wikisrc/users/ryoon/how_to_update_www_firefox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/ryoon/how_to_update_www_firefox.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/users/ryoon/how_to_update_www_firefox.mdwn	22 Jan 2017 13:00:58 -0000	1.10
+++ wikisrc/users/ryoon/how_to_update_www_firefox.mdwn	22 Jan 2017 13:02:09 -0000	1.11
@@ -12,6 +12,7 @@
 
 You should follow "Working with the Unified Repo" section.
 In short, run:
+
 	$ hg clone https://hg.mozilla.org/mozilla-unified
 
 # Update trees to latest

Explain pkgsrc/www/firefox update instruction with recent example
Index: wikisrc/users/ryoon/how_to_update_www_firefox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/ryoon/how_to_update_www_firefox.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/users/ryoon/how_to_update_www_firefox.mdwn	19 Jun 2016 09:21:40 -0000	1.9
+++ wikisrc/users/ryoon/how_to_update_www_firefox.mdwn	22 Jan 2017 13:00:58 -0000	1.10
@@ -1,24 +1,21 @@
 [[!meta title="How to update pkgsrc/www/firefox"]]
 
-This article shows how to update pkgsrc/www/firefox package to latest release.
+This article shows you how to update pkgsrc/www/firefox package to latest
+release.
 You can use Mozilla's Mercurial (hg) repositories to track upstream changes.
 
-You should have pkgsrc/meta-pkgs/pkg_developer package.
+You should have pkgsrc/meta-pkgs/pkg_developer package
+and pkgsrc/devel/py-mercurial package.
 
 # Clone hg tree
-See <https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Source_Code/Mercurial>.
-
-You should follow "Using Bookmarks to Manage Multiple Repositories from a Single Clone" section.
+See <http://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/unifiedrepo.html>
 
+You should follow "Working with the Unified Repo" section.
+In short, run:
+	$ hg clone https://hg.mozilla.org/mozilla-unified
 
 # Update trees to latest
 
-	$ hg pull central
-	$ hg pull inbound
-	$ hg pull aurora
-	$ hg pull beta
-	$ hg pull release
-
 	$ hg update
 
 
@@ -26,19 +23,19 @@
 
 Find latest release.
 
-	$ hg tags|grep 46_
+	$ hg tags|grep 50_
 	(snip)
-	FIREFOX_46_0_1_RELEASE		341775:0b8492c110be
+	FIREFOX_50_1_0_RELEASE         359965:8612c3320053
 	(snip)
 
 Checkout the branch.
 
-	$ hg checkout FIREFOX_46_0_1_RELEASE
+	$ hg checkout FIREFOX_50_1_0_RELEASE
 
 Create named branch for applying pkgsrc patches
 
-	$ hg branch pkgsrc_firefox-46.0.1
-	$ hg commit -m "Create pkgsrc_firefox-46.0.1 branch for applying pkgsrc patches"
+	$ hg branch pkgsrc_firefox-50.1.0
+	$ hg commit -m "Create pkgsrc_firefox-50.1.0 branch for applying pkgsrc patches"
 
 Add .*\.orig$ to .hgignore, and commit this change
 
@@ -52,26 +49,26 @@
 	$ popd
 	$ cat /usr/pkgsrc/www/firefox/patches/patch-*|patch -p0
 	$ hg add ...(necessary files)
-	$ hg commit -m "Apply pkgsrc patches for firefox-46.0.1nb1"
+	$ hg commit -m "Apply pkgsrc patches for firefox-50.1.0nb3"
 
 
 # Checkout latest beta source, and create your branch
 
 Find latest branch.
 
-	$ hg tags | grep 47_
+	$ hg tags | grep 51_
 	(snip)
-	FIREFOX_47_0b9_RELEASE		341367:2ee4473c729a
+	FIREFOX_51_0b14_RELEASE        364880:09142d07fd73
 	(snip)
 
 Checkout the branch.
 
-	$ hg checkout FIREFOX_47_0b9_RELEASE
+	$ hg checkout FIREFOX_51_0b14_RELEASE
 
 Create named branch for working.
 
-	$ hg branch ryoon_firefox-47.0b9
-	$ hg commit -m "Create ryoon_firefox-47.0 branch for merging pkgsrc patches"
+	$ hg branch ryoon_firefox-51.0
+	$ hg commit -m "Create ryoon_firefox-51.0 branch for merging pkgsrc patches"
 
 Add .*\.orig$ to .hgignore, and commit this change
 
@@ -79,19 +76,19 @@
 
 # Merge your patches
 
-	$ hg merge pkgsrc_firefox-46.0.1
+	$ hg merge pkgsrc_firefox-50.1.0
 	$ hg resolve -l
 	$ vi file/marked/as/U
 	$ hg resolve --mark file/marked/as/U
 	(loop)
-	$ hg commit -m "Merge pkgsrc_firefox-46.0.1 branch to 47.0"
+	$ hg commit -m "Merge pkgsrc_firefox-50.1.0 branch to 51.0"
 
 
 # Create patch file for patch -p0
 
-	$ hg diff -r (revision of first commit in ryoon_firefox-47.0b9) | \
-	sed -e 's!^--- a/!--- !' -e 's!^+++ b/!+++ !' > ~/firefox-47.0.diff
-	$ vi ~/firefox-47.0.diff
+	$ hg diff -r (revision of first commit in ryoon_firefox-51.0) | \
+	sed -e 's!^--- a/!--- !' -e 's!^+++ b/!+++ !' > ~/firefox-51.0.diff
+	$ vi ~/firefox-51.0.diff
 	(Remove patch to .hgignore)
 	(Remove patch to .hgtags)
 
@@ -103,8 +100,8 @@
 	(Remove PKGREVISION)
 	$ make mdi
 	$ make extract
-	$ pushd ${WRKOBJDIR}/www/firefox/work/mozilla-beta
-	$ patch -p0 < ~/firefox-47.0.diff
+	$ pushd ${WRKOBJDIR}/www/firefox/work/${DISTNAME}
+	$ patch -p0 < ~/firefox-51.0.diff
 	$ popd
 	$ mkpatches
 	$ patchdiff

Use pkg template to add anchors to ircII and irssi packages
Index: wikisrc/netbsd-code-chat.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/netbsd-code-chat.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/netbsd-code-chat.mdwn	20 Jan 2017 07:08:24 -0000	1.1
+++ wikisrc/netbsd-code-chat.mdwn	20 Jan 2017 08:32:11 -0000	1.2
@@ -4,5 +4,5 @@
 
  #NetBSD-code is pretty quiet when no-one has a question; that is a feature.
 
-[freenode](http://freenode.net/) has a list of servers. If you have never used IRC before, start with the Webchat at the Freenode website, and we recommend ircII or irssi (both in pkgsrc, try what fits you better) for later.
+[freenode](http://freenode.net/) has a list of servers. If you have never used IRC before, start with the Webchat at the Freenode website, and we recommend [[!template id=pkg category="chat" name="ircII"]] or [[!template id=pkg category="chat" name="irssi"]] (both in pkgsrc, try what fits you better) for later.
 For general hanging out and meeting the community, join #NetBSD or #pkgsrc instead.

also done
Index: wikisrc/projects/project/npf_web_ui.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/npf_web_ui.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/npf_web_ui.mdwn	3 Feb 2016 16:58:29 -0000	1.5
+++ wikisrc/projects/project/npf_web_ui.mdwn	20 Jan 2017 07:23:40 -0000	1.6
@@ -10,6 +10,10 @@
 TBD
 """
 
+done_by="""
+maya@NetBSD.org
+"""
+
 category="userland"
 difficulty="hard"
 duration="3 months"

initialize page about #NetBSD-code for the GSoC 2017 application
--- /dev/null	2017-01-20 07:00:33.000000000 +0000
+++ wikisrc/netbsd-code-chat.mdwn	2017-01-20 07:08:37.000000000 +0000
@@ -0,0 +1,8 @@
+# The Freenode channel #NetBSD-code
+
+This IRC channel was created as a resource for Google Summer of Code students, and expanded as a general resource for people doing programming on NetBSD or pkgsrc, because not only GSoC students can use a hand finding which Fine Manual page will help them with the latest snag on the way to done, or how they should best use an API. Design questions are better discussed on the mailing lists.
+
+ #NetBSD-code is pretty quiet when no-one has a question; that is a feature.
+
+[freenode](http://freenode.net/) has a list of servers. If you have never used IRC before, start with the Webchat at the Freenode website, and we recommend ircII or irssi (both in pkgsrc, try what fits you better) for later.
+For general hanging out and meeting the community, join #NetBSD or #pkgsrc instead.

retry
Index: wikisrc/community.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/community.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/community.mdwn	20 Jan 2017 06:46:50 -0000	1.4
+++ wikisrc/community.mdwn	20 Jan 2017 06:48:52 -0000	1.5
@@ -21,7 +21,7 @@
 * Channel #NetBSD on [IRCnet](http://www.ircnet.info/)
 * Channel #NetBSD on [EFnet](http://www.efnet.org/)
 * Channel #NetBSD on [freenode](http://freenode.net/)
-* Channel [[#NetBSD-code]] on [freenode](http://freenode.net/)
+* Channel [[#NetBSD-code|netbsd-code-chat]] on [freenode](http://freenode.net/)
 * SILC - [SILCNet](http://silcnet.org/) has a netbsd channel for secure chats.
 
 ## Internet forums, discussion groups, etc

Index: wikisrc/community.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/community.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/community.mdwn	20 Jan 2017 06:45:47 -0000	1.3
+++ wikisrc/community.mdwn	20 Jan 2017 06:46:50 -0000	1.4
@@ -21,7 +21,7 @@
 * Channel #NetBSD on [IRCnet](http://www.ircnet.info/)
 * Channel #NetBSD on [EFnet](http://www.efnet.org/)
 * Channel #NetBSD on [freenode](http://freenode.net/)
-* Channel [#NetBSD-code] on [freenode](http://freenode.net/)
+* Channel [[#NetBSD-code]] on [freenode](http://freenode.net/)
 * SILC - [SILCNet](http://silcnet.org/) has a netbsd channel for secure chats.
 
 ## Internet forums, discussion groups, etc

add a reference to #NetBSD-code
Index: wikisrc/community.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/community.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/community.mdwn	26 May 2013 12:56:16 -0000	1.2
+++ wikisrc/community.mdwn	20 Jan 2017 06:45:47 -0000	1.3
@@ -21,6 +21,7 @@
 * Channel #NetBSD on [IRCnet](http://www.ircnet.info/)
 * Channel #NetBSD on [EFnet](http://www.efnet.org/)
 * Channel #NetBSD on [freenode](http://freenode.net/)
+* Channel [#NetBSD-code] on [freenode](http://freenode.net/)
 * SILC - [SILCNet](http://silcnet.org/) has a netbsd channel for secure chats.
 
 ## Internet forums, discussion groups, etc

add reference to 2016
Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/projects/gsoc.mdwn	16 Feb 2016 17:40:53 -0000	1.20
+++ wikisrc/projects/gsoc.mdwn	20 Jan 2017 06:27:36 -0000	1.21
@@ -1,7 +1,7 @@
 [[!meta title="Google Summer of Code project proposals"]]
 
-NetBSD participated successfully in all of Google's Summer of Code
-programs up to 2013 (see our results of
+NetBSD participated successfully in the following Google's Summer of Code
+programs (see our results of
 [2005](http://www.netbsd.org/foundation/press/soc-summary.html),
 [2006](http://www.netbsd.org/foundation/press/soc2006-summary.html),
 [2007](http://www.netbsd.org/foundation/press/soc2007-summary.html),
@@ -10,7 +10,8 @@
 [2010](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2010),
 [2011](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of),
 [2012](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of1),
-[2013](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2)).
+[2013](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2) and
+[2016](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2016)).
 
 This page contains a list of concrete suggestions for projects we would
 like to see applications for in the next Summer of Code. Note that they

fix magic
Index: wikisrc/projects/project/posix_suite_compliance.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/posix_suite_compliance.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/posix_suite_compliance.mdwn	19 Jan 2017 23:46:20 -0000	1.5
+++ wikisrc/projects/project/posix_suite_compliance.mdwn	19 Jan 2017 23:48:26 -0000	1.6
@@ -8,7 +8,7 @@
 mentors="""
 [Christos Zoulas](mailto:christos@NetBSD.org)
 """
-completed_by="""
+done_by="""
 charles cui
 """
 

done in 2016
Index: wikisrc/projects/project/posix_suite_compliance.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/posix_suite_compliance.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/posix_suite_compliance.mdwn	21 Feb 2016 20:06:48 -0000	1.4
+++ wikisrc/projects/project/posix_suite_compliance.mdwn	19 Jan 2017 23:46:20 -0000	1.5
@@ -8,6 +8,9 @@
 mentors="""
 [Christos Zoulas](mailto:christos@NetBSD.org)
 """
+completed_by="""
+charles cui
+"""
 
 category="kernel"
 difficulty="easy"

test edit
Index: wikisrc/users/spz/sandbox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/sandbox.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/users/spz/sandbox.mdwn	9 Dec 2016 12:16:00 -0000	1.9
+++ wikisrc/users/spz/sandbox.mdwn	18 Jan 2017 20:03:18 -0000	1.10
@@ -1,3 +1,3 @@
 help, I'm caught in a cookie factory .. on second thought, send help later. Much later :)
 
-*blip*
+fussel

Define `no_install_notes' for all ports that do not have INSTALL notes
Index: wikisrc/ports/algor.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/algor.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/ports/algor.mdwn	26 Oct 2016 20:16:33 -0000	1.11
+++ wikisrc/ports/algor.mdwn	13 Jan 2017 16:06:02 -0000	1.12
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/algor/alogo2.gif"
+no_install_notes="defined"
 about="""
 NetBSD/algor is the port of NetBSD to the Algorithmics, Ltd. MIPS evaluation
 boards. Algorithmics was a long-time supplier of MIPS evaluation/prototyping
Index: wikisrc/ports/amigappc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amigappc.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/amigappc.mdwn	26 Oct 2016 20:16:33 -0000	1.10
+++ wikisrc/ports/amigappc.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -7,6 +7,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/arm26/arch310.gif"
+no_install_notes="defined"
 about="""
 NetBSD/amigappc is a very experimental port to the PowerPC-based Amiga expansion
 boards as manufactured by Phase 5.
Index: wikisrc/ports/cesfic.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cesfic.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/cesfic.mdwn	26 Oct 2016 20:16:33 -0000	1.9
+++ wikisrc/ports/cesfic.mdwn	13 Jan 2017 16:06:02 -0000	1.10
@@ -6,6 +6,7 @@
 pkg_rel="6.0"
 changes_cur="7.0"
 changes_future="8.0"
+no_install_notes="defined"
 about="""
 NetBSD/cesfic is a port to the m68040 based FIC8234 VME processor board, made by
 the swiss company CES (Geneve). These boards were popular in high energy physics
Index: wikisrc/ports/cobalt.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cobalt.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/cobalt.mdwn	26 Oct 2016 20:16:33 -0000	1.9
+++ wikisrc/ports/cobalt.mdwn	13 Jan 2017 16:06:02 -0000	1.10
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/cobalt/quberaq.gif"
+no_install_notes="defined"
 about="""
 NetBSD/cobalt is the port of NetBSD to Cobalt Networks' MIPS-based Microservers,
 now known as Sun Server Appliances.
Index: wikisrc/ports/ibmnws.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/ibmnws.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/ports/ibmnws.mdwn	26 Oct 2016 20:16:33 -0000	1.8
+++ wikisrc/ports/ibmnws.mdwn	13 Jan 2017 16:06:02 -0000	1.9
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/ibmnws/nws1000.png"
+no_install_notes="defined"
 about="""
 NetBSD/ibmnws is the port of NetBSD to [IBM](http://www.ibm.com/)
 Network Station Series 1000 PowerPC-based computers.
Index: wikisrc/ports/iyonix.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/iyonix.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/iyonix.mdwn	26 Oct 2016 20:16:33 -0000	1.10
+++ wikisrc/ports/iyonix.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -5,6 +5,7 @@
 pkg_rel="6.1"
 changes_cur="7.0"
 changes_future="8.0"
+no_install_notes="defined"
 about="""
 NetBSD/iyonix is a port of NetBSD to Castle Technology's [Iyonix](http://www.iyonix.com/32bit/)
 computers, an ARM based PC. It was first committed to the NetBSD source tree on
Index: wikisrc/ports/luna68k.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/luna68k.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/luna68k.mdwn	26 Oct 2016 20:16:34 -0000	1.10
+++ wikisrc/ports/luna68k.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/luna68k/luna.gif"
+no_install_notes="defined"
 about="""
 NetBSD/luna68k is a port of NetBSD to the LUNA product line of OMRON Tateisi
 Electronics, Japan. The LUNA was a 20MHz/m68030 desktop computer at the age of
Index: wikisrc/ports/mipsco.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/mipsco.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/mipsco.mdwn	26 Oct 2016 20:16:34 -0000	1.7
+++ wikisrc/ports/mipsco.mdwn	13 Jan 2017 16:06:02 -0000	1.8
@@ -5,6 +5,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/mipsco/rc3230.gif"
+no_install_notes="defined"
 about="""
 NetBSD/mipsco is a port of NetBSD to the MIPS Computer Systems Inc. family of
 workstations and servers. The Mips Magnum 3000 was a popular workstation that
Index: wikisrc/ports/mvmeppc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/mvmeppc.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/mvmeppc.mdwn	26 Oct 2016 20:16:34 -0000	1.10
+++ wikisrc/ports/mvmeppc.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/mvmeppc/mvme2600.gif"
+no_install_notes="defined"
 about="""
 NetBSD/mvmeppc is the port of NetBSD to Motorola's PowerPC VME Single Board
 Computers (SBC). The first Motorola SBC (68k-based) was introduced in 1988.
Index: wikisrc/ports/netwinder.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/netwinder.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/netwinder.mdwn	26 Oct 2016 20:16:34 -0000	1.9
+++ wikisrc/ports/netwinder.mdwn	13 Jan 2017 16:06:02 -0000	1.10
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/netwinder/2100.gif"
+no_install_notes="defined"
 about="""
 NetBSD/netwinder is a port of NetBSD to StrongARM based NetWinder machines.
 """
Index: wikisrc/ports/zaurus.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/zaurus.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/zaurus.mdwn	26 Oct 2016 20:16:34 -0000	1.10
+++ wikisrc/ports/zaurus.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/zaurus/zaurus.gif"
+no_install_notes="defined"
 about="""
 NetBSD/zaurus is a port of NetBSD to the ARM processor based PDAs by
 [Sharp](http://www.sharpusa.com/).

NetBSD/dreamcast packages for 6.0 no longer available. Switch to the 7.0 ones.
Pointed out by <sevan> via port-dreamcast/51836.
Members: 
	ports/dreamcast.mdwn:1.10->1.11 

Index: wikisrc/ports/dreamcast.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/dreamcast.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/dreamcast.mdwn	13 Jan 2017 10:09:08 -0000	1.10
+++ wikisrc/ports/dreamcast.mdwn	13 Jan 2017 10:15:11 -0000	1.11
@@ -2,7 +2,7 @@
 port="dreamcast"
 cur_rel="7.0.2"
 future_rel="8.0"
-pkg_rel="6.0"
+pkg_rel="7.0"
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/dreamcast/dreamcast2.gif"

NetBSD/dreamcast currently does not have INSTALL notes, define no_install_notes
to address that.
Pointed out by <sevan> via port-dreamcast/51836.
Members: 
	ports/dreamcast.mdwn:1.9->1.10 

Index: wikisrc/ports/dreamcast.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/dreamcast.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/dreamcast.mdwn	26 Oct 2016 20:16:33 -0000	1.9
+++ wikisrc/ports/dreamcast.mdwn	13 Jan 2017 10:09:08 -0000	1.10
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/dreamcast/dreamcast2.gif"
+no_install_notes="defined"
 about="""
 NetBSD/dreamcast is the port of NetBSD for the Japanese game console
 [SEGA](http://www.sega.co.jp) Dreamcast.

Add support for no_install_notes variable that if defined will not add the
`INSTALL notes' link for ports that does not have install notes available.
Should fix part of port-dreamcast/51836 problem reported by <sevan>.
Members: 
	templates/port.mdwn:1.16->1.17 

Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/templates/port.mdwn	22 Mar 2016 22:10:23 -0000	1.16
+++ wikisrc/templates/port.mdwn	13 Jan 2017 10:06:34 -0000	1.17
@@ -15,8 +15,8 @@
 <TMPL_IF port_var6>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var6> <TMPL_VAR cur_rel> via FTP](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>-<TMPL_VAR port_var6>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var6> FTP")</TMPL_IF>
 <TMPL_IF port_var7>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var7> <TMPL_VAR cur_rel> via FTP](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>-<TMPL_VAR port_var7>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var7> FTP")</TMPL_IF>
 <TMPL_ELSE>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> via FTP](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/ "NetBSD/<TMPL_VAR port> FTP")</TMPL_IF></TMPL_IF>
-<TMPL_IF cur_rel><TMPL_IF port_var1><TMPL_IF port_var_install_notes>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port_var_install_notes>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes")</TMPL_IF>
-<TMPL_ELSE>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes")</TMPL_IF></TMPL_IF>
+<TMPL_UNLESS no_install_notes><TMPL_IF cur_rel><TMPL_IF port_var1><TMPL_IF port_var_install_notes>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port_var_install_notes>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes")</TMPL_IF>
+<TMPL_ELSE>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes")</TMPL_IF></TMPL_IF></TMPL_UNLESS>
 <TMPL_IF pkg_rel><TMPL_IF port_var1>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var1> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc](http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var1>/<TMPL_VAR pkg_rel>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var1> pkgsrc binary packages")
 <TMPL_IF port_var2>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var2> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc](http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var2>/<TMPL_VAR pkg_rel>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var2> pkgsrc binary packages")</TMPL_IF>
 <TMPL_IF port_var3>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var3> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc](http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var3>/<TMPL_VAR pkg_rel>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var3> pkgsrc binary packages")</TMPL_IF>
@@ -83,6 +83,7 @@
 - thumbnail (optional)
 - supported_hardware (optional)
 - unsupported_hardware (optional)
+- no_install_notes (optional)
 - additional (optional)
 
 </TMPL_IF>

Make the text about using a serial console for the dom0 more consistent
with reality.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.138
retrieving revision 1.139
diff -u -r1.138 -r1.139
--- wikisrc/ports/xen/howto.mdwn	29 Dec 2016 19:32:51 -0000	1.138
+++ wikisrc/ports/xen/howto.mdwn	4 Jan 2017 10:25:16 -0000	1.139
@@ -435,11 +435,16 @@
 which specifies that the dom0 should have 256M, leaving the rest to be
 allocated for domUs.  To use a serial console, use
 
-        menu=Xen:load /netbsd-XEN3_DOM0.gz console=com0;multiboot /xen.gz dom0_mem=256M console=com1 com1=9600,8n1
+        menu=Xen:load /netbsd-XEN3_DOM0.gz;multiboot /xen.gz dom0_mem=256M console=com1 com1=9600,8n1
 
 which will use the first serial port for Xen (which counts starting
-from 1), forcing speed/parity, and also for NetBSD (which counts
-starting at 0).  In an attempt to add performance, one can also add
+from 1, unlike NetBSD which counts starting from 0), forcing
+speed/parity.  Because the NetBSD command line lacks a
+"console=pc" argument, it will use the default "xencons" console device,
+which directs the console I/O through Xen to the same console device Xen
+itself uses (in this case, the serial port).
+
+In an attempt to add performance, one can also add
 
         dom0_max_vcpus=1 dom0_vcpus_pin
 

Added a comment: Encryption PS
--- /dev/null	2017-01-04 09:52:03.000000000 +0000
+++ wikisrc/projects/project/transparent-cgd/comment_2_db7fddc05f1196353a702f21fce70d70._comment	2017-01-04 09:56:24.000000000 +0000
@@ -0,0 +1,22 @@
+[[!comment format=mdwn
+ username="https://openid.stackexchange.com/user/9e1973a3-233c-4f35-8b87-56c7ef1cd21d"
+ nickname="Sam"
+ subject="Encryption PS"
+ date="2017-01-04T09:56:08Z"
+ content="""
+I forgot to add that Truecrypt had a version for Linux and at one time had a BSD version which I believe no longer is around or operative. Truecrypt was anonymously written and he closed up shop and just disappeared one day. Truecrypt has also had extensive code verification leading to additions in Veracrypt.
+
+Here's a link for tcplay(derivative or Truecrypt).
+
+https://github.com/bwalex/tc-play
+
+Veracrypt
+
+https://veracrypt.codeplex.com/
+
+and the Dragonfly BSD I linked above where it's use of tcplay is described.
+
+I hope this is helpful All the questions that you asked in the summary have been answered on other systems with TC and VC. I know they're not Net but it could be a good start on how they've managed it.
+
+
+"""]]

Added a comment: Encryption
--- /dev/null	2017-01-04 09:32:00.000000000 +0000
+++ wikisrc/projects/project/transparent-cgd/comment_1_c816f012ad042401a47885ee192981e0._comment	2017-01-04 09:32:03.000000000 +0000
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="https://openid.stackexchange.com/user/9e1973a3-233c-4f35-8b87-56c7ef1cd21d"
+ nickname="Sam"
+ subject="Encryption"
+ date="2017-01-04T09:31:47Z"
+ content="""
+I think you should do something that no one wants to do. Take as much as you can from a long term existing system. There's a program that started on win98(name change)(scramdisk) and moved to Win 2000(ECM) then on Win XP,...etc(Truecrpyt). It now is rewritten and called (Veracrypt) for Windows, Linux, Mac OS and Raspberry Pi ARMv7. The only thing stopping me from moving to one of the BSD's is reading truecrypt files. DragonflyBSD reads Truecrypt through tcplay a rewrite of truecrypt but DF is a little more experimental than I want for a desktop.
+ 
+https://www.dragonflybsd.org/features/#index5h2
+
+ So there's two versions from the same Truecrypt source. Tcplay and Veracrypt. Veracrypt is a newer version that is audited and has corrected some small deficiencies of TC so is better but bigger, more complete and complex. The MacOS works through FUSE specifically OSXFUSE 2.5. Linux I think through DMcrypt. Here's what so good about Veracrypt/Truecrypt. It has encryption on the fly for not only regular drives but the OS system drive also, after it's running. This means not setting up encryption but encrypting the drive as the OS runs, then writing the boot with password enabled. It's very, very nice. I'm not saying that all these things need to be in place at once but using the code they have already written shows a pathway. Too start just use the code for equivalent encryption to Veracrypt(which has a compatibility function for Truecrypt). The important thing is Truecrypt has been around a long, long time and lots of people have this format and it works. For some reason people keep reinventing the wheel 
+"""]]

Remove preapproved funding designations.
Per discussion between board and core, these stale designations will
be replaced by something we hope to be more lively and maintained.
Members: 
	projects/project/atomic_fifo_lifo_queues.mdwn:1.1->1.2 
	projects/project/atomic_radix_patricia_trees.mdwn:1.1->1.2 
	projects/project/fast_protocol.mdwn:1.1->1.2 
	projects/project/if_poll.mdwn:1.1->1.2 
	projects/project/kernel_continuations.mdwn:1.3->1.4 
	projects/project/lazy_receive.mdwn:1.1->1.2 
	projects/project/nexthop_cache.mdwn:1.1->1.2 
	projects/project/optional_tcp_syncache.mdwn:1.1->1.2 

Index: wikisrc/projects/project/atomic_fifo_lifo_queues.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/atomic_fifo_lifo_queues.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/atomic_fifo_lifo_queues.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/atomic_fifo_lifo_queues.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -10,11 +10,9 @@
 
 category="kernel"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to implement lockless and atomic FIFO/LIFO
 queues in the kernel.  The routines to be implemented allow for commonly
Index: wikisrc/projects/project/atomic_radix_patricia_trees.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/atomic_radix_patricia_trees.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/atomic_radix_patricia_trees.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/atomic_radix_patricia_trees.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -10,11 +10,9 @@
 
 category="kernel"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to implement lockless, atomic and generic Radix
 and Patricia trees.  BSD systems have always used a radix tree for their
Index: wikisrc/projects/project/fast_protocol.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fast_protocol.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/fast_protocol.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/fast_protocol.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to enhance the networking protocols to process
 incoming packets more efficiently.  The basic idea is the following: when a
Index: wikisrc/projects/project/if_poll.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/if_poll.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/if_poll.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/if_poll.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to implement interrupt handling at the
 granularity of a networking interface.  When a network device gets an
Index: wikisrc/projects/project/kernel_continuations.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/kernel_continuations.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/kernel_continuations.mdwn	16 Feb 2015 06:46:30 -0000	1.3
+++ wikisrc/projects/project/kernel_continuations.mdwn	3 Jan 2017 20:51:24 -0000	1.4
@@ -10,11 +10,9 @@
 
 category="kernel"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to implement continuations at the kernel level.
 Most of the pieces are already available in the kernel, so this can be
Index: wikisrc/projects/project/lazy_receive.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/lazy_receive.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/lazy_receive.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/lazy_receive.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to improve the way the processing of incoming
 packets is handled.
Index: wikisrc/projects/project/nexthop_cache.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/nexthop_cache.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/nexthop_cache.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/nexthop_cache.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to remove the ARP, AARP, ISO SNPA, and IPv6
 Neighbors from the routing table.  Instead, the `ifnet` structure should
Index: wikisrc/projects/project/optional_tcp_syncache.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/optional_tcp_syncache.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/optional_tcp_syncache.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/optional_tcp_syncache.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to make the SYN cache optional.  For small systems,
 this is complete overkill and should be made optional.

goodbye 2016, hello 2017
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- wikisrc/templates/page.tmpl	15 Apr 2016 17:39:25 -0000	1.32
+++ wikisrc/templates/page.tmpl	1 Jan 2017 07:09:15 -0000	1.33
@@ -279,7 +279,7 @@
       <span class="footcopy"><a href="about/disclaimer.html">
         Disclaimer</a> |
         <span class="copyright">
-          Copyright &copy; 1994-2016 The NetBSD Foundation, Inc.
+          Copyright &copy; 1994-2017 The NetBSD Foundation, Inc.
         </span>
         ALL
         RIGHTS RESERVED. <br /> NetBSD<sup>&reg;</sup> is a registered

calendar update
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1 @@
+[[!calendar type=year year=2017 pages="internal(blog/*)"]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/01.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=01 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(01) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/02.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=02 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(02) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/03.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=03 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(03) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/04.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=04 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(04) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/05.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=05 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(05) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/06.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=06 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(06) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/07.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=07 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(07) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/08.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=08 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(08) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/09.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=09 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(09) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/10.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=10 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(10) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/11.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=11 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(11) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/12.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=12 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(12) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]

Spam
--- wikisrc/wiki/news/no_longer_pre-release__44___but.../comment_1_ffb400c52c1902a31c1f140e3fa3cd80._comment	2016-12-30 12:26:31.000000000 +0000
+++ /dev/null	2016-12-30 12:24:05.000000000 +0000
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
- nickname="harsh"
- subject="Describe 1…800…204…4122 @@@@ Lexmark printer customer Support phone number usa "
- date="2016-12-29T23:18:08Z"
- content="""
-((moti))Call @@@++ USA 18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t
-p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r
-n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1
-18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r
-u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER
-s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1844-848-1262 USA, LEXMARK  PRINTER 
-Tech Support phone number,LEXMARK  PRINTER technical support phone number 1 18002044122
-.LEXMARK  PRINTER Tech Support Number LEXMARK  PRINTER Tech LEXMARK  PRINTER tech support, LEXMARK  PRINTER tech support
-number, LEXMARK  PRINTER tech support phone number, LEXMARK  PRINTER technical support, LEXMARK  PRINTER
-technical support number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER tech
-support number, LEXMARK  PRINTER support number, LEXMARK  PRINTER Tech support phone number, LEXMARK  PRINTER
-support phone number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER technical
-support number,Support Phone Number for LEXMARK  PRINTER  Phone Number for LEXMARK  PRINTER
-CustomerService Technical Support Telephone Number LEXMARK  PRINTER  support number
-LEXMARK  PRINTER LEXMARK  PRINTER  tech support number LEXMARK  PRINTER LEXMARK  PRINTER  technical support
-number LEXMARK  PRINTER LEXMARK  PRINTER  technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER 
-customer service number LEXMARK  PRINTER LEXMARK  PRINTER internet security technical support LEXMARK  PRINTER
-technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
-LEXMARK  PRINTER customer support phone number I-844-848-1262 LEXMARK  PRINTER LEXMARK  PRINTER  support
-phone number LEXMARK  PRINTER LEXMARK  PRINTER support phone LEXMARK  PRINTER tech support LEXMARK  PRINTER customer
-support LEXMARK  PRINTER phone support LEXMARK  PRINTER support number LEXMARK  PRINTER LEXMARK  PRINTER technical support
-LEXMARK  PRINTER  customer support phone 
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_1_2e85048f0cd0ba602ae62c2706fe4159._comment	2016-12-30 12:26:31.000000000 +0000
+++ /dev/null	2016-12-30 12:24:05.000000000 +0000
@@ -1,93 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
- nickname="harsh"
- subject="(((((((1800 204 4122)))))))))@@.@ Lexmark printer tech support number Lexmark printer customer service number"
- date="2016-12-29T23:14:06Z"
- content="""
-((moti))Call @@@++ USA 18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t
-p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r
-n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1
-18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r
-u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER
-s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1844-848-1262 USA, LEXMARK  PRINTER 
-Tech Support phone number,LEXMARK  PRINTER technical support phone number 1 18002044122
-.LEXMARK  PRINTER Tech Support Number LEXMARK  PRINTER Tech LEXMARK  PRINTER tech support, LEXMARK  PRINTER tech support
-number, LEXMARK  PRINTER tech support phone number, LEXMARK  PRINTER technical support, LEXMARK  PRINTER
-technical support number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER tech
-support number, LEXMARK  PRINTER support number, LEXMARK  PRINTER Tech support phone number, LEXMARK  PRINTER
-support phone number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER technical
-support number,Support Phone Number for LEXMARK  PRINTER  Phone Number for LEXMARK  PRINTER
-CustomerService Technical Support Telephone Number LEXMARK  PRINTER  support number
-LEXMARK  PRINTER LEXMARK  PRINTER  tech support number LEXMARK  PRINTER LEXMARK  PRINTER  technical support
-number LEXMARK  PRINTER LEXMARK  PRINTER  technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER 
-customer service number LEXMARK  PRINTER LEXMARK  PRINTER internet security technical support LEXMARK  PRINTER
-technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
-LEXMARK  PRINTER customer support phone number I-844-848-1262 LEXMARK  PRINTER LEXMARK  PRINTER  support
-phone number LEXMARK  PRINTER LEXMARK  PRINTER support phone LEXMARK  PRINTER tech support LEXMARK  PRINTER customer
-support LEXMARK  PRINTER phone support LEXMARK  PRINTER support number LEXMARK  PRINTER LEXMARK  PRINTER technical support
-LEXMARK  PRINTER  customer support phone number LEXMARK  PRINTER LEXMARK  PRINTER  tech support
-phone number LEXMARK  PRINTER contact LEXMARK  PRINTER support LEXMARK  PRINTER  technical support phone
-number ~!~18002044122++ LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER tech support LEXMARK  PRINTER
-support ticket LEXMARK  PRINTER customer support number LEXMARK  PRINTER LEXMARK  PRINTER tech support number
-LEXMARK  PRINTER LEXMARK  PRINTER technical support number LEXMARK  PRINTER LEXMARK  PRINTER support center LEXMARK  PRINTER telephone
-support call LEXMARK  PRINTER support LEXMARK  PRINTER  support support LEXMARK  PRINTER LEXMARK  PRINTER billing
-support LEXMARK  PRINTER  technical support number LEXMARK  PRINTER support LEXMARK  PRINTER 
-LEXMARK  PRINTER online support LEXMARK  PRINTER contasct support LEXMARK  PRINTER  support number LEXMARK  PRINTER
-LEXMARK  PRINTER  customer support number LEXMARK  PRINTER LEXMARK  PRINTER  tech support number
-LEXMARK  PRINTER support for LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone
-number LEXMARK  PRINTER LEXMARK  PRINTER contact phone number LEXMARK  PRINTER LEXMARK  PRINTER  phone number LEXMARK  PRINTER
-LEXMARK  PRINTER  customer service phone number LEXMARK  PRINTER phone number LEXMARK  PRINTER for LEXMARK  PRINTER
-customer service LEXMARK  PRINTER software phone number LEXMARK  PRINTER phone number LEXMARK  PRINTER for LEXMARK  PRINTER
-LEXMARK  PRINTER customer service telephone number LEXMARK  PRINTER LEXMARK  PRINTER helpline phone number LEXMARK  PRINTER
-LEXMARK  PRINTER contact number LEXMARK  PRINTER LEXMARK  PRINTER customer service number LEXMARK  PRINTER LEXMARK  PRINTER customer
-service phone number ~!~18002044122++ LEXMARK  PRINTER us LEXMARK  PRINTER customer service phone
-number LEXMARK  PRINTER usa LEXMARK  PRINTER telephone number LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER usa
-LEXMARK  PRINTER  contact number LEXMARK  PRINTER LEXMARK  PRINTER number LEXMARK  PRINTER LEXMARK  PRINTER contact number
-LEXMARK  PRINTER usa LEXMARK  PRINTER  helpline number LEXMARK  PRINTER LEXMARK  PRINTER helpline number LEXMARK  PRINTER LEXMARK  PRINTER
-customer number LEXMARK  PRINTER LEXMARK  PRINTER  customer service number LEXMARK  PRINTER LEXMARK  PRINTER contact
-telephone number LEXMARK  PRINTER contact number LEXMARK  PRINTER for LEXMARK  PRINTER LEXMARK  PRINTER software contact
-number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER LEXMARK  PRINTER telephone number LEXMARK  PRINTER uk LEXMARK  PRINTER
-registration number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER usa LEXMARK  PRINTER customer
-service LEXMARK  PRINTER software customer service contact LEXMARK  PRINTER customer service LEXMARK  PRINTER
-customer service phone LEXMARK  PRINTER  customer service LEXMARK  PRINTER service LEXMARK  PRINTER
- technical support LEXMARK  PRINTER  customer support LEXMARK  PRINTER technical
-support reviews telephone LEXMARK  PRINTER  LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
-LEXMARK  PRINTER  tech support phone number LEXMARK  PRINTER LEXMARK  PRINTER  customer service
-LEXMARK  PRINTER technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER  free  support
-LEXMARK  PRINTER customer service billing LEXMARK  PRINTER customer service email address LEXMARK  PRINTER
-customer service reviews contact LEXMARK  PRINTER customer service LEXMARK  PRINTER tech support
-number LEXMARK  PRINTER usa LEXMARK  PRINTER  support number LEXMARK  PRINTER LEXMARK  PRINTER  contact
-number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone number LEXMARK  PRINTER LEXMARK  PRINTER technical support
-usa LEXMARK  PRINTER technical support number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone LEXMARK  PRINTER tech
-support number LEXMARK  PRINTER LEXMARK  PRINTER customer service telephone number LEXMARK  PRINTER LEXMARK  PRINTER
- customer support number LEXMARK  PRINTER LEXMARK  PRINTER  phone number LEXMARK  PRINTER LEXMARK  PRINTER
- online support LEXMARK  PRINTER customer service number LEXMARK  PRINTER LEXMARK  PRINTER tech support
-center LEXMARK  PRINTER customer service LEXMARK  PRINTER software customer service LEXMARK  PRINTER customer
-care number LEXMARK  PRINTER usa LEXMARK  PRINTER customer number LEXMARK  PRINTER LEXMARK  PRINTER customer support number
-LEXMARK  PRINTER LEXMARK  PRINTER customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care toll free number
-LEXMARK  PRINTER LEXMARK  PRINTER tech support LEXMARK  PRINTER technical support LEXMARK  PRINTER  support LEXMARK  PRINTER
- tech support LEXMARK  PRINTER support center LEXMARK  PRINTER.com customer service LEXMARK  PRINTER
- customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care LEXMARK  PRINTER phone number LEXMARK  PRINTER
-phone number LEXMARK  PRINTER for LEXMARK  PRINTER customer service LEXMARK  PRINTER phone support LEXMARK  PRINTER phone
-number LEXMARK  PRINTER tech support LEXMARK  PRINTER support phone number LEXMARK  PRINTER contact LEXMARK  PRINTER by
-phone LEXMARK  PRINTER contact phone number LEXMARK  PRINTER LEXMARK  PRINTER helpline phone number LEXMARK  PRINTER LEXMARK  PRINTER
- phone LEXMARK  PRINTER  for phone LEXMARK  PRINTER contact number LEXMARK  PRINTER LEXMARK  PRINTER contact
-support contact LEXMARK  PRINTER  LEXMARK  PRINTER contact number LEXMARK  PRINTER usa LEXMARK  PRINTER toll free
-number LEXMARK  PRINTER LEXMARK  PRINTER telephone number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER usa
-LEXMARK  PRINTER  support services technical support for  LEXMARK  PRINTER LEXMARK  PRINTER
-customer service phone number LEXMARK  PRINTER usa LEXMARK  PRINTER  customer care number
-LEXMARK  PRINTER usa LEXMARK  PRINTER customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care center LEXMARK  PRINTER
-customer support LEXMARK  PRINTER customer support phone LEXMARK  PRINTER customer help LEXMARK  PRINTER
-customer & technical support LEXMARK  PRINTER customer portal LEXMARK  PRINTER customer care phone
-number LEXMARK  PRINTER usa LEXMARK  PRINTER customer care email LEXMARK  PRINTER helpline LEXMARK  PRINTER tech support
-contact LEXMARK  PRINTER customer care toll free LEXMARK  PRINTER  customer service number
-LEXMARK  PRINTER LEXMARK  PRINTER  protection norton  customer service number LEXMARK  PRINTER
-LEXMARK  PRINTER software customer service number LEXMARK  PRINTER LEXMARK  PRINTER hotline customer service
-phone number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone number LEXMARK  PRINTER us how to contact
-LEXMARK  PRINTER by email LEXMARK  PRINTER free phone support LEXMARK  PRINTER  technical support number
-LEXMARK  PRINTER LEXMARK  PRINTER  technical support help desk phone number LEXMARK  PRINTER LEXMARK  PRINTER
-technical support number LEXMARK  PRINTER toll free number LEXMARK  PRINTER LEXMARK  PRINTER  customer
-support phone number LEXMARK  PRINTER LEXMARK  PRINTER  customer
-
-
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_2_4a48aa610335921245f39a8641cca5da._comment	2016-12-30 12:26:31.000000000 +0000
+++ /dev/null	2016-12-30 12:24:05.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
- nickname="harsh"
- subject="HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell Pr"
- date="2016-12-29T23:19:26Z"
- content="""
-HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_3_14b1e5237919f09714489f6e79123ad4._comment	2016-12-30 12:26:31.000000000 +0000
+++ /dev/null	2016-12-30 12:24:05.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
- nickname="harsh"
- subject="USA))))@.@@.@1*800~204-4122 Lexmark printer technical support number,Lexmar"
- date="2016-12-29T23:20:26Z"
- content="""
-HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer
-"""]]

Added a comment: USA))))@.@@.@1*800~204-4122 Lexmark printer technical support number,Lexmar
--- /dev/null	2016-12-30 12:24:05.000000000 +0000
+++ wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_3_14b1e5237919f09714489f6e79123ad4._comment	2016-12-30 12:26:32.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
+ nickname="harsh"
+ subject="USA))))@.@@.@1*800~204-4122 Lexmark printer technical support number,Lexmar"
+ date="2016-12-29T23:20:26Z"
+ content="""
+HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer
+"""]]

Added a comment: HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell Pr
--- /dev/null	2016-12-30 12:24:05.000000000 +0000
+++ wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_2_4a48aa610335921245f39a8641cca5da._comment	2016-12-30 12:26:32.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
+ nickname="harsh"
+ subject="HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell Pr"
+ date="2016-12-29T23:19:26Z"
+ content="""
+HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer
+"""]]

Added a comment: Describe 1…800…204…4122 @@@@ Lexmark printer customer Support phone number usa
--- /dev/null	2016-12-30 12:24:05.000000000 +0000
+++ wikisrc/wiki/news/no_longer_pre-release__44___but.../comment_1_ffb400c52c1902a31c1f140e3fa3cd80._comment	2016-12-30 12:26:32.000000000 +0000
@@ -0,0 +1,29 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
+ nickname="harsh"
+ subject="Describe 1…800…204…4122 @@@@ Lexmark printer customer Support phone number usa "
+ date="2016-12-29T23:18:08Z"
+ content="""
+((moti))Call @@@++ USA 18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t
+p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r
+n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1
+18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r
+u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER
+s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1844-848-1262 USA, LEXMARK  PRINTER 
+Tech Support phone number,LEXMARK  PRINTER technical support phone number 1 18002044122
+.LEXMARK  PRINTER Tech Support Number LEXMARK  PRINTER Tech LEXMARK  PRINTER tech support, LEXMARK  PRINTER tech support
+number, LEXMARK  PRINTER tech support phone number, LEXMARK  PRINTER technical support, LEXMARK  PRINTER
+technical support number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER tech
+support number, LEXMARK  PRINTER support number, LEXMARK  PRINTER Tech support phone number, LEXMARK  PRINTER
+support phone number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER technical
+support number,Support Phone Number for LEXMARK  PRINTER  Phone Number for LEXMARK  PRINTER
+CustomerService Technical Support Telephone Number LEXMARK  PRINTER  support number
+LEXMARK  PRINTER LEXMARK  PRINTER  tech support number LEXMARK  PRINTER LEXMARK  PRINTER  technical support
+number LEXMARK  PRINTER LEXMARK  PRINTER  technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER 
+customer service number LEXMARK  PRINTER LEXMARK  PRINTER internet security technical support LEXMARK  PRINTER
+technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
+LEXMARK  PRINTER customer support phone number I-844-848-1262 LEXMARK  PRINTER LEXMARK  PRINTER  support
+phone number LEXMARK  PRINTER LEXMARK  PRINTER support phone LEXMARK  PRINTER tech support LEXMARK  PRINTER customer
+support LEXMARK  PRINTER phone support LEXMARK  PRINTER support number LEXMARK  PRINTER LEXMARK  PRINTER technical support
+LEXMARK  PRINTER  customer support phone 
+"""]]

Added a comment: (((((((1800 204 4122)))))))))@@.@ Lexmark printer tech support number Lexmark printer customer service number
--- /dev/null	2016-12-29 23:10:01.000000000 +0000
+++ wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_1_2e85048f0cd0ba602ae62c2706fe4159._comment	2016-12-29 23:14:21.000000000 +0000
@@ -0,0 +1,93 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
+ nickname="harsh"
+ subject="(((((((1800 204 4122)))))))))@@.@ Lexmark printer tech support number Lexmark printer customer service number"
+ date="2016-12-29T23:14:06Z"
+ content="""
+((moti))Call @@@++ USA 18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t
+p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r
+n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1
+18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r
+u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER
+s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1844-848-1262 USA, LEXMARK  PRINTER 
+Tech Support phone number,LEXMARK  PRINTER technical support phone number 1 18002044122
+.LEXMARK  PRINTER Tech Support Number LEXMARK  PRINTER Tech LEXMARK  PRINTER tech support, LEXMARK  PRINTER tech support
+number, LEXMARK  PRINTER tech support phone number, LEXMARK  PRINTER technical support, LEXMARK  PRINTER
+technical support number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER tech
+support number, LEXMARK  PRINTER support number, LEXMARK  PRINTER Tech support phone number, LEXMARK  PRINTER
+support phone number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER technical
+support number,Support Phone Number for LEXMARK  PRINTER  Phone Number for LEXMARK  PRINTER
+CustomerService Technical Support Telephone Number LEXMARK  PRINTER  support number
+LEXMARK  PRINTER LEXMARK  PRINTER  tech support number LEXMARK  PRINTER LEXMARK  PRINTER  technical support
+number LEXMARK  PRINTER LEXMARK  PRINTER  technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER 
+customer service number LEXMARK  PRINTER LEXMARK  PRINTER internet security technical support LEXMARK  PRINTER
+technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
+LEXMARK  PRINTER customer support phone number I-844-848-1262 LEXMARK  PRINTER LEXMARK  PRINTER  support
+phone number LEXMARK  PRINTER LEXMARK  PRINTER support phone LEXMARK  PRINTER tech support LEXMARK  PRINTER customer
+support LEXMARK  PRINTER phone support LEXMARK  PRINTER support number LEXMARK  PRINTER LEXMARK  PRINTER technical support
+LEXMARK  PRINTER  customer support phone number LEXMARK  PRINTER LEXMARK  PRINTER  tech support
+phone number LEXMARK  PRINTER contact LEXMARK  PRINTER support LEXMARK  PRINTER  technical support phone
+number ~!~18002044122++ LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER tech support LEXMARK  PRINTER
+support ticket LEXMARK  PRINTER customer support number LEXMARK  PRINTER LEXMARK  PRINTER tech support number
+LEXMARK  PRINTER LEXMARK  PRINTER technical support number LEXMARK  PRINTER LEXMARK  PRINTER support center LEXMARK  PRINTER telephone
+support call LEXMARK  PRINTER support LEXMARK  PRINTER  support support LEXMARK  PRINTER LEXMARK  PRINTER billing
+support LEXMARK  PRINTER  technical support number LEXMARK  PRINTER support LEXMARK  PRINTER 
+LEXMARK  PRINTER online support LEXMARK  PRINTER contasct support LEXMARK  PRINTER  support number LEXMARK  PRINTER
+LEXMARK  PRINTER  customer support number LEXMARK  PRINTER LEXMARK  PRINTER  tech support number
+LEXMARK  PRINTER support for LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone
+number LEXMARK  PRINTER LEXMARK  PRINTER contact phone number LEXMARK  PRINTER LEXMARK  PRINTER  phone number LEXMARK  PRINTER
+LEXMARK  PRINTER  customer service phone number LEXMARK  PRINTER phone number LEXMARK  PRINTER for LEXMARK  PRINTER
+customer service LEXMARK  PRINTER software phone number LEXMARK  PRINTER phone number LEXMARK  PRINTER for LEXMARK  PRINTER
+LEXMARK  PRINTER customer service telephone number LEXMARK  PRINTER LEXMARK  PRINTER helpline phone number LEXMARK  PRINTER
+LEXMARK  PRINTER contact number LEXMARK  PRINTER LEXMARK  PRINTER customer service number LEXMARK  PRINTER LEXMARK  PRINTER customer
+service phone number ~!~18002044122++ LEXMARK  PRINTER us LEXMARK  PRINTER customer service phone
+number LEXMARK  PRINTER usa LEXMARK  PRINTER telephone number LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER usa
+LEXMARK  PRINTER  contact number LEXMARK  PRINTER LEXMARK  PRINTER number LEXMARK  PRINTER LEXMARK  PRINTER contact number
+LEXMARK  PRINTER usa LEXMARK  PRINTER  helpline number LEXMARK  PRINTER LEXMARK  PRINTER helpline number LEXMARK  PRINTER LEXMARK  PRINTER
+customer number LEXMARK  PRINTER LEXMARK  PRINTER  customer service number LEXMARK  PRINTER LEXMARK  PRINTER contact
+telephone number LEXMARK  PRINTER contact number LEXMARK  PRINTER for LEXMARK  PRINTER LEXMARK  PRINTER software contact
+number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER LEXMARK  PRINTER telephone number LEXMARK  PRINTER uk LEXMARK  PRINTER
+registration number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER usa LEXMARK  PRINTER customer
+service LEXMARK  PRINTER software customer service contact LEXMARK  PRINTER customer service LEXMARK  PRINTER
+customer service phone LEXMARK  PRINTER  customer service LEXMARK  PRINTER service LEXMARK  PRINTER
+ technical support LEXMARK  PRINTER  customer support LEXMARK  PRINTER technical
+support reviews telephone LEXMARK  PRINTER  LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
+LEXMARK  PRINTER  tech support phone number LEXMARK  PRINTER LEXMARK  PRINTER  customer service
+LEXMARK  PRINTER technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER  free  support
+LEXMARK  PRINTER customer service billing LEXMARK  PRINTER customer service email address LEXMARK  PRINTER
+customer service reviews contact LEXMARK  PRINTER customer service LEXMARK  PRINTER tech support
+number LEXMARK  PRINTER usa LEXMARK  PRINTER  support number LEXMARK  PRINTER LEXMARK  PRINTER  contact
+number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone number LEXMARK  PRINTER LEXMARK  PRINTER technical support
+usa LEXMARK  PRINTER technical support number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone LEXMARK  PRINTER tech
+support number LEXMARK  PRINTER LEXMARK  PRINTER customer service telephone number LEXMARK  PRINTER LEXMARK  PRINTER
+ customer support number LEXMARK  PRINTER LEXMARK  PRINTER  phone number LEXMARK  PRINTER LEXMARK  PRINTER
+ online support LEXMARK  PRINTER customer service number LEXMARK  PRINTER LEXMARK  PRINTER tech support
+center LEXMARK  PRINTER customer service LEXMARK  PRINTER software customer service LEXMARK  PRINTER customer
+care number LEXMARK  PRINTER usa LEXMARK  PRINTER customer number LEXMARK  PRINTER LEXMARK  PRINTER customer support number
+LEXMARK  PRINTER LEXMARK  PRINTER customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care toll free number
+LEXMARK  PRINTER LEXMARK  PRINTER tech support LEXMARK  PRINTER technical support LEXMARK  PRINTER  support LEXMARK  PRINTER
+ tech support LEXMARK  PRINTER support center LEXMARK  PRINTER.com customer service LEXMARK  PRINTER
+ customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care LEXMARK  PRINTER phone number LEXMARK  PRINTER
+phone number LEXMARK  PRINTER for LEXMARK  PRINTER customer service LEXMARK  PRINTER phone support LEXMARK  PRINTER phone
+number LEXMARK  PRINTER tech support LEXMARK  PRINTER support phone number LEXMARK  PRINTER contact LEXMARK  PRINTER by
+phone LEXMARK  PRINTER contact phone number LEXMARK  PRINTER LEXMARK  PRINTER helpline phone number LEXMARK  PRINTER LEXMARK  PRINTER
+ phone LEXMARK  PRINTER  for phone LEXMARK  PRINTER contact number LEXMARK  PRINTER LEXMARK  PRINTER contact
+support contact LEXMARK  PRINTER  LEXMARK  PRINTER contact number LEXMARK  PRINTER usa LEXMARK  PRINTER toll free
+number LEXMARK  PRINTER LEXMARK  PRINTER telephone number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER usa
+LEXMARK  PRINTER  support services technical support for  LEXMARK  PRINTER LEXMARK  PRINTER
+customer service phone number LEXMARK  PRINTER usa LEXMARK  PRINTER  customer care number
+LEXMARK  PRINTER usa LEXMARK  PRINTER customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care center LEXMARK  PRINTER
+customer support LEXMARK  PRINTER customer support phone LEXMARK  PRINTER customer help LEXMARK  PRINTER
+customer & technical support LEXMARK  PRINTER customer portal LEXMARK  PRINTER customer care phone
+number LEXMARK  PRINTER usa LEXMARK  PRINTER customer care email LEXMARK  PRINTER helpline LEXMARK  PRINTER tech support
+contact LEXMARK  PRINTER customer care toll free LEXMARK  PRINTER  customer service number
+LEXMARK  PRINTER LEXMARK  PRINTER  protection norton  customer service number LEXMARK  PRINTER
+LEXMARK  PRINTER software customer service number LEXMARK  PRINTER LEXMARK  PRINTER hotline customer service
+phone number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone number LEXMARK  PRINTER us how to contact
+LEXMARK  PRINTER by email LEXMARK  PRINTER free phone support LEXMARK  PRINTER  technical support number
+LEXMARK  PRINTER LEXMARK  PRINTER  technical support help desk phone number LEXMARK  PRINTER LEXMARK  PRINTER
+technical support number LEXMARK  PRINTER toll free number LEXMARK  PRINTER LEXMARK  PRINTER  customer
+support phone number LEXMARK  PRINTER LEXMARK  PRINTER  customer
+
+
+"""]]

Fix typo.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.137
retrieving revision 1.138
diff -u -r1.137 -r1.138
--- wikisrc/ports/xen/howto.mdwn	29 Dec 2016 19:24:16 -0000	1.137
+++ wikisrc/ports/xen/howto.mdwn	29 Dec 2016 19:32:51 -0000	1.138
@@ -111,7 +111,7 @@
 
 Note that 3.1, 3.3 and 4.1 have been removed from pkgsrc-current, but
 are in 2016Q4.  They will be removed from this HOWTO sometime after
-12017Q1.
+2017Q1.
 
 xenkernel42 provides Xen 4.2.  It is no longer maintained by Xen, but
 as of 2016-12 received backported security patches.  Xen 4.2 runs on

Note removal of 3.1, 3.3 and 4.1 from pkgsrc-current
Threaten purging them from the HOWTO after 2017Q1 is cut.
Members: 
	ports/xen/howto.mdwn:1.136->1.137 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.136
retrieving revision 1.137
diff -u -r1.136 -r1.137
--- wikisrc/ports/xen/howto.mdwn	21 Dec 2016 17:03:03 -0000	1.136
+++ wikisrc/ports/xen/howto.mdwn	29 Dec 2016 19:24:16 -0000	1.137
@@ -109,6 +109,10 @@
 i386 PAE and amd64 hardware.  There are no good reasons to run this
 version.
 
+Note that 3.1, 3.3 and 4.1 have been removed from pkgsrc-current, but
+are in 2016Q4.  They will be removed from this HOWTO sometime after
+12017Q1.
+
 xenkernel42 provides Xen 4.2.  It is no longer maintained by Xen, but
 as of 2016-12 received backported security patches.  Xen 4.2 runs on
 i386 PAE and amd64 hardware.  The only reason to run this is if you

Indent code fragments properly.
Index: wikisrc/features/uvm_hotplug.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/features/uvm_hotplug.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/features/uvm_hotplug.mdwn	29 Dec 2016 16:59:58 -0000	1.2
+++ wikisrc/features/uvm_hotplug.mdwn	29 Dec 2016 17:02:27 -0000	1.3
@@ -7,8 +7,10 @@
      [[!template id=man name=uvm_hotplug section=9]] change.
 
      Early boot code of every port is affected. Global variables:
-     struct vm_physseg vm_physmem;
-     int vm_nphysmem;
+
+     	   struct vm_physseg vm_physmem;
+     	   int vm_nphysmem;
+
      are no longer visible. They need to be replaced by appropriate
      accessor calls in [[!template id=man name=uvm_hotplug section=9]]
 

Formatting.
Index: wikisrc/features/uvm_hotplug.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/features/uvm_hotplug.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/features/uvm_hotplug.mdwn	29 Dec 2016 16:54:37 -0000	1.1
+++ wikisrc/features/uvm_hotplug.mdwn	29 Dec 2016 16:59:58 -0000	1.2
@@ -1,65 +1,63 @@
 # [[!template id=man name=uvm_hotplug section=9]] port-masters' FAQ.
 
-1. Why does it matter?
+  1. Why does it matter?
 
-As a port maintainer any architecture that needs to use the virtual memory
-sub-system of NetBSD aka uvm is affected by the
-[[!template id=man name=uvm_hotplug section=9]] change.
+     As a port maintainer any architecture that needs to use the virtual memory
+     sub-system of NetBSD aka uvm is affected by the
+     [[!template id=man name=uvm_hotplug section=9]] change.
 
-Early boot code of every port is affected. Global variables:
-struct vm_physseg vm_physmem;
-int vm_nphysmem;
-are no longer visible. They need to be replaced by appropriate
-accessor calls in [[!template id=man name=uvm_hotplug section=9]]
+     Early boot code of every port is affected. Global variables:
+     struct vm_physseg vm_physmem;
+     int vm_nphysmem;
+     are no longer visible. They need to be replaced by appropriate
+     accessor calls in [[!template id=man name=uvm_hotplug section=9]]
 
-These calls are documented as "Utility Functions" in the
-[[!template id=man name=uvm_hotplug section=9]] manual.
+     These calls are documented as "Utility Functions" in the
+     [[!template id=man name=uvm_hotplug section=9]] manual.
 
+     The "switchover" CVS commit log is here:
+     [http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html](http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html)
 
-The "switchover" CVS commit log is here:
-[http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html](http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html)
+  2. What files may be affected?
 
+     In most of the architectures the "sys/arch/<arch_name>/<arch_name>/machdep.c"
+     and "sys/arch/<arch_name>/<arch_name>/pmap.c" if they exist are usually
+     affected.
 
-2. What files may be affected?
+     But this may not be a exhaustive list. Any other files that deals with pmap and
+     stealing pages might also be affected.
 
-In most of the architectures the "sys/arch/<arch_name>/<arch_name>/machdep.c"
-and "sys/arch/<arch_name>/<arch_name>/pmap.c" if they exist are usually
-affected.
+  3. What does it do ?
 
-But this may not be a exhaustive list. Any other files that deals with pmap and
-stealing pages might also be affected.
+     [[!template id=man name=uvm_hotplug section=9]] manages the previously exposed "vm_physmem" static array which
+     used to keep track of the memory segments.
 
-3. What does it do ?
+     In the current implementation, the array has been replaced with a
+     [[!template id=man name=rbtree section=3]] backing which makes the
+     data structure dynamic.
 
-[[!template id=man name=uvm_hotplug section=9]] manages the previously exposed "vm_physmem" static array which
-used to keep track of the memory segments.
+     An array based implementation is also provided, for backwards
+     compatibility. This is the default implementation and does not provide
+     hot pluggability. It is also used without 'options UVM_HOTPLUG'
+     However the API itself is implementation agnostic.
 
-In the current implementation, the array has been replaced with a
-[[!template id=man name=rbtree section=3]] backing which makes the
-data structure dynamic.
+  4. Why is it needed?
 
-An array based implementation is also provided, for backwards
-compatibility. This is the default implementation and does not provide
-hot pluggability. It is also used without 'options UVM_HOTPLUG'
-However the API itself is implementation agnostic.
+     With the [[!template id=man name=rbtree section=3]] backing
+     implementation, the list of physical pages 
+     in the system is no longer in a static array and can dynamically
+     expand or collapse, hence adding new pages to the freelist from newly
+     available RAM / physical memory (plug) or removing retired pages
+     (unplug) via taking them off the freelist and the old vm_physmem.
 
-4. Why is it needed?
+  5. What should I do?
 
-With the [[!template id=man name=rbtree section=3]] backing
-implementation, the list of physical pages 
-in the system is no longer in a static array and can dynamically
-expand or collapse, hence adding new pages to the freelist from newly
-available RAM / physical memory (plug) or removing retired pages
-(unplug) via taking them off the freelist and the old vm_physmem.
+     Review the changes to your port due to this new feature. The changes
+     may have been made without direct knowledge of your port architecture.
 
-5. What should I do?
+     See if your port has hotpluggable hardware. If it does, write a driver
+     to use the [[!template id=man name=uvm_hotplug section=9]] api.
 
-Review the changes to your port due to this new feature. The changes
-may have been made without direct knowledge of your port architecture.
-
-See if your port has hotpluggable hardware. If it does, write a driver
-to use the [[!template id=man name=uvm_hotplug section=9]] api.
-
-An example of [[!template id=man name=uvm_hotplug section=9]] api's
-application can be found in
-[[!template id=man name=balloon section=4]].
\ No newline at end of file
+     An example of [[!template id=man name=uvm_hotplug section=9]] api's
+     application can be found in
+     [[!template id=man name=balloon section=4]].
\ No newline at end of file

Add an FAQ about uvm_hotplug(9)
Index: wikisrc/features.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/features.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/features.mdwn	2 Apr 2014 06:01:46 -0000	1.2
+++ wikisrc/features.mdwn	29 Dec 2016 16:54:37 -0000	1.3
@@ -8,3 +8,6 @@
 ##Hardware Support
 * [[Video|features/video-hardware]]
 * [[Audio|features/audio-hardware]]
+
+##Memory
+* [[Hotplug|features/uvm_hotplug]]
\ No newline at end of file
--- /dev/null	2016-12-29 16:51:46.000000000 +0000
+++ wikisrc/features/uvm_hotplug.mdwn	2016-12-29 16:54:50.000000000 +0000
@@ -0,0 +1,65 @@
+# [[!template id=man name=uvm_hotplug section=9]] port-masters' FAQ.
+
+1. Why does it matter?
+
+As a port maintainer any architecture that needs to use the virtual memory
+sub-system of NetBSD aka uvm is affected by the
+[[!template id=man name=uvm_hotplug section=9]] change.
+
+Early boot code of every port is affected. Global variables:
+struct vm_physseg vm_physmem;
+int vm_nphysmem;
+are no longer visible. They need to be replaced by appropriate
+accessor calls in [[!template id=man name=uvm_hotplug section=9]]
+
+These calls are documented as "Utility Functions" in the
+[[!template id=man name=uvm_hotplug section=9]] manual.
+
+
+The "switchover" CVS commit log is here:
+[http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html](http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html)
+
+
+2. What files may be affected?
+
+In most of the architectures the "sys/arch/<arch_name>/<arch_name>/machdep.c"
+and "sys/arch/<arch_name>/<arch_name>/pmap.c" if they exist are usually
+affected.
+
+But this may not be a exhaustive list. Any other files that deals with pmap and
+stealing pages might also be affected.
+
+3. What does it do ?
+
+[[!template id=man name=uvm_hotplug section=9]] manages the previously exposed "vm_physmem" static array which
+used to keep track of the memory segments.
+
+In the current implementation, the array has been replaced with a
+[[!template id=man name=rbtree section=3]] backing which makes the
+data structure dynamic.
+
+An array based implementation is also provided, for backwards
+compatibility. This is the default implementation and does not provide
+hot pluggability. It is also used without 'options UVM_HOTPLUG'
+However the API itself is implementation agnostic.
+
+4. Why is it needed?
+
+With the [[!template id=man name=rbtree section=3]] backing
+implementation, the list of physical pages 
+in the system is no longer in a static array and can dynamically
+expand or collapse, hence adding new pages to the freelist from newly
+available RAM / physical memory (plug) or removing retired pages
+(unplug) via taking them off the freelist and the old vm_physmem.
+
+5. What should I do?
+
+Review the changes to your port due to this new feature. The changes
+may have been made without direct knowledge of your port architecture.
+
+See if your port has hotpluggable hardware. If it does, write a driver
+to use the [[!template id=man name=uvm_hotplug section=9]] api.
+
+An example of [[!template id=man name=uvm_hotplug section=9]] api's
+application can be found in
+[[!template id=man name=balloon section=4]].

Sync with htdocs/gallery/events.xml (add BSDCan 2017 and AsiaBSDCan 2017)
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/events.mdwn	14 Nov 2016 13:31:18 -0000	1.39
+++ wikisrc/events.mdwn	26 Dec 2016 16:24:57 -0000	1.40
@@ -7,6 +7,30 @@
 
 Future Events
 -------------
+### `Jun 2017` - BSDCAN 2017, Ottawa, Canada
+
+*June 7 - 10, Ottawa, Canada*
+
+BSDCan hosts talks and tutorials on a range of topics based
+around the BSD family of operating systems. The event is held over a
+four day period at the University of Ottawa.
+
+Please see
+[website](https://www.bsdcan.org/2017/)
+for details.
+
+### `Mar 2017` - AsiaBSDCon 2017
+
+*March 9 - 12, Tokyo University of Science, Tokyo, Japan*
+
+[AsiaBSDCon](https://2017.asiabsdcon.org/) is a
+conference for users and developers on BSD based systems.
+The conference is for anyone developing, deploying and using systems
+based on FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Darwin, and MacOS X.
+AsiaBSDCon is a technical conference and aims to collect the best
+technical papers and presentations available to ensure that the latest
+developments in our open source community are shared with the widest
+possible audience.
 
 ### `Feb 2017` - FOSDEM 2017 Brussels, Belgium
 

Advise staying up to date
Mention the 2016-12 ubuntu/46 fix.
Members: 
	ports/xen/howto.mdwn:1.135->1.136 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.135
retrieving revision 1.136
diff -u -r1.135 -r1.136
--- wikisrc/ports/xen/howto.mdwn	21 Dec 2016 16:57:10 -0000	1.135
+++ wikisrc/ports/xen/howto.mdwn	21 Dec 2016 17:03:03 -0000	1.136
@@ -126,7 +126,8 @@
 of 2016-12, security patches were released by Xen and applied to
 pkgsrc.  Xen 4.6 runs on amd64 hardware only For new installations,
 4.6 is probably the appropriate choice and it will likely soon be the
-standard approach.
+standard approach.  (If using Ubuntu guests, be sure to have the
+xentools46 from December, 2016).
 
 Xen 4.7 (released 2016-06) and 4.8 (released 2016-12) are not yet in
 pkgsrc.
@@ -243,6 +244,14 @@
 dom0.  Either the i386PAE or amd64 version of NetBSD may be used as
 domUs.
 
+Because bugs are fixed quite often, and because of Xen security
+advisories, it is good to stay up to date with NetBSD (tracking a
+stable branch), with the Xen kernel (tracking a Xen version via
+pkgsrc), and with the Xen tools.  Specifically, NetBSD (-7 and
+-current) got an important fix affecting dom0/domU timesharing in
+November, 2015, and xentools46 got a fix to enable Ubuntu guests to
+boot in December, 2016.
+
 Status
 ------
 

Adjust architecture section
Add link to "expensive syscalls on amd64" xen-devel message.
Make assorted minor improvements, including explaining how machine
size relates to sum of dom[0U] sizes.
Members: 
	ports/xen/howto.mdwn:1.134->1.135 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.134
retrieving revision 1.135
diff -u -r1.134 -r1.135
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 21:22:57 -0000	1.134
+++ wikisrc/ports/xen/howto.mdwn	21 Dec 2016 16:57:10 -0000	1.135
@@ -150,7 +150,7 @@
 xentools packages provide xm for 3.1, 3.3 and 4.1 and xl for 4.2 and up.
 
 In 4.2, you can choose to use xm by simply changing the ctl_command
-variable.
+variable and setting xend=YES in rc.conf.
 
 With xl, virtual devices are configured in parallel, which can cause
 problems if they are written assuming serial operation (e.g., updating
@@ -197,19 +197,30 @@
 Xen/dom0 is known to support both i386 and amd64 domUs.
 
 i386 dom0 and domU kernels must be PAE (except for an i386 Xen 3.1
-kernel, where one can use non-PAE for dom0 and all domUs); PAE
-versions are included in the NetBSD default build.  (Note that emacs
-(at least) fails if run on i386 with PAE when built without, and vice
-versa, presumably due to bugs in the undump code.)
-
-Because of the above, the standard approach is to use NetBSD/amd64 for
-the dom0 and therefore an amd64 Xen kernel, and to use PAE kernels for
-i386 domUs.
+kernel, where one can use non-PAE for dom0 and all domUs); PAE kernels
+are included in the NetBSD default build.  (Note that emacs (at least)
+fails if run on i386 with PAE when built without, and vice versa,
+presumably due to bugs in the undump code.)
+
+Because of the above, the standard approach is to use an amd64 Xen
+kernel and NetBSD/amd64 for the dom0.  For domUs, NetBSD/i386 (with
+the PAE kernel) and NetBSD/amd64 are in widespread use, and there is
+little to no Xen-specific reason to prefer one over the other.
 
 Note that to use an i386 dom0 with Xen 4.5 or higher, one must build
-an amd64 Xen kernel and install that on the system.  One must also use
-a PAE i386 kernel.  There is no good reason to undertake these
-contortions; you should use a NetBSD/amd64 dom0 system.
+(or obtain from pre-built packages) an amd64 Xen kernel and install
+that on the system.  (One must also use a PAE i386 kernel, but this is
+also required with an i386 Xen kernel.).  Almost no one in the
+NetBSD/Xen community does this, and the standard, well-tested,
+approach is to use an amd64 dom0.
+
+A [posting on
+xen-devel](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)
+explained that PV system call overhead was higher on amd64, and thus
+there is some notion that i386 guests are faster.  It goes on to
+caution that the total situation is complex and not entirely
+understood. On top of that caution, the post is about Linux, not
+NetBSD.  TODO: Include link to benchmarks, if someone posts them.
 
 Stability
 ---------
@@ -247,7 +258,8 @@
 (generally on the most recent quarterly branch).  The first code is
 "builds" if it builds ok, and "FAIL" for a failure to build.  The
 second code/date only appears for xenkernel* and is "works" if it runs
-ok as a dom0, and "FAIL" if it won't boot or run a domU.
+ok as a dom0 and can support a domU, and "FAIL" if it won't boot or
+run a domU.
 
 	xenkernel3 netbsd-6 i386 FAIL 201612
 	xenkernel33 netbsd-6 i386 FAIL 201612
@@ -303,7 +315,10 @@
 
 For experimenting with Xen, a machine with as little as 1G of RAM and
 100G of disk can work.  For running many domUs in productions, far
-more will be needed.
+more will be needed; e.g. 4-8G and 1T of disk is reasonable for a
+half-dozen domUs of 512M and 32G each.  Basically, the RAM and disk
+have to be bigger than the sum of the RAM/disk needs of the dom0 and
+all the domUs.
 
 Styles of dom0 operation
 ------------------------
@@ -390,13 +405,13 @@
 should not use Xen 3.1.)  Both xen and the NetBSD kernel may be (and
 typically are) left compressed.
 
-In a dom0 kernel, kernfs is mandatory for xend to communicate with the
-kernel, so ensure that /kern is in fstab.  TODO: Say this is default,
-or file a PR and give a reference.
+In a dom0, kernfs is mandatory for xend to communicate with the
+kernel, so ensure that /kern is in fstab.  (A standard NetBSD install
+should already mount /kern.)
 
 Because you already installed NetBSD, you have a working boot setup
 with an MBR bootblock, either bootxx_ffsv1 or bootxx_ffsv2 at the
-beginning of your root file system, /boot present, and likely
+beginning of your root file system, have /boot, and likely also
 /boot.cfg.  (If not, fix before continuing!)
 
 Add a line to to /boot.cfg to boot Xen.  See boot.cfg(5) for an
@@ -441,13 +456,14 @@
 
 Before NetBSD's native bootloader could support Xen, the use of
 grub was recommended.  If necessary, see the
-[old grub information](/ports/xen/howto-grub/).
+[old grub information](/ports/xen/howto-grub).
 
 The [HowTo on Installing into
 RAID-1](http://mail-index.NetBSD.org/port-xen/2006/03/01/0010.html)
 explains how to set up booting a dom0 with Xen using grub with
 NetBSD's RAIDframe.  (This is obsolete with the use of NetBSD's native
-boot.)
+boot.  Now, just create a system with RAID-1, and alter /boot.cfg as
+described above.)
 
 Configuring Xen
 ---------------

Add missing space. Completely different feeling compared to the usual removals.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.133
retrieving revision 1.134
diff -u -r1.133 -r1.134
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 20:59:49 -0000	1.133
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 21:22:57 -0000	1.134
@@ -190,7 +190,7 @@
 
 Xen, the dom0 system, and each domU system can be either i386 or
 amd64.  When building a xenkernel package, one obtains an i386 Xen
-kernel on an i386 host, and anamd64 Xen kernel on an amd64 host.  If
+kernel on an i386 host, and an amd64 Xen kernel on an amd64 host.  If
 the Xen kernel is i386, then the dom0 kernel and all domU kernels must
 be i386.  With an amd64 Xen kernel, an amd64 dom0 kernel is known to
 work, and an i386 dom0 kernel should in theory work.  An amd64

Explain xen/dom0 arch better
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.132
retrieving revision 1.133
diff -u -r1.132 -r1.133
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:59:38 -0000	1.132
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 20:59:49 -0000	1.133
@@ -81,6 +81,11 @@
 which version to choose.  Versions not in pkgsrc and older unsupported
 versions of NetBSD are intentionally ignored.
 
+The term "amd64" is used to refer to both the NetBSD port and to the
+hardware architecture on which it runs.  (Such hardware is made by
+both Intel and AMD, and in 2016 a normal PC has this CPU
+architecture.)
+
 Xen
 ---
 
@@ -89,38 +94,39 @@
 but note that both packages must be installed together and must have
 matching versions.
 
-xenkernel3 provides Xen 3.1.  It is no longer maintained by Xen, and the last applied security patch was in
-2011. Thus, it should not be used.  It supports PCI passthrough,
-which is why people use it anyway. Xen 3.1 supports i386, both PAE and
-non-PAE.
+xenkernel3 provides Xen 3.1.  It is no longer maintained by Xen, and
+the last applied security patch was in 2011. Thus, it should not be
+used.  It supports PCI passthrough, which is why people use it anyway.
+Xen 3.1 runs on i386 (both non-PAE and PAE) and amd64 hardware.
 
 xenkernel33 provides Xen 3.3.  It is no longer maintained by Xen, and
 the last applied security patch was in 2012.  Thus, it should not be
-used.  Xen 3.3 supports i386, but only in PAE mode.  There are no good
+used.  Xen 3.3 runs on i386 PAE and amd64 hardware.  There are no good
 reasons to run this version.
 
 xenkernel41 provides Xen 4.1.  It is no longer maintained by Xen, but
-as of 2016-12 received backported security patches.  Xen 4.1 supports
-i386, but only in PAE mode.  There are no good reasons to run this
+as of 2016-12 received backported security patches.  Xen 4.1 runs on
+i386 PAE and amd64 hardware.  There are no good reasons to run this
 version.
 
 xenkernel42 provides Xen 4.2.  It is no longer maintained by Xen, but
-as of 2016-12 received backported security patches.  Xen 4.2 supports
-i386, but only in PAE mode.  The only reason to run this is if you
-need to use xm instead of xl, or if you need to run an i386 dom0
-(because your hardware is i386 only).
+as of 2016-12 received backported security patches.  Xen 4.2 runs on
+i386 PAE and amd64 hardware.  The only reason to run this is if you
+need to use xm instead of xl, or if you need to run on hardware that
+supports i386 but not amd64.  (This might also be useful if you need
+an i386 dom0, if it turns out that an amd64 Xen kernel and an i386
+dom0 is problematic.)
 
 xenkernel45 provides Xen 4.5.  As of 2016-12, security patches were
-released by Xen and applied to pkgsrc.  Xen 4.5 requires using a dom0
-running NetBSD's amd64 port (Intel or AMD hardware is fine), but domUs
-can be amd64 or i386 PAE.  While slightly old, n4.5 has been tested and
-run by others, so it is the conservative choice.
+released by Xen and applied to pkgsrc.  Xen 4.5 runs on amd64 hardware
+only.  While slightly old, 4.5 has been tested and run by others, so
+it is the conservative choice.
 
 xenkernel46 provides Xen 4.6.  It is new to pkgsrc as of 2016-05.  As
 of 2016-12, security patches were released by Xen and applied to
-pkgsrc.  Xen 4.6 similarly requires a NetBSD/amd64 dom0, but domUs can
-be amd64 or i386 PAE.  For new installations, 4.6 is probably the
-appropriate choice and it will likely soon be the standard approach.
+pkgsrc.  Xen 4.6 runs on amd64 hardware only For new installations,
+4.6 is probably the appropriate choice and it will likely soon be the
+standard approach.
 
 Xen 4.7 (released 2016-06) and 4.8 (released 2016-12) are not yet in
 pkgsrc.
@@ -178,30 +184,32 @@
 Architecture
 ------------
 
-Xen itself can run on i386 (Xen < 3.1) or amd64 machines (all Xen
+Xen itself can run on i386 (Xen < 4.2) or amd64 hardware (all Xen
 versions).  (Practically, almost any computer where one would want to
 run Xen today supports amd64.)
 
-Xen, the dom0 kernel, and each domU kernel can be either i386 or
-amd64.  When building a xenkernel package, one obtains i386 on an i386
-host, and amd64 on an amd64 host.  If the Xen kernel is i386, then the
-dom0 kernel and all domU kernels must be i386.  With an amd64 Xen
-kernel, an amd64 dom0 kernel is known to work, and an i386PAE dom0
-kernel should in theory work.  An amd64 Xen/dom0 is known to support
-both i386PAE and amd64 domUs.
-
-i386 dom0 and domU kernels must be PAE (except for Xen 3.1); these are
-built by default.  (Note that emacs (at least) fails if run on i386
-with PAE when built without, and vice versa, presumably due to bugs in
-the undump code.)
-
-Because of the above, the standard approach is to use amd64 for the
-dom0.
-
-Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify
-if this is about the CPU, the Xen kernel, or the dom0 kernel having to
-be amd64.
-
+Xen, the dom0 system, and each domU system can be either i386 or
+amd64.  When building a xenkernel package, one obtains an i386 Xen
+kernel on an i386 host, and anamd64 Xen kernel on an amd64 host.  If
+the Xen kernel is i386, then the dom0 kernel and all domU kernels must
+be i386.  With an amd64 Xen kernel, an amd64 dom0 kernel is known to
+work, and an i386 dom0 kernel should in theory work.  An amd64
+Xen/dom0 is known to support both i386 and amd64 domUs.
+
+i386 dom0 and domU kernels must be PAE (except for an i386 Xen 3.1
+kernel, where one can use non-PAE for dom0 and all domUs); PAE
+versions are included in the NetBSD default build.  (Note that emacs
+(at least) fails if run on i386 with PAE when built without, and vice
+versa, presumably due to bugs in the undump code.)
+
+Because of the above, the standard approach is to use NetBSD/amd64 for
+the dom0 and therefore an amd64 Xen kernel, and to use PAE kernels for
+i386 domUs.
+
+Note that to use an i386 dom0 with Xen 4.5 or higher, one must build
+an amd64 Xen kernel and install that on the system.  One must also use
+a PAE i386 kernel.  There is no good reason to undertake these
+contortions; you should use a NetBSD/amd64 dom0 system.
 
 Stability
 ---------

Resolve which-daemon confusion
There are two issues: 3 vs 4, and xm vs xl. Resolve after discussion
with bouyer@.
Members: 
	ports/xen/howto.mdwn:1.131->1.132 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.131
retrieving revision 1.132
diff -u -r1.131 -r1.132
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:51:53 -0000	1.131
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:59:38 -0000	1.132
@@ -456,18 +456,17 @@
 4.2 and up packages use xl.  To use xm with 4.2, edit xendomains to
 use xm instead.
 
-For "xm", you should enable xend and xenbackendd:
+For 3.1 and 3.3, you should enable xend and xenbackendd:
 
         xend=YES
         xenbackendd=YES
 
-For "xl", you should enable xend and xencommons (xenstored).  Trying
-to use xl without xencommons=YES will result in a hang; it is
-necessary to hit ^C on the console to let the machine finish booting.
-TODO: Check if xend really should be used, and if not why it is
-installed.
+For 4.1 and up, you should enable xencommons.  Not enabling xencommons
+will result in a hang; it is necessary to hit ^C on the console to let
+the machine finish booting.  If you are using xm (default in 4.1, or
+if you changed xendomains in 4.2), you should also enable xend:
 
-        xend=YES
+        xend=YES # only if using xm, and only installed <= 4.2
         xencommons=YES
 
 TODO: Recommend for/against xen-watchdog.

Add a comment
Contact | Disclaimer | Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
NetBSD® is a registered trademark of The NetBSD Foundation, Inc.