Recent changes to this wiki:

Refer to the original Pi as first generation.
Add Pi Zero & Pi 3.
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Mar 2017 15:53:47 -0000	1.47
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	21 Apr 2017 14:48:31 -0000	1.48
@@ -114,7 +114,7 @@
          ...
 
  - Besides the "netbsd" kernel in ELF format, there is also a "netbsd.bin" kernel that is in a format that the Raspberry can boot.
- - Depending on your hardware version, copy this either to /boot/kernel.img (old/V1 hardware) or to /boot/kernel7.img (new/V2 hardware)
+ - Depending on your hardware version, copy this either to /boot/kernel.img (First generation Pi, Pi Zero hardware) or to /boot/kernel7.img (Pi 2, Pi 3 hardware)
  - reboot
 
 # Wireless Networking

Markdown. no indenting normal text, even though my editor syntax highlights it.
Index: wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	15 Apr 2017 06:01:49 -0000	1.5
+++ wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	15 Apr 2017 06:09:22 -0000	1.6
@@ -67,7 +67,7 @@
 
     # newfs /dev/rwd0x
 
-    Replacing x with the partition name.
+Replacing x with the partition name.
 
 Note: Don't care about error messages that newfs couldn't touch the disklabel - that's right since we've created everything with pdisk.
 

newfs also needs rwd0x and not wd0x, from timothy in comment.
Expand that x is the partition name, in case it's not obvious.
Members: 
	tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn:1.4->1.5 

Index: wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	15 Apr 2017 05:45:49 -0000	1.4
+++ wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	15 Apr 2017 06:01:49 -0000	1.5
@@ -65,7 +65,9 @@
 
 Now newfs your partitions:
 
-    # newfs /dev/wd0x
+    # newfs /dev/rwd0x
+
+    Replacing x with the partition name.
 
 Note: Don't care about error messages that newfs couldn't touch the disklabel - that's right since we've created everything with pdisk.
 

Replace guide with a single command.
isn't setxkbmap amazing?
Index: wikisrc/tutorials/how_to_swap_cap_lock_with_escape.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_swap_cap_lock_with_escape.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/tutorials/how_to_swap_cap_lock_with_escape.mdwn	5 Feb 2012 07:14:36 -0000	1.2
+++ wikisrc/tutorials/how_to_swap_cap_lock_with_escape.mdwn	15 Apr 2017 05:56:39 -0000	1.3
@@ -4,22 +4,6 @@
 
 Well, we need tab, but most of us don't use the caps key, so we can just swap them right away. 
 
-You only need to create a file with this content: 
+You can add the following to your ~/.xinitrc file, or run as a command: 
     
-    ! Swap caps lock and escape
-    remove Lock = Caps_Lock
-    keysym Escape = Caps_Lock
-    keysym Caps_Lock = Escape
-    add Lock = Caps_Lock
-    
-
-Or you can just have them both as an Escape key. 
-    
-    ! Making caps acting as esc
-    remove Lock = Caps_Lock
-    keysym Caps_Lock = Escape
-    
-
-You can save it to a file something like .swapesc and call it from .xinitrc: 
-    
-    xmodmap ~/.swapesc
+    setxkbmap -option "caps:swapescape"

specify rc.conf flags which work.
Index: wikisrc/tutorials/how_to_use_wpa_supplicant.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_wpa_supplicant.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/tutorials/how_to_use_wpa_supplicant.mdwn	14 Apr 2016 21:56:08 -0000	1.7
+++ wikisrc/tutorials/how_to_use_wpa_supplicant.mdwn	15 Apr 2017 05:51:41 -0000	1.8
@@ -33,7 +33,7 @@
  to add
 
     wpa_supplicant=YES
-    wpa_supplicant_flags="${wpa_supplicant_flags} -i iwn0"
+    wpa_supplicant_flags="-i iwn0 -c /etc/wpa_supplicant.conf"
 
 If your LAN is configured with DHCP, you will likely also want
  `dhcpcd=YES` in `/etc/rc.conf` to run [dhcpcd](http://netbsd.gw.com/cgi-bin/man-cgi?dhcpcd+8+NetBSD-current).

Pulseaudio doesn't need hald, it can do with just dbus in my experience
omit the mention of configuring - it works without changes to configs
Index: wikisrc/tutorials/using_pulseaudio.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/using_pulseaudio.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/tutorials/using_pulseaudio.mdwn	22 Aug 2014 19:02:14 -0000	1.6
+++ wikisrc/tutorials/using_pulseaudio.mdwn	15 Apr 2017 05:48:58 -0000	1.7
@@ -10,19 +10,10 @@
 
 ## Pre-requisites
 
-pulseaudio needs hald to run. So if it's not running already:
+pulseaudio needs dbus to run. So if it's not running already:
 
-    cp /usr/pkg/share/examples/rc.d/hal /etc/rc.d
-    echo hal=YES >> /etc/rc.conf
-
-## Configure it
-
-pulseaudio needs the oss audio sink to be configured, i.e., it needs to be told
-about the sound card it should use. Thus, edit /usr/pkg/etc/pulse/default.pa,
-uncomment the "load-module module-oss" line and change it to point to the correct
-audio device, usually audio0:
-
-    load-module module-oss device="/dev/audio0" sink_name=output source_name=input
+    cp /usr/pkg/share/examples/rc.d/dbus /etc/rc.d
+    echo dbus=YES >> /etc/rc.conf
 
 #  Third Party Applications 
 

dhclient->dhcpcd.
mention fstab should have a ptyfs entry. heads by timothy in comment.
Members: 
	tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn:1.3->1.4 

Index: wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	15 Apr 2017 05:42:02 -0000	1.3
+++ wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	15 Apr 2017 05:45:49 -0000	1.4
@@ -87,6 +87,7 @@
     # echo /dev/wd0g /var ffs rw 1 2 >> /mnt2/etc/fstab
     # echo /dev/wd0f /usr ffs rw 1 2 >> /mnt2/etc/fstab
     # echo /dev/wd0h /home ffs rw 1 2 >> /mnt2/etc/fstab
+    # echo ptyfs /dev/pts ptyfs rw 0 0 >> /mnt2/etc/fstab
 
 #Umount
 
@@ -130,13 +131,13 @@
     rc_configured=YES
     wscons=YES
     hostname=my.powermac.g4
-    dhclient=yes
+    dhcpcd=yes
 
-Please use /etc/ifconfig.gem0 if you don't have a DHCP Server in your network and remove dhclient=yes from rc.conf
+Please use /etc/ifconfig.gem0 if you don't have a DHCP Server in your network and remove dhcpcd=yes from rc.conf
 
-Right now, set up your network. Either use dhclient to configure your network via DHCP
+Right now, set up your network. Either use dhcpcd to configure your network via DHCP
 
-    # dhclient gem0  
+    # dhcpcd gem0  
 
 or manually specify your network using ifconfig.
 

No need to fetch pdisk, so omit this part.
heads by timothy in comment.
Members: 
	tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn:1.2->1.3 

Index: wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	15 Apr 2017 05:40:44 -0000	1.2
+++ wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	15 Apr 2017 05:42:02 -0000	1.3
@@ -24,17 +24,6 @@
 
 Please configure now your integrated gem0 (100baseTX) or wi0 (WLAN) NIC to have an internet connection to match your local network configuration and exit the sysinst program.
 
-#Fetching pdisk
-
-We will need to fetch pdisk, the partition tool to partition the hard disk. To fetch pdisk from your local ftp mirror enter:
-
-    # cd /sbin
-    # ftp -a ftp://ftp3.de.netbsd.org/pub/NetBSD/arch/macppc/netbsd-pdisk/netbsd-pdisk.macppc-1-6
-
-and rename it to pdisk
-
-    # mv netbsd-pdisk.macppc-1-6 pdisk
-	
 #Partitioning the hard disk
 
 Now we're going to partition the disk. Enter:

pdisk /dev/rwd0c instead of /dev/wd0c (doesn't work)
Index: wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	20 Nov 2011 20:55:21 -0000	1.1
+++ wikisrc/tutorials/how_to_install_netbsd_on_a_power_macintosh_g4___40__grey__41__.mdwn	15 Apr 2017 05:40:44 -0000	1.2
@@ -39,7 +39,7 @@
 
 Now we're going to partition the disk. Enter:
 
-    # pdisk /dev/wd0c
+    # pdisk /dev/rwd0c
 
 to start the pdisk program. Create a new partition map using i.
 

SD card device is ld0, update bootargs example
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- wikisrc/ports/evbarm/tegra.mdwn	14 Apr 2017 11:13:55 -0000	1.44
+++ wikisrc/ports/evbarm/tegra.mdwn	14 Apr 2017 12:09:08 -0000	1.45
@@ -57,7 +57,7 @@
 
 [[!template  id=programlisting text="""
 $ cat boot.txt
-setenv bootargs root=ld1a
+setenv bootargs root=ld0a
 fatload mmc 1:1 0x90000000 netbsd.ub
 fatload mmc 1:1 ${fdt_addr_r} tegra124-jetson-tk1.dtb
 fdt addr ${fdt_addr_r}

Fix list (maybe)
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- wikisrc/ports/evbarm/tegra.mdwn	14 Apr 2017 11:12:44 -0000	1.43
+++ wikisrc/ports/evbarm/tegra.mdwn	14 Apr 2017 11:13:55 -0000	1.44
@@ -100,8 +100,8 @@
 
 For the nouveau driver to load successfully, firmware is required:
 
- - Install the [sysutils/tegra-firmware](http://pkgsrc.se/sysutils/tegra-firmware) package from pkgsrc.
- - Extract the contents of [tegra-nouveau-firmware.tar.gz](http://cdn.netbsd.org/pub/NetBSD/misc/jmcneill/tegra/tegra-nouveau-firmware.tar.gz) to ''/libdata/firmware/nouveau''.
+* Install the [sysutils/tegra-firmware](http://pkgsrc.se/sysutils/tegra-firmware) package from pkgsrc.
+* Extract the contents of [tegra-nouveau-firmware.tar.gz](http://cdn.netbsd.org/pub/NetBSD/misc/jmcneill/tegra/tegra-nouveau-firmware.tar.gz) to ''/libdata/firmware/nouveau''.
 
 You should see the following messages at boot:
 

Fix list (I think)
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- wikisrc/ports/evbarm/tegra.mdwn	14 Apr 2017 11:11:38 -0000	1.42
+++ wikisrc/ports/evbarm/tegra.mdwn	14 Apr 2017 11:12:44 -0000	1.43
@@ -99,6 +99,7 @@
 """]]
 
 For the nouveau driver to load successfully, firmware is required:
+
  - Install the [sysutils/tegra-firmware](http://pkgsrc.se/sysutils/tegra-firmware) package from pkgsrc.
  - Extract the contents of [tegra-nouveau-firmware.tar.gz](http://cdn.netbsd.org/pub/NetBSD/misc/jmcneill/tegra/tegra-nouveau-firmware.tar.gz) to ''/libdata/firmware/nouveau''.
 

Describe how to enable GPU (nouveau) support.
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- wikisrc/ports/evbarm/tegra.mdwn	13 Apr 2017 20:56:52 -0000	1.41
+++ wikisrc/ports/evbarm/tegra.mdwn	14 Apr 2017 11:11:38 -0000	1.42
@@ -90,6 +90,37 @@
 EndSection
 """]]
 
+# GPU (nouveau)
+
+To enable the GPU, add the following before the ''bootm'' command in the boot script:
+
+[[!template  id=programlisting text="""
+fdt set /gpu@0,57000000 status okay
+"""]]
+
+For the nouveau driver to load successfully, firmware is required:
+ - Install the [sysutils/tegra-firmware](http://pkgsrc.se/sysutils/tegra-firmware) package from pkgsrc.
+ - Extract the contents of [tegra-nouveau-firmware.tar.gz](http://cdn.netbsd.org/pub/NetBSD/misc/jmcneill/tegra/tegra-nouveau-firmware.tar.gz) to ''/libdata/firmware/nouveau''.
+
+You should see the following messages at boot:
+
+[[!template  id=programlisting text="""
+nouveau0 at fdt0: GPU
+drm kern info: nouveau  [  DEVICE][nouveau0] BOOT0  : 0x0ea000a1
+drm kern info: nouveau  [  DEVICE][nouveau0] Chipset: GK20A (NVEA)
+drm kern info: nouveau  [  DEVICE][nouveau0] Family : NVE0
+drm kern info: nouveau  [     PFB][nouveau0] RAM type: stolen system memory
+drm kern info: nouveau  [     PFB][nouveau0] RAM size: 2019 MiB
+drm kern info: nouveau  [     PFB][nouveau0]    ZCOMP: 0 tags
+drm kern info: nouveau  [  PGRAPH][nouveau0] using external firmware
+drm kern info: nouveau  [     DRM] VRAM: 2019 MiB
+drm kern info: nouveau  [     DRM] GART: 1048576 MiB
+drm kern error: nouveau E[   PFIFO][nouveau0] unsupported engines 0x00000030
+drm kern error: nouveau E[     DRM] failed to create ce channel, -22
+drm kern info: nouveau  [     DRM] MM: using GRCE for buffer copies
+nouveau0: initialized nouveau 1.1.1 20120801 on minor 1
+"""]]
+
 # dmesg
 
 [[!template  id=programlisting text="""

Take XHCI out of TODO
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- wikisrc/ports/evbarm/tegra.mdwn	13 Apr 2017 20:32:07 -0000	1.40
+++ wikisrc/ports/evbarm/tegra.mdwn	13 Apr 2017 20:56:52 -0000	1.41
@@ -21,6 +21,8 @@
  - Watchdog timer
  - SDMMC [[!template id=man name="sdhc" section="4"]] controller
  - USB 2.0 [[!template id=man name="ehci" section="4"]] controller
+ - USB 3.0 [[!template id=man name="xhci" section="4"]] controller
+   - Requires the [sysutils/tegra-firmware](http://pkgsrc.se/sysutils/tegra-firmware) package to be installed.
  - PCI express
  - SATA [[!template id=man name="ahcisata" section="4"]] controller
  - HDMI
@@ -43,7 +45,6 @@
  - APB DMA
  - Audio Hub (AHUB)
  - GPU (nouveau)
- - USB 3.0 [[!template id=man name="xhci" section="4"]] controller
  - SPI controller
  - PWM controller
  - PCIe MSI support

Update dtb reference for new Jetson TK1 dtb based on Linux 4.10.10 tree.
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/ports/evbarm/tegra.mdwn	13 Apr 2017 20:30:52 -0000	1.39
+++ wikisrc/ports/evbarm/tegra.mdwn	13 Apr 2017 20:32:07 -0000	1.40
@@ -52,7 +52,7 @@
 
 # Generating a boot script
 
-The Tegra kernels need a .dtb for your board to boot. The dtb here was updated on 18th June 2016 to fix an issue with the USB port. [NVIDIA Jetson TK1 .dtb](http://ftp.netbsd.org/pub/NetBSD/misc/skrll/tegra/tegra124-jetson-tk1.dtb)
+The Tegra kernels need a .dtb for your board to boot. The dtb here was updated on 2017-04-13 and is generated from a Linux 4.10.10 source tree. [NVIDIA Jetson TK1 .dtb](http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/tegra/tegra124-jetson-tk1.dtb)
 
 [[!template  id=programlisting text="""
 $ cat boot.txt

try to tickle issues with web editing the page
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- wikisrc/ports/evbarm/tegra.mdwn	18 Jun 2016 18:35:55 -0000	1.38
+++ wikisrc/ports/evbarm/tegra.mdwn	13 Apr 2017 20:30:52 -0000	1.39
@@ -364,3 +364,5 @@
 - [Hardware documentation](https://developer.nvidia.com/hardware-design-and-development)
 - [Linux For Tegra](https://developer.nvidia.com/linux-tegra)
 - [Device Tree](http://www.devicetree.org)
+
+.

Add simplified installation instructions for NetBSD -current after
20170412.
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- wikisrc/ports/evbarm/odroid-c1.mdwn	1 Apr 2017 10:19:27 -0000	1.27
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	12 Apr 2017 23:56:35 -0000	1.28
@@ -28,7 +28,28 @@
  - I2C
  - Audio
 
-# Installation
+# Installation (NetBSD -current after 20170412)
+
+* Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *armv7.img*
+* Build U-Boot for ODROID-C1 <https://github.com/hardkernel/u-boot/tree/odroidc-v2011.03>
+  * Pre-built binaries here: <http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/odroidc1/u-boot-odroidc-v2011.03-20150308.tar.gz>
+* Write the bootloader to the empty space at the start of the base image:
+[[!template  id=programlisting text="""
+# dd if=bl1.bin.hardkernel of=armv7.img bs=1 count=442 conv=notrunc
+# dd if=bl1.bin.hardkernel of=armv7.img bs=512 skip=1 seek=1 conv=notrunc
+# dd if=u-boot.bin of=armv7.img bs=512 seek=64 conv=notrunc
+"""]]
+* Write the image to an SD card.
+* Edit *boot.ini* on the MS-DOS partition. Note that the default boot.ini has `console=fb` in `bootargs`, which you should remove if you want serial console:
+[[!template  id=programlisting text="""
+ODROIDC-UBOOT-CONFIG
+
+setenv bootargs "root=ld0a awge0.mac-address=${ethaddr} console=fb"
+setenv bootcmd "fatload mmc 0:1 0x21000000 netbsd-ODROID-C1.ub; bootm 0x21000000"
+run bootcmd
+"""]] 
+
+# Installation (NetBSD 7.0/7.1)
 
 * Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *armv7.img*
 * Build U-Boot for ODROID-C1 <https://github.com/hardkernel/u-boot/tree/odroidc-v2011.03>

DTrace on armv4 confirmed using hpcarm port on a Jornada 720.
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.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	22 Mar 2017 16:04:46 -0000	1.17
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	8 Apr 2017 21:38:18 -0000	1.18
@@ -8,7 +8,7 @@
 DTrace is a work-in-progress effort and it is for x86 systems and some arm boards.
 
 * i386 and amd64
-* earm* (evbarm and armv4 based ports (armv4 side requires further testing but system is built with CTF)
+* earm* (evbarm and armv4 based ports)
 
 ## Supported providers
 

Say more about my NetBSDoings.
Index: wikisrc/users/schmonz.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/schmonz.mdwn,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- wikisrc/users/schmonz.mdwn	2 Aug 2016 22:51:45 -0000	1.29
+++ wikisrc/users/schmonz.mdwn	8 Apr 2017 03:23:49 -0000	1.30
@@ -1,6 +1,28 @@
 [[schmonz_73x73.jpg]]
 
-I attended, and took some quick notes during, [[pkgsrccon2014]].
+## This site
 
-If you've got an idea about how this wiki ought to work, edit the
-[[wiki/todo]] list! Here's what's been [[wiki/todo/done]] so far.
+You can mostly point a finger at me for how `wiki.netbsd.org` works, or doesn't.
+If you've got an idea about how it ought to, edit the [[wiki/todo]] list!
+Here's what's been [[wiki/todo/done]] so far.
+
+## pkgsrcCon talks
+
+- 2014: [pkgsrc Design Goals](https://schmonz.com/2014/06/21/pkgsrccon-2014-pkgsrc-design-goals/) (and [[quick notes from the conference|pkgsrccon2014]])
+- 2013: [Rehabilitating pkglint](https://schmonz.com/2013/03/23/pkgsrccon-2013-rehabilitating-pkglint/)
+- 2010: [What pkgsrc Needs Most](https://schmonz.com/2010/05/30/pkgsrccon-2010-what-pkgsrc-needs-most/)
+- 2008: [The Wrapper Framework: Then, Now, and Soon](https://schmonz.com/2008/06/15/pkgsrccon-2008-the-wrapper-framework-then-now-and-soon/)
+- 2007: [Packaging djbware](https://schmonz.com/2007/04/29/pkgsrccon-2007-packaging-djbware/),
+  [pkgsrc on Mac OS X](https://schmonz.com/2007/04/28/pkgsrccon-2007-pkgsrc-on-mac-os-x/)
+- 2005: [Packaging Complex Software](https://schmonz.com/2005/05/08/pkgsrccon-2005-packaging-complex-software/),
+  [pkgsrc on Mac OS X](https://schmonz.com/2005/05/07/pkgsrccon-2005-pkgsrc-on-mac-os-x/)
+
+## qmail from pkgsrc on NetBSD
+
+- 2017: [Automation for mail hosting](https://schmonz.com/2017/03/27/automation-for-mail-hosting/),
+  [qmail + SMTP AUTH + TLS redux](https://schmonz.com/2017/01/18/qmail-smtp-auth-tls-redux/)
+- 2007: [qmail + spam filtering](https://schmonz.com/2007/03/07/qmail-spam-filtering/),
+  [qmail + IMAP-before-SMTP](https://schmonz.com/2007/02/28/qmail-imap-before-smtp/),
+  [qmail + NetBSD nightly maintenance](https://schmonz.com/2007/02/07/qmail-netbsd-nightly-maintenance/),
+  [qmail + badrcptto - patches](https://schmonz.com/2007/01/15/qmail-badrcptto-patches/),
+  [qmail + SMTP AUTH + SSL + TLS - patches](https://schmonz.com/2007/01/14/qmail-smtp-auth-ssl-tls-patches/)

Update my face.
Index: wikisrc/users/schmonz/schmonz_73x73.jpg
===================================================================
RCS file: /cvsroot/wikisrc/users/schmonz/schmonz_73x73.jpg,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
Binary files /tmp/cvskMfCmV and /tmp/cvskBLEhc differ

Removed Xen since it is already supported; added simh instead.
Removed overly detailed milestones. Change "multiple" in title
to "additional", since multiple VM systems are alerady supprted.
Index: wikisrc/projects/project/anita-vms.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/anita-vms.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/anita-vms.mdwn	28 Feb 2017 18:13:42 -0000	1.5
+++ wikisrc/projects/project/anita-vms.mdwn	3 Apr 2017 14:34:31 -0000	1.6
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Make Anita support multiple virtual machine systems"
+title="Make Anita support additional virtual machine systems"
 
 contact="""
 [tech-userlevel](mailto:tech-userlevel@NetBSD.org)
@@ -16,19 +16,11 @@
 description="""
 [Anita](http://www.gson.org/netbsd/anita/) is a tool for automated testing of NetBSD. Anita automates the process of downloading a NetBSD distribution, installing it into a fresh virtual machine and running the ATF tests in the distribution in a fully-automated manner. Originally, the main focus of Anita was on testing the sysinst installation procedure and on finding regressions that cause the system to fail to install or boot, but Anita is now used as the canonical platform for running the ATF test suite distributed with NetBSD. (You can see the results of such tests in the [Test Run Logs](http://releng.netbsd.org/test-results.html) page.)
 
-At the moment, Anita only supports qemu as the system to create the virtual machine with. qemu gives us the ability to test several ports of NetBSD (because qemu emulates many different architectures), but qemu is very slow because it lacks hardware virtualization support in NetBSD. The goal of this project is to extend Anita to support other virtual machine systems.
+At the moment, Anita supports qemu and Xen as the system to create the virtual machine with. qemu gives us the ability to test several ports of NetBSD (because qemu emulates many different architectures), but qemu is very slow because it lacks hardware virtualization support in NetBSD. The goal of this project is to extend Anita to support other virtual machine systems.
 
-There are many virtual machine systems out there, but this project focuses on adding support to, at least, the following two: [Xen](http://www.xen.org/) and [VirtualBox](http://www.virtualbox.org/). Xen because NetBSD has [native support to run as a dom0 and a domU](http://www.netbsd.org/ports/xen/) so Anita could be used out of the box. VirtualBox because it is the canonical free virtual machine system for workstation setups.
+There are many virtual machine systems out there, but this project focuses on adding support to at least [VirtualBox](http://www.virtualbox.org/), because it is the canonical free virtual machine system for workstation setups.  Another possibility would be adding support for [SIMH][http://simh.trailing-edge.com] for running NetBSD/vax.
 
-This project has the following milestones, in this order:
-
-1. Abstract the VM-specific code in Anita to provide a modular interface that supports different virtual machines at run time. This will result in one single module implementation for qemu.
-2. Create a module to provide support for Xen dom0.
-3. Create a module to provide support for VirtualBox.
-4. Update the pkgsrc package misc/py-anita to support the different virtual machine systems. This must be done by providing new packages, not by using package options.
-5. If time permits: add extra modules.
-
-The obvious deliverable is a new version of Anita that can use any of the three mentioned virtual machines at run time, without having to be rebuilt, and the updated pkgsrc packages to install such updated version.
+The obvious deliverable is a new version of Anita that can use any of the mentioned virtual machines at run time, without having to be rebuilt, and the updated pkgsrc packages to install such updated version.
 
 The candidate is supposed to know Python and be familiar with at least one virtual machine system.
 """

Add missing space.
Add www host prefix to url for consistency.
Index: wikisrc/ports/zaurus.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/zaurus.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/ports/zaurus.mdwn	2 Apr 2017 17:59:54 -0000	1.16
+++ wikisrc/ports/zaurus.mdwn	2 Apr 2017 18:03:15 -0000	1.17
@@ -53,7 +53,7 @@
 * [OpenBSD Zaurus port](http://www.openbsd.org/zaurus.html)
 * [NetBSD/zaurus FAQ](http://www.NetBSD.org/ports/zaurus/faq.html)
 * SL-C750/760/860 Quick Start Guide: [English](http://www.trisoft.de/pdf/c750qse.pdf), [German](http://www.trisoft.de/pdf/c750qs.pdf)
-* SL-C1000/3000/3100/3200 Quick Start Guide: [English](http://trisoft.de/pdf/c3000qse.pdf),[German](http://www.trisoft.de/pdf/c3000qs.pdf)
+* SL-C1000/3000/3100/3200 Quick Start Guide: [English](http://www.trisoft.de/pdf/c3000qse.pdf), [German](http://www.trisoft.de/pdf/c3000qs.pdf)
 """
 
 ]]

Link to English & German translated quick start guides, produced by a TRIsoft ONLINE.
Index: wikisrc/ports/zaurus.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/zaurus.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/ports/zaurus.mdwn	2 Apr 2017 01:26:25 -0000	1.15
+++ wikisrc/ports/zaurus.mdwn	2 Apr 2017 17:59:54 -0000	1.16
@@ -52,6 +52,8 @@
 * [SHARP Zaurus support station - Developer information (including Linux source code)](http://support.ezaurus.com/developer/)
 * [OpenBSD Zaurus port](http://www.openbsd.org/zaurus.html)
 * [NetBSD/zaurus FAQ](http://www.NetBSD.org/ports/zaurus/faq.html)
+* SL-C750/760/860 Quick Start Guide: [English](http://www.trisoft.de/pdf/c750qse.pdf), [German](http://www.trisoft.de/pdf/c750qs.pdf)
+* SL-C1000/3000/3100/3200 Quick Start Guide: [English](http://trisoft.de/pdf/c3000qse.pdf),[German](http://www.trisoft.de/pdf/c3000qs.pdf)
 """
 
 ]]

Capitalise
Index: wikisrc/ports/zaurus.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/zaurus.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/ports/zaurus.mdwn	2 Apr 2017 01:23:29 -0000	1.14
+++ wikisrc/ports/zaurus.mdwn	2 Apr 2017 01:26:25 -0000	1.15
@@ -48,7 +48,7 @@
 
 """
 additional="""
-* [some install tips](https://mail-index.netbsd.org/port-zaurus/2012/02/04/msg000050.html)
+* [Some install tips](https://mail-index.netbsd.org/port-zaurus/2012/02/04/msg000050.html)
 * [SHARP Zaurus support station - Developer information (including Linux source code)](http://support.ezaurus.com/developer/)
 * [OpenBSD Zaurus port](http://www.openbsd.org/zaurus.html)
 * [NetBSD/zaurus FAQ](http://www.NetBSD.org/ports/zaurus/faq.html)

Point to the updated installation tips post.
Index: wikisrc/ports/zaurus.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/zaurus.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/ports/zaurus.mdwn	30 Mar 2017 16:06:58 -0000	1.13
+++ wikisrc/ports/zaurus.mdwn	2 Apr 2017 01:23:29 -0000	1.14
@@ -48,7 +48,7 @@
 
 """
 additional="""
-* [some install tips](http://mail-index.netbsd.org/port-zaurus/2011/05/20/msg000045.html)
+* [some install tips](https://mail-index.netbsd.org/port-zaurus/2012/02/04/msg000050.html)
 * [SHARP Zaurus support station - Developer information (including Linux source code)](http://support.ezaurus.com/developer/)
 * [OpenBSD Zaurus port](http://www.openbsd.org/zaurus.html)
 * [NetBSD/zaurus FAQ](http://www.NetBSD.org/ports/zaurus/faq.html)

typo
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- wikisrc/ports/evbarm/odroid-c1.mdwn	29 Nov 2015 22:16:21 -0000	1.26
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	1 Apr 2017 10:19:27 -0000	1.27
@@ -33,7 +33,7 @@
 * Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *armv7.img*
 * Build U-Boot for ODROID-C1 <https://github.com/hardkernel/u-boot/tree/odroidc-v2011.03>
   * Pre-built binaries here: <http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/odroidc1/u-boot-odroidc-v2011.03-20150308.tar.gz>
-* Note the location and size of the FFS partition in the * armv7.img* disklabel:
+* Note the location and size of the FFS partition in the *armv7.img* disklabel:
 [[!template  id=programlisting text="""
 # $TOOLDIR/bin/nbdisklabel -M evbarm -B le armv7.img
 ...

whitespace
Index: wikisrc/ports/acorn32.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn32.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/ports/acorn32.mdwn	15 Mar 2017 08:29:15 -0000	1.14
+++ wikisrc/ports/acorn32.mdwn	30 Mar 2017 16:06:58 -0000	1.15
@@ -15,7 +15,7 @@
 
 The port first saw light as RiscBSD in 1994 and was later transformed into
 NetBSD/arm32. In 2001, the arm32 port was split into separate ports for the
-various supported hardware types. NetBSD/acorn32 was one of these. 
+various supported hardware types. NetBSD/acorn32 was one of these.
 """
 supported_hardware="""
 ###Supported System Models
Index: wikisrc/ports/algor.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/algor.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/ports/algor.mdwn	15 Mar 2017 08:29:15 -0000	1.13
+++ wikisrc/ports/algor.mdwn	30 Mar 2017 16:06:58 -0000	1.14
@@ -20,7 +20,7 @@
 network (in ELF format) using BOOTP/TFTP.
 
 Algorithmics boards can generally be run in big- or little-endian mode, although
-NetBSD/algor currently only supports little-endian. 
+NetBSD/algor currently only supports little-endian.
 """
 supported_hardware="""
 ###Supported System Models
@@ -49,34 +49,34 @@
 ###Not Yet Supported
 
 * The PC keyboard controller on the P-4032. The interrupt handling code needs
-  some work in order to support this. 
+  some work in order to support this.
 * The Centronics port on the P-4032. This may, in fact, work, but the logic is
   apparently buggy, and the interrupts are wired up in a strange way. The device
-  is completely untested. 
+  is completely untested.
 * The floppy controller on the P-4032. The P-4032 floppy controller uses
   pseudo-DMA via a "DMA request" interrupt. Support for this function has not
-  yet been implemented. 
+  yet been implemented.
 * The PC keyboard controller on the P-5064. The interrupt handling code needs
-  some work in order to support this. 
+  some work in order to support this.
 * The Centronics port on the P-5064. This may, in fact, work, but the logic is
   apparently buggy, and the interrupts are wired up in a strange way. The device
-  is completely untested. 
+  is completely untested.
 * The on-board PCI IDE (part of the PIIX3 southbridge) on the P-5064. The PMON
   firmware does not configure the IDE controller, so NetBSD sees it as
   "disabled". Some code will have to be added to initialize the PCI IDE
-  controller before it can be used. 
+  controller before it can be used.
 * On-board USB on the PCI bus (part of the PIIX3 southbridge) on the P-5064.
   The uhci driver causes a bus error when it attempts to perform DMA, and the
-  system hangs. A bug report has been filed so that the issue can be tracked. 
+  system hangs. A bug report has been filed so that the issue can be tracked.
 * Devices plugged into the ISA slot on the P-5064. The interrupt handling code
-  needs some work in order to support this. 
+  needs some work in order to support this.
 * Devices plugged into the PCMCIA slots on the P-5064. The interrupt handling
-  code needs some work in order to support this. 
+  code needs some work in order to support this.
 * Algorithmic P-4000i -- this is a very old machine, with considerably different
   hardware than the newer Algorithmics boards. It is unlikely that NetBSD/algor
-  will ever support this machine. 
+  will ever support this machine.
 * Algorithmics P-6032 -- this is Algorithmics' latest board. Support for this
-  model is in-progress. 
+  model is in-progress.
 """
 ]]
 [[!tag tier2port]]
Index: wikisrc/ports/amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amd64.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/ports/amd64.mdwn	15 Mar 2017 08:29:15 -0000	1.20
+++ wikisrc/ports/amd64.mdwn	30 Mar 2017 16:06:58 -0000	1.21
@@ -12,7 +12,7 @@
 architecture. This covers all recent AMD and Intel models.
 
 NetBSD/amd64 is a true 64bit operating system. Running
-32-bit NetBSD/i386 binaries is supported as well; see 
+32-bit NetBSD/i386 binaries is supported as well; see
 [[!template id=man name="compat_netbsd32" section="8"]].
 
 The port was first committed to the NetBSD source tree as NetBSD/x86_64
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/ports/amiga.mdwn	15 Mar 2017 08:29:15 -0000	1.15
+++ wikisrc/ports/amiga.mdwn	30 Mar 2017 16:06:58 -0000	1.16
@@ -23,7 +23,7 @@
 
 The minimum RAM requirement is about 24 MB FASTMEM, the minimum hard disk space
 needed is about 250 MB, depending on how many system components you install.
-Check the install document for more details. 
+Check the install document for more details.
 """
 supported_hardware="""
 
@@ -85,7 +85,7 @@
   * NE2000-compatible PCI cards <sup>[\[8\]](#ftn.pci-ethernet)</sup><a name="pci-ethernet"></a> (6.0)
 
 * ARCnet controllers:
-  * A2060 ARCnet 
+  * A2060 ARCnet
 
 * ISDN controllers:
   * BSC ISDN Master
@@ -96,7 +96,7 @@
   * Individual Computers ISDN Surfer
 
 * Tape drives:
-  * Most SCSI tape drives, including Archive Viper, Cipher SCSI-2 ST150 
+  * Most SCSI tape drives, including Archive Viper, Cipher SCSI-2 ST150
 
 * Scanners: With the machine independent PINT interface integrated, these should
   work:
@@ -105,7 +105,7 @@
   * Mustek SCSI scanner <sup>[\[9\]](#ftn.scsi-scanners)</sup><a name="scsi-scanners"></a>
 
 * CD-ROM drives:
-  * Most SCSI CD-ROM drives 
+  * Most SCSI CD-ROM drives
 
 * Serial ports on these boards:
   * Amiga builtin
@@ -139,16 +139,16 @@
             </p>
           </div>
 <div id="ftn.voodoo-footnote" class="footnote">
-              <p><a href="#voodoo-footnote" class="para"><sup class="para">[3] </sup></a>3Dfx Voodoo 3 and Banshee cards are only supported with 
+              <p><a href="#voodoo-footnote" class="para"><sup class="para">[3] </sup></a>3Dfx Voodoo 3 and Banshee cards are only supported with
 	      wscons and only if installed in a compatible PCI bridge. Voodoo 4
-	      and Voodoo 5 boards might work but are untested. X server is not 
+	      and Voodoo 5 boards might work but are untested. X server is not
 	      supported on Voodoo yet. Currently Voodoo needs initialization in
 	      AmigaOS before starting the NetBSD (unless used with G-REX, which
 	      does this on a firmware level).</p>
             </div>
 <div id="ftn.cvppc-footnote" class="footnote">
               <p><a href="#cvppc-footnote" class="para"><sup class="para">[4] </sup></a>CVPPC/BVPPC cards are only supported with wscons and only
-	      with unaccelearted genfb driver. X server is not supported on 
+	      with unaccelearted genfb driver. X server is not supported on
 	      these cards yet.</p>
 	    </div>
 <div id="ftn.no-X-retina-a2410" class="footnote">
@@ -166,7 +166,7 @@
 	    cards are expected to work.</p>
 	    </div>
 <div id="ftn.pci-ethernet" class="footnote">
-            <p><a href="#pci-ethernet" class="para"><sup class="para">[8] </sup></a>PCI network cards are supported only when installed in a 
+            <p><a href="#pci-ethernet" class="para"><sup class="para">[8] </sup></a>PCI network cards are supported only when installed in a
 	    compatible PCI bridge.</p>
 	    </div>
 <div id="ftn.scsi-scanners" class="footnote">
Index: wikisrc/ports/arc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/arc.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/ports/arc.mdwn	15 Mar 2017 08:29:15 -0000	1.12
+++ wikisrc/ports/arc.mdwn	30 Mar 2017 16:06:58 -0000	1.13
@@ -11,7 +11,7 @@
 based computers which comply wih the
 [Advanced RISC Computing (ARC) specification](http://www.netbsd.org/docs/Hardware/Machines/ARC/)
 put together by the Advanced Computing Environment (ACE) Consortium in the early
-1990's, as an alternative to Intel-based PC's. 
+1990's, as an alternative to Intel-based PC's.
 
 This port originally started as NetBSD/pica port made by Per Fogelstr&ouml;m,
 and supersedes it. This port is also based on efforts done in [OpenBSD/arc](http://www.openbsd.org/arc.html).
@@ -20,7 +20,7 @@
 
 The portmaster is collecting detailed information on as many ARC implementation
 variations as possible. An explanation of how to get internal details
-[using Windows NT is available.](http://mail-index.netbsd.org/port-mips/2000/02/19/0000.html) 
+[using Windows NT is available.](http://mail-index.netbsd.org/port-mips/2000/02/19/0000.html)
 """
 supported_hardware="""
 ###Supported System Models
@@ -60,7 +60,7 @@
 * VXL frame buffer (Magnum and RISCstation 2200)
 * AD1848 audio
 

(Diff truncated)
whitespace
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	3 Aug 2016 16:11:39 -0000	1.46
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	30 Mar 2017 15:53:47 -0000	1.47
@@ -26,7 +26,7 @@
 
 	   edit cmdline.txt and remove '"console=fb"'
 
-   - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none". 
+   - Most (all?) USB-to-TTL serial adapters only connect Tx, Rx and ground, and do not connect any flow control lines. An effect of missing flow control is that you see console output, but cannot type anything. If so, adjust your serial console application's flow control settings to "none".
 
       In Kermit, the command is "set flow none".
 
@@ -113,7 +113,7 @@
           /Users/feyrer/work/NetBSD/cvs/src-current/obj.evbarm-Darwin-XXX/sys/arch/evbarm/compile/RPI2/netbsd
          ...
 
- - Besides the "netbsd" kernel in ELF format, there is also a "netbsd.bin" kernel that is in a format that the Raspberry can boot. 
+ - Besides the "netbsd" kernel in ELF format, there is also a "netbsd.bin" kernel that is in a format that the Raspberry can boot.
  - Depending on your hardware version, copy this either to /boot/kernel.img (old/V1 hardware) or to /boot/kernel7.img (new/V2 hardware)
  - reboot
 

Add missing space
Switch spelling of colour.
Index: wikisrc/ports/hpcsh/hpcsh_support_status.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/hpcsh/hpcsh_support_status.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/hpcsh/hpcsh_support_status.mdwn	15 Jan 2014 10:56:48 -0000	1.1
+++ wikisrc/ports/hpcsh/hpcsh_support_status.mdwn	30 Mar 2017 15:34:21 -0000	1.2
@@ -3,15 +3,15 @@
 [[!table data="""
 Sold in 	|Model										|CPU 			|Video 			|RAM 	|Companion Chip 	|Boot 	|PCMCIA Controller 	|Keymap 	|Xserver
 **Hewlett-Packard Models**	||
-World (Disc) 	|[Jornada 680](http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&product=59950)	|SH-3 SH7709A 133MHz	|640x240 64K color	|16MB	|HITACHI HD64461 	|Y	|Y 			|US/UK, Japanese, European, French, German, Scandinavian, Spanish	|Y
-World (Disc)	|[Jornada 690](http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&product=57664)	|SH-3 SH7709A 133MHz	|640x240 64Kcolor	|32MB	|HITACHI HD64461	|Y	|Y		|US/UK, Japanese, European, French, German, Scandinavian, Spanish|Y
-World (Disc)	|[HP 620LX](http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&product=58814#)	|SH-3 SH7709 75MHz	|640x240 256color	|16MB	|HITACHI HD64461	|Y	|Y	|US/UK, Japanese	|Y
-World (Disc)	|[Jornada 548](http://www.hp.com/jornada/products/540/overview.html)		|SH-3 SH7709A 133MHz	|240x320 64Kcolor	|32MB	|HP F1796		|N 	  	  	 
+World (Disc) 	|[Jornada 680](http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&product=59950)	|SH-3 SH7709A 133MHz	|640x240 64K colour	|16MB	|HITACHI HD64461 	|Y	|Y 			|US/UK, Japanese, European, French, German, Scandinavian, Spanish	|Y
+World (Disc)	|[Jornada 690](http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&product=57664)	|SH-3 SH7709A 133MHz	|640x240 64K colour	|32MB	|HITACHI HD64461	|Y	|Y		|US/UK, Japanese, European, French, German, Scandinavian, Spanish|Y
+World (Disc)	|[HP 620LX](http://h10025.www1.hp.com/ewfrf/wc/product?cc=us&product=58814#)	|SH-3 SH7709 75MHz	|640x240 256 colour	|16MB	|HITACHI HD64461	|Y	|Y	|US/UK, Japanese	|Y
+World (Disc)	|[Jornada 548](http://www.hp.com/jornada/products/540/overview.html)		|SH-3 SH7709A 133MHz	|240x320 64K colour	|32MB	|HP F1796		|N 	  	  	 
 **CASIO Models** ||
 Japan		|Cassiopeia A-50/51	|SH-3 SH7093 40MHz	|640x240 2bpp gray-scale	|4/8MB		|CASIO FM-7403	|N
 Japan		|Cassiopeia A-55V	|SH-3 SH7093R 80MHz	|640x240 2bpp gray-scale	|16MB		|CASIO FM-7403	|N
 **HITACHI Models**	||
-Japan		|[PERSONA HPW-50PAD](http://www.hitachi.co.jp/Prod/persona/seihin/shiyo_50pa.htm)	|SH-3 SH7709R 100MHz	|640x240 64Kcolor	|32MB	|HITACHI HD64461	|Y	|Y	|Japanese
-Japan		|[PERSONA HPW-230JC](http://www.hitachi.co.jp/Prod/persona/seihin/shiyo_230jc.htm)	|SH-3 SH7709R 100MHz	|640x240 64Kcolor	|32MB	|HITACHI HD64461	|Y	|Y
-Japan		|[PERSONA HPW-650PA](http://www.hitachi.co.jp/Prod/persona/seihin/shiyo_650pa.htm)	|SH-4 SH7750V 128MHz	|640x480 64Kcolor	|16MB	|HITACHI HD64465, HD64464(MQ100), HD64560	|Y (serial console only)	|partial	|N (keyboard access cause hang up) 	 
+Japan		|[PERSONA HPW-50PAD](http://www.hitachi.co.jp/Prod/persona/seihin/shiyo_50pa.htm)	|SH-3 SH7709R 100MHz	|640x240 64K colour	|32MB	|HITACHI HD64461	|Y	|Y	|Japanese
+Japan		|[PERSONA HPW-230JC](http://www.hitachi.co.jp/Prod/persona/seihin/shiyo_230jc.htm)	|SH-3 SH7709R 100MHz	|640x240 64K colour	|32MB	|HITACHI HD64461	|Y	|Y
+Japan		|[PERSONA HPW-650PA](http://www.hitachi.co.jp/Prod/persona/seihin/shiyo_650pa.htm)	|SH-4 SH7750V 128MHz	|640x480 64K colour	|16MB	|HITACHI HD64465, HD64464(MQ100), HD64560	|Y (serial console only)	|partial	|N (keyboard access cause hang up) 	 
 """]]

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-29 19:00:33.000000000 +0000
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF/comment_1_cc0bea24bebbae74140352791b7263d4._comment	2017-03-29 19:04:18.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-29 19:00:33.000000000 +0000
+++ wikisrc/projects/project/performance_regress.mdwn	2017-03-29 19:04:22.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-29 19:04:22.000000000 +0000
+++ /dev/null	2017-03-29 19:00:33.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-29 19:00:33.000000000 +0000
+++ wikisrc/projects/project/performance_regress.mwdn	2017-03-29 19:04:23.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-03-29 19:00:33.000000000 +0000
+++ wikisrc/projects/project/pkgsrc-chromium/comment_1_934e3961b6ab5d13d8897ab49bdfbb38._comment	2017-03-29 19:04:23.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-03-29 19:00:33.000000000 +0000
+++ wikisrc/projects/project/desktop-infrastructure/comment_2_a3ac0c57d5235df43377e255b387b1f1._comment	2017-03-29 19:04:24.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-03-29 19:00:33.000000000 +0000
+++ wikisrc/tutorials/how_to_set_up_a_xen_dom0/comment_3_4869b54ac386c98c7ef8a6d3159d2315._comment	2017-03-29 19:04:24.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-03-29 19:00:33.000000000 +0000
+++ wikisrc/users/maya.mdwn	2017-03-29 19:04:26.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-03-29 19:00:33.000000000 +0000
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	2017-03-29 19:04:26.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-03-29 19:00:33.000000000 +0000
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	2017-03-29 19:04:26.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-03-29 19:04:28.000000000 +0000
+++ /dev/null	2017-03-29 19:00:33.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-03-29 19:00:33.000000000 +0000
+++ wikisrc/ports/evbarm/raspberry_pi/comment_19_82864947fcb8737650f36e90ed1ed9b8._comment	2017-03-29 19:04:28.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-03-29 19:00:33.000000000 +0000
+++ wikisrc/netbsd-code-chat.mdwn	2017-03-29 19:04:29.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

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.