Recent changes to this wiki:

start my engine for 2020 NetBSD Japan tour
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/users/jun.mdwn	13 Jun 2019 01:27:28 -0000	1.16
+++ wikisrc/users/jun.mdwn	22 Jan 2020 04:52:48 -0000	1.17
@@ -3,11 +3,17 @@
 ## Current my job mission
 - SOUM Corporation [[http://www.soum.co.jp]],TOKYO
 - Support Open Science Framework in Japan
+- Job offer: via SOUM Corporation.
 
 ## make NetBSD booth and presentation around Japan area.
 - Open Source Conference [[https://www.ospn.jp/]] 
 - Report on [[http://mail-index.netbsd.org/netbsd-advocacy/tindex.html]]
+- [[https://github.com/ebijun/NetBSD/blob/master/Guide/OSC/OSC2020.rst]]
 - [[https://github.com/ebijun/NetBSD/blob/master/Guide/OSC/OSC2019.rst]]
+- [[https://github.com/ebijun/NetBSD/blob/master/Guide/OSC/OSC2018.rst]]
+- [[https://github.com/ebijun/NetBSD/blob/master/Guide/OSC/OSC2017.rst]]
+- [[https://github.com/ebijun/NetBSD/blob/master/Guide/OSC/OSC2016.rst]]
+- [[https://github.com/ebijun/NetBSD/blob/master/Guide/OSC/OSC2015.rst]]
 
 ## NetBSD machines in Japan
 -  [[http://www.re.soum.co.jp/~jun/asiabsdcon2019.pdf]]
@@ -15,7 +21,11 @@
 ## NetBSD Raspberry PI Images
 - [[https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README]]
 - [[ftp://ftp.netbsd.org/pub/NetBSD/misc/jun/raspberry-pi/]]
+- [[https://github.com/ebijun/NetBSD/blob/master/Guide/RPI/RPIupdate2020.rst]]
 - [[https://github.com/ebijun/NetBSD/blob/master/Guide/RPI/RPIupdate2019.rst]]
+- [[https://github.com/ebijun/NetBSD/blob/master/Guide/RPI/RPIupdate2018.rst]]
+- [[https://github.com/ebijun/NetBSD/blob/master/Guide/RPI/RPIupdate2017.rst]]
+- [[https://github.com/ebijun/NetBSD/blob/master/Guide/RPI/RPIupdate2016.rst]]
 
 ## NetBSD/pinebook status
 - [[https://github.com/ebijun/NetBSD/blob/master/pinebook/README]]
@@ -23,7 +33,10 @@
 ## update NetBSD.jp Facebook Page
 -  [[http://www.facebook.com/NetBSD.jp]]
 
-## NetBSD Guide
+## update togetter Page 
+- [[https://togetter.com/id/ebijun]]
+
+## NetBSD Travel Guide for NetBSD booth
 - [[https://github.com/ebijun/osc-demo]]
 
 ## Japan NetBSD Users' Group

Add EuroBSDCon 2020 venue
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.84
retrieving revision 1.85
diff -u -r1.84 -r1.85
--- wikisrc/events.mdwn	20 Nov 2019 10:51:17 -0000	1.84
+++ wikisrc/events.mdwn	21 Jan 2020 13:40:05 -0000	1.85
@@ -58,7 +58,7 @@
 
 ### `Sep 2020` - EuroBSDcon 2020, Vienna, Austria
 
-*September 17 - 20, 2020, Vienna, Austria*
+*September 17 - 20, 2020, The Gußhaus Campus of Vienna's Technical University, Vienna, Austria*
 
 [EuroBSDcon](https://2020.eurobsdcon.org/) is the premier European
 conference on the open source BSD operating systems attracting

Mention FDDI removal.
Index: wikisrc/attic_museum.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/attic_museum.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/attic_museum.mdwn	20 Jan 2020 14:02:35 -0000	1.14
+++ wikisrc/attic_museum.mdwn	21 Jan 2020 07:56:06 -0000	1.15
@@ -41,6 +41,9 @@
 HIPPI		|Network Protocol	|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113013.html)
 de		|Network Driver		|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113030.html)
 Token Ring	|Network Protocol	|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113037.html)
+tr		|Network Driver		|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113037.html)
 filemon		|Pseudo Device		|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113041.html)
+FDDI		|Network Protocol	|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/20/msg113058.html)
+fpa		|Network Driver		|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/20/msg113058.html)
 """]]
 

Mention de(4), Token Ring, and filemon(4) removals.
Index: wikisrc/attic_museum.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/attic_museum.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/attic_museum.mdwn	19 Jan 2020 07:59:11 -0000	1.13
+++ wikisrc/attic_museum.mdwn	20 Jan 2020 14:02:35 -0000	1.14
@@ -39,5 +39,8 @@
 uyurex		|Device Driver		|01/2020	|				|[Commit](http://mail-index.netbsd.org/source-changes/2020/01/17/msg112930.html)
 strip		|Network Driver		|01/2020	|				|[Commit](http://mail-index.netbsd.org/source-changes/2020/01/19/msg113009.html)
 HIPPI		|Network Protocol	|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113013.html)
+de		|Network Driver		|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113030.html)
+Token Ring	|Network Protocol	|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113037.html)
+filemon		|Pseudo Device		|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113041.html)
 """]]
 

global.css: sync from htdocs
Index: wikisrc/global.css
===================================================================
RCS file: /cvsroot/wikisrc/global.css,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/global.css	19 Jan 2020 21:39:26 -0000	1.14
+++ wikisrc/global.css	20 Jan 2020 06:08:22 -0000	1.15
@@ -1,7 +1,7 @@
-/* $NetBSD: global.css,v 1.14 2020/01/19 21:39:26 rillig Exp $ */
+/* $NetBSD: global.css,v 1.15 2020/01/20 06:08:22 rillig Exp $ */
 
 /* Remember to keep htdocs/globals.css and wikisrc/globals.css in sync. */
-/* See https://wiki.netbsd.org/wiki/cvs/. */
+/* See https://wiki.NetBSD.org/wiki/cvs/. */
 
 /* ##### Common Styles ##### */
 

global.css: sync from htdocs
Index: wikisrc/global.css
===================================================================
RCS file: /cvsroot/wikisrc/global.css,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/global.css	24 Sep 2019 09:02:37 -0000	1.13
+++ wikisrc/global.css	19 Jan 2020 21:39:26 -0000	1.14
@@ -1,4 +1,7 @@
-/* $NetBSD: global.css,v 1.13 2019/09/24 09:02:37 leot Exp $ */
+/* $NetBSD: global.css,v 1.14 2020/01/19 21:39:26 rillig Exp $ */
+
+/* Remember to keep htdocs/globals.css and wikisrc/globals.css in sync. */
+/* See https://wiki.netbsd.org/wiki/cvs/. */
 
 /* ##### Common Styles ##### */
 
@@ -679,21 +682,17 @@
 	Color: red;
 }
 
-.book {
-  margin: 2em;
-}
+/* The NetBSD Guide, The pkgsrc guide and other books. */
 
-.preface {
+body > .book,
+body > .preface,
+body > .part,
+body > .chapter,
+body > .appendix {
   margin: 2em;
 }
 
-.chapter {
-  margin: 2em;
-}
-
-.appendix {
-  margin: 2em;
-}
+/* end books */
 
 #twodonate input {
   min-height: 20px;
@@ -866,7 +865,6 @@
 	  width: 0px;
 	}
 
-
 	#hamburger:checked ~ .menuicon span::before {
 	  -webkit-transform: rotate(-45deg);
 	  -moz-transform: rotate(-45deg);

Mention HIPPI removal
Index: wikisrc/attic_museum.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/attic_museum.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/attic_museum.mdwn	19 Jan 2020 06:39:06 -0000	1.12
+++ wikisrc/attic_museum.mdwn	19 Jan 2020 07:59:11 -0000	1.13
@@ -38,5 +38,6 @@
 compat_osf1	|Compatibility Layer	|03/2019	|				|[Commit](https://mail-index.netbsd.org/source-changes/2019/03/25/msg104511.html)
 uyurex		|Device Driver		|01/2020	|				|[Commit](http://mail-index.netbsd.org/source-changes/2020/01/17/msg112930.html)
 strip		|Network Driver		|01/2020	|				|[Commit](http://mail-index.netbsd.org/source-changes/2020/01/19/msg113009.html)
+HIPPI		|Network Protocol	|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/19/msg113013.html)
 """]]
 

Undo filemon (surely soon to be added) but add strip and uyurex.
Index: wikisrc/attic_museum.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/attic_museum.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/attic_museum.mdwn	18 Dec 2019 07:44:08 -0000	1.11
+++ wikisrc/attic_museum.mdwn	19 Jan 2020 06:39:06 -0000	1.12
@@ -36,6 +36,7 @@
 compat_ibcs2	|Compatibility Layer	|12/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/12/29/msg101841.html)
 satlink		|Device Driver		|01/2019	|				|[Commit](https://mail-index.netbsd.org/source-changes/2019/01/27/msg102772.html)
 compat_osf1	|Compatibility Layer	|03/2019	|				|[Commit](https://mail-index.netbsd.org/source-changes/2019/03/25/msg104511.html)
-filemon		|Pseudo Device		|12/2019	|				|[Commit](https://mail-index.netbsd.org/source-changes/2019/12/18/msg112062.html)
+uyurex		|Device Driver		|01/2020	|				|[Commit](http://mail-index.netbsd.org/source-changes/2020/01/17/msg112930.html)
+strip		|Network Driver		|01/2020	|				|[Commit](http://mail-index.netbsd.org/source-changes/2020/01/19/msg113009.html)
 """]]
 

"Filesystem Fuzzing with Americal Fuzzy Lop " done by Maciej Grochowski
Index: wikisrc/projects/project/afl_filesystem_fuzzing.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/afl_filesystem_fuzzing.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/afl_filesystem_fuzzing.mdwn	4 May 2019 15:43:38 -0000	1.2
+++ wikisrc/projects/project/afl_filesystem_fuzzing.mdwn	16 Jan 2020 12:03:26 -0000	1.3
@@ -13,6 +13,7 @@
 category="analyzers"
 difficulty="medium"
 duration="3 months"
+done_by="Maciej Grochowski"
 
 description="""
 

Mark TriforceAFL as done by Akul Pillai
Index: wikisrc/projects/project/triforceafl.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/triforceafl.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/triforceafl.mdwn	23 Jan 2019 23:20:19 -0000	1.1
+++ wikisrc/projects/project/triforceafl.mdwn	16 Jan 2020 12:01:30 -0000	1.2
@@ -13,6 +13,7 @@
 category="analyzers"
 difficulty="medium"
 duration="3 months"
+done_by="Akul Pillai"
 
 description="""
 

Correct struct kevent types
Index: wikisrc/tutorials/kqueue_tutorial.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/kqueue_tutorial.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/tutorials/kqueue_tutorial.mdwn	5 Apr 2019 00:06:57 -0000	1.3
+++ wikisrc/tutorials/kqueue_tutorial.mdwn	11 Jan 2020 06:22:57 -0000	1.4
@@ -16,11 +16,11 @@
     
     struct kevent {
                 uintptr_t ident;        /* identifier for this event */
-                short     filter;       /* filter for event */
-                u_short   flags;        /* action flags for kqueue */
-                u_int     fflags;       /* filter flag value */
-                intptr_t  data;         /* filter data value */
-                void      *udata;       /* opaque user data identifier */
+                uint32_t  filter;       /* filter for event */
+                uint32_t  flags;        /* action flags for kqueue */
+                uint32_t  fflags;       /* filter flag value */
+                int64_t   data;         /* filter data value */
+                void     *udata;        /* opaque user data identifier */
     };
     
 
@@ -375,4 +375,3 @@
   2. [Kqueue: A generic and scalable event notification facility (pdf)](http://people.freebsd.org/~jlemon/papers/kqueue.pdf)
   3. [kqueue slides](http://people.freebsd.org/~jlemon/kqueue_slides/)
   4. [The Julipedia: An example of kqueue](http://julipedia.blogspot.com/2004/10/example-of-kqueue.html)
-

it's rksd_loader.img not rkspi_loader.img. from aymeric@
Index: wikisrc/ports/evbarm/rockchip.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/rockchip.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/evbarm/rockchip.mdwn	8 Jan 2020 06:50:41 -0000	1.7
+++ wikisrc/ports/evbarm/rockchip.mdwn	10 Jan 2020 03:12:40 -0000	1.8
@@ -69,7 +69,7 @@
 - Download or build **arm64.img** (64-bit) from NetBSD 9.0 or later
 - Write the image to disk: **dd if=arm64.img of=/dev/rld0d bs=1m conv=sync**
 - Install a board-specific U-Boot from pkgsrc to the SD card
-  **dd if=/usr/pkg/share/u-boot/<boardname>/rkspi_loader.img of=/dev/rld0d seek=64 conv=sync**
+  **dd if=/usr/pkg/share/u-boot/<boardname>/rksd_loader.img of=/dev/rld0d seek=64 conv=sync**
 
 If your SoC has a SATA controller and you would like to install on
 an hard disk and use a SD card only for u-boot please give a look

add a list of cpus and some boards supported.
Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/ports/aarch64.mdwn	3 Jan 2019 00:29:04 -0000	1.4
+++ wikisrc/ports/aarch64.mdwn	8 Jan 2020 07:11:25 -0000	1.5
@@ -20,7 +20,46 @@
 multiprocessor configurations, including big.LITTLE asymmetric multiprocessing.
 
 It is not yet available in a release, and will be available in NetBSD 9.0.
-"""
 
+The lists of supported boards, SoCs and CPUs is likely incomplete.
+
+### SoC specific information
+
+ * Broadcom BCM2837
+ * Amlogic Meson-GXBB, and Meson-GXL
+ * Rockchip RK3328 and RK3399
+ * Allwinner A64, H5 and H6
+ * NVIDIA Tegra X1
+
+### Board specific information
+
+ * ARM SBSA (Server Base System Architecture) compliant systems
+ * FriendlyARM NanoPi NEO Plus2
+ * FriendlyARM NanoPi NEO2
+ * Hardkernel ODROID-C2
+ * Libre Computer AML-S905-X-CC (Le Potato)
+ * NVIDIA Jetson TX1
+ * PINE64 A64, A64+, A64-LTS, SOPINE, Pinebook, Pinebook Pro, Rock64, RockPro64
+ * Raspberry Pi 3
+
+### Known Supported CPUs
+
+ * ARM Cortex-A53
+ * ARM Cortex-A57
+ * ARM Cortex-A72
+ * Marvell ThunderX
+ * Ampere eMAG
+ * NVIDIA Denver2
+
+[//]: ### Unknown CPUs list:
+[//]: * ARM Cortex-A32
+[//]: * ARM Cortex-A35
+[//]: * ARM Cortex-A55
+[//]: * ARM Cortex-A65
+[//]: * ARM Cortex-A73
+[//]: * ARM Cortex-A75
+[//]: * ARM Cortex-A76
+
+"""
 ]]
 [[!tag tier1port]]

refer to the right files and the right uboot.
Index: wikisrc/ports/evbarm/rockchip.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/rockchip.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports/evbarm/rockchip.mdwn	8 Jan 2020 06:48:19 -0000	1.6
+++ wikisrc/ports/evbarm/rockchip.mdwn	8 Jan 2020 06:50:41 -0000	1.7
@@ -67,8 +67,8 @@
 # Installation
 
 - Download or build **arm64.img** (64-bit) from NetBSD 9.0 or later
-- Write the image to disk: **dd if=armv7.img of=/dev/rld0d bs=1m conv=sync**
-- Install a board-specific U-Boot (2018.05 or later) from pkgsrc to the SD card
+- Write the image to disk: **dd if=arm64.img of=/dev/rld0d bs=1m conv=sync**
+- Install a board-specific U-Boot from pkgsrc to the SD card
   **dd if=/usr/pkg/share/u-boot/<boardname>/rkspi_loader.img of=/dev/rld0d seek=64 conv=sync**
 
 If your SoC has a SATA controller and you would like to install on

remove unwanted H6 leftover from the allwinner list i copied.
Index: wikisrc/ports/evbarm/rockchip.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/rockchip.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/evbarm/rockchip.mdwn	8 Jan 2020 06:45:15 -0000	1.5
+++ wikisrc/ports/evbarm/rockchip.mdwn	8 Jan 2020 06:48:19 -0000	1.6
@@ -48,7 +48,7 @@
     <tr><td>I2S/PCM</td><td>Experimental</td><td></td></tr>
     <tr><td>NAND</td><td>Yes</td><td></td></tr>
     <tr><td>P2WI/RSB</td><td>Yes</td><td></td></tr>
-    <tr><td>PCIe</td><td>-</td><td>H6</td></tr>
+    <tr><td>PCIe</td><td>-</td><td></td></tr>
     <tr><td>PWM</td><td>Yes</td><td></td></tr>
     <tr><td>RTC</td><td>Yes</td><td></td></tr>
     <tr><td>SATA</td><td>Yes</td><td></td></tr>

add some basic rockchip info. update pine64 product URLs.
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -r1.82 -r1.83
--- wikisrc/ports/evbarm.mdwn	3 Dec 2019 11:17:35 -0000	1.82
+++ wikisrc/ports/evbarm.mdwn	8 Jan 2020 06:45:15 -0000	1.83
@@ -6,6 +6,7 @@
 port_var3="earmv6hf"
 port_var4="earmv7hf"
 port_var5="earmv7hfeb"
+port_var6="aarch64"
 port_var_install_notes="evbarm-earm"
 cur_rel="8.1"
 future_rel="9.0"
@@ -71,6 +72,7 @@
  - [[NVIDIA Tegra|Tegra]]
  - [[ODROID C1 and C1+|ODROID-C1]]
  - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]]
+ - [[RockChip SoCs|RockChip]]
 
 ### SSH configuration for installtion
 
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -r1.104 -r1.105
--- wikisrc/ports/evbarm/allwinner.mdwn	24 Nov 2019 14:45:36 -0000	1.104
+++ wikisrc/ports/evbarm/allwinner.mdwn	8 Jan 2020 06:45:15 -0000	1.105
@@ -36,9 +36,9 @@
     <tr><td>sun8i</td><td>H3</td><td>8.0</td><td><a href="http://nanopi.io/nanopi-neo.html">FriendlyARM NanoPi NEO</a>, <a href="http://www.orangepi.org/orangepiplus2e/">Xunlong Orange Pi Plus 2E</a></td><td></td></tr>
     <tr><td>sun8i</td><td>V3s</td><td>-</td><td><a href="https://www.indiegogo.com/projects/licheepi-zero-6-extensible-linux-module-on-finger-wifi-diy#/">Lichee Pi Zero</a></td><td></td></tr>
     <tr><td>sun9i</td><td>A80</td><td>8.0</td><td><a href="http://linux-sunxi.org/Cubietech_Cubieboard4">Cubietech Cubieboard 4</a></td><td></td></tr>
-    <tr><td>sun50i</td><td>A64</td><td>9.0</td><td><a href="https://www.pine64.org/?page_id=1194">Pine64</a>, <a href="https://www.pine64.org/?page_id=3707">Pinebook</a></td><td></td></tr>
+    <tr><td>sun50i</td><td>A64</td><td>9.0</td><td><a href="https://www.pine64.org/devices/single-board-computers/pine-a64/">Pine64</a>, <a href="https://www.pine64.org/pinebook/">Pinebook</a></td><td></td></tr>
     <tr><td>sun50i</td><td>H5</td><td>9.0</td><td><a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180">FriendlyARM NanoPi NEO2, <a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=196">FriendlyARM NanoPi NEO Plus2</a></td><td></td></tr>
-    <tr><td>sun50i</td><td>H6</td><td>9.0</td><td><a href="http://www.orangepi.org/OrangePiOneplus/">Orange Pi One Plus</a>, <a href="https://www.pine64.org/?product_cat=pine-h64-boards">Pine H64</a></td></tr>
+    <tr><td>sun50i</td><td>H6</td><td>9.0</td><td><a href="http://www.orangepi.org/OrangePiOneplus/">Orange Pi One Plus</a>, <a href="https://www.pine64.org/pine-h64-ver-b/">Pine H64</a></td></tr>
   </tbody>
 </table>
 
--- /dev/null	2020-01-08 06:44:29.919621557 +0000
+++ wikisrc/ports/evbarm/rockchip.mdwn	2020-01-08 06:45:41.485766318 +0000
@@ -0,0 +1,83 @@
+[[!meta title="NetBSD/evbarm on Fuzhou RockChip SoCs"]]
+
+NetBSD supports several boards based on RockChip SoCs. Starting with NetBSD 9.0, FDT is used to configure devices. As a result, a large number of boards and configurations can be supported with a single kernel.
+
+<img src="https://pbs.twimg.com/media/ENlmzo7UUAIfSM6.jpg" width="300">
+
+[[!toc levels=2]]
+
+# Supported SoCs
+
+<table>
+  <thead>
+    <tr>
+      <th>Family</th>
+      <th>SoC</th>
+      <th>NetBSD version</th>
+      <th>Example boards</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr><td>RK3328</td><td>Rock64</td><td>9.0</td><td><a href="https://www.pine64.org/devices/single-board-computers/rock64/">Pine64 Rock64</a><td></td></tr>
+    <tr><td>RK3399</td><td>Rock64</td><td>9.0</td><td><a href="https://www.pine64.org/rockpro64/">Pine64 RockPro64</a>, <a href="https://www.pine64.org/pinebook-pro/">Pine64 Pinebook Pro</a><td></td></tr>
+  </tbody>
+</table>
+
+Other systems may work, but they have not been tested.
+
+# Supported hardware
+
+Please refer to the [GENERIC64 (64-bit)](https://nxr.netbsd.org/xref/src/sys/arch/evbarm/conf/GENERIC64) kernel configs for the most up-to-date list of supported hardware.
+
+<table>
+  <thead>
+    <tr>
+      <th>Device</th>
+      <th>Supported</th>
+      <th>Notes</th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr><td>Audio codec</td><td>Yes</td><td></td></tr>
+    <tr><td>Framebuffer</td><td>Yes</td><td>Uses simplefb configured by bootloader</td></tr>
+    <tr><td>Gigabit Ethernet</td><td>Yes</td><td></td></tr>
+    <tr><td>GPIO</td><td>Yes</td><td></td></tr>
+    <tr><td>GPU</td><td>-</td><td></td></tr>
+    <tr><td>I2C</td><td>Yes</td><td></td></tr>
+    <tr><td>I2S/PCM</td><td>Experimental</td><td></td></tr>
+    <tr><td>NAND</td><td>Yes</td><td></td></tr>
+    <tr><td>P2WI/RSB</td><td>Yes</td><td></td></tr>
+    <tr><td>PCIe</td><td>-</td><td>H6</td></tr>
+    <tr><td>PWM</td><td>Yes</td><td></td></tr>
+    <tr><td>RTC</td><td>Yes</td><td></td></tr>
+    <tr><td>SATA</td><td>Yes</td><td></td></tr>
+    <tr><td>SD/MMC</td><td>Yes</td><td></td></tr>
+    <tr><td>SMP</td><td>Yes</td><td></td></tr>
+    <tr><td>SPDIF</td><td>-</td><td></td></tr>
+    <tr><td>SPI</td><td>Yes</td><td></td></tr>
+    <tr><td>Thermal sensors</td><td>Yes</td><td></td></tr>
+    <tr><td>UART</td><td>Yes</td><td></td></tr>
+    <tr><td>USB 2.0</td><td>Yes</td><td></td></tr>
+    <tr><td>USB 3.0</td><td>Yes</td><td></td></tr>
+    <tr><td>Watchdog timer</td><td>Yes</td><td></td></tr>
+  </tbody>
+</table>
+
+# Installation
+
+- Download or build **arm64.img** (64-bit) from NetBSD 9.0 or later
+- Write the image to disk: **dd if=armv7.img of=/dev/rld0d bs=1m conv=sync**
+- Install a board-specific U-Boot (2018.05 or later) from pkgsrc to the SD card
+  **dd if=/usr/pkg/share/u-boot/&lt;boardname&gt;/rkspi_loader.img of=/dev/rld0d seek=64 conv=sync**
+
+If your SoC has a SATA controller and you would like to install on
+an hard disk and use a SD card only for u-boot please give a look
+to
+[[NetBSD/evbarm install via sysinst(8) on a SATA hard disk, USB stick or (u)SD card|ports/evbarm/install_using_sysinst]].
+
+# Tips and tricks
+
+# Links
+
+- [[NetBSD/evbarm install via sysinst(8) on a SATA hard disk, USB stick or (u)SD card|ports/evbarm/install_using_sysinst]]

raspberry-pi: spelling
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.123
retrieving revision 1.124
diff -u -r1.123 -r1.124
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Jan 2020 15:06:05 -0000	1.123
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Jan 2020 15:09:58 -0000	1.124
@@ -297,7 +297,7 @@
 
 ## Power supply needed (or: why there is a little rainbow square in the top-right corner?)
 Raspberry Pi devices are powered by 5V micro USB and a 2.5A (2500mA)
-power supply is reccomended.  For more information please read:
+power supply is recommended.  For more information please read:
 
  <https://www.raspberrypi.org/documentation/faqs/#pi-power>
 
@@ -309,7 +309,7 @@
 sd0: cache synchronization failed
 """]]
 
-Using a reccomended power supply avoid such issues.
+Using a recommended power supply avoid such issues.
 
 ## Xenon death flash (Raspberry Pi 2 is camera-shy)
 When using laser pointers or xenon flashes in cameras (or other

raspberry_pi: Update aarch64 support
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.122
retrieving revision 1.123
diff -u -r1.122 -r1.123
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Jan 2020 13:09:23 -0000	1.122
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Jan 2020 15:06:05 -0000	1.123
@@ -14,6 +14,8 @@
 
 # What works (and what doesn't yet)
 
+"Works" is primarily relative to the earmv6hf-el and earmv7hf-el CPU targets (32-bit).
+
 ## NetBSD 7 and NetBSD 8
 
  - RPI1, RPI2, RPI2-1.2, RPI3, RPI3+ (except RPI3 builtin WiFi and bluetooth)
@@ -33,11 +35,14 @@
  - I²C: works, could use enhancements, man page
  - SPI: could use enhancements, man page
 
+## NetBSD 9
+
+ - aarch64 support (RPI3, and should work on all supported systems with 64-bit CPUs)
+
 ## NetBSD current (and probably 9)
 
  - RPI3 builtin bluetooth
  - RPI3 new SD host controller driver
- - \todo Verify: RPI2-1.2 and RPI3 aarch64
 
 ## What needs documenting if it works
 
@@ -51,7 +56,6 @@
  - USB (host); isochronous transfers.
  - RPI3, RPI0W builtin WiFi
  - RPI0W Bluetooth Low Energy (probably)
- - aarch64 support is evolving very rapidly, and not yet recommended for production, largely because one must run -current.
 
 # CPU types
 
@@ -70,8 +74,8 @@
 
 The RPI2-1.2 and RPI3 have an armv8 CPU that supports aarch64 (64-bit
 mode) in addition to aarch32 (regular 32-bit ARM).  This is supported,
-in -current only, by the "aarch64" MACHINE_ARCH of evbarm, also
-available in build.sh via the alias evbarm64.  This is sometimes
+from -9 onwards, by the "aarch64" MACHINE_ARCH of evbarm, also
+available in build.sh via the alias evbarm64.  This is also
 referred to as [[NetBSD/aarch64|aarch64]].
 
 # Installation

raspberry_pi: Update what works
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.121
retrieving revision 1.122
diff -u -r1.121 -r1.122
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	2 Sep 2019 20:48:37 -0000	1.121
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	7 Jan 2020 13:09:23 -0000	1.122
@@ -33,9 +33,8 @@
  - I²C: works, could use enhancements, man page
  - SPI: could use enhancements, man page
 
-## NetBSD current
+## NetBSD current (and probably 9)
 
- - RPI3+ 
  - RPI3 builtin bluetooth
  - RPI3 new SD host controller driver
  - \todo Verify: RPI2-1.2 and RPI3 aarch64
@@ -48,7 +47,7 @@
 
 ## What needs work
 
- - RPI4 (almost certainly; not clear)
+ - RPI4 (as of 2020-01, still does not work in current)
  - USB (host); isochronous transfers.
  - RPI3, RPI0W builtin WiFi
  - RPI0W Bluetooth Low Energy (probably)

github.mdwn: add pkgsrc technote from fossil-scm.org (since we are keeping track of Fossil on this page)
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/github.mdwn	3 Jan 2020 00:15:39 -0000	1.13
+++ wikisrc/github.mdwn	6 Jan 2020 23:12:20 -0000	1.14
@@ -47,6 +47,7 @@
 
 * [2011-10: EuroBSDcon: Fossilizing NetBSD: The road to modern version control](https://2011.eurobsdcon.org/papers/sonnenberger/fossilizing.pdf)
 * <https://www.sonnenberger.org/archive/cvs2fossil-20140502.tar.gz>
+* [2010-10: fossil-scm.org: Design Note: Scaling Fossil Up (pkgsrc)](http://fossil-scm.org/home/technote/be8f2f3447ef2ea3344f8058b6733aa08c08336f)
 * [[mailing-lists/tech-repository]]
 * [[projects/project/cvs-migration]]
 

index.mdwn: move GitHub one line up to group with Community, leaving Amazon EC2 grouped with Ports
Index: wikisrc/index.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/index.mdwn,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -r1.64 -r1.65
--- wikisrc/index.mdwn	5 Jan 2020 18:49:07 -0000	1.64
+++ wikisrc/index.mdwn	5 Jan 2020 18:52:28 -0000	1.65
@@ -24,6 +24,6 @@
 * [[Security|security]] -- Security features and hardening
 * [[Users]] -- Developer sandbox pages
 * [[Community|community]] -- Known community resources
-* [[Amazon EC2|amazon_ec2]] -- NetBSD on amazon's EC2
 * [[GitHub|github]] -- NetBSD on GitHub
+* [[Amazon EC2|amazon_ec2]] -- NetBSD on amazon's EC2
 * [[Ports]] -- NetBSD on your hardware

index.mdwn: link github.mdwn
Index: wikisrc/index.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/index.mdwn,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- wikisrc/index.mdwn	30 Aug 2018 21:13:17 -0000	1.63
+++ wikisrc/index.mdwn	5 Jan 2020 18:49:07 -0000	1.64
@@ -25,4 +25,5 @@
 * [[Users]] -- Developer sandbox pages
 * [[Community|community]] -- Known community resources
 * [[Amazon EC2|amazon_ec2]] -- NetBSD on amazon's EC2
+* [[GitHub|github]] -- NetBSD on GitHub
 * [[Ports]] -- NetBSD on your hardware

Welcome to 2020!
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- wikisrc/templates/page.tmpl	30 Aug 2019 18:19:30 -0000	1.55
+++ wikisrc/templates/page.tmpl	3 Jan 2020 16:22:14 -0000	1.56
@@ -278,7 +278,7 @@
     <span class="footcopy"><a href="//www.NetBSD.org/about/disclaimer.html">
       Disclaimer</a> |
       <span class="copyright">
-        Copyright &copy; 1994-2019 The NetBSD Foundation, Inc.
+        Copyright &copy; 1994-2020 The NetBSD Foundation, Inc.
       </span>
       ALL
       RIGHTS RESERVED. <br /> NetBSD<sup>&reg;</sup> is a registered

github.mdwn: let us do a few subheadings due to the new subsection
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/github.mdwn	3 Jan 2020 00:07:41 -0000	1.12
+++ wikisrc/github.mdwn	3 Jan 2020 00:15:39 -0000	1.13
@@ -8,6 +8,8 @@
 
 * <https://github.com/NetBSD>
 
+### GitHub NetBSD org membership
+
 Anyone with a `NetBSD.org` account is eligible for an invitation to our organisation on GitHub; 
 email your NetBSD.org and GitHub.com login names to `cnst@` and/or `joerg@`. 
 Once an invitation is furnished by GitHub, it must be accepted by the recipient. 
@@ -17,6 +19,8 @@
 as well as within the public <https://GitHub.com/orgs/NetBSD/people> page; 
 the default is *Private*, and it cannot be toggled to *Public* by the owners of the org).
 
+### Official repositories on GitHub
+
 The `src`, `xsrc` and `pkgsrc` repositories, each as a read-only copy,
 have been available under `github.com/NetBSD` since 2017-06:
 

github.mdwn: are two spaces at the end of line too much? why does it <br/>?
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/github.mdwn	3 Jan 2020 00:05:10 -0000	1.11
+++ wikisrc/github.mdwn	3 Jan 2020 00:07:41 -0000	1.12
@@ -9,8 +9,8 @@
 * <https://github.com/NetBSD>
 
 Anyone with a `NetBSD.org` account is eligible for an invitation to our organisation on GitHub; 
-email your NetBSD.org and GitHub.com login names to `cnst@` and/or `joerg@`.  
-Once an invitation is furnished by GitHub, it must be accepted by the recipient.  
+email your NetBSD.org and GitHub.com login names to `cnst@` and/or `joerg@`. 
+Once an invitation is furnished by GitHub, it must be accepted by the recipient. 
 In order to publicly show your affiliation with the NetBSD organisation on GitHub, you 
 must also toggle the *organisation visibility* setting from *Private* to *Public* 
 (this membership setting affects public visibility both on your own public profile page 

github.mdwn: document GitHub membership information for developers
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/github.mdwn	3 Sep 2019 03:23:10 -0000	1.10
+++ wikisrc/github.mdwn	3 Jan 2020 00:05:10 -0000	1.11
@@ -4,10 +4,19 @@
 
 ## Official
 
-NetBSD developers maintain GitHub presence at <https://GitHub.com/NetBSD>:
+[NetBSD developers](//www.NetBSD.org/people/developers.html) maintain GitHub presence at <https://GitHub.com/NetBSD>:
 
 * <https://github.com/NetBSD>
 
+Anyone with a `NetBSD.org` account is eligible for an invitation to our organisation on GitHub; 
+email your NetBSD.org and GitHub.com login names to `cnst@` and/or `joerg@`.  
+Once an invitation is furnished by GitHub, it must be accepted by the recipient.  
+In order to publicly show your affiliation with the NetBSD organisation on GitHub, you 
+must also toggle the *organisation visibility* setting from *Private* to *Public* 
+(this membership setting affects public visibility both on your own public profile page 
+as well as within the public <https://GitHub.com/orgs/NetBSD/people> page; 
+the default is *Private*, and it cannot be toggled to *Public* by the owners of the org).
+
 The `src`, `xsrc` and `pkgsrc` repositories, each as a read-only copy,
 have been available under `github.com/NetBSD` since 2017-06:
 

calendar update
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020.mdwn	2020-01-02 00:00:36.180311579 +0000
@@ -0,0 +1 @@
+[[!calendar type=year year=2020 pages="internal(blog/*)"]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/01.mdwn	2020-01-02 00:00:36.205575173 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=01 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(01) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/02.mdwn	2020-01-02 00:00:36.228623650 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=02 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(02) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/03.mdwn	2020-01-02 00:00:36.249230748 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=03 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(03) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/04.mdwn	2020-01-02 00:00:36.567648781 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=04 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(04) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/05.mdwn	2020-01-02 00:00:36.295200237 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=05 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(05) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/06.mdwn	2020-01-02 00:00:36.322012199 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=06 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(06) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/07.mdwn	2020-01-02 00:00:36.344586243 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=07 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(07) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/08.mdwn	2020-01-02 00:00:36.367196043 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=08 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(08) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/09.mdwn	2020-01-02 00:00:36.386951484 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=09 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(09) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/10.mdwn	2020-01-02 00:00:36.412624150 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=10 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(10) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/11.mdwn	2020-01-02 00:00:36.435119727 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=11 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(11) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2020-01-02 00:00:35.917763659 +0000
+++ wikisrc/archives/2020/12.mdwn	2020-01-02 00:00:36.458206029 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=12 year=2020 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(12) and creation_year(2020) and internal(blog/*)" show=0 feeds=no reverse=yes]]

The top bar isn't orange anymore... just call it `top bar'.
Pointed out via comments by sigo via comments.
Members: 
	wiki/todo/write_wiki_howtos.mdwn:1.2->1.3 

Index: wikisrc/wiki/todo/write_wiki_howtos.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/wiki/todo/write_wiki_howtos.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/wiki/todo/write_wiki_howtos.mdwn	11 Nov 2009 09:59:46 -0000	1.2
+++ wikisrc/wiki/todo/write_wiki_howtos.mdwn	30 Dec 2019 16:41:50 -0000	1.3
@@ -2,7 +2,7 @@
 
 * edit via CVS
 * edit via web browser:<br>
-  Just hit the 'Edit' link in the orange bar. For markup advice, see the [[FormattingHelp|ikiwiki/formatting]] link at the bottom next to the save etc buttons. Or use the cheat option: look at a page that already does what you want to achieve. :)
+  Just hit the 'Edit' link in the top bar. For markup advice, see the [[FormattingHelp|ikiwiki/formatting]] link at the bottom next to the save etc buttons. Or use the cheat option: look at a page that already does what you want to achieve. :)
 * set up [[Kerberos|kerberos/system]]
 * report the `"do" parameter missing` bug
 

Remove spammish/unrelated comment
--- wikisrc/users/tm/comment_1_d9b4fa2726e37f9900d9ec7930d62a0f._comment	2019-12-30 16:37:43.069739467 +0000
+++ /dev/null	2019-12-30 16:36:52.409112408 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://launchpad.net/~sigo"
- nickname="sigo"
- subject="locked"
- date="2019-12-30T14:16:37Z"
- content="""
-this wiki is locked down
-"""]]

Added a comment: orange bar
--- /dev/null	2019-12-30 15:32:05.301300905 +0000
+++ wikisrc/wiki/todo/write_wiki_howtos/comment_1_f3e50e818bc2fc512c2d0d1f2c2fb786._comment	2019-12-30 15:34:53.950563039 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://launchpad.net/~sigo"
+ nickname="sigo"
+ subject="orange bar"
+ date="2019-12-30T15:34:15Z"
+ content="""
+there is no orange bar. maybe go to the orange juice bar.
+"""]]

Added a comment: convenience ?
--- /dev/null	2019-12-30 15:32:05.301300905 +0000
+++ wikisrc/kerberos/system/comment_1_9b42495d432f5bb3982e2ee188a50902._comment	2019-12-30 15:32:17.228380191 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://launchpad.net/~sigo"
+ nickname="sigo"
+ subject="convenience ?"
+ date="2019-12-30T15:31:45Z"
+ content="""
+you state \"convenience\" as a reason? You gotta be kidding me...
+"""]]

Added a comment: locked
--- /dev/null	2019-12-30 14:17:05.801508380 +0000
+++ wikisrc/users/tm/comment_1_d9b4fa2726e37f9900d9ec7930d62a0f._comment	2019-12-30 14:17:09.736493387 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://launchpad.net/~sigo"
+ nickname="sigo"
+ subject="locked"
+ date="2019-12-30T14:16:37Z"
+ content="""
+this wiki is locked down
+"""]]

Added a comment: well
--- /dev/null	2019-12-30 14:09:03.116857740 +0000
+++ wikisrc/ikiwiki/openid/comment_1_03aa0d0bc01c034abca907a997088685._comment	2019-12-30 14:09:03.681872502 +0000
@@ -0,0 +1,8 @@
+[[!comment format=py
+ username="https://launchpad.net/~sigo"
+ nickname="sigo"
+ subject="well"
+ date="2019-12-30T14:08:31Z"
+ content="""
+print \"openiddirectory.com is a bit of a joke.\"
+"""]]

Cross off the two bug reports by Tero Kivinen, there's a reply that
they do not occur any more.
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- wikisrc/releng/netbsd9.mdwn	27 Dec 2019 21:01:37 -0000	1.63
+++ wikisrc/releng/netbsd9.mdwn	27 Dec 2019 21:04:14 -0000	1.64
@@ -6,8 +6,8 @@
 
 * ~~[[!template id=pr number=53053]]: non-MULTIPROCESSOR hangs building Go~~ (still reproducable with newer go?)  
   [[!template id=pr number=53173]]: "go test net/http" locks up the machine (both PRs tied /!\ )
-* [[!template id=pr number=53016]]: Clock not stable /!\
-* [[!template id=pr number=53017]]: Kernel panics every now and then with "fpusave_lwp: did not" message
+* ~~[[!template id=pr number=53016]]: Clock not stable /!\~~
+* ~~[[!template id=pr number=53017]]: Kernel panics every now and then with "fpusave_lwp: did not" message~~
 * [[!template id=pr number=53155]]: Wedge after <12h uptime when >2 bnx network interfaces in use /!\
 * ~~[[!template id=pr number=53161]]: ATF test runs leave a rump_server process around~~
 * ~~[[!template id=pr number=53286]]: hdaudio(4), iwm(4) and rtsx(4) detections fail in UEFI case /!\~~

Cross off vax breakage (although I should double-check that netbsd-9 is fine)
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- wikisrc/releng/netbsd9.mdwn	27 Dec 2019 20:59:10 -0000	1.62
+++ wikisrc/releng/netbsd9.mdwn	27 Dec 2019 21:01:37 -0000	1.63
@@ -17,7 +17,7 @@
 
 * [[!template id=pr number=53128]]: Boot says "default boot twice, skipping..."
 * ~~[[!template id=pr number=54074]]: Test cases ending in 32 fail on sparc64 since jemalloc update~~
-* [[!template id=pr number=54089]]: vax installer does not boot (init dies)
+* ~~[[!template id=pr number=54089]]: vax installer does not boot (init dies)~~
 * ~~[[!template id=pr number=54093]]: Recent test regressions on sparc~~
 * [[!template id=pr number=54300]]: lib/libutil/t_snprintb test regression on sparc
 * [[!template id=pr number=54345]]: kernel diagnostic assertion "xfer != NULL" in wdc.c

Link to the PR blocking ubc_direct.
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -r1.61 -r1.62
--- wikisrc/releng/netbsd9.mdwn	16 Dec 2019 12:47:51 -0000	1.61
+++ wikisrc/releng/netbsd9.mdwn	27 Dec 2019 20:59:10 -0000	1.62
@@ -42,8 +42,9 @@
    - ~~[[!template id=pr number=52614]] qemu virtual CD-ROM reports read errors since recent wdc changes~~ (done)
    - ~~[[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks~~ (done)
 * UBC using direct map - removal of pmap_enter()/pmap_remove()/pmap_update() for read()/write()-based I/O
+   - [[!template id=pr number=54759]] (vm.ubc_direct deadlock when read()/write() into mapping of itself)
    - [[!template id=pr number=53124]] (FFS is slow because pmap_update doesn't scale)
-   - all known issues fixed - confirmed working on amd64, alpha, aarch64
+   - confirmed working on amd64, alpha, aarch64
    - ~~need sysctl to more easily turn on, will be left off by default for 9.0~~ (done)
 * XEN AVX working
    - ~~[[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set~~ (done)

Add filemon.
Index: wikisrc/attic_museum.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/attic_museum.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/attic_museum.mdwn	25 Mar 2019 19:34:37 -0000	1.10
+++ wikisrc/attic_museum.mdwn	18 Dec 2019 07:44:08 -0000	1.11
@@ -20,7 +20,7 @@
 Component	|Category		|Removed Since	|Most Functional Version	|References
 vm86		|x86 CPU Mode		|08/2017	|NetBSD 7			|Many, was widespread, not reinstatable
 ipkdb		|Remote Debugger	|07/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/07/15/msg096801.html)
-n8		|Driver			|08/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/08/08/msg097370.html)
+n8		|Device Driver		|08/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/08/08/msg097370.html)
 ndis		|Network Driver		|08/2018	|				|[Userland Commit](https://mail-index.netbsd.org/source-changes/2018/08/25/msg097800.html), [Kernel Commit](https://mail-index.netbsd.org/source-changes/2018/08/25/msg097796.html)
 midway		|Network Driver		|09/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/09/06/msg098894.html)
 natm		|Network Protocol	|09/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/09/06/msg098895.html)
@@ -32,9 +32,10 @@
 isic		|Network Driver		|09/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/09/22/msg099351.html)
 isdn		|Network Protocol	|09/2018	|				|[Userland Commit](https://mail-index.netbsd.org/source-changes/2018/09/23/msg099370.html), [Kernel Commit](https://mail-index.netbsd.org/source-changes/2018/09/23/msg099381.html)
 lmc		|Network Driver		|12/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/12/12/msg101368.html)
-compat_svr4	|Compatibility layer	|12/2018	|NetBSD 4			|[Commit](https://mail-index.netbsd.org/source-changes/2018/12/19/msg101565.html)
-compat_ibcs2	|Compatibility layer	|12/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/12/29/msg101841.html)
+compat_svr4	|Compatibility Layer	|12/2018	|NetBSD 4			|[Commit](https://mail-index.netbsd.org/source-changes/2018/12/19/msg101565.html)
+compat_ibcs2	|Compatibility Layer	|12/2018	|				|[Commit](https://mail-index.netbsd.org/source-changes/2018/12/29/msg101841.html)
 satlink		|Device Driver		|01/2019	|				|[Commit](https://mail-index.netbsd.org/source-changes/2019/01/27/msg102772.html)
-compat_osf1	|Compatibility layer	|03/2019	|				|[Commit](https://mail-index.netbsd.org/source-changes/2019/03/25/msg104511.html)
+compat_osf1	|Compatibility Layer	|03/2019	|				|[Commit](https://mail-index.netbsd.org/source-changes/2019/03/25/msg104511.html)
+filemon		|Pseudo Device		|12/2019	|				|[Commit](https://mail-index.netbsd.org/source-changes/2019/12/18/msg112062.html)
 """]]
 

xen hotwo: clarify i386/amd64 issues
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.166
retrieving revision 1.167
diff -u -r1.166 -r1.167
--- wikisrc/ports/xen/howto.mdwn	17 Dec 2019 20:36:16 -0000	1.166
+++ wikisrc/ports/xen/howto.mdwn	17 Dec 2019 20:59:09 -0000	1.167
@@ -46,11 +46,11 @@
 
 [[!table data="""
 Xen Version	|Package Name	|Xen CPU Support	|xm?	|EOL'ed By Upstream
-4.2		|xenkernel42	|32bit, 64bit		|yes	|Yes
-4.5		|xenkernel45	|64bit			|	|Yes
-4.6		|xenkernel46	|64bit			|	|Yes
-4.8		|xenkernel48	|64bit			|	|Yes
-4.11		|xenkernel411	|64bit			|	|No
+4.2		|xenkernel42	|i386 x86_64		|yes	|Yes
+4.5		|xenkernel45	|x86_64			|	|Yes
+4.6		|xenkernel46	|x86_64			|	|Yes
+4.8		|xenkernel48	|x86_64			|	|Yes
+4.11		|xenkernel411	|x86_64			|	|No
 """]]
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
@@ -63,7 +63,7 @@
 domU		|Yes
 """]]
 
-Note: NetBSD support is called XEN3. However, it does support Xen 4,
+Note: NetBSD support is called XEN3.  However, it does support Xen 4,
 because the hypercall interface has remained identical.
 
 Older Xen had a python-based management tool called xm, now replaced
@@ -74,15 +74,17 @@
 Architecture
 ------------
 
-Xen itself runs on x86_64 hardware.
+Xen 4.5 and later runs on x86_64 hardware (the NetBSD amd64 port).
+Xen 4.2 can in theory use i386 hardware, but we do not have
+recent reports of success.
 
 The dom0 system, plus each domU, can be either i386PAE or amd64.
 i386 without PAE is not supported.
 
 The standard approach is to use NetBSD/amd64 for the dom0.
 
-To use an i386PAE dom0, one must build or obtain a 64bit Xen kernel and
-install it on the system.
+To use an i386PAE dom0 (other than on 4.2), one must build or obtain a
+64bit Xen kernel and install it on the system.
 
 For domUs, i386PAE is considered as
 [faster](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)

ports/xen/howto: Update eol status
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.165
retrieving revision 1.166
diff -u -r1.165 -r1.166
--- wikisrc/ports/xen/howto.mdwn	11 Apr 2019 17:33:16 -0000	1.165
+++ wikisrc/ports/xen/howto.mdwn	17 Dec 2019 20:36:16 -0000	1.166
@@ -45,12 +45,12 @@
 Versions available in pkgsrc:
 
 [[!table data="""
-Xen Version	|Package Name	|Xen CPU Support	|EOL'ed By Upstream
-4.2		|xenkernel42	|32bit, 64bit		|Yes
-4.5		|xenkernel45	|64bit			|Yes
-4.6		|xenkernel46	|64bit			|Partially
-4.8		|xenkernel48	|64bit			|No
-4.11		|xenkernel411	|64bit			|No
+Xen Version	|Package Name	|Xen CPU Support	|xm?	|EOL'ed By Upstream
+4.2		|xenkernel42	|32bit, 64bit		|yes	|Yes
+4.5		|xenkernel45	|64bit			|	|Yes
+4.6		|xenkernel46	|64bit			|	|Yes
+4.8		|xenkernel48	|64bit			|	|Yes
+4.11		|xenkernel411	|64bit			|	|No
 """]]
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
@@ -66,6 +66,11 @@
 Note: NetBSD support is called XEN3. However, it does support Xen 4,
 because the hypercall interface has remained identical.
 
+Older Xen had a python-based management tool called xm, now replaced
+by xl.  xm is obsolete, but 4.2 remains in pkgsrc because migrating
+from xm to xl is not always trivial, and because 4.2 is the last
+version to run on an i386 dom0.
+
 Architecture
 ------------
 
@@ -83,7 +88,7 @@
 [faster](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)
 than amd64.
 
-#Creating a dom0
+# Creating a dom0
 
 In order to install a NetBSD as a dom0, one must first install a normal
 NetBSD system, and then pivot the install to a dom0 install by changing

Mark ptrace goals as done for 9.0
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.60
retrieving revision 1.61
diff -u -r1.60 -r1.61
--- wikisrc/releng/netbsd9.mdwn	16 Dec 2019 12:42:30 -0000	1.60
+++ wikisrc/releng/netbsd9.mdwn	16 Dec 2019 12:47:51 -0000	1.61
@@ -71,8 +71,8 @@
 ## Nice to have, but likely won't be finished on time
 
 * ~~~merge pgoyette-compat~~~ (done)
-* address failing ptrace(2) tests, cover the remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
-* rework semantics of threading operations in ptrace(2)
+* ~~~address failing ptrace(2) tests, cover the remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)~~~ (done in the scope for 9.0)
+* ~~~rework semantics of threading operations in ptrace(2)~~~ (done)
 
 ## Abandoned for 9.0
 

Add PR 54771 as showstopper
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.59
retrieving revision 1.60
diff -u -r1.59 -r1.60
--- wikisrc/releng/netbsd9.mdwn	13 Dec 2019 20:49:37 -0000	1.59
+++ wikisrc/releng/netbsd9.mdwn	16 Dec 2019 12:42:30 -0000	1.60
@@ -24,6 +24,7 @@
 * ~~[[!template id=pr number=54503]]: Panic during attaching nvme(4) when # of logical CPUs >= 32 ? /!\~~
 * [[!template id=pr number=54727]]: writing a large file causes unreasonable system behaviour (may not be a regression, but became more noticable with -9)
 * [[!template id=pr number=54761]]: nvme corruption on GENERIC without DIAGNOSTIC
+* [[!template id=pr number=54771]]: nvme(4) fails to attach
 
 ## Bug Bountys
 

Fix format of users/tkusumi.mdwn
Index: wikisrc/users/tkusumi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/tkusumi.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/users/tkusumi.mdwn	15 Dec 2019 12:46:48 -0000	1.7
+++ wikisrc/users/tkusumi.mdwn	15 Dec 2019 12:49:09 -0000	1.8
@@ -9,6 +9,5 @@
 * <https://www.netbsd.org/~tkusumi/>
 * <https://www.netbsd.org/people/developers.html>
 * <https://wiki.netbsd.org/projects/project/new-automounter/>
-
 * <https://www.phoronix.com/scan.php?page=news_item&px=DragonFlyBSD-FUSE>
 * <https://www.phoronix.com/scan.php?page=news_item&px=DragonFly-HAMMER2-FSCK>

Update users/tkusumi.mdwn
Index: wikisrc/users/tkusumi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/tkusumi.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/users/tkusumi.mdwn	15 Dec 2019 01:39:13 -0000	1.6
+++ wikisrc/users/tkusumi.mdwn	15 Dec 2019 12:46:48 -0000	1.7
@@ -9,3 +9,6 @@
 * <https://www.netbsd.org/~tkusumi/>
 * <https://www.netbsd.org/people/developers.html>
 * <https://wiki.netbsd.org/projects/project/new-automounter/>
+
+* <https://www.phoronix.com/scan.php?page=news_item&px=DragonFlyBSD-FUSE>
+* <https://www.phoronix.com/scan.php?page=news_item&px=DragonFly-HAMMER2-FSCK>

Update users/tkusumi.mdwn
Index: wikisrc/users/tkusumi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/tkusumi.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/tkusumi.mdwn	14 Dec 2019 11:42:24 -0000	1.5
+++ wikisrc/users/tkusumi.mdwn	15 Dec 2019 01:39:13 -0000	1.6
@@ -4,6 +4,7 @@
 
 * <https://github.com/kusumi>
 * <https://github.com/NetBSD/src/commits?author=kusumi>
+* <https://sourceforge.net/u/kusumi/profile/>
 * <https://www.dragonflybsd.org/~tkusumi/>
 * <https://www.netbsd.org/~tkusumi/>
 * <https://www.netbsd.org/people/developers.html>

Add people/developers.html link to users/tkusumi
Index: wikisrc/users/tkusumi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/tkusumi.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/tkusumi.mdwn	14 Dec 2019 10:09:42 -0000	1.4
+++ wikisrc/users/tkusumi.mdwn	14 Dec 2019 11:42:24 -0000	1.5
@@ -6,4 +6,5 @@
 * <https://github.com/NetBSD/src/commits?author=kusumi>
 * <https://www.dragonflybsd.org/~tkusumi/>
 * <https://www.netbsd.org/~tkusumi/>
+* <https://www.netbsd.org/people/developers.html>
 * <https://wiki.netbsd.org/projects/project/new-automounter/>

Add GitHub link to users/tkusumi
Index: wikisrc/users/tkusumi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/tkusumi.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/tkusumi.mdwn	14 Dec 2019 07:50:00 -0000	1.3
+++ wikisrc/users/tkusumi.mdwn	14 Dec 2019 10:09:42 -0000	1.4
@@ -3,6 +3,7 @@
 Tomohiro Kusumi <<tkusumi@netbsd.org>>
 
 * <https://github.com/kusumi>
+* <https://github.com/NetBSD/src/commits?author=kusumi>
 * <https://www.dragonflybsd.org/~tkusumi/>
 * <https://www.netbsd.org/~tkusumi/>
 * <https://wiki.netbsd.org/projects/project/new-automounter/>

Add links to users/tkusumi
Index: wikisrc/users/tkusumi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/tkusumi.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/tkusumi.mdwn	14 Dec 2019 07:42:18 -0000	1.2
+++ wikisrc/users/tkusumi.mdwn	14 Dec 2019 07:50:00 -0000	1.3
@@ -2,7 +2,7 @@
 
 Tomohiro Kusumi <<tkusumi@netbsd.org>>
 
-* https://github.com/kusumi
-* https://www.dragonflybsd.org/~tkusumi/
-* https://www.netbsd.org/~tkusumi/
-* https://wiki.netbsd.org/projects/project/new-automounter/
+* <https://github.com/kusumi>
+* <https://www.dragonflybsd.org/~tkusumi/>
+* <https://www.netbsd.org/~tkusumi/>
+* <https://wiki.netbsd.org/projects/project/new-automounter/>

new-automounter.mdwn: Fix format
Index: wikisrc/projects/project/new-automounter.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/new-automounter.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/projects/project/new-automounter.mdwn	12 Dec 2019 16:37:13 -0000	1.9
+++ wikisrc/projects/project/new-automounter.mdwn	14 Dec 2019 07:45:06 -0000	1.10
@@ -12,7 +12,7 @@
 category="filesystems"
 difficulty="medium"
 duration="3 months"
-done_by="Tomohiro Kusumi <tkusumi@netbsd.org> (a port from DragonFlyBSD which was a port from FreeBSD)"
+done_by="Tomohiro Kusumi <<tkusumi@netbsd.org>> (a port from DragonFlyBSD which was a port from FreeBSD)"
 
 description="""
 NetBSD currently uses amd for automatically mounting (network) file systems. This software package implements an automounter file system as a userland NFS daemon. While this generally works it has major drawbacks:

Fix users/tkusumi.mdwn
Index: wikisrc/users/tkusumi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/tkusumi.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/tkusumi.mdwn	14 Dec 2019 07:39:15 -0000	1.1
+++ wikisrc/users/tkusumi.mdwn	14 Dec 2019 07:42:18 -0000	1.2
@@ -1,10 +1,8 @@
 # About
 
-Tomohiro Kusumi <tkusumi@netbsd.org>
+Tomohiro Kusumi <<tkusumi@netbsd.org>>
 
-https://github.com/kusumi
-
-https://www.dragonflybsd.org/~tkusumi/
-https://www.netbsd.org/~tkusumi/
-
-https://wiki.netbsd.org/projects/project/new-automounter/
+* https://github.com/kusumi
+* https://www.dragonflybsd.org/~tkusumi/
+* https://www.netbsd.org/~tkusumi/
+* https://wiki.netbsd.org/projects/project/new-automounter/

Add users/tkusumi
--- /dev/null	2019-12-14 07:39:24.922246334 +0000
+++ wikisrc/users/tkusumi.mdwn	2019-12-14 07:39:54.753855105 +0000
@@ -0,0 +1,10 @@
+# About
+
+Tomohiro Kusumi <tkusumi@netbsd.org>
+
+https://github.com/kusumi
+
+https://www.dragonflybsd.org/~tkusumi/
+https://www.netbsd.org/~tkusumi/
+
+https://wiki.netbsd.org/projects/project/new-automounter/

add PR 54761 as showstopper
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.58
retrieving revision 1.59
diff -u -r1.58 -r1.59
--- wikisrc/releng/netbsd9.mdwn	6 Dec 2019 18:44:13 -0000	1.58
+++ wikisrc/releng/netbsd9.mdwn	13 Dec 2019 20:49:37 -0000	1.59
@@ -22,7 +22,8 @@
 * [[!template id=pr number=54300]]: lib/libutil/t_snprintb test regression on sparc
 * [[!template id=pr number=54345]]: kernel diagnostic assertion "xfer != NULL" in wdc.c
 * ~~[[!template id=pr number=54503]]: Panic during attaching nvme(4) when # of logical CPUs >= 32 ? /!\~~
-* [[!template id=pr number=54727]]: writing a large file causes unreasonable system behaviour
+* [[!template id=pr number=54727]]: writing a large file causes unreasonable system behaviour (may not be a regression, but became more noticable with -9)
+* [[!template id=pr number=54761]]: nvme corruption on GENERIC without DIAGNOSTIC
 
 ## Bug Bountys
 

It's SHLIB_TEENY, not SHLIB_TINY!
Noticed by Greg A. Woods via WWW Feedback form, thanks!
Members: 
	tutorials/bsd_make.mdwn:1.1->1.2 

Index: wikisrc/tutorials/bsd_make.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/bsd_make.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/tutorials/bsd_make.mdwn	27 Apr 2019 20:19:32 -0000	1.1
+++ wikisrc/tutorials/bsd_make.mdwn	13 Dec 2019 09:16:31 -0000	1.2
@@ -42,7 +42,7 @@
     SHLIB_MINOR=0
     .include <bsd.lib.mk>
 
-You may define SHLIB_TINY variable too.
+You may define SHLIB_TEENY variable too.
 
 Alternatively, you may define variables in "shlib_version" file:
 

Mention autofs in *BSD originate from FreeBSD
Index: wikisrc/projects/project/new-automounter.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/new-automounter.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/projects/project/new-automounter.mdwn	11 Dec 2019 06:33:30 -0000	1.8
+++ wikisrc/projects/project/new-automounter.mdwn	12 Dec 2019 16:37:13 -0000	1.9
@@ -12,7 +12,7 @@
 category="filesystems"
 difficulty="medium"
 duration="3 months"
-done_by="Tomohiro Kusumi <tkusumi@netbsd.org> (a port from DragonFlyBSD)"
+done_by="Tomohiro Kusumi <tkusumi@netbsd.org> (a port from DragonFlyBSD which was a port from FreeBSD)"
 
 description="""
 NetBSD currently uses amd for automatically mounting (network) file systems. This software package implements an automounter file system as a userland NFS daemon. While this generally works it has major drawbacks:

Fix case DragonflyBSD -> DragonFlyBSD
Index: wikisrc/projects/project/new-automounter.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/new-automounter.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/projects/project/new-automounter.mdwn	11 Dec 2019 06:31:57 -0000	1.7
+++ wikisrc/projects/project/new-automounter.mdwn	11 Dec 2019 06:33:30 -0000	1.8
@@ -12,7 +12,7 @@
 category="filesystems"
 difficulty="medium"
 duration="3 months"
-done_by="Tomohiro Kusumi <tkusumi@netbsd.org> (a port from DragonflyBSD)"
+done_by="Tomohiro Kusumi <tkusumi@netbsd.org> (a port from DragonFlyBSD)"
 
 description="""
 NetBSD currently uses amd for automatically mounting (network) file systems. This software package implements an automounter file system as a userland NFS daemon. While this generally works it has major drawbacks:

autofs: "for DragonflyBSD" -> "a port from DragonFlyBSD"
Index: wikisrc/projects/project/new-automounter.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/new-automounter.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/project/new-automounter.mdwn	28 Nov 2019 16:43:23 -0000	1.6
+++ wikisrc/projects/project/new-automounter.mdwn	11 Dec 2019 06:31:57 -0000	1.7
@@ -12,7 +12,7 @@
 category="filesystems"
 difficulty="medium"
 duration="3 months"
-done_by="Tomohiro Kusumi (for DragonflyBSD)"
+done_by="Tomohiro Kusumi <tkusumi@netbsd.org> (a port from DragonflyBSD)"
 
 description="""
 NetBSD currently uses amd for automatically mounting (network) file systems. This software package implements an automounter file system as a userland NFS daemon. While this generally works it has major drawbacks:

Cross off some completed items
Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/users/youri/pinebook-bugs.mdwn	11 Nov 2018 14:23:46 -0000	1.12
+++ wikisrc/users/youri/pinebook-bugs.mdwn	10 Dec 2019 17:00:00 -0000	1.13
@@ -6,8 +6,8 @@
 - Datasheets: <http://wiki.pine64.org/index.php/Pinebook_Main_Page#Datasheets_for_Components_and_Peripherals>
 
 ## Firmware / hardware issues
-- ANX6345 EDID detection fails at boot with sysutils/u-boot-pinebook
-  - Patch to use static EDID and LCD parameters for 14" Pinebook: <http://www.netbsd.org/~jmcneill/patch-drivers_video_bridge_anx6345.c>
+- <del>ANX6345 EDID detection fails at boot with sysutils/u-boot-pinebook</del>
+  - <del>Patch to use static EDID and LCD parameters for 14" Pinebook: <http://www.netbsd.org/~jmcneill/patch-drivers_video_bridge_anx6345.c></del>
 
 ## Kernel Bugs
 
@@ -18,9 +18,10 @@
 
 ## TODO
 
-- Native display driver (2D)
-  - Display Engine 2.0 manual: <http://linux-sunxi.org/images/7/7b/Allwinner_DE2.0_Spec_V1.0.pdf>
-  - Should be implemented as a DRM driver to support KMS and 3D
+- <del>Native display driver (2D)</del>
+  - <del>Display Engine 2.0 manual: <http://linux-sunxi.org/images/7/7b/Allwinner_DE2.0_Spec_V1.0.pdf></del>
+  - <del>Should be implemented as a DRM driver to support KMS and 3D</del>
+  - Supported in NetBSD 9
 - 3D graphics
   - Should be supported by lima driver: <https://gitlab.freedesktop.org/lima/web/wikis/home> (GPL)
   - Requires DRM PRIME

Add release status and tentative timeline
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- wikisrc/releng/netbsd9.mdwn	6 Dec 2019 18:38:44 -0000	1.57
+++ wikisrc/releng/netbsd9.mdwn	6 Dec 2019 18:44:13 -0000	1.58
@@ -76,4 +76,10 @@
 
 * ~~~gcc 8+ from a sanitizers point of view~~~ (abandoned)
 
-...
+## Current status and timeline
+
+* release candidate 1 is available
+  [[https://www.netbsd.org/releases/formal-9/]]
+* several important fixes queued for pullup after RC1, releng decided to do a second RC
+* expecting RC2 around mid of december 2019
+* final release hopefully (very) early january 2020

update some PR stati
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- wikisrc/releng/netbsd9.mdwn	6 Dec 2019 18:18:37 -0000	1.56
+++ wikisrc/releng/netbsd9.mdwn	6 Dec 2019 18:38:44 -0000	1.57
@@ -16,12 +16,12 @@
 Regression since [[netbsd8]]:
 
 * [[!template id=pr number=53128]]: Boot says "default boot twice, skipping..."
-* [[!template id=pr number=54074]]: Test cases ending in 32 fail on sparc64 since jemalloc update
+* ~~[[!template id=pr number=54074]]: Test cases ending in 32 fail on sparc64 since jemalloc update~~
 * [[!template id=pr number=54089]]: vax installer does not boot (init dies)
-* [[!template id=pr number=54093]]: Recent test regressions on sparc
+* ~~[[!template id=pr number=54093]]: Recent test regressions on sparc~~
 * [[!template id=pr number=54300]]: lib/libutil/t_snprintb test regression on sparc
 * [[!template id=pr number=54345]]: kernel diagnostic assertion "xfer != NULL" in wdc.c
-* [[!template id=pr number=54503]]: Panic during attaching nvme(4) when # of logical CPUs >= 32 ? /!\
+* ~~[[!template id=pr number=54503]]: Panic during attaching nvme(4) when # of logical CPUs >= 32 ? /!\~~
 * [[!template id=pr number=54727]]: writing a large file causes unreasonable system behaviour
 
 ## Bug Bountys

add PR 54727 as show stopper
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.55
retrieving revision 1.56
diff -u -r1.55 -r1.56
--- wikisrc/releng/netbsd9.mdwn	8 Sep 2019 09:08:20 -0000	1.55
+++ wikisrc/releng/netbsd9.mdwn	6 Dec 2019 18:18:37 -0000	1.56
@@ -22,6 +22,7 @@
 * [[!template id=pr number=54300]]: lib/libutil/t_snprintb test regression on sparc
 * [[!template id=pr number=54345]]: kernel diagnostic assertion "xfer != NULL" in wdc.c
 * [[!template id=pr number=54503]]: Panic during attaching nvme(4) when # of logical CPUs >= 32 ? /!\
+* [[!template id=pr number=54727]]: writing a large file causes unreasonable system behaviour
 
 ## Bug Bountys
 

Remove explicit mention of port master (outdated)
Index: wikisrc/ports/cesfic.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cesfic.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/ports/cesfic.mdwn	2 Jun 2019 10:27:04 -0000	1.16
+++ wikisrc/ports/cesfic.mdwn	4 Dec 2019 10:25:36 -0000	1.17
@@ -11,8 +11,6 @@
 NetBSD/cesfic is a port to the m68040 based FIC8234 VME processor board, made by
 the swiss company CES (Geneve). These boards were popular in high energy physics
 data acquisition (think of CERN!).
-
-Matthias Drochner is the port maintainer of NetBSD/cesfic.
 """
 ]]
 [[!tag tier2port]]

qemu-image -> qemu-img
Index: wikisrc/ports/evbarm/qemu_arm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/qemu_arm.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/evbarm/qemu_arm.mdwn	2 Dec 2019 22:55:55 -0000	1.7
+++ wikisrc/ports/evbarm/qemu_arm.mdwn	3 Dec 2019 12:52:20 -0000	1.8
@@ -25,7 +25,7 @@
 The disk image (armv7.img.gz or arm64.img.gz) must first be uncompressed. The *qemu-img* tool can then resize the image to the desired size. On first boot, NetBSD will grow the root file-system to match the size of the disk.
 
     $ gunzip arm64.img.gz
-    $ qemu-image resize arm64.img 20g
+    $ qemu-img resize arm64.img 20g
 
 # Booting the system (arm64)
 

xref QEMU page
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -r1.81 -r1.82
--- wikisrc/ports/evbarm.mdwn	27 Jun 2019 17:32:09 -0000	1.81
+++ wikisrc/ports/evbarm.mdwn	3 Dec 2019 11:17:35 -0000	1.82
@@ -49,7 +49,11 @@
 (Note also that armv8 is the first architecture to support aarch64, so
 this will not be an issue until at least armv9.)
 
-### anita and qemu
+### QEMU
+
+See the [[NetBSD/evbarm under QEMU|qemu_arm]] page for instructions on how to get started with QEMU.
+
+### anita
 
 anita can be used to test builds.  (In addition to anita, install qemu and dtb-arm-vexpress from pkgsrc.)   The release subdirectory should follow the naming convention on the autobuild cluster, used below.
 

Modernize QEMU evbarm instructions.
Index: wikisrc/ports/evbarm/qemu_arm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/qemu_arm.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports/evbarm/qemu_arm.mdwn	1 Jul 2017 07:24:09 -0000	1.6
+++ wikisrc/ports/evbarm/qemu_arm.mdwn	2 Dec 2019 22:55:55 -0000	1.7
@@ -4,140 +4,59 @@
 [QEMU](http://www.qemu.org/) open source processor emulator.
 This can be extremely useful for development and testing.
 
-# Introduction
-QEMU emulates ARM's Integrator/CP board. You can run NetBSD under it.
-Older NetBSD had the problem to run under QEMU's emulated Integrator/CP
-board.
-Sergio López had created the patch for NetBSD current and had posted
-to port-arm mailing list in [6 Febrary, 2013](http://mail-index.NetBSD.org/port-arm/2013/02/06/msg001739.html).
-
 # Requirements
-* pkgsrc/emulators/qemu 1.6.2 and 1.7.0
-* INTEGRATOR_CP kernel of NetBSD/evbearm 6.99.28 or later
-(some provious versions should work, but not tested)
+* qemu 4.1.0 or higher
+* disk image
+  * [NetBSD 9.x armv7](http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-earmv7hf/binary/gzimg/armv7.img.gz)
+  * [NetBSD 9.x arm64](http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz)
+* Tianocore EDK2 firmware
+  * [QEMU_EFI.fd for armv7](http://snapshots.linaro.org/components/kernel/leg-virt-tianocore-edk2-upstream/latest/QEMU-ARM/RELEASE_GCC5/QEMU_EFI.fd)
+  * [QEMU_EFI.fd for arm64](http://snapshots.linaro.org/components/kernel/leg-virt-tianocore-edk2-upstream/latest/QEMU-AARCH64/RELEASE_GCC5/QEMU_EFI.fd)
 
-## Preparing QEMU
+# Installing QEMU on NetBSD
 You can install latest qemu with the following commands.
 It is assumed that your pkgsrc tree is in /usr/pkgsrc directory.
 
     # cd /usr/pkgsrc/emulators/qemu
     # make install
 
-## Preparing NetBSD userland and kernel
-You can create INTEGRATOR_CP kernel, and kernel/userland tarball with
-the following commands.
-It is assumed that your NetBSD src tree is in /usr/src directory.
-
-    $ cd /usr/src
-    $ ./build.sh -U -T /usr/tools/evbearm-el -O /usr/obj/evbearm-el \
-      -D /usr/NewWorld/evbearm-el -R /usr/release/evbearm-el \
-      -m evbearm release
-    $ ./build.sh -U -T /usr/tools/evbearm-el -O /usr/obj/evbearm-el \
-      -D /usr/NewWorld/evbearm-el -R /usr/release/evbearm-el \
-      -m evbearm kernel=INTEGRATOR_CP
-
-# Booting
-INTEGRATOR_CP kernel has no disk drive support.
-You should setup netboot environment.
-
-## Setting up netboot environment
-You can use existing NetBSD or other Unix like operating system environment
-for host netboot.
-You can also utilize qemu-system-amd64 or qemu-system-i386 to host
-netboot.
-
-tftp is not needed, kernel is specified in commandline of qemu-system-arm.
-Only NFS root is needed.
-In detail see [Diskless NetBSD howto's Setting up the NFS server section](http://www.netbsd.org/docs/network/netboot/nfs.html).
-
-
-# Booting INTEGRATOR_CP kernel
-You can boot INTEGRATOR_CP kernel with the following commandline.
-It is assumed that the host machine uses bge0 to connect to your network.
-
-    # ifconfig bridge0 create
-    # brconfig bridge0 add bge0
-    # ifconfig bridge0 up
-    # ifconfig tap0 create
-    # ifconfig tap0 0.0.0.0 up
-    # brconfig bridge0 add tap0
-    $ cp /usr/obj/evbearm-el/sys/arch/evbarm/compile/INTEGRATOR_CP/netbsd.gz.ub .
-    $ qemu-system-arm -M integratorcp -cpu arm1136 -m 512m -kernel netbsd.gz.ub -serial stdio -net nic -net tap,fd=3 3<>/dev/tap0
-
-# After booted
-You will get the following boot messages.
-
-    Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
-        2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014
-        The NetBSD Foundation, Inc.  All rights reserved.
-    Copyright (c) 1982, 1986, 1989, 1991, 1993
-        The Regents of the University of California.  All rights reserved.
-    
-    NetBSD 6.99.28 (INTEGRATOR_CP) #0: Sat Jan 11 23:47:15 UTC 2014
-    	ryo_on@bismuth.elements.tetera.org:/usr/obj/evbearm-el/sys/arch/evbarm/compile/INTEGRATOR_CP
-    total memory = 255 MB
-    avail memory = 246 MB
-    sysctl_createv: sysctl_create(machine_arch) returned 17
-    timecounter: Timecounters tick every 10.000 msec
-    mainbus0 (root)
-    cpu0 at mainbus0 core 0: ARM1136J-S r1p3 (ARM11J V6J core)
-    cpu0: DC enabled IC enabled WB disabled EABT
-    cpu0: isar: [0]=0x140011 [1]=0x12002111 [2]=0x11231111 [3]=0x1102131, [4]=0x141, [5]=0
-    cpu0: mmfr: [0]=0x1130003 [1]=0x10030302 [2]=0x1222110 [3]=0
-    cpu0: pfr: [0]=0x111 [1]=0x1
-    cpu0: 4KB/32B 4-way L1 Instruction cache
-    cpu0: 64KB/32B 4-way write-through L1 Data cache
-    vfp0 at cpu0: VFP11
-    vfp0: mvfr: [0]=0x11111111 [1]=0
-    ifpga0 at mainbus0: Build 0, Rev A, Manufacturer Unknown, ASB, Little-endian,
-    ifpga0: FPGA unknown, SYSCLK 2.00MHz
-    ifpga0: vendor 0x0000 product 0x0000 (miscellaneous prehistoric)
-    pci_configure_bus done
-    sm0 at ifpga0 addr 0xb8000000 irq 27
-    sm0: SMC91C111, revision 1, buffer size: 8192
-    sm0: MAC address 52:54:00:12:34:56, default media MII (internal PHY)
-    plcom0 at ifpga0 addr 0x6000000 irq 1
-    plcom0: console
-    plcom1 at ifpga0 addr 0x7000000 irq 2
-    plrtc0 at ifpga0 addr 0x5000000
-    pci0 at ifpga0 bus 0
-    pci0: i/o space, memory space enabled
-    timecounter: Timecounter "clockinterrupt" frequency 100 Hz quality 0
-    clock: hz=100 stathz = 100 profhz = 500
-    timecounter: Timecounter "ifpga" frequency 62500 Hz quality 100
-    boot device: <unknown>
-    root device: sm0
-    dump device: 
-    file system (default generic): 
-    root on sm0
-    nfs_boot: trying DHCP/BOOTP
-    nfs_boot: DHCP next-server: 192.168.81.249
-    nfs_boot: my_domain=elements.tetera.org
-    nfs_boot: my_addr=192.168.81.167
-    nfs_boot: my_mask=255.255.255.0
-    nfs_boot: gateway=192.168.81.1
-    root on 192.168.81.249:/exports/integratorcp
-    root file system type: nfs
-    init path (default /sbin/init): 
-    init: trying /sbin/init
-
-
-You will see many error messages from src/sys/arch/evbarm/ifpga/ifpga_clock.c.
-
-    statclockhandler: Statclock overrun
-
-After NetBSD is booted, you can setup sm0 network interface with dhcpcd command.
-
-    # dhcpcd sm0
-
-# Using QEMU to debug the kernel
- - there is info elsewhere on the wiki about this; maybe adapt to ARM
-   and link?
+# Preparing the disk image
+
+The disk image (armv7.img.gz or arm64.img.gz) must first be uncompressed. The *qemu-img* tool can then resize the image to the desired size. On first boot, NetBSD will grow the root file-system to match the size of the disk.
+
+    $ gunzip arm64.img.gz
+    $ qemu-image resize arm64.img 20g
+
+# Booting the system (arm64)
+
+    $ qemu-system-aarch64 -M virt -cpu cortex-a53 -smp 4 -m 4g \
+          -drive if=none,file=arm64.img,id=hd0 -device virtio-blk-device,drive=hd0 \
+          -netdev type=user,id=net0 -device virtio-net-device,netdev=net0,mac=00:11:22:33:44:55 \
+          -bios QEMU_EFI.fd -nographic
+
+# Booting the system (armv7)
+
+    $ qemu-system-arm -M virt -cpu cortex-a15 -smp 4 -m 2g \
+          -drive if=none,file=armv7.img,id=hd0 -device virtio-blk-device,drive=hd0 \
+          -netdev type=user,id=net0 -device virtio-net-device,netdev=net0,mac=00:11:22:33:44:55 \
+          -bios QEMU_EFI.fd -nographic
+
+# Bridged networking
+
+To bridge a QEMU guest to your network, you need to create a tap(4) interface for your VM, then connect it to a physical interface with a bridge(4) interface.
+
+The following example assumes NetBSD as a host OS, and a physical interface named *bge0*.
 
-# Additional links
+[[!template  id=filecontent name="/etc/ifconfig.bridge0" text="""
+descr "LAN VM bridge" up
+!brconfig bridge0 add bge0
+"""]]
 
-# What works
+[[!template  id=filecontent name="/etc/ifconfig.tap0" text="""
+link f2:0b:a4:d1:f2:69 descr "NetBSD Arm64 VM" up
+!brconfig bridge0 add tap0
+"""]]
 
-# What needs work
+Then replace the *-netdev* part of the qemu command with:
 
-# more info
+    -net nic -net tap,ifname=tap0,script=no

Correct typo in name. From tkusumi.
Index: wikisrc/projects/project/new-automounter.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/new-automounter.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/new-automounter.mdwn	15 Feb 2018 00:45:04 -0000	1.5
+++ wikisrc/projects/project/new-automounter.mdwn	28 Nov 2019 16:43:23 -0000	1.6
@@ -12,7 +12,7 @@
 category="filesystems"
 difficulty="medium"
 duration="3 months"
-done_by="Tomohiro Kasumi (for DragonflyBSD)"
+done_by="Tomohiro Kusumi (for DragonflyBSD)"
 
 description="""
 NetBSD currently uses amd for automatically mounting (network) file systems. This software package implements an automounter file system as a userland NFS daemon. While this generally works it has major drawbacks:

Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.103
retrieving revision 1.104
diff -u -r1.103 -r1.104
--- wikisrc/ports/evbarm/allwinner.mdwn	24 Nov 2019 14:43:29 -0000	1.103
+++ wikisrc/ports/evbarm/allwinner.mdwn	24 Nov 2019 14:45:36 -0000	1.104
@@ -158,7 +158,7 @@
 
 To fix jittery touch input on the touchpad, you can adjust the input sensitivity by creating the file:
 
-[[!template  id=filecontent name="/etc/X11/xorg.conf.d/00-system-keyboard.conf" text="""
+[[!template  id=filecontent name="/etc/X11/xorg.conf.d/00-system-touchpad.conf" text="""
 Section "InputDevice"
         Identifier "Pinebook touchpad"    
         Driver "mouse"

Add touchpad sensitivity fix
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -r1.102 -r1.103
--- wikisrc/ports/evbarm/allwinner.mdwn	5 Sep 2019 21:00:37 -0000	1.102
+++ wikisrc/ports/evbarm/allwinner.mdwn	24 Nov 2019 14:43:29 -0000	1.103
@@ -154,6 +154,21 @@
 EndSection
 """]]
 
+## Pinebook touchpad
+
+To fix jittery touch input on the touchpad, you can adjust the input sensitivity by creating the file:
+
+[[!template  id=filecontent name="/etc/X11/xorg.conf.d/00-system-keyboard.conf" text="""
+Section "InputDevice"
+        Identifier "Pinebook touchpad"    
+        Driver "mouse"
+        Option "AccelerationProfile" "2"
+        Option "AdaptiveDeceleration" "1"
+        Option "ConstantDeceleration" "2.4" # Pinebook 14"
+        #Option "ConstantDeceleration" "1.2" # Pinebook 11"
+EndSection
+"""]]
+
 ## Pinebook screen
 
 X11 currently cannot work out the size of the screen, resulting in a very small DPI on a very small screen.

Document cvs issues
Index: wikisrc/reproducable_builds.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/reproducable_builds.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/reproducable_builds.mdwn	22 Nov 2019 14:07:06 -0000	1.1
+++ wikisrc/reproducable_builds.mdwn	22 Nov 2019 14:34:04 -0000	1.2
@@ -8,4 +8,16 @@
 
 There are various advantages, one of them is the possibility to create binary patches later (after changing small things in the source, e.g. for security fixes). They are also useful if you do not trust the official builds, or are doing local builds and want to compare parts supposed to be identical.
 
-  TBD - page under construction
+# The Source
+
+First prerequisite for reproducing a build is to get the same source. With cvs (as we use it now) this either happens via using a relase tag or a date for a checkout. Assuming you do a clean new checkout, examples would be:
+
+  cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot co -r netbsd-8-1-RELEASE src xsrc
+
+or
+
+  cvs -d anoncvs@anoncvs.NetBSD.org:/cvsroot co -D "20190401 12:00UTC" src xsrc
+
+If you are not using a fresh checkout (but updating an existing one) make sure to use the *-t* option to force cvs to use the commit time (instead of the update time) for updated files.
+
+# TBD - page under construction

start documenting our reproducable builds
--- /dev/null	2019-11-22 14:04:17.673612450 +0000
+++ wikisrc/reproducable_builds.mdwn	2019-11-22 14:07:45.034835756 +0000
@@ -0,0 +1,11 @@
+[[!meta title="Reproducable Builds"]]
+
+# What is a Reproducable Build?
+
+There are various definitions, but we will use common sense here: if I install a NetBSD release on a machine and come back to it in a year (or 10), it should be possible to create all of the installation again, 100% bitwise identical.
+
+# Why are Reproducable Builds a good thing?
+
+There are various advantages, one of them is the possibility to create binary patches later (after changing small things in the source, e.g. for security fixes). They are also useful if you do not trust the official builds, or are doing local builds and want to compare parts supposed to be identical.
+
+  TBD - page under construction

Index: wikisrc/tutorials.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials.mdwn,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- wikisrc/tutorials.mdwn	11 Jun 2019 13:16:32 -0000	1.38
+++ wikisrc/tutorials.mdwn	22 Nov 2019 13:55:23 -0000	1.39
@@ -38,6 +38,7 @@
 
 ### Testing
 * [[atf]]
+* [[reproducable_builds]]
 * [[Continuous_building_and_testing_netbsd_with_buildbot]]
 
 ### Procedural

Add BSDCan 2020 and EuroBSDCon 2020
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.83
retrieving revision 1.84
diff -u -r1.83 -r1.84
--- wikisrc/events.mdwn	19 Oct 2019 11:19:34 -0000	1.83
+++ wikisrc/events.mdwn	20 Nov 2019 10:51:17 -0000	1.84
@@ -44,6 +44,31 @@
 possible audience.
 
 
+### `Jun 2020` - BSDCan 2020, Ottawa, Canada
+
+*June 3 - 6, 2020, University of Ottawa, Ottawa, Canada*
+
+[BSDCan](https://www.bsdcan.org/2020/), a BSD conference held in
+Ottawa, Canada, quickly established itself as the technical conference
+for people working on and with 4.4BSD based operating systems and
+related projects. The organizers have found a fantastic formula
+that appeals to a wide range of people from extreme novices to
+advanced developers.
+
+
+### `Sep 2020` - EuroBSDcon 2020, Vienna, Austria
+
+*September 17 - 20, 2020, Vienna, Austria*
+
+[EuroBSDcon](https://2020.eurobsdcon.org/) is the premier European
+conference on the open source BSD operating systems attracting
+about 300 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
 -----------
 ### `Sep 2019` - EuroBSDcon 2019, Lillehammer, Norway

Link the page since it's not automatically done.
Index: wikisrc/security.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/security.mdwn	14 May 2019 17:07:52 -0000	1.7
+++ wikisrc/security.mdwn	12 Nov 2019 21:36:44 -0000	1.8
@@ -5,4 +5,5 @@
 * [Meltdown and Spectre Status Page](meltdown_spectre)
 * [Using KASLR](kaslr)
 * [Intel MDS Status Page](intel_mds)
+* [Intel TAA Status Page](intel_taa)
 

details
Index: wikisrc/security/intel_taa.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/intel_taa.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:28:31 -0000	1.5
+++ wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:33:54 -0000	1.6
@@ -1,9 +1,14 @@
 [[!meta title="Intel TAA"]]
 
+Release date: 2019-11-12
+
 ###Description
 Details and mitigation information about a sub-class of speculative execution
 side-channel vulnerabilities called TSX Asynchronous Abort (TAA).
 
+Please refer to the Intel Security Advisory 00270 located at:
+[Intel website](https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00270.html).
+
 The TAA vulnerability is a sub-set of the MDS vulnerability, already mitigated
 in NetBSD.
 

slightly clarify
Index: wikisrc/security/intel_taa.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/intel_taa.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:25:11 -0000	1.4
+++ wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:28:31 -0000	1.5
@@ -33,7 +33,8 @@
 The TAA mitigation may be provided by the already-existing MDS mitigation.
 Before enabling the TAA mitigation, you should first
 [enable the MDS mitigation](https://wiki.netbsd.org/security/intel_mds/)
-if not already enabled.
+if not already enabled. This may imply loading an updated microcode, if not
+already provided by the BIOS.
 
 Two cases must then be considered, depending the content of `machdep.taa.method`:
 
@@ -50,6 +51,6 @@
 
    * If the BIOS does not provide this updated microcode, you may use NetBSD's
      pkgsrc to fetch the latest microcode distribution from Intel via the
-     **sysutils/intel-microcode-netbsd** package. Once loaded, you can issue the
-     `sysctl -w machdep.taa.mitigated=1` command to enable the TAA-specific
-     mitigation.
+     **sysutils/intel-microcode-netbsd** package. With the new microcode loaded,
+     you can issue the `sysctl -w machdep.taa.mitigated=1` command to enable the
+     TAA-specific mitigation.

style
Index: wikisrc/security/intel_taa.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/intel_taa.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:22:49 -0000	1.3
+++ wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:25:11 -0000	1.4
@@ -31,11 +31,11 @@
 """]]
 
 The TAA mitigation may be provided by the already-existing MDS mitigation.
-Before enabling the TAA mitigation, you should first enable the MDS mitigation
+Before enabling the TAA mitigation, you should first
 [enable the MDS mitigation](https://wiki.netbsd.org/security/intel_mds/)
 if not already enabled.
 
-Two cases must be considered, depending the content of `machdep.taa.method`:
+Two cases must then be considered, depending the content of `machdep.taa.method`:
 
  * If this leaf is set to `[MDS]`, then there is no TAA-specific mitigation to
    use: the `machdep.taa.mitigated` leaf will be equal to `machdep.mds.mitigated`,

nope, let's see if this works
Index: wikisrc/security/intel_taa.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/intel_taa.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:19:44 -0000	1.2
+++ wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:22:49 -0000	1.3
@@ -44,11 +44,11 @@
  * Otherwise, there is a TAA-specific mitigation needed. Two sub-cases must be
    considered:
 
- ** If the BIOS provides an updated microcode containing this TAA-specific
+   * If the BIOS provides an updated microcode containing this TAA-specific
      mitigation, then NetBSD will have set `machdep.taa.mitigated=1` automatically
      at boot time.
 
- ** If the BIOS does not provide this updated microcode, you may use NetBSD's
+   * If the BIOS does not provide this updated microcode, you may use NetBSD's
      pkgsrc to fetch the latest microcode distribution from Intel via the
      **sysutils/intel-microcode-netbsd** package. Once loaded, you can issue the
      `sysctl -w machdep.taa.mitigated=1` command to enable the TAA-specific

formatting
Index: wikisrc/security/intel_taa.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/intel_taa.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:16:32 -0000	1.1
+++ wikisrc/security/intel_taa.mdwn	12 Nov 2019 21:19:44 -0000	1.2
@@ -35,21 +35,21 @@
 [enable the MDS mitigation](https://wiki.netbsd.org/security/intel_mds/)
 if not already enabled.
 
-Two cases must be considered, depending the content of "machdep.taa.method":
+Two cases must be considered, depending the content of `machdep.taa.method`:
 
- * If this leaf is set to "[MDS]", then there is no TAA-specific mitigation to
-   use: the "machdep.taa.mitigated" leaf will be equal to "machdep.mds.mitigated",
+ * If this leaf is set to `[MDS]`, then there is no TAA-specific mitigation to
+   use: the `machdep.taa.mitigated` leaf will be equal to `machdep.mds.mitigated`,
    and only the latter is to be used.
 
  * Otherwise, there is a TAA-specific mitigation needed. Two sub-cases must be
    considered:
 
- * * If the BIOS provides an updated microcode containing this TAA-specific
-     mitigation, then NetBSD will have set "machdep.taa.mitigated=1" automatically
+ ** If the BIOS provides an updated microcode containing this TAA-specific
+     mitigation, then NetBSD will have set `machdep.taa.mitigated=1` automatically
      at boot time.
 
- * * If the BIOS does not provide this updated microcode, you may use NetBSD's
+ ** If the BIOS does not provide this updated microcode, you may use NetBSD's
      pkgsrc to fetch the latest microcode distribution from Intel via the
      **sysutils/intel-microcode-netbsd** package. Once loaded, you can issue the
-     "sysctl -w machdep.taa.mitigated=1" command to enable the TAA-specific
+     `sysctl -w machdep.taa.mitigated=1` command to enable the TAA-specific
      mitigation.

Page for the TAA vuln.
--- /dev/null	2019-11-12 21:16:00.201438337 +0000
+++ wikisrc/security/intel_taa.mdwn	2019-11-12 21:17:11.056613241 +0000
@@ -0,0 +1,55 @@
+[[!meta title="Intel TAA"]]
+
+###Description
+Details and mitigation information about a sub-class of speculative execution
+side-channel vulnerabilities called TSX Asynchronous Abort (TAA).
+
+The TAA vulnerability is a sub-set of the MDS vulnerability, already mitigated
+in NetBSD.
+
+##Status of the Fix
+
+NetBSD-8 and above have received a fix. NetBSD-7, and all the anterior releases,
+have no planned fixes.
+
+###Mitigation
+
+The mitigation for TAA depends on the Intel CPU model and available microcode
+or motherboard BIOS revision.
+
+You may also want to disable SMT/HyperThreading to address certain aspects of
+the vulnerabilities. Should you not be able to disable SMT/HT in your BIOS, you
+can put **smtoff=YES** in your */etc/rc.conf* file.
+
+###Enabling the mitigation
+
+The two following sysctls are now available:
+
+[[!template id=programlisting text="""
+machdep.taa.mitigated = {0/1} user-settable
+machdep.taa.method = {string} constructed by the kernel
+"""]]
+
+The TAA mitigation may be provided by the already-existing MDS mitigation.
+Before enabling the TAA mitigation, you should first enable the MDS mitigation
+[enable the MDS mitigation](https://wiki.netbsd.org/security/intel_mds/)
+if not already enabled.
+
+Two cases must be considered, depending the content of "machdep.taa.method":
+
+ * If this leaf is set to "[MDS]", then there is no TAA-specific mitigation to
+   use: the "machdep.taa.mitigated" leaf will be equal to "machdep.mds.mitigated",
+   and only the latter is to be used.
+
+ * Otherwise, there is a TAA-specific mitigation needed. Two sub-cases must be
+   considered:
+
+ * * If the BIOS provides an updated microcode containing this TAA-specific
+     mitigation, then NetBSD will have set "machdep.taa.mitigated=1" automatically
+     at boot time.
+
+ * * If the BIOS does not provide this updated microcode, you may use NetBSD's
+     pkgsrc to fetch the latest microcode distribution from Intel via the
+     **sysutils/intel-microcode-netbsd** package. Once loaded, you can issue the
+     "sysctl -w machdep.taa.mitigated=1" command to enable the TAA-specific
+     mitigation.

Add FOSDEM 2020
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.82
retrieving revision 1.83
diff -u -r1.82 -r1.83
--- wikisrc/events.mdwn	24 Sep 2019 08:57:22 -0000	1.82
+++ wikisrc/events.mdwn	19 Oct 2019 11:19:34 -0000	1.83
@@ -12,6 +12,24 @@
 
 Future Events
 -------------
+### `Feb 2020` - FOSDEM 2020 Brussels, Belgium
+
+*February 1 - 2, 2020, ULB Solbosch Campus, Brussels, Belgium*
+
+[FOSDEM](https://fosdem.org/2020/) is 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
+operating systems and their talks.
+
+Please see
+[this announcement](//mail-index.NetBSD.org/netbsd-advocacy/2019/10/10/msg000816.html)
+for details.
+
+
 ### `Mar 2020` - AsiaBSDCon 2020, Tokyo, Japan
 
 *March 19 - 22, Tokyo University of Science, Tokyo, Japan*

style
Index: wikisrc/tutorials/sysinst_translations_and_testing.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/sysinst_translations_and_testing.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/sysinst_translations_and_testing.mdwn	11 Jun 2019 15:32:06 -0000	1.4
+++ wikisrc/tutorials/sysinst_translations_and_testing.mdwn	17 Oct 2019 08:51:10 -0000	1.5
@@ -25,19 +25,25 @@
 
 Make sure you are on a filesystem that does support lazy allocation (that is: not tmpfs) and do something like this (as root):
 
-    dd if=/dev/zero of=disk.img seek=6g count=1
-    vnconfig -c vnd0 disk.img
+[[!template id=programlisting text="""
+# dd if=/dev/zero of=disk.img seek=6g count=1
+# vnconfig -c vnd0 disk.img
+"""]]
 
 This will create a virtual disk (vnd0) with about 3 TB space.
 (If you are curious about the math: 6g sectors of 512 byte each plus one, so 1 sector = 1/2 kByte and 6g sectors ~3 terrabyte.)
 To get rid of the vnd, use:
 
-    vnconfig -u vnd0
-    rm disk.img
-
-Now you can just run
-
-    sysinst
+[[!template id=programlisting text="""
+# vnconfig -u vnd0
+# rm disk.img
+"""]]
+
+Now you can just run:
+
+[[!template id=programlisting text="""
+# sysinst
+"""]]
 
 and select vnd0 as installation target.
 
@@ -47,18 +53,22 @@
 
 In general they look like:
 
-    messge name_of_message {translated_content}
+[[!template id=filecontent name="msg.*.*" text="""
+message name_of_message {translated_content}
+"""]]
 
 and sometimes they have positional parameters, which typically are explained in a comment right before the message:
 
-    /* Called with:                         Example
-     *  $0 = device name                    wd0
-     *  $1 = outer partitioning name        Master Boot Record (MBR)
-     *  $2 = short version of $1            MBR
-     */
-    message dofdisk
-    {$0: schreibe die $2 Partitionstabelle ...
-    }
+[[!template id=filecontent name="msg.*.*" text="""
+/* Called with:                         Example
+ *  $0 = device name                    wd0
+ *  $1 = outer partitioning name        Master Boot Record (MBR)
+ *  $2 = short version of $1            MBR
+ */
+message dofdisk
+{$0: schreibe die $2 Partitionstabelle ...
+}
+"""]]
 
 The content (between { braces }) is free flowing text, that is: if the display is wider, newlines may be replace by spaces to fill the display width.
 Whenever a hard line break is meant, a space followed by a newline is used.

Index: wikisrc/amazon_ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/amazon_ec2.mdwn,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- wikisrc/amazon_ec2.mdwn	10 Oct 2019 14:31:51 -0000	1.54
+++ wikisrc/amazon_ec2.mdwn	10 Oct 2019 14:33:12 -0000	1.55
@@ -5,5 +5,5 @@
 * [Subscribe to Amazon EC2, and understand its vocabulary](first_steps)
 * [Launching your first NetBSD instance in 5 minutes](netbsd_in_5_min)
 * [Building your own NetBSD AMI - Xen PV](build_your_own_ami)
-* [Build instructions for NetBSD AMI with ENA/NVMe - HVM](http://www.netbsd.org/~ryoon/ena/how-to-create-ami-for-aws-c5.txt)
+* [Build instructions for NetBSD AMI with ENA support - HVM](http://www.netbsd.org/~ryoon/ena/how-to-create-ami-for-aws-c5.txt)
 * [NetBSD AMIs identifiers, by region](amis)

Index: wikisrc/amazon_ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/amazon_ec2.mdwn,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- wikisrc/amazon_ec2.mdwn	8 Oct 2019 18:55:52 -0000	1.53
+++ wikisrc/amazon_ec2.mdwn	10 Oct 2019 14:31:51 -0000	1.54
@@ -4,6 +4,6 @@
 
 * [Subscribe to Amazon EC2, and understand its vocabulary](first_steps)
 * [Launching your first NetBSD instance in 5 minutes](netbsd_in_5_min)
-* [Building your own NetBSD AMI for t* instance](build_your_own_ami)
-* [Building NetBSD AMI for c5 instance with ENA](http://www.netbsd.org/~ryoon/ena/how-to-create-ami-for-aws-c5.txt)
+* [Building your own NetBSD AMI - Xen PV](build_your_own_ami)
+* [Build instructions for NetBSD AMI with ENA/NVMe - HVM](http://www.netbsd.org/~ryoon/ena/how-to-create-ami-for-aws-c5.txt)
 * [NetBSD AMIs identifiers, by region](amis)

Index: wikisrc/amazon_ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/amazon_ec2.mdwn,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- wikisrc/amazon_ec2.mdwn	8 Oct 2019 17:24:55 -0000	1.52
+++ wikisrc/amazon_ec2.mdwn	8 Oct 2019 18:55:52 -0000	1.53
@@ -4,6 +4,6 @@
 
 * [Subscribe to Amazon EC2, and understand its vocabulary](first_steps)
 * [Launching your first NetBSD instance in 5 minutes](netbsd_in_5_min)
-* [Building your own NetBSD AMI](build_your_own_ami)
+* [Building your own NetBSD AMI for t* instance](build_your_own_ami)
+* [Building NetBSD AMI for c5 instance with ENA](http://www.netbsd.org/~ryoon/ena/how-to-create-ami-for-aws-c5.txt)
 * [NetBSD AMIs identifiers, by region](amis)
-* [How to build NetBSD AMI for c5 instance with ENA](http://www.netbsd.org/~ryoon/ena/how-to-create-ami-for-aws-c5.txt)

Index: wikisrc/amazon_ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/amazon_ec2.mdwn,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- wikisrc/amazon_ec2.mdwn	23 Feb 2018 17:32:56 -0000	1.51
+++ wikisrc/amazon_ec2.mdwn	8 Oct 2019 17:24:55 -0000	1.52
@@ -6,3 +6,4 @@
 * [Launching your first NetBSD instance in 5 minutes](netbsd_in_5_min)
 * [Building your own NetBSD AMI](build_your_own_ami)
 * [NetBSD AMIs identifiers, by region](amis)
+* [How to build NetBSD AMI for c5 instance with ENA](http://www.netbsd.org/~ryoon/ena/how-to-create-ami-for-aws-c5.txt)

Index: wikisrc/amazon_ec2/first_steps.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/amazon_ec2/first_steps.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/amazon_ec2/first_steps.mdwn	5 Feb 2013 12:31:33 -0000	1.3
+++ wikisrc/amazon_ec2/first_steps.mdwn	8 Oct 2019 11:03:51 -0000	1.4
@@ -67,4 +67,4 @@
 
 These instances are tied to a *region* (a geographical location; typically US East, US West, Europe West, etc.). Each region has *availability zones*, which can be compared to a sub-region, each one being physically distinct from another. Regions are identified by a name, like *us-east-1*, *eu-west-1*. Same goes for availability zones, usually with the region's name as prefix: *us-east-1a*, *us-east-1b*, and so forth. Note that resources are **not** shared between zones, so if you transfer data from one zone to another, you will be charged for it.
 
-AKI, or *Amazon Kernel Image*, are a specific type of image. It represents the Xen guest para-virtualized kernel, as used by an AMI. Certain AKIs are allowed to boot customized operating systems, e.g. those that are still not officially supported by Amazon. Thanks to [PyGrub](http://wiki.xensource.com/xenwiki/PyGrub), it can boot a kernel that resides inside an AMI's snapshot.
+AKI, or *Amazon Kernel Image*, are a specific type of image. It represents the Xen guest para-virtualized kernel, as used by an AMI. Certain AKIs are allowed to boot customized operating systems, e.g. those that are still not officially supported by Amazon. Thanks to [PyGrub](https://wiki.xenproject.org/wiki/PyGrub), it can boot a kernel that resides inside an AMI's snapshot.

Remove outdated copy of current users FAQ.
https://www.netbsd.org/docs/current/
--- wikisrc/tracking_current.mdwn	2019-10-04 12:07:26.468589119 +0000
+++ /dev/null	2019-10-04 12:06:07.408550622 +0000
@@ -1,446 +0,0 @@
-# Tracking NetBSD-current
-
-**Contents**
-
-[[!toc levels=2]]
-
-## Why track NetBSD-current?
-
-The developers of NetBSD have made the current development sources
-available to the public for several reasons. Overall, providing
-NetBSD-current helps us to create a more stable, accessible system.
-
-It makes it easier for people to become involved in the development of
-NetBSD. Distributing the current development sources allows a greater
-number of people to see where the system is going, and to become
-involved with new features as they are implemented.
-
-It also makes changes from users easier to integrate. If users make
-changes against the current development sources, then virtually no
-integration is needed to get them into the master source tree.
-
-It also allows wider testing of the software as it is developed. Users
-of NetBSD-current are encouraged to send in
-[bug reports](http://netbsd.org/support/send-pr.html) about the current sources,
-and that helps find and fix bugs. Because people are testing the software soon
-after it's written, more bugs can be found and eliminated.
-
-## Things you need to remember
-
- * People using NetBSD-current are strongly encouraged to subscribe to
-   the [current-users](http://netbsd.org/mailinglists/#current-users) mailing
-   list. The [source-changes](http://netbsd.org/mailinglists/#source-changes)
-   mailing list is also of interest.
-
- * When upgrading to a more recent version of -current you should
-   *always* install and boot a new kernel before installing any new libs (unless 
-   you are certain there have been no new system calls added, but do it anyway; 
-   it's safer).In general the best approach is to try the new kernel before 
-   anything else, and if you hit any problems see the entry in the
-   [Kernel FAQ](http://netbsd.org/docs/kernel/#problems_compiling_a_current_kernel).
-
- * When compiling a -current kernel, always remember to include the
-   `COMPAT_<lastrelease>` option (e.g., `COMPAT_80`). As current diverges from
-   the last stable release, compatibility code will be added, but it will only
-   be enabled if this option is present. At a bare minimum, you will need this
-   compatibility code for the time between booting the new kernel and finishing
-   your build via `build.sh`
-
-## Updating an existing system from a current snapshot
-
-*Please remember to check
-[src/UPDATING](http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/UPDATING) for
-quirks around certain specific changes.*
-
-To quickly begin using current, start with a snapshot generated by release
-engineering. The current status of each platform can be seen at
-[NetBSD Autobuild](http://releng.NetBSD.org/cgi-bin/builds.cgi) and the
-corresponding releases found in by date and platform.
-
- 1. Hunt down to the desired `binary/sets` directory, and `mget *.tgz` files
-    into your favorite local administrative directory (for example,
-    `$HOME/current`); when limited by disk space and/or time, only
-	`kern-GENERIC`, `etc`, `base`, and `comp` (if you want a compiler) are
-	essential.
- 2. Extract the desired kernel (usually `GENERIC`), copy it into (root) directory.
-
-        # cd /root
-        # tar -zxpf ~/kern-GENERIC.tgz
-        # ln -fh /netbsd /netbsd.old
-        # cp netbsd /netbsd.new
-        # ln -fh /netbsd.new /netbsd
-
-    > **Warning**: Don't extract any userland binary sets before rebooting your
-    > machine with the new kernel. Newer binaries might use new system calls an
-    > old running kernel doesn't support.
-
- 3. Check if there are any other files which might also be required by a new
-    kernel. Again,
-    [src/UPDATING](http://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/UPDATING)
-    might mention possible quirks on daily changes.
-	
-	The following items are typical files that possibly need to be updated:
-
-     1. bootloader
-        
-        Usually a machine specific bootloader passes several parameters to a 
-        loaded kernel. If some new parameters have been added or some existing 
-        APIs between bootloader and kernel are changed you might also have to 
-        install new bootloader files for a new kernel to handle new features. A 
-        method to update bootloader files is quite machine dependent, so check 
-        boot(8) and installboot(8) man pages for details.
-        
-        
-        On i386 and amd64, if you are using FFSv1 for root file system on `wd0a` 
-        (i.e. first ATA drive), typical commands to update bootloaders are:
-
-            # tar -C /tmp -zxf ~/base.tgz ./usr/mdec
-            # cp /tmp/usr/mdec/boot /
-            # installboot -v /dev/rwd0a /tmp/usr/mdec/bootxx_ffsv1
-
-        If you are using FFSv2 for root file system use the following commands 
-        instead:
-
-            # tar -C /tmp -zxf ~/base.tgz ./usr/mdec
-            # cp /tmp/usr/mdec/boot /
-            # installboot -v /dev/rwd0a /tmp/usr/mdec/bootxx_ffsv2
-
-        Note `/usr/mdec/bootxx_ffsv1` and `/usr/mdec/bootxx_ffsv2` are primary 
-        bootloaders which are file system dependent. `/usr/mdec/boot` is 
-        secondary loader and it's file system independenet.
-
-        If you forget your root file system type (FFSv1 or FFSv2), you can check 
-        it by dumpfs(8) command:
-
-            # dumpfs /dev/rwd0a | head -3
-            file system: /dev/rwd0a
-            format  FFSv2
-            endian  little-endian
-
-     2. kernel modules
-
-        A new framework *kernel modules* was been introduced after netbsd-5 was 
-        branched.
-        The kernel module files 
-        will be loaded dynamically by the kernel to support various kernel 
-        options (including file systems) on demand, rather than linking all 
-        necessary (but possibly unused) object files into the kernel binary. 
-        This means if you are trying to boot a new `GENERIC` kernel, you also 
-        have to prepare new kernel module files for the new kernel. 
-
-        To prepare new kernel module files, you can simply use a new `modules` 
-        set file which has been prepared since September 2009:
-
-            # cd /
-            # tar -zxpf ~/modules.tgz
-                
-        Note i386 port also provides `MONOLITHIC` kernel binary in 
-        `kern-MONOLITHIC.tgz` set file since October 2009. The `MONOLITHIC` 
-        kernel includes all necessary options in its kernel as well as 5.0 and 
-        prior `GENERIC` kernels and it doesn't depend on kernel module files at 
-        all. If you would just like to test new features of a new kernel without 
-        updating kernel modules, using `MONOLITHIC` kernel is easier way for the 
-        first and quick trial. 
-
-        It's also a good idea to put an old `MONOLITHIC` kernel into `/` (root) 
-        directory for emergency and recovery because if newer modules have some 
-        fatal issue there is no easy way to specify an alternative path of old 
-        module files to a modular'ized kernel (and you can't rename directories 
-        without a working kernel).
-
- 4. Reboot machine with the new kernel:
-
-        # shutdown -r now
-
- 5. Make sure the new kernel boots and works properly. If your new kernel has
-    any trouble, you can recover it by loading the renamed old one. If you are 
-    using a modularised GENERIC kernel as mentioned above, you might also have to 
-    restore old kernel module files.
-
- 6. Extract the matching base, and any other desirable feature sets **except 
-    etc**:
-
-        # cd /
-        # tar -zxpf ~/base.tgz
-        # tar -zxpf ~/comp.tgz
-        # ...
-            
-
-    Don't forget to specify "p" option (preserve permissions) on tar(1) command 
-    otherwise setuid'ed commands (like su(1)) won't work.
-
-    **Warning**: Extracting `etc.tgz` on the installed system will overwrite your 
-    local settings.
-
- 7. [Update](http://netbsd.org/docs/current/index.html#etcupdate) `/etc` as the 
-    last step: postinstall(8) will first check and fix most things that can be 
-    automated, and etcupdate(8) in the second step will ask on what to merge:
-
-        # /usr/sbin/postinstall -s ~/etc.tgz check
-        # /usr/sbin/postinstall -s ~/etc.tgz fix
-        # /usr/sbin/etcupdate -s ~/etc.tgz
-        # shutdown -r now
-            
-    If you have the X sets installed (xbase, ...), you can repeat the 
-	postinstall and etcupdate steps with xetc.tgz as argument before rebooting.
-
-At this point, you are relatively current and ready to build your own current 
-source.
-
-## Downloading current source
-
-See the [Obtaining the sources](http://netbsd.org/docs/guide/en/chap-fetch.html) 
-section in the [[NetBSD Guide|guide/index]].
-
-## Building a release from source
-
-See the [Crosscompiling NetBSD](http://netbsd.org/docs/guide/en/chap-build.html) 

(Diff truncated)
Index: wikisrc/ports/evbarm/tegra.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/tegra.mdwn,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- wikisrc/ports/evbarm/tegra.mdwn	11 Oct 2017 08:43:24 -0000	1.49
+++ wikisrc/ports/evbarm/tegra.mdwn	4 Oct 2019 10:13:52 -0000	1.50
@@ -1,9 +1,9 @@
 [[!meta title="NetBSD/evbarm on NVIDIA Tegra"]]
 
-NetBSD 8.0 supports the NVIDIA Tegra K1 (32-bit) system-on-a-chip.
-NetBSD -current adds support for the NVIDIA Tegra X1 system-on-a-chip.
+NetBSD 8.0 supports the NVIDIA Tegra K1 (32-bit) system-on-a-chip.  
+NetBSD 9.0 adds support for the NVIDIA Tegra X1 system-on-a-chip.
 
-The [NVIDIA Jetson TK1 development kit](https://developer.nvidia.com/jetson-tk1) is a board based on the Tegra K1 SoC.
+The [NVIDIA Jetson TK1 development kit](https://developer.nvidia.com/jetson-tk1) is a board based on the Tegra K1 SoC.  
 The [NVIDIA Jetson TX1 development kit](https://developer.nvidia.com/jetson-tx1) is a board based on the Tegra X1 SoC.
 
 

Adjust port_alt to point to port-powerpc@ ML (there was/is not any
port-evbppc@ ML)
Problem noticed by Tim via WWW Feedback form.
Members: 
	ports/evbppc.mdwn:1.21->1.22 

Index: wikisrc/ports/evbppc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbppc.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/ports/evbppc.mdwn	2 Jun 2019 13:32:38 -0000	1.21
+++ wikisrc/ports/evbppc.mdwn	3 Oct 2019 20:47:56 -0000	1.22
@@ -1,5 +1,6 @@
 [[!template id=port
 port="evbppc"
+port_alt="powerpc"
 cur_rel="8.1"
 future_rel="9.0"
 changes_cur="8.1"

Sync with htdocs/global.css,-r1.86
Index: wikisrc/global.css
===================================================================
RCS file: /cvsroot/wikisrc/global.css,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/global.css	4 Sep 2019 22:09:32 -0000	1.12
+++ wikisrc/global.css	24 Sep 2019 09:02:37 -0000	1.13
@@ -1,4 +1,4 @@
-/* $NetBSD: global.css,v 1.12 2019/09/04 22:09:32 cnst Exp $ */
+/* $NetBSD: global.css,v 1.13 2019/09/24 09:02:37 leot Exp $ */
 
 /* ##### Common Styles ##### */
 
@@ -148,7 +148,6 @@
 
 #navBar {
   font-size: 14px;
-  min-width: 1050px;
   background-color: #444;
 }
 
@@ -191,6 +190,13 @@
   white-space: nowrap;
 }
 
+@media only screen and (min-device-width: 801px) and (max-width: 1050px) {
+  #navBar ul li:last-child ul {
+	left: inherit;
+	right: 7%;
+  }
+}
+
 #navBar ul li ul li a {
   min-width: 8em;
   border-left:  1px solid #fd6720;
@@ -414,7 +420,7 @@
 }
 
 .fullWidth {
-  width: 96%;
+  width: inherit;
   padding: 0 1.2em;
   border-left: none;
 }
@@ -567,28 +573,26 @@
 	Padding: 5pt;
 }
 
-th, td {
+#content table:not([border='0']) th {
+	border: 3px solid #eee;
+}
+#content table:not([border='0']) td:not(:empty) {
 	border: 1px solid #ddd;
 }
+#content table:not([border]) {
+	border-collapse: collapse;
+}
 
-td.developerslist {
+table.developerslist td {
 	White-space: nowrap;
-	Padding: 0.3em 0.3em 0.3em 0.3em;
+	vertical-align: middle;
 }
 
-td.developerslistwrap {
+table.developerslist td.developerslistwrap {
         White-space: normal;
-        Padding: 0.3em 0.3em 0.3em 0.3em;
-}
-
-table.developerslist {
-	Border-Width: 0.0em;
-	Margin-Left: 0.5em;
-	Margin-Right: 0.5em;
 }
 
 table.downloadtable {
-  border: 0;
   width: 100%;
 }
 
@@ -705,59 +709,46 @@
   display: none;
 }
 
-table.build-results th {
+table.build-results > tbody > tr > th[rowspan] {
   text-align: left;
+  vertical-align: top;
+  padding: 8pt;
 }
 
-table.build-results td {
-  padding: 0 1em 0 0;
+table.build-results > tbody > tr > td {
+  text-align: right;
 }
 
-table.build-results td.empty {
-  padding: 0 3em 0 0;
+table.build-results > tbody > tr:first-child > td {
+  padding-top: 8pt;
 }
 
-table.build-results td.build-time {
-  text-align: right;
-  padding-right: 0;
-  font-family: Ubuntu Mono, DejaVu Sans Mono, Lucida Console, Courier, monospace;
+table.build-results > tbody > tr:last-child > td {
+  padding-bottom: 8pt;
 }
 
-table.build-results td.failed {
-  color: red;
+table.build-results > tbody > tr > td {
+  padding: 0 8pt;
 }
 
-table.build-results td.totals {
-  text-align: right;
-  padding-right: 1em;
+table.build-results > tbody {
+  font-family: Ubuntu Mono, DejaVu Sans Mono, Lucida Console, Courier, monospace;
 }
 
 table.build-results td.good {
   color: #50FF50;
-  text-align: right;
-  padding-right: 2em;
 }
 
 table.build-results td.partial {
   color: #008000;
-  text-align: right;
-  padding-right: 2em;
 }
 
 table.build-results td.all-ok {
   color: #c0c0c0;
-  text-align: right;
-  padding-right: 2em;
 }
 
 table.build-results td.fails {
   color: red;
-  text-align: right;
-  padding-right: 2em;
-}
-
-table.build-results {
-  padding-bottom: 2em;
 }
 
 /* mobile overrides:
@@ -769,10 +760,6 @@
        only screen and (-webkit-min-device-pixel-ratio: 2) and (max-width: 800px) {
 	body {
 	  font-size: xx-large;
-	  margin-top: 2em;
-	}
-	#centralHeader {
-	  display: none;
 	}
 
 	#navBar {
@@ -834,21 +821,6 @@
 	  margin: 0 !important;
 	}
 
-	.menuicon {
-	  position: fixed;
-	  width: 100%;
-	  background-color: #f8f8f8;
-	  top: 0;
-	  right: 0;
-	  z-index:200;
-	  display: block;
-	  height: 2.5em;
-	  -webkit-transition-duration: 0.5s;
-	  -moz-transition-duration: 0.5s;
-	  -ms-transition-duration: 0.5s;
-	  -o-transition-duration: 0.5s;
-	  transition-duration: 0.5s;
-	}
 	.menuicon span {
 	  display: block;
 	  background-color: #fd6720;

Move EuroBSDCon 2019 to past events
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.81
retrieving revision 1.82
diff -u -r1.81 -r1.82
--- wikisrc/events.mdwn	2 Sep 2019 22:17:05 -0000	1.81
+++ wikisrc/events.mdwn	24 Sep 2019 08:57:22 -0000	1.82
@@ -12,19 +12,6 @@
 
 Future Events
 -------------
-### `Sep 2019` - EuroBSDcon 2019, Lillehammer, Norway
-
-*September 19 - 22, 2019, Scandic Lillehammer Hotel, Lillehammer, Norway*
-
-[EuroBSDcon](https://2019.eurobsdcon.org/) is the premier European
-conference on the open source BSD operating systems attracting
-about 300 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.
-
-
 ### `Mar 2020` - AsiaBSDCon 2020, Tokyo, Japan
 
 *March 19 - 22, Tokyo University of Science, Tokyo, Japan*
@@ -41,6 +28,19 @@
 
 Past Events
 -----------
+### `Sep 2019` - EuroBSDcon 2019, Lillehammer, Norway
+
+*September 19 - 22, 2019, Scandic Lillehammer Hotel, Lillehammer, Norway*
+
+[EuroBSDcon](https://2019.eurobsdcon.org/) is the premier European
+conference on the open source BSD operating systems attracting
+about 300 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.
+
+
 ### `Jul 2019` - pkgsrcCon 2019, Cambridge, United Kingdom
 
 *July 13 - 14, 2019, Cambridge, United Kingdom*

Add some upstream bug reports.
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/users/maya/vax-gcc.mdwn	31 Aug 2019 13:17:56 -0000	1.11
+++ wikisrc/users/maya/vax-gcc.mdwn	15 Sep 2019 12:56:38 -0000	1.12
@@ -2,7 +2,7 @@
 
 [WIP tree](gcc-mirror/)
 
-## libgomp crash with -O2 ##
+## libgomp crash with -O2 [#58901](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58901) ##
 Repro:
 
     #!/bin/sh
@@ -24,6 +24,24 @@
 It looks like a real bug in vax_legitimate_address_p not handling some addressing modes.  
 The code to handle offset(reg)[index] might be off: it doesn't like if neither xfoo0, xfoo1 are constant.
 
+
+## change_address_1, at emit-rtl.c:2286 [#85152](https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85152) ##
+
+Repro:
+
+    #!/bin/sh
+
+    cat << EOF > oacc.i
+    void fn2();
+    unsigned a;
+    int fn1() {
+      int b = a >> 16;
+      if (b)
+        fn2();
+    }
+    EOF
+    vax--netbsdelf-gcc -O2 -c oacc.i
+
 ## unrecognizable insn with any optimization ##
 
 Repro:

markup mistake in previous
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- wikisrc/releng/netbsd9.mdwn	8 Sep 2019 09:06:43 -0000	1.54
+++ wikisrc/releng/netbsd9.mdwn	8 Sep 2019 09:08:20 -0000	1.55
@@ -9,8 +9,8 @@
 * [[!template id=pr number=53016]]: Clock not stable /!\
 * [[!template id=pr number=53017]]: Kernel panics every now and then with "fpusave_lwp: did not" message
 * [[!template id=pr number=53155]]: Wedge after <12h uptime when >2 bnx network interfaces in use /!\
-* ~~[[!template id=pr number=53161]]: ATF test runs leave a rump_server process around
-* ~~[[!template id=pr number=53286]]: hdaudio(4), iwm(4) and rtsx(4) detections fail in UEFI case /!\
+* ~~[[!template id=pr number=53161]]: ATF test runs leave a rump_server process around~~
+* ~~[[!template id=pr number=53286]]: hdaudio(4), iwm(4) and rtsx(4) detections fail in UEFI case /!\~~
 * [[!template id=pr number=53291]]: GPT prevents installation
 
 Regression since [[netbsd8]]:

Add another bug with bounty and update some old ones
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.53
retrieving revision 1.54
diff -u -r1.53 -r1.54
--- wikisrc/releng/netbsd9.mdwn	3 Sep 2019 13:03:52 -0000	1.53
+++ wikisrc/releng/netbsd9.mdwn	8 Sep 2019 09:06:43 -0000	1.54
@@ -9,8 +9,8 @@
 * [[!template id=pr number=53016]]: Clock not stable /!\
 * [[!template id=pr number=53017]]: Kernel panics every now and then with "fpusave_lwp: did not" message
 * [[!template id=pr number=53155]]: Wedge after <12h uptime when >2 bnx network interfaces in use /!\
-* [[!template id=pr number=53161]]: ATF test runs leave a rump_server process around
-* [[!template id=pr number=53286]]: hdaudio(4), iwm(4) and rtsx(4) detections fail in UEFI case /!\
+* ~~[[!template id=pr number=53161]]: ATF test runs leave a rump_server process around
+* ~~[[!template id=pr number=53286]]: hdaudio(4), iwm(4) and rtsx(4) detections fail in UEFI case /!\
 * [[!template id=pr number=53291]]: GPT prevents installation
 
 Regression since [[netbsd8]]:
@@ -21,7 +21,7 @@
 * [[!template id=pr number=54093]]: Recent test regressions on sparc
 * [[!template id=pr number=54300]]: lib/libutil/t_snprintb test regression on sparc
 * [[!template id=pr number=54345]]: kernel diagnostic assertion "xfer != NULL" in wdc.c
-
+* [[!template id=pr number=54503]]: Panic during attaching nvme(4) when # of logical CPUs >= 32 ? /!\
 
 ## Bug Bountys
 

Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -r1.101 -r1.102
--- wikisrc/ports/evbarm/allwinner.mdwn	5 Feb 2019 19:47:58 -0000	1.101
+++ wikisrc/ports/evbarm/allwinner.mdwn	5 Sep 2019 21:00:37 -0000	1.102
@@ -20,25 +20,25 @@
     </tr>
   </thead>
   <tbody>
-    <tr><td>sun4i</td><td>A10</td><td>8.99.3 and later</td><td><a href="https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/open-source-hardware">Olimex A10-OLinuXino-LIME</a><td></td></tr>
+    <tr><td>sun4i</td><td>A10</td><td>9.0</td><td><a href="https://www.olimex.com/Products/OLinuXino/A10/A10-OLinuXino-LIME/open-source-hardware">Olimex A10-OLinuXino-LIME</a><td></td></tr>
     <tr><td>sun5i</td><td>A10s</td><td>-</td><td></td></tr>
-    <tr><td>sun5i</td><td>A13</td><td>8.99.2 and later</td><td><a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/open-source-hardware">Olimex A13-OLinuXino</a>, <a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/open-source-hardware">Olimex A13-OLinuXino-MICRO</a></td></tr>
-    <tr><td>sun5i</td><td>GR8</td><td>8.99.5</td><td><a href="https://getchip.com/pages/chippro">C.H.I.P. Pro</a></td><td></td></tr>
-    <tr><td>sun5i</td><td>R8</td><td>8.99.2 and later</td><td><a href="https://getchip.com/pages/chip">C.H.I.P.</a>, <a href="https://getchip.com/pages/pocketchip">Pocket C.H.I.P.</a></td><td></td></tr>
-    <tr><td>sun6i</td><td>A31</td><td>7.0 and later</td><td><a href="http://linux-sunxi.org/Merrii_Hummingbird_A31">Merrii Hummingbird A31</a></td><td></td></tr>
+    <tr><td>sun5i</td><td>A13</td><td>9.0</td><td><a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino/open-source-hardware">Olimex A13-OLinuXino</a>, <a href="https://www.olimex.com/Products/OLinuXino/A13/A13-OLinuXino-MICRO/open-source-hardware">Olimex A13-OLinuXino-MICRO</a></td></tr>
+    <tr><td>sun5i</td><td>GR8</td><td>9.0</td><td><a href="https://getchip.com/pages/chippro">C.H.I.P. Pro</a></td><td></td></tr>
+    <tr><td>sun5i</td><td>R8</td><td>9.0</td><td><a href="https://getchip.com/pages/chip">C.H.I.P.</a>, <a href="https://getchip.com/pages/pocketchip">Pocket C.H.I.P.</a></td><td></td></tr>
+    <tr><td>sun6i</td><td>A31</td><td>7.0</td><td><a href="http://linux-sunxi.org/Merrii_Hummingbird_A31">Merrii Hummingbird A31</a></td><td></td></tr>
     <tr><td>sun6i</td><td>A31s</td><td>-</td><td></td><td></td></tr>
-    <tr><td>sun7i</td><td>A20</td><td>7.0 and later</td><td><a href="https://linux-sunxi.org/Cubietech_Cubieboard2">Cubietech Cubieboard 2</a>, <a href="https://linux-sunxi.org/Cubietruck">Cubietech Cubietruck</a>, <a href="http://linux-sunxi.org/LeMaker_Banana_Pi">LeMaker Banana Pi</a></td><td></td></tr>
+    <tr><td>sun7i</td><td>A20</td><td>7.0</td><td><a href="https://linux-sunxi.org/Cubietech_Cubieboard2">Cubietech Cubieboard 2</a>, <a href="https://linux-sunxi.org/Cubietruck">Cubietech Cubietruck</a>, <a href="http://linux-sunxi.org/LeMaker_Banana_Pi">LeMaker Banana Pi</a></td><td></td></tr>
     <tr><td>sun8i</td><td>A23</td><td>-</td><td></td></tr>
     <tr><td>sun8i</td><td>A33</td><td>-</td><td><a href="https://www.olimex.com/Products/OLinuXino/A33/A33-OLinuXino/open-source-hardware">Olimex A33-OLinuXino</a></td></tr>
     <tr><td>sun8i</td><td>R40</td><td>-</td><td><a href="http://www.banana-pi.org/m2u.html">Sinovoip Banana Pi BPI-M2U</a></td></tr>
-    <tr><td>sun8i</td><td>A83T</td><td>8.0 and later</td><td><a href="http://www.banana-pi.org/m3.html">Sinovoip Banana Pi BPI-M3</a></td><td></td></tr>
-    <tr><td>sun8i</td><td>H2+</td><td>8.0 and later</td><td><a href="http://www.orangepi.org/orangepizero/">Xunlong Orange Pi Zero</a></td><td></td></tr>
-    <tr><td>sun8i</td><td>H3</td><td>8.0 and later</td><td><a href="http://nanopi.io/nanopi-neo.html">FriendlyARM NanoPi NEO</a>, <a href="http://www.orangepi.org/orangepiplus2e/">Xunlong Orange Pi Plus 2E</a></td><td></td></tr>
+    <tr><td>sun8i</td><td>A83T</td><td>8.0</td><td><a href="http://www.banana-pi.org/m3.html">Sinovoip Banana Pi BPI-M3</a></td><td></td></tr>
+    <tr><td>sun8i</td><td>H2+</td><td>8.0</td><td><a href="http://www.orangepi.org/orangepizero/">Xunlong Orange Pi Zero</a></td><td></td></tr>
+    <tr><td>sun8i</td><td>H3</td><td>8.0</td><td><a href="http://nanopi.io/nanopi-neo.html">FriendlyARM NanoPi NEO</a>, <a href="http://www.orangepi.org/orangepiplus2e/">Xunlong Orange Pi Plus 2E</a></td><td></td></tr>
     <tr><td>sun8i</td><td>V3s</td><td>-</td><td><a href="https://www.indiegogo.com/projects/licheepi-zero-6-extensible-linux-module-on-finger-wifi-diy#/">Lichee Pi Zero</a></td><td></td></tr>
-    <tr><td>sun9i</td><td>A80</td><td>8.0 and later</td><td><a href="http://linux-sunxi.org/Cubietech_Cubieboard4">Cubietech Cubieboard 4</a></td><td></td></tr>
-    <tr><td>sun50i</td><td>A64</td><td>8.99.2 and later</td><td><a href="https://www.pine64.org/?page_id=1194">Pine64</a>, <a href="https://www.pine64.org/?page_id=3707">Pinebook</a></td><td></td></tr>
-    <tr><td>sun50i</td><td>H5</td><td>8.99.4 and later</td><td><a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180">FriendlyARM NanoPi NEO2, <a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=196">FriendlyARM NanoPi NEO Plus2</a></td><td></td></tr>
-    <tr><td>sun50i</td><td>H6</td><td>8.99.14 and later</td><td><a href="http://www.orangepi.org/OrangePiOneplus/">Orange Pi One Plus</a>, <a href="https://www.pine64.org/?product_cat=pine-h64-boards">Pine H64</a></td></tr>
+    <tr><td>sun9i</td><td>A80</td><td>8.0</td><td><a href="http://linux-sunxi.org/Cubietech_Cubieboard4">Cubietech Cubieboard 4</a></td><td></td></tr>
+    <tr><td>sun50i</td><td>A64</td><td>9.0</td><td><a href="https://www.pine64.org/?page_id=1194">Pine64</a>, <a href="https://www.pine64.org/?page_id=3707">Pinebook</a></td><td></td></tr>
+    <tr><td>sun50i</td><td>H5</td><td>9.0</td><td><a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180">FriendlyARM NanoPi NEO2, <a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=196">FriendlyARM NanoPi NEO Plus2</a></td><td></td></tr>
+    <tr><td>sun50i</td><td>H6</td><td>9.0</td><td><a href="http://www.orangepi.org/OrangePiOneplus/">Orange Pi One Plus</a>, <a href="https://www.pine64.org/?product_cat=pine-h64-boards">Pine H64</a></td></tr>
   </tbody>
 </table>
 
@@ -92,7 +92,7 @@
 
 # Installation
 
-- Download or build **armv7.img** (32-bit) or **arm64.img** (64-bit) from NetBSD -current
+- Download or build **armv7.img** (32-bit) or **arm64.img** (64-bit) from NetBSD 9.0 or later
 - Write the image to disk: **dd if=armv7.img of=/dev/rld0d bs=1m conv=sync**
 - Install a board-specific U-Boot (2018.05 or later) from pkgsrc to the SD card
   (the `u-boot-sunxi-with-spl.bin`-s are provided by `sysutils/u-boot-<boardname>` packages):

global.css: add a border around th and td elements (because tables without borders look weird)
Index: wikisrc/global.css
===================================================================
RCS file: /cvsroot/wikisrc/global.css,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/global.css	18 May 2019 13:19:36 -0000	1.11
+++ wikisrc/global.css	4 Sep 2019 22:09:32 -0000	1.12
@@ -1,4 +1,4 @@
-/* $NetBSD: global.css,v 1.11 2019/05/18 13:19:36 leot Exp $ */
+/* $NetBSD: global.css,v 1.12 2019/09/04 22:09:32 cnst Exp $ */
 
 /* ##### Common Styles ##### */
 
@@ -567,6 +567,10 @@
 	Padding: 5pt;
 }
 
+th, td {
+	border: 1px solid #ddd;
+}
+
 td.developerslist {
 	White-space: nowrap;
 	Padding: 0.3em 0.3em 0.3em 0.3em;

amazon_ec2/amis.mdwn: document how resize_root is performed; confirmed with <riz>
Index: wikisrc/amazon_ec2/amis.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/amazon_ec2/amis.mdwn,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- wikisrc/amazon_ec2/amis.mdwn	22 Nov 2015 01:18:54 -0000	1.48
+++ wikisrc/amazon_ec2/amis.mdwn	4 Sep 2019 03:56:55 -0000	1.49
@@ -6,7 +6,9 @@
 
 Starting with the NetBSD 7.0 AMIs, the images have a very small disk
 by default.  If you launch it with a larger disk, it will resize the
-root file system on initial boot, expanding it to the full size of
+root file system on initial boot
+(through [`/etc/rc.d/resize_root`](http://bxr.su/n/etc/rc.d/resize_root)),
+expanding it to the full size of
 your primary disk.  The 6.x AMIs default to a 5GB root file system,
 and do not currently auto-expand.
 

Abandon GCC 8+ for NetBSD-9
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- wikisrc/releng/netbsd9.mdwn	3 Sep 2019 13:01:02 -0000	1.52
+++ wikisrc/releng/netbsd9.mdwn	3 Sep 2019 13:03:52 -0000	1.53
@@ -56,7 +56,6 @@
 
 ## Nice to have
 
-* gcc 8+ from a sanitizers point of view
 * ~~~arm: GENERIC kernel config for armv7 boards.~~~ (done)
 * ~~~arm64: Support for servers following SBSA/SBBR standards~~~ (done)
 * ~~~updated graphics drivers~~~ (done)
@@ -72,4 +71,8 @@
 * address failing ptrace(2) tests, cover the remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
 * rework semantics of threading operations in ptrace(2)
 
+## Abandoned for 9.0
+
+* ~~~gcc 8+ from a sanitizers point of view~~~ (abandoned)
+
 ...

Add strike formating for finished feature
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- wikisrc/releng/netbsd9.mdwn	3 Sep 2019 12:59:22 -0000	1.51
+++ wikisrc/releng/netbsd9.mdwn	3 Sep 2019 13:01:02 -0000	1.52
@@ -47,7 +47,7 @@
 * ZFS
 * ~~~kASan for amd64~~~ (done)
 * ~~~kASan for aarch64~~~ (done)
-* compiler-rt in the base with enabled features for Clang/LLVM (done)
+* ~~~compiler-rt in the base with enabled features for Clang/LLVM~~~ (done)
 * LVM mirror target
 * ~~~add NVMM~~~ (done)
 * ~~~plug kernel pointer leaks~~~ (done)

Mark LLVM sanitizers as done
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- wikisrc/releng/netbsd9.mdwn	26 Aug 2019 12:59:36 -0000	1.50
+++ wikisrc/releng/netbsd9.mdwn	3 Sep 2019 12:59:22 -0000	1.51
@@ -47,7 +47,7 @@
 * ZFS
 * ~~~kASan for amd64~~~ (done)
 * ~~~kASan for aarch64~~~ (done)
-* compiler-rt in the base with enabled features for Clang/LLVM
+* compiler-rt in the base with enabled features for Clang/LLVM (done)
 * LVM mirror target
 * ~~~add NVMM~~~ (done)
 * ~~~plug kernel pointer leaks~~~ (done)

github.mdwn: get rid of <pre><code> under <th>; try to move the table under the prior <li>, too
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/github.mdwn	3 Sep 2019 03:17:21 -0000	1.9
+++ wikisrc/github.mdwn	3 Sep 2019 03:23:10 -0000	1.10
@@ -13,11 +13,11 @@
 
 * [2017-06: New home for the repository conversion](//mail-index.NetBSD.org/tech-repository/2017/06/10/msg000637.html)
 
-[[!table data="""
-	CVSweb		|	Fossil				|	GitHub
-[[!nbcvsweb src]]	| <https://src.fossil.NetBSD.org/>	| <https://github.com/NetBSD/src>
-[[!nbcvsweb pkgsrc]]	| <https://pkgsrc.fossil.NetBSD.org/>	| <https://github.com/NetBSD/pkgsrc>
-[[!nbcvsweb xsrc]]	| <https://xsrc.fossil.NetBSD.org/>	| <https://github.com/NetBSD/xsrc>
+  [[!table data="""
+CVSweb			|Fossil					|GitHub
+[[!nbcvsweb src]]	|<https://src.fossil.NetBSD.org/>	|<https://github.com/NetBSD/src>
+[[!nbcvsweb pkgsrc]]	|<https://pkgsrc.fossil.NetBSD.org/>	|<https://github.com/NetBSD/pkgsrc>
+[[!nbcvsweb xsrc]]	|<https://xsrc.fossil.NetBSD.org/>	|<https://github.com/NetBSD/xsrc>
 """]]
 
 ---

github.mdwn: we use https://ikiwiki.info/ikiwiki/directive/table/, not https://ikiwiki.iki.fi/wiki/syntax, apparently
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/github.mdwn	3 Sep 2019 03:10:19 -0000	1.8
+++ wikisrc/github.mdwn	3 Sep 2019 03:17:21 -0000	1.9
@@ -13,10 +13,12 @@
 
 * [2017-06: New home for the repository conversion](//mail-index.NetBSD.org/tech-repository/2017/06/10/msg000637.html)
 
-^	CVSweb		^	Fossil				^	GitHub				^
-| [[!nbcvsweb src/]]	| <https://src.fossil.NetBSD.org/>	| <https://github.com/NetBSD/src>	|
-| [[!nbcvsweb pkgsrc/]]	| <https://pkgsrc.fossil.NetBSD.org/>	| <https://github.com/NetBSD/pkgsrc>	|
-| [[!nbcvsweb xsrc/]]	| <https://xsrc.fossil.NetBSD.org/>	| <https://github.com/NetBSD/xsrc>	|
+[[!table data="""
+	CVSweb		|	Fossil				|	GitHub
+[[!nbcvsweb src]]	| <https://src.fossil.NetBSD.org/>	| <https://github.com/NetBSD/src>
+[[!nbcvsweb pkgsrc]]	| <https://pkgsrc.fossil.NetBSD.org/>	| <https://github.com/NetBSD/pkgsrc>
+[[!nbcvsweb xsrc]]	| <https://xsrc.fossil.NetBSD.org/>	| <https://github.com/NetBSD/xsrc>
+"""]]
 
 ---
 

Add a comment