Recent changes to this wiki:

fix up ` usages
Index: wikisrc/tutorials/how_to_set_up_nfs_and_nis.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_set_up_nfs_and_nis.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/how_to_set_up_nfs_and_nis.mdwn	26 May 2020 07:24:36 -0000	1.4
+++ wikisrc/tutorials/how_to_set_up_nfs_and_nis.mdwn	30 May 2020 06:15:02 -0000	1.5
@@ -15,7 +15,7 @@
 
 We will need NIS (or another directory service) to make sure the NFS user ids/group ids are the same on the server as on all clients. Otherwise, bad things will happen, as you can probably imagine (especially in our example of mounting /home over NFS). Note that using NIS with NFS is not mandatory, you can also keep the server and client's passwd in synch. 
 
-NIS used to be called the `Yellow Pages', or YP for short. Because of trademarks it had to be renamed, but the programs are all still prefixed with `yp'. 
+NIS used to be called the "Yellow Pages", or YP for short. Because of trademarks it had to be renamed, but the programs are all still prefixed with `yp`. 
 
   
 
@@ -42,7 +42,7 @@
 The first thing we should do is decide on a NIS domain name. This has nothing to do with your machine's Internet domain name. It is just a unique name that is used to identify machines in the same NIS block. 
 
 The domainname is set (as root) using the [domainname(1)](http://netbsd.gw.com/cgi-bin/man-cgi?domainname+1+NetBSD-current) program, or can be set in the /etc/mydomain file.   
-Alternatively, in most BSD systems, it can be set in /etc/rc.conf under the variable `domainname'. 
+Alternatively, in most BSD systems, it can be set in /etc/rc.conf under the variable `domainname`. 
     
 
  root@earth# domainname planets
@@ -57,7 +57,7 @@
 The -m means we are creating a master server. On more complex networks, you can even want slave servers. The tool will ask you for a list of YP servers to bind to.   
 Since we're only using one server, just press RETURN (make sure your own server's internal address is in the list). 
 
-Before we run `make' in /var/yp, as the tool says, we must enable the NIS daemons: rpcbind, ypserv and ypbind (in that order). After that, we can run `make' in /var/yp. 
+Before we run `make` in /var/yp, as the tool says, we must enable the NIS daemons: rpcbind, ypserv and ypbind (in that order). After that, we can run `make` in /var/yp. 
 
 To test if your setup is working, try yptest. It should spew out the passwd file among others, so don't panic ;) 
 
@@ -80,7 +80,7 @@
 
 [rpc.yppasswdd(8)](http://netbsd.gw.com/cgi-bin/man-cgi?rpc.yppasswdd+8+NetBSD-current) must be running on the NIS master server to allow users to change information in the password file.   
 [ypserv(8)](http://netbsd.gw.com/cgi-bin/man-cgi?ypserv+8+NetBSD-current) provides information from NIS maps to the NIS clients on the network.   
-[ypbind(8)](http://netbsd.gw.com/cgi-bin/man-cgi?ypbind+8+NetBSD-current) finds the server for a particular NIS domain and stores information about it in a ``binding file_._
+[ypbind(8)](http://netbsd.gw.com/cgi-bin/man-cgi?ypbind+8+NetBSD-current) finds the server for a particular NIS domain and stores information about it in a "binding file".
 
 After that, you can use ypinit: 
     
@@ -89,7 +89,7 @@
 
 Then, add your NIS server's address to the list. To test if everything is working, use yptest on the client as well. **Note that ypbind will HANG if it can't find the server!**
 
-If everything is working, you are ready to go! Just edit /etc/nsswitch.conf and put in some `nis' keywords. For example: 
+If everything is working, you are ready to go! Just edit /etc/nsswitch.conf and put in some `nis` keywords. For example: 
     
      passwd:		files nis
     
@@ -143,7 +143,7 @@
 
 and have them mounted at system startup. 
 
-NOTE: I had much trouble with NFS which was caused by UDP packet fragmentation. This made all writes extremely slow (and other outgoing network traffic as well!) while reads were at an acceptable speed. To solve this, I added the (undocumented?) `tcp' option to fstab to mount NFS over TCP. You'll probably also need to add 
+NOTE: I had much trouble with NFS which was caused by UDP packet fragmentation. This made all writes extremely slow (and other outgoing network traffic as well!) while reads were at an acceptable speed. To solve this, I added the (undocumented?) `tcp` option to fstab to mount NFS over TCP. You'll probably also need to add 
     
     nfsd_flags='-t'
     

EuroBSDCon 2020 is cancelled, remove from events
<https://lists.eurobsdcon.org/pipermail/announce/2020-May/000008.html>
Members: 
	events.mdwn:1.87->1.88 

Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.87
retrieving revision 1.88
diff -u -r1.87 -r1.88
--- wikisrc/events.mdwn	3 Mar 2020 16:05:45 -0000	1.87
+++ wikisrc/events.mdwn	27 May 2020 16:32:15 -0000	1.88
@@ -24,19 +24,6 @@
 advanced developers.
 
 
-### `Sep 2020` - EuroBSDcon 2020, Vienna, Austria
-
-*September 17 - 20, 2020, The Gußhaus Campus of Vienna's Technical University, Vienna, Austria*
-
-[EuroBSDcon](https://2020.eurobsdcon.org/) is the premier European
-conference on the open source BSD operating systems attracting
-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
 -----------
 ### `Feb 2020` - FOSDEM 2020 Brussels, Belgium

update stale URLs
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- wikisrc/ports/evbarm/odroid-c1.mdwn	22 Nov 2017 14:35:02 -0000	1.29
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	26 May 2020 13:46:46 -0000	1.30
@@ -1,6 +1,6 @@
 [[!meta title="NetBSD/evbarm on Hardkernel ODROID-C1 and ODROID-C1+"]]
 
-[ODROID-C1](http://www.hardkernel.com/main/products/prdt_info.php?g_code=G141578608433&tab_idx=1) was a $35 quad-core SBC from Hardkernel. ODROID-C1 support was introduced in NetBSD 7.0.  It has been succeeded by the [ODROID-C1+](http://www.hardkernel.com/main/products/prdt_info.php?g_code=G143703355573), which is supported by the same NetBSD kernel.
+[ODROID-C1](https://www.hardkernel.com/shop/odroid-c1-2/) was a $35 quad-core SBC from Hardkernel. ODROID-C1 support was introduced in NetBSD 7.0.  It has been succeeded by the [ODROID-C1+](https://www.hardkernel.com/shop/odroid-c1/), which is supported by the same NetBSD kernel.
 
 [[!toc levels=2]]
 

be consistent, deamon->daemon
Index: wikisrc/tutorials/how_to_set_up_nfs_and_nis.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_set_up_nfs_and_nis.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/tutorials/how_to_set_up_nfs_and_nis.mdwn	24 Nov 2014 02:18:26 -0000	1.3
+++ wikisrc/tutorials/how_to_set_up_nfs_and_nis.mdwn	26 May 2020 07:24:36 -0000	1.4
@@ -57,7 +57,7 @@
 The -m means we are creating a master server. On more complex networks, you can even want slave servers. The tool will ask you for a list of YP servers to bind to.   
 Since we're only using one server, just press RETURN (make sure your own server's internal address is in the list). 
 
-Before we run `make' in /var/yp, as the tool says, we must enable the NIS deamons: rpcbind, ypserv and ypbind (in that order). After that, we can run `make' in /var/yp. 
+Before we run `make' in /var/yp, as the tool says, we must enable the NIS daemons: rpcbind, ypserv and ypbind (in that order). After that, we can run `make' in /var/yp. 
 
 To test if your setup is working, try yptest. It should spew out the passwd file among others, so don't panic ;) 
 
@@ -96,7 +96,7 @@
 
 would first look up usernames/passwords/uids in /etc/passwd, and if it can't find it, it would look it up using NIS. Right after changing this file, you should be able to log in on your system using a username which is only in /etc/passwd on the server. That's all there is to it. 
 
-#  The deamons 
+#  The daemons 
 
 What are all those daemons for? Well, here's a quick rundown: 
 
@@ -114,7 +114,7 @@
      /home		-network 192.168.0.0 -mask 255.255.0.0 -maproot=root
     
 
-This exports /home only on the LAN 192.168.x.x. The maproot line is needed, because otherwise the client's root will not have superuser access. Now, start the mount daemon and the NFS deamons (mountd and nfsd) as root on your server, in that order. For that type: 
+This exports /home only on the LAN 192.168.x.x. The maproot line is needed, because otherwise the client's root will not have superuser access. Now, start the mount daemon and the NFS daemons (mountd and nfsd) as root on your server, in that order. For that type: 
     
      root@mars# /etc/rc.d/rpcbind onestart
      root@mars# /etc/rc.d/mountd onestart

s/less than/up to/
as domains can have 'less than or equal to' the number of CPUs seen
by the hypervisor, but that is cumbersome to say
Members: 
	ports/xen/howto.mdwn:1.168->1.169 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.168
retrieving revision 1.169
diff -u -r1.168 -r1.169
--- wikisrc/ports/xen/howto.mdwn	3 Apr 2020 10:48:35 -0000	1.168
+++ wikisrc/ports/xen/howto.mdwn	25 May 2020 09:28:21 -0000	1.169
@@ -337,7 +337,7 @@
 CPU and memory
 --------------
 
-A domain is provided with some number of vcpus, less than the number
+A domain is provided with some number of vcpus, up to the number
 of CPUs seen by the hypervisor. For a domU, it is controlled
 from the config file by the "vcpus = N" directive.
 

set CC=cc in environment, discussed in #pkgsrc
Index: wikisrc/pkgsrc/how_to_use_pkgsrc_on_irix.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/how_to_use_pkgsrc_on_irix.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/pkgsrc/how_to_use_pkgsrc_on_irix.mdwn	5 Feb 2012 07:14:36 -0000	1.2
+++ wikisrc/pkgsrc/how_to_use_pkgsrc_on_irix.mdwn	24 May 2020 22:41:47 -0000	1.3
@@ -64,7 +64,7 @@
 $ gzcat ../pkgsrc.tar.gz | tar xf -
 $ cd pkgsrc
 
-$ ./bootstrap/bootstrap --unprivileged --compiler=mipspro
+$ CC=cc ./bootstrap/bootstrap --unprivileged --compiler=mipspro
 </code></pre>
 ... TODO: continue
 
@@ -77,4 +77,4 @@
 #External links
 
 * [pkgsrc on IRIX](http://wtf.hijacked.us/wiki/index.php/Pkgsrc_on_IRIX) @ WTFwiki
-* [Using NetBSD's pkgsrc on IRIX](http://forums.nekochan.net/viewtopic.php?f=15&t=11217) @ Nekochan 
\ No newline at end of file
+* [Using NetBSD's pkgsrc on IRIX](http://forums.nekochan.net/viewtopic.php?f=15&t=11217) @ Nekochan 

Expand a bit regarding nvi package option (pointed out by mef via #pkgsrc @
Freenode and consistent with e.g. mutt entry)
Index: wikisrc/tutorials/unicode.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/unicode.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/tutorials/unicode.mdwn	23 May 2020 14:13:16 -0000	1.2
+++ wikisrc/tutorials/unicode.mdwn	23 May 2020 14:31:07 -0000	1.3
@@ -179,7 +179,10 @@
 
 ##  nvi 
 
-  * pkgsrc' nvi (v1.81.6) works with wide-range characters if built with `wide-curses` option.
+pkgsrc' nvi (v1.81.6) works with wide-range characters if built with `wide-curses` option,
+e.g. by adding to mk.conf:
+
+      PKG_OPTIONS.nvi+= wide-curses
 
 ##  vim 
 

Integrate the nvi comment in the wiki article.
Thanks to Ottavio Caruso!
Members: 
	tutorials/unicode.mdwn:1.1->1.2 

Index: wikisrc/tutorials/unicode.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/unicode.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/tutorials/unicode.mdwn	27 Apr 2019 19:55:01 -0000	1.1
+++ wikisrc/tutorials/unicode.mdwn	23 May 2020 14:13:16 -0000	1.2
@@ -179,9 +179,7 @@
 
 ##  nvi 
 
-  * pkgsrc' nvi (v1.81.5) is supposed to work with wide-range characters after some tweaks. 
-
-(XXX) 
+  * pkgsrc' nvi (v1.81.6) works with wide-range characters if built with `wide-curses` option.
 
 ##  vim 
 

Added a comment: Enable unicode on editors/nvi
--- /dev/null	2020-05-23 14:06:37.390311645 +0000
+++ wikisrc/tutorials/unicode/comment_1_00b1174bf1ae2f62e4d32da440f83d79._comment	2020-05-23 14:06:38.667818605 +0000
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="https://launchpad.net/~ottaviocr"
+ nickname="ottaviocr"
+ subject="Enable unicode on editors/nvi"
+ date="2020-05-23T14:05:46Z"
+ content="""
+In order for editors/nvi (pkgsrc) to understand unicode, it needs to be built with PKG_OPTIONS.nvi=\"wide-curses\" .
+
+"""]]

List changes_port as an optional variable
Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- wikisrc/templates/port.mdwn	23 May 2020 12:40:03 -0000	1.25
+++ wikisrc/templates/port.mdwn	23 May 2020 13:02:15 -0000	1.26
@@ -223,6 +223,7 @@
 - pkg_rel (optional)
 - changes_cur (optional)
 - changes_future (required)
+- changes_port (optional)
 - thumbnail (optional)
 - supported_hardware (optional)
 - unsupported_hardware (optional)

Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/aarch64.mdwn	13 Apr 2020 10:17:01 -0000	1.9
+++ wikisrc/ports/aarch64.mdwn	23 May 2020 12:43:34 -0000	1.10
@@ -1,5 +1,6 @@
 [[!template id=port
-port="aarch64"
+port="evbarm-aarch64"
+changes_port="evbarm64"
 port_alt="arm"
 future_rel="10.0"
 changes_future="10.0"

Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- wikisrc/templates/port.mdwn	23 May 2020 12:37:15 -0000	1.24
+++ wikisrc/templates/port.mdwn	23 May 2020 12:40:03 -0000	1.25
@@ -147,7 +147,6 @@
         <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR changes_port>">
           NetBSD/<TMPL_VAR changes_port> <TMPL_VAR changes_cur> changes
         </a>
-      </TMPL_IF>
       <TMPL_ELSE>
         <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR port>">
           NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes
@@ -160,7 +159,6 @@
       <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_future>.html#port-<TMPL_VAR changes_port>">
         NetBSD/<TMPL_VAR changes_port> <TMPL_VAR changes_future> changes
       </a>
-    </TMPL_IF>
     <TMPL_ELSE>
       <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_future>.html#port-<TMPL_VAR port>">
         NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes

Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- wikisrc/templates/port.mdwn	29 Feb 2020 21:11:26 -0000	1.23
+++ wikisrc/templates/port.mdwn	23 May 2020 12:37:15 -0000	1.24
@@ -143,15 +143,29 @@
   </TMPL_IF>
   <TMPL_IF changes_cur>
     <li>
-      <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR port>">
-        NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes
-      </a>
+      <TMPL_IF changes_port>
+        <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR changes_port>">
+          NetBSD/<TMPL_VAR changes_port> <TMPL_VAR changes_cur> changes
+        </a>
+      </TMPL_IF>
+      <TMPL_ELSE>
+        <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_cur>.html#port-<TMPL_VAR port>">
+          NetBSD/<TMPL_VAR port> <TMPL_VAR changes_cur> changes
+        </a>
+      </TMPL_IF>
     </li>
   </TMPL_IF>
   <li>
-    <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_future>.html#port-<TMPL_VAR port>">
-      NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes
-    </a>
+    <TMPL_IF changes_port>
+      <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_future>.html#port-<TMPL_VAR changes_port>">
+        NetBSD/<TMPL_VAR changes_port> <TMPL_VAR changes_future> changes
+      </a>
+    </TMPL_IF>
+    <TMPL_ELSE>
+      <a title="NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes" href="https://www.NetBSD.org/changes/changes-<TMPL_VAR changes_future>.html#port-<TMPL_VAR port>">
+        NetBSD/<TMPL_VAR port> <TMPL_VAR changes_future> changes
+      </a>
+    </TMPL_IF>
   </li>
 </ul>
 

there is no -g, filename is specified with -e
Index: wikisrc/users/haad/ddb_howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/haad/ddb_howto.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/haad/ddb_howto.mdwn	8 Apr 2019 23:46:36 -0000	1.3
+++ wikisrc/users/haad/ddb_howto.mdwn	20 May 2020 21:12:48 -0000	1.4
@@ -18,7 +18,7 @@
 
 Then add `0x5` to the address, and use [[!template id=man name="addr2line" section="1"]] to get the exact line in the kernel source code where you get the crash:
 
-    addr2line -g netbsd {sum address}
+    addr2line -e netbsd {sum address}
 
 In [[!template id=man name="gdb" section="1"]], this can be achieved with the command `info line *(function_name)+0x5`.
 

Removed uyap
Index: wikisrc/attic_museum.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/attic_museum.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/attic_museum.mdwn	29 Jan 2020 19:03:42 -0000	1.17
+++ wikisrc/attic_museum.mdwn	16 May 2020 13:51:06 -0000	1.18
@@ -47,5 +47,6 @@
 FDDI		|Network Protocol	|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/20/msg113058.html)
 fpa		|Network Driver		|01/2020	|				|[Commit](https://mail-index.netbsd.org/source-changes/2020/01/20/msg113058.html)
 urio		|Device Driver		|01/2020	|				|[Commit](http://mail-index.netbsd.org/source-changes/2020/01/29/msg113476.html)
+uyap		|Device Driver		|05/2020	|				|[Commit](http://mail-index.netbsd.org/source-changes/2020/05/16/msg117393.html)
 """]]
 

Mention pkgtasks and how to enable it
Index: wikisrc/projects/project/pkgsrc_installtasks.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_installtasks.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/project/pkgsrc_installtasks.mdwn	15 May 2020 22:18:33 -0000	1.6
+++ wikisrc/projects/project/pkgsrc_installtasks.mdwn	16 May 2020 10:55:48 -0000	1.7
@@ -27,5 +27,12 @@
 * allow options framework to configure these resources per-package
 
 An intermediate step would be to replace various remaining INSTALL scripts by declarative statements and install script snippets using them.
+
+This was implemented via the new pkgtasks framework that can be enabled by
+setting in `mk.conf`:
+
+````
+_USE_NEW_PKGINSTALL=    yes
+````
 """
 ]]

remove gsoc tag
Index: wikisrc/projects/project/pkgsrc_installtasks.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_installtasks.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/pkgsrc_installtasks.mdwn	15 May 2020 22:16:32 -0000	1.5
+++ wikisrc/projects/project/pkgsrc_installtasks.mdwn	15 May 2020 22:18:33 -0000	1.6
@@ -29,5 +29,3 @@
 An intermediate step would be to replace various remaining INSTALL scripts by declarative statements and install script snippets using them.
 """
 ]]
-
-[[!tag gsoc]]

Mark as done by jlam, so it doesn't show up in next gsoc.
Index: wikisrc/projects/project/pkgsrc_installtasks.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_installtasks.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/pkgsrc_installtasks.mdwn	20 Feb 2015 17:42:22 -0000	1.4
+++ wikisrc/projects/project/pkgsrc_installtasks.mdwn	15 May 2020 22:16:32 -0000	1.5
@@ -13,6 +13,7 @@
 category="pkgsrc"
 difficulty="medium"
 duration="3 months"
+done_by="Johnny C. Lam"
 
 description="""
 Instead of including install scripts from the infrastructure into every binary package, just include the necessary information and split the scripts off into a separate package that is installed first (right after bootstrap, as soon as the first package needs it). This affects user creation, installation of tex packages, ...

Fix some typos, uppercase CVS.
Index: wikisrc/Wifi_renewal_on_hg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/Wifi_renewal_on_hg.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/Wifi_renewal_on_hg.mdwn	26 Apr 2020 16:12:42 -0000	1.2
+++ wikisrc/Wifi_renewal_on_hg.mdwn	26 Apr 2020 16:35:39 -0000	1.3
@@ -4,9 +4,9 @@
 
 ## Why hg?
 
-The project started with a traditional cvs branch, but as we will be moving to mercurial anyway (and this "branch" could live for quite some time, even accross the general repo switch), it is a good test case for the hg environment and also nice practice for the developers involved.
+The project started with a traditional CVS branch, but as we will be moving to mercurial anyway (and this "branch" could live for quite some time, even across the general repo switch), it is a good test case for the hg environment and also nice practice for the developers involved.
 
-The developement uses a "topic", which is a kind of lightweight branch that goes away after the project finished. The hg documentation includes
+The development uses a "topic", which is a kind of lightweight branch that goes away after the project finished. The hg documentation includes
 an [introduction to topics](https://www.mercurial-scm.org/doc/evolution/tutorials/topic-tutorial.html).
 
 ## Helping with testing
@@ -22,15 +22,15 @@
     [extensions]
     topic=
 
-to the .hg/hgrc file in your clone dir and then update to the 'wifi' topic:
+to the .hg/hgrc file in your clone directory and then update to the 'wifi' topic:
 
     > hg up wifi
 
-## Helping with developement
+## Helping with development
 
-As a developer, you should start with an annonhg clone as well, as that uses 'clonebundles' and the CDN to get your clone faster.
+As a developer, you should start with an anonhg clone as well, as that uses 'clonebundles' and the CDN to get your clone faster.
 
-The developement happens using the topic and evolve extensions, which unfortunately slows down some hg operations.
+The development happens using the topic and evolve extensions, which unfortunately slows down some hg operations.
 
 After initial cloning (see above) you will have to edit your global ~/.hgrc and the clone local .hg/hgrc files. Here is my ~/.hgrc:
 
@@ -48,14 +48,14 @@
     pager=
     rebase=
 
-The .hgignore file referened there tells hg to leave editor backups and compiled kernels alone. Mine looks like:
+The .hgignore file referenced there tells hg to leave editor backups and compiled kernels alone. Mine looks like:
 
     syntax: glob
     *~
     *.o
     sys/arch/amd64/compile/*
 
-Finaly the clone local config (.hg/hgrc) looks like this:
+Finally the clone local config (.hg/hgrc) looks like this:
 
     [paths]
     default = ssh://hgmaster.netbsd.org//repo/src-draft
@@ -63,4 +63,4 @@
     [phases]
     publish=false
 
-This directs normal pushes to the src-draft repository and prevents publishing (that is what "merging the branch to HEAD" would have been in cvs). When it is time to do that, a "final" push will be done that moves the changes to the src-public repository (and empties the topic, which will make it vanish on next update).
+This directs normal pushes to the src-draft repository and prevents publishing (that is what "merging the branch to HEAD" would have been in CVS). When it is time to do that, a "final" push will be done that moves the changes to the src-public repository (and empties the topic, which will make it vanish on next update).

typo
Index: wikisrc/Wifi_renewal_on_hg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/Wifi_renewal_on_hg.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/Wifi_renewal_on_hg.mdwn	26 Apr 2020 12:03:41 -0000	1.1
+++ wikisrc/Wifi_renewal_on_hg.mdwn	26 Apr 2020 16:12:42 -0000	1.2
@@ -63,4 +63,4 @@
     [phases]
     publish=false
 
-This directs normal pushes to the src-draft repository and prevents publishing (that is what "merging the branch to HEAD" would have been in cvs). When it is time to do that, a "final" push will be done that moves the changes to the src-pulbic repository (and empties the topic, which will make it vanish on next update).
+This directs normal pushes to the src-draft repository and prevents publishing (that is what "merging the branch to HEAD" would have been in cvs). When it is time to do that, a "final" push will be done that moves the changes to the src-public repository (and empties the topic, which will make it vanish on next update).

First draft of instructions how to participate in the wifi developement via hg
--- /dev/null	2020-04-26 12:04:04.728453499 +0000
+++ wikisrc/Wifi_renewal_on_hg.mdwn	2020-04-26 12:04:20.783062053 +0000
@@ -0,0 +1,66 @@
+#How to help with the Wifi renewal "branch" in hg
+
+The wifi renewal project is trying to sync our sys/net80211 with FreeBSD as far as possible, to allow easier sharing of drivers.
+
+## Why hg?
+
+The project started with a traditional cvs branch, but as we will be moving to mercurial anyway (and this "branch" could live for quite some time, even accross the general repo switch), it is a good test case for the hg environment and also nice practice for the developers involved.
+
+The developement uses a "topic", which is a kind of lightweight branch that goes away after the project finished. The hg documentation includes
+an [introduction to topics](https://www.mercurial-scm.org/doc/evolution/tutorials/topic-tutorial.html).
+
+## Helping with testing
+
+** Note that this project is not ready for general testing yet! **
+
+If you just want to check out the wifi project source and build your own test kernel for it, you simply start by cloning the repository from anonhg:
+
+    > hg clone https://anonhg.netbsd.org/src-draft
+
+Now enable the 'topic' extension by adding
+
+    [extensions]
+    topic=
+
+to the .hg/hgrc file in your clone dir and then update to the 'wifi' topic:
+
+    > hg up wifi
+
+## Helping with developement
+
+As a developer, you should start with an annonhg clone as well, as that uses 'clonebundles' and the CDN to get your clone faster.
+
+The developement happens using the topic and evolve extensions, which unfortunately slows down some hg operations.
+
+After initial cloning (see above) you will have to edit your global ~/.hgrc and the clone local .hg/hgrc files. Here is my ~/.hgrc:
+
+    [ui]
+    user=Martin Husemann <martin@NetBSD.org>
+    color = no
+    ignore = ~/.hgignore
+    [paths]
+    default:pushrev = .
+    [extensions]
+    evolve=
+    topic=
+    share=
+    purge=
+    pager=
+    rebase=
+
+The .hgignore file referened there tells hg to leave editor backups and compiled kernels alone. Mine looks like:
+
+    syntax: glob
+    *~
+    *.o
+    sys/arch/amd64/compile/*
+
+Finaly the clone local config (.hg/hgrc) looks like this:
+
+    [paths]
+    default = ssh://hgmaster.netbsd.org//repo/src-draft
+    final = ssh://hgmaster.netbsd.org//repo/src-public
+    [phases]
+    publish=false
+
+This directs normal pushes to the src-draft repository and prevents publishing (that is what "merging the branch to HEAD" would have been in cvs). When it is time to do that, a "final" push will be done that moves the changes to the src-pulbic repository (and empties the topic, which will make it vanish on next update).

Guide for using the hg wifi "branch"
Index: wikisrc/tutorials.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials.mdwn,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- wikisrc/tutorials.mdwn	25 Feb 2020 20:00:28 -0000	1.40
+++ wikisrc/tutorials.mdwn	26 Apr 2020 11:40:53 -0000	1.41
@@ -36,6 +36,7 @@
 
 ### Kernel
 * [[Kernel debugging with QEMU]]
+* [[Wifi renewal on hg]]
 
 ### Testing
 * [[atf]]

Index: wikisrc/wiki/RootOnZFS.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/wiki/RootOnZFS.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/wiki/RootOnZFS.mdwn	25 Feb 2020 19:56:20 -0000	1.2
+++ wikisrc/wiki/RootOnZFS.mdwn	14 Apr 2020 12:04:37 -0000	1.3
@@ -52,6 +52,8 @@
   *  Add `rpool/ROOT /altroot zfs rw` to /etc/fstab
   *  `mount /altroot`
   *  Extract the sets you need to `/altroot`. At a minimum you will need etc and base.
+  *  `cd /altroot/dev; ./MAKEDEV all`
+  *  `cd /altroot; mkdir kern proc`
   *  Copy `/etc/wscons.conf`, `/etc/fstab` and any other config files sysinst might have created to `/etc/rc.conf` to `/altroot/etc`
   *  Set `zfs=YES` in `/altroot/etc/rc.conf`
   *  Remove `rpool/ROOT` from `/altroot/etc/fstab`

More boards
Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/ports/aarch64.mdwn	15 Feb 2020 15:43:14 -0000	1.8
+++ wikisrc/ports/aarch64.mdwn	13 Apr 2020 10:17:01 -0000	1.9
@@ -41,6 +41,8 @@
  * NVIDIA Jetson TX1
  * PINE64 A64, A64+, A64-LTS, SOPINE, Pinebook, Pinebook Pro, Rock64, RockPro64
  * Raspberry Pi 3
+ * Orange Pi PC 2, Prime, Zero Plus, Zero Plus 2, Lite 2, One Plus
+ * Banana Pi M64, M2+
 
 ### Known Supported CPUs
 

Grammar fixes
Index: wikisrc/grub2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/grub2.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/grub2.mdwn	9 Dec 2012 18:47:53 -0000	1.2
+++ wikisrc/grub2.mdwn	10 Apr 2020 16:24:15 -0000	1.3
@@ -1,21 +1,20 @@
 # How to install GRUB2 on NetBSD
 
 This how-to explains the steps needed to install GRUB2 on an existing i386/AMD64
-NetBSD-installation. The steps should work on a properly chroot'ed system too.
+NetBSD installation. The steps should work on a properly chroot'ed system too.
 Tested on NetBSD 6.0 AMD64:
 
 First of all, either download the package, using `pkgin install grub2`, or build 
 it yourself from package sources (`/usr/pkgsrc/sysutils/grub2`).
 
-
 After that, generate a GRUB configuration file, which tells GRUB the positions 
 of the operating system(s). The following command will generate such a file, 
-while adding your NetBSD system into it's list.
+while adding your NetBSD system into its list.
 
     # grub-mkconfig -o /grub/grub.cfg
 
 Now, install GRUB into your hard drive's master boot record (MBR).
-You have to know it's device name for this step (e.g. `/dev/rwd0a`).
+You have to know its device name for this step (e.g. `/dev/rwd0a`).
 Exchange `/dev/rwd0a` with your desired device name, then change `/dev/rXXXa` 
 to `/dev/rwXXXd` to access the raw disk, as in the following example:
 
@@ -31,6 +30,6 @@
 OS-selector.
 If not, recheck your device names, if that doesn't fix it, search the web for 
 the error message.
-Even though there aren't that much resources about *GRUB on NetBSD*, you'll
+Even though there aren't that many resources about *GRUB on NetBSD*, you'll
 find a lot of information at GNU/Linux-related sites which apply to this 
 scenario as well.

Moved pygrub under pvgrub and heavily discouridged the use. Also add the note that pygrub doesn't seem to actually work for Linux DomUs under NetBSD Dom0
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.167
retrieving revision 1.168
diff -u -r1.167 -r1.168
--- wikisrc/ports/xen/howto.mdwn	17 Dec 2019 20:59:09 -0000	1.167
+++ wikisrc/ports/xen/howto.mdwn	3 Apr 2020 10:48:35 -0000	1.168
@@ -657,14 +657,6 @@
 multiple vcpus, and it is typical for VPS providers to enable multiple
 CPUs for NetBSD domUs.
 
-pygrub
--------
-
-pygrub runs in the dom0 and looks into the domU file system.  This
-implies that the domU must have a kernel in a file system in a format
-known to pygrub.  As of 2014, pygrub seems to be of mostly historical
-interest.
-
 pvgrub
 ------
 
@@ -691,6 +683,21 @@
 which leads to /netbsd not being the actual kernel.  One must remember
 to update the special boot partition.
 
+pygrub
+-------
+
+pygrub runs in the dom0 and looks into the domU file system.  This
+implies that the domU must have a kernel in a file system in a format
+known to pygrub.
+
+pygrub doesn't seem to work to load Linux images under NetBSD dom0,
+and is inherently less secure than pvgrub due to running inside dom0. For both these
+reasons, pygrub should not be used, and is only still present so that
+historical DomU images using it still work.
+
+As of 2014, pygrub seems to be of mostly historical
+interest. New DomUs should use pvgrub.
+
 Amazon
 ------
 

Add minor branch info for -9
Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/releng.mdwn	2 Apr 2020 11:05:54 -0000	1.39
+++ wikisrc/releng.mdwn	2 Apr 2020 11:08:30 -0000	1.40
@@ -11,6 +11,8 @@
 ## Active Major Releases
 
 ### NetBSD 9.x
+
+* Next minor release: NetBSD 9.1 (no schedule)
   + 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)
 

Update for 8.2, remove netbsd-7 (out of support)
Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- wikisrc/releng.mdwn	14 Feb 2020 19:15:18 -0000	1.38
+++ wikisrc/releng.mdwn	2 Apr 2020 11:05:54 -0000	1.39
@@ -10,29 +10,16 @@
 
 ## Active Major Releases
 
-### NetBSD 9.0
+### NetBSD 9.x
   + 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 8.x
 
-* Next minor release: NetBSD 8.2 (planed to be released early March 2020)
+* Next minor release: NetBSD 8.3 (no schedule)
   + CVS branch tag: <code>netbsd-8</code>
 * [Current pull-up queue for the netbsd-8 branch](http://releng.netbsd.org/cgi-bin/req-8.cgi)
 
-### NetBSD 7.x
-
-* Next minor release: NetBSD 7.3 (may never happen)
-  + CVS branch tag: <code>netbsd-7</code>
-* Actively supported teeny releases:
-  + [NetBSD 7.2](http://www.netbsd.org/releases/formal-7/NetBSD-7.2.html)
-    - CVS branch has not been created yet (using <code>netbsd-7</code>)
-  + [NetBSD 7.1.2](http://www.netbsd.org/releases/formal-7/NetBSD-7.1.2.html)
-    - CVS branch tag: <code>netbsd-7-1</code>
-  + [NetBSD 7.0.2](http://www.netbsd.org/releases/formal-7/NetBSD-7.0.2.html)
-    - CVS branch tag: <code>netbsd-7-0</code>
-* [Current pull-up queue for the netbsd-7 branch](http://releng.netbsd.org/cgi-bin/req-7.cgi)
-
 ## Automated Status Information
 
 * [Daily build snapshot status](http://releng.netbsd.org/cgi-bin/builds.cgi)

formatting
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	30 Mar 2020 15:40:27 -0000	1.28
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	30 Mar 2020 15:45:00 -0000	1.29
@@ -158,6 +158,7 @@
 working correctly.
 
 Check the number of types using `ctfdump` e.g
+
     ctfdump -S /netbsd
 
 Note the line which states `total number of types`, the value should by less than 32768.

Add some notes on troubleshooting when DTrace doesn't appear to be working
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.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	21 Jul 2019 12:28:26 -0000	1.27
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	30 Mar 2020 15:40:27 -0000	1.28
@@ -151,3 +151,19 @@
 - `execsnoop` - snoop on execution of processes as they occur
 - `opensnoop` - snoop on openning of files as they occur
 - `procsystime` -  print process system call time details.
+
+## Troubleshooting
+
+The Compact C Type Format (CTF) has a 2^15 limit on types which can overflow, this prevents DTrace from
+working correctly.
+
+Check the number of types using `ctfdump` e.g
+    ctfdump -S /netbsd
+
+Note the line which states `total number of types`, the value should by less than 32768.
+
+If overflow is not an issue, `libdtrace(3)` can provide some insight into what is going on via an
+environment variable. Define `DTRACE_DEBUG` before tracing.
+
+     env DTRACE_DEBUG= execsnoop
+

mark done by ad@
Index: wikisrc/projects/project/page_queues.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/page_queues.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/page_queues.mdwn	22 Feb 2016 20:45:29 -0000	1.2
+++ wikisrc/projects/project/page_queues.mdwn	28 Mar 2020 17:42:27 -0000	1.3
@@ -14,7 +14,7 @@
 
 category="kernel"
 difficulty="hard"
-duration="2-3 months"
+done_by="Andrew Doran"
 
 description="""
 For many resource-intensive applications on NetBSD, the biggest
@@ -51,5 +51,3 @@
  new strategy is needed, e.g. perhaps a lockless radix tree.
 """
 ]]
-
-[[!tag gsoc]]

Fix typo
Index: wikisrc/projects/project/tickless.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/tickless.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/tickless.mdwn	3 Aug 2017 14:35:58 -0000	1.3
+++ wikisrc/projects/project/tickless.mdwn	19 Mar 2020 07:39:51 -0000	1.4
@@ -25,7 +25,7 @@
  10 ms resolution for sleep times; and mandatory periodic activity on
  idle machines wastes power.
 
-There are four main miletones to this project:
+There are four main milestones to this project:
 
 1. Choose a data structure for high-resolution timers, and a way to
  request high-resolution vs low-resolution sleeps, and adapt the

Fix path to user skeleton files.
From ottavio@freenode
Index: wikisrc/tutorials/the_netbsd_system_manager__39__s_manual.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/the_netbsd_system_manager__39__s_manual.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/tutorials/the_netbsd_system_manager__39__s_manual.mdwn	27 Apr 2019 20:19:32 -0000	1.1
+++ wikisrc/tutorials/the_netbsd_system_manager__39__s_manual.mdwn	16 Mar 2020 13:29:01 -0000	1.2
@@ -438,7 +438,7 @@
 
 ##  Control which files are copied to a new user's home directory during account creation 
 
-The _-k_ option of the [useradd(8)](http://netbsd.gw.com/cgi-bin/man-cgi?useradd++NetBSD-current) command can be used to specify a "skeleton directory". The contents of the specified skeleton directory will be copied to the new user's home directory. If no skeleton directory is specified with _-k_, the default of `/usr/skel/` is used. 
+The _-k_ option of the [useradd(8)](http://netbsd.gw.com/cgi-bin/man-cgi?useradd++NetBSD-current) command can be used to specify a "skeleton directory". The contents of the specified skeleton directory will be copied to the new user's home directory. If no skeleton directory is specified with _-k_, the default of `/etc/skel/` is used. 
 
 
 ##  Change a password 

Amiga International is no longer @amiga.com
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- wikisrc/ports/amiga.mdwn	13 Mar 2020 12:46:51 -0000	1.31
+++ wikisrc/ports/amiga.mdwn	13 Mar 2020 19:20:34 -0000	1.32
@@ -8,7 +8,7 @@
 thumbnail="//www.netbsd.org/images/ports/amiga/header.gif"
 about="""
 NetBSD/amiga is the port of NetBSD to the Amiga line of personal computers by
-Commodore and [Amiga International](http://www.amiga.com/) and to the DraCo by
+Commodore and [Amiga International] and to the DraCo by
 [MacroSystem GmbH](http://www.macrosystem.de/).
 
 Development activity on NetBSD/amiga continues at a speed dependent on people's

Don't let me be misunderstood.
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- wikisrc/ports/amiga.mdwn	13 Mar 2020 12:35:40 -0000	1.30
+++ wikisrc/ports/amiga.mdwn	13 Mar 2020 12:46:51 -0000	1.31
@@ -158,8 +158,7 @@
             <p><a href="#draco-zorro" class="para"><sup class="para">[6] </sup></a>The DraCo Zorro-2 bus does not recognize a couple of boards
             (known: Melody Z2, ITH ISDN Master II).  Worse: boards in
             ConfigIn/ConfigOut order behind them won't be found, either. This
-            is not a NetBSD problem, but a design problem in the board (yes,
-            right).</p>
+            is not a NetBSD problem, but a design problem in the board.</p>
           </div>
 <div id="ftn.pcmcia-ethernet" class="footnote">
             <p><a href="#pcmcia-ethernet" class="para"><sup class="para">[7] </sup></a>Due to a bug in amiga-specific PCMCIA code only NE2000-compatible

Last piece of (current) clutter.
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- wikisrc/ports/amiga.mdwn	13 Mar 2020 12:27:04 -0000	1.29
+++ wikisrc/ports/amiga.mdwn	13 Mar 2020 12:35:40 -0000	1.30
@@ -80,7 +80,7 @@
   * A2065, Hydra, ASDG LanRover, A4066, Ariadne, Quicknet Ethernet
   * AriadneII Ethernet
   * Individual Computers X-Surf / X-Surf 2 / X-Surf 3CC
-  * Individual Computers X-Surf 100 (current)
+  * Individual Computers X-Surf 100
   * PCMCIA cards in the A1200 <sup>[\[7\]](#ftn.pcmcia-ethernet)</sup><a name="pcmcia-ethernet"></a>
   * NE2000-compatible PCI cards <sup>[\[8\]](#ftn.pci-ethernet)</sup><a name="pci-ethernet"></a> 
 

Remove (current) marks for devices that appeared in -7ish or the earlier
initial wiki file version 1.1
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- wikisrc/ports/amiga.mdwn	13 Mar 2020 12:02:08 -0000	1.28
+++ wikisrc/ports/amiga.mdwn	13 Mar 2020 12:27:04 -0000	1.29
@@ -31,8 +31,8 @@
   * A4000/A1200 builtin
   * Buddha, Catweasel/Z2
   * ELBOX FastATA 1200 (Mk-III, Mk-IV)
-  * Individual Computers ACA500 CF controller (current)
-  * Individual Computers X-Surf IDE controller (current)
+  * Individual Computers ACA500 CF controller
+  * Individual Computers X-Surf IDE controller
 
 * SCSI host adapters:
   * 33c93 based boards: A2091, A3000 builtin, A3000 builtin modified for Apollo
@@ -46,11 +46,11 @@
   * Cyberstorm Mk III / Cyberstorm PPC
 
 * PCI bridges:
-  * ELBOX Mediator PCI (current): Mediator PCI 1200, Mediator PCI 1200 LT2,
+  * ELBOX Mediator PCI: Mediator PCI 1200, Mediator PCI 1200 LT2,
     Mediator PCI 1200 LT4, Mediator PCI 1200 SX, Mediator PCI 1200 TX
     Mediator PCI 4000D, Mediator PCI 3000D, Mediator 4000Di, Mediator 3/4000T
   * Phase5 PCI bridge: CyberVision PPC, BlizzardVision PPC, G-REX
-    1200 (current), G-REX 4000 (current),
+    1200, G-REX 4000
   * Prometheus PCI bridge
 
 * Clockports:
@@ -58,7 +58,7 @@
   * Generic Zorro-based clockport (currently X-Surf only)
 
 * Video controllers:
-  * 3Dfx Voodoo 3, 3Dfx Voodoo Banshee (current) <sup>[\[3\]](#ftn.voodoo-footnote)</sup><a name="voodoo-footnote"></a>
+  * 3Dfx Voodoo 3, 3Dfx Voodoo Banshee <sup>[\[3\]](#ftn.voodoo-footnote)</sup><a name="voodoo-footnote"></a>
   * A2410 <sup>[\[5\]](#ftn.no-X-retina-a2410)</sup><a name="no-X-retina-a2410"></a>
   * Cirrus CL GD 54xx based boards: GVP Spectrum, Picasso II, II+ and IV,
     Piccolo, Piccolo SD64

Remove long-past (current) and (6.0) comments.
Some (current) remain and need to be checked.
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.27
retrieving revision 1.28
diff -u -r1.27 -r1.28
--- wikisrc/ports/amiga.mdwn	13 Mar 2020 11:53:48 -0000	1.27
+++ wikisrc/ports/amiga.mdwn	13 Mar 2020 12:02:08 -0000	1.28
@@ -30,7 +30,7 @@
 * IDE controllers:
   * A4000/A1200 builtin
   * Buddha, Catweasel/Z2
-  * ELBOX FastATA 1200 (Mk-III, Mk-IV) (6.0)
+  * ELBOX FastATA 1200 (Mk-III, Mk-IV)
   * Individual Computers ACA500 CF controller (current)
   * Individual Computers X-Surf IDE controller (current)
 
@@ -39,7 +39,7 @@
     accellerator, GVP series II
   * 53c80 based boards: Hacker, 12 Gauge, IVS, Wordsync/Bytesync,
     Emplant <sup>[\[2\]](#ftn.emplant-scsi)</sup><a name="emplant-scsi"></a>
-  * 53c710 based boards: A4000T, A4091, BlizzardPPC 603e+ (6.0), Magnum, Warp
+  * 53c710 based boards: A4000T, A4091, BlizzardPPC 603e+, Magnum, Warp
     Engine, Zeus, DraCo builtin SCSI
   * FAS216 based SCSI boards: FastLane Z3, Blizzard I and II, Blizzard IV,
     Blizzard 2060, CyberSCSI Mk I and II
@@ -49,13 +49,13 @@
   * ELBOX Mediator PCI (current): Mediator PCI 1200, Mediator PCI 1200 LT2,
     Mediator PCI 1200 LT4, Mediator PCI 1200 SX, Mediator PCI 1200 TX
     Mediator PCI 4000D, Mediator PCI 3000D, Mediator 4000Di, Mediator 3/4000T
-  * Phase5 PCI bridge: CyberVision PPC (6.0), BlizzardVision PPC (6.0), G-REX
+  * Phase5 PCI bridge: CyberVision PPC, BlizzardVision PPC, G-REX
     1200 (current), G-REX 4000 (current),
-  * Prometheus PCI bridge (6.0)
+  * Prometheus PCI bridge
 
 * Clockports:
-  * Amiga 1200 on-board clockport (current)
-  * Generic Zorro-based clockport (currently X-Surf only) (current)
+  * Amiga 1200 on-board clockport
+  * Generic Zorro-based clockport (currently X-Surf only)
 
 * Video controllers:
   * 3Dfx Voodoo 3, 3Dfx Voodoo Banshee (current) <sup>[\[3\]](#ftn.voodoo-footnote)</sup><a name="voodoo-footnote"></a>
@@ -64,7 +64,7 @@
     Piccolo, Piccolo SD64
   * CyberVision 64
   * CyberVision 64/3D
-  * CyberVision PPC, BlizzardVision PPC (6.0) <sup>[\[4\]](#ftn.cvppc-footnote)</sup><a name="cvppc-footnote"></a>
+  * CyberVision PPC, BlizzardVision PPC <sup>[\[4\]](#ftn.cvppc-footnote)</sup><a name="cvppc-footnote"></a>
   * ECS, AGA and A2024 built in on various Amigas
   * Retina Z2 <sup>[\[5\]](#no-X-retina-a2410)</sup><a name="no-X-retina-a2410"></a>,
     Retina Z3, Altais
@@ -82,7 +82,7 @@
   * Individual Computers X-Surf / X-Surf 2 / X-Surf 3CC
   * Individual Computers X-Surf 100 (current)
   * PCMCIA cards in the A1200 <sup>[\[7\]](#ftn.pcmcia-ethernet)</sup><a name="pcmcia-ethernet"></a>
-  * NE2000-compatible PCI cards <sup>[\[8\]](#ftn.pci-ethernet)</sup><a name="pci-ethernet"></a> (6.0)
+  * NE2000-compatible PCI cards <sup>[\[8\]](#ftn.pci-ethernet)</sup><a name="pci-ethernet"></a> 
 
 * ARCnet controllers:
   * A2060 ARCnet
@@ -114,7 +114,7 @@
   * MultiFaceCard II and III
   * HyperCom Z3 (serial only), HyperCom 4, 3+ and 4+ (not the A1200 clockport
     models!)
-  * Individual Computers SilverSurfer (current)
+  * Individual Computers SilverSurfer
 
 * Parallel printer ports on these boards:
   * Amiga builtin

more pcmcia doc
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- wikisrc/ports/amiga.mdwn	13 Mar 2020 11:10:49 -0000	1.26
+++ wikisrc/ports/amiga.mdwn	13 Mar 2020 11:53:48 -0000	1.27
@@ -81,7 +81,7 @@
   * AriadneII Ethernet
   * Individual Computers X-Surf / X-Surf 2 / X-Surf 3CC
   * Individual Computers X-Surf 100 (current)
-  * Some PCMCIA cards in the A1200 (tested with a few network cards only) <sup>[\[7\]](#ftn.pcmcia-ethernet)</sup><a name="pcmcia-ethernet"></a>
+  * PCMCIA cards in the A1200 <sup>[\[7\]](#ftn.pcmcia-ethernet)</sup><a name="pcmcia-ethernet"></a>
   * NE2000-compatible PCI cards <sup>[\[8\]](#ftn.pci-ethernet)</sup><a name="pci-ethernet"></a> (6.0)
 
 * ARCnet controllers:
@@ -162,7 +162,7 @@
             right).</p>
           </div>
 <div id="ftn.pcmcia-ethernet" class="footnote">
-            <p><a href="#pcmcia-ethernet" class="para"><sup class="para">[7] </sup></a>Due to bugs in amiga-specific PCMCIA code only NE2000-compatible
+            <p><a href="#pcmcia-ethernet" class="para"><sup class="para">[7] </sup></a>Due to a bug in amiga-specific PCMCIA code only NE2000-compatible
 	    cards are expected to work on NetBSD-9.0/NetBSD-8.1 and earlier.</p>
 	    </div>
 <div id="ftn.pci-ethernet" class="footnote">

RIP, King Lear.
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.25
retrieving revision 1.26
diff -u -r1.25 -r1.26
--- wikisrc/ports/amiga.mdwn	13 Mar 2020 11:03:57 -0000	1.25
+++ wikisrc/ports/amiga.mdwn	13 Mar 2020 11:10:49 -0000	1.26
@@ -148,7 +148,7 @@
             </div>
 <div id="ftn.cvppc-footnote" class="footnote">
               <p><a href="#cvppc-footnote" class="para"><sup class="para">[4] </sup></a>CVPPC/BVPPC cards are only supported with wscons and only
-	      with unaccelearted genfb driver. X server is not supported on
+	      with unaccelerated genfb driver. X server is not supported on
 	      these cards yet.</p>
 	    </div>
 <div id="ftn.no-X-retina-a2410" class="footnote">

Note fixed pcmcia 16bit code on A1200.
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- wikisrc/ports/amiga.mdwn	15 Feb 2020 08:00:05 -0000	1.24
+++ wikisrc/ports/amiga.mdwn	13 Mar 2020 11:03:57 -0000	1.25
@@ -163,7 +163,7 @@
           </div>
 <div id="ftn.pcmcia-ethernet" class="footnote">
             <p><a href="#pcmcia-ethernet" class="para"><sup class="para">[7] </sup></a>Due to bugs in amiga-specific PCMCIA code only NE2000-compatible
-	    cards are expected to work.</p>
+	    cards are expected to work on NetBSD-9.0/NetBSD-8.1 and earlier.</p>
 	    </div>
 <div id="ftn.pci-ethernet" class="footnote">
             <p><a href="#pci-ethernet" class="para"><sup class="para">[8] </sup></a>PCI network cards are supported only when installed in a

Try to more explicitly says that's for NetBSD 8.0
XXX: Needs to be updated for NetBSD 9.0!
Members: 
	ports/evbarm/install_using_sysinst.mdwn:1.18->1.19 

Index: wikisrc/ports/evbarm/install_using_sysinst.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/install_using_sysinst.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/ports/evbarm/install_using_sysinst.mdwn	20 Nov 2018 12:54:50 -0000	1.18
+++ wikisrc/ports/evbarm/install_using_sysinst.mdwn	10 Mar 2020 22:22:10 -0000	1.19
@@ -1,6 +1,6 @@
-[[!meta title="NetBSD/evbarm install via sysinst(8) on a SATA hard disk, USB stick or (u)SD card"]]
+[[!meta title="NetBSD/evbarm 8.0 install via sysinst(8) on a SATA hard disk, USB stick or (u)SD card"]]
 
-In this document we will see step by step how to install NetBSD/evbarm on an
+In this document we will see step by step how to install NetBSD/evbarm 8.0 on an
 external media (SATA hard disk, USB stick or (u)SD card) using
 [[!template id=man name="sysinst" section="8"]].
 

Remove AsiaBSDCon 2020, unfortunately it was canceled.
Directly quoting the ABC web site:
> Due to increasing risk of the coronavirus disease (COVID-19) in Japan,
> the organizing team of AsiaBSDCon 2020 has decided to cancel the
> conference which was originally planned on 19-22 March, 2020.
>
> We are sorry for any inconvenience this will cause you. For
> registration fees, we will accept cancel requests and 50% refund.
> Please contact asiabsd2020@gmt.jtb.jp with your registration number.
> Due to increasing risk of the coronavirus disease (COVID-19) in Japan,
> the organizing team of AsiaBSDCon 2020 has decided to cancel the
> conference which was originally planned on 19-22 March, 2020.
>
> We are sorry for any inconvenience this will cause you. For
> registration fees, we will accept cancel requests and 50% refund.
> Please contact asiabsd2020@gmt.jtb.jp with your registration number.

Members: 
	events.mdwn:1.86->1.87 

Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -r1.86 -r1.87
--- wikisrc/events.mdwn	6 Feb 2020 20:28:36 -0000	1.86
+++ wikisrc/events.mdwn	3 Mar 2020 16:05:45 -0000	1.87
@@ -12,20 +12,6 @@
 
 Future Events
 -------------
-### `Mar 2020` - AsiaBSDCon 2020, Tokyo, Japan
-
-*March 19 - 22, Tokyo University of Science, Tokyo, Japan*
-
-[AsiaBSDCon](https://www.asiabsdcon.org/) is a
-conference for users and developers on BSD based systems.
-The conference is for anyone developing, deploying and using systems
-based on FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Darwin, and MacOS X.
-AsiaBSDCon is a technical conference and aims to collect the best
-technical papers and presentations available to ensure that the latest
-developments in our open source community are shared with the widest
-possible audience.
-
-
 ### `Jun 2020` - BSDCan 2020, Ottawa, Canada
 
 *June 3 - 6, 2020, University of Ottawa, Ottawa, Canada*

zfs: add NFS PR link
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- wikisrc/zfs.mdwn	2 Mar 2020 17:30:07 -0000	1.24
+++ wikisrc/zfs.mdwn	2 Mar 2020 20:50:56 -0000	1.25
@@ -155,7 +155,7 @@
 print information that can be added to exports(5).
 
 This is reported to work on 9.0 STABLE, but to cause a panic on
-current (20200302).
+current (20200302).  See [misc/55042](http://gnats.netbsd.org/55042).
 
 ## zvol
 

zfs: formatting
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- wikisrc/zfs.mdwn	2 Mar 2020 17:28:14 -0000	1.23
+++ wikisrc/zfs.mdwn	2 Mar 2020 17:30:07 -0000	1.24
@@ -17,7 +17,7 @@
   - [FreeBSD Handbook ZFS Chapter](https://www.freebsd.org/doc/handbook/zfs.html)
   - [OpenZFS admin docs index page](https://github.com/openzfs/zfs/wiki/Admin-Documentation)
 
-  - https://en.wikipedia.org/wiki/ZFS
+  - [Wikipedia](https://en.wikipedia.org/wiki/ZFS)
 
 # Status of ZFS in NetBSD
 

zfs: Explain code lineage better
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/zfs.mdwn	2 Mar 2020 17:21:18 -0000	1.22
+++ wikisrc/zfs.mdwn	2 Mar 2020 17:28:14 -0000	1.23
@@ -35,11 +35,24 @@
 
 OpenZFS is a coordinating project to align open ZFS codebases.  There
 is a notion of a shared core codebase and OS-specific adaptation code.
+As of early 2020, it appears that there are two co-root repositories:
+illumos and zfsonlinux, with a notion that fixes and improvements
+should be cross-shared.  This is different from the situation through
+late 2019 where sharing was done via a designated sharing repository,
+and appears to be a new, more efficient, procedure among cooperating
+people, rather than any kind of fork.
 
+  - [deprecation of OpenZFS repo](https://github.com/openzfs/openzfs/)
   - [zfsonlinux relationship to OpenZFS](https://github.com/openzfs/zfs/wiki/OpenZFS-Patches)
 
-\todo Explain clearly the relationship between OpenZFS and zfsonlinux,
-and also the Illumos and OSX versions.
+\todo Explain how FreeBSD code relates to zfsonlinux (imported/merged and fixes pushed upstream?).
+
+\todo Explain how the NetBSD code relates (imported from FreeBSD? intent to continue to track?)
+
+\todo Explain if NetBSD has a plan to join zfsonlinux as a first-class
+member, vs tracking via FreeBSD.
+
+\todo Explain how OpenZFS on OS X relates (tracks zfsonlinux?).
 
 See [FreeBSD's history](https://wiki.freebsd.org/ZFSTuningGuide).
 

zfs: Add zfsonlinux tracking plan
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/zfs.mdwn	2 Mar 2020 17:17:59 -0000	1.21
+++ wikisrc/zfs.mdwn	2 Mar 2020 17:21:18 -0000	1.22
@@ -36,6 +36,8 @@
 OpenZFS is a coordinating project to align open ZFS codebases.  There
 is a notion of a shared core codebase and OS-specific adaptation code.
 
+  - [zfsonlinux relationship to OpenZFS](https://github.com/openzfs/zfs/wiki/OpenZFS-Patches)
+
 \todo Explain clearly the relationship between OpenZFS and zfsonlinux,
 and also the Illumos and OSX versions.
 
@@ -45,10 +47,10 @@
 
 \todo This section really needs help.
 
-Before NetBSD 8, NetBSD imported ZFS code from ?
+Before NetBSD 8, NetBSD imported ZFS code from ?, which was version ?
 
 Before NetBSD 9, NetBSD imported updated ZFS code from FreeBSD.  That
-FreeBSD code came from ?
+FreeBSD code came from ?, which was version ?
 
 ## NetBSD 8 and earlier
 

zfs: Improve doc pointers
Inspired by a suggestion from Jason Mitchell
Members: 
	zfs.mdwn:1.20->1.21 

Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/zfs.mdwn	2 Mar 2020 15:22:43 -0000	1.20
+++ wikisrc/zfs.mdwn	2 Mar 2020 17:17:59 -0000	1.21
@@ -17,25 +17,29 @@
   - [FreeBSD Handbook ZFS Chapter](https://www.freebsd.org/doc/handbook/zfs.html)
   - [OpenZFS admin docs index page](https://github.com/openzfs/zfs/wiki/Admin-Documentation)
 
+  - https://en.wikipedia.org/wiki/ZFS
+
 # Status of ZFS in NetBSD
 
-## Sources
+## Sources of ZFS code
 
 \todo Verify/fix.
 
-Currently, there are multiple ZFS projects/codebases:
+Currently, there are multiple ZFS projects and codebases:
 
   - ZFS as released under the CDDL (common ancestor)
-  - [OpenZFS](http://www.open-zfs.org/wiki/Main_Page)
+  - [OpenZFS](http://www.open-zfs.org/wiki/Main_Page) [github wiki](https://github.com/openzfs/zfs/wiki)
   - [zfsonlinux](https://zfsonlinux.org/)
+  - [OpenZFS on OS X ](https://openzfsonosx.org/) [repo](https://github.com/openzfsonosx)
   - proprietary ZFS in Solaris (not relevant in open source)
 
 OpenZFS is a coordinating project to align open ZFS codebases.  There
 is a notion of a shared core codebase and OS-specific adaptation code.
 
-See [FreeBSD's history](https://wiki.freebsd.org/ZFSTuningGuide).
+\todo Explain clearly the relationship between OpenZFS and zfsonlinux,
+and also the Illumos and OSX versions.
 
-\todo Explain the relationship between OpenZFS and zfsonlinux.
+See [FreeBSD's history](https://wiki.freebsd.org/ZFSTuningGuide).
 
 ## NetBSD code history
 

zfs: nfs on current is broken
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- wikisrc/zfs.mdwn	2 Mar 2020 15:20:44 -0000	1.19
+++ wikisrc/zfs.mdwn	2 Mar 2020 15:22:43 -0000	1.20
@@ -135,6 +135,9 @@
 commands that appear to be about controlling exports, they simply
 print information that can be added to exports(5).
 
+This is reported to work on 9.0 STABLE, but to cause a panic on
+current (20200302).
+
 ## zvol
 
 Within a ZFS pool, the standard approach is to have file systems, but

zfs: explain nfs
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/zfs.mdwn	2 Mar 2020 00:58:14 -0000	1.18
+++ wikisrc/zfs.mdwn	2 Mar 2020 15:20:44 -0000	1.19
@@ -127,6 +127,14 @@
 NetBSD current after 20200301 mounts ZFS first. \todo Explain
 consequences.
 
+## NFS
+
+\todo Verify if this is accurate.
+
+zfs filesystems can be exported over NFS.  While there are zfs
+commands that appear to be about controlling exports, they simply
+print information that can be added to exports(5).
+
 ## zvol
 
 Within a ZFS pool, the standard approach is to have file systems, but

AsiaBSDCon2020 cancelled
Index: wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn	9 Feb 2020 12:39:27 -0000	1.4
+++ wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn	2 Mar 2020 05:07:45 -0000	1.5
@@ -3,8 +3,22 @@
 [[!meta title="AsiaBSDCon 2020 NetBSD BoF"]]
 
 
-# NetBSD BoF 2020
+# NetBSD BoF 2020 (Canceled)
 ------------------------------------------------------
+*  Due to increasing risk of the coronavirus disease (COVID-19) in
+ Japan, the organizing team of AsiaBSDCon 2020 has decided to cancel
+ the conference which was originally planned on 19-22 March, 2020.
+
+ While we estimated the impact was limited, according to the
+ statistics it is expected that the number of patients in Japan will
+ increase in the period from March 1st to March 15th, and the Japanese
+ government has issued an emergency alert nationwide since the last
+ weekend.  Following this, some companies forbid attending events in
+ Japan and some of major airlines started to cancel international
+ flights to/from Japan.  Although our conference days are in
+ 19th-22nd, it is unclear that how long will it take until getting
+ back to normal after that period.
+
 * Let's run a NetBSD BoF on [AsiaBSDCon2020](https://2020.asiabsdcon.org/index.html.en).
 * [announce on netbsd-advocacy](http://mail-index.netbsd.org/netbsd-advocacy/2020/02/06/msg000824.html)
 * All BSD speakers are welcome (No AsiaBSDCon registration is required).

zfs: minor improvements
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/zfs.mdwn	2 Mar 2020 00:52:14 -0000	1.17
+++ wikisrc/zfs.mdwn	2 Mar 2020 00:58:14 -0000	1.18
@@ -166,12 +166,12 @@
 is cleanly enough.
 
 For now, a good guess is that a 4G system with only 1T of disk is
-probably ok, 1G is very likely not ok.
+probably ok, and that 1G is very likely not ok.
 
 FreeBSD has some documentation about memory use.  There is a notion of
-a minimum of 1G, and using 1G for 1T of storage, and more if
-deduplication is enabled.  FreeBSD considers all i386 systems to be
-low memory; this appears to be a clue.
+a minimum of 1G (used for ZFS), and using 1G for 1T of storage, and
+more if deduplication is enabled.  FreeBSD considers all i386 systems
+to be low memory; this appears to be a clue.
 
 \todo Explain if the FreeBSD sysctl list applies, or if not what we
 should do instead.
@@ -183,6 +183,9 @@
 \todo Explain pool version and feature flags relationship to FreeBSD,
 Linux, OpenIndiana/Illumos/?, and ?
 
+\todo Explain how to configure a pool in terms of version/features for
+use with particula other systems.
+
 # Quick Start
 
 See the [FreeBSD Quickstart

zfs: Finish sentence.
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/zfs.mdwn	2 Mar 2020 00:44:23 -0000	1.16
+++ wikisrc/zfs.mdwn	2 Mar 2020 00:52:14 -0000	1.17
@@ -195,5 +195,4 @@
 
   - df and see /pool1
 
-  - Really, read the FreeBSD docs and the 
-
+  - Really, read the FreeBSD docs and the other linked documentation above.

zfs: formatting
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/zfs.mdwn	2 Mar 2020 00:43:05 -0000	1.15
+++ wikisrc/zfs.mdwn	2 Mar 2020 00:44:23 -0000	1.16
@@ -33,7 +33,7 @@
 OpenZFS is a coordinating project to align open ZFS codebases.  There
 is a notion of a shared core codebase and OS-specific adaptation code.
 
-See [FreeBSD's history](https://wiki.freebsd.org/ZFSTuningGuide)
+See [FreeBSD's history](https://wiki.freebsd.org/ZFSTuningGuide).
 
 \todo Explain the relationship between OpenZFS and zfsonlinux.
 
@@ -79,7 +79,7 @@
 
 One can make a ccd using a zvol as a component.  See the zvol section below.
 
-## things that aren't supported yet
+## Things that aren't supported yet
 
 \todo hotswap (maybe - not clear exactly what this means)
 

zfs: ask for openzfs/zfsonlinux unconfusion
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/zfs.mdwn	2 Mar 2020 00:41:17 -0000	1.14
+++ wikisrc/zfs.mdwn	2 Mar 2020 00:43:05 -0000	1.15
@@ -35,6 +35,8 @@
 
 See [FreeBSD's history](https://wiki.freebsd.org/ZFSTuningGuide)
 
+\todo Explain the relationship between OpenZFS and zfsonlinux.
+
 ## NetBSD code history
 
 \todo This section really needs help.

zfs: Add quick start and discuss pools/zvols
Explain the types of disks/partitions one can add to a pool.
Explain zvols briefly.
Give the briefest of quickstart and tell people again to read the
FreeBSD quickstart.
Explain zvols briefly.

Give the briefest of quickstart and tell people again to read the
FreeBSD quickstart.

Members: 
	zfs.mdwn:1.13->1.14 

Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/zfs.mdwn	2 Mar 2020 00:16:06 -0000	1.13
+++ wikisrc/zfs.mdwn	2 Mar 2020 00:41:17 -0000	1.14
@@ -15,6 +15,7 @@
 
   - [Oracle ZFS Administration Manual](https://docs.oracle.com/cd/E26505_01/html/E37384/index.html)
   - [FreeBSD Handbook ZFS Chapter](https://www.freebsd.org/doc/handbook/zfs.html)
+  - [OpenZFS admin docs index page](https://github.com/openzfs/zfs/wiki/Admin-Documentation)
 
 # Status of ZFS in NetBSD
 
@@ -32,6 +33,8 @@
 OpenZFS is a coordinating project to align open ZFS codebases.  There
 is a notion of a shared core codebase and OS-specific adaptation code.
 
+See [FreeBSD's history](https://wiki.freebsd.org/ZFSTuningGuide)
+
 ## NetBSD code history
 
 \todo This section really needs help.
@@ -72,9 +75,7 @@
 There is initial support for [[ZFS root|wiki/RootOnZFS]], via booting from
 ffs and pivoting.
 
-One can make a ccd using a zvol as a component.  This allows reading a
-GPT label from the zvol, which is useful in case the zvol had been
-exported via iscsi and some other system created a label.
+One can make a ccd using a zvol as a component.  See the zvol section below.
 
 ## things that aren't supported yet
 
@@ -100,6 +101,15 @@
 The main configuration is to put zfs=YES in rc.conf, so that the rc.d
 scripts bring up ZFS and mount ZFS file systems.
 
+## pool locations
+
+One can add disks or parts of disks into pools.  Methods of specifying
+areas to be included include:
+
+  - entire disks (e.g., /dev/rwd0d on amd64)
+  - disklabel partitions (e.g., /dev/sd0e)
+  - wedges (e.g., /dev/dk0)
+
 ## legacy vs ? mount points
 
 \todo Explain, if this is NetBSD specific.  Explain consequences, as
@@ -115,6 +125,25 @@
 NetBSD current after 20200301 mounts ZFS first. \todo Explain
 consequences.
 
+## zvol
+
+Within a ZFS pool, the standard approach is to have file systems, but
+one can also create a zvol, which is a block device of a certain size.
+
+\todo The zvol will appear as /dev/???? and can be used in many
+respects like a slice.  However, the system will not read disklabels
+and gpt labels from a zvol; in this respect it is more like a disklabel
+partition or wedge than a disk drive.
+
+\todo Explain that one can export a zvol via iscsi.
+
+\todo Explain if one can swap on a zvol.
+
+\todo Explain that one can use ccd to create a normal-looking disk
+from a zvol.  This allows reading a GPT label from the zvol, which is
+useful in case the zvol had been exported via iscsi and some other
+system created a label.
+
 ## TRIM
 
 There is some notion of TRIM and zfs using it.
@@ -152,4 +181,17 @@
 \todo Explain pool version and feature flags relationship to FreeBSD,
 Linux, OpenIndiana/Illumos/?, and ?
 
+# Quick Start
+
+See the [FreeBSD Quickstart
+Guide](https://www.freebsd.org/doc/handbook/zfs-quickstart.html); only
+the first item is NetBSD specific.
+
+  - Put zfs=YES in rc.conf.
+
+  - Create a pool as "zpool create pool1 /dev/dk0".
+
+  - df and see /pool1
+
+  - Really, read the FreeBSD docs and the 
 

Fix some typos, split some words.
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/zfs.mdwn	2 Mar 2020 00:09:25 -0000	1.12
+++ wikisrc/zfs.mdwn	2 Mar 2020 00:16:06 -0000	1.13
@@ -1,7 +1,7 @@
 # ZFS on NetBSD
 
 This page attempts to do two things: provide enough orientation and
-pointers to dstandard ZFS documentation for NetBSD users who are new to
+pointers to standard ZFS documentation for NetBSD users who are new to
 ZFS, and to describe NetBSD-specific ZFS information.  It is
 emphatically not a tutorial or an introduction to ZFS.
 
@@ -48,7 +48,7 @@
 unlikely that anyone is interested in helping, other than telling you
 to upgrade to 9.
 
-(Reports of how well NetBDS 8 works are welcome on netbsd-users, if it
+(Reports of how well NetBSD 8 works are welcome on netbsd-users, if it
 can actually be recommended for use.)
 
 ## NetBSD 9
@@ -76,11 +76,11 @@
 GPT label from the zvol, which is useful in case the zvol had been
 exported via iscsi and some other system created a label.
 
-## things that aren't suported yet
+## things that aren't supported yet
 
 \todo hotswap (maybe - not clear exactly what this means)
 
-\todo direct boot into zfs root (via bootblocks reading zfs)
+\todo direct boot into zfs root (via boot blocks reading zfs)
 
 ## Architectures
 
@@ -98,7 +98,7 @@
 ## rc.conf
 
 The main configuration is to put zfs=YES in rc.conf, so that the rc.d
-scripts bring up ZFS and mount ZFS filesystems.
+scripts bring up ZFS and mount ZFS file systems.
 
 ## legacy vs ? mount points
 
@@ -107,7 +107,7 @@
 
 ## mount order
 
-NetBSD 9 mounts other filesystems and then ZFS filesystems.  This can
+NetBSD 9 mounts other file systems and then ZFS file systems.  This can
 be a problem if /usr/pkgsrc is on ZFS and /usr/pkgsrc/distfiles is on
 NFS.  A workaround is to use noauto and do the mounts in
 /etc/rc.local.

zfs: improve code heritage section
Thanks to prlw1@ for hints, but mistakes are still my fault.
Members: 
	zfs.mdwn:1.11->1.12 

Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/zfs.mdwn	1 Mar 2020 23:54:13 -0000	1.11
+++ wikisrc/zfs.mdwn	2 Mar 2020 00:09:25 -0000	1.12
@@ -18,7 +18,28 @@
 
 # Status of ZFS in NetBSD
 
-NetBSD has imported OpenZFS.  \todo versions, links
+## Sources
+
+\todo Verify/fix.
+
+Currently, there are multiple ZFS projects/codebases:
+
+  - ZFS as released under the CDDL (common ancestor)
+  - [OpenZFS](http://www.open-zfs.org/wiki/Main_Page)
+  - [zfsonlinux](https://zfsonlinux.org/)
+  - proprietary ZFS in Solaris (not relevant in open source)
+
+OpenZFS is a coordinating project to align open ZFS codebases.  There
+is a notion of a shared core codebase and OS-specific adaptation code.
+
+## NetBSD code history
+
+\todo This section really needs help.
+
+Before NetBSD 8, NetBSD imported ZFS code from ?
+
+Before NetBSD 9, NetBSD imported updated ZFS code from FreeBSD.  That
+FreeBSD code came from ?
 
 ## NetBSD 8 and earlier
 
@@ -33,9 +54,10 @@
 ## NetBSD 9
 
 There have been fixes since 9.0 RELEASE.  It is best to upgrade along
-the netbsd-9 branch, but the release should be ok.
+the netbsd-9 branch, but the release should be ok.  Most aspects work solidly.
 
-\todo This is OpenZFS as of X.   Most aspects work solidly.
+\todo Explain this in terms of versions of FreeBSD OpenZFS and/or
+zfsonlinux.
 
 \todo This supports pool version 28/5000 (really true?).  Of the
 feature flags found in modern OpenZFS, \todo are supported.

zfs: typos (thanks prlw1)
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/zfs.mdwn	1 Mar 2020 16:34:38 -0000	1.10
+++ wikisrc/zfs.mdwn	1 Mar 2020 23:54:13 -0000	1.11
@@ -1,8 +1,8 @@
 # ZFS on NetBSD
 
-This page attempts to do two things: provide enough orientatino and
-pointers to standard ZFS documentation for NetBSD users who are new to
-ZFS, and to to describe NetBSD-specific ZFS information.  It is
+This page attempts to do two things: provide enough orientation and
+pointers to dstandard ZFS documentation for NetBSD users who are new to
+ZFS, and to describe NetBSD-specific ZFS information.  It is
 emphatically not a tutorial or an introduction to ZFS.
 
 Many things are marked with \todo because they need a better
@@ -106,7 +106,7 @@
 comparatively small amounts of memory.  So a natural question is how
 well ZFS works on one's VAX with 2M of RAM :-)
 
-More seriously, one might ask if is reasonable to run ZFS on a RPI3
+More seriously, one might ask if it is reasonable to run ZFS on a RPI3
 with 1G of RAM, or even if it is reasonable on a system with 4G.
 
 \todo Give ballpark level for minimum sane RAM, and the amount which

update with link to austin group proposal (and accepted proposal status)
Index: wikisrc/projects/project/posix__95__spawn__40__3__41___chdir_support.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/posix__95__spawn__40__3__41___chdir_support.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/posix__95__spawn__40__3__41___chdir_support.mdwn	24 Jan 2019 18:54:38 -0000	1.1
+++ wikisrc/projects/project/posix__95__spawn__40__3__41___chdir_support.mdwn	1 Mar 2020 18:32:01 -0000	1.2
@@ -14,13 +14,13 @@
 difficulty="easy"
 
 description="""
-The Austin Group is currently discussing to extend the standard for posix_spawn(3)
+The Austin Group has accepted a proposal to extend the standard for posix_spawn(3)
 to support chdir(2) functionality in the new created process.
 This is useful and relatively easy to implement.
 
 This project is about adding the full functionality as described in the Austin Groups
-ticket tracker, which means both kernel extensions as well as associated changes to
-the C library.
+[ticket tracker](https://www.austingroupbugs.net/view.php?id=1208),
+which means both kernel extensions as well as associated changes to the C library.
 """
 ]]
 

edit test
Index: wikisrc/users/spz.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/users/spz.mdwn	23 Dec 2018 11:46:59 -0000	1.21
+++ wikisrc/users/spz.mdwn	1 Mar 2020 16:55:27 -0000	1.22
@@ -4,8 +4,6 @@
 
 *[[uefi+gpt+raidframe|spz/moderndisk]]
 
-*[[Tax evasion|spz/projects]]
-
 *[[sandbox|spz/sandbox]]
 
 *[[(old) Security Reference List|spz/secref2]]

zfs: memory requirements guess
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/zfs.mdwn	1 Mar 2020 16:29:48 -0000	1.9
+++ wikisrc/zfs.mdwn	1 Mar 2020 16:34:38 -0000	1.10
@@ -112,6 +112,9 @@
 \todo Give ballpark level for minimum sane RAM, and the amount which
 is cleanly enough.
 
+For now, a good guess is that a 4G system with only 1T of disk is
+probably ok, 1G is very likely not ok.
+
 FreeBSD has some documentation about memory use.  There is a notion of
 a minimum of 1G, and using 1G for 1T of storage, and more if
 deduplication is enabled.  FreeBSD considers all i386 systems to be

zfs: fix linkn
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/zfs.mdwn	1 Mar 2020 16:28:10 -0000	1.8
+++ wikisrc/zfs.mdwn	1 Mar 2020 16:29:48 -0000	1.9
@@ -47,7 +47,7 @@
 
 The ZFS code in current is very similar to that in 9.
 
-There is initial support for [[ZFS root|RootOnZFS]], via booting from
+There is initial support for [[ZFS root|wiki/RootOnZFS]], via booting from
 ffs and pivoting.
 
 One can make a ccd using a zvol as a component.  This allows reading a

zfs: markup
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/zfs.mdwn	1 Mar 2020 16:25:44 -0000	1.7
+++ wikisrc/zfs.mdwn	1 Mar 2020 16:28:10 -0000	1.8
@@ -56,9 +56,9 @@
 
 ## things that aren't suported yet
 
-\todo (?) hotswap
+\todo hotswap (maybe - not clear exactly what this means)
 
-\todo (?) direct boot into zfs root
+\todo direct boot into zfs root (via bootblocks reading zfs)
 
 ## Architectures
 

zfs: typos
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/zfs.mdwn	1 Mar 2020 16:23:46 -0000	1.6
+++ wikisrc/zfs.mdwn	1 Mar 2020 16:25:44 -0000	1.7
@@ -40,14 +40,14 @@
 \todo This supports pool version 28/5000 (really true?).  Of the
 feature flags found in modern OpenZFS, \todo are supported.
 
-Generlly, fixes to ZFS in current will be pulled up to 9, but new
+Generally, fixes to ZFS in current will be pulled up to 9, but new
 features typically will not be.
 
 ## NetBSD current
 
 The ZFS code in current is very similar to that in 9.
 
-There is initial support for [[RootOnZFS|ZFS root]], via booting from
+There is initial support for [[ZFS root|RootOnZFS]], via booting from
 ffs and pivoting.
 
 One can make a ccd using a zvol as a component.  This allows reading a
@@ -120,7 +120,7 @@
 \todo Explain if the FreeBSD sysctl list applies, or if not what we
 should do instead.
 
-[FreeBSD low memory documentation](https://www.freebsd.org/doc/handbook/zfs-advanced.html)
+  - [FreeBSD low memory documentation](https://www.freebsd.org/doc/handbook/zfs-advanced.html)
 
 # Interoperability with other systems
 

zfs: add note about legacy mountpoints
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/zfs.mdwn	1 Mar 2020 16:22:13 -0000	1.5
+++ wikisrc/zfs.mdwn	1 Mar 2020 16:23:46 -0000	1.6
@@ -78,6 +78,11 @@
 The main configuration is to put zfs=YES in rc.conf, so that the rc.d
 scripts bring up ZFS and mount ZFS filesystems.
 
+## legacy vs ? mount points
+
+\todo Explain, if this is NetBSD specific.  Explain consequences, as
+this seems to have something to do with mount ordering.
+
 ## mount order
 
 NetBSD 9 mounts other filesystems and then ZFS filesystems.  This can

zfs: point to RootOnZFS
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/zfs.mdwn	1 Mar 2020 16:15:29 -0000	1.4
+++ wikisrc/zfs.mdwn	1 Mar 2020 16:22:13 -0000	1.5
@@ -40,9 +40,15 @@
 \todo This supports pool version 28/5000 (really true?).  Of the
 feature flags found in modern OpenZFS, \todo are supported.
 
+Generlly, fixes to ZFS in current will be pulled up to 9, but new
+features typically will not be.
+
 ## NetBSD current
 
-There is initial support for ZFS root, via booting from ffs and pivoting.
+The ZFS code in current is very similar to that in 9.
+
+There is initial support for [[RootOnZFS|ZFS root]], via booting from
+ffs and pivoting.
 
 One can make a ccd using a zvol as a component.  This allows reading a
 GPT label from the zvol, which is useful in case the zvol had been

zfs: formatting
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/zfs.mdwn	1 Mar 2020 16:14:54 -0000	1.3
+++ wikisrc/zfs.mdwn	1 Mar 2020 16:15:29 -0000	1.4
@@ -13,8 +13,8 @@
 
 See the man pages for zfs(8) and zpool(8).
 
-[Oracle ZFS Administration Manual](https://docs.oracle.com/cd/E26505_01/html/E37384/index.html)
-[FreeBSD Handbook ZFS Chapter](https://www.freebsd.org/doc/handbook/zfs.html)
+  - [Oracle ZFS Administration Manual](https://docs.oracle.com/cd/E26505_01/html/E37384/index.html)
+  - [FreeBSD Handbook ZFS Chapter](https://www.freebsd.org/doc/handbook/zfs.html)
 
 # Status of ZFS in NetBSD
 

zfs: Note that current mounts zfs first
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/zfs.mdwn	1 Mar 2020 16:13:20 -0000	1.2
+++ wikisrc/zfs.mdwn	1 Mar 2020 16:14:54 -0000	1.3
@@ -74,9 +74,13 @@
 
 ## mount order
 
-NetBSD mounts other filesystems and then ZFS filesystems.  This can be
-a problem if /usr/pkgsrc is on ZFS and /usr/pkgsrc/distfiles is on
-NFS.  A workaround is to use noauto and do the mounts in /etc/rc.local.
+NetBSD 9 mounts other filesystems and then ZFS filesystems.  This can
+be a problem if /usr/pkgsrc is on ZFS and /usr/pkgsrc/distfiles is on
+NFS.  A workaround is to use noauto and do the mounts in
+/etc/rc.local.
+
+NetBSD current after 20200301 mounts ZFS first. \todo Explain
+consequences.
 
 ## TRIM
 

zfs: markdownify links
Index: wikisrc/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/zfs.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/zfs.mdwn	1 Mar 2020 16:04:52 -0000	1.1
+++ wikisrc/zfs.mdwn	1 Mar 2020 16:13:20 -0000	1.2
@@ -13,8 +13,8 @@
 
 See the man pages for zfs(8) and zpool(8).
 
-https://docs.oracle.com/cd/E26505_01/html/E37384/index.html
-https://www.freebsd.org/doc/handbook/zfs.html
+[Oracle ZFS Administration Manual](https://docs.oracle.com/cd/E26505_01/html/E37384/index.html)
+[FreeBSD Handbook ZFS Chapter](https://www.freebsd.org/doc/handbook/zfs.html)
 
 # Status of ZFS in NetBSD
 
@@ -97,10 +97,15 @@
 \todo Give ballpark level for minimum sane RAM, and the amount which
 is cleanly enough.
 
-FreeBSD has some documentation about memory use.  \todo Explain if
-this applies, or if not what we should do instead.
+FreeBSD has some documentation about memory use.  There is a notion of
+a minimum of 1G, and using 1G for 1T of storage, and more if
+deduplication is enabled.  FreeBSD considers all i386 systems to be
+low memory; this appears to be a clue.
 
-https://www.freebsd.org/doc/handbook/zfs-advanced.html
+\todo Explain if the FreeBSD sysctl list applies, or if not what we
+should do instead.
+
+[FreeBSD low memory documentation](https://www.freebsd.org/doc/handbook/zfs-advanced.html)
 
 # Interoperability with other systems
 

zfs: initial very rough draft
--- /dev/null	2020-03-01 16:05:05.298082624 +0000
+++ wikisrc/zfs.mdwn	2020-03-01 16:05:45.004807887 +0000
@@ -0,0 +1,110 @@
+# ZFS on NetBSD
+
+This page attempts to do two things: provide enough orientatino and
+pointers to standard ZFS documentation for NetBSD users who are new to
+ZFS, and to to describe NetBSD-specific ZFS information.  It is
+emphatically not a tutorial or an introduction to ZFS.
+
+Many things are marked with \todo because they need a better
+explanation, and some have question marks, indicating that the
+statement needs verification.
+
+# Documentation Pointers
+
+See the man pages for zfs(8) and zpool(8).
+
+https://docs.oracle.com/cd/E26505_01/html/E37384/index.html
+https://www.freebsd.org/doc/handbook/zfs.html
+
+# Status of ZFS in NetBSD
+
+NetBSD has imported OpenZFS.  \todo versions, links
+
+## NetBSD 8 and earlier
+
+While there is some ZFS code, it is old, and seems to have significant
+problems.  If one wants to use ZFS, first upgrade to NetBSD 9.  It is
+unlikely that anyone is interested in helping, other than telling you
+to upgrade to 9.
+
+(Reports of how well NetBDS 8 works are welcome on netbsd-users, if it
+can actually be recommended for use.)
+
+## NetBSD 9
+
+There have been fixes since 9.0 RELEASE.  It is best to upgrade along
+the netbsd-9 branch, but the release should be ok.
+
+\todo This is OpenZFS as of X.   Most aspects work solidly.
+
+\todo This supports pool version 28/5000 (really true?).  Of the
+feature flags found in modern OpenZFS, \todo are supported.
+
+## NetBSD current
+
+There is initial support for ZFS root, via booting from ffs and pivoting.
+
+One can make a ccd using a zvol as a component.  This allows reading a
+GPT label from the zvol, which is useful in case the zvol had been
+exported via iscsi and some other system created a label.
+
+## things that aren't suported yet
+
+\todo (?) hotswap
+
+\todo (?) direct boot into zfs root
+
+## Architectures
+
+Most people seem to be using amd64.
+
+To build zfs, one puts MKZFS=yes in mk.conf.  This is default on amd64
+and aarch64 on netbsd-9.  In current, it is also default on sparc64.
+
+More or less, zfs can be enabled on an architecture when it is known
+to build and run reliably.  (Of course, users are welcome to build it
+and report.)
+
+# NetBSD-specific information
+
+## rc.conf
+
+The main configuration is to put zfs=YES in rc.conf, so that the rc.d
+scripts bring up ZFS and mount ZFS filesystems.
+
+## mount order
+
+NetBSD mounts other filesystems and then ZFS filesystems.  This can be
+a problem if /usr/pkgsrc is on ZFS and /usr/pkgsrc/distfiles is on
+NFS.  A workaround is to use noauto and do the mounts in /etc/rc.local.
+
+## TRIM
+
+There is some notion of TRIM and zfs using it.
+
+\todo Explain how this relates to NetBSD.
+
+# Memory usage
+
+Basically, ZFS uses lots of memory and most people run it on systems
+with large amounts of memory.  NetBSD works well on systems with
+comparatively small amounts of memory.  So a natural question is how
+well ZFS works on one's VAX with 2M of RAM :-)
+
+More seriously, one might ask if is reasonable to run ZFS on a RPI3
+with 1G of RAM, or even if it is reasonable on a system with 4G.
+
+\todo Give ballpark level for minimum sane RAM, and the amount which
+is cleanly enough.
+
+FreeBSD has some documentation about memory use.  \todo Explain if
+this applies, or if not what we should do instead.
+
+https://www.freebsd.org/doc/handbook/zfs-advanced.html
+
+# Interoperability with other systems
+
+\todo Explain pool version and feature flags relationship to FreeBSD,
+Linux, OpenIndiana/Illumos/?, and ?
+
+

update the mailing lists to port-mips@
Index: wikisrc/ports/cobalt.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cobalt.mdwn,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- wikisrc/ports/cobalt.mdwn	15 Feb 2020 08:00:06 -0000	1.19
+++ wikisrc/ports/cobalt.mdwn	29 Feb 2020 21:17:35 -0000	1.20
@@ -1,5 +1,6 @@
 [[!template id=port
 port="cobalt"
+port_alt="mips"
 cur_rel="9.0"
 future_rel="10.0"
 pkg_rel="6.0"
Index: wikisrc/ports/evbmips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbmips.mdwn,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- wikisrc/ports/evbmips.mdwn	15 Feb 2020 08:00:06 -0000	1.23
+++ wikisrc/ports/evbmips.mdwn	29 Feb 2020 21:17:35 -0000	1.24
@@ -1,5 +1,6 @@
 [[!template id=port
 port="evbmips"
+port_alt="mips"
 port_var1="mips64eb"
 port_var2="mips64el"
 port_var3="mipseb"
Index: wikisrc/ports/ews4800mips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/ews4800mips.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/ports/ews4800mips.mdwn	15 Feb 2020 08:00:06 -0000	1.18
+++ wikisrc/ports/ews4800mips.mdwn	29 Feb 2020 21:17:35 -0000	1.19
@@ -1,5 +1,6 @@
 [[!template id=port
 port="ews4800mips"
+port_alt="mips"
 cur_rel="9.0"
 future_rel="10.0"
 pkg_rel="5.0"
Index: wikisrc/ports/hpcmips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/hpcmips.mdwn,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- wikisrc/ports/hpcmips.mdwn	15 Feb 2020 08:00:06 -0000	1.23
+++ wikisrc/ports/hpcmips.mdwn	29 Feb 2020 21:17:35 -0000	1.24
@@ -1,5 +1,6 @@
 [[!template id=port
 port="hpcmips"
+port_alt="mips"
 cur_rel="9.0"
 future_rel="10.0"
 pkg_rel="6.0"
Index: wikisrc/ports/mipsco.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/mipsco.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/ports/mipsco.mdwn	15 Feb 2020 08:00:06 -0000	1.17
+++ wikisrc/ports/mipsco.mdwn	29 Feb 2020 21:17:35 -0000	1.18
@@ -1,5 +1,6 @@
 [[!template id=port
 port="mipsco"
+port_alt="mips"
 cur_rel="9.0"
 future_rel="10.0"
 changes_cur="9.0"
Index: wikisrc/ports/newsmips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/newsmips.mdwn,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- wikisrc/ports/newsmips.mdwn	15 Feb 2020 08:00:06 -0000	1.19
+++ wikisrc/ports/newsmips.mdwn	29 Feb 2020 21:17:35 -0000	1.20
@@ -1,5 +1,6 @@
 [[!template id=port
 port="newsmips"
+port_alt="mips"
 cur_rel="9.0"
 future_rel="10.0"
 changes_cur="9.0"
Index: wikisrc/ports/sbmips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sbmips.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/ports/sbmips.mdwn	15 Feb 2020 08:00:06 -0000	1.22
+++ wikisrc/ports/sbmips.mdwn	29 Feb 2020 21:17:35 -0000	1.23
@@ -1,5 +1,6 @@
 [[!template id=port
 port="sbmips"
+port_alt="mips"
 port_var1="mipseb"
 port_var2="mipsel"
 cur_rel="9.0"
Index: wikisrc/ports/sgimips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sgimips.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/ports/sgimips.mdwn	15 Feb 2020 08:00:06 -0000	1.21
+++ wikisrc/ports/sgimips.mdwn	29 Feb 2020 21:17:35 -0000	1.22
@@ -1,5 +1,6 @@
 [[!template id=port
 port="sgimips"
+port_alt="mips"
 cur_rel="9.0"
 future_rel="10.0"
 pkg_rel="6.0"

ok that works, but actually there's some pre-existing nonsense going on,
namely, that all of the pages that use port_alt have a broken "port
maintainer" link (eg epoc32, mmeye, etc); so, fix that link in the template
to use port_alt too, hopefully that should fix all pages at once
Index: wikisrc/ports/pmax.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/pmax.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/ports/pmax.mdwn	29 Feb 2020 21:04:26 -0000	1.22
+++ wikisrc/ports/pmax.mdwn	29 Feb 2020 21:11:26 -0000	1.23
@@ -1,7 +1,6 @@
 [[!template id=port
 port="pmax"
 port_alt="mips"
-port_maint="mips"
 cur_rel="9.0"
 future_rel="10.0"
 pkg_rel="6.0"
Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/templates/port.mdwn	29 Feb 2020 21:04:26 -0000	1.22
+++ wikisrc/templates/port.mdwn	29 Feb 2020 21:11:26 -0000	1.23
@@ -173,8 +173,8 @@
 ]
 
 </TMPL_IF>
-<TMPL_IF port_maint>
-<a href="mailto:port-<TMPL_VAR port_maint>-maintainer@NetBSD.org">Mail the NetBSD/<TMPL_VAR port_maint> port maintainer</a>
+<TMPL_IF port_alt>
+<a href="mailto:port-<TMPL_VAR port_alt>-maintainer@NetBSD.org">Mail the NetBSD/<TMPL_VAR port_alt> port maintainer</a>
 <TMPL_ELSE>
 <a href="mailto:port-<TMPL_VAR port>-maintainer@NetBSD.org">Mail the NetBSD/<TMPL_VAR port> port maintainer</a>
 </TMPL_IF>

nope, let's try this
Index: wikisrc/ports/pmax.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/pmax.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/ports/pmax.mdwn	29 Feb 2020 20:59:56 -0000	1.21
+++ wikisrc/ports/pmax.mdwn	29 Feb 2020 21:04:26 -0000	1.22
@@ -1,6 +1,7 @@
 [[!template id=port
 port="pmax"
 port_alt="mips"
+port_maint="mips"
 cur_rel="9.0"
 future_rel="10.0"
 pkg_rel="6.0"
Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/templates/port.mdwn	25 Jul 2018 05:54:25 -0000	1.21
+++ wikisrc/templates/port.mdwn	29 Feb 2020 21:04:26 -0000	1.22
@@ -173,7 +173,11 @@
 ]
 
 </TMPL_IF>
+<TMPL_IF port_maint>
+<a href="mailto:port-<TMPL_VAR port_maint>-maintainer@NetBSD.org">Mail the NetBSD/<TMPL_VAR port_maint> port maintainer</a>
+<TMPL_ELSE>
 <a href="mailto:port-<TMPL_VAR port>-maintainer@NetBSD.org">Mail the NetBSD/<TMPL_VAR port> port maintainer</a>
+</TMPL_IF>
 
 <TMPL_IF supported_hardware>
 ## Supported Hardware

Try to fix the mailing list, let's see if it works.
Index: wikisrc/ports/pmax.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/pmax.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/ports/pmax.mdwn	15 Feb 2020 08:00:06 -0000	1.20
+++ wikisrc/ports/pmax.mdwn	29 Feb 2020 20:59:56 -0000	1.21
@@ -1,5 +1,6 @@
 [[!template id=port
 port="pmax"
+port_alt="mips"
 cur_rel="9.0"
 future_rel="10.0"
 pkg_rel="6.0"

port-sgimips@ got merged into port-mips@
Index: wikisrc/projects/project/sgibootloader.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sgibootloader.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/sgibootloader.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/sgibootloader.mdwn	29 Feb 2020 20:54:12 -0000	1.3
@@ -3,7 +3,7 @@
 title="Improve the SGI bootloader"
 
 contact="""
-[port-sgimips](mailto:port-sgimips@NetBSD.org)
+[port-mips](mailto:port-mips@NetBSD.org)
 """
 
 category="ports"
Index: wikisrc/projects/project/sgimips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sgimips.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/sgimips.mdwn	31 Aug 2018 21:26:27 -0000	1.5
+++ wikisrc/projects/project/sgimips.mdwn	29 Feb 2020 20:54:12 -0000	1.6
@@ -3,7 +3,7 @@
 title="Port NetBSD to SGI Octane and Origin machines"
 
 contact="""
-[port-sgimips](mailto:port-sgimips@NetBSD.org)
+[port-mips](mailto:port-mips@NetBSD.org)
 """
 
 category="ports"
Index: wikisrc/projects/project/sgimipsr10k.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sgimipsr10k.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/sgimipsr10k.mdwn	15 Feb 2018 00:33:13 -0000	1.3
+++ wikisrc/projects/project/sgimipsr10k.mdwn	29 Feb 2020 20:54:12 -0000	1.4
@@ -3,7 +3,7 @@
 title="Optimize for R10k CPUs in machines like the SGI O2"
 
 contact="""
-[port-sgimips](mailto:port-sgimips@NetBSD.org)
+[port-mips](mailto:port-mips@NetBSD.org)
 """
 
 category="ports"

Link Root on ZFS
Index: wikisrc/tutorials.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/tutorials.mdwn	22 Nov 2019 13:55:23 -0000	1.39
+++ wikisrc/tutorials.mdwn	25 Feb 2020 20:00:28 -0000	1.40
@@ -6,6 +6,7 @@
 * [[Installation on UEFI systems]]
 
 ## Guide and HOWTOs
+* [Root on ZFS](../wiki/RootOnZFS/)
 * [[set-up raidframe]]
 * [[LaTeX in NetBSD]]
 * [[How to use snapshots]]

Update
Index: wikisrc/wiki/RootOnZFS.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/wiki/RootOnZFS.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/wiki/RootOnZFS.mdwn	22 Feb 2020 19:17:04 -0000	1.1
+++ wikisrc/wiki/RootOnZFS.mdwn	25 Feb 2020 19:56:20 -0000	1.2
@@ -1,26 +1,34 @@
 # Root On ZFS
 
 NetBSD-9 gained much improved ZFS support.
-However, one feature it's still missing is the ability to have your system root on ZFS.
-For that, we need to teach our boot loader about ZFS, but until then we can work around this limitation by using a FFS boot partition and a ZFS root ramdisk.
-You'll also need to use NetBSD-9.99.47 or newer.
-
-The idea is simple - the boot loader loads the NetBSD kernel from FFS and the ZFS root ramdisk.
-The ramdisk then mounts the boot partition and copies the requires ZFS modules from it into the ramdisk.
-ZFS is then initialised to load the modules and then umounts the boot partition.
-This step saves you from having to load the modules in boot.cfg.
-Because the initial root is on a ramdisk, we can then load the boot partition from inside the ZFS root to maintain it.
-
-Once ZFS is initialised, the ZFS root is then mounted and sysctl then instructs init to chroot to it and the normal boot procedure then starts.
-Once started, the kernel and modules can updated by mounting the boot partition to /altroot.
+However, one feature it's still missing is the ability to have your system
+root on ZFS.
+For that, we need to teach our boot loader about ZFS,xi
+but until then we can work around this limitation by using a FFS boot
+partition and a ZFS root ramdisk.
+You'll also need to use NetBSD-9.99.48 or newer.
+
+The idea is simple - the boot loader loads the NetBSD kernel and the
+required modules *(solaris and zfs)* from FFS and the ZFS root ramdisk.
+The ramdisk then imports the ZFS root pool called `rpool`,
+mounts `rpool/ROOT` to `/altroot` and finally instructs the kernel to
+chroot to it.
+Because the initial root is on a ramdisk,
+we can then load the boot partition from inside the ZFS chroot to maintain it;
+for example to update the kernel and modules.
 
 ## Assumptions
 
-The ramdisk does make some assumptions as there is no way to pass variables from boot.cfg:
+The ramdisk does make some assumptions as there is no way to pass variables
+from boot.cfg:
 
-  *  The boot partition can be referenced as `NAME=boot` - for GPT this is as simple as giving it a label.
+  *  The kernel has matching modules installed in the same partition; you only need `solaris` and `zfs`.
   *  The ZFS root pool is called `rpool` and the root filesystem is called `ROOT`.
 
+Once inside the chroot the kernel will load modules from the ZFS filesystem
+because there is a symlink to it from the ramdisk.
+The same is true for any firmware needed after boot.
+
 ## Generic setup
 
 Until the NetBSD installer can be updated, here are the manual steps from fresh:
@@ -31,7 +39,6 @@
   *  Create a partition for ZFS
   *  Finish the NetBSD installation - install the etc, base and maybe rescue sets
   *  Reboot into your minimal NetBSD install
-  *  Label the boot partition boot - if you don't do this then the ramdisk will moan it can't load modules
 
 ## ZFS Setup
 
@@ -51,19 +58,15 @@
   *  Add `name=boot /altroot ffs rw,noauto` to `/altroot/etc/fstab` along with any ZFS filesytems you created in '/usr' and '/var'
   *  Add the filesystems as well to `critical_filesystems_local` in `/altroot/etc/rc.conf` - such as `critical_filesystems_local="/usr /var /var/log"`
   *  Copy the `ramdisk-zfsroot.fs` to `/`
-  *  Edit `/boot.cfg` and add `menu=Boot ZFS Root:fs /ramdisk-zfsroot.fs;boot`
+  *  Edit `/boot.cfg` and add `menu=Boot ZFS Root:load solaris;load zfs;fs /ramdisk-zfsroot.fs;boot`
 
-And done! You can now reboot and enjoy your root on ZFS and all the benefits it brings.
-When updating the kernel, remember to `mount /altroot` and update it there as well as the modules.
+And done!
+You can now reboot and enjoy your root on ZFS and all the benefits it brings.
+When updating the kernel, remember to `mount /altroot` and update it there as
+well as the modules.
 
 ## Future work
 
 All these steps could be done in the installer.
-This is probably an easier task than adding ZFS support to the bootloader. But don't let that stop you if you are stuck for something to do!
-
-# DANGER NETBSD ROOT ON ZFS USER, DANGER!
-
-There seems to be an issue accessing `/dev` nodes on ZFS.
-While -current has enough fixes to work somewhat, accessing the boot partition whilst while root is on ZFS will hang, panic and maybe even corrupt your boot partition.
-As such, you'll have to reboot into single user. From here you can mount the ZFS partition to `/altroot` and copy the updated kernel and modules from there to the boot partition.
-Ironically, this is what the ramdisk approach was designed to actively avoid. Hopefully we can get it resolved soon.
+This is probably an easier task than adding ZFS support to the bootloader.
+But don't let that stop you if you are stuck for something to do!

--- /dev/null	2020-02-22 19:17:04.127252982 +0000
+++ wikisrc/wiki/RootOnZFS.mdwn	2020-02-22 19:17:36.838308036 +0000
@@ -0,0 +1,69 @@
+# Root On ZFS
+
+NetBSD-9 gained much improved ZFS support.
+However, one feature it's still missing is the ability to have your system root on ZFS.
+For that, we need to teach our boot loader about ZFS, but until then we can work around this limitation by using a FFS boot partition and a ZFS root ramdisk.
+You'll also need to use NetBSD-9.99.47 or newer.
+
+The idea is simple - the boot loader loads the NetBSD kernel from FFS and the ZFS root ramdisk.
+The ramdisk then mounts the boot partition and copies the requires ZFS modules from it into the ramdisk.
+ZFS is then initialised to load the modules and then umounts the boot partition.
+This step saves you from having to load the modules in boot.cfg.
+Because the initial root is on a ramdisk, we can then load the boot partition from inside the ZFS root to maintain it.
+
+Once ZFS is initialised, the ZFS root is then mounted and sysctl then instructs init to chroot to it and the normal boot procedure then starts.
+Once started, the kernel and modules can updated by mounting the boot partition to /altroot.
+
+## Assumptions
+
+The ramdisk does make some assumptions as there is no way to pass variables from boot.cfg:
+
+  *  The boot partition can be referenced as `NAME=boot` - for GPT this is as simple as giving it a label.
+  *  The ZFS root pool is called `rpool` and the root filesystem is called `ROOT`.
+
+## Generic setup
+
+Until the NetBSD installer can be updated, here are the manual steps from fresh:
+
+  *  Build the ramdisk (`cd src/distrib/amd64/ramdisks/ramdisk-zfsroot; nbmake-amd64`)
+  *  Boot the NetBSD installer
+  *  Create a small (I used 2G) FFS partition and a normal swap partition
+  *  Create a partition for ZFS
+  *  Finish the NetBSD installation - install the etc, base and maybe rescue sets
+  *  Reboot into your minimal NetBSD install
+  *  Label the boot partition boot - if you don't do this then the ramdisk will moan it can't load modules
+
+## ZFS Setup
+
+So far, so good. Now we need to make the needed adjustments to change root:
+
+  *  Create a ZFS pool called `rpool` on your ZFS partition
+  *  Create a ZFS filesystem called `ROOT` in `rpool`
+  *  Set the mountpoint of `rpool/ROOT` to legacy so that the mount command can deal with it
+  *  Create any other ZFS filesystems you want to - if you create `/usr` or `/var` or anything in these they **must** to be legacy mount points as well
+  *  `zfs umount rpool/ROOT`
+  *  Add `rpool/ROOT /altroot zfs rw` to /etc/fstab
+  *  `mount /altroot`
+  *  Extract the sets you need to `/altroot`. At a minimum you will need etc and base.
+  *  Copy `/etc/wscons.conf`, `/etc/fstab` and any other config files sysinst might have created to `/etc/rc.conf` to `/altroot/etc`
+  *  Set `zfs=YES` in `/altroot/etc/rc.conf`
+  *  Remove `rpool/ROOT` from `/altroot/etc/fstab`
+  *  Add `name=boot /altroot ffs rw,noauto` to `/altroot/etc/fstab` along with any ZFS filesytems you created in '/usr' and '/var'
+  *  Add the filesystems as well to `critical_filesystems_local` in `/altroot/etc/rc.conf` - such as `critical_filesystems_local="/usr /var /var/log"`
+  *  Copy the `ramdisk-zfsroot.fs` to `/`
+  *  Edit `/boot.cfg` and add `menu=Boot ZFS Root:fs /ramdisk-zfsroot.fs;boot`
+
+And done! You can now reboot and enjoy your root on ZFS and all the benefits it brings.
+When updating the kernel, remember to `mount /altroot` and update it there as well as the modules.
+
+## Future work
+
+All these steps could be done in the installer.
+This is probably an easier task than adding ZFS support to the bootloader. But don't let that stop you if you are stuck for something to do!
+
+# DANGER NETBSD ROOT ON ZFS USER, DANGER!
+
+There seems to be an issue accessing `/dev` nodes on ZFS.
+While -current has enough fixes to work somewhat, accessing the boot partition whilst while root is on ZFS will hang, panic and maybe even corrupt your boot partition.
+As such, you'll have to reboot into single user. From here you can mount the ZFS partition to `/altroot` and copy the updated kernel and modules from there to the boot partition.
+Ironically, this is what the ramdisk approach was designed to actively avoid. Hopefully we can get it resolved soon.

Add ZFS root project
No listed mentor. If you care about this please sign up.
Members: 
	projects/project/zfs_root.mdwn:INITIAL->1.1 

--- /dev/null	2020-02-21 22:41:33.685397432 +0000
+++ wikisrc/projects/project/zfs_root.mdwn	2020-02-21 22:42:35.358457360 +0000
@@ -0,0 +1,45 @@
+[[!template id=project
+
+title="ZFS root support (bootloader and mount_root)"
+
+contact="""
+[tech-kern](mailto:tech-kern@NetBSD.org)
+"""
+
+mentors="""
+[tech-kern](mailto:tech-kern@NetBSD.org)
+"""
+
+category="kernel"
+difficulty="easy"
+duration="1-2 months"
+
+description="""
+This project consists of two parts: getting the bootloader code ("libsa") to
+read ZFS filesystems, and enabling mounting ZFS as a root filesystem.
+
+For ZFS bootloader support, fortunately code already exists in the FreeBSD
+variant of libsa, so it's a matter of adapting it.
+
+Milestones:
+
+ZFS bootloader:
+
+* Setup test environment for testing bootloader changes, experiment with debug printing in libsa
+* Identify & import ZFS libsa code in FreeBSD
+* Read a kernel from a ZFS filesystem, while booting into a non-ZFS root.
+
+ZFS as root filesystem:
+
+* Understanding what root mount functions must do
+* ???
+* Write one for ZFS on NetBSD
+
+Stretch goal:
+
+* Pass a parameter for which ZFS snapshot to boot to, using the bootloader.
+"""
+
+]]
+
+[[!tag gsoc]]

Mark as done by jason high
Index: wikisrc/projects/project/Add_Argon2_password_hashing.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/Add_Argon2_password_hashing.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/Add_Argon2_password_hashing.mdwn	4 May 2019 16:06:11 -0000	1.3
+++ wikisrc/projects/project/Add_Argon2_password_hashing.mdwn	21 Feb 2020 22:25:18 -0000	1.4
@@ -15,6 +15,7 @@
 category="userland"
 difficulty="medium"
 duration="3 months"
+done_by="Jason High"
 
 description="""
 We are currently offering to store local users passwords (in `/etc/master.passwd`) using various encodings, including MD5, SHA1 and blowfish.

Unlist myself as possible mentor. No time for anything.
Index: wikisrc/projects/project/vc4.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/vc4.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/vc4.mdwn	18 Jan 2019 15:59:53 -0000	1.2
+++ wikisrc/projects/project/vc4.mdwn	21 Feb 2020 22:23:16 -0000	1.3
@@ -7,7 +7,7 @@
 """
 
 mentors="""
-[Maya Rashish](mailto:maya@NetBSD.org)
+[port-arm](mailto:port-arm@NetBSD.org)
 """
 
 category="kernel"

Mark as done in GSoC 2019.
Index: wikisrc/projects/project/drm_compat.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/drm_compat.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/drm_compat.mdwn	18 Jan 2019 16:06:40 -0000	1.1
+++ wikisrc/projects/project/drm_compat.mdwn	21 Feb 2020 22:20:52 -0000	1.2
@@ -13,6 +13,7 @@
 category="kernel"
 difficulty="easy"
 duration="1-2 months"
+done_by="Surya Shankar, Christos Zoulas"
 
 description="""
 NetBSD already has DRM/KMS support. It's implementing all the same calls as linux.  

catch up with htdocs fundraiser thing and sync global.css in general
Index: wikisrc/global.css
===================================================================
RCS file: /cvsroot/wikisrc/global.css,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/global.css	20 Jan 2020 06:08:22 -0000	1.15
+++ wikisrc/global.css	16 Feb 2020 21:31:24 -0000	1.16
@@ -1,4 +1,4 @@
-/* $NetBSD: global.css,v 1.15 2020/01/20 06:08:22 rillig Exp $ */
+/* $NetBSD: global.css,v 1.16 2020/02/16 21:31:24 maya Exp $ */
 
 /* Remember to keep htdocs/globals.css and wikisrc/globals.css in sync. */
 /* See https://wiki.NetBSD.org/wiki/cvs/. */
@@ -262,8 +262,8 @@
   clear: both;
 }
 
-.iconsLeft img {
-  float: left;
+img.icon {
+  vertical-align: middle;
 }
 
 .iconsRight img {
@@ -335,6 +335,37 @@
   padding-left: 1em;
 }
 
+.donation input[type=number], .donation select {
+  border:1px solid black;
+  width: 3em;
+  text-align: right;
+}
+
+.donation input[type=image] {
+  vertical-align: middle;
+  margin: 2px 0;
+}
+
+#fundraiser {
+  position: absolute;
+  top: 50px;
+  right: 10px;
+}
+
+#fundraiser-amount {
+  height: 10px;
+  border: 1px solid #fd6720;
+  border-radius: 10px;
+}
+
+#fundraiser-raised {
+  box-sizing: border-box;
+  background: #fd6720;
+  height: 10px;
+  border: 1px solid #fd6720;
+  border-radius: 10px 0 0 10px;
+}
+
 .buttons {
   text-align: center;
   margin-top: 2em;
@@ -377,6 +408,10 @@
   padding: 0.5em 0;
 }
 
+span.more {
+  font-weight: bold;
+}
+
 .more a, .more li a {
   color: #fd6720;
   background-color: transparent;
@@ -499,6 +534,12 @@
   display: table;
 }
 
+img.sponsor {
+  width: 100px;
+  display: table-cell;
+  padding: 0 0.3em;
+}
+
 #hackathonBox {
   background: #fd6720;
   color: #ffffff;
@@ -624,6 +665,7 @@
 	Border-Style: solid;
 	Border-Width: thin;
 	Padding: 5pt;
+	text-align: center;
 }
 
 .head {
@@ -694,16 +736,6 @@
 
 /* end books */
 
-#twodonate input {
-  min-height: 20px;
-  vertical-align: middle;
-  margin-top: 3px;
-}
-
-#monthlydonate {
-  margin-top: 20px;
-}
-
 #hamburger {
   display: none;
 }
@@ -806,11 +838,11 @@
 	  border: none;
 	}
 
-	.sideBarLeft {
+	.sideBarLeft, #fundraiser {
 	  display: none;
 	}
 
-	.half, .quarter {
+	.half, .quarter, .oneThird, .twoThirds {
 	  width: initial;
 	}
 
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- wikisrc/templates/page.tmpl	10 Feb 2020 19:56:11 -0000	1.57
+++ wikisrc/templates/page.tmpl	16 Feb 2020 21:31:24 -0000	1.58
@@ -14,6 +14,7 @@
 <link rel="icon" href="<TMPL_VAR BASEURL><TMPL_VAR FAVICON>" type="image/x-icon" />
 </TMPL_IF>
 <link rel="stylesheet" href="//wiki.netbsd.org/global.css" type="text/css" />
+<link rel="stylesheet" href="//www.netbsd.org/donations/thermo/fundraiser.css" type="text/css" />
 <link rel="stylesheet" href="//wiki.netbsd.org/style.css" type="text/css" />
 <TMPL_IF LOCAL_CSS>
 <link rel="stylesheet" href="<TMPL_VAR BASEURL><TMPL_VAR LOCAL_CSS>" type="text/css" />
@@ -38,6 +39,14 @@
         <div id="name"><a href="//www.NetBSD.org/">The NetBSD Project</a></div>
         <div id="slogan"><a href="//www.NetBSD.org/">&ldquo;Of course it runs NetBSD&rdquo;</a></div>
       </div>
+        <a href="https://netbsd.org/donations/#how-to-donate">
+          <div id="fundraiser">
+            <br />
+            <div id="fundraiser-amount">
+              <div id="fundraiser-raised"></div>
+            </div>
+          </div>
+        </a>
     </div>
 
     <!-- mobile menu icon -->

Link to new DE0 Nano SoC page
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -r1.86 -r1.87
--- wikisrc/ports/evbarm.mdwn	15 Feb 2020 08:00:06 -0000	1.86
+++ wikisrc/ports/evbarm.mdwn	15 Feb 2020 21:08:38 -0000	1.87
@@ -73,6 +73,7 @@
  - [[ODROID C1 and C1+|ODROID-C1]]
  - [[Raspberry Pi 1, 2 and 3|Raspberry Pi]]
  - [[RockChip SoCs|RockChip]]
+ - [[Terasic DE0 Nano-SoC|Cyclone5]]
 
 ### SSH configuration for installtion
 

Add page for the DE0 Nano SoC, with installation instructions
--- /dev/null	2020-02-15 21:01:32.212339978 +0000
+++ wikisrc/ports/evbarm/cyclone5.mdwn	2020-02-15 21:06:15.953298449 +0000
@@ -0,0 +1,134 @@
+[[!meta title="NetBSD/evbarm on DE0 Nano-SoC"]]
+
+NetBSD runs on the Terasic DE0 Nano-SoC board, based on the
+Altera/Intel Cyclone V.
+The `evbearmv7hf-el` version of NetBSD should be used.
+
+# Hardware supported
+
+Currently, ethernet, USB, micro-SD slot, and UART are supported.
+FPGA, GPIO's, SPI, ADC, accelerometer, and so on are not yet supported.
+
+# Image build and installation
+
+Basically, you need to `dd` u-boot from `sysutils/u-boot-de0-nanosoc` into
+a new partition of type 162 (0xA2) in `armv7.img`, and that's it.
+
+Here are the precise instructions under NetBSD.
+
+[[!template id=programlisting text="""
+$ gunzip -c armv7.img.gz > armv7-for-nanosoc.img
+$ fdisk -f -u -2 -s 162/2048/2048 armv7-for-nanosoc.img
+$ dd if=/usr/pkg/share/u-boot/de0-nanosoc/u-boot-with-spl.sfp of=armv7-for-nanosoc.img seek=2048 conv=notrunc
+# dd if=armv7-for-nanosoc.img of=/dev/rXXN bs=1m conv=sync
+"""]]
+
+# dmesg
+
+[[!template id=programlisting text="""
+>> NetBSD/evbarm efiboot (arm), Revision 1.13 ()
+Press return to boot now, any other key for boot prompt
+booting netbsd - starting in 0 seconds.     
+6727600+2108376+1397800 [494666+457680+477547]=0xb25820
+[   1.0000000] NetBSD/evbarm (fdt) booting ...
+[   1.0000000] [ Kernel symbol table missing! ]
+[   1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
+[   1.0000000]     2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017,
+[   1.0000000]     2018, 2019, 2020 The NetBSD Foundation, Inc.  All rights reserved.
+[   1.0000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
+[   1.0000000]     The Regents of the University of California.  All rights reserved.
+
+[   1.0000000] NetBSD 9.0 (GENERIC) #0: 
+[   1.0000000]  mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/evbarm/compile/GENERIC
+[   1.0000000] total memory = 1023 MB
+[   1.0000000] avail memory = 1003 MB
+[   1.0000000] armfdt0 (root)
+[   1.0000000] simplebus0 at armfdt0: Terasic DE-0(Atlas)
+[   1.0000000] simplebus1 at simplebus0
+[   1.0000000] cpus0 at simplebus0
+[   1.0000000] simplebus2 at simplebus0
+[   1.0000000] cpu0 at cpus0: Cortex-A9 r3p0 (Cortex V7A core)
+[   1.0000000] cpu0: DC enabled IC enabled WB enabled LABT branch prediction enabled
+[   1.0000000] cpu0: 32KB/32B 4-way L1 VIPT Instruction cache
+[   1.0000000] cpu0: 32KB/32B 4-way write-back-locking-C L1 PIPT Data cache
+[   1.0000000] cpu0: 512KB/32B 8-way write-back-locking-D L2 PIPT Unified cache
+[   1.0000000] vfp0 at cpu0: NEON MPE (VFP 3.0+), rounding, NaN propagation, denormals
+[   1.0000000] cpu1 at cpus0
+[   1.0000000] cycvrstmgr0 at simplebus1: reset manager
+[   1.0000000] simplebus3 at simplebus1
+[   1.0000000] gic0 at simplebus0: GIC
+[   1.0000000] armgic0 at gic0: Generic Interrupt Controller, 256 sources (245 valid)
+[   1.0000000] armgic0: 32 Priorities, 224 SPIs, 5 PPIs, 16 SGIs
+[   1.0000000] cycvclkmgr0 at simplebus1: clock manager
+[   1.0000000] syscon0 at simplebus1: System Controller Registers
+[   1.0000000] syscon1 at simplebus1: System Controller Registers
+[   1.0000000] syscon2 at simplebus1: System Controller Registers
+[   1.0000000] l2cc0 at simplebus1
+[   1.0000000] arml2cc0 at l2cc0: ARM PL310 r3p3 L2 Cache Controller (disabled)
+[   1.0000000] arml2cc0: cache enabled
+[   1.0000000] a9tmr0 at simplebus1
+[   1.0000000] a9tmr0: interrupting on GIC irq 27
+[   1.0000000] arma9tmr0 at a9tmr0: A9 Global 64-bit Timer (231 MHz)
+[   1.0000000] com0 at simplebus1: ns16550a, working fifo
+[   1.0000000] com0: console
+[   1.0000000] com0: interrupting on GIC irq 194
+[   1.0000000] com1 at simplebus1: ns16550a, working fifo
+[   1.0000000] com1: interrupting on GIC irq 195
+[   1.0000000] fregulator0 at simplebus0: 3.3V
+[   1.0000000] usbnopphy0 at simplebus1: USB PHY
+[   1.0000000] /soc/fpgamgr@ff706000 at simplebus1 not configured
+[   1.0000000] /soc/gpio@ff70a000 at simplebus1 not configured
+[   1.0000000] /soc/sram@ffff0000 at simplebus1 not configured
+[   1.0000000] /soc/amba/pdma@ffe01000 at simplebus3 not configured
+[   1.0000000] /soc/gpio@ff709000 at simplebus1 not configured
+[   1.0000000] armpmu0 at simplebus0: Performance Monitor Unit
+[   1.0000000] /soc/fpga_bridge@ff400000 at simplebus1 not configured
+[   1.0000000] /soc/fpga_bridge@ff500000 at simplebus1 not configured
+[   1.0000000] awge0 at simplebus1: GMAC
+[   1.0000000] awge0: interrupting on GIC irq 152
+[   1.0000000] awge0: Core version: 00001037
+[   1.0000000] awge0: Ethernet address f2:00:74:49:ce:e1
+[   1.0000000] awge0: HW feature mask: 170d69bf
+[   1.0000000] awge0: Using enhanced descriptor format
+[   1.0000000] ukphy0 at awge0 phy 1: OUI 0x0010a1, model 0x0022, rev. 2
+[   1.0000000] ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
+[   1.0000000] /soc/gpio@ff708000 at simplebus1 not configured
+[   1.0000000] /soc/i2c@ffc04000 at simplebus1 not configured
+[   1.0000000] /soc/eccmgr at simplebus1 not configured
+[   1.0000000] dwcmmc0 at simplebus1: MHS (50000000 Hz)
+[   1.0000000] dwcmmc0: interrupting on GIC irq 171
+[   1.0000000] /soc/snoop-control-unit@fffec000 at simplebus1 not configured
+[   1.0000000] /soc/timer0@ffc08000 at simplebus1 not configured
+[   1.0000000] /soc/timer1@ffc09000 at simplebus1 not configured
+[   1.0000000] /soc/timer2@ffd00000 at simplebus1 not configured
+[   1.0000000] /soc/timer3@ffd01000 at simplebus1 not configured
+[   1.0000000] dwctwo0 at simplebus1: DesignWare USB2 OTG
+[   1.0000000] dwctwo0: interrupting on GIC irq 160
+[   1.0000000] dwcwdt0 at simplebus1: DesignWare Watchdog Timer
+[   1.0000000] dwcwdt0: default watchdog period is 15 seconds
+[   1.0000000] gpioleds0 at simplebus0:
+[   1.0000000] /soc/base_fpga_region at simplebus1 not configured
+[   1.0000000] /soc/sdramedac at simplebus1 not configured
+[   1.0000370] cpu1: Cortex-A9 r3p0 (Cortex V7A core)
+[   1.0000370] cpu1: DC enabled IC enabled WB enabled LABT branch prediction enabled
+[   1.0100305] cpu1: 32KB/32B 4-way L1 VIPT Instruction cache
+[   1.0100305] cpu1: 32KB/32B 4-way write-back-locking-C L1 PIPT Data cache
+[   1.0200189] cpu1: 512KB/32B 8-way write-back-locking-D L2 PIPT Unified cache
+[   1.0300185] vfp1 at cpu1: NEON MPE (VFP 3.0+), rounding, NaN propagation, denormals
+[   1.0300185] armpmu0: interrupting on GIC irq 208
+[   1.0400229] armpmu0: interrupting on GIC irq 209
+[   1.0400229] sdmmc0 at dwcmmc0
+[   1.1700197] usb0 at dwctwo0: USB revision 2.0
+[   1.1800215] sdmmc0: SD card status: 4-bit, C6
+[   1.1800215] ld0 at sdmmc0: <0x1b:0x534d:00000:0x10:0x7e34ebec:0x0d4>
+[   1.1919757] uhub0 at usb0: NetBSD (0000) DWC2 root hub (0000), class 9/0, rev 2.00/1.00, addr 1
+[   1.2049057] ld0: 14991 MB, 7614 cyl, 64 head, 63 sec, 512 bytes/sect x 30702592 sectors
+[   1.2128828] ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz
+[   1.9200187] boot device: ld0
+[   1.9200187] root on ld0a dumps on ld0b
+[   1.9300197] root file system type: ffs
+[   1.9300197] kern.module.path=/stand/evbarm/9.0/modules
+[   1.9400190] WARNING: no TOD clock present
+[   1.9400190] WARNING: using filesystem time
+[   1.9528594] WARNING: CHECK AND RESET THE DATE!
+"""]]

Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/aarch64.mdwn	15 Feb 2020 08:00:05 -0000	1.7
+++ wikisrc/ports/aarch64.mdwn	15 Feb 2020 15:43:14 -0000	1.8
@@ -6,23 +6,21 @@
 cur_rel="9.0"
 changes_cur="9.0"
 about="""
-NetBSD/aarch64 is a port to ARM's 64-bit CPUs and other compatible
+NetBSD/aarch64 is a port to Arm's 64-bit CPUs and other compatible
 machines.
 
-Running 32-bit NetBSD/arm EABI binaries is supported as well; see
+Running 32-bit NetBSD/arm EABI binaries is supported on CPUs that are capable of 32-bit EL0 mode; see
 [[!template id=man name="compat_netbsd32" section="8"]].
 
 The port was first committed to the NetBSD source tree as NetBSD/aarch64
-on April 1st, 2018.
+on April 1st, 2018. The first release with support for NetBSD/aarch64 was NetBSD 9.0 on February 14th, 2020.
 
 The original work to do this port was done by Ryo Shimizu, Tohru Nishimura,
-Nick Hudson, Jared D. McNeill, and Matt Thomas.
+Nick Hudson, Jared McNeill, and Matt Thomas.
 
 The port is fully functional. It has been tested on single-CPU and
 multiprocessor configurations, including big.LITTLE asymmetric multiprocessing.
 
-It is not yet available in a release, and will be available in NetBSD 9.0.
-
 The lists of supported boards, SoCs and CPUs is likely incomplete.
 
 ### SoC specific information
@@ -46,11 +44,12 @@
 
 ### Known Supported CPUs
 
- * ARM Cortex-A53
- * ARM Cortex-A57
- * ARM Cortex-A72
- * Marvell ThunderX
  * Ampere eMAG
+ * Arm Cortex-A53
+ * Arm Cortex-A57
+ * Arm Cortex-A72
+ * Arm Neoverse N1
+ * Marvell ThunderX
  * NVIDIA Denver2
 
 [//]: ### Unknown CPUs list:

Update for the 9.0 release
Update for the 9.0 release
Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/aarch64.mdwn	8 Jan 2020 07:11:25 -0000	1.5
+++ wikisrc/ports/aarch64.mdwn	15 Feb 2020 08:00:02 -0000	1.6
@@ -1,8 +1,10 @@
 [[!template id=port
 port="aarch64"
 port_alt="arm"
-future_rel="9.0"
-changes_future="9.0"
+future_rel="10.0"
+changes_future="10.0"
+cur_rel="9.0"
+changes_cur="9.0"
 about="""
 NetBSD/aarch64 is a port to ARM's 64-bit CPUs and other compatible
 machines.
Index: wikisrc/ports/algor.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/algor.mdwn,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- wikisrc/ports/algor.mdwn	2 Jun 2019 13:32:38 -0000	1.19
+++ wikisrc/ports/algor.mdwn	15 Feb 2020 08:00:02 -0000	1.20
@@ -1,10 +1,10 @@
 [[!template id=port
 port="algor"
-cur_rel="8.1"
-future_rel="9.0"
+cur_rel="9.0"
+future_rel="10.0"
 pkg_rel="6.0"
-changes_cur="8.1"
-changes_future="9.0"
+changes_cur="9.0"
+changes_future="10.0"
 thumbnail="//www.netbsd.org/images/ports/algor/alogo2.gif"
 no_install_notes="defined"
 about="""
Index: wikisrc/ports/alpha.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/alpha.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/ports/alpha.mdwn	2 Jun 2019 13:32:38 -0000	1.18
+++ wikisrc/ports/alpha.mdwn	15 Feb 2020 08:00:02 -0000	1.19
@@ -1,10 +1,10 @@
 [[!template id=port
 port="alpha"
-cur_rel="8.1"
+cur_rel="9.0"
 pkg_rel="8.0"
-future_rel="9.0"
-changes_cur="8.1"
-changes_future="9.0"
+future_rel="10.0"
+changes_cur="9.0"
+changes_future="10.0"
 thumbnail="//www.netbsd.org/images/ports/alpha/au-1000.gif"
 about="""
 NetBSD/alpha is a true 64-bit system that fully implements the LP64 architecture,
Index: wikisrc/ports/amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amd64.mdwn,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- wikisrc/ports/amd64.mdwn	2 Sep 2019 22:17:05 -0000	1.28
+++ wikisrc/ports/amd64.mdwn	15 Feb 2020 08:00:02 -0000	1.29
@@ -1,10 +1,10 @@
 [[!template id=port
 port="amd64"
-cur_rel="8.1"
-future_rel="9.0"
+cur_rel="9.0"
+future_rel="10.0"
 pkg_rel="8.0"
-changes_cur="8.1"
-changes_future="9.0"
+changes_cur="9.0"
+changes_future="10.0"
 thumbnail="//www.netbsd.org/images/ports/amd64/AMD_Opteron.gif"
 about="""
 NetBSD/amd64 is a port to the AMD64 family of processors; it
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/ports/amiga.mdwn	2 Jun 2019 13:32:38 -0000	1.22
+++ wikisrc/ports/amiga.mdwn	15 Feb 2020 08:00:02 -0000	1.23
@@ -1,10 +1,10 @@
 [[!template id=port
 port="amiga"
-cur_rel="8.1"
-future_rel="9.0"
+cur_rel="9.0"
+future_rel="10.0"
 pkg_rel="8.0"
-changes_cur="8.1"
-changes_future="9.0"
+changes_cur="9.0"
+changes_future="10.0"
 thumbnail="//www.netbsd.org/images/ports/amiga/header.gif"
 about="""
 NetBSD/amiga is the port of NetBSD to the Amiga line of personal computers by
Index: wikisrc/ports/amigappc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amigappc.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/ports/amigappc.mdwn	2 Jun 2019 13:32:38 -0000	1.18
+++ wikisrc/ports/amigappc.mdwn	15 Feb 2020 08:00:02 -0000	1.19
@@ -1,11 +1,11 @@
 [[!template id=port
 port="amigappc"
 port_alt="powerpc"
-cur_rel="8.1"
+cur_rel="9.0"
 pkg_rel="8.0"
-future_rel="9.0"
-changes_cur="8.1"
-changes_future="9.0"
+future_rel="10.0"
+changes_cur="9.0"
+changes_future="10.0"
 thumbnail="//www.netbsd.org/images/ports/arm26/arch310.gif"
 no_install_notes="defined"
 about="""
Index: wikisrc/ports/arc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/arc.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/ports/arc.mdwn	2 Jun 2019 13:32:38 -0000	1.18
+++ wikisrc/ports/arc.mdwn	15 Feb 2020 08:00:02 -0000	1.19
@@ -1,10 +1,10 @@
 [[!template id=port
 port="arc"
-cur_rel="8.1"
-future_rel="9.0"
+cur_rel="9.0"
+future_rel="10.0"
 pkg_rel="6.0"
-changes_cur="8.1"
-changes_future="9.0"
+changes_cur="9.0"
+changes_future="10.0"
 thumbnail="//www.netbsd.org/images/ports/arc/2200.gif"
 about="""
 NetBSD/arc is a port of NetBSD to the [MIPS](http://www.mips.com) processor
Index: wikisrc/ports/atari.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/atari.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/ports/atari.mdwn	2 Jun 2019 13:32:38 -0000	1.17
+++ wikisrc/ports/atari.mdwn	15 Feb 2020 08:00:02 -0000	1.18
@@ -1,10 +1,10 @@
 [[!template id=port
 port="atari"
-cur_rel="8.1"
-future_rel="9.0"
+cur_rel="9.0"
+future_rel="10.0"
 pkg_rel="8.0"
-changes_cur="8.1"
-changes_future="9.0"
+changes_cur="9.0"
+changes_future="10.0"
 thumbnail="//www.netbsd.org/images/ports/atari/atari.gif"
 about="""
 NetBSD/atari is the port of NetBSD to the Atari line of personal computers.
Index: wikisrc/ports/bebox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/bebox.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/ports/bebox.mdwn	2 Jun 2019 13:32:38 -0000	1.17
+++ wikisrc/ports/bebox.mdwn	15 Feb 2020 08:00:02 -0000	1.18
@@ -1,10 +1,10 @@
 [[!template id=port
 port="bebox"
-cur_rel="8.1"
-future_rel="9.0"
+cur_rel="9.0"
+future_rel="10.0"
 pkg_rel="8.0"
-changes_cur="8.1"

(Diff truncated)
Update for the 9.0 release
Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- wikisrc/ports.mdwn	2 Jun 2019 10:27:03 -0000	1.23
+++ wikisrc/ports.mdwn	14 Feb 2020 19:15:18 -0000	1.24
@@ -20,15 +20,15 @@
 
 [[!table data="""
 Port		|CPU		|Machines						|Latest Release
-[[aarch64]]	|aarch64	|64-bit ARM CPUs					|Not yet released
-[[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[evbarm]]	|arm		|ARM evaluation boards					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[evbmips]]	|mips		|MIPS-based evaluation boards				|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[evbppc]]	|powerpc	|PowerPC-based evaluation boards			|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[hpcarm]]	|arm		|StrongARM based Windows CE PDA machines		|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[i386]]	|i386		|32-bit x86-family generic machines ("PC clones")	|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[sparc64]]	|sparc		|Sun UltraSPARC (64-bit)				|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[xen]]		|i386, x86_64	|Xen Virtual Machine Monitor				|[8.1](http://www.netbsd.org/releases/formal-8/)
+[[aarch64]]	|aarch64	|64-bit ARM CPUs					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[evbarm]]	|arm		|ARM evaluation boards					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[evbmips]]	|mips		|MIPS-based evaluation boards				|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[evbppc]]	|powerpc	|PowerPC-based evaluation boards			|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[hpcarm]]	|arm		|StrongARM based Windows CE PDA machines		|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[i386]]	|i386		|32-bit x86-family generic machines ("PC clones")	|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[sparc64]]	|sparc		|Sun UltraSPARC (64-bit)				|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[xen]]		|i386, x86_64	|Xen Virtual Machine Monitor				|[9.0](http://www.netbsd.org/releases/formal-9/)
 """]]
 
 
@@ -46,55 +46,55 @@
 [[!table data="""
 Port		|CPU		|Machines								|Latest Release
 [[acorn32]]	|arm		|Acorn RiscPC/A7000/NC and compatibles					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[algor]]	|mips		|Algorithmics MIPS evaluation boards					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[alpha]]	|alpha		|Digital Alpha (64-bit)							|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[amiga]]	|m68k		|Commodore Amiga, MacroSystem DraCo					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[amigappc]]	|powerpc	|PowerPC-based Amiga boards						|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[arc]]		|mips		|Machines following the Advanced RISC Computing spec			|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[atari]]	|m68k		|Atari TT030, Falcon, Hades						|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[bebox]]	|powerpc	|Be Inc's BeBox								|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[cats]]	|arm		|Chalice Technology's Strong Arm evaluation board			|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[cesfic]]	|m68k		|CES's FIC8234 VME processor board					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[cobalt]]	|mips		|Cobalt Networks' Microservers						|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[dreamcast]]	|[[sh3]]	|Sega Dreamcast game console						|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[epoc32]]	|arm		|32bit PSION EPOC PDA							|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[emips]]	|mips		|Machines based on "Extensible MIPS"					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[evbsh3]]	|[[sh3]]	|Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs	|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[ews4800mips]]	|mips		|NEC's MIPS based EWS4800 workstations					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[hp300]]	|m68k		|Hewlett-Packard 9000/300 and 400 series				|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[hppa]]	|hppa		|Hewlett-Packard 9000/700 series					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[hpcmips]]	|mips		|MIPS based Windows CE PDA machines					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[hpcsh]]	|[[sh3]]	|Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines		|[8.1](http://www.netbsd.org/releases/formal-8/)
+[[algor]]	|mips		|Algorithmics MIPS evaluation boards					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[alpha]]	|alpha		|Digital Alpha (64-bit)							|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[amiga]]	|m68k		|Commodore Amiga, MacroSystem DraCo					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[amigappc]]	|powerpc	|PowerPC-based Amiga boards						|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[arc]]		|mips		|Machines following the Advanced RISC Computing spec			|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[atari]]	|m68k		|Atari TT030, Falcon, Hades						|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[bebox]]	|powerpc	|Be Inc's BeBox								|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[cats]]	|arm		|Chalice Technology's Strong Arm evaluation board			|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[cesfic]]	|m68k		|CES's FIC8234 VME processor board					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[cobalt]]	|mips		|Cobalt Networks' Microservers						|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[dreamcast]]	|[[sh3]]	|Sega Dreamcast game console						|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[epoc32]]	|arm		|32bit PSION EPOC PDA							|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[emips]]	|mips		|Machines based on "Extensible MIPS"					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[evbsh3]]	|[[sh3]]	|Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs	|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[ews4800mips]]	|mips		|NEC's MIPS based EWS4800 workstations					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[hp300]]	|m68k		|Hewlett-Packard 9000/300 and 400 series				|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[hppa]]	|hppa		|Hewlett-Packard 9000/700 series					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[hpcmips]]	|mips		|MIPS based Windows CE PDA machines					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[hpcsh]]	|[[sh3]]	|Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines		|[9.0](http://www.netbsd.org/releases/formal-9/)
 [[ia64]]	|itanium	|Itanium family of processors						|none
-[[ibmnws]]	|powerpc	|IBM Network Station Series 1000					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[iyonix]]	|arm		|Iyonix ARM pc								|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[landisk]]	|[[sh3]]	|SH4 based NAS appliances by I-O DATA					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[luna68k]]	|m68k		|OMRON Tateisi Electronics' LUNA series					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[mac68k]]	|m68k		|Apple Macintosh							|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[macppc]]	|powerpc	|Apple Power Macintosh and clones					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[mipsco]]	|mips		|Mips family of workstations and servers				|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[mmeye]]	|[[sh3]]	|Brains' mmEye Multi Media Server					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[mvme68k]]	|m68k		|Motorola MVME 68k SBCs							|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[mvmeppc]]	|powerpc	|Motorola MVME PowerPC SBCs						|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[netwinder]]	|arm		|StrongARM based NetWinder machines					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[news68k]]	|arm		|Sony's m68k based "NET WORK STATION" series				|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[newsmips]]	|mips		|Sony's MIPS based "NET WORK STATION" series				|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[next68k]]	|m68k		|NeXT 68k 'black' hardware						|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[ofppc]]	|powerpc	|Generic OpenFirmware compliant PowerPC machines			|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[pmax]]	|mips		|Digital MIPS-based DECstations and DECsystems				|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[prep]]	|powerpc	|PReP (PowerPC Reference Platform) and CHRP machines			|[8.1](http://www.netbsd.org/releases/formal-8/)
+[[ibmnws]]	|powerpc	|IBM Network Station Series 1000					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[iyonix]]	|arm		|Iyonix ARM pc								|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[landisk]]	|[[sh3]]	|SH4 based NAS appliances by I-O DATA					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[luna68k]]	|m68k		|OMRON Tateisi Electronics' LUNA series					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[mac68k]]	|m68k		|Apple Macintosh							|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[macppc]]	|powerpc	|Apple Power Macintosh and clones					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[mipsco]]	|mips		|Mips family of workstations and servers				|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[mmeye]]	|[[sh3]]	|Brains' mmEye Multi Media Server					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[mvme68k]]	|m68k		|Motorola MVME 68k SBCs							|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[mvmeppc]]	|powerpc	|Motorola MVME PowerPC SBCs						|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[netwinder]]	|arm		|StrongARM based NetWinder machines					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[news68k]]	|arm		|Sony's m68k based "NET WORK STATION" series				|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[newsmips]]	|mips		|Sony's MIPS based "NET WORK STATION" series				|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[next68k]]	|m68k		|NeXT 68k 'black' hardware						|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[ofppc]]	|powerpc	|Generic OpenFirmware compliant PowerPC machines			|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[pmax]]	|mips		|Digital MIPS-based DECstations and DECsystems				|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[prep]]	|powerpc	|PReP (PowerPC Reference Platform) and CHRP machines			|[9.0](http://www.netbsd.org/releases/formal-9/)
 [[riscv]]	|riscv		|RISC-V									|none
-[[rs6000]]	|powerpc	|MCA-based IBM RS/6000 workstations					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[sandpoint]]	|powerpc	|Motorola Sandpoint reference platform					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[sbmips]]	|mips		|Broadcom SiByte evaluation boards					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[sgimips]]	|mips		|Silicon Graphics' MIPS-based workstations				|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[shark]]	|arm		|Digital DNARD ("shark")						|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[sparc]]	|sparc		|Sun SPARC (32-bit)							|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[sun2]]	|m68k		|Sun 2									|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[sun3]]	|m68k		|Sun 3 and 3x								|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[vax]]		|vax		|Digital VAX								|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[x68k]]	|m68k		|Sharp X680x0 series							|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[zaurus]]	|arm		|Sharp C7x0/C860/C1000/C3x00 series PDA					|[8.1](http://www.netbsd.org/releases/formal-8/)
+[[rs6000]]	|powerpc	|MCA-based IBM RS/6000 workstations					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[sandpoint]]	|powerpc	|Motorola Sandpoint reference platform					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[sbmips]]	|mips		|Broadcom SiByte evaluation boards					|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[sgimips]]	|mips		|Silicon Graphics' MIPS-based workstations				|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[shark]]	|arm		|Digital DNARD ("shark")						|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[sparc]]	|sparc		|Sun SPARC (32-bit)							|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[sun2]]	|m68k		|Sun 2									|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[sun3]]	|m68k		|Sun 3 and 3x								|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[vax]]		|vax		|Digital VAX								|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[x68k]]	|m68k		|Sharp X680x0 series							|[9.0](http://www.netbsd.org/releases/formal-9/)
+[[zaurus]]	|arm		|Sharp C7x0/C860/C1000/C3x00 series PDA					|[9.0](http://www.netbsd.org/releases/formal-9/)
 """]]
 
 
Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- wikisrc/releng.mdwn	2 Feb 2020 20:26:31 -0000	1.37
+++ wikisrc/releng.mdwn	14 Feb 2020 19:15:18 -0000	1.38
@@ -6,14 +6,13 @@
 
 ## Next Major Release
 
-The next major release will be NetBSD 9.0 (tentative release date: February 14, 2020)
+The next major release will be NetBSD 10.0 (not branched yet, no schedule)
 
-* Next release: NetBSD 9.0
+## Active Major Releases
+
+### NetBSD 9.0
   + 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
 
 ### NetBSD 8.x
 

Improve wording.
Index: wikisrc/security/kaslr.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/kaslr.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/security/kaslr.mdwn	29 Dec 2018 09:43:04 -0000	1.4
+++ wikisrc/security/kaslr.mdwn	14 Feb 2020 06:37:24 -0000	1.5
@@ -16,7 +16,7 @@
 the NetBSD FTP server, for example on:
 
 [[!template id=programlisting text="""
-https://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201812280800Z/amd64/binary/kernel/netbsd-GENERIC_KASLR.gz
+https://cdn.netbsd.org/pub/NetBSD/NetBSD-9.0_RC2/amd64/binary/kernel/netbsd-GENERIC_KASLR.gz
 """]]
 
 Or compiled from scratch, using:
@@ -26,7 +26,7 @@
 # ./build.sh kernel=GENERIC_KASLR
 """]]
 
-Install this KASLR kernel:
+Extract this KASLR kernel, and install it:
 
 [[!template id=programlisting text="""
 # cp /path/to/your/kaslr/kernel /netbsd_kaslr
@@ -49,8 +49,15 @@
 Technical Details
 -----------------
 
-Kernel ASLR is applied by default in GENERIC on as many VM areas as possible.
-GENERIC_KASLR provides randomization of one more area: the Kernel Image.
+"Kernel ASLR" means randomizing the location of the kernel memory areas.
+By default, in GENERIC, all areas are already randomized except one: the
+Kernel Image.
+
+The GENERIC_KASLR configuration provides randomization of this additional
+area.
+
+Therefore, it should be understood that GENERIC actually provides 80% of
+KASLR, and GENERIC_KASLR covers the remaining 20%.
 
 Table of what gets randomized:
 

Use web.archive.org for the BSDFreak article.
Broken links reported by Jay Patel, thanks!
Members: 
	pkgsrc/how_to_upgrade_packages.mdwn:1.6->1.7 

Index: wikisrc/pkgsrc/how_to_upgrade_packages.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/how_to_upgrade_packages.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/pkgsrc/how_to_upgrade_packages.mdwn	2 Sep 2019 21:15:38 -0000	1.6
+++ wikisrc/pkgsrc/how_to_upgrade_packages.mdwn	12 Feb 2020 10:00:36 -0000	1.7
@@ -190,7 +190,7 @@
 
 If you use PKGBASE instead of PKGNAME, you get the basename of the file.
 
-See [this BSDFreak Article](http://bsdfreak.org/modules/news/article.php?storyid=1) for a nice tutorial on how to set up and use pkg_comp.
+See [this BSDFreak Article](http://web.archive.org/web/20081002065622/http://www.bsdfreak.org/modules/news/article.php?storyid=1) for a nice tutorial on how to set up and use pkg_comp.
 
 ## bulk build framework
 

Update for new installer
Index: wikisrc/Installation_on_UEFI_systems.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/Installation_on_UEFI_systems.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/Installation_on_UEFI_systems.mdwn	26 Jul 2019 07:30:42 -0000	1.3
+++ wikisrc/Installation_on_UEFI_systems.mdwn	11 Feb 2020 11:03:02 -0000	1.4
@@ -1,10 +1,45 @@
-## Installing NetBSD 8.0 on a x86 system with UEFI
+# Installing NetBSD on a x86 system with UEFI
 
-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.
+Modern x86 machines have UEFI instead of BIOS firmware.
+The boot procedure is slightly different, and the installation needs to take care of this.
 
-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.
+Starting with NetBSD 9.0 the installer should be able to handle this automatically. Earlier NetBSD versions were able to boot in this setups, but needed a bit manual help to get everything installed.
 
-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.
+As of now NetBSD/amd64 provide separate images for installation, depending on how your machine boots. This will be integrated into a single image in the (near?) future. If you look at the <a href="//nycdn.NetBSD.org/pub/NetBSD-daily/HEAD/latest/images/">images</a> directory of your NetBSD release you will find 
+a `NetBSD-XXX-amd64-uefi-install.img.gz`, which is intended to be written to a USB disk and booted via UEFI. Alternatively there are `NetBSD-XXX-amd64-install.img.gz` and `NetBSD-XXX-i386-install.img.gz`, also intended to be written to USB sticks and booted via BIOS. Or if your machine has a DVD drive, there are `NetBSD-XXX-i386.iso` and `NetBSD-XXX-amd64.iso`, intended to be burned to a CD or DVD.
+
+Preparing the USB medium on NetBSD works like this:
+
+        # gunzip NetBSD-9.0-amd64-uefi-install.img.gz
+        # sudo dd if=NetBSD-9.0-amd64-uefi-install.img of=/dev/rsd0d bs=1m conv=sync
+
+If you do not (yet) have a NetBSD machine installed, you can use <a href="//www.NetBSD.org/~martin/rawrite32">Rawrite32</a> on a Windows machine.
+
+## Installing NetBSD 9.0 or newer on a x86 system with UEFI
+
+After booting from the USB stick there is nothing special you need to do to get UEFI booting set up properly. The installer will recognize the way you booted your install medium (either BIOS or UEFI) and prepare the installation on your hard disk for the same boot method.
+
+First you need to select the target disk. The installation USB stick will usually show up as sd0.
+
+![screenshot of sysinst disk selection](https://netbsd.org/images/misc/uefi/uefi9_01.png "Select Disk")
+
+Here we have an (artificially tiny) harddisk wd0 and select that as install target. In this setup the disk had been completely wiped before, so now we can choose what type of partitioning scheme we want to use. GPT is the more universal method, and also allows using disks of arbitrary size.
+
+![screenshot of sysinst partitioning scheme selection](https://netbsd.org/images/misc/uefi/uefi9_02.png "Select type of partitions")
+
+After the partitioning scheme selection (which will be skipped if the installer already finds valid partitions on your disk) you are presented size suggestions for the to-be-created NetBSD partitions.
+
+![screenshot of sysinst partition size display](https://netbsd.org/images/misc/uefi/uefi9_03.png "Partition Sizes")
+
+Details depend on the size of the target disk and available memory (swap is also used to store kernel crash dumps, so with more installed RAM the installer will suggest bigger swap partitions). Note the MSDOS partition on the above screenshot, it is used by UEFI instead of bootblocks to load the bootloader.
+
+Just continue the regular installation process from here - it should automatically create a UEFI bootable hard disk.
+
+## Installing NetBSD 8 on a x86 system with UEFI
+
+Unfortunately the installer on the netbsd-8 branch does not fully support an UEFI setup.
+
+The tutorial below shows (__only for NetBSD 8.x!__) 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
 

events->presentations, follow htdocs
(presentation link better)
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- wikisrc/templates/page.tmpl	3 Jan 2020 16:22:14 -0000	1.56
+++ wikisrc/templates/page.tmpl	10 Feb 2020 19:56:11 -0000	1.57
@@ -58,8 +58,8 @@
 		    Recent changes</a></li>
 	<li><a href="//blog.NetBSD.org/">
 		    NetBSD blog</a></li>
-	<li><a href="//www.NetBSD.org/gallery/events.html">
-		    Events</a></li>
+	<li><a href="//www.NetBSD.org/gallery/presentations/">
+		    Presentations</a></li>
 	</ul>
 	</li>
 	<li>

Add me as attendee
Index: wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn	8 Feb 2020 00:05:38 -0000	1.3
+++ wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn	9 Feb 2020 12:39:27 -0000	1.4
@@ -35,6 +35,7 @@
 Name Surname | `login@` | join |
 Jun Ebihara | `jun@` | join |
 Sevan Janiyan | `sevan@` | join |
+Ryo ONODERA | `ryoon@` | join |
 """]]
 
 ## Planning to present something?

count me in
Index: wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn	7 Feb 2020 00:56:11 -0000	1.2
+++ wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn	8 Feb 2020 00:05:38 -0000	1.3
@@ -34,6 +34,7 @@
 First Last | `login@` | join dinner? | comment(s)
 Name Surname | `login@` | join |
 Jun Ebihara | `jun@` | join |
+Sevan Janiyan | `sevan@` | join |
 """]]
 
 ## Planning to present something?
@@ -42,6 +43,7 @@
 Speaker  |Title
 `login@` |_Very Interesting Thing_
 `jun@` | Raspberry Pi and pinebook status update  [AsiaBSDCon2020 NetBSD travellers guide](http://www.re.soum.co.jp/~jun/AsiaBSDCon2020.pdf)
+`sevan@` | Something about getting pkgsrc through the door at $CORP
 """]]
 
 ## Discussions

mention that a Bourne style shell must be used
Index: wikisrc/tutorials/pkgsrc/pbulk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/pbulk.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/tutorials/pkgsrc/pbulk.mdwn	23 Oct 2018 12:19:51 -0000	1.15
+++ wikisrc/tutorials/pkgsrc/pbulk.mdwn	7 Feb 2020 02:22:35 -0000	1.16
@@ -66,9 +66,9 @@
 
 	# /path/to/your/sandbox/sandbox
 
-Create pbulk user
+Create pbulk user (a Bourne style shell must be used)
 
-	# useradd pbulk
+	# useradd pbulk -s /bin/sh
 
 In a file, set the preferences to use when building packages (mk.conf fragment).
 Here is a sample mk.conf.frag file:

add AsiaBSDCon2020 URL and netbsd-advocacy mail URL
Index: wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn	6 Feb 2020 12:18:27 -0000	1.1
+++ wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn	7 Feb 2020 00:56:11 -0000	1.2
@@ -5,8 +5,8 @@
 
 # NetBSD BoF 2020
 ------------------------------------------------------
-* Let's run a NetBSD BoF on AsiaBSDCon2020.
-* [announce on netbsd-advocacy](http://mail-index.netbsd.org/netbsd-advocacy/)
+* Let's run a NetBSD BoF on [AsiaBSDCon2020](https://2020.asiabsdcon.org/index.html.en).
+* [announce on netbsd-advocacy](http://mail-index.netbsd.org/netbsd-advocacy/2020/02/06/msg000824.html)
 * All BSD speakers are welcome (No AsiaBSDCon registration is required).
 * Day & time: 2020/3/20 (Friday)
   * 11:00-18:00(JST)

Move FOSDEM to past events
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.85
retrieving revision 1.86
diff -u -r1.85 -r1.86
--- wikisrc/events.mdwn	21 Jan 2020 13:40:05 -0000	1.85
+++ wikisrc/events.mdwn	6 Feb 2020 20:28:36 -0000	1.86
@@ -12,24 +12,6 @@
 
 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*
@@ -71,6 +53,24 @@
 
 Past 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.
+
+
 ### `Sep 2019` - EuroBSDcon 2019, Lillehammer, Norway
 
 *September 19 - 22, 2019, Scandic Lillehammer Hotel, Lillehammer, Norway*

AsiaBSDCon2020 NetBSD BoF Mar.20 2020 Tokyo
--- /dev/null	2020-02-06 12:19:02.909591542 +0000
+++ wikisrc/summits/AsiaBSDCon_2020_NetBSD_BoF.mdwn	2020-02-06 12:19:03.513604236 +0000
@@ -0,0 +1,49 @@
+<!-- we are supposed to use all lowercase letters in the link, so set a proper title for the page: -->
+
+[[!meta title="AsiaBSDCon 2020 NetBSD BoF"]]
+
+
+# NetBSD BoF 2020
+------------------------------------------------------
+* Let's run a NetBSD BoF on AsiaBSDCon2020.
+* [announce on netbsd-advocacy](http://mail-index.netbsd.org/netbsd-advocacy/)
+* All BSD speakers are welcome (No AsiaBSDCon registration is required).
+* Day & time: 2020/3/20 (Friday)
+  * 11:00-18:00(JST)
+  * 02:00-09:00(UTC)
+* Venue:
+  * Morito Memorial Hall
+* Live streaming URL: <https://2020.asiabsdcon.org/streaming_roomd.html.en>
+* Booth Report [NetBSD machines at AsiaBSDCon 2020](http://mail-index.netbsd.org/netbsd-advocacy/)
+ 
+# Dinner
+* After the BoF, we usually go to a bar or a restaurant near the venue.
+
+
+## Details
+
+add description here
+
+### NetBSD Dinner
+
+more description
+
+## Planning to attend?
+
+[[!table data="""
+First Last | `login@` | join dinner? | comment(s)
+Name Surname | `login@` | join |
+Jun Ebihara | `jun@` | join |
+"""]]
+
+## Planning to present something?
+
+[[!table data="""
+Speaker  |Title
+`login@` |_Very Interesting Thing_
+`jun@` | Raspberry Pi and pinebook status update  [AsiaBSDCon2020 NetBSD travellers guide](http://www.re.soum.co.jp/~jun/AsiaBSDCon2020.pdf)
+"""]]
+
+## Discussions
+
+## Varia

Add a comment