Recent changes to this wiki:

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>
+"""]]
 
 ---
 

github.mdwn: let us try a table, covertly showing off Fossil under the pretence of GitHub
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/github.mdwn	3 Sep 2019 02:23:34 -0000	1.7
+++ wikisrc/github.mdwn	3 Sep 2019 03:10:19 -0000	1.8
@@ -13,11 +13,14 @@
 
 * [2017-06: New home for the repository conversion](//mail-index.NetBSD.org/tech-repository/2017/06/10/msg000637.html)
 
-  * <https://github.com/NetBSD/src>
+^	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>	|
 
-  * <https://github.com/NetBSD/pkgsrc>
+---
 
-  * <https://github.com/NetBSD/xsrc>
+### History and Technical Details
 
 Prior to 2017-06, an earlier generation of the export has been available 
 under `github.com/jsonn` since [2011-07](//mail-index.NetBSD.org/tech-repository/2011/07/28/msg000387.html), 

github.mdwn: add spacing, and pkgsrc forks, too
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/github.mdwn	3 Sep 2019 01:05:55 -0000	1.6
+++ wikisrc/github.mdwn	3 Sep 2019 02:23:34 -0000	1.7
@@ -12,8 +12,11 @@
 have been available under `github.com/NetBSD` since 2017-06:
 
 * [2017-06: New home for the repository conversion](//mail-index.NetBSD.org/tech-repository/2017/06/10/msg000637.html)
+
   * <https://github.com/NetBSD/src>
+
   * <https://github.com/NetBSD/pkgsrc>
+
   * <https://github.com/NetBSD/xsrc>
 
 Prior to 2017-06, an earlier generation of the export has been available 
@@ -49,6 +52,13 @@
 
 ## GitHub Forks
 
+### src
+
 * <https://github.com/NetBSD/src/network/members>
 * <https://github.com/jsonn/src/network/members>
 * <https://github.com/IIJ-NetBSD/netbsd-src/network/members>
+
+### pkgsrc
+
+* <https://github.com/NetBSD/pkgsrc/network/members>
+* <https://github.com/jsonn/pkgsrc/network/members>

gitsofar: wikilink github
Index: wikisrc/gitsofar.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/gitsofar.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/gitsofar.mdwn	2 Sep 2019 19:29:52 -0000	1.9
+++ wikisrc/gitsofar.mdwn	3 Sep 2019 01:16:05 -0000	1.10
@@ -2,6 +2,7 @@
 
 * [[mailing-lists/tech-repository]]
 * [[projects/project/cvs-migration]]
+* [[github]]
 * [2011-10: Fossilizing NetBSD: The road to modern version control](https://2011.eurobsdcon.org/papers/sonnenberger/fossilizing.pdf)
 * [2015-01: Core statement on version control systems](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)
 * [2017-06: New home for the repository conversion](http://mail-index.netbsd.org/tech-repository/2017/06/10/msg000637.html)

mailing-lists/tech-repository: mention [[github]]
Index: wikisrc/mailing-lists/tech-repository.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/mailing-lists/tech-repository.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/mailing-lists/tech-repository.mdwn	19 Dec 2014 12:59:12 -0000	1.17
+++ wikisrc/mailing-lists/tech-repository.mdwn	3 Sep 2019 01:12:38 -0000	1.18
@@ -154,10 +154,12 @@
 ### fossil
 
 We have a successful conversion from cvs to fossil since ~mid 2011, mostly thanks to the work of Jörg Sonnenberger.
+See [[github]] for more details.
 
 ### git
 
 We have a successful conversion to git via the fossil conversion; also, probably now a successful direct conversion via the tools by Eric S. Raymond.
+See [[github]] for more details.
 
 ### hg
 

github.mdwn: mention pkgsrc commit message policy
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/github.mdwn	3 Sep 2019 00:46:25 -0000	1.5
+++ wikisrc/github.mdwn	3 Sep 2019 01:05:55 -0000	1.6
@@ -12,9 +12,9 @@
 have been available under `github.com/NetBSD` since 2017-06:
 
 * [2017-06: New home for the repository conversion](//mail-index.NetBSD.org/tech-repository/2017/06/10/msg000637.html)
-* <https://github.com/NetBSD/src>
-* <https://github.com/NetBSD/pkgsrc>
-* <https://github.com/NetBSD/xsrc>
+  * <https://github.com/NetBSD/src>
+  * <https://github.com/NetBSD/pkgsrc>
+  * <https://github.com/NetBSD/xsrc>
 
 Prior to 2017-06, an earlier generation of the export has been available 
 under `github.com/jsonn` since [2011-07](//mail-index.NetBSD.org/tech-repository/2011/07/28/msg000387.html), 
@@ -31,9 +31,14 @@
 
 The core team has provided a statement on version control systems in 2015:
 
-* [2015-01: Core statement on version control systems](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)
+* [2015-01: Core statement on version control systems](//mail-index.NetBSD.org/tech-repository/2015/01/04/msg000497.html)
 * [[gitsofar]]
 
+The pkgsrc repository has adopted a GitHub-friendly commit message policy in 2017,
+limiting the first line of the message to 65 characters:
+
+* [2017-09: pkgsrc Commit Message Policy](//mail-index.NetBSD.org/pkgsrc-users/2017/09/12/msg025574.html)
+
 ---
 
 ## Unofficial

github.mdwn: provide a copy of cvs2fossil from joerg; ok joerg; also more explicit GitHub links whilst here
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/github.mdwn	3 Sep 2019 00:42:01 -0000	1.4
+++ wikisrc/github.mdwn	3 Sep 2019 00:46:25 -0000	1.5
@@ -12,15 +12,20 @@
 have been available under `github.com/NetBSD` since 2017-06:
 
 * [2017-06: New home for the repository conversion](//mail-index.NetBSD.org/tech-repository/2017/06/10/msg000637.html)
+* <https://github.com/NetBSD/src>
+* <https://github.com/NetBSD/pkgsrc>
+* <https://github.com/NetBSD/xsrc>
 
 Prior to 2017-06, an earlier generation of the export has been available 
 under `github.com/jsonn` since [2011-07](//mail-index.NetBSD.org/tech-repository/2011/07/28/msg000387.html), 
 which has been deprecated and discontinued in 2017-07 with the move to @NetBSD.
 
 The export is maintained by `joerg@` and performed through an intermediate step of
-converting the repositories from CVS into Fossil, which has been the process since 2011:
+converting the repositories from CVS into Fossil with `cvs2fossil`,
+which has been the process since 2011:
 
 * [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>
 * [[mailing-lists/tech-repository]]
 * [[projects/project/cvs-migration]]
 

github.mdwn: give the main github link twice, in case anyone misses it the first time
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/github.mdwn	3 Sep 2019 00:40:23 -0000	1.3
+++ wikisrc/github.mdwn	3 Sep 2019 00:42:01 -0000	1.4
@@ -4,7 +4,9 @@
 
 ## Official
 
-NetBSD developers maintain GitHub presence at <https://GitHub.com/NetBSD>.
+NetBSD developers maintain GitHub presence at <https://GitHub.com/NetBSD>:
+
+* <https://github.com/NetBSD>
 
 The `src`, `xsrc` and `pkgsrc` repositories, each as a read-only copy,
 have been available under `github.com/NetBSD` since 2017-06:

github.mdwn: fix wikilinks
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/github.mdwn	3 Sep 2019 00:39:03 -0000	1.2
+++ wikisrc/github.mdwn	3 Sep 2019 00:40:23 -0000	1.3
@@ -19,13 +19,13 @@
 converting the repositories from CVS into Fossil, which has been the process since 2011:
 
 * [2011-10: EuroBSDcon: Fossilizing NetBSD: The road to modern version control](https://2011.eurobsdcon.org/papers/sonnenberger/fossilizing.pdf)
-* <mailing-lists/tech-repository>
-* <projects/project/cvs-migration>
+* [[mailing-lists/tech-repository]]
+* [[projects/project/cvs-migration]]
 
 The core team has provided a statement on version control systems in 2015:
 
 * [2015-01: Core statement on version control systems](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)
-* <gitsofar>
+* [[gitsofar]]
 
 ---
 

github.mdwn: formatting
Index: wikisrc/github.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/github.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/github.mdwn	3 Sep 2019 00:35:57 -0000	1.1
+++ wikisrc/github.mdwn	3 Sep 2019 00:39:03 -0000	1.2
@@ -7,22 +7,25 @@
 NetBSD developers maintain GitHub presence at <https://GitHub.com/NetBSD>.
 
 The `src`, `xsrc` and `pkgsrc` repositories, each as a read-only copy,
-have been available under <GitHub.com/NetBSD> since 2017-06:
+have been available under `github.com/NetBSD` since 2017-06:
+
 * [2017-06: New home for the repository conversion](//mail-index.NetBSD.org/tech-repository/2017/06/10/msg000637.html)
 
 Prior to 2017-06, an earlier generation of the export has been available 
-under github.com/jsonn since [2011-07](//mail-index.NetBSD.org/tech-repository/2011/07/28/msg000387.html), 
+under `github.com/jsonn` since [2011-07](//mail-index.NetBSD.org/tech-repository/2011/07/28/msg000387.html), 
 which has been deprecated and discontinued in 2017-07 with the move to @NetBSD.
 
 The export is maintained by `joerg@` and performed through an intermediate step of
 converting the repositories from CVS into Fossil, which has been the process since 2011:
+
 * [2011-10: EuroBSDcon: Fossilizing NetBSD: The road to modern version control](https://2011.eurobsdcon.org/papers/sonnenberger/fossilizing.pdf)
-* [[mailing-lists/tech-repository]]
-* [[projects/project/cvs-migration]]
+* <mailing-lists/tech-repository>
+* <projects/project/cvs-migration>
 
 The core team has provided a statement on version control systems in 2015:
+
 * [2015-01: Core statement on version control systems](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)
-* [[gitsofar]]
+* <gitsofar>
 
 ---
 

github.mdwn: initial revision
--- /dev/null	2019-09-03 00:33:30.665270472 +0000
+++ wikisrc/github.mdwn	2019-09-03 00:36:28.367164399 +0000
@@ -0,0 +1,39 @@
+[[!meta title="GitHub"]]
+
+# NetBSD at GitHub
+
+## Official
+
+NetBSD developers maintain GitHub presence at <https://GitHub.com/NetBSD>.
+
+The `src`, `xsrc` and `pkgsrc` repositories, each as a read-only copy,
+have been available under <GitHub.com/NetBSD> since 2017-06:
+* [2017-06: New home for the repository conversion](//mail-index.NetBSD.org/tech-repository/2017/06/10/msg000637.html)
+
+Prior to 2017-06, an earlier generation of the export has been available 
+under github.com/jsonn since [2011-07](//mail-index.NetBSD.org/tech-repository/2011/07/28/msg000387.html), 
+which has been deprecated and discontinued in 2017-07 with the move to @NetBSD.
+
+The export is maintained by `joerg@` and performed through an intermediate step of
+converting the repositories from CVS into Fossil, which has been the process since 2011:
+* [2011-10: EuroBSDcon: Fossilizing NetBSD: The road to modern version control](https://2011.eurobsdcon.org/papers/sonnenberger/fossilizing.pdf)
+* [[mailing-lists/tech-repository]]
+* [[projects/project/cvs-migration]]
+
+The core team has provided a statement on version control systems in 2015:
+* [2015-01: Core statement on version control systems](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)
+* [[gitsofar]]
+
+---
+
+## Unofficial
+
+Additionally, an independent export of the src tree from CVS directly into Git is performed by IIJ at <https://GitHub.com/IIJ-NetBSD/netbsd-src>.
+
+---
+
+## GitHub Forks
+
+* <https://github.com/NetBSD/src/network/members>
+* <https://github.com/jsonn/src/network/members>
+* <https://github.com/IIJ-NetBSD/netbsd-src/network/members>

wasabisystems.com has been dropped many times now, replace with web.archive.org
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -r1.80 -r1.81
--- wikisrc/events.mdwn	2 Sep 2019 21:23:49 -0000	1.80
+++ wikisrc/events.mdwn	2 Sep 2019 22:17:05 -0000	1.81
@@ -4599,7 +4599,7 @@
 <http://www.linuxworldexpo.com/>
 
 The NetBSD Project shared a stand with [Wasabi
-Systems](http://www.wasabisystems.com/) at LinuxWorld Expo 2001. The
+Systems](http://web.archive.org/web/2002/http://www.wasabisystems.com/) at LinuxWorld Expo 2001. The
 stand had a variety of different platforms running NetBSD, 1.5 CDs, and
 other swag.
 
@@ -4793,7 +4793,7 @@
 There was also a BSD BoF which included people kicking around beach
 balls emblazoned with "NetBSD support: it's not hot air anymore" in
 reference to the launch of [Wasabi
-Systems](http://www.wasabisystems.com/).
+Systems](http://web.archive.org/web/2002/http://www.wasabisystems.com/).
 
 Expenses for this event were underwritten by The Usenix Association and
 The NetBSD Mission.
Index: wikisrc/ports/amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amd64.mdwn,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- wikisrc/ports/amd64.mdwn	2 Jun 2019 13:32:38 -0000	1.27
+++ wikisrc/ports/amd64.mdwn	2 Sep 2019 22:17:05 -0000	1.28
@@ -19,7 +19,7 @@
 on June 19th, 2001 and renamed to NetBSD/amd64 on April 26th, 2003.
 
 The original work to do this port was done by Frank van der Linden at
-<a class="ulink" href="http://www.wasabisystems.com/" target="_top">Wasabi Systems</a>, assisted by
+<a class="ulink" href="http://web.archive.org/web/2002/http://www.wasabisystems.com/" target="_top">Wasabi Systems</a>, assisted by
 <a class="ulink" href="http://www.amd.com/" target="_top">AMD</a>, who provided the simulator
 (Simics VirtuHammer), pre-release hardware and access to a range
 of Opteron hardware through the

kerberos/web_browser: the {href='about:config'} part gets removed anyways, so, let's just omit it
Index: wikisrc/kerberos/web_browser.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/kerberos/web_browser.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/kerberos/web_browser.mdwn	2 Sep 2019 21:35:05 -0000	1.13
+++ wikisrc/kerberos/web_browser.mdwn	2 Sep 2019 21:37:56 -0000	1.14
@@ -3,7 +3,7 @@
 ## Firefox
 
 7. Open Firefox.
-7. Go to <a href='about:config'><tt>about:config</tt></a>.
+7. Go to <a><tt>about:config</tt></a>.
 7. Filter for `network.negotiate-auth`.
 7. Set `network.negotiate-auth.trusted-uris` (_not_
 `network.negotiate-auth.delegation-uris`) to `netbsd.org`.

kerberos/web_browser: let us try HTML, as [[about:config]] results in just ?about:config
Index: wikisrc/kerberos/web_browser.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/kerberos/web_browser.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/kerberos/web_browser.mdwn	2 Sep 2019 21:32:34 -0000	1.12
+++ wikisrc/kerberos/web_browser.mdwn	2 Sep 2019 21:35:05 -0000	1.13
@@ -3,7 +3,7 @@
 ## Firefox
 
 7. Open Firefox.
-7. Go to [[about:config]].
+7. Go to <a href='about:config'><tt>about:config</tt></a>.
 7. Filter for `network.negotiate-auth`.
 7. Set `network.negotiate-auth.trusted-uris` (_not_
 `network.negotiate-auth.delegation-uris`) to `netbsd.org`.

kerberos/web_browser: let us try [[about:config]] in place of <about:config> (originally, [about:config](about:config) resulted in <a>about:config</a>, now it renders as <about:config>)
Index: wikisrc/kerberos/web_browser.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/kerberos/web_browser.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/kerberos/web_browser.mdwn	2 Sep 2019 21:28:13 -0000	1.11
+++ wikisrc/kerberos/web_browser.mdwn	2 Sep 2019 21:32:34 -0000	1.12
@@ -3,7 +3,7 @@
 ## Firefox
 
 7. Open Firefox.
-7. Go to <about:config>.
+7. Go to [[about:config]].
 7. Filter for `network.negotiate-auth`.
 7. Set `network.negotiate-auth.trusted-uris` (_not_
 `network.negotiate-auth.delegation-uris`) to `netbsd.org`.

final remnant of the [x](x) paradigm {s#\[([^]]*)]\(\1\)#<\1>#g}
Index: wikisrc/kerberos/web_browser.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/kerberos/web_browser.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/kerberos/web_browser.mdwn	16 Feb 2013 13:42:32 -0000	1.10
+++ wikisrc/kerberos/web_browser.mdwn	2 Sep 2019 21:28:13 -0000	1.11
@@ -3,7 +3,7 @@
 ## Firefox
 
 7. Open Firefox.
-7. Go to [about:config](about:config).
+7. Go to <about:config>.
 7. Filter for `network.negotiate-auth`.
 7. Set `network.negotiate-auth.trusted-uris` (_not_
 `network.negotiate-auth.delegation-uris`) to `netbsd.org`.

events.mdwn: fix random usenix2001 link
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- wikisrc/events.mdwn	2 Sep 2019 20:48:36 -0000	1.79
+++ wikisrc/events.mdwn	2 Sep 2019 21:23:49 -0000	1.80
@@ -4516,8 +4516,7 @@
 Luke Mewburn. A list of highlights is available in Chuck Toporek's
 "[Greetings from the BSD Super
 BoF](http://unix.oreilly.com/news/usenixchuck_0601.html)" article. The
-slides from this talk are available at
-[events/usenix2001/](events/usenix2001/).
+[slides from this talk](//www.netbsd.org/gallery/events/usenix2001/) are available.
 
 Luke Mewburn was also a part of the scripting technical session; his
 presentation was entitled, "The Design and Implementation of the NetBSD

replace [ftp...](ftp...) with <ftp...> (w/ 's#\[(ftp[^]]*)]\(\1\)#<\1>#g', of course)
Index: wikisrc/pkgsrc/how_to_upgrade_packages.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/how_to_upgrade_packages.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/pkgsrc/how_to_upgrade_packages.mdwn	2 Sep 2019 20:48:37 -0000	1.5
+++ wikisrc/pkgsrc/how_to_upgrade_packages.mdwn	2 Sep 2019 21:15:38 -0000	1.6
@@ -33,7 +33,7 @@
 
 ## pkg_chk -b
 
-Use "-b -P URL" where URL is where the binary packages are (e.g. [ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/5.1/All/](ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/5.1/All/)).
+Use "-b -P URL" where URL is where the binary packages are (e.g. <ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/5.1/All/>).
 
 For example, to update any missing packages by using binary packages:
 

find wikisrc -name '*.mdwn' | xargs perl -pi'' -e's#\[(http[^]]*)]\(\1\)#<\1>#g'
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -r1.78 -r1.79
--- wikisrc/events.mdwn	19 Jul 2019 12:22:44 -0000	1.78
+++ wikisrc/events.mdwn	2 Sep 2019 20:48:36 -0000	1.79
@@ -3117,7 +3117,7 @@
 
 The event takes place on September 9th and 10th 2006 at the Glaspavillon
 of the University of Duisburg-Essen. See
-[http://www.come2linux.org/](http://www.come2linux.org/) for more
+<http://www.come2linux.org/> for more
 information.
 
 A report on the event was [posted to the regional-de mailing
@@ -3128,7 +3128,7 @@
 There will be a NetBSD booth at the Linux-Kongress in Nuremberg on
 September 7th and 8th at the University of Applied Sciences
 (Fachhochschule) Nuernberg. See
-[http://www.linux-kongress.org/](http://www.linux-kongress.org/) for
+<http://www.linux-kongress.org/> for
 more information on the event, and contact Hubert Feyrer
 <hubertf@NetBSD.org> if you have any questions or want to help out at
 the booth.
@@ -3220,7 +3220,7 @@
 
 For more information, including how to register, and how to submit a
 presentation proposal, please visit
-[http://www.pkgsrcCon.org/](http://www.pkgsrcCon.org/).
+<http://www.pkgsrcCon.org/>.
 
 ### `May 2006` - LinuxTag 2006
 
@@ -3531,7 +3531,7 @@
 *July 23, 2005, [NADYA
 Park](http://www.u-net.city.nagoya.jp/t-index/nadia.htm) Nagoya, Japan*
 
-[http://www.bsdcon.jp/](http://www.bsdcon.jp/) with 80 attendances.
+<http://www.bsdcon.jp/> with 80 attendances.
 There had be a BSD booth staffed by members of the [Nagoya \*BSD Users'
 Group](http://www.nagoya.bug.gr.jp/). See more
 [Reports](http://pcweb.mycom.co.jp/articles/2005/07/27/bsdcon/).
@@ -3612,7 +3612,7 @@
 Around 1000 people attended the past two years.
 
 More information is at
-[http://linuxnorthwest.org/](http://linuxnorthwest.org/). (If you can
+<http://linuxnorthwest.org/>. (If you can
 volunteer to help with NetBSD advocacy at LinuxFest, please see [this
 email](http://mail-index.NetBSD.org/netbsd-advocacy/2005/03/25/0000.html).)
 
@@ -3857,7 +3857,7 @@
 Packages Collection (pkgsrc), focusing on existing technologies,
 research projects, and works-in-progress in pkgsrc infrastructure. For
 more information, including slides of the talks, please visit
-[http://www.pkgsrcCon.org/2004/](http://www.pkgsrcCon.org/2004/), and
+<http://www.pkgsrcCon.org/2004/>, and
 see Hubert Feyrer's report in the [DaemonNews
 Ezine](http://ezine.daemonnews.org/200405/pkgsrcCon2004.html).
 
@@ -3870,7 +3870,7 @@
 throughout the day. Among them will be introductions to BSD and pkgsrc.
 There will be a BSD booth, occupied by two NetBSD developers and other
 BSD enthusiasts. Admission is free. Please see
-[http://www.linuxnorthwest.org/](http://www.linuxnorthwest.org/) and
+<http://www.linuxnorthwest.org/> and
 [this message to the netbsd-news
 mailinglist](http://mail-index.NetBSD.org/netbsd-news/2004/04/16/0000.html)
 for more information.
@@ -3949,14 +3949,14 @@
 *December 6 and 7, 2003, Instituto Militar de Engenharia (military
 institute of engineering - IME), Rio de Janeiro, Brasil*
 
-See [http://bsdcon.myfreebsd.com.br](http://bsdcon.myfreebsd.com.br) for
+See <http://bsdcon.myfreebsd.com.br> for
 details.
 
 ### `Dec 2003` - BSD-Linux-Day 2003
 
 *December 2, 2003, Pacifico Yokohama, Japan*
 
-[http://www.jus.or.jp/events/bsd-linux-day/](http://www.jus.or.jp/events/bsd-linux-day/)
+<http://www.jus.or.jp/events/bsd-linux-day/>
 
 ### `Nov 2003` - NetBSD System Administration training
 
@@ -3965,7 +3965,7 @@
 [Puget Sound Technology](http://www.pugetsoundtechnology.com/) is
 teaching a hands-on class covering the fundamentals of NetBSD system
 administration. See
-[http://www.pugetsoundtechnology.com/training/netbsd/](http://www.pugetsoundtechnology.com/training/netbsd/)
+<http://www.pugetsoundtechnology.com/training/netbsd/>
 for details.
 
 ### `Oct 2003` - KANSAI-OPENSOURCE+FREEWARE-2003
@@ -3998,7 +3998,7 @@
 
 Meet the movers and shakers of the BSD community, and learn how you can
 use BSD as part of your enterprise-grade solutions. For details, see
-[http://www.usenix.org/events/bsdcon03/cfp/](http://www.usenix.org/events/bsdcon03/cfp/).
+<http://www.usenix.org/events/bsdcon03/cfp/>.
 Contact name, address, phone, fax and/or e-mail: Conference Department,
 510-528-8649, conference@usenix.org. A
 [report](http://mail-index.NetBSD.org/netbsd-advocacy/2003/09/13/0000.html)
@@ -4028,7 +4028,7 @@
 ### `Jul 2003` - Libre Software Meeting in Metz
 
 *July 9-12, 2003, Metz, France*
-[http://www.rencontresmondiales.org/](http://www.rencontresmondiales.org/)
+<http://www.rencontresmondiales.org/>
 
 The NetBSD Project was represented at the LSM 2003 by Emmanuel Dreyfus
 and Gilbert Fernandes. A
@@ -4039,7 +4039,7 @@
 
 *July 2, 2003, Makuhari-Messe, Chiba, Japan, 18:30-20:00 JST*
 
-[http://www.interop.jp/](http://www.interop.jp/)
+<http://www.interop.jp/>
 
 Call for Presentation: contact Jun Ebihara <jun@NetBSD.org>.
 
@@ -4052,7 +4052,7 @@
 
 *June 7-8, 2003, Nagoya, Japan*
 
-[http://tokai.opensource.jp/tsudoi/2003/](http://tokai.opensource.jp/tsudoi/2003/)
+<http://tokai.opensource.jp/tsudoi/2003/>
 
 ### `Jun 2003` - 2003 USENIX Annual Technical Conference
 
@@ -4063,7 +4063,7 @@
 Birds-of-a-Feather sessions. There will be a [Super BSD BOF
 Session](http://www.usenix.org/events/usenix03/bofs.html). For details,
 see
-[http://www.usenix.org/events/usenix03/](http://www.usenix.org/events/usenix03/).
+<http://www.usenix.org/events/usenix03/>.
 Contact name, address, phone, fax and/or e-mail: Conference Department,
 510-528-8649, conference@usenix.org
 
@@ -4105,7 +4105,7 @@
 
 There was a NetBSD booth and presentation at the Magdeburg Linuxtag in
 Magdeburg, Germany on April 5th 2003 at the University of Magdeburg,
-Germany. See [http://www.mdlug.de/](http://www.mdlug.de/) for more
+Germany. See <http://www.mdlug.de/> for more
 information. Contact Bernd Sieker <bsieker@freenet.de> for information
 regarding representation of NetBSD at the event.
 
@@ -4133,7 +4133,7 @@
 [Puget Sound Technology](http://www.pugetsoundtechnology.com/) is
 teaching a hands-on class covering the fundamentals of NetBSD system
 administration. See
-[http://www.pugetsoundtechnology.com/training/netbsd/](http://www.pugetsoundtechnology.com/training/netbsd/)
+<http://www.pugetsoundtechnology.com/training/netbsd/>
 for details.
 
 ### `Mar 2003` - Chemnitzer Linux-Tag
@@ -4143,7 +4143,7 @@
 NetBSD was represented with a booth at the [Chemnitzer Linux-Tag
 (CLT5)](http://www.tu-chemnitz.de/linux/tag/lt5/). A summary of the
 events including several pictures is available online at
-[http://www.feyrer.de/NetBSD/clt5.html](http://www.feyrer.de/NetBSD/clt5.html).
+<http://www.feyrer.de/NetBSD/clt5.html>.
 Presentations, including mp3s of the talks (in German!) are available
 from:
 
@@ -4185,7 +4185,7 @@
 -   Linuxfest at Carleton University (Sat. Jan. 25th)
 -   The Business of Open Source Software conference. (Sun. Jan. 26th)
 
-For details, please see [http://www.osw.ca/](http://www.osw.ca/).
+For details, please see <http://www.osw.ca/>.
 
 ### `Jan 2003` - LinuxWorld 2003
 
@@ -4225,7 +4225,7 @@
 BSD BoF on December 18th, 18:00(JST) at this years Internet Week. The
 BoF was broadcasted via RealVideo (179 clients)/[xcast (3
 clients)](http://www.xcast.jp/)/IRC. See
-[http://www.nic.ad.jp/iw2002/bof/bof04.htm](http://www.nic.ad.jp/iw2002/bof/bof04.htm)
+<http://www.nic.ad.jp/iw2002/bof/bof04.htm>
 for details.
 
 ### `Nov 2002` - KNF Congress 2002
@@ -4243,7 +4243,7 @@
 The congress will take place Sunday Nov 24th, 10-18h at the
 Gemeinschaftshaus Langwasser, Glogauer Str. 50, 90473 Nuremberg,
 Germany. See
-[http://www.franken.de/kongress/index.html](http://www.franken.de/kongress/index.html)
+<http://www.franken.de/kongress/index.html>
 for more information.
 
 ### `Nov 2002` - BSD Conference Japan
@@ -4256,7 +4256,7 @@
 
 *November 15-17, 2002, Amsterdam, Netherlands*
 

(Diff truncated)
gitsofar: add two wiki-links and a EuroBSDcon 2011 paper (to have everything in same place)
Index: wikisrc/gitsofar.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/gitsofar.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/gitsofar.mdwn	2 Sep 2019 05:44:21 -0000	1.8
+++ wikisrc/gitsofar.mdwn	2 Sep 2019 19:29:52 -0000	1.9
@@ -1,5 +1,8 @@
 ## NetBSD with git so far
 
+* [[mailing-lists/tech-repository]]
+* [[projects/project/cvs-migration]]
+* [2011-10: Fossilizing NetBSD: The road to modern version control](https://2011.eurobsdcon.org/papers/sonnenberger/fossilizing.pdf)
 * [2015-01: Core statement on version control systems](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)
 * [2017-06: New home for the repository conversion](http://mail-index.netbsd.org/tech-repository/2017/06/10/msg000637.html)
 * [2017-09: pkgsrc Commit Message Policy](http://mail-index.netbsd.org/pkgsrc-users/2017/09/12/msg025574.html)

gitsofar: add a few links from 2017 and 2019 on the most recent status
Index: wikisrc/gitsofar.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/gitsofar.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/gitsofar.mdwn	22 Sep 2017 10:37:52 -0000	1.7
+++ wikisrc/gitsofar.mdwn	2 Sep 2019 05:44:21 -0000	1.8
@@ -1,6 +1,9 @@
 ## NetBSD with git so far
 
-[core statement on vcs](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)
+* [2015-01: Core statement on version control systems](http://mail-index.netbsd.org/tech-repository/2015/01/04/msg000497.html)
+* [2017-06: New home for the repository conversion](http://mail-index.netbsd.org/tech-repository/2017/06/10/msg000637.html)
+* [2017-09: pkgsrc Commit Message Policy](http://mail-index.netbsd.org/pkgsrc-users/2017/09/12/msg025574.html)
+* [GitHub.com/NetBSD](https://github.com/NetBSD)
 
 ### Low memory hosts:
 
@@ -59,6 +62,8 @@
 [dfbsd workflows](http://lists.dragonflybsd.org/pipermail/users/2015-January/207422.html)<br>
 [dfbsd config](http://lists.dragonflybsd.org/pipermail/users/2015-January/207424.html)<br>
 
+[In 2019, FreeBSD core team has appointed a WG to explore transition from Subversion to Git.](https://www.freebsd.org/news/status/report-2019-04-2019-06.html#FreeBSD-Core-Team)
+
 ### how to install
 
 git should fit into NetBSD src/tools easily.  I have not personally tested

subregs of mem isn't the problem. this is erroring out in recog, when it
tries to match patterns against VAX-specific machine description code.
Comment out the stuff about instruction scheduling.
Members: 
	users/maya/vax-gcc.mdwn:1.10->1.11 

Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/users/maya/vax-gcc.mdwn	30 Aug 2019 05:07:15 -0000	1.10
+++ wikisrc/users/maya/vax-gcc.mdwn	31 Aug 2019 13:17:56 -0000	1.11
@@ -66,8 +66,11 @@
     during RTL pass: vregs
     /home/fly/oacc/decl.ii:17:1: internal compiler error: in extract_insn, at recog.c:2310
     
-Providing a trivial scheduling will avoid subregs of mem.  
-However, this doesn't work for us. Our crash and mem subregs happen at a too early pass, most likely.
+
+This is in VAX-specific code. We need to figure out what instruction pattern this is, that we're missing.
+
+<!--Providing a trivial scheduling will avoid subregs of mem.  
+However, this doesn't work for us. Our crash and mem subregs happen at a too early pass, most likely.-->
 
 ## DWARF ##
 

Sync with recent htdocs/share/xsl/{errorpage,webpage}.xsl changes:
- Remove duplicate Community -> Blog anchor, already present under
News & Media -> NetBSD blog.
- Rename About -> Advocacy anchor to About -> Gallery to better reflect
current reality and page name.
Both noticed by <maxv>, thanks!
Both noticed by <maxv>, thanks!

Members: 
	templates/page.tmpl:1.54->1.55 

Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- wikisrc/templates/page.tmpl	1 Jan 2019 05:16:09 -0000	1.54
+++ wikisrc/templates/page.tmpl	30 Aug 2019 18:19:30 -0000	1.55
@@ -70,7 +70,7 @@
 	<li><a href="//www.NetBSD.org/people/developers.html">
 		    NetBSD developers</a></li>
 	<li><a href="//www.NetBSD.org/gallery/">
-		    Advocacy</a></li>
+		    Gallery</a></li>
 	</ul>
 	</li>
 	<li>
@@ -102,8 +102,6 @@
 	<li>
 	<a href="//www.NetBSD.org/community/">
 		  Community</a><ul>
-	<li><a href="//blog.NetBSD.org/">
-		    Blog</a></li>
 	<li><a href="//www.NetBSD.org/mailinglists/">
 		    Mailing lists</a></li>
 	<li><a href="//mail-index.NetBSD.org/">

Moar notes
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/users/maya/vax-gcc.mdwn	30 Aug 2019 04:49:49 -0000	1.9
+++ wikisrc/users/maya/vax-gcc.mdwn	30 Aug 2019 05:07:15 -0000	1.10
@@ -81,6 +81,8 @@
     ld: .eh_frame_hdr refers to overlapping FDEs
     ld: final link failed: bad value
 
+[riscv seemed to share the issue](https://github.com/riscv/riscv-binutils-gdb/issues/76) and had fixed it.
+
 ## review comments ##
 
 Jeff Law [provided some feedback](https://gcc.gnu.org/ml/gcc/2019-04/msg00281.html). More of it should be addressed.

Moar notes.
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/users/maya/vax-gcc.mdwn	30 Aug 2019 02:09:23 -0000	1.8
+++ wikisrc/users/maya/vax-gcc.mdwn	30 Aug 2019 04:49:49 -0000	1.9
@@ -68,3 +68,19 @@
     
 Providing a trivial scheduling will avoid subregs of mem.  
 However, this doesn't work for us. Our crash and mem subregs happen at a too early pass, most likely.
+
+## DWARF ##
+
+    flag_dwarf2_cfi_asm = 0;
+
+is kind of a big deal. We should probably get rid of it, but [binutils hates that.](https://github.com/NetBSD/src/commit/1df57dce3744cf4743358b098728a0658b80b8fb)
+
+    ld: warning: dynamic relocation to `?' in readonly section `.eh_frame'
+    ld: warning: dynamic relocation to `?' in readonly section `.eh_frame'
+    ld: warning: creating a DT_TEXTREL in a shared object
+    ld: .eh_frame_hdr refers to overlapping FDEs
+    ld: final link failed: bad value
+
+## review comments ##
+
+Jeff Law [provided some feedback](https://gcc.gnu.org/ml/gcc/2019-04/msg00281.html). More of it should be addressed.

Link to my tree, provide more info about how the suggested workaround
doesn't work.
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 21:57:38 -0000	1.7
+++ wikisrc/users/maya/vax-gcc.mdwn	30 Aug 2019 02:09:23 -0000	1.8
@@ -1,5 +1,7 @@
 # Various GCC/vax issues and invesigation #
 
+[WIP tree](gcc-mirror/)
+
 ## libgomp crash with -O2 ##
 Repro:
 
@@ -64,4 +66,5 @@
     during RTL pass: vregs
     /home/fly/oacc/decl.ii:17:1: internal compiler error: in extract_insn, at recog.c:2310
     
-Providing a trivial scheduling will avoid subregs of mem.
+Providing a trivial scheduling will avoid subregs of mem.  
+However, this doesn't work for us. Our crash and mem subregs happen at a too early pass, most likely.

Expand with the failure and information from segher.
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 21:19:09 -0000	1.6
+++ wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 21:57:38 -0000	1.7
@@ -49,3 +49,19 @@
     EOF
     vax--netbsdelf-g++ -O2 -c decl.ii
 
+This errors out with:
+
+    $ env PATH=$PWD:$PATH ./xgcc -fno-use-linker-plugin -c -O2 ~/oacc/decl.ii -fno-tree-vectorize
+    /home/fly/oacc/decl.ii: In function 'bool i()':
+    /home/fly/oacc/decl.ii:17:1: error: unrecognizable insn:
+       17 | }
+          | ^
+    (insn 13 12 14 2 (set (reg:SI 33)
+            (subreg:SI (mem:DI (plus:SI (mult:SI (reg/v:SI 24 [ g ])
+                            (const_int 8 [0x8]))
+                        (reg/f:SI 23 [ _6 ])) [1 *_10+0 S8 A32]) 4)) "/home/fly/oacc/decl.ii":16:14 -1
+         (nil))
+    during RTL pass: vregs
+    /home/fly/oacc/decl.ii:17:1: internal compiler error: in extract_insn, at recog.c:2310
+    
+Providing a trivial scheduling will avoid subregs of mem.

correct url
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 20:40:51 -0000	1.5
+++ wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 21:19:09 -0000	1.6
@@ -18,7 +18,7 @@
 
 Asserts at emit-rtl.c:2310 gcc_assert (memory_address_addr_space_p (mode, addr, as));
 
-NetBSD avoids it with a [local diff](5f534f20bc66738c05c442a8f20088f55335b653/external/gpl3/gcc/dist/libgcc/gthr-posix.h#L418) to reload.c/dse.c.  
+NetBSD avoids it with a [local diff](https://github.com/NetBSD/src/commit/e437e96750193b86d0464965661f616e011056fa) to reload.c/dse.c.  
 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.
 

More markdown
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 20:39:43 -0000	1.4
+++ wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 20:40:51 -0000	1.5
@@ -26,7 +26,7 @@
 
 Repro:
 
-#!/bin/sh
+    #!/bin/sh
 
     cat << EOF > decl.ii
     struct a {

add another creduced crash, so I won't have to look from scratch
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 13:01:34 -0000	1.3
+++ wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 20:39:43 -0000	1.4
@@ -1,6 +1,6 @@
 # Various GCC/vax issues and invesigation #
 
-# libgomp crash with -O2 #
+## libgomp crash with -O2 ##
 Repro:
 
     #!/bin/sh
@@ -21,3 +21,31 @@
 NetBSD avoids it with a [local diff](5f534f20bc66738c05c442a8f20088f55335b653/external/gpl3/gcc/dist/libgcc/gthr-posix.h#L418) to reload.c/dse.c.  
 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.
+
+## unrecognizable insn with any optimization ##
+
+Repro:
+
+#!/bin/sh
+
+    cat << EOF > decl.ii
+    struct a {
+      long long *b() const;
+    };
+    template <typename> class d : a {
+    public:
+      template <typename e> d(e);
+      long long f() const;
+    };
+    template <typename c> long long d<c>::f() const {
+      int g;
+      return b()[g];
+    }
+    int h;
+    bool i() {
+      d<int> j(h);
+      return j.f();
+    }
+    EOF
+    vax--netbsdelf-g++ -O2 -c decl.ii
+

more info, more markdown
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 12:46:29 -0000	1.2
+++ wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 13:01:34 -0000	1.3
@@ -18,8 +18,6 @@
 
 Asserts at emit-rtl.c:2310 gcc_assert (memory_address_addr_space_p (mode, addr, as));
 
-NetBSD avoids it with a local diff to reload.c/dse.c.
-
-It looks like a real bug in vax_legitimate_address_p not handling some addressing modes.
-
+NetBSD avoids it with a [local diff](5f534f20bc66738c05c442a8f20088f55335b653/external/gpl3/gcc/dist/libgcc/gthr-posix.h#L418) to reload.c/dse.c.  
+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.

More info on some crash, more attempts to markdown
Index: wikisrc/users/maya/vax-gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya/vax-gcc.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 12:43:34 -0000	1.1
+++ wikisrc/users/maya/vax-gcc.mdwn	29 Aug 2019 12:46:29 -0000	1.2
@@ -2,22 +2,24 @@
 
 # libgomp crash with -O2 #
 Repro:
-````
-#!/bin/sh
 
-cat << EOF > oacc.i
-int a, b;
-int e() {
-  short *c = 0;
-  char d = c[a + 1];
-  b = d;
-  a += 2;
-}
-EOF
-vax--netbsdelf-gcc -O2 -c oacc.i
-````
+    #!/bin/sh
+    
+    cat << EOF > oacc.i
+    int a, b;
+    int e() {
+      short *c = 0;
+      char d = c[a + 1];
+      b = d;
+      a += 2;
+    }
+    EOF
+    vax--netbsdelf-gcc -O2 -c oacc.i
+
 Asserts at emit-rtl.c:2310 gcc_assert (memory_address_addr_space_p (mode, addr, as));
 
 NetBSD avoids it with a local diff to reload.c/dse.c.
 
-It looks like a real bug in vax_legitimate_address_p not handling some addressing modes
+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.

Add some local notes, to be expanded...
--- /dev/null	2019-08-29 12:40:02.614430650 +0000
+++ wikisrc/users/maya/vax-gcc.mdwn	2019-08-29 12:44:24.838207216 +0000
@@ -0,0 +1,23 @@
+# Various GCC/vax issues and invesigation #
+
+# libgomp crash with -O2 #
+Repro:
+````
+#!/bin/sh
+
+cat << EOF > oacc.i
+int a, b;
+int e() {
+  short *c = 0;
+  char d = c[a + 1];
+  b = d;
+  a += 2;
+}
+EOF
+vax--netbsdelf-gcc -O2 -c oacc.i
+````
+Asserts at emit-rtl.c:2310 gcc_assert (memory_address_addr_space_p (mode, addr, as));
+
+NetBSD avoids it with a local diff to reload.c/dse.c.
+
+It looks like a real bug in vax_legitimate_address_p not handling some addressing modes

add another regression; redefine "show stopper" - those bugs did not stop the show
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- wikisrc/releng/netbsd9.mdwn	20 Aug 2019 14:12:14 -0000	1.49
+++ wikisrc/releng/netbsd9.mdwn	26 Aug 2019 12:59:36 -0000	1.50
@@ -20,12 +20,12 @@
 * [[!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
 
 
 ## Bug Bountys
 
-PRs in the above list marked with /!\ are show stoppers and have a bug bounty of $100 attached.
+PRs in the above list marked with /!\ are likely hard and critical, and have a bug bounty of $100 attached.
 If you find a solution for one of the marked issues that leads to closing of the PRs, we will get
 in touch with you.
 

Mark as finished by myself (Kamil Rytarowski)
Index: wikisrc/projects/project/safestack.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/safestack.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/safestack.mdwn	27 Jan 2018 16:42:44 -0000	1.4
+++ wikisrc/projects/project/safestack.mdwn	23 Aug 2019 06:45:03 -0000	1.5
@@ -13,6 +13,7 @@
 category="analyzers"
 difficulty="easy"
 duration="3 months"
+done_by="Kamil Rytarowski"
 
 description="""
 

Update with regressions since -8 (from gson)
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- wikisrc/releng/netbsd9.mdwn	31 Jul 2019 06:49:51 -0000	1.48
+++ wikisrc/releng/netbsd9.mdwn	20 Aug 2019 14:12:14 -0000	1.49
@@ -6,19 +6,23 @@
 
 * ~~[[!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=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=53291]]: GPT prevents installation
 
+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=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
+
+
+
 ## Bug Bountys
 
 PRs in the above list marked with /!\ are show stoppers and have a bug bounty of $100 attached.

Add a project "saslc implementation for openldap client"
Suggested by christos. Some fields are filled out by the project I copied,
and might have to be changed.
Members: 
	projects/project/saslc_openldap.mdwn:INITIAL->1.1 

--- /dev/null	2019-08-11 13:48:00.138302960 +0000
+++ wikisrc/projects/project/saslc_openldap.mdwn	2019-08-11 13:49:00.577017572 +0000
@@ -0,0 +1,30 @@
+[[!template id=project
+
+title="SASL-C implementation for the OpenLDAP client"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Christos Zoulas](mailto:christos@NetBSD.org)
+"""
+
+category="userland"
+difficulty="medium"
+duration="3 months"
+
+description="""
+OpenLDAP already has a SASL back-end for CYRUS-SASL.  
+In NetBSD, we have our own SASL-C library which has similar functionality and can be used in OpenLDAP instead of CYRUS.  
+Base postfix already does this.
+
+There is a cyrus.c file where all the work is done.  
+We can make a saslc.c one that uses our library.  
+This will allow different authentication schemes to be used for the client programs (so we will be able to run ldapsearch against an Active Directory server using GSSAPI.
+
+"""
+
+]]
+
+[[!tag gsoc]]

userlevel -> userland.
The latter exists as a category.
Members: 
	projects/project/static-analyzers.mdwn:1.3->1.4 

Index: wikisrc/projects/project/static-analyzers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/static-analyzers.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/static-analyzers.mdwn	15 Feb 2018 00:35:06 -0000	1.3
+++ wikisrc/projects/project/static-analyzers.mdwn	11 Aug 2019 13:41:28 -0000	1.4
@@ -10,7 +10,7 @@
 [Christos Zoulas](mailto:christos@NetBSD.org)
 """
 
-category="userlevel"
+category="userland"
 difficulty="medium"
 duration="2-3 months"
 

Update title to better specify it's a Xen project.
Index: wikisrc/projects/project/xen-drmkms.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/xen-drmkms.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/xen-drmkms.mdwn	19 Aug 2015 00:12:08 -0000	1.1
+++ wikisrc/projects/project/xen-drmkms.mdwn	11 Aug 2019 13:35:19 -0000	1.2
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="DRMKMS support (gui support on dom0)"
+title="Xen DRMKMS support (GUI support on dom0)"
 
 contact="""
 [port-xen](mailto:port-xen@NetBSD.org)

Remove drmkms project.
It's not "done" in the sense that it will never be done. But we do have
the result, and keep need to work on it.
Members: 
	projects/project/kms-gem.mdwn:1.3->1.4(DEAD) 

--- wikisrc/projects/project/kms-gem.mdwn	2019-08-11 13:32:01.520547107 +0000
+++ /dev/null	2019-08-11 13:32:00.086456787 +0000
@@ -1,27 +0,0 @@
-[[!template id=project
-
-title="Kernel Mode Setting and Graphics Execution Manager"
-
-contact="""
-[tech-kern](mailto:tech-kern@NetBSD.org),
-[tech-x11](mailto:tech-x11@NetBSD.org)
-"""
-
-category="misc"
-difficulty="hard"
-
-description="""
-Recent overhaul of the X server infrastructure lead to the appearance of Kernel
-Mode Setting (KMS) and Graphics Execution Manager (GEM) to rejuvenate the X
-world. This has a number of benefits, from improving 3D GPU support,
-deprivileged X server to in-kernel video mode management, which can be very
-helpful when it is necessary to debug a live system using ddb(4).
-
-The goal of this project is to add the missing bits inside NetBSD, most notably
-KMS and GEM. Testing the port using a recent driver like nouveau would be worth
-the effort.
-
-Work on this is underway on the riastradh-drm2 branch.
-
-"""
-]]

Third time's the charm: mark this project done
Index: wikisrc/projects/project/wine_amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/wine_amd64.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/projects/project/wine_amd64.mdwn	11 Aug 2019 13:23:48 -0000	1.7
+++ wikisrc/projects/project/wine_amd64.mdwn	11 Aug 2019 13:28:47 -0000	1.8
@@ -10,7 +10,7 @@
 
 category="userland"
 difficulty="easy"
-done_by"Naveen Narayanan (GSoC 2019)"
+done_by="Naveen Narayanan (GSoC 2019)"
 
 description="""
 The Wine program is made of two components, Wine32 and Wine64, that respectively

Try to mark it done again (?)
Index: wikisrc/projects/project/wine_amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/wine_amd64.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/project/wine_amd64.mdwn	11 Aug 2019 13:20:11 -0000	1.6
+++ wikisrc/projects/project/wine_amd64.mdwn	11 Aug 2019 13:23:48 -0000	1.7
@@ -7,14 +7,10 @@
 [tech-kern](mailto:tech-kern@NetBSD.org)
 """
 
-mentors="""
-[Maxime Villard](mailto:maxv@NetBSD.org)
-[Maya Rashish](mailto:maya@NetBSD.org)
-"""
 
 category="userland"
 difficulty="easy"
-done_by"Naveen Narayanan"
+done_by"Naveen Narayanan (GSoC 2019)"
 
 description="""
 The Wine program is made of two components, Wine32 and Wine64, that respectively

Mark wine project as done by Naveen Narayanan.
Index: wikisrc/projects/project/wine_amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/wine_amd64.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/wine_amd64.mdwn	6 Sep 2018 14:57:51 -0000	1.5
+++ wikisrc/projects/project/wine_amd64.mdwn	11 Aug 2019 13:20:11 -0000	1.6
@@ -14,6 +14,7 @@
 
 category="userland"
 difficulty="easy"
+done_by"Naveen Narayanan"
 
 description="""
 The Wine program is made of two components, Wine32 and Wine64, that respectively
@@ -40,5 +41,3 @@
 Note that reaching the first step is already good.
 """
 ]]
-
-[[!tag gsoc]]

pgoyette-compat has been merged
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- wikisrc/releng/netbsd9.mdwn	31 Jul 2019 06:47:29 -0000	1.47
+++ wikisrc/releng/netbsd9.mdwn	31 Jul 2019 06:49:51 -0000	1.48
@@ -64,7 +64,7 @@
 
 ## Nice to have, but likely won't be finished on time
 
-* merge pgoyette-compat
+* ~~~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)
 

Remove pmax item that does not apply to this branch
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- wikisrc/releng/netbsd9.mdwn	7 Jan 2019 22:48:28 -0000	1.46
+++ wikisrc/releng/netbsd9.mdwn	31 Jul 2019 06:47:29 -0000	1.47
@@ -49,7 +49,6 @@
 * ~~~plug kernel pointer leaks~~~ (done)
 * ~~~fix Nouveau, some GPUs stopped working after the update~~~ (done)
 * umb(4) confirmed working with network traffic
-* [Revert pmax switch to common MIPS bus_space and bus_dma](https://releng.netbsd.org/cgi-bin/req-8.cgi?show=154)
 
 ## Nice to have
 

Update netbsd-9 status
Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- wikisrc/releng.mdwn	2 Jun 2019 10:27:03 -0000	1.35
+++ wikisrc/releng.mdwn	31 Jul 2019 06:39:21 -0000	1.36
@@ -9,7 +9,8 @@
 The next major release will be NetBSD 9.0.
 
 * Next release: NetBSD 9.0
-  + no CVS branch yet
+  + CVS branch tag: <code>netbsd-9</code>
+* [Current pull-up queue for the netbsd-9 branch](http://releng.netbsd.org/cgi-bin/req-9.cgi)
 * [[NetBSD 9.0 preliminary task list|releng/netbsd9]]
 
 ## Active Major Releases

Restrict scope to netbsd-8, newer versions have been fixed
Index: wikisrc/Installation_on_UEFI_systems.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/Installation_on_UEFI_systems.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/Installation_on_UEFI_systems.mdwn	13 Jun 2018 07:30:36 -0000	1.2
+++ wikisrc/Installation_on_UEFI_systems.mdwn	26 Jul 2019 07:30:42 -0000	1.3
@@ -1,8 +1,10 @@
 ## Installing NetBSD 8.0 on a x86 system with UEFI
 
-Modern x86 machines have UEFI instead of BIOS firmware. Unfortunately, as of the upcoming NetBSD 8.0 release the installer does not fully support this setup. We hope to address this shortcoming quickly after the NetBSD 8.0 release and provide full automatic installations for this kind of systems (and also mixed operating system setups) in NetBSD 8.1.
+Modern x86 machines have UEFI instead of BIOS firmware. Unfortunately, as of the NetBSD 8.0 release the installer did not fully support this setup.
 
-This tutorial shows how to semi-manually do it. For simplicity we assume that you have booted the UEFI install image from a USB stick and want to install NetBSD onto the whole disk in the machine.
+For NetBSD-current and NetBSD 9 the installer has been enhanced, it should automatically do the right thing for your machine, no matter if it has BIOS or UEFI firmware, or how big the disks are.
+
+This tutorial (__only for NetBSD 8.x!__) shows how to semi-manually do it. For simplicity we assume that you have booted the UEFI install image from a USB stick and want to install NetBSD onto the whole disk in the machine.
 
 ### Getting out of the Installer
 

Remove ISDN project following ISDN kernel code being removed.
ok martin
Members: 
	projects/project/isdn-nt-asterisk.mdwn:1.5->1.6(DEAD) 

--- wikisrc/projects/project/isdn-nt-asterisk.mdwn	2019-07-25 19:00:00.129473797 +0000
+++ /dev/null	2019-07-25 18:55:03.626518445 +0000
@@ -1,32 +0,0 @@
-[[!template id=project
-
-title="ISDN NT support and Asterisk integration"
-
-contact="""
-[tech-kern](mailto:tech-kern@NetBSD.org)
-"""
-
-mentors="""
-[Martin Husemann](mailto:martin@NetBSD.org)
-"""
-
-category="kernel"
-difficulty="medium"
-duration="3 months"
-
-description="""
-NetBSD is a common target for asterisk installations and could use some improvements.
-Improving ISDN puts us back in the running as a high-end installation target.
-
-This project has three milestones:
-
-* add support for the NT (network) side of ISDN to the NetBSD ISDN stack
-* interface ISDN (in NT mode) to the [Asterisk PBX](http://asterisk.org/), which would allow using existing ISDN PBXes as SIP/VoIP phones
-* show this makes it easier to test new ISDN card drivers
-
-Previous work in this area can be found at the [alternative ISDN driver site](http://www.turbocat.net/~hselasky/isdn4bsd/).
-
-The student needs access to ISDN and telephony hardware for this project.
-
-"""
-]]

show how the same script could be executed as a one liner
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	22 Jul 2018 17:18:06 -0000	1.26
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	21 Jul 2019 12:28:26 -0000	1.27
@@ -101,7 +101,10 @@
     dtrace: script './hello.d' matched 1 probe
     CPU     ID                    FUNCTION:NAME
       0      1                           :BEGIN   Hello world
-    
+
+The same script could be executed as a one liner on the shell, using
+
+    dtrace -n 'BEGIN { trace("Hello world"); exit(0); }'
 
 ## A more complex example
 

Move pkgsrcCon 2019 to past events
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -r1.77 -r1.78
--- wikisrc/events.mdwn	14 Jun 2019 21:56:52 -0000	1.77
+++ wikisrc/events.mdwn	19 Jul 2019 12:22:44 -0000	1.78
@@ -12,19 +12,6 @@
 
 Future Events
 -------------
-
-### `Jul 2019` - pkgsrcCon 2019, Cambridge, United Kingdom
-
-*July 13 - 14, 2019, Cambridge, United Kingdom*
-
-[pkgsrcCon](//pkgsrc.org/pkgsrcCon/2019/) is the annual technical
-conference for people working on pkgsrc, a framework for building
-over 19,000 open source software packages.
-pkgsrc is the native package manager on NetBSD, SmartOS and Minix, and
-is portable across many different operating systems including Linux and
-Mac OS X.
-
-
 ### `Sep 2019` - EuroBSDcon 2019, Lillehammer, Norway
 
 *September 19 - 22, 2019, Scandic Lillehammer Hotel, Lillehammer, Norway*
@@ -54,6 +41,18 @@
 
 Past Events
 -----------
+### `Jul 2019` - pkgsrcCon 2019, Cambridge, United Kingdom
+
+*July 13 - 14, 2019, Cambridge, United Kingdom*
+
+[pkgsrcCon](//pkgsrc.org/pkgsrcCon/2019/) is the annual technical
+conference for people working on pkgsrc, a framework for building
+over 19,000 open source software packages.
+pkgsrc is the native package manager on NetBSD, SmartOS and Minix, and
+is portable across many different operating systems including Linux and
+Mac OS X.
+
+
 ### `May 2019` - BSDCan 2019, Ottawa, Canada
 
 *May 15 - 18, 2019, University of Ottawa, Ottawa, Canada*

do not claim RPI4 is supported
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -r1.119 -r1.120
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	19 May 2019 10:23:52 -0000	1.119
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	27 Jun 2019 17:34:15 -0000	1.120
@@ -1,10 +1,10 @@
 [[!meta title="NetBSD/evbarm on Raspberry Pi"]]
 
-This page describes the NetBSD/evbarm port on [Raspberry Pi](http://www.raspberrypi.org) hardware.  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are believed supported, and specific boards know to work are listed.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.  This web page is 32-bit (aarch32) centric, as that has been until mid-2018 the only approach.
+This page describes the NetBSD/evbarm port on [Raspberry Pi](http://www.raspberrypi.org) hardware.  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) earlier than the RPI4 are believed supported, and specific boards known to work are listed.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.  This web page is 32-bit (aarch32) centric, as that has been until mid-2018 the only approach.
 
 Initial, limited, Raspberry Pi support was introduced in NetBSD 6.0.  NetBSD 7.0 adds complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board.  Raspberry Pi 3 support was added for NetBSD 8, and backported to NetBSD 7 in July of 2017.  (This page assumes those using NetBSD 7 are using 7.2 or later, but note that everyone uses 8 or -current.)
 
-In mid-2018, -current gained support for 64-bit ARM (aarch64) support.
+In mid-2018, -current gained support for 64-bit ARM (aarch64) support.  This will be in NetBSD 9.
 
 [[images/raspberrypi.jpg]]
 
@@ -48,6 +48,7 @@
 
 ## What needs work
 
+ - RPI4 (almost certainly; not clear)
  - USB (host); isochronous transfers.
  - RPI3, RPI0W builtin WiFi
  - RPI0W Bluetooth Low Energy (probably)

add another rpi page pointer
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.80
retrieving revision 1.81
diff -u -r1.80 -r1.81
--- wikisrc/ports/evbarm.mdwn	27 Jun 2019 17:30:46 -0000	1.80
+++ wikisrc/ports/evbarm.mdwn	27 Jun 2019 17:32:09 -0000	1.81
@@ -283,6 +283,8 @@
 ### Raspberry Pi Foundation **Raspberry Pi**/**Raspberry Pi 2**/**Raspberry Pi 3**
 The [[Raspberry Pi]] is a low-cost credit-card-sized computer from the Raspberry Pi Foundation.  The Raspberry Pi, Pi 2, and Pi 3 are supported.
 
+See the [[Raspberry Pi 1, 2 and 3|Raspberry Pi]] page for much more information.
+
 ### Samsung **SMDK2410**
 
 The SMDK2410 is the reference platform for the Samsung **S3C2410** processor,

note that board-specific info has installation info
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- wikisrc/ports/evbarm.mdwn	27 Jun 2019 17:29:39 -0000	1.79
+++ wikisrc/ports/evbarm.mdwn	27 Jun 2019 17:30:46 -0000	1.80
@@ -61,7 +61,7 @@
 
 NetBSD developer Jared McNeill provides [builds of NetBSD-current for a vast variety of hardware.](https://www.invisible.ca/arm/)   In addition to the standard build, these images have board-specific uboot contents.  See also /usr/pkgsrc/sysutils/u-boot*.
 
-### Board specific information
+### Board specific information (often including installation information)
  - [[Allwinner sunxi family SoCs|Allwinner]]
  - [[BeagleBone, BeagleBone Black, and PocketBeagle|BeagleBone]]
  - [[NVIDIA Tegra|Tegra]]

restore ssh content
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -r1.78 -r1.79
--- wikisrc/ports/evbarm.mdwn	27 Jun 2019 17:28:31 -0000	1.78
+++ wikisrc/ports/evbarm.mdwn	27 Jun 2019 17:29:39 -0000	1.79
@@ -68,8 +68,6 @@
  - [[ODROID C1 and C1+|ODROID-C1]]
  - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]]
 
-"""
-
 ### SSH configuration for installtion
 
 The default configuration will connect to the local network via DHCP and
@@ -82,6 +80,7 @@
 
 <!--TODO: Additional configuration options are available on creds_msdos.8-->
 
+"""
 supported_hardware="""
 
 **NOTE**: This list is incomplete. For a full list of boards, please see the [GENERIC DTS files](http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sys/arch/evbarm/conf/GENERIC).

Add invisible.ca pointer
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -r1.77 -r1.78
--- wikisrc/ports/evbarm.mdwn	27 Jun 2019 16:52:01 -0000	1.77
+++ wikisrc/ports/evbarm.mdwn	27 Jun 2019 17:28:31 -0000	1.78
@@ -57,6 +57,10 @@
  - evbarm-aarch64 uses "qemu-system-aarch64 -M virt"
  - Information on how to test emulated versions of other specific hardware is welcome.
 
+### invisible.ca builds
+
+NetBSD developer Jared McNeill provides [builds of NetBSD-current for a vast variety of hardware.](https://www.invisible.ca/arm/)   In addition to the standard build, these images have board-specific uboot contents.  See also /usr/pkgsrc/sysutils/u-boot*.
+
 ### Board specific information
  - [[Allwinner sunxi family SoCs|Allwinner]]
  - [[BeagleBone, BeagleBone Black, and PocketBeagle|BeagleBone]]

evbarm: move ssh info (which is a detail) later
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -r1.76 -r1.77
--- wikisrc/ports/evbarm.mdwn	12 Jun 2019 09:02:16 -0000	1.76
+++ wikisrc/ports/evbarm.mdwn	27 Jun 2019 16:52:01 -0000	1.77
@@ -18,18 +18,6 @@
 supports some specific embedded system products based on prototype board
 designs.
 
-### SSH configuration
-
-The default configuration will connect to the local network via DHCP and
-run an SSH server. In order to use the SSH server, we must configure
-users. This can be done by writing to the SD card's MS-DOS partition.
-
-Create a creds.txt file and use:
-
-           useradd user password
-
-<!--TODO: Additional configuration options are available on creds_msdos.8-->
-
 ### CPU types
 
 The evbarm port can be built with a variety of CPU options, corresponding to the
@@ -78,6 +66,18 @@
 
 """
 
+### SSH configuration for installtion
+
+The default configuration will connect to the local network via DHCP and
+run an SSH server. In order to use the SSH server, we must configure
+users. This can be done by writing to the SD card's MS-DOS partition.
+
+Create a creds.txt file and use:
+
+           useradd user password
+
+<!--TODO: Additional configuration options are available on creds_msdos.8-->
+
 supported_hardware="""
 
 **NOTE**: This list is incomplete. For a full list of boards, please see the [GENERIC DTS files](http://cvsweb.netbsd.org/bsdweb.cgi/~checkout~/src/sys/arch/evbarm/conf/GENERIC).

Add a comment