Recent changes to this wiki:

Mention restaurant we can go to, hours, myself coming late, etc.
Index: wikisrc/summits/eurobsdcon_2018.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2018.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/summits/eurobsdcon_2018.mdwn	12 Sep 2018 21:31:19 -0000	1.13
+++ wikisrc/summits/eurobsdcon_2018.mdwn	20 Sep 2018 13:01:30 -0000	1.14
@@ -5,7 +5,8 @@
 There will be a NetBSD developer summit, suggested
 date is the day before [EuroBSDCon](https://2018.eurobsdcon.org/) in Bucharest this year:
 
-Friday, 2018-09-21, time and place to be announced.
+Friday, 2018-09-21, [conference venue](https://2018.eurobsdcon.org/venue-location/), around 9:00 - 17:00
+Afterwards we can go to [Hanu' lui Manuc](https://www.hanumanucrestaurant.ro/en/) (we have a reservation for 19:00)
 
 ## Planning to attend?
 
@@ -19,7 +20,7 @@
 Yang Zheng | `@` |
 Siddharth Muralee | `@` |
 Stephen Borrill | `sborrill@` |
-Maya Rashish | `maya@` |
+Maya Rashish | `maya@` | arriving at 2pm
 Adrian Steinmann | `ast@` |
 Valery Ushakov | `uwe@` |
  | |

Add MeetBSDCA 2018
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -r1.66 -r1.67
--- wikisrc/events.mdwn	30 Aug 2018 21:21:10 -0000	1.66
+++ wikisrc/events.mdwn	19 Sep 2018 10:51:27 -0000	1.67
@@ -26,6 +26,16 @@
 facilitate coordination and cooperation among users and developers.
 
 
+### `Oct 2018` - MeetBSDCA 2018, Santa Clara, US
+
+*October 19 - 20, 2018, Intel Santa Clara Campus, California, US*
+
+[MeetBSD California](https://www.meetbsd.com/) is a biennial BSD
+Unix conference that takes place in Silicon Valley. The first
+MeetBSD California took place in 2008 and in 2018 it will take
+place at the Intel Santa Clara Campus.
+
+
 ### `Mar 2019` - AsiaBSDCon 2019, Tokyo, Japan
 
 *March 21 - 24, Tokyo University of Science, Tokyo, Japan*

Fix formatting in previous.
Index: wikisrc/summits/eurobsdcon_2018.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2018.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/summits/eurobsdcon_2018.mdwn	12 Sep 2018 21:30:26 -0000	1.12
+++ wikisrc/summits/eurobsdcon_2018.mdwn	12 Sep 2018 21:31:19 -0000	1.13
@@ -21,7 +21,7 @@
 Stephen Borrill | `sborrill@` |
 Maya Rashish | `maya@` |
 Adrian Steinmann | `ast@` |
-Valery Ushakov | | `uwe@` |
+Valery Ushakov | `uwe@` |
  | |
 """]]
 

Add myself.
Index: wikisrc/summits/eurobsdcon_2018.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2018.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/summits/eurobsdcon_2018.mdwn	29 Jul 2018 11:06:17 -0000	1.11
+++ wikisrc/summits/eurobsdcon_2018.mdwn	12 Sep 2018 21:30:26 -0000	1.12
@@ -21,6 +21,7 @@
 Stephen Borrill | `sborrill@` |
 Maya Rashish | `maya@` |
 Adrian Steinmann | `ast@` |
+Valery Ushakov | | `uwe@` |
  | |
 """]]
 

Use web.archive.org for no longer available ONLamp article.
From and thanks to yambo via #NetBSD@Freenode!
Members: 
	how_netbsd_boots_on_x86.mdwn:1.3->1.4 

Index: wikisrc/how_netbsd_boots_on_x86.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/how_netbsd_boots_on_x86.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/how_netbsd_boots_on_x86.mdwn	27 May 2013 09:21:34 -0000	1.3
+++ wikisrc/how_netbsd_boots_on_x86.mdwn	10 Sep 2018 07:59:13 -0000	1.4
@@ -80,7 +80,7 @@
 
 ##  See also
 
-  * [Making NetBSD Multiboot-Compatible](http://onlamp.com/pub/a/bsd/2007/03/01/inside-multiboot.html)
+  * [Making NetBSD Multiboot-Compatible](https://web.archive.org/web/20180218133134/http://onlamp.com/pub/a/bsd/2007/03/01/inside-multiboot.html)
 
 ##  References
 

elaborate
Index: wikisrc/projects/project/wine_amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/wine_amd64.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/wine_amd64.mdwn	13 Feb 2018 12:50:20 -0000	1.4
+++ wikisrc/projects/project/wine_amd64.mdwn	6 Sep 2018 14:57:51 -0000	1.5
@@ -26,13 +26,18 @@
 
 Milestones:
 
- * Make Wine32 work on amd64. As a first shot, it should be possible to compile
-   Wine32 on NetBSD-i386, and launch it on NetBSD-amd64 (which supports running
-   native 32bit binaries). At this stage, old Windows video games should work.
+ * Test a static Wine32 on amd64. That is, compile Wine32 statically on
+   NetBSD-i386, and launch it on NetBSD-amd64 (which supports running native
+   32bit binaries). See if it works, and if not, apply the necessary fixes.
+   At this stage, old Windows video games should work.
+ * Make a dynamic Wine32 work on amd64. Compile Wine32 on NetBSD-i386 in
+   a non-static way, and launch it on NetBSD-amd64.
  * Make Wine32+Wine64 work on amd64. See the WineHQ wiki on how to achieve
    this. At this stage, 64bit Windows binaries that use 32bit libraries should
    work.
  * Package Wine32+Wine64 for pkgsrc.
+
+Note that reaching the first step is already good.
 """
 ]]
 

give people a stronger chance if we get a debugger that can handle firefox.
Index: wikisrc/tutorials/pkgsrc/debugging_firefox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/debugging_firefox.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/tutorials/pkgsrc/debugging_firefox.mdwn	30 Jul 2014 11:37:59 -0000	1.1
+++ wikisrc/tutorials/pkgsrc/debugging_firefox.mdwn	6 Sep 2018 01:23:09 -0000	1.2
@@ -36,8 +36,9 @@
 
 After building the pkg, you can use files in the obj/workdir to run this firefox inside gdb. But first make sure to not have any remaining firefox instances running, as those would cause just another window to open but running the non-debugable code version of the already running instance.
 
-You have to locate your pkgsrc work directory for this pkg, which could be for example `pkgsrc/www/firefox/work`, or if you have set WRKOBJDIR to a special directory, something like: `/usr/pkgobj/www/firefox/work`. Assuming the latter, now cd to the `build/dist/bin` directory inside it and invoke the helper shell script `run-mozilla.sh` with `-g` option:
+You have to locate your pkgsrc work directory for this pkg, which could be for example `pkgsrc/www/firefox/work`, or if you have set WRKOBJDIR to a special directory, something like: `/usr/pkgobj/www/firefox/work`. Assuming the latter, now cd to the `build/dist/bin` directory inside it, and invoke the helper shell script `run-mozilla.sh` with `-g` option:
 
+    [/usr/pkgobj/www/firefox/work/build/dist/bin] martin@night-owl > paxctl +m ./firefox
     [/usr/pkgobj/www/firefox/work/build/dist/bin] martin@night-owl > ./run-mozilla.sh -g ./firefox
     MOZILLA_FIVE_HOME=.
       LD_LIBRARY_PATH=.:./plugins:.

rename one section, for consistency
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.160
retrieving revision 1.161
diff -u -r1.160 -r1.161
--- wikisrc/ports/xen/howto.mdwn	5 Sep 2018 09:37:37 -0000	1.160
+++ wikisrc/ports/xen/howto.mdwn	5 Sep 2018 09:39:39 -0000	1.161
@@ -83,7 +83,7 @@
 [faster](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)
 than amd64.
 
-#NetBSD as a dom0
+#Creating a dom0
 
 In order to install a NetBSD as a dom0, one must first install a normal
 NetBSD system, and then pivot the install to a dom0 install by changing

more noise reduction, and also add a summary at the beginning
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.159
retrieving revision 1.160
diff -u -r1.159 -r1.160
--- wikisrc/ports/xen/howto.mdwn	5 Sep 2018 09:25:10 -0000	1.159
+++ wikisrc/ports/xen/howto.mdwn	5 Sep 2018 09:37:37 -0000	1.160
@@ -33,12 +33,9 @@
 installing software from pkgsrc.  See also the [Xen
 website](http://www.xenproject.org/).
 
-This HOWTO attempts to address both the case of running a NetBSD dom0
-on hardware and running domUs under it (NetBSD and other), and also
-running NetBSD as a domU in a VPS.
+[[!toc]]
 
-Versions and Support
-====================
+#Versions and Support
 
 In NetBSD, Xen is provided in pkgsrc, via matching pairs of packages
 xenkernel and xentools.  We will refer only to the kernel versions,
@@ -86,8 +83,7 @@
 [faster](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)
 than amd64.
 
-NetBSD as a dom0
-================
+#NetBSD as a dom0
 
 In order to install a NetBSD as a dom0, one must first install a normal
 NetBSD system, and then pivot the install to a dom0 install by changing
@@ -269,8 +265,7 @@
 xenkernel version and copy the new xen.gz to `/` (where `/boot.cfg`
 references it), and reboot.
 
-Unprivileged domains (domU)
-===========================
+#Unprivileged domains (domU)
 
 This section describes general concepts about domUs.  It does not
 address specific domU operating systems or how to install them.  The
@@ -429,8 +424,7 @@
 xendomains="domU-netbsd domU-linux"
 """]]
 
-Creating a domU
-===============
+#Creating a domU
 
 Creating domUs is almost entirely independent of operating system.  We
 have already presented the basics of config files.  Note that you must
@@ -629,8 +623,7 @@
         cd*     at scsibus? target ? lun ?      # SCSI CD-ROM drives
 
 
-NetBSD as a domU in a VPS
-=========================
+#NetBSD as a domU in a VPS
 
 The bulk of the HOWTO is about using NetBSD as a dom0 on your own
 hardware.  This section explains how to deal with Xen in a domU as a
@@ -695,13 +688,3 @@
 ------
 
 See the [Amazon EC2 page](/amazon_ec2/).
-
-Random pointers
-===============
-
-This section contains links from elsewhere not yet integrated into the
-HOWTO, and other guides.
-
-* http://www.lumbercartel.ca/library/xen/
-* http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html
-* https://gmplib.org/~tege/xen.html

Remove "How to set up a Xen Dom0 running NetBSD 6.1". Replaced by the Xen
HowTo, now that the noise has been considerably reduced.
--- wikisrc/tutorials/how_to_set_up_a_xen_dom0.mdwn	2018-09-05 09:31:01.000000000 +0000
+++ /dev/null	2018-09-05 09:31:01.000000000 +0000
@@ -1,66 +0,0 @@
-[[!meta title="How to set up a Xen Dom0 running NetBSD 6.1"]]
-
-Meta
-====
-
-Note that there is also a [Xen HOWTO](../../ports/xen/howto/).
-Arguably this content could be folded in there.
-
-HOWTO
-=====
-
-Here's how to install and get a dom0 running in the simplest way.
-It's not as simple as it could be, but it's pretty fast compared
-to older methods. We hope to fix the system installer for NetBSD
-7.0 so it can all be done from there.
-
-STEPS:
-
-1) boot a 6.1 install image.  I'm booting the CD-ROM image,
-NetBSD-6.1-amd64.iso .
-
-2) Perform a normal amd64 install.  At the end of the install,
-there is a "configure additional items as needed" menu.  Choose
-"e", "Enable installation of binary packages". (This requires that
-the network be available)
-
-3) reboot the newly installed system, and log in as root.
-
-4) Install the Xen binary packages using pkgin (assuming the network
-is configured):
-
-    # pkgin install xentools41
-    <answer Y when asked to install dependencies>
-
-    # pkgin install xenkernel41
-    <answer Y>
-
-5) install a dom0 netbsd kernel that Xen can load:
-
-    cd / && ftp http://ftp.netbsd.org/pub/NetBSD/NetBSD-6.1/amd64/binary/kernel/netbsd-XEN3_DOM0.gz
-
-6) Edit /boot.cfg to add Xen Dom0 as an option at boot time
-
-Add the following line:
-
-    menu=Boot Xen:load /netbsd-XEN3_DOM0.gz console=pc; multiboot /usr/pkg/xen41-kernel/xen.gz dom0_mem=512M
-
-(you may also want to increase the default timeout from 5sec to
-30sec to make choosing "Xen" easier)
-
-7) Copy the boot scripts from /usr/pkg/share/examples/rc.d :
-
-    # cp /usr/pkg/share/examples/rc.d/xen* /etc/rc.d
-
-(The default *should* be to install these files when installing a
-pkg, but it isn't yet.  )
-
-8) edit /etc/rc.conf and add the following lines:
-
-    xencommons=YES
-    xend=YES
-
-9) reboot and choose "Boot Xen" from the menu.  (You can make it
-the default by editing /boot.cfg)
-
-10) demonstrate you're running a dom0 by doing "xm list" at a root prompt.
--- wikisrc/tutorials/how_to_set_up_a_xen_dom0/comment_1_d777e91d6edf0406555ad805d6270c65._comment	2018-09-05 09:31:01.000000000 +0000
+++ /dev/null	2018-09-05 09:31:01.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="spz"
- ip="2001:a60:f000:67::2"
- subject="automatically installing rc scripts"
- date="2013-10-03T14:14:36Z"
- content="""
-it's not \"obviously and always good\" to install rc scripts automatically; otherwise you'd eg have xencommons in rc.d on a machine that is supposed to control other systems without being a Xen server itself (there are other examples like that in pkgsrc). Thus, I disagree with the \"should be installed automatically, it's an error that they don't\" sentiment.
-"""]]
--- wikisrc/tutorials/how_to_set_up_a_xen_dom0/comment_2_b024b470d056743d507c87e1c055d090._comment	2018-09-05 09:31:01.000000000 +0000
+++ /dev/null	2018-09-05 09:31:01.000000000 +0000
@@ -1,15 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawlLYXNcaa6_fHcRVVxo3Rik5VJzW9ONTtA"
- nickname="Raimundo"
- subject="Why not /usr/pkg/etc/rc.d?"
- date="2014-04-28T02:31:46Z"
- content="""
-Hello,
-
-nice to see a more updated Xen how to.
-
-But I am curious on that: why not use /usr/pkg/etc/rc.d instead of polluting /etc/rc.d with third part scripts?
-
-Thank you,
-Raimundo Santos
-"""]]
--- wikisrc/tutorials/how_to_set_up_a_xen_dom0/comment_3_4869b54ac386c98c7ef8a6d3159d2315._comment	2018-09-05 09:31:01.000000000 +0000
+++ /dev/null	2018-09-05 09:31:01.000000000 +0000
@@ -1,9 +0,0 @@
-[[!comment format=mdwn
- username="schnoebe"
- subject="/boot.cfg entry"
- date="2017-02-20T02:30:54Z"
- content="""
-I can't imagine the specified /boot.cfg entry, with a path going into /usr/pkg/... can really be found by boot.  All previous tutorials and how-to's specify copying .../xen*-kernel/xen.gz into the root directory.
-
-The number of users having problems following the advice on the boot.cfg entry suggests that /boot can't traverse the directory tree deep enough to find xen.gz, even assuming /usr/pkg is on the same filesystem as /.
-"""]]

improve a bit
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.158
retrieving revision 1.159
diff -u -r1.158 -r1.159
--- wikisrc/ports/xen/howto.mdwn	5 Sep 2018 09:16:10 -0000	1.158
+++ wikisrc/ports/xen/howto.mdwn	5 Sep 2018 09:25:10 -0000	1.159
@@ -115,8 +115,13 @@
 # cp /usr/pkg/xen48-kernel/xen.gz /
 """]]
 
-Then, place a NetBSD XEN3_DOM0 kernel in the `/` directory, copied from
-`releasedir/amd64/binary/kernel/netbsd-XEN3_DOM0.gz` of a NetBSD build.
+Then, place a NetBSD XEN3_DOM0 kernel in the `/` directory. Such kernel
+can either be compiled manually, or downloaded from the NetBSD FTP, for
+example at:
+
+[[!template id=programlisting text="""
+ftp.netbsd.org/pub/NetBSD/NetBSD-8.0/amd64/binary/kernel/netbsd-XEN3_DOM0.gz
+"""]]
 
 Add a line to /boot.cfg to boot Xen:
 
@@ -124,8 +129,8 @@
 menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=512M
 """]]
 
-which specifies that the dom0 should have 512MB of ram, leaving the rest
-to be allocated for domUs.  To use a serial console, use
+This specifies that the dom0 should have 512MB of ram, leaving the rest
+to be allocated for domUs.  To use a serial console, use:
 
 [[!template id=filecontent name="/boot.cfg" text="""
 menu=Xen:load /netbsd-XEN3_DOM0.gz;multiboot /xen.gz dom0_mem=512M console=com1 com1=9600,8n1
@@ -145,6 +150,12 @@
 and other than dom0 memory and max_vcpus, they are generally not
 necessary.
 
+Copy the boot scripts into `/etc/rc.d`:
+
+[[!template id=programlisting text="""
+# cp /usr/pkg/share/examples/rc.d/xen* /etc/rc.d/
+"""]]
+
 Enable `xencommons`:
 
 [[!template id=filecontent name="/etc/rc.conf" text="""

noise reduction police, and clarify a few things
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.157
retrieving revision 1.158
diff -u -r1.157 -r1.158
--- wikisrc/ports/xen/howto.mdwn	27 Aug 2018 16:54:42 -0000	1.157
+++ wikisrc/ports/xen/howto.mdwn	5 Sep 2018 09:16:10 -0000	1.158
@@ -89,31 +89,14 @@
 NetBSD as a dom0
 ================
 
-NetBSD can be used as a dom0 and works very well.  The following
-sections address installation, updating NetBSD, and updating Xen.
-
-Note that it doesn't make sense to talk about installing a dom0 OS
-without also installing Xen itself.  We first address installing
-NetBSD, which is not yet a dom0, and then adding Xen, pivoting the
-NetBSD install to a dom0 install by just changing the kernel and boot
-configuration.
+In order to install a NetBSD as a dom0, one must first install a normal
+NetBSD system, and then pivot the install to a dom0 install by changing
+the kernel and boot configuration.
 
 In 2018-05, trouble booting a dom0 was reported with 256M of RAM: with
 512M it worked reliably.  This does not make sense, but if you see
 "not ELF" after Xen boots, try increasing dom0 RAM.
 
-Styles of dom0 operation
-------------------------
-
-There are two basic ways to use Xen.  The traditional method is for
-the dom0 to do absolutely nothing other than providing support to some
-number of domUs.  Such a system was probably installed for the sole
-purpose of hosting domUs, and sits in a server room on a UPS.
-
-The other way is to put Xen under a normal-usage computer, so that the
-dom0 is what the computer would have been without Xen, perhaps a
-desktop or laptop.  Then, one can run domUs at will.
-
 Installation of NetBSD
 ----------------------
 
@@ -125,7 +108,6 @@
 
 We will consider that you chose to use Xen 4.8, with NetBSD/amd64 as
 dom0. In the dom0, install xenkernel48 and xentools48 from pkgsrc.
-Ensure that your packages are recent.
 
 Once this is done, install the Xen kernel itself:
 
@@ -158,39 +140,23 @@
 
 In an attempt to add performance, one can also add `dom0_max_vcpus=1 dom0_vcpus_pin`,
 to force only one vcpu to be provided (since NetBSD dom0 can't use
-more) and to pin that vcpu to a physical CPU.
-
-Xen has [many boot
-options](http://xenbits.xenproject.org/docs/4.5-testing/misc/xen-command-line.html),
+more) and to pin that vcpu to a physical CPU. Xen has
+[many boot options](http://xenbits.xenproject.org/docs/4.8-testing/misc/xen-command-line.html),
 and other than dom0 memory and max_vcpus, they are generally not
 necessary.
 
-Now, reboot so that you are running a DOM0 kernel under Xen, rather
-than GENERIC without Xen.
-
-Configuring Xen
----------------
-
-Now, you have a system that will boot Xen and the dom0 kernel, but not
-do anything else special.  Make sure that you have rebooted into Xen.
-There will be no domUs, and none can be started because you still have
-to configure the dom0 daemons.
-
-Since Xen 4.2, the tool which should be used is `xl`.
-
-For 4.1 and up, you should enable `xencommons`:
+Enable `xencommons`:
 
 [[!template id=filecontent name="/etc/rc.conf" text="""
 xencommons=YES
 """]]
 
-Not enabling xencommons will result in a hang; it is necessary to hit `^C` on
-the console to let the machine finish booting:
+Now, reboot so that you are running a DOM0 kernel under Xen, rather
+than GENERIC without Xen.
 
 TODO: Recommend for/against xen-watchdog.
 
-After you have configured the daemons and either started them (in the
-order given) or rebooted, use `xl` to inspect Xen's boot messages,
+Once the reboot is done, use `xl` to inspect Xen's boot messages,
 available resources, and running domains.  For example:
 
 [[!template id=programlisting text="""
@@ -311,11 +277,7 @@
 Config files
 ------------
 
-There is no good order to present config files and the concepts
-surrounding what is being configured.  We first show an example config
-file, and then in the various sections give details.
-
-See /usr/pkg/share/examples/xen/xmexample*,
+See /usr/pkg/share/examples/xen/xlexample*,
 for a large number of well-commented examples, mostly for running
 GNU/Linux.
 
@@ -359,21 +321,6 @@
 power-press event and do a clean shutdown.  Shutting down the dom0
 will trigger controlled shutdowns of all configured domUs.
 
-domU kernels
-------------
-
-On a physical computer, the BIOS reads sector 0, and a chain of boot
-loaders finds and loads a kernel.  Normally this comes from the root
-file system.  With Xen domUs, the process is totally different.  The
-normal path is for the domU kernel to be a file in the dom0's
-file system.  At the request of the dom0, Xen loads that kernel into a
-new domU instance and starts execution. domU kernels can be anyplace.
-
-Note that loading the domU kernel from the dom0 implies that boot
-blocks, /boot, /boot.cfg, and so on are all ignored in the domU.
-See the VPS section near the end for discussion of alternate ways to
-obtain domU kernels.
-
 CPU and memory
 --------------
 
@@ -392,50 +339,34 @@
 Virtual disks
 -------------
 
-With the file/vnd style, typically one creates a directory,
-e.g. /u0/xen, on a disk large enough to hold virtual disks for all
-domUs.  Then, for each domU disk, one writes zeros to a file that then
-serves to hold the virtual disk's bits; a suggested name is foo-xbd0
-for the first virtual disk for the domU called foo.  Writing zeros to
-the file serves two purposes.  One is that preallocating the contents
-improves performance.  The other is that vnd on sparse files has
-failed to work.  TODO: give working/notworking NetBSD versions for
-sparse vnd and gnats reference.  Note that the use of file/vnd for Xen
-is not really different than creating a file-backed virtual disk for
-some other purpose, except that xentools handles the vnconfig
-commands.  To create an empty 4G virtual disk, simply do
-
-        dd if=/dev/zero of=foo-xbd0 bs=1m count=4096
-
-Do not use qemu-img-xen, because this will create sparse file.  There
-have been recent (2015) reports of sparse vnd(4) devices causing
-lockups, but there is apparently no PR.
-
-With the lvm style, one creates logical devices.  They are then used
-similarly to vnds.  TODO: Add an example with lvm.
-
-In domU config files, the disks are defined as a sequence of 3-tuples.
-The first element is "method:/path/to/disk".  Common methods are
-"file:" for file-backed vnd. and "phy:" for something that is already
-a (TODO: character or block) device.
-
-The second element is an artifact of how virtual disks are passed to
-Linux, and a source of confusion with NetBSD Xen usage.  Linux domUs
-are given a device name to associate with the disk, and values like
-"hda1" or "sda1" are common.  In a NetBSD domU, the first disk appears
-as xbd0, the second as xbd1, and so on.  However, xm/xl demand a
-second argument.  The name given is converted to a major/minor by
-calling stat(2) on the name in /dev and this is passed to the domU.
-In the general case, the dom0 and domU can be different operating
-systems, and it is an unwarranted assumption that they have consistent
-numbering in /dev, or even that the dom0 OS has a /dev.  With NetBSD
-as both dom0 and domU, using values of 0x0 for the first disk and 0x1
-for the second works fine and avoids this issue.  For a GNU/Linux
-guest, one can create /dev/hda1 in /dev, or to pass 0x301 for
-/dev/hda1.
+In domU config files, the disks are defined as a sequence of 3-tuples:
+
+ * The first element is "method:/path/to/disk". Common methods are
+   "file:" for file-backed vnd, and "phy:" for something that is already
+   a device.
+
+ * The second element is an artifact of how virtual disks are passed to
+   Linux, and a source of confusion with NetBSD Xen usage.  Linux domUs
+   are given a device name to associate with the disk, and values like
+   "hda1" or "sda1" are common.  In a NetBSD domU, the first disk appears
+   as xbd0, the second as xbd1, and so on.  However, xl demands a
+   second argument.  The name given is converted to a major/minor by
+   calling stat(2) on the name in /dev and this is passed to the domU.
+   In the general case, the dom0 and domU can be different operating
+   systems, and it is an unwarranted assumption that they have consistent
+   numbering in /dev, or even that the dom0 OS has a /dev.  With NetBSD
+   as both dom0 and domU, using values of 0x0 for the first disk and 0x1
+   for the second works fine and avoids this issue.  For a GNU/Linux
+   guest, one can create /dev/hda1 in /dev, or to pass 0x301 for
+   /dev/hda1.
 
-The third element is "w" for writable disks, and "r" for read-only
-disks.

(Diff truncated)
Updates for 7.2 release
Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- wikisrc/releng.mdwn	23 Aug 2018 07:05:12 -0000	1.32
+++ wikisrc/releng.mdwn	2 Sep 2018 14:14:10 -0000	1.33
@@ -16,15 +16,17 @@
 
 ### NetBSD 8.x
 
-* Next minor release: NetBSD 8.1 (No release date proposed)
+* Next minor release: NetBSD 8.1 (provisionaly scheduled for October 2018)
   + 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.2 (No release date proposed)
+* 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)

Respect the syntax of WikiLink.
Index: wikisrc/projects/project/sgimips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sgimips.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/sgimips.mdwn	31 Aug 2018 21:24:24 -0000	1.4
+++ wikisrc/projects/project/sgimips.mdwn	31 Aug 2018 21:26:27 -0000	1.5
@@ -13,6 +13,6 @@
 NetBSD/sgimips currently runs on a number of SGI hardware, but support for IP27
 (Origin) and IP30 (Octane) is not yet available.
 
-See also [[ports/sgimips|NetBSD/sgimips]].
+See also [[NetBSD/sgimips|ports/sgimips]].
 """
 ]]

Fix the link to the sgimips port page.
Spottend and thanks to <jschauma>!
Members: 
	projects/project/sgimips.mdwn:1.3->1.4 

Index: wikisrc/projects/project/sgimips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sgimips.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/sgimips.mdwn	31 Aug 2018 21:19:19 -0000	1.3
+++ wikisrc/projects/project/sgimips.mdwn	31 Aug 2018 21:24:24 -0000	1.4
@@ -13,6 +13,6 @@
 NetBSD/sgimips currently runs on a number of SGI hardware, but support for IP27
 (Origin) and IP30 (Octane) is not yet available.
 
-See also [NetBSD/sgimips](../ports/sgimips/).
+See also [[ports/sgimips|NetBSD/sgimips]].
 """
 ]]

Remove the sentence about a possible available Octane for development.
Requested by <jschauma> via www@.
Members: 
	projects/project/sgimips.mdwn:1.2->1.3 

Index: wikisrc/projects/project/sgimips.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sgimips.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/sgimips.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/sgimips.mdwn	31 Aug 2018 21:19:19 -0000	1.3
@@ -11,9 +11,7 @@
 
 description="""
 NetBSD/sgimips currently runs on a number of SGI hardware, but support for IP27
-(Origin) and IP30 (Octane) is not yet available.  An Octane for development is
-available for pickup in Hoboken, NJ (contact Jan Schaumann jschauma AT
-NetBSD.org).
+(Origin) and IP30 (Octane) is not yet available.
 
 See also [NetBSD/sgimips](../ports/sgimips/).
 """

Link to the NetBSD developer summits
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -r1.65 -r1.66
--- wikisrc/events.mdwn	17 Jul 2018 07:51:25 -0000	1.65
+++ wikisrc/events.mdwn	30 Aug 2018 21:21:10 -0000	1.66
@@ -7,6 +7,8 @@
 For a list of NetBSD-related presentations, please check out our
 [presentation pages](//www.NetBSD.org/gallery/presentations/).
 
+See also the NetBSD [[developer summits|summits]].
+
 
 Future Events
 -------------

More consistency
Index: wikisrc/index.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/index.mdwn,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- wikisrc/index.mdwn	30 Aug 2018 21:10:57 -0000	1.62
+++ wikisrc/index.mdwn	30 Aug 2018 21:13:17 -0000	1.63
@@ -15,14 +15,14 @@
 
 * [[Events|events]] -- NetBSD related events are listed here
 * [[Summits]] -- Stories from past NetBSD Developer summits
-* [blog](//blog.netbsd.org) -- Weblog
+* [Blog](//blog.netbsd.org) -- Weblog
 * [[Tutorials]] -- Guides & Docs (some from the former user-wiki)
 * [[Features]] -- Features of the NetBSD Operating System
-* [[Projects]] -- The big list of work.  Get hacking!
-* [[pkgsrc]] -- pkgsrc docs - the NetBSD package manager
-* [[releng]] -- release engineering
+* [[Projects]] -- The big list of work. Get hacking!
+* [[pkgsrc]] -- pkgsrc docs - The NetBSD package manager
+* [[releng]] -- Release engineering
 * [[Security|security]] -- Security features and hardening
-* [[Users]] -- developer sandbox pages
-* [[Community|community]] -- known community resources
+* [[Users]] -- Developer sandbox pages
+* [[Community|community]] -- Known community resources
 * [[Amazon EC2|amazon_ec2]] -- NetBSD on amazon's EC2
 * [[Ports]] -- NetBSD on your hardware

Consistency
Index: wikisrc/index.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/index.mdwn,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -r1.61 -r1.62
--- wikisrc/index.mdwn	10 Sep 2017 13:36:13 -0000	1.61
+++ wikisrc/index.mdwn	30 Aug 2018 21:10:57 -0000	1.62
@@ -21,8 +21,8 @@
 * [[Projects]] -- The big list of work.  Get hacking!
 * [[pkgsrc]] -- pkgsrc docs - the NetBSD package manager
 * [[releng]] -- release engineering
-* [[security]] -- Security features and hardening
+* [[Security|security]] -- Security features and hardening
 * [[Users]] -- developer sandbox pages
 * [[Community|community]] -- known community resources
-* [[amazon_ec2]] -- NetBSD on amazon's EC2
+* [[Amazon EC2|amazon_ec2]] -- NetBSD on amazon's EC2
 * [[Ports]] -- NetBSD on your hardware

briefly say that GENERIC does ASLR on kernel memory already
Index: wikisrc/security/kaslr.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/kaslr.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/security/kaslr.mdwn	2 Aug 2018 17:24:41 -0000	1.1
+++ wikisrc/security/kaslr.mdwn	28 Aug 2018 13:11:52 -0000	1.2
@@ -46,6 +46,24 @@
 To use KASLR, just choose the "Boot KASLR" option in the menu at boot
 time. That's it!
 
+Technical Details
+-----------------
+
+Kernel ASLR is applied by default in GENERIC on as many VM areas as possible.
+GENERIC_KASLR offers randomization of one more area: the Kernel Image.
+
+Table of what gets randomized:
+
+[[!table data="""
+Memory Region		|GENERIC		|GENERIC_KASLR		|Xen dom0/domU
+Userland		|Yes			|Yes			|Yes
+PTE Area		|Yes			|Yes			|No
+Main Kernel Memory	|Yes			|Yes			|Yes
+Direct Map		|Yes			|Yes			|[Not Applicable]
+PCPU Area		|[Not Applicable]	|[Not Applicable]	|[Not Applicable]
+Kernel Image		|No			|Yes			|No
+"""]]
+
 Technical Resources
 -------------------
 

Noise reduction again, and use ikiwiki markers to improve the style.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.156
retrieving revision 1.157
diff -u -r1.156 -r1.157
--- wikisrc/ports/xen/howto.mdwn	25 Aug 2018 09:42:48 -0000	1.156
+++ wikisrc/ports/xen/howto.mdwn	27 Aug 2018 16:54:42 -0000	1.157
@@ -1,16 +1,12 @@
 [[!meta title="Xen HowTo"]]
 
-Introduction
-============
-
-Xen is a hypervisor for x86 hardware, which supports running multiple guest
-operating systems on a single physical machine.  Xen is a Type 1 or
-bare-metal hypervisor; one uses the Xen kernel to control the CPU,
-memory and console, a dom0 operating system which mediates access to
-other hardware (e.g., disks, network, USB), and one or more domU
-operating systems which operate in an unprivileged virtualized
-environment.  IO requests from the domU systems are forwarded by the
-Xen hypervisor to the dom0 to be fulfilled.
+Xen is a Type 1 hypervisor which supports running multiple guest operating
+systems on a single physical machine. One uses the Xen kernel to control the
+CPU, memory and console, a dom0 operating system which mediates access to
+other hardware (e.g., disks, network, USB), and one or more domU operating
+systems which operate in an unprivileged virtualized environment. IO requests
+from the domU systems are forwarded by the Xen hypervisor to the dom0 to be
+fulfilled.
 
 Xen supports different styles of guest:
 
@@ -41,20 +37,8 @@
 on hardware and running domUs under it (NetBSD and other), and also
 running NetBSD as a domU in a VPS.
 
-Versions of Xen and NetBSD
-==========================
-
-Most of the installation concepts and instructions are independent
-of Xen version and NetBSD version.  This section gives advice on
-which version to choose.  Versions not in pkgsrc and older unsupported
-versions of NetBSD are intentionally ignored.
-
-The term "amd64" is used to refer to both the NetBSD port and to the
-hardware architecture on which it runs.  Such hardware is generally
-made by both Intel and AMD, and common on PC computers.
-
-Xen versions
-------------
+Versions and Support
+====================
 
 In NetBSD, Xen is provided in pkgsrc, via matching pairs of packages
 xenkernel and xentools.  We will refer only to the kernel versions,
@@ -74,20 +58,13 @@
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 
-Note: Xen 4.2 was the last version to support 32bit CPUs.
-
-NetBSD versions
----------------
-
-NetBSD 8 is recommended as the stable version of the most recent
-release for production use.
-
-For developing Xen, netbsd-current may be appropriate.
+Multiprocessor (SMP) support in NetBSD differs depending on the domain:
 
-As of NetBSD 6, a NetBSD domU will support multiple vcpus.  There is
-no SMP support for NetBSD as dom0.  (The dom0 itself doesn't really
-need SMP for dom0 functions; the lack of support is really a problem
-when using a dom0 as a normal computer.)
+[[!table data="""
+Domain		|Supports SMP
+dom0		|No
+domU		|Yes
+"""]]
 
 Note: NetBSD support is called XEN3. However, it does support Xen 4,
 because the hypercall interface has remained identical.
@@ -95,47 +72,32 @@
 Architecture
 ------------
 
-Xen itself runs on amd64 hardware. Practically, almost any computer
-where one would want to run Xen today supports amd64.
+Xen itself runs on x86_64 hardware.
 
 The dom0 system, plus each domU, can be either i386PAE or amd64.
 i386 without PAE is not supported.
 
-The standard approach is to use NetBSD/amd64 for the dom0.  For domUs,
-NetBSD/i386 (PAE) and NetBSD/amd64 are in widespread use, and there is
-little to no Xen-specific reason to prefer one over the other.
-
-Note that to use an i386 dom0 with Xen 4.5 or higher, one must build
-(or obtain from pre-built packages) an amd64 Xen kernel and install
-that on the system.  Almost no one in the NetBSD/Xen community does
-this, and the standard, well-tested, approach is to use an amd64 dom0.
-
-A [posting on
-xen-devel](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)
-explained that PV system call overhead was higher on amd64, and thus
-there is some notion that i386 guests are faster.  It goes on to
-caution that the total situation is complex and not entirely
-understood. On top of that caution, the post is about Linux, not
-NetBSD.
+The standard approach is to use NetBSD/amd64 for the dom0.
+
+To use an i386PAE dom0, one must build or obtain a 64bit Xen kernel and
+install it on the system.
+
+For domUs, i386PAE is considered as
+[faster](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)
+than amd64.
 
 NetBSD as a dom0
 ================
 
 NetBSD can be used as a dom0 and works very well.  The following
 sections address installation, updating NetBSD, and updating Xen.
+
 Note that it doesn't make sense to talk about installing a dom0 OS
 without also installing Xen itself.  We first address installing
 NetBSD, which is not yet a dom0, and then adding Xen, pivoting the
 NetBSD install to a dom0 install by just changing the kernel and boot
 configuration.
 
-For experimenting with Xen, a machine with as little as 1G of RAM and
-100G of disk can work.  For running many domUs in productions, far
-more will be needed; e.g. 4-8G and 1T of disk is reasonable for a
-half-dozen domUs of 512M and 32G each.  Basically, the RAM and disk
-have to be bigger than the sum of the RAM/disk needs of the dom0 and
-all the domUs.
-
 In 2018-05, trouble booting a dom0 was reported with 256M of RAM: with
 512M it worked reliably.  This does not make sense, but if you see
 "not ELF" after Xen boots, try increasing dom0 RAM.
@@ -150,54 +112,13 @@
 
 The other way is to put Xen under a normal-usage computer, so that the
 dom0 is what the computer would have been without Xen, perhaps a
-desktop or laptop.  Then, one can run domUs at will.  Purists will
-deride this as less secure than the previous approach, and for a
-computer whose purpose is to run domUs, they are right.  But Xen and a
-dom0 (without domUs) is not meaningfully less secure than the same
-things running without Xen.  One can boot Xen or boot regular NetBSD
-alternately with little problems, simply refraining from starting the
-Xen daemons when not running Xen.
-
-Note that NetBSD as dom0 does not support multiple CPUs.  This will
-limit the performance of the Xen/dom0 workstation approach.  In theory
-the only issue is that the "backend drivers" are not yet MPSAFE:
-  https://mail-index.netbsd.org/netbsd-users/2014/08/29/msg015195.html
+desktop or laptop.  Then, one can run domUs at will.
 
 Installation of NetBSD
 ----------------------
 
-First,
-[install NetBSD/amd64](/guide/inst/)
+[Install NetBSD/amd64](/guide/inst/)
 just as you would if you were not using Xen.
-However, the partitioning approach is very important.
-
-If you want to use RAIDframe for the dom0, there are no special issues
-for Xen.  Typically one provides RAID storage for the dom0, and the
-domU systems are unaware of RAID.  The 2nd-stage loader bootxx_* skips
-over a RAID1 header to find /boot from a file system within a RAID
-partition; this is no different when booting Xen.
-
-There are 4 styles of providing backing storage for the virtual disks
-used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN.
-
-With raw partitions, one has a disklabel (or gpt) partition sized for
-each virtual disk to be used by the domU.  (If you are able to predict
-how domU usage will evolve, please add an explanation to the HOWTO.
-Seriously, needs tend to change over time.)
-
-One can use [lvm(8)](/guide/lvm/) to create logical devices to use
-for domU disks.  This is almost as efficient as raw disk partitions
-and more flexible.  Hence raw disk partitions should typically not
-be used.
-
-One can use files in the dom0 file system, typically created by dd'ing
-/dev/zero to create a specific size.  This is somewhat less efficient,
-but very convenient, as one can cp the files for backup, or move them
-between dom0 hosts.
-
-Finally, in theory one can place the files backing the domU disks in a
-SAN.  (This is an invitation for someone who has done this to add a
-HOWTO page.)
 
 Installation of Xen
 -------------------
@@ -212,19 +133,19 @@
 # cp /usr/pkg/xen48-kernel/xen.gz /
 """]]

(Diff truncated)
Add name= config entry for domUs, with xl it is a mandatory item.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.155
retrieving revision 1.156
diff -u -r1.155 -r1.156
--- wikisrc/ports/xen/howto.mdwn	1 Aug 2018 13:19:43 -0000	1.155
+++ wikisrc/ports/xen/howto.mdwn	25 Aug 2018 09:42:48 -0000	1.156
@@ -462,13 +462,14 @@
 
         # -*- mode: python; -*-
 
+        name = "domU-id"
         kernel = "/netbsd-XEN3PAE_DOMU-i386-foo.gz"
         memory = 1024
         vif = [ 'mac=aa:00:00:d1:00:09,bridge=bridge0' ]
         disk = [ 'file:/n0/xen/foo-wd0,0x0,w',
                  'file:/n0/xen/foo-wd1,0x1,w' ]
 
-The domain will have the same name as the file.  The kernel has the
+The domain will have name given in the name setting.  The kernel has the
 host/domU name in it, so that on the dom0 one can update the various
 domUs independently.  The vif line causes an interface to be provided,
 with a specific mac address (do not reuse MAC addresses!), in bridge

Mark as done by nonaka.
Patches here: https://github.com/IIJ-NetBSD/netbsd-src/compare/master...nonakap:nonakap/hyperv
Or alternatively: https://ftp.netbsd.org/pub/NetBSD/misc/nonaka/Hyper-V/
Members: 
	projects/project/netbsd_on_microsoft_azure.mdwn:1.10->1.11 

Index: wikisrc/projects/project/netbsd_on_microsoft_azure.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/netbsd_on_microsoft_azure.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/projects/project/netbsd_on_microsoft_azure.mdwn	17 Jul 2018 15:13:41 -0000	1.10
+++ wikisrc/projects/project/netbsd_on_microsoft_azure.mdwn	25 Aug 2018 01:02:02 -0000	1.11
@@ -13,6 +13,7 @@
 category="kernel"
 difficulty="medium"
 duration="3 months"
+done_by="NONAKA Kimihiro"
 
 description="""
 [Microsoft's cloud platform](http://www.windowsazure.com/en-us/) WindowsAzure has ec2-like features of creating custom virtual disks.
@@ -40,6 +41,3 @@
 """
 
 ]]
-
-
-[[!tag gsoc]]

Mark as done by berte.
Tree up at https://github.com/berte/u-boot/tree/ufs
Also, alternatively:
https://mail-index.netbsd.org/port-arm/2018/02/23/msg004650.html
Index: wikisrc/projects/project/u-boot-ffs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/u-boot-ffs.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/project/u-boot-ffs.mdwn	12 Mar 2018 13:26:12 -0000	1.6
+++ wikisrc/projects/project/u-boot-ffs.mdwn	25 Aug 2018 00:58:25 -0000	1.7
@@ -13,6 +13,7 @@
 category="kernel"
 difficulty="easy"
 duration="3 months"
+done_by="berte"
 
 description="""
 

Mark as done. Not 100%, but it should probably not be a project at this
stage.
Index: wikisrc/projects/project/cvs-migration.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/cvs-migration.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/projects/project/cvs-migration.mdwn	19 Dec 2014 17:13:46 -0000	1.15
+++ wikisrc/projects/project/cvs-migration.mdwn	25 Aug 2018 00:53:28 -0000	1.16
@@ -8,6 +8,7 @@
 
 category="misc"
 difficulty="hard"
+done_by="Joerg Sonnenberger"
 
 description="""
 

note that updated graphics is very realistic.
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/releng/netbsd9.mdwn	24 Aug 2018 13:41:30 -0000	1.10
+++ wikisrc/releng/netbsd9.mdwn	25 Aug 2018 00:46:15 -0000	1.11
@@ -29,7 +29,8 @@
 * gcc 8+ from a sanitizers point of view
 * arm: GENERIC kernel config for armv7 boards.
 * arm64: Support for servers following SBSA/SBBR standards
-* updated graphics drivers
+* updated graphics drivers.
+  - [Almost ready for merge](https://github.com/riastradh/netbsd-src/tree/riastradh-drm), only nouveau blocking changes
 
 
 ...

Mark done.
Index: wikisrc/projects/project/efi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/efi.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/project/efi.mdwn	12 Feb 2018 22:52:47 -0000	1.6
+++ wikisrc/projects/project/efi.mdwn	25 Aug 2018 00:42:44 -0000	1.7
@@ -13,6 +13,7 @@
 category="kernel"
 difficulty="easy"
 duration="2 months"
+done_by="Jared McNeill"
 
 description="""
 
@@ -32,5 +33,3 @@
 
 """
 ]]
-
-[[!tag gsoc]]

Mark Kernel Address Sanitizer as done
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/releng/netbsd9.mdwn	22 Aug 2018 06:32:57 -0000	1.9
+++ wikisrc/releng/netbsd9.mdwn	24 Aug 2018 13:41:30 -0000	1.10
@@ -18,7 +18,7 @@
 * XEN AVX working
    - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
 * ZFS
-* Kernel Address Sanitizer
+* ~~~Kernel Address Sanitizer~~~
 * compiler-rt in the base with enabled features for Clang/LLVM
 * address failing ptrace(2) tests, cover the remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
 * rework semantics of threading operations in ptrace(2)

no more 6. update some version numbers.
Index: wikisrc/releng/workflow.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/workflow.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/releng/workflow.mdwn	5 Jul 2017 18:52:00 -0000	1.2
+++ wikisrc/releng/workflow.mdwn	23 Aug 2018 07:11:53 -0000	1.3
@@ -98,7 +98,6 @@
 
    The current revs are:
 
-        6                    - NetBSD 6 queue
         7                    - NetBSD 7 queue
         8                    - NetBSD 8 queue
         pkgsrc            - Current pkgsrc branch
@@ -111,7 +110,7 @@
 
         ssh releng.netbsd.org $(basename $0) $*
 
-   ...and link it to the various commands I wish to run, such as "5-req".
+   ...and link it to the various commands I wish to run, such as "7-req".
 
 2. Create two directories:  one for source trees (I like to keep one
    for each supported branch checked out, to speed things up, but if space
@@ -133,20 +132,20 @@
 
         $ cvs -q -d cvs.netbsd.org:/cvsroot co -P -r<BRANCH> src xsrc
 
-   (I generally rename these to "src6" and "xsrc6" (etc), and maintain
-    "src51" "src52"  and "src60" as well.  YMMV)
+   (I generally rename these to "src7" and "xsrc7" (etc), and maintain
+    other branches similarly.  YMMV)
 
-5. Use (for example) "6-q" to list the queue for pullup-6;  Take ownership
+5. Use (for example) "7-q" to list the queue for pullup-7;  Take ownership
    of the ticket you're going to work on.  Let's use "9999" as the ticket
    number:
 
-        $ 6-q
+        $ 7-q
         <lots of output;  I want to work on 9999>
-        $ 6-req take 9999
+        $ 7-req take 9999
    
 6. Get the text of the ticket.
 
-        $ 6-req show 9999 > 9999   # put it in a file "9999" in /usr/releng
+        $ 7-req show 9999 > 9999   # put it in a file "9999" in /usr/releng
    
 7. Find the login name of the developer *requesting the pullup* (not
    necessarily the one who made the original change, though they're often
@@ -200,7 +199,7 @@
     well-formed message.
 
 10. Append the changes file ("cl") to doc/CHANGES-<rev>.  For example,
-    doc/CHANGES-5.2 is the currently-in-use log for post-5.1 but pre-5.2
+    doc/CHANGES-7.2 is the currently-in-use log for post-7.1 but pre-7.2
     changes that we're working on.  Each branch has a different file.
 
 11.  Commit the changes file.  In the log message, note which ticket you

bye bye 6
Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- wikisrc/releng.mdwn	1 Aug 2018 17:38:24 -0000	1.31
+++ wikisrc/releng.mdwn	23 Aug 2018 07:05:12 -0000	1.32
@@ -31,17 +31,6 @@
     - 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)
 
-### NetBSD 6.x
-
-* Next minor release: NetBSD 6.2 (No release date proposed)
-  + CVS branch tag: <code>netbsd-6</code>
-* Actively supported teeny releases:
-  + [NetBSD 6.1.5](http://www.netbsd.org/releases/formal-6/NetBSD-6.1.5.html)
-    - CVS branch tag: <code>netbsd-6-1</code>
-  + [NetBSD 6.0.6](http://www.netbsd.org/releases/formal-6/NetBSD-6.0.6.html)
-    - CVS branch tag: <code>netbsd-6-0</code>
-* [Current pull-up queue for the netbsd-6 branch](http://releng.netbsd.org/cgi-bin/req-6.cgi)
-
 ## Automated Status Information
 
 * [Daily build snapshot status](http://releng.netbsd.org/cgi-bin/builds.cgi)

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/releng/netbsd9.mdwn	21 Aug 2018 22:30:25 -0000	1.8
+++ wikisrc/releng/netbsd9.mdwn	22 Aug 2018 06:32:57 -0000	1.9
@@ -14,7 +14,9 @@
    - [[!template id=pr number=52614]] qemu virtual CD-ROM reports read errors since recent wdc changes
    - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
 * UBC using direct map working on amd64 and alpha
-* XEN AVX working - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
+   - [[!template id=pr number=53124]] (FFS is slow because pmap_update doesn't scale)
+* XEN AVX working
+   - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
 * ZFS
 * Kernel Address Sanitizer
 * compiler-rt in the base with enabled features for Clang/LLVM

Add "updated graphics drivers" to NetBSD 9 nice-to-have, from pgoyette@.
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/releng/netbsd9.mdwn	21 Aug 2018 21:26:47 -0000	1.7
+++ wikisrc/releng/netbsd9.mdwn	21 Aug 2018 22:30:25 -0000	1.8
@@ -27,6 +27,7 @@
 * gcc 8+ from a sanitizers point of view
 * arm: GENERIC kernel config for armv7 boards.
 * arm64: Support for servers following SBSA/SBBR standards
+* updated graphics drivers
 
 
 ...

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/releng/netbsd9.mdwn	3 Aug 2018 10:17:56 -0000	1.6
+++ wikisrc/releng/netbsd9.mdwn	21 Aug 2018 21:26:47 -0000	1.7
@@ -10,7 +10,8 @@
    - TODO: docs, what features to add to NPF ...
 * ATA/NCQ
    - variants of [[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
-   - [[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]
+   - ~~[[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]~~
+   - [[!template id=pr number=52614]] qemu virtual CD-ROM reports read errors since recent wdc changes
    - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
 * UBC using direct map working on amd64 and alpha
 * XEN AVX working - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set

this is not speced enough to be a gsoc project
Index: wikisrc/projects/project/madwifi-ng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/madwifi-ng.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/madwifi-ng.mdwn	12 Feb 2018 20:51:53 -0000	1.5
+++ wikisrc/projects/project/madwifi-ng.mdwn	21 Aug 2018 15:55:56 -0000	1.6
@@ -14,5 +14,3 @@
 would be nice to have these devices supported in NetBSD.
 """
 ]]
-
-[[!tag gsoc]]

adjust done_by to include both people.
Index: wikisrc/projects/project/kasan.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/kasan.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/kasan.mdwn	21 Aug 2018 12:31:47 -0000	1.4
+++ wikisrc/projects/project/kasan.mdwn	21 Aug 2018 12:34:11 -0000	1.5
@@ -13,8 +13,7 @@
 category="analyzers"
 difficulty="hard"
 duration="3 months"
-done_by="Maxime Villard"
-done_by="Siddharth Muralee"
+done_by="Maxime Villard and Siddharth Muralee"
 
 description="""
 

Mark as done by r3x and maxv (hopefully in the correct way)
Index: wikisrc/projects/project/kasan.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/kasan.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/kasan.mdwn	27 Jan 2018 16:43:18 -0000	1.3
+++ wikisrc/projects/project/kasan.mdwn	21 Aug 2018 12:31:47 -0000	1.4
@@ -13,6 +13,8 @@
 category="analyzers"
 difficulty="hard"
 duration="3 months"
+done_by="Maxime Villard"
+done_by="Siddharth Muralee"
 
 description="""
 
@@ -33,5 +35,3 @@
 
 """
 ]]
-
-[[!tag gsoc]]

Use a more modern skiplink, which works with browsers supporting CSS too
Index: wikisrc/global.css
===================================================================
RCS file: /cvsroot/wikisrc/global.css,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/global.css	25 Jun 2018 19:14:32 -0000	1.8
+++ wikisrc/global.css	19 Aug 2018 16:34:37 -0000	1.9
@@ -1,4 +1,4 @@
-/* $NetBSD: global.css,v 1.8 2018/06/25 19:14:32 leot Exp $ */
+/* $NetBSD: global.css,v 1.9 2018/08/19 16:34:37 maya Exp $ */
 
 /* ##### Common Styles ##### */
 
@@ -60,6 +60,15 @@
   display: none !important;
 }
 
+#skiplink {
+  position: absolute;
+  left: -99999px;
+}
+
+#skiplink:active, #skiplink:focus {
+  position: initial;
+}
+
 /* ##### Header ##### */
 
 .topNavigation {
@@ -579,6 +588,10 @@
   width: 100%;
 }
 
+.email-obfuscate {
+	font-size: 0;
+}
+
 .center {
 	Vertical-Align: middle;
 	Text-Align: center;
@@ -703,6 +716,7 @@
 table.build-results td.build-time {
   text-align: right;
   padding-right: 0;
+  font-family: Ubuntu Mono, DejaVu Sans Mono, Lucida Console, Courier, monospace;
 }
 
 table.build-results td.failed {
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- wikisrc/templates/page.tmpl	19 Aug 2018 15:29:02 -0000	1.52
+++ wikisrc/templates/page.tmpl	19 Aug 2018 16:34:37 -0000	1.53
@@ -30,7 +30,7 @@
 </head>
 <body>
     <!-- For non-visual user agents: -->
-    <div id="top"><a href="#content" class="doNotDisplay doNotPrint">Skip to main content.</a></div>
+    <div id="top"><a href="#content" id="skiplink" tabindex="1">Skip to main content.</a></div>
 
     <div id="centralHeader">
       <div id="logo">

Add a 'skip to main content' link at the top for non-visual users.
(On the wiki, skipping to content rather than mainContent...)
Members: 
	templates/page.tmpl:1.51->1.52 

Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- wikisrc/templates/page.tmpl	10 Aug 2018 08:45:24 -0000	1.51
+++ wikisrc/templates/page.tmpl	19 Aug 2018 15:29:02 -0000	1.52
@@ -29,6 +29,9 @@
 <TMPL_IF NAME="META"><TMPL_VAR META></TMPL_IF>
 </head>
 <body>
+    <!-- For non-visual user agents: -->
+    <div id="top"><a href="#content" class="doNotDisplay doNotPrint">Skip to main content.</a></div>
+
     <div id="centralHeader">
       <div id="logo">
         <a href="//www.NetBSD.org/"><img src="//www.NetBSD.org/images/NetBSD-smaller.png" alt="[NetBSD Logo]"/></a>

typo
Index: wikisrc/the_netbsd_system_manager__39__s_manual.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/the_netbsd_system_manager__39__s_manual.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/the_netbsd_system_manager__39__s_manual.mdwn	22 Jun 2018 21:14:08 -0000	1.3
+++ wikisrc/the_netbsd_system_manager__39__s_manual.mdwn	11 Aug 2018 13:23:36 -0000	1.4
@@ -155,7 +155,7 @@
 
 ##  Enable exploit mitigation 
 
-Follow advices in [security(8)](http://netbsd.gw.com/cgi-bin/man-cgi?security++NetBSD-current) man page. 
+Follow advices in [security(7)](http://netbsd.gw.com/cgi-bin/man-cgi?security++NetBSD-current) man page. 
 
 
 ##  Recognize methods for restraining a service 

Try to make links clickable
Index: wikisrc/users/kamil/sanitizers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/kamil/sanitizers.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:26:35 -0000	1.5
+++ wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:33:22 -0000	1.6
@@ -65,11 +65,11 @@
 
 MKSANITIZER blog entry:
 
-http://blog.netbsd.org/tnf/entry/mksanitizer_bug_detector_software_integration
+[http://blog.netbsd.org/tnf/entry/mksanitizer_bug_detector_software_integration](http://blog.netbsd.org/tnf/entry/mksanitizer_bug_detector_software_integration)
 
 MKLIBCSANITIZER and kernel sanitizer blog entry:
 	
-http://blog.netbsd.org/tnf/entry/introduction_to_%C2%B5ubsan_a_clean
+[http://blog.netbsd.org/tnf/entry/introduction_to_%C2%B5ubsan_a_clean](http://blog.netbsd.org/tnf/entry/introduction_to_%C2%B5ubsan_a_clean)
 
 # Support in NetBSD
 

Document types of linking of runtimes.
Index: wikisrc/users/kamil/sanitizers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/kamil/sanitizers.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:20:48 -0000	1.4
+++ wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:26:35 -0000	1.5
@@ -43,6 +43,17 @@
 As a NetBSD specific extension, there is a micro-UBSan runtime developed and maintained in the NetBSD source code.
 It is designed to function inside libc (uUBSan - usermode-UBSan) and inside the kernel (kUBSan - kernel-UBSan).
 
+# Types of runtimes
+
+There are two types of sanitizer runtimes:
+
+ * dynamically linked ones (default in GCC)
+ * statically linked ones (default in Clang)
+
+Base GCC/NetBSD works with the former, upstream HEAD version of LLVM/NetBSD works with the latter.
+
+Both compilers should support both of them, but the other options (GCC/NetBSD & static runtime, LLVM/NetBSD & dynamic runtime) are to be done.
+
 # Sanitizers in NetBSD
 
 Sanitizers in NetBSD are shipped with the following options:

Improve the wording.
Index: wikisrc/users/kamil/sanitizers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/kamil/sanitizers.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:19:03 -0000	1.3
+++ wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:20:48 -0000	1.4
@@ -115,17 +115,17 @@
 
 Name      | NetBSD status
 ----------|---------------------------------
-UBSan     | works with all ports
-ASan      | works with amd64 and i386
-MSan      | works with amd64
-TSan      | works with amd64
+UBSan     | mostly works with all LLVM ports
+ASan      | mostly works with amd64 and i386
+MSan      | mostly works with amd64
+TSan      | mostly works with amd64
 
 ### LLVM with MKSANITIZER
 
 Name      | NetBSD status
 ----------|---------------------------------
-UBSan     | works with all ports
-ASan      | works with amd64 and i386
+UBSan     | mostly works with all LLVM ports
+ASan      | mostly works with amd64 and i386
 
 ### LLVM with MKLIBCSANITIZER
 

Add content to the MKSANITIZER LLVM entry
Index: wikisrc/users/kamil/sanitizers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/kamil/sanitizers.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:17:12 -0000	1.2
+++ wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:19:03 -0000	1.3
@@ -122,7 +122,10 @@
 
 ### LLVM with MKSANITIZER
 
-Untested.
+Name      | NetBSD status
+----------|---------------------------------
+UBSan     | works with all ports
+ASan      | works with amd64 and i386
 
 ### LLVM with MKLIBCSANITIZER
 

Try to fix the syntax of tables.
Index: wikisrc/users/kamil/sanitizers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/kamil/sanitizers.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:14:52 -0000	1.1
+++ wikisrc/users/kamil/sanitizers.mdwn	11 Aug 2018 12:17:12 -0000	1.2
@@ -86,7 +86,7 @@
 ### GCC with the default runtime
 
 Name      | NetBSD status
-----------+---------------------------------
+----------|---------------------------------
 UBSan     | mostly works with all ports
 ASan      | mostly works with amd64 and i386
 LSan      | might work with amd64 and i386
@@ -98,13 +98,13 @@
 ### GCC with MKLIBCSANITIZER
 
 Name      | NetBSD status
-----------+---------------------------------
+----------|---------------------------------
 UBSan     | works with micro-UBSan
 
 ### GCC with kernel sanitizers
 
 Name      | NetBSD status
-----------+---------------------------------
+----------|---------------------------------
 UBSan     | works with micro-UBSan
 
 ## LLVM
@@ -114,7 +114,7 @@
 ### LLVM with the default runtime
 
 Name      | NetBSD status
-----------+---------------------------------
+----------|---------------------------------
 UBSan     | works with all ports
 ASan      | works with amd64 and i386
 MSan      | works with amd64
@@ -127,11 +127,11 @@
 ### LLVM with MKLIBCSANITIZER
 
 Name      | NetBSD status
-----------+---------------------------------
+----------|---------------------------------
 UBSan     | works with micro-UBSan
 
 ### LLVM with kernel sanitizers
 
 Name      | NetBSD status
-----------+---------------------------------
+----------|---------------------------------
 UBSan     | works with micro-UBSan

Add a short wiki entry with the status of Sanitizers
--- /dev/null	2018-08-11 12:15:05.000000000 +0000
+++ wikisrc/users/kamil/sanitizers.mdwn	2018-08-11 12:15:10.000000000 +0000
@@ -0,0 +1,137 @@
+Sanitizers for NetBSD
+
+# Current status
+
+Summary of the current status of sanitizers on a NetBSD host.
+
+# What are sanitizers?
+
+Sanitizer is a programming tool that detects computer program bugs such as buffer overflows, signed integer overflow, uninitialized memory read etc.
+
+Sanitizers are developed in LLVM, and a downstream port exists to GCC.
+
+# Types of sanitizers
+
+There are various types of sanitizers.
+
+A sanitizer is composed of an instrumentation part builtin into a compiler's code generation part.
+
+The instrumentation part emitted by a compiler requires a runtime library, that is shipped with compiler-rt.
+
+ * Undefined Behavior Sanitizer (UBSan)
+ * Undefined Behavior with minimal runtime (UBSan_minimal)
+ * Address Sanitizer (ASan)
+ * Hardware Assisted Address Sanitizer (HWASan)
+ * Thread Sanitizer (TSan)
+ * Memory Sanitizer (MSan)
+ * Efficiency Sanitizer (ESan)
+ * Data Flow Sanitizer (DFSan)
+ * Leak Sanitizer (LSan)
+
+Additionally there are the following features shipped together with sanitizers:
+
+ * profile
+ * SafeStack
+ * Control Flow Integrity
+ * Scudo Hardened Allocator
+ * XRay
+ * libFuzzer
+ * ShadowCallStack
+
+The compiler-rt package ships with libBlocksRuntime, builtins etc.
+
+As a NetBSD specific extension, there is a micro-UBSan runtime developed and maintained in the NetBSD source code.
+It is designed to function inside libc (uUBSan - usermode-UBSan) and inside the kernel (kUBSan - kernel-UBSan).
+
+# Sanitizers in NetBSD
+
+Sanitizers in NetBSD are shipped with the following options:
+
+ * together with the toolchain with the default compiler runtime (default),
+ * together with the MKSANITIZER option (build the userland with the default compiler sanitizer),
+ * together with the MKLIBCSANITIZER option (build the userland with a homegrown sanitizer runtime),
+ * together with the NetBSD kernel (build the kernel with a homegrown kernel sanitizer runtime).
+
+MKSANITIZER blog entry:
+
+http://blog.netbsd.org/tnf/entry/mksanitizer_bug_detector_software_integration
+
+MKLIBCSANITIZER and kernel sanitizer blog entry:
+	
+http://blog.netbsd.org/tnf/entry/introduction_to_%C2%B5ubsan_a_clean
+
+# Support in NetBSD
+
+Currently the main focus is with LLVM and GCC.
+
+Generic TODO:
+
+ * switch syscall(2)/__syscall(2) to libc calls
+ * upstream local patches / rebase to newly developed support in LLVM available in GCC 8.x and newer
+ * develop missing interceptors such as fts(3) (mostly MSan-centric)
+ * FILE and DIR sanitization (needed by at least: ESan, MSan)
+ * improve the framework for ioctl(2) database and handle special cases when a part of a struct can be uninitialized and passed to the kernel (MSan)
+ * finish StopTheWorld() and upstream to LLVM
+ * port to !x86
+ * fixes with the signal code
+ * pkgsrc integration
+ * finish the support of float128 for Clang/LLVM/libstdc++/libgcc
+ * LLVM fixes for shared (dlopen(3)-powered) runtime
+ * fix other bugs.
+
+## GCC
+
+The GCC compiler assumed the version in distribution.
+
+### GCC with the default runtime
+
+Name      | NetBSD status
+----------+---------------------------------
+UBSan     | mostly works with all ports
+ASan      | mostly works with amd64 and i386
+LSan      | might work with amd64 and i386
+
+### GCC with MKSANITIZER
+
+Untested.
+
+### GCC with MKLIBCSANITIZER
+
+Name      | NetBSD status
+----------+---------------------------------
+UBSan     | works with micro-UBSan
+
+### GCC with kernel sanitizers
+
+Name      | NetBSD status
+----------+---------------------------------
+UBSan     | works with micro-UBSan
+
+## LLVM
+
+The LLVM support is available only with the HEAD version of the toolchain and not shipped in the base distribution.
+
+### LLVM with the default runtime
+
+Name      | NetBSD status
+----------+---------------------------------
+UBSan     | works with all ports
+ASan      | works with amd64 and i386
+MSan      | works with amd64
+TSan      | works with amd64
+
+### LLVM with MKSANITIZER
+
+Untested.
+
+### LLVM with MKLIBCSANITIZER
+
+Name      | NetBSD status
+----------+---------------------------------
+UBSan     | works with micro-UBSan
+
+### LLVM with kernel sanitizers
+
+Name      | NetBSD status
+----------+---------------------------------
+UBSan     | works with micro-UBSan

Fix href of the `Disclaimer' <a>.
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- wikisrc/templates/page.tmpl	25 Jul 2018 21:17:23 -0000	1.50
+++ wikisrc/templates/page.tmpl	10 Aug 2018 08:45:24 -0000	1.51
@@ -274,7 +274,7 @@
       <a href="//www.NetBSD.org/cgi-bin/feedback.cgi">
         Contact</a> |
     </span>
-    <span class="footcopy"><a href="about/disclaimer.html">
+    <span class="footcopy"><a href="//www.NetBSD.org/about/disclaimer.html">
       Disclaimer</a> |
       <span class="copyright">
         Copyright &copy; 1994-2018 The NetBSD Foundation, Inc.

Mark 'Kernel Undefined Behavior SANitizer' as finished by myself
Index: wikisrc/projects/project/ubsan.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ubsan.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/ubsan.mdwn	27 Jan 2018 15:22:49 -0000	1.2
+++ wikisrc/projects/project/ubsan.mdwn	8 Aug 2018 00:51:10 -0000	1.3
@@ -13,6 +13,7 @@
 category="analyzers"
 difficulty="medium"
 duration="3 months"
+done_by="Kamil Rytarowski"
 
 description="""
 

Mark 'Building userland with sanitizers' as finished by myself
Index: wikisrc/projects/project/userland-san.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/userland-san.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/userland-san.mdwn	4 Feb 2018 19:46:22 -0000	1.1
+++ wikisrc/projects/project/userland-san.mdwn	8 Aug 2018 00:49:04 -0000	1.2
@@ -13,6 +13,7 @@
 category="analyzers"
 difficulty="easy"
 duration="3 months"
+done_by="Kamil Rytarowski"
 
 description="""
 

Direct reader to mysql 5.6
Index: wikisrc/pkgsrc/how_to_install_a_mysql_server.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/how_to_install_a_mysql_server.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/pkgsrc/how_to_install_a_mysql_server.mdwn	5 Feb 2012 07:14:36 -0000	1.2
+++ wikisrc/pkgsrc/how_to_install_a_mysql_server.mdwn	6 Aug 2018 21:25:05 -0000	1.3
@@ -11,7 +11,7 @@
 
 If you decide to install via pkgsrc, because of a newer version, just enter: 
     
-    # cd /usr/pkgsrc/databases/mysql5-server/
+    # cd /usr/pkgsrc/databases/mysql56-server/
     # make install clean
     
 

Formatting
Index: wikisrc/pkgsrc/how_to_install_a_lamp_server.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/how_to_install_a_lamp_server.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/pkgsrc/how_to_install_a_lamp_server.mdwn	6 Aug 2018 21:16:52 -0000	1.4
+++ wikisrc/pkgsrc/how_to_install_a_lamp_server.mdwn	6 Aug 2018 21:22:03 -0000	1.5
@@ -10,7 +10,7 @@
 
 The new Apache 2.4 server comes with two different threading models from which [prefork](http://httpd.apache.org/docs/2.4/mod/prefork.html) is installed by default. It is **not** recommended to use the Worker model, if you wish to use Apache and PHP. As that is the case, we will install a default Apache 2.4 server. 
     
-# cd /usr/pkgsrc/www/apache24
+    # cd /usr/pkgsrc/www/apache24
     # make install clean clean-depends
     
 

Update for Apache 2.4 & mysql 5.6.
Index: wikisrc/pkgsrc/how_to_install_a_lamp_server.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/how_to_install_a_lamp_server.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/pkgsrc/how_to_install_a_lamp_server.mdwn	24 Dec 2017 17:44:32 -0000	1.3
+++ wikisrc/pkgsrc/how_to_install_a_lamp_server.mdwn	6 Aug 2018 21:16:52 -0000	1.4
@@ -8,13 +8,13 @@
 
 #  Installing the Apache webserver 
 
-The new Apache 2.2 server comes with two different threading models from which [prefork](http://httpd.apache.org/docs/2.2/mod/prefork.html) is installed by default. It is **not** recommended to use the Worker model, if you wish to use Apache and PHP. As that is the case, we will install a default Apache 2.2 server. 
+The new Apache 2.4 server comes with two different threading models from which [prefork](http://httpd.apache.org/docs/2.4/mod/prefork.html) is installed by default. It is **not** recommended to use the Worker model, if you wish to use Apache and PHP. As that is the case, we will install a default Apache 2.4 server. 
     
-# cd /usr/pkgsrc/www/apache22
+# cd /usr/pkgsrc/www/apache24
     # make install clean clean-depends
     
 
-This will install the Apache 2.2 server and all it's dependencies. The package currently depends on 10 other packages like perl, gmake and libtool to name a few. All dependencies are build before the Apache webserver is build, otherwise it wouldn't be dependencies. 
+This will install the Apache 2.4 server and all it's dependencies. The package currently depends on 10 other packages like perl, gmake and libtool to name a few. All dependencies are build before the Apache webserver is build, otherwise it wouldn't be dependencies. 
 
 If your build was successful, you should now edit the Apache configuration file _`/usr/pkg/etc/httpd/httpd.conf`_ to fit your needs. At least set the `Listen` Attribute and your `ServerName`. Please ensure that if your machines hostname does not globally resolve, to put it into your `/etc/hosts` file, otherwise Apache will refuse to start. 
 
@@ -50,7 +50,7 @@
 
 You can skip this part, if you don't want to install a MySQL Server. To install the MySQL Server enter: 
     
-    # cd /usr/pkgsrc/databases/mysql5-server
+    # cd /usr/pkgsrc/databases/mysql56-server
     # make install clean clean-depends
     
 
@@ -87,7 +87,7 @@
     # sockstat -l
     
 
-For much more Options, consider reading the MySQL [Documentation](http://dev.mysql.com/doc/refman/5.0/en/). 
+For much more Options, consider reading the MySQL [Documentation](http://dev.mysql.com/doc/refman/5.6/en/). 
 
 
 #  Installing the PHP Module for Apache
@@ -96,7 +96,7 @@
     # make install clean
     
 
-This will install by default the latest Version of PHP 5.x and the PHP5 Module for Apache 2.2 
+This will install by default the latest Version of PHP 7.x and the PHP7 Module for Apache 2.4 
 
 ##  Configuring PHP 
 
@@ -104,7 +104,7 @@
 
 Add following lines: 
     
-    LoadModule php5_module /usr/pkg/lib/httpd/mod_php5.so
+    LoadModule php7_module /usr/pkg/lib/httpd/mod_php7.so
     
 
 and 
@@ -137,7 +137,7 @@
     <?php phpinfo(); ?>
     
 
-if you use php5 and wish to use short tags like `<? phpinfo() ?>`, then edit your `/usr/pkg/etc/php.ini` file and change option `short_open_tag = Off `to `On` to make this line working. In PHP5 short_open_tag is off by default. 
+if you use php7 and wish to use short tags like `<? phpinfo() ?>`, then edit your `/usr/pkg/etc/php.ini` file and change option `short_open_tag = Off `to `On` to make this line working. In PHP7 short_open_tag is off by default. 
 
 Open your browser and point it to this url: 
     

LVM
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/releng/netbsd9.mdwn	3 Aug 2018 01:06:33 -0000	1.5
+++ wikisrc/releng/netbsd9.mdwn	3 Aug 2018 10:17:56 -0000	1.6
@@ -19,6 +19,7 @@
 * compiler-rt in the base with enabled features for Clang/LLVM
 * address failing ptrace(2) tests, cover the remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
 * rework semantics of threading operations in ptrace(2)
+* LVM mirror target
 
 ## Nice to have
 

typo
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/releng/netbsd9.mdwn	2 Aug 2018 14:21:59 -0000	1.4
+++ wikisrc/releng/netbsd9.mdwn	3 Aug 2018 01:06:33 -0000	1.5
@@ -17,7 +17,7 @@
 * ZFS
 * Kernel Address Sanitizer
 * compiler-rt in the base with enabled features for Clang/LLVM
-* address failing ptrace(2) tests, cover te remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
+* address failing ptrace(2) tests, cover the remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
 * rework semantics of threading operations in ptrace(2)
 
 ## Nice to have

Add link to the KASLR page.
Index: wikisrc/security.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/security.mdwn	23 Feb 2018 17:20:34 -0000	1.4
+++ wikisrc/security.mdwn	2 Aug 2018 17:26:46 -0000	1.5
@@ -3,3 +3,4 @@
 * [Hardening packages](../pkgsrc/hardening)
 * [Root filesystem encryption](cgdroot)
 * [Meltdown and Spectre Status Page](meltdown_spectre)
+* [Using KASLR](kaslr)

Add a KASLR howto. Not much to say, but it needs to be officially said
somewhere. I'll perhaps add a nude or two to enlighten if there is some
confusion.
--- /dev/null	2018-08-02 17:25:01.000000000 +0000
+++ wikisrc/security/kaslr.mdwn	2018-08-02 17:25:01.000000000 +0000
@@ -0,0 +1,54 @@
+[[!meta title="Using KASLR"]]
+
+NetBSD supports Kernel ASLR on x86 64bit CPUs (amd64), starting from
+NetBSD 9.0.
+
+Installation
+------------
+
+Install the prekern:
+
+[[!template id=programlisting text="""
+# cp /usr/mdec/prekern /
+"""]]
+
+Obtain a GENERIC_KASLR kernel. Such a kernel can be either downloaded from
+the NetBSD FTP server, for example on:
+
+[[!template id=programlisting text="""
+http://nycdn.netbsd.org/pub/NetBSD-daily/HEAD/201808020450Z/amd64/binary/kernel/netbsd-GENERIC_KASLR.gz
+"""]]
+
+Or compiled from scratch, using:
+
+[[!template id=programlisting text="""
+# cd /usr/src
+# ./build.sh kernel=GENERIC_KASLR
+"""]]
+
+Install this KASLR kernel:
+
+[[!template id=programlisting text="""
+# cp /path/to/your/kernel /netbsd_kaslr
+"""]]
+
+Finally, add the following line in the `/boot.cfg` file:
+
+[[!template id=filecontent name="/boot.cfg" text="""
+menu=Boot KASLR:rndseed /var/db/entropy-file;pkboot netbsd_kaslr
+"""]]
+
+Now the installation is complete.
+
+Use
+---
+
+To use KASLR, just choose the "Boot KASLR" option in the menu at boot
+time. That's it!
+
+Technical Resources
+-------------------
+
+* NetBSD.org: [Kernel ASLR on amd64](http://blog.netbsd.org/tnf/entry/kernel_aslr_on_amd64)
+* NetBSD.org: [The strongest KASLR, ever?](http://blog.netbsd.org/tnf/entry/the_strongest_kaslr_ever)
+

ARM/ARM64 wishlist
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/releng/netbsd9.mdwn	2 Aug 2018 11:46:45 -0000	1.3
+++ wikisrc/releng/netbsd9.mdwn	2 Aug 2018 14:21:59 -0000	1.4
@@ -23,6 +23,8 @@
 ## Nice to have
 
 * gcc 8+ from a sanitizers point of view
+* arm: GENERIC kernel config for armv7 boards.
+* arm64: Support for servers following SBSA/SBBR standards
 
 
 ...

Add NetBSD -9 TODO items from myself
Kernel Address Sanitizer
compiler-rt
ptrace
Nice to have: gcc 8+
Nice to have: gcc 8+

Members: 
	releng/netbsd9.mdwn:1.2->1.3 

Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/releng/netbsd9.mdwn	2 Aug 2018 08:57:28 -0000	1.2
+++ wikisrc/releng/netbsd9.mdwn	2 Aug 2018 11:46:45 -0000	1.3
@@ -15,5 +15,14 @@
 * UBC using direct map working on amd64 and alpha
 * XEN AVX working - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
 * ZFS
+* Kernel Address Sanitizer
+* compiler-rt in the base with enabled features for Clang/LLVM
+* address failing ptrace(2) tests, cover te remaining scenarios (there are planned ~2k ATF tests total for the elementary functionality)
+* rework semantics of threading operations in ptrace(2)
+
+## Nice to have
+
+* gcc 8+ from a sanitizers point of view
+
 
 ...

ZFS is a must-have
Index: wikisrc/releng/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd9.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/releng/netbsd9.mdwn	1 Aug 2018 17:38:21 -0000	1.1
+++ wikisrc/releng/netbsd9.mdwn	2 Aug 2018 08:57:28 -0000	1.2
@@ -14,5 +14,6 @@
    - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
 * UBC using direct map working on amd64 and alpha
 * XEN AVX working - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
+* ZFS
 
 ...

update for rename of netbsd9.mdwn to releng/netbsd9.mdwn
Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- wikisrc/releng.mdwn	1 Aug 2018 17:20:07 -0000	1.30
+++ wikisrc/releng.mdwn	1 Aug 2018 17:38:24 -0000	1.31
@@ -10,7 +10,7 @@
 
 * Next release: NetBSD 9.0
   + no CVS branch yet
-* [[NetBSD 9.0 preliminary task list|netbsd9]]
+* [[NetBSD 9.0 preliminary task list|releng/netbsd9]]
 
 ## Active Major Releases
 

rename netbsd9.mdwn to releng/netbsd9.mdwn
--- wikisrc/netbsd9.mdwn	2018-08-01 17:38:38.000000000 +0000
+++ /dev/null	2018-08-01 17:38:01.000000000 +0000
@@ -1,18 +0,0 @@
-[[!meta title="NetBSD 9.0 preliminary tasklist"]]
-
-## PRs worth fixing
-
-* TBD
-
-## Features to finish/implement
-
-* IPF/PF deprecation in favour of NPF
-   - TODO: docs, what features to add to NPF ...
-* ATA/NCQ
-   - variants of [[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
-   - [[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]
-   - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
-* UBC using direct map working on amd64 and alpha
-* XEN AVX working - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
-
-...
--- /dev/null	2018-08-01 17:38:01.000000000 +0000
+++ wikisrc/releng/netbsd9.mdwn	2018-08-01 17:38:38.000000000 +0000
@@ -0,0 +1,18 @@
+[[!meta title="NetBSD 9.0 preliminary tasklist"]]
+
+## PRs worth fixing
+
+* TBD
+
+## Features to finish/implement
+
+* IPF/PF deprecation in favour of NPF
+   - TODO: docs, what features to add to NPF ...
+* ATA/NCQ
+   - variants of [[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
+   - [[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]
+   - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
+* UBC using direct map working on amd64 and alpha
+* XEN AVX working - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
+
+...

Index: wikisrc/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/netbsd9.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/netbsd9.mdwn	1 Aug 2018 17:30:32 -0000	1.3
+++ wikisrc/netbsd9.mdwn	1 Aug 2018 17:31:15 -0000	1.4
@@ -13,6 +13,6 @@
    - [[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]
    - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
 * UBC using direct map working on amd64 and alpha
-* XEN AVX working - [[!template id=pr number= 50332]] AVX instructions don't work but OSXSAVE flag is set
+* XEN AVX working - [[!template id=pr number=50332]] AVX instructions don't work but OSXSAVE flag is set
 
 ...

Index: wikisrc/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/netbsd9.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/netbsd9.mdwn	1 Aug 2018 17:28:12 -0000	1.2
+++ wikisrc/netbsd9.mdwn	1 Aug 2018 17:30:32 -0000	1.3
@@ -2,16 +2,17 @@
 
 ## PRs worth fixing
 
-*
+* TBD
 
 ## Features to finish/implement
 
 * IPF/PF deprecation in favour of NPF
    - TODO: docs, what features to add to NPF ...
 * ATA/NCQ
-   - ~~[[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
-   - ~~[[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]
-   - ~~[[!template id=pr number= 53183]] System stops servicing I/O requests and eventually deadlocks
+   - variants of [[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
+   - [[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]
+   - [[!template id=pr number=53183]] System stops servicing I/O requests and eventually deadlocks
 * UBC using direct map working on amd64 and alpha
+* XEN AVX working - [[!template id=pr number= 50332]] AVX instructions don't work but OSXSAVE flag is set
 
 ...

Index: wikisrc/netbsd9.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/netbsd9.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/netbsd9.mdwn	1 Aug 2018 17:23:37 -0000	1.1
+++ wikisrc/netbsd9.mdwn	1 Aug 2018 17:28:12 -0000	1.2
@@ -1,17 +1,17 @@
-[[!meta title="NetBSD 8.0 pre-release tasklist"]]
+[[!meta title="NetBSD 9.0 preliminary tasklist"]]
 
 ## PRs worth fixing
 
-* ~~[[!template id=pr number=52769]]: hang with an ffs stored in an nvme device~~ (done)
-
+*
 
 ## Features to finish/implement
 
 * IPF/PF deprecation in favour of NPF
-   - TODO: docs, ...
+   - TODO: docs, what features to add to NPF ...
 * ATA/NCQ
-   - WDCTL_RST
-   - hang on paralell fsck -
-   - Sevan hang on error
+   - ~~[[!template id=pr number=48214]] "clearing WDCTL_RST failed" during boot
+   - ~~[[!template id=pr number=52783]] parallel fsck hangs during boot of 8.99.[5678]
+   - ~~[[!template id=pr number= 53183]] System stops servicing I/O requests and eventually deadlocks
+* UBC using direct map working on amd64 and alpha
 
 ...

--- /dev/null	2018-08-01 17:23:05.000000000 +0000
+++ wikisrc/netbsd9.mdwn	2018-08-01 17:23:52.000000000 +0000
@@ -0,0 +1,17 @@
+[[!meta title="NetBSD 8.0 pre-release tasklist"]]
+
+## PRs worth fixing
+
+* ~~[[!template id=pr number=52769]]: hang with an ffs stored in an nvme device~~ (done)
+
+
+## Features to finish/implement
+
+* IPF/PF deprecation in favour of NPF
+   - TODO: docs, ...
+* ATA/NCQ
+   - WDCTL_RST
+   - hang on paralell fsck -
+   - Sevan hang on error
+
+...

Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- wikisrc/releng.mdwn	19 Jul 2018 09:59:46 -0000	1.29
+++ wikisrc/releng.mdwn	1 Aug 2018 17:20:07 -0000	1.30
@@ -10,6 +10,7 @@
 
 * Next release: NetBSD 9.0
   + no CVS branch yet
+* [[NetBSD 9.0 preliminary task list|netbsd9]]
 
 ## Active Major Releases
 

noise reduction police
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.154
retrieving revision 1.155
diff -u -r1.154 -r1.155
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 16:29:45 -0000	1.154
+++ wikisrc/ports/xen/howto.mdwn	1 Aug 2018 13:19:43 -0000	1.155
@@ -3,9 +3,6 @@
 Introduction
 ============
 
-[![[Xen
-screenshot]](https://www.netbsd.org/gallery/in-Action/hubertf-xens.png)](https://www.netbsd.org/gallery/in-Action/hubertf-xen.png)
-
 Xen is a hypervisor for x86 hardware, which supports running multiple guest
 operating systems on a single physical machine.  Xen is a Type 1 or
 bare-metal hypervisor; one uses the Xen kernel to control the CPU,
@@ -31,10 +28,6 @@
 modification is required; however, hardware support is required, such
 as VT-x on Intel CPUs and SVM on AMD CPUs.
 
-There are further features for IOMMU virtualization, Intel's VT-d and
-AMD's AMD-Vi.  TODO: Explain whether Xen on NetBSD makes use of these
-features.  TODO: Review by someone who really understands this.
-
 At boot, the dom0 kernel is loaded as a module with Xen as the kernel.
 The dom0 can start one or more domUs.  (Booting is explained in detail
 in the dom0 section.)
@@ -83,35 +76,9 @@
 
 Note: Xen 4.2 was the last version to support 32bit CPUs.
 
-Xen command program
--------------------
-
-Early Xen used a program called xm to manipulate the system from the
-dom0.  Starting in 4.1, a replacement program with similar behavior
-called xl is provided, but it does not work well in 4.1.  In 4.2, both
-xm and xl work fine.  4.4 is the last version that has xm.
-
-You must make a global choice to use xm or xl, because it affects not
-only which command you use, but the command used by rc.d scripts
-(specifically xendomains) and which daemons should be run.  The
-xentools packages provide xl for 4.2 and up.
-
-In 4.2, you can choose to use xm by simply changing the ctl_command
-variable and setting xend=YES in rc.conf.
-
-With xl, virtual devices are configured in parallel, which can cause
-problems if they are written assuming serial operation (e.g., updating
-firewall rules without explicit locking).  There is now locking for
-the provided scripts, which works for normal casses (e.g, file-backed
-xbd, where a vnd must be allocated).  But, as of 201612, it has not
-been adequately tested for a complex custom setup with a large number
-of interfaces.
-
 NetBSD versions
 ---------------
 
-The netbsd-7, netbsd-8, and -current branches are all reasonable
-choices, with more or less the same considerations for non-Xen use.
 NetBSD 8 is recommended as the stable version of the most recent
 release for production use.
 
@@ -128,24 +95,14 @@
 Architecture
 ------------
 
-Xen itself can run on i386 (Xen < 4.2) or amd64 hardware (all Xen
-versions).  Practically, almost any computer where one would want to
-run Xen today supports amd64.
-
-Xen, the dom0 system, and each domU system can be either i386 or
-amd64.  When building a xenkernel package, one obtains an i386 Xen
-kernel on an i386 host, and an amd64 Xen kernel on an amd64 host.  If
-the Xen kernel is i386, then the dom0 kernel and all domU kernels must
-be i386.  With an amd64 Xen kernel, an amd64 dom0 kernel is known to
-work, and an i386 dom0 kernel should in theory work.  An amd64
-Xen/dom0 is known to support both i386 and amd64 domUs.
-
-i386 dom0 and domU kernels must be PAE. PAE kernels are included in
-the NetBSD default build.
-
-Because of the above, the standard approach is to use an amd64 Xen
-kernel and NetBSD/amd64 for the dom0.  For domUs, NetBSD/i386 (PAE) and
-NetBSD/amd64 are in widespread use, and there is
+Xen itself runs on amd64 hardware. Practically, almost any computer
+where one would want to run Xen today supports amd64.
+
+The dom0 system, plus each domU, can be either i386PAE or amd64.
+i386 without PAE is not supported.
+
+The standard approach is to use NetBSD/amd64 for the dom0.  For domUs,
+NetBSD/i386 (PAE) and NetBSD/amd64 are in widespread use, and there is
 little to no Xen-specific reason to prefer one over the other.
 
 Note that to use an i386 dom0 with Xen 4.5 or higher, one must build
@@ -159,7 +116,7 @@
 there is some notion that i386 guests are faster.  It goes on to
 caution that the total situation is complex and not entirely
 understood. On top of that caution, the post is about Linux, not
-NetBSD.  TODO: Include link to benchmarks, if someone posts them.
+NetBSD.
 
 NetBSD as a dom0
 ================
@@ -245,40 +202,27 @@
 Installation of Xen
 -------------------
 
-In the dom0, install sysutils/xenkernel42 and sysutils/xentools42 from
-pkgsrc (or another matching pair).  See [the pkgsrc
-documentation](https://www.NetBSD.org/docs/pkgsrc/) for help with
-pkgsrc.  Ensure that your packages are recent; the HOWTO does not
-contemplate old builds.
-
-Next you need to install the selected Xen kernel itself, which is
-installed by pkgsrc as "/usr/pkg/xen*-kernel/xen.gz".  Copy it to /.
-For debugging, one may copy xen-debug.gz; this is conceptually similar
-to DIAGNOSTIC and DEBUG in NetBSD.  xen-debug.gz is basically only
-useful with a serial console.  Then, place a NetBSD XEN3_DOM0 kernel
-in /, copied from releasedir/amd64/binary/kernel/netbsd-XEN3_DOM0.gz
-of a NetBSD build.  If using i386, use
-releasedir/i386/binary/kernel/netbsd-XEN3PAE_DOM0.gz.  Both xen and
-the NetBSD kernel may be (and typically are) left compressed.
-
-In a dom0, kernfs is mandatory for xend to communicate with the
-kernel, so ensure that /kern is in fstab.  (A standard NetBSD install
-should already mount /kern.)
-
-Because you already installed NetBSD, you have a working boot setup
-with an MBR bootblock, either bootxx_ffsv1 or bootxx_ffsv2 at the
-beginning of your root file system, have /boot, and likely also
-/boot.cfg.  (If not, fix before continuing!)
+We will consider that you chose to use Xen 4.8, with NetBSD/amd64 as
+dom0. In the dom0, install xenkernel48 and xentools48 from pkgsrc.
+Ensure that your packages are recent.
+
+Once this is done, install the Xen kernel itself:
+
+[[!template id=programlisting text="""
+# cp /usr/pkg/xen48-kernel/xen.gz /
+"""]]
+
+Then, place a NetBSD XEN3_DOM0 kernel in /, copied from
+releasedir/amd64/binary/kernel/netbsd-XEN3_DOM0.gz of a NetBSD build.
 
-Add a line to /boot.cfg to boot Xen.  See boot.cfg(5) for an
-example.  The basic line is:
+Add a line to /boot.cfg to boot Xen:
 
 [[!template id=programlisting text="""
 menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=512M
 """]]
 
-which specifies that the dom0 should have 512M, leaving the rest to be
-allocated for domUs.  To use a serial console, use
+which specifies that the dom0 should have 512MB of ram, leaving the rest
+to be allocated for domUs.  To use a serial console, use
 
 [[!template id=programlisting text="""
 menu=Xen:load /netbsd-XEN3_DOM0.gz;multiboot /xen.gz dom0_mem=512M console=com1 com1=9600,8n1
@@ -298,7 +242,7 @@
 """]]
 
 to force only one vcpu to be provided (since NetBSD dom0 can't use
-more) and to pin that vcpu to a physical CPU.  TODO: benchmark this.
+more) and to pin that vcpu to a physical CPU.
 
 Xen has [many boot
 options](http://xenbits.xenproject.org/docs/4.5-testing/misc/xen-command-line.html),
@@ -306,11 +250,7 @@
 necessary.
 
 As with non-Xen systems, you should have a line to boot /netbsd (a
-kernel that works without Xen).  Consider a line to boot /netbsd.ok (a
-fallback version of the non-Xen kernel, updated manually when you are
-sure /netbsd is ok).  Consider also a line to boot fallback versions
-of Xen and the dom0 kernel, but note that non-Xen NetBSD can be used
-to resolve Xen booting issues.
+kernel that works without Xen).
 
 Now, reboot so that you are running a DOM0 kernel under Xen, rather
 than GENERIC without Xen.

polkit should be fixed now
Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/users/youri/pinebook-bugs.mdwn	30 Jul 2018 13:04:14 -0000	1.9
+++ wikisrc/users/youri/pinebook-bugs.mdwn	1 Aug 2018 09:33:24 -0000	1.10
@@ -33,6 +33,7 @@
 
 ## Pkgsrc bugs
 
-- polkit Memory fault (youri)
+- <del>polkit Memory fault</del>
+  - Fixed in spidermonkey52-52.7.4nb3
 - <del>www/firefox52 does not enable ARM64 asm for JS JIT engine.</del>
   - Fixed in firefox52-52.9.0nb4

Update hpcsh port wiki page
- Add link to EuroBSDCon 2004 paper (user on mailing list found it helpful)
- Update pkg_rel to 7.1 (there are no packages for 6.0)
Members: 
	ports/hpcsh.mdwn:1.16->1.17 

Index: wikisrc/ports/hpcsh.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/hpcsh.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/ports/hpcsh.mdwn	19 Jul 2018 10:15:06 -0000	1.16
+++ wikisrc/ports/hpcsh.mdwn	1 Aug 2018 07:45:44 -0000	1.17
@@ -2,7 +2,7 @@
 port="hpcsh"
 cur_rel="8.0"
 future_rel="9.0"
-pkg_rel="6.0"
+pkg_rel="7.1"
 changes_cur="8.0"
 changes_future="9.0"
 thumbnail="http://www.netbsd.org/images/ports/hpcsh/jornada690.gif"
@@ -47,6 +47,7 @@
     3.0](http://msdn.microsoft.com/mobility/windowsmobile/downloads/default.aspx)
 -   [SuperH RISC enabling Windows
     CE](http://semiconductor.hitachi.com/windowsce/)
+-   [NetBSD and handheld platforms (EuroBSDCon 2004)](http://www.stderr.spb.ru/~uwe/netbsd/jornada/netbsd-hpc-euro2004.pdf)
 """
 
 ]]

Update landisk port wiki page
- Landisk does not have its own mailing list, use port-sh3 list
- Update pkg_rel to 7.1 (there are no packages for 6.0)
Index: wikisrc/ports/landisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/landisk.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/ports/landisk.mdwn	19 Jul 2018 10:15:06 -0000	1.15
+++ wikisrc/ports/landisk.mdwn	1 Aug 2018 07:27:39 -0000	1.16
@@ -1,8 +1,9 @@
 [[!template id=port
 port="landisk"
+port_alt="sh3"
 cur_rel="8.0"
 future_rel="9.0"
-pkg_rel="6.0"
+pkg_rel="7.1"
 changes_cur="8.0"
 changes_future="9.0"
 about="""

Update the information about mpv SIGSEGVs and add a possible kludge and try to
describe and isolate the real problem about `strnlen(s, (size_t)-1)' behaviour.
Index: wikisrc/users/leot/aarch64_problems.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/leot/aarch64_problems.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/users/leot/aarch64_problems.mdwn	29 Jul 2018 10:59:29 -0000	1.10
+++ wikisrc/users/leot/aarch64_problems.mdwn	31 Jul 2018 22:22:28 -0000	1.11
@@ -4,7 +4,7 @@
 investigation in order to write proper PR or better yet to fix them!
 
 
-## `mpv` and NetBSD crashes
+## `mpv` SIGSEGVs (strnlen(s, (size_t)-1) always returns -1)
 Just by invoking `mpv` via:
 
     % mpv
@@ -59,56 +59,61 @@
     #3  0x00000002001cbea4 in ta_strdup_append_buffer (str=str@entry=0xf96f6f4ff348, a=<optimized out>) at ../ta/ta_utils.c:165
     #4  0x00000002001cb7b8 in ta_talloc_strdup_append_buffer (s=<optimized out>, s@entry=0x0, a=<optimized out>) at ../ta/ta_talloc.c:31
     #5  0x0000000200157eec in print_str_list (opt=<optimized out>, src=<optimized out>) at ../options/m_option.c:1477
-    #6  0x000000020015db90 in m_option_print (val_ptr=0xf96f6f4ff3c0, opt=0xf96f6f4ff430) at ../options/m_option.h:496
-    #7  m_property_do (log=0xf96f71045130, prop_list=0xf96f71081040, name=name@entry=0xf96f6e139218 "property-list",
-        action=action@entry=6, arg=arg@entry=0xf96f6f4ff598, ctx=ctx@entry=0xf96f71011040) at ../options/m_property.c:127
-    #8  0x000000020016f9f8 in mp_property_do_silent (name=0xf96f6e139218 "property-list", action=6, val=0xf96f6f4ff598, ctx=0xf96f71011040)
-        at ../player/command.c:4167
-    #9  0x0000000200171014 in mp_property_do (name=0xf96f6e139218 "property-list", action=action@entry=6, val=<optimized out>,
-        val@entry=0xf96f6f4ff5c8, ctx=0xf96f71011040) at ../player/command.c:4177
-    #10 0x00000002001637bc in getproperty_fn (arg=0xf96f6f4ff5d8, arg@entry=0xf96f6f4ff5e8) at ../player/client.c:1261
-    #11 0x00000002001655b0 in run_locked (fn_data=0xf96f6f4ff5e8, fn=0x200163648 <getproperty_fn>, ctx=0xf96f6f5071c0)
-        at ../player/client.c:1003
-    #12 mpv_get_property (ctx=0xf96f6f5071c0, name=name@entry=0xf96f6e139218 "property-list", format=format@entry=MPV_FORMAT_STRING,
-        data=data@entry=0xf96f6f4ff668) at ../player/client.c:1335
-    #13 0x0000000200179b4c in script_get_property (L=0xf96f6e103400) at ../player/lua.c:794
-    #14 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
-    #15 0x0000f96f72b3877c in luaV_execute () from /usr/pkg/lib/liblua5.2.so.5
-    #16 0x0000f96f72b2cf04 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
-    #17 0x0000f96f72b28e40 in lua_callk () from /usr/pkg/lib/liblua5.2.so.5
-    #18 0x0000000200178270 in load_builtin (L=0xf96f6e103400) at ../player/lua.c:214
-    #19 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
-    #20 0x0000f96f72b2cef8 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
-    #21 0x0000f96f72b28e40 in lua_callk () from /usr/pkg/lib/liblua5.2.so.5
-    #22 0x0000f96f72b43900 in ll_require () from /usr/pkg/lib/liblua5.2.so.5
-    #23 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
-    ---Type <return> to continue, or q <return> to quit---
-    #24 0x0000f96f72b3877c in luaV_execute () from /usr/pkg/lib/liblua5.2.so.5
-    #25 0x0000f96f72b2cf04 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
-    #26 0x0000f96f72b28e40 in lua_callk () from /usr/pkg/lib/liblua5.2.so.5
-    #27 0x0000000200179524 in require (L=L@entry=0xf96f6e103400, name=name@entry=0xf96f6f503420 "@stats.lua") at ../player/lua.c:232
-    #28 0x000000020017963c in load_scripts (L=0xf96f6e103400) at ../player/lua.c:260
-    #29 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
-    #30 0x0000f96f72b2cef8 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
-    #31 0x0000f96f72b2c4b8 in luaD_rawrunprotected () from /usr/pkg/lib/liblua5.2.so.5
-    #32 0x0000f96f72b2d19c in luaD_pcall () from /usr/pkg/lib/liblua5.2.so.5
-    #33 0x0000f96f72b28f14 in lua_pcallk () from /usr/pkg/lib/liblua5.2.so.5
-    #34 0x000000020017b020 in run_lua (L=0xf96f6e103400) at ../player/lua.c:354
-    #35 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
-    #36 0x0000f96f72b2cef8 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
-    #37 0x0000f96f72b2c4b8 in luaD_rawrunprotected () from /usr/pkg/lib/liblua5.2.so.5
-    #38 0x0000f96f72b2d19c in luaD_pcall () from /usr/pkg/lib/liblua5.2.so.5
-    #39 0x0000f96f72b28f14 in lua_pcallk () from /usr/pkg/lib/liblua5.2.so.5
-    #40 0x000000020017b4c8 in mp_cpcall (func=0x20017abd0 <run_lua>, ud=0xf96f6e1010c0, L=0xf96f6e103400) at ../player/lua.c:99
-    #41 load_lua (client=<optimized out>, fname=0xf96f6f503420 "@stats.lua") at ../player/lua.c:387
-    #42 0x00000002001815c0 in script_thread (p=0xf96f6f5050c0) at ../player/scripting.c:95
-    #43 0x0000f96f743ec588 in pthread__create_tramp (cookie=0xf96f6f515000) at /usr/src/lib/libpthread/pthread.c:593
-    #44 0x0000f96f727385ec in _lwp_makecontext (u=0x0, start=0x0, arg=0x0, private=0xff00000014,
-        stack_base=0x1 <error: Cannot access memory at address 0x1>, stack_size=8589934592) at /usr/src/lib/libc/arch/aarch64/gen/_lwp.c:47
-    #45 0x0000f96f743df000 in ?? ()
-    #46 0x544a8f02d40034c1 in ?? ()
-    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
+    [...]
 
+This happens because `strnlen(s, (size_t)-1)`, always returns -1, e.g.:
+
+    % cat strnlen_size_max.c
+    #include <stdio.h>
+    #include <string.h>
+    
+    
+    int
+    main(int argc, char *argv[])
+    {
+    	int i;
+    	for (i = 1; i < argc; i++) {
+    		printf("strnlen(\"%s\", (size_t)-1) -> %ld\n",
+    		    argv[i], strnlen(argv[i], ~(size_t)0));
+    	}
+    
+    	return 0;
+    }
+    % gcc -Wall strnlen_size_max.c
+    % ./a.out foo
+    strnlen("foo", (size_t)-1) -> -1
+
+(This should returns 3, not -1!)
+
+The following patch workaround the mpv problem by avoiding all
+`strnlen(s, (size_t)-1)` calls (and just using strlen() instead):
+
+    $NetBSD: aarch64_problems.mdwn,v 1.11 2018/07/31 22:22:28 leot Exp $
+    
+    Avoid to directly call:
+    
+     strnlen(s, (size_t)-1)
+    
+    because on aarch64 ATM it (incorrectly) always returns -1 (also
+    when s is a string with less than SIZE_MAX characters).
+    
+    Add a kludge in order to use strlen() in these cases.
+    
+    --- ta/ta_utils.c.orig	2018-07-31 21:45:47.492269366 +0000
+    +++ ta/ta_utils.c
+    @@ -98,7 +98,11 @@ static bool strndup_append_at(char **str
+         if (!*str && !append)
+             return true; // stays NULL, but not an OOM condition
+     
+    -    size_t real_len = append ? strnlen(append, append_len) : 0;
+    +    size_t real_len = append ?
+    +	append_len == (size_t)-1 ?
+    +	   strlen(append) :
+    +	   strnlen(append, append_len) :
+    +	0;
+         if (append_len > real_len)
+             append_len = real_len;
+ 
 
 ## Python `import requests` SIGILLs
 Doing a (please note that also `python36` is affected):

linkify links
Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/users/youri/pinebook-bugs.mdwn	30 Jul 2018 12:26:08 -0000	1.8
+++ wikisrc/users/youri/pinebook-bugs.mdwn	30 Jul 2018 13:04:14 -0000	1.9
@@ -7,7 +7,7 @@
 
 ## Firmware / hardware issues
 - ANX6345 EDID detection fails at boot with sysutils/u-boot-pinebook
-  - Patch to use static EDID and LCD parameters for 14" Pinebook: http://www.netbsd.org/~jmcneill/patch-drivers_video_bridge_anx6345.c
+  - Patch to use static EDID and LCD parameters for 14" Pinebook: <http://www.netbsd.org/~jmcneill/patch-drivers_video_bridge_anx6345.c>
 
 ## Kernel Bugs
 
@@ -19,13 +19,13 @@
 ## TODO
 
 - Native display driver (2D)
-  - Display Engine 2.0 manual: http://linux-sunxi.org/images/7/7b/Allwinner_DE2.0_Spec_V1.0.pdf
+  - Display Engine 2.0 manual: <http://linux-sunxi.org/images/7/7b/Allwinner_DE2.0_Spec_V1.0.pdf>
   - Should be implemented as a DRM driver to support KMS and 3D
 - 3D graphics
-  - Should be supported by lima driver: https://gitlab.freedesktop.org/lima/web/wikis/home (GPL)
+  - Should be supported by lima driver: <https://gitlab.freedesktop.org/lima/web/wikis/home> (GPL)
   - Requires DRM PRIME
 - VPU
-  - Linux kernel support: https://lkml.org/lkml/2018/7/25/267
+  - Linux kernel support: <https://lkml.org/lkml/2018/7/25/267>
 - wifi support
 - bluetooth support
 - suspend/resume support

urtwn and firefox52 issues resolved
Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:55:28 -0000	1.7
+++ wikisrc/users/youri/pinebook-bugs.mdwn	30 Jul 2018 12:26:08 -0000	1.8
@@ -11,7 +11,8 @@
 
 ## Kernel Bugs
 
-- USB devices sometimes not detected after reboot
+- <del>USB devices sometimes not detected after reboot</del>
+  - urtwn(4) issue with 88EU support, workaround committed
 - Some USB keyboards cause problems (full sized FILCO tested)
 - sdmmc: DDR52 and HS200 are currently disabled in sunximmc(4) for Allwinner A64 due to issues on other boards. Need to track these down so we can run eMMC at full speed.
 
@@ -33,4 +34,5 @@
 ## Pkgsrc bugs
 
 - polkit Memory fault (youri)
-- www/firefox52 does not enable ARM64 asm for JS JIT engine. Setting JS_CODEGEN_ARM64=1 results in a working (much faster) build, but not sure where this needs to be patched in to the package.
+- <del>www/firefox52 does not enable ARM64 asm for JS JIT engine.</del>
+  - Fixed in firefox52-52.9.0nb4

It's unlikely new build mechanisms will be added to netbsd-7 for DTrace.
--- wikisrc/tutorials/how_to_enable_and_run_dtrace/comment_1_31ab21a2670f5b84e9b71928eed7a1a0._comment	2018-07-29 23:18:13.000000000 +0000
+++ /dev/null	2018-07-29 23:18:02.000000000 +0000
@@ -1,23 +0,0 @@
-[[!comment format=mdwn
- username="miwarin@0313732bc8d467929d936e58b4035a129c8f703c"
- nickname="miwarin"
- subject="build option...."
- date="2016-05-05T14:15:53Z"
- content="""
-(NetBSD 7.0 i386)
-
-please fix.
-
-add to build.sh option:
-
-    -V SLOPPY_FLIST=yes 
-
-modload command miss. Properly do this:
-
-    modload solaris
-    modload dtrace
-    modload sdt
-    modload fbt
-    modload profile
-
-"""]]

Try to tweak font size
Index: wikisrc/users/kamil/proposals.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/kamil/proposals.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/kamil/proposals.mdwn	29 Jul 2018 19:24:08 -0000	1.2
+++ wikisrc/users/kamil/proposals.mdwn	29 Jul 2018 19:27:00 -0000	1.3
@@ -24,77 +24,77 @@
  - addition of ATF (automated test framework in NetBSD) regression tests covering the new feature,
  - integration with MKSANITIZER/MKLIBCSANITIZER/kernel.
 
-# Port the LLVM DataFlow sanitizer to NetBSD (MKSANITIZER).
+#### Port the LLVM DataFlow sanitizer to NetBSD (MKSANITIZER).
 
 Not started and not researched.
 
-# Port Scudo to NetBSD (MKSANITIZER).
+#### Port Scudo to NetBSD (MKSANITIZER).
 
 There is a draft port, however tests are designed against the
 GNU malloc(3) API (mallinfo). Porting or reimplementing the
 tests for jemalloc(3) is needed. The feature might be fully
 functional with local patches, but its status is unknown.
 
-# Port LLVM CFI to NetBSD (MKSANITIZER).
+#### Port LLVM CFI to NetBSD (MKSANITIZER).
 
 This project certainly needs commitment and connection of
 all the toolchain pieces together. It might require work
 on programs like ar(1), ld(1), and dynamic ELF loader.
 
-# Port SafeStack to MKSANITIZER.
+#### Port SafeStack to MKSANITIZER.
 
 The port is done. All tests pass. It needs research and
 integration as the MKSANITIZER option. It might work
 out of the box, but it's not tested and not researched.
 
-# Research and reimplement safestack shared between MKLIBCSANITIZER and the kernel.
+#### Research and reimplement safestack shared between MKLIBCSANITIZER and the kernel.
 
 Already done by Fuchsia, a research OS from Google.
 The feature must be C++ free, similar to micro-UBSan.
 
-# Port the LLVM cov, profile, xray, and sancov profiling to NetBSD.
+#### Port the LLVM cov, profile, xray, and sancov profiling to NetBSD.
 
 Most of this already works, but investigation
 of the failing tests is needed.
 
 A quick comparison (as explained by an upstream developer):
 
-## cov
+##### cov
 
 Did my test execute everything?
 
-## profile
+##### profile
 
 Record optimizer-relevant details of what was executed.
 Profile can have performance overhead where useful, as
 long as it doesn't skew the profile or make it unusable.
 
-## xray
+##### xray
 
 Record programmer-relevant details of what was
 executed. Xray must have *absolute* minimal overhead
 when *not* doing anything, but ability dynamically
 to enable this kind of tracing is necessary.
 
-## sancov
+##### sancov
 
 Record the degree to which possible paths/data are covered
 by fuzz testing, in order to direct the fuzzer itself.
 
-# Research LLVM cov, profile and sancov in the NetBSD kernel. Compare it to Linux and FreeBSD KCOV.
+#### Research LLVM cov, profile and sancov in the NetBSD kernel. Compare it to Linux and FreeBSD KCOV.
 
 Port as much as possible to the NetBSD kernel.
 
-# Research LLVM XRay as a replacement of DTrace in the NetBSD kernel.
+#### Research LLVM XRay as a replacement of DTrace in the NetBSD kernel.
 
 This is a tricky feature with userland assumptions.
 Upstream is looking forward to this research and offers assistance.
 
-# Port AFL Triforce kernel fuzzer to NetBSD.
+#### Port AFL Triforce kernel fuzzer to NetBSD.
 
 A port to OpenBSD already exists. Port and eliminate bugs.
 
-# Integration of rumpkernel (the NetBSD kernel) with userland tools.
+#### Integration of rumpkernel (the NetBSD kernel) with userland tools.
 
 Slice the NetBSD kernel in userland as a library,
 and integrate fuzzers with the subsystems (network

Tweak the syntax to improve the rendering
Index: wikisrc/users/kamil/proposals.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/kamil/proposals.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/kamil/proposals.mdwn	29 Jul 2018 19:20:24 -0000	1.1
+++ wikisrc/users/kamil/proposals.mdwn	29 Jul 2018 19:24:08 -0000	1.2
@@ -24,69 +24,77 @@
  - addition of ATF (automated test framework in NetBSD) regression tests covering the new feature,
  - integration with MKSANITIZER/MKLIBCSANITIZER/kernel.
 
-1. Port the LLVM DataFlow sanitizer to NetBSD (MKSANITIZER).
+# Port the LLVM DataFlow sanitizer to NetBSD (MKSANITIZER).
 
 Not started and not researched.
 
-2. Port Scudo to NetBSD (MKSANITIZER).
+# Port Scudo to NetBSD (MKSANITIZER).
 
 There is a draft port, however tests are designed against the
 GNU malloc(3) API (mallinfo). Porting or reimplementing the
 tests for jemalloc(3) is needed. The feature might be fully
 functional with local patches, but its status is unknown.
 
-3. Port LLVM CFI to NetBSD (MKSANITIZER).
+# Port LLVM CFI to NetBSD (MKSANITIZER).
 
 This project certainly needs commitment and connection of
 all the toolchain pieces together. It might require work
 on programs like ar(1), ld(1), and dynamic ELF loader.
 
-4. Port SafeStack to MKSANITIZER.
+# Port SafeStack to MKSANITIZER.
 
 The port is done. All tests pass. It needs research and
 integration as the MKSANITIZER option. It might work
 out of the box, but it's not tested and not researched.
 
-5. Research and reimplement safestack shared between MKLIBCSANITIZER and the kernel.
+# Research and reimplement safestack shared between MKLIBCSANITIZER and the kernel.
 
 Already done by Fuchsia, a research OS from Google.
 The feature must be C++ free, similar to micro-UBSan.
 
-6. Port the LLVM cov, profile, xray, and sancov profiling to NetBSD.
+# Port the LLVM cov, profile, xray, and sancov profiling to NetBSD.
 
 Most of this already works, but investigation
 of the failing tests is needed.
 
 A quick comparison (as explained by an upstream developer):
 
-cov -> Did my test execute everything?
+## cov
 
-profile -> Record optimizer-relevant details of what was executed.
-           Profile can have performance overhead where useful, as
-	   long as it doesn't skew the profile or make it unusable.
+Did my test execute everything?
 
-xray -> Record programmer-relevant details of what was
-        executed. Xray must have *absolute* minimal overhead
-        when *not* doing anything, but ability dynamically
-        to enable this kind of tracing is necessary.
+## profile
 
-sancov -> Record the degree to which possible paths/data are covered
-          by fuzz testing, in order to direct the fuzzer itself.
+Record optimizer-relevant details of what was executed.
+Profile can have performance overhead where useful, as
+long as it doesn't skew the profile or make it unusable.
 
-7. Research LLVM cov, profile and sancov in the NetBSD kernel. Compare it to Linux and FreeBSD KCOV.
+## xray
+
+Record programmer-relevant details of what was
+executed. Xray must have *absolute* minimal overhead
+when *not* doing anything, but ability dynamically
+to enable this kind of tracing is necessary.
+
+## sancov
+
+Record the degree to which possible paths/data are covered
+by fuzz testing, in order to direct the fuzzer itself.
+
+# Research LLVM cov, profile and sancov in the NetBSD kernel. Compare it to Linux and FreeBSD KCOV.
 
 Port as much as possible to the NetBSD kernel.
 
-8. Research LLVM XRay as a replacement of DTrace in the NetBSD kernel.
+# Research LLVM XRay as a replacement of DTrace in the NetBSD kernel.
 
 This is a tricky feature with userland assumptions.
 Upstream is looking forward to this research and offers assistance.
 
-9. Port AFL Triforce kernel fuzzer to NetBSD.
+# Port AFL Triforce kernel fuzzer to NetBSD.
 
 A port to OpenBSD already exists. Port and eliminate bugs.
 
-10. Integration of rumpkernel (the NetBSD kernel) with userland tools.
+# Integration of rumpkernel (the NetBSD kernel) with userland tools.
 
 Slice the NetBSD kernel in userland as a library,
 and integrate fuzzers with the subsystems (network

Add a list of project proposals for students
Topic: sanitizers and fuzzers.
Members: 
	users/kamil/proposals.mdwn:INITIAL->1.1 

--- /dev/null	2018-07-29 19:20:02.000000000 +0000
+++ wikisrc/users/kamil/proposals.mdwn	2018-07-29 19:20:41.000000000 +0000
@@ -0,0 +1,97 @@
+Projects proposal
+
+Two kinds of tasks:
+
+ - sanitization,
+ - fuzzing.
+
+And in particular sanitization in the context of:
+
+ - MKSANITIZER (using the default runtime ported to NetBSD),
+ - MKLIBCSANITIZER (a reimplementation of the runtime inside libc),
+ - kernel (a reimplementation of the userland runtime, usually inspired by the counterpart in a different OS).
+
+Fuzzing covers:
+
+ - userland programs and libraries,
+ - the kernel.
+
+A typical project consist of:
+
+ - work directly on the LLVM trunk version, unless the feature is available in a stable release,
+ - if needed, porting and upstreaming of NetBSD support to LLVM,
+ - validation of the feature against upstream test-suite, porting the tests to it,
+ - addition of ATF (automated test framework in NetBSD) regression tests covering the new feature,
+ - integration with MKSANITIZER/MKLIBCSANITIZER/kernel.
+
+1. Port the LLVM DataFlow sanitizer to NetBSD (MKSANITIZER).
+
+Not started and not researched.
+
+2. Port Scudo to NetBSD (MKSANITIZER).
+
+There is a draft port, however tests are designed against the
+GNU malloc(3) API (mallinfo). Porting or reimplementing the
+tests for jemalloc(3) is needed. The feature might be fully
+functional with local patches, but its status is unknown.
+
+3. Port LLVM CFI to NetBSD (MKSANITIZER).
+
+This project certainly needs commitment and connection of
+all the toolchain pieces together. It might require work
+on programs like ar(1), ld(1), and dynamic ELF loader.
+
+4. Port SafeStack to MKSANITIZER.
+
+The port is done. All tests pass. It needs research and
+integration as the MKSANITIZER option. It might work
+out of the box, but it's not tested and not researched.
+
+5. Research and reimplement safestack shared between MKLIBCSANITIZER and the kernel.
+
+Already done by Fuchsia, a research OS from Google.
+The feature must be C++ free, similar to micro-UBSan.
+
+6. Port the LLVM cov, profile, xray, and sancov profiling to NetBSD.
+
+Most of this already works, but investigation
+of the failing tests is needed.
+
+A quick comparison (as explained by an upstream developer):
+
+cov -> Did my test execute everything?
+
+profile -> Record optimizer-relevant details of what was executed.
+           Profile can have performance overhead where useful, as
+	   long as it doesn't skew the profile or make it unusable.
+
+xray -> Record programmer-relevant details of what was
+        executed. Xray must have *absolute* minimal overhead
+        when *not* doing anything, but ability dynamically
+        to enable this kind of tracing is necessary.
+
+sancov -> Record the degree to which possible paths/data are covered
+          by fuzz testing, in order to direct the fuzzer itself.
+
+7. Research LLVM cov, profile and sancov in the NetBSD kernel. Compare it to Linux and FreeBSD KCOV.
+
+Port as much as possible to the NetBSD kernel.
+
+8. Research LLVM XRay as a replacement of DTrace in the NetBSD kernel.
+
+This is a tricky feature with userland assumptions.
+Upstream is looking forward to this research and offers assistance.
+
+9. Port AFL Triforce kernel fuzzer to NetBSD.
+
+A port to OpenBSD already exists. Port and eliminate bugs.
+
+10. Integration of rumpkernel (the NetBSD kernel) with userland tools.
+
+Slice the NetBSD kernel in userland as a library,
+and integrate fuzzers with the subsystems (network
+stack, syscall layer, SCSI stack, filesystems, etc.).
+
+There is a research project in which rumpkernel has been
+successfully fuzzed on the syscall layer with AFL. The layer
+accepts input generated by the fuzzer via standard input stream.

Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:48:55 -0000	1.6
+++ wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:55:28 -0000	1.7
@@ -1,5 +1,10 @@
 # Pinebook bugs
 
+## Info
+- Pinebook function key usage on the wiki: [[ports/evbarm/allwinner]]
+- Schematics: <http://wiki.pine64.org/index.php/Pinebook_Main_Page#Pinebook_Schematics_and_Certifications>
+- Datasheets: <http://wiki.pine64.org/index.php/Pinebook_Main_Page#Datasheets_for_Components_and_Peripherals>
+
 ## Firmware / hardware issues
 - ANX6345 EDID detection fails at boot with sysutils/u-boot-pinebook
   - Patch to use static EDID and LCD parameters for 14" Pinebook: http://www.netbsd.org/~jmcneill/patch-drivers_video_bridge_anx6345.c

add sysinst to todo list
Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:42:13 -0000	1.5
+++ wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:48:55 -0000	1.6
@@ -23,6 +23,7 @@
 - wifi support
 - bluetooth support
 - suspend/resume support
+- sysinst support
 
 ## Pkgsrc bugs
 

Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:40:26 -0000	1.4
+++ wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:42:13 -0000	1.5
@@ -8,6 +8,7 @@
 
 - USB devices sometimes not detected after reboot
 - Some USB keyboards cause problems (full sized FILCO tested)
+- sdmmc: DDR52 and HS200 are currently disabled in sunximmc(4) for Allwinner A64 due to issues on other boards. Need to track these down so we can run eMMC at full speed.
 
 ## TODO
 

www/firefox52 notes
Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:37:10 -0000	1.3
+++ wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:40:26 -0000	1.4
@@ -26,3 +26,4 @@
 ## Pkgsrc bugs
 
 - polkit Memory fault (youri)
+- www/firefox52 does not enable ARM64 asm for JS JIT engine. Setting JS_CODEGEN_ARM64=1 results in a working (much faster) build, but not sure where this needs to be patched in to the package.

Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:21:46 -0000	1.2
+++ wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:37:10 -0000	1.3
@@ -11,6 +11,14 @@
 
 ## TODO
 
+- Native display driver (2D)
+  - Display Engine 2.0 manual: http://linux-sunxi.org/images/7/7b/Allwinner_DE2.0_Spec_V1.0.pdf
+  - Should be implemented as a DRM driver to support KMS and 3D
+- 3D graphics
+  - Should be supported by lima driver: https://gitlab.freedesktop.org/lima/web/wikis/home (GPL)
+  - Requires DRM PRIME
+- VPU
+  - Linux kernel support: https://lkml.org/lkml/2018/7/25/267
 - wifi support
 - bluetooth support
 - suspend/resume support

Index: wikisrc/users/youri/pinebook-bugs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri/pinebook-bugs.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 17:58:08 -0000	1.1
+++ wikisrc/users/youri/pinebook-bugs.mdwn	29 Jul 2018 18:21:46 -0000	1.2
@@ -1,7 +1,12 @@
 # Pinebook bugs
 
+## Firmware / hardware issues
+- ANX6345 EDID detection fails at boot with sysutils/u-boot-pinebook
+  - Patch to use static EDID and LCD parameters for 14" Pinebook: http://www.netbsd.org/~jmcneill/patch-drivers_video_bridge_anx6345.c
+
 ## Kernel Bugs
 
+- USB devices sometimes not detected after reboot
 - Some USB keyboards cause problems (full sized FILCO tested)
 
 ## TODO

New pinebook bugs page
--- /dev/null	2018-07-29 17:58:04.000000000 +0000
+++ wikisrc/users/youri/pinebook-bugs.mdwn	2018-07-29 17:58:22.000000000 +0000
@@ -0,0 +1,15 @@
+# Pinebook bugs
+
+## Kernel Bugs
+
+- Some USB keyboards cause problems (full sized FILCO tested)
+
+## TODO
+
+- wifi support
+- bluetooth support
+- suspend/resume support
+
+## Pkgsrc bugs
+
+- polkit Memory fault (youri)

Index: wikisrc/users/youri.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/youri.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/users/youri.mdwn	11 Apr 2016 20:06:16 -0000	1.6
+++ wikisrc/users/youri.mdwn	29 Jul 2018 17:55:52 -0000	1.7
@@ -1,4 +1,5 @@
 My corner of the NetBSD wiki
 
+- [[pinebook-bugs]] 
 - [[xfce4]] desktop work
 - [[hackathon2016]]

Added a comment: Consolekit issue
--- /dev/null	2018-07-29 17:49:04.000000000 +0000
+++ wikisrc/users/leot/aarch64_problems/comment_1_26a73982b532e325d5b2b5e2bc2ef915._comment	2018-07-29 17:49:43.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="youri"
+ subject="Consolekit issue"
+ date="2018-07-29T17:49:24Z"
+ content="""
+Please run $PREFIX/sbin/console-kit-daemon to get the database and pid files in /var/run :)
+I'm currently debugging the memory fault on the pinebook
+"""]]

Add myself
Index: wikisrc/summits/eurobsdcon_2018.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2018.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/summits/eurobsdcon_2018.mdwn	27 Jul 2018 02:19:13 -0000	1.10
+++ wikisrc/summits/eurobsdcon_2018.mdwn	29 Jul 2018 11:06:17 -0000	1.11
@@ -20,6 +20,7 @@
 Siddharth Muralee | `@` |
 Stephen Borrill | `sborrill@` |
 Maya Rashish | `maya@` |
+Adrian Steinmann | `ast@` |
  | |
 """]]
 

Do not share the possible LOCALPATCHES and just add a note about that the kludge
is present since py-cffi-1.11.5nb1.
Index: wikisrc/users/leot/aarch64_problems.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/leot/aarch64_problems.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/users/leot/aarch64_problems.mdwn	28 Jul 2018 19:14:29 -0000	1.9
+++ wikisrc/users/leot/aarch64_problems.mdwn	29 Jul 2018 10:59:29 -0000	1.10
@@ -225,23 +225,8 @@
     #define _cffi_save_errno                                                 \
         ((void(*)(void))_cffi_exports[14])
 
-The following patch workaround the issue:
-
-    $NetBSD: aarch64_problems.mdwn,v 1.9 2018/07/28 19:14:29 leot Exp $
-    
-    Kludge for NetBSD/aarch64 SIGILL.
-    
-    --- setup.py.orig	2018-02-27 18:15:41.000000000 +0000
-    +++ setup.py
-    @@ -70,7 +70,7 @@ def ask_supports_thread():
-         ok = (sys.platform != 'win32' and
-               config.try_compile('__thread int some_threadlocal_variable_42;'))
-         if ok:
-    -        define_macros.append(('USE__THREAD', None))
-    +        pass
-         else:
-             ok1 = config.try_compile('int some_regular_variable_42;')
-             if not ok1:
+Since py-cffi-1.11.5nb1 a kludge to workaround the issue is present (by
+disabling __thread).
 
 
 ## polkitd crashes

Update the mpv entry.
Now the problem is in the userland and we have a .core!
Members: 
	users/leot/aarch64_problems.mdwn:1.8->1.9 

Index: wikisrc/users/leot/aarch64_problems.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/leot/aarch64_problems.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/users/leot/aarch64_problems.mdwn	24 Jul 2018 00:09:53 -0000	1.8
+++ wikisrc/users/leot/aarch64_problems.mdwn	28 Jul 2018 19:14:29 -0000	1.9
@@ -7,12 +7,107 @@
 ## `mpv` and NetBSD crashes
 Just by invoking `mpv` via:
 
-    $ mpv
+    % mpv
 
-It is possible to completely crash NetBSD on aarch64. Investigate why and if
-possible get a complete backtrace.
+It SEGV as follows:
 
-(Is it PaX MPROTECT related?)
+    % mpv
+    /usr/pkg/lib/ffmpeg4/libavcodec.so.58: text relocations
+    mpv 0.29.0 Copyright © 2000-2018 mpv/MPlayer/mplayer2 projects
+     built on Sat Jul 28 21:02:57 CEST 2018
+    ffmpeg library versions:
+       libavutil       56.14.100
+       libavcodec      58.18.100
+       libavformat     58.12.100
+       libswscale      5.1.100
+       libavfilter     7.16.100
+       libswresample   3.1.100
+    ffmpeg version: 4.0.2
+    
+    Usage:   mpv [options] [url|path/]filename
+    
+    Basic options:
+     --start=<time>    seek to given (percent, seconds, or hh:mm:ss) position
+     --no-audio        do not play sound
+     --no-video        do not play video
+     --fs              fullscreen playback
+     --sub-file=<file> specify subtitle file to use
+     --playlist=<file> specify playlist file
+    
+     --list-options    list all mpv options
+     --h=<string>      print options which contain the given string in their name
+    
+    [1]   Segmentation fault (core dumped) /usr/pkg/bin/mpv...
+    % gdb -core mpv.core /usr/pkg/bin/mpv
+    Reading symbols from /usr/pkg/bin/mpv...done.
+    [New process 5]
+    [New process 6]
+    [New process 4]
+    [New process 3]
+    [New process 2]
+    [New process 1]
+    Core was generated by `mpv'.
+    Program terminated with signal SIGSEGV, Segmentation fault.
+    #0  0x0000f96f727f40b0 in memcpy () from /usr/lib/libc.so.12
+    [Current thread is 1 (process 5)]
+    (gdb) bt
+    #0  0x0000f96f727f40b0 in memcpy () from /usr/lib/libc.so.12
+    #1  0x00000002001cba34 in __memcpy_ichk (len=18446744073709551615, src=0xf96f6e10fec0, dst=<optimized out>)
+        at /usr/include/ssp/string.h:82
+    #2  strndup_append_at (str=str@entry=0xf96f6f4ff348, at=0, append=0xf96f6e10fec0 "speed", append_len=<optimized out>,
+        append_len@entry=18446744073709551615) at ../ta/ta_utils.c:113
+    #3  0x00000002001cbea4 in ta_strdup_append_buffer (str=str@entry=0xf96f6f4ff348, a=<optimized out>) at ../ta/ta_utils.c:165
+    #4  0x00000002001cb7b8 in ta_talloc_strdup_append_buffer (s=<optimized out>, s@entry=0x0, a=<optimized out>) at ../ta/ta_talloc.c:31
+    #5  0x0000000200157eec in print_str_list (opt=<optimized out>, src=<optimized out>) at ../options/m_option.c:1477
+    #6  0x000000020015db90 in m_option_print (val_ptr=0xf96f6f4ff3c0, opt=0xf96f6f4ff430) at ../options/m_option.h:496
+    #7  m_property_do (log=0xf96f71045130, prop_list=0xf96f71081040, name=name@entry=0xf96f6e139218 "property-list",
+        action=action@entry=6, arg=arg@entry=0xf96f6f4ff598, ctx=ctx@entry=0xf96f71011040) at ../options/m_property.c:127
+    #8  0x000000020016f9f8 in mp_property_do_silent (name=0xf96f6e139218 "property-list", action=6, val=0xf96f6f4ff598, ctx=0xf96f71011040)
+        at ../player/command.c:4167
+    #9  0x0000000200171014 in mp_property_do (name=0xf96f6e139218 "property-list", action=action@entry=6, val=<optimized out>,
+        val@entry=0xf96f6f4ff5c8, ctx=0xf96f71011040) at ../player/command.c:4177
+    #10 0x00000002001637bc in getproperty_fn (arg=0xf96f6f4ff5d8, arg@entry=0xf96f6f4ff5e8) at ../player/client.c:1261
+    #11 0x00000002001655b0 in run_locked (fn_data=0xf96f6f4ff5e8, fn=0x200163648 <getproperty_fn>, ctx=0xf96f6f5071c0)
+        at ../player/client.c:1003
+    #12 mpv_get_property (ctx=0xf96f6f5071c0, name=name@entry=0xf96f6e139218 "property-list", format=format@entry=MPV_FORMAT_STRING,
+        data=data@entry=0xf96f6f4ff668) at ../player/client.c:1335
+    #13 0x0000000200179b4c in script_get_property (L=0xf96f6e103400) at ../player/lua.c:794
+    #14 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
+    #15 0x0000f96f72b3877c in luaV_execute () from /usr/pkg/lib/liblua5.2.so.5
+    #16 0x0000f96f72b2cf04 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
+    #17 0x0000f96f72b28e40 in lua_callk () from /usr/pkg/lib/liblua5.2.so.5
+    #18 0x0000000200178270 in load_builtin (L=0xf96f6e103400) at ../player/lua.c:214
+    #19 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
+    #20 0x0000f96f72b2cef8 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
+    #21 0x0000f96f72b28e40 in lua_callk () from /usr/pkg/lib/liblua5.2.so.5
+    #22 0x0000f96f72b43900 in ll_require () from /usr/pkg/lib/liblua5.2.so.5
+    #23 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
+    ---Type <return> to continue, or q <return> to quit---
+    #24 0x0000f96f72b3877c in luaV_execute () from /usr/pkg/lib/liblua5.2.so.5
+    #25 0x0000f96f72b2cf04 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
+    #26 0x0000f96f72b28e40 in lua_callk () from /usr/pkg/lib/liblua5.2.so.5
+    #27 0x0000000200179524 in require (L=L@entry=0xf96f6e103400, name=name@entry=0xf96f6f503420 "@stats.lua") at ../player/lua.c:232
+    #28 0x000000020017963c in load_scripts (L=0xf96f6e103400) at ../player/lua.c:260
+    #29 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
+    #30 0x0000f96f72b2cef8 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
+    #31 0x0000f96f72b2c4b8 in luaD_rawrunprotected () from /usr/pkg/lib/liblua5.2.so.5
+    #32 0x0000f96f72b2d19c in luaD_pcall () from /usr/pkg/lib/liblua5.2.so.5
+    #33 0x0000f96f72b28f14 in lua_pcallk () from /usr/pkg/lib/liblua5.2.so.5
+    #34 0x000000020017b020 in run_lua (L=0xf96f6e103400) at ../player/lua.c:354
+    #35 0x0000f96f72b2cb80 in luaD_precall () from /usr/pkg/lib/liblua5.2.so.5
+    #36 0x0000f96f72b2cef8 in luaD_call () from /usr/pkg/lib/liblua5.2.so.5
+    #37 0x0000f96f72b2c4b8 in luaD_rawrunprotected () from /usr/pkg/lib/liblua5.2.so.5
+    #38 0x0000f96f72b2d19c in luaD_pcall () from /usr/pkg/lib/liblua5.2.so.5
+    #39 0x0000f96f72b28f14 in lua_pcallk () from /usr/pkg/lib/liblua5.2.so.5
+    #40 0x000000020017b4c8 in mp_cpcall (func=0x20017abd0 <run_lua>, ud=0xf96f6e1010c0, L=0xf96f6e103400) at ../player/lua.c:99
+    #41 load_lua (client=<optimized out>, fname=0xf96f6f503420 "@stats.lua") at ../player/lua.c:387
+    #42 0x00000002001815c0 in script_thread (p=0xf96f6f5050c0) at ../player/scripting.c:95
+    #43 0x0000f96f743ec588 in pthread__create_tramp (cookie=0xf96f6f515000) at /usr/src/lib/libpthread/pthread.c:593
+    #44 0x0000f96f727385ec in _lwp_makecontext (u=0x0, start=0x0, arg=0x0, private=0xff00000014,
+        stack_base=0x1 <error: Cannot access memory at address 0x1>, stack_size=8589934592) at /usr/src/lib/libc/arch/aarch64/gen/_lwp.c:47
+    #45 0x0000f96f743df000 in ?? ()
+    #46 0x544a8f02d40034c1 in ?? ()
+    Backtrace stopped: previous frame identical to this frame (corrupt stack?)
 
 
 ## Python `import requests` SIGILLs
@@ -132,7 +227,7 @@
 
 The following patch workaround the issue:
 
-    $NetBSD: aarch64_problems.mdwn,v 1.8 2018/07/24 00:09:53 wiki Exp $
+    $NetBSD: aarch64_problems.mdwn,v 1.9 2018/07/28 19:14:29 leot Exp $
     
     Kludge for NetBSD/aarch64 SIGILL.
     

Add myself.
Index: wikisrc/summits/eurobsdcon_2018.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2018.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/summits/eurobsdcon_2018.mdwn	24 Jul 2018 11:18:38 -0000	1.9
+++ wikisrc/summits/eurobsdcon_2018.mdwn	27 Jul 2018 02:19:13 -0000	1.10
@@ -19,6 +19,7 @@
 Yang Zheng | `@` |
 Siddharth Muralee | `@` |
 Stephen Borrill | `sborrill@` |
+Maya Rashish | `maya@` |
  | |
 """]]
 

Remove references to non-PAE i386.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -r1.153 -r1.154
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 12:21:24 -0000	1.153
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 16:29:45 -0000	1.154
@@ -144,16 +144,14 @@
 the NetBSD default build.
 
 Because of the above, the standard approach is to use an amd64 Xen
-kernel and NetBSD/amd64 for the dom0.  For domUs, NetBSD/i386 (with
-the PAE kernel) and NetBSD/amd64 are in widespread use, and there is
+kernel and NetBSD/amd64 for the dom0.  For domUs, NetBSD/i386 (PAE) and
+NetBSD/amd64 are in widespread use, and there is
 little to no Xen-specific reason to prefer one over the other.
 
 Note that to use an i386 dom0 with Xen 4.5 or higher, one must build
 (or obtain from pre-built packages) an amd64 Xen kernel and install
-that on the system.  (One must also use a PAE i386 kernel, but this is
-also required with an i386 Xen kernel.).  Almost no one in the
-NetBSD/Xen community does this, and the standard, well-tested,
-approach is to use an amd64 dom0.
+that on the system.  Almost no one in the NetBSD/Xen community does
+this, and the standard, well-tested, approach is to use an amd64 dom0.
 
 A [posting on
 xen-devel](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html)
@@ -722,13 +720,9 @@
 The kernel must be specifically for Xen and for use as a domU.  The
 i386 and amd64 provide the following kernels:
 
-        i386 XEN3_DOMU
         i386 XEN3PAE_DOMU
         amd64 XEN3_DOMU
 
-Unless using Xen 3.1 (and you shouldn't) with i386-mode Xen, you must
-use the PAE version of the i386 kernel.
-
 This will boot NetBSD, but this is not that useful if the disk is
 empty.  One approach is to unpack sets onto the disk outside of xen
 (by mounting it, just as you would prepare a physical disk for a

less noise, more swag
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.152
retrieving revision 1.153
diff -u -r1.152 -r1.153
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 11:44:17 -0000	1.152
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 12:21:24 -0000	1.153
@@ -260,10 +260,8 @@
 useful with a serial console.  Then, place a NetBSD XEN3_DOM0 kernel
 in /, copied from releasedir/amd64/binary/kernel/netbsd-XEN3_DOM0.gz
 of a NetBSD build.  If using i386, use
-releasedir/i386/binary/kernel/netbsd-XEN3PAE_DOM0.gz.  (If using Xen
-3.1 and i386, you may use XEN3_DOM0 with the non-PAE Xen.  But you
-should not use Xen 3.1.)  Both xen and the NetBSD kernel may be (and
-typically are) left compressed.
+releasedir/i386/binary/kernel/netbsd-XEN3PAE_DOM0.gz.  Both xen and
+the NetBSD kernel may be (and typically are) left compressed.
 
 In a dom0, kernfs is mandatory for xend to communicate with the
 kernel, so ensure that /kern is in fstab.  (A standard NetBSD install
@@ -316,9 +314,6 @@
 of Xen and the dom0 kernel, but note that non-Xen NetBSD can be used
 to resolve Xen booting issues.
 
-Probably you want a default=N line to choose Xen in the absence of
-intervention.
-
 Now, reboot so that you are running a DOM0 kernel under Xen, rather
 than GENERIC without Xen.
 
@@ -339,8 +334,6 @@
 Configuring Xen
 ---------------
 
-Xen logs will be in /var/log/xen.
-
 Now, you have a system that will boot Xen and the dom0 kernel, but not
 do anything else special.  Make sure that you have rebooted into Xen.
 There will be no domUs, and none can be started because you still have
@@ -366,13 +359,17 @@
 order given) or rebooted, use xm or xl to inspect Xen's boot messages,
 available resources, and running domains.  An example with xl follows:
 
-        # xl dmesg
-	[xen's boot info]
-        # xl info
-	[available memory, etc.]
-        # xl list
-        Name              Id  Mem(MB)  CPU  State  Time(s)  Console
-        Domain-0           0       64    0  r----     58.1
+[[!template id=programlisting text="""
+# xl dmesg
+... xen's boot info ...
+# xl info
+... available memory, etc ...
+# xl list
+Name              Id  Mem(MB)  CPU  State  Time(s)  Console
+Domain-0           0       64    0  r----     58.1
+"""]]
+
+Xen logs will be in /var/log/xen.
 
 ### Issues with xencommons
 
@@ -391,7 +388,9 @@
 The installation of NetBSD should already have created devices for xen
 (xencons, xenevt, xsd_kva), but if they are not present, create them:
 
-        cd /dev && sh MAKEDEV xen
+[[!template id=programlisting text="""
+cd /dev && sh MAKEDEV xen
+"""]]
 
 anita (for testing NetBSD)
 --------------------------
@@ -400,7 +399,9 @@
 anita (see pkgsrc/misc/py-anita) to test NetBSD releases, by doing (as
 root, because anita must create a domU):
 
-        anita --vmm=xl test file:///usr/obj/i386/
+[[!template id=programlisting text="""
+anita --vmm=xl test file:///usr/obj/i386/
+"""]]
 
 Alternatively, one can use --vmm=xm to use xm-based domU creation
 instead (and must, on Xen <= 4.1).   TODO: confirm that anita xl really works.
@@ -489,46 +490,6 @@
 are specified with numbers as the second argument, as the examples
 above show, and not NetBSD device names.
 
-Hardware known to work
-----------------------
-
-Arguably, this section is misplaced, and there should be a page of
-hardware that runs NetBSD/amd64 well, with the mostly-well-founded
-assumption that NetBSD/xen runs fine on any modern hardware that
-NetBSD/amd64 runs well on.  Until then, we give motherboard/CPU (and
-sometimes RAM) pairs/triples to aid those choosing a motherboard.
-Note that Xen systems usually do not run X, so a listing here does not
-imply that X works at all.
-
-        Supermicro X9SRL-F, Xeon E5-1650 v2, 96 GiB ECC
-        Supermicro ??, Atom C2758 (8 core), 32 GiB ECC
-        ASUS M5A78L-M/USB3 AM3+ microATX, AMD Piledriver X8 4000MHz, 16 GiB ECC
-
-Older hardware:
-
-        Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2
-        INTEL DG33FB, "Intel(R) Core(TM)2 Duo CPU     E6850  @ 3.00GHz"
-        INTEL DG33FB, "Intel(R) Core(TM)2 Duo CPU     E8400  @ 3.00GHz"
-
-Running Xen under qemu
-----------------------
-
-The astute reader will note that this section is somewhat twisted.
-However, it can be useful to run Xen under qemu either because the
-version of NetBSD as a dom0 does not run on the hardware in use, or to
-generate automated test cases involving Xen.
-
-In 2015-01, the following combination was reported to mostly work:
-
-        host OS: NetBSD/amd64 6.1.4
-        qemu: 2.2.0 from pkgsrc
-        Xen kernel: xenkernel42-4.2.5nb1 from pkgsrc
-        dom0 kernel: NetBSD/amd64 6.1.5
-        Xen tools: xentools42-4.2.5 from pkgsrc
-
-See [PR 47720](https://gnats.netbsd.org/47720) for a problem with dom0
-shutdown.
-
 Unprivileged domains (domU)
 ===========================
 

More noise reduction, fix typo, and use the proper ikiwiki style.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.151
retrieving revision 1.152
diff -u -r1.151 -r1.152
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 11:16:22 -0000	1.151
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 11:44:17 -0000	1.152
@@ -253,11 +253,6 @@
 pkgsrc.  Ensure that your packages are recent; the HOWTO does not
 contemplate old builds.
 
-
-For Xen 3.1, support for HVM guests is in sysutils/xentool3-hvm.  More
-recent versions have HVM support integrated in the main xentools
-package.  It is entirely reasonable to run only PV guests.
-
 Next you need to install the selected Xen kernel itself, which is
 installed by pkgsrc as "/usr/pkg/xen*-kernel/xen.gz".  Copy it to /.
 For debugging, one may copy xen-debug.gz; this is conceptually similar
@@ -279,15 +274,19 @@
 beginning of your root file system, have /boot, and likely also
 /boot.cfg.  (If not, fix before continuing!)
 
-Add a line to to /boot.cfg to boot Xen.  See boot.cfg(5) for an
-example.  The basic line is
+Add a line to /boot.cfg to boot Xen.  See boot.cfg(5) for an
+example.  The basic line is:
 
-        menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=512M
+[[!template id=programlisting text="""
+menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=512M
+"""]]
 
 which specifies that the dom0 should have 512M, leaving the rest to be
 allocated for domUs.  To use a serial console, use
 
-        menu=Xen:load /netbsd-XEN3_DOM0.gz;multiboot /xen.gz dom0_mem=512M console=com1 com1=9600,8n1
+[[!template id=programlisting text="""
+menu=Xen:load /netbsd-XEN3_DOM0.gz;multiboot /xen.gz dom0_mem=512M console=com1 com1=9600,8n1
+"""]]
 
 which will use the first serial port for Xen (which counts starting
 from 1, unlike NetBSD which counts starting from 0), forcing
@@ -296,9 +295,11 @@
 which directs the console I/O through Xen to the same console device Xen
 itself uses (in this case, the serial port).
 
-In an attempt to add performance, one can also add
+In an attempt to add performance, one can also add:
 
-        dom0_max_vcpus=1 dom0_vcpus_pin
+[[!template id=programlisting text="""
+dom0_max_vcpus=1 dom0_vcpus_pin
+"""]]
 
 to force only one vcpu to be provided (since NetBSD dom0 can't use
 more) and to pin that vcpu to a physical CPU.  TODO: benchmark this.
@@ -346,22 +347,18 @@
 to configure the dom0 daemons.
 
 The daemons which should be run vary with Xen version and with whether
-one is using xm or xl.  The Xen 3.1, 3.3 and 4.1 packages use xm.  Xen
-4.2 and up packages use xl.  To use xm with 4.2, edit xendomains to
-use xm instead.
-
-For 3.1 and 3.3, you should enable xend and xenbackendd:
-
-        xend=YES
-        xenbackendd=YES
+one is using xm or xl. Xen 4.2 and up packages use xl. To use xm with 4.2,
+edit xendomains to use xm instead.
 
 For 4.1 and up, you should enable xencommons.  Not enabling xencommons
 will result in a hang; it is necessary to hit ^C on the console to let
 the machine finish booting.  If you are using xm (default in 4.1, or
 if you changed xendomains in 4.2), you should also enable xend:
 
-        xend=YES # only if using xm, and only installed <= 4.2
-        xencommons=YES
+[[!template id=programlisting text="""
+xend=YES # only if using xm, and only installed <= 4.2
+xencommons=YES
+"""]]
 
 TODO: Recommend for/against xen-watchdog.
 

Remove the noise surrounding PAE.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.150
retrieving revision 1.151
diff -u -r1.150 -r1.151
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 11:08:33 -0000	1.150
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 11:16:22 -0000	1.151
@@ -129,8 +129,8 @@
 ------------
 
 Xen itself can run on i386 (Xen < 4.2) or amd64 hardware (all Xen
-versions).  (Practically, almost any computer where one would want to
-run Xen today supports amd64.)
+versions).  Practically, almost any computer where one would want to
+run Xen today supports amd64.
 
 Xen, the dom0 system, and each domU system can be either i386 or
 amd64.  When building a xenkernel package, one obtains an i386 Xen
@@ -140,11 +140,8 @@
 work, and an i386 dom0 kernel should in theory work.  An amd64
 Xen/dom0 is known to support both i386 and amd64 domUs.
 
-i386 dom0 and domU kernels must be PAE (except for an i386 Xen 3.1
-kernel, where one can use non-PAE for dom0 and all domUs); PAE kernels
-are included in the NetBSD default build.  (Note that emacs (at least)
-fails if run on i386 with PAE when built without, and vice versa,
-presumably due to bugs in the undump code.)
+i386 dom0 and domU kernels must be PAE. PAE kernels are included in
+the NetBSD default build.
 
 Because of the above, the standard approach is to use an amd64 Xen
 kernel and NetBSD/amd64 for the dom0.  For domUs, NetBSD/i386 (with

Improve the table, remove more duplicated noise (eg "Recommendation",
already said in other sections).
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.149
retrieving revision 1.150
diff -u -r1.149 -r1.150
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 11:00:10 -0000	1.149
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 11:08:33 -0000	1.150
@@ -19,8 +19,8 @@
 
 [[!table data="""
 Style of guest	|Supported by NetBSD
-PV		|Yes
-HVM		|Yes
+PV		|Yes (dom0, domU)
+HVM		|Yes (domU)
 PVHVM		|No
 PVH		|No
 """]]
@@ -35,44 +35,19 @@
 AMD's AMD-Vi.  TODO: Explain whether Xen on NetBSD makes use of these
 features.  TODO: Review by someone who really understands this.
 
-Generally any machine that runs NetBSD/amd64 will work with Xen and PV
-guests.  In theory i386 computers (without x86_64/amd64 support) can
-be used for Xen <= 4.2, but we have no recent reports of this working
-(this is a hint).  For HVM guests, hardware support is needed, but it
-is common on recent machines.
-
 At boot, the dom0 kernel is loaded as a module with Xen as the kernel.
 The dom0 can start one or more domUs.  (Booting is explained in detail
 in the dom0 section.)
 
-NetBSD supports Xen in that it can serve as dom0, be used as a domU,
-and that Xen kernels and tools are available in pkgsrc.  This HOWTO
-attempts to address both the case of running a NetBSD dom0 on hardware
-and running domUs under it (NetBSD and other), and also running NetBSD
-as a domU in a VPS.
-
-Xen 3.1 in pkgsrc used to support "PCI passthrough", which means that
-specific PCI devices can be made available to a specific domU instead
-of the dom0.  This can be useful to let a domU run X11, or access some
-network interface or other peripheral.
-
-NetBSD 6 and earlier supported Xen 2; support was removed from NetBSD
-7.  Xen 2 has been removed from pkgsrc.
-
-Prerequisites
--------------
-
-Installing NetBSD/Xen is not extremely difficult, but it is more
-complex than a normal installation of NetBSD.
-In general, this HOWTO is occasionally overly restrictive about how
-things must be done, guiding the reader to stay on the established
-path when there are no known good reasons to stray.
-
 This HOWTO presumes a basic familiarity with the Xen system
 architecture, with installing NetBSD on i386/amd64 hardware, and with
 installing software from pkgsrc.  See also the [Xen
 website](http://www.xenproject.org/).
 
+This HOWTO attempts to address both the case of running a NetBSD dom0
+on hardware and running domUs under it (NetBSD and other), and also
+running NetBSD as a domU in a VPS.
+
 Versions of Xen and NetBSD
 ==========================
 
@@ -82,9 +57,8 @@
 versions of NetBSD are intentionally ignored.
 
 The term "amd64" is used to refer to both the NetBSD port and to the
-hardware architecture on which it runs.  (Such hardware is made by
-both Intel and AMD, and in 2016 a normal PC has this CPU
-architecture.)
+hardware architecture on which it runs.  Such hardware is generally
+made by both Intel and AMD, and common on PC computers.
 
 Xen versions
 ------------
@@ -192,24 +166,6 @@
 understood. On top of that caution, the post is about Linux, not
 NetBSD.  TODO: Include link to benchmarks, if someone posts them.
 
-Recommendation
---------------
-
-Therefore, this HOWTO recommends running xenkernel46, xl, the NetBSD 7
-stable branch, and therefore to use an amd64 kernel as the dom0.
-Either the i386PAE or amd64 version of NetBSD may be used as domUs.
-
-A tentative replacement recommendation is xenkernel48, xl, and NetBSD
-8.
-
-Because bugs are fixed quite often, and because of Xen security
-advisories, it is good to stay up to date with NetBSD (tracking a
-stable branch), with the Xen kernel (tracking a Xen version via
-pkgsrc), and with the Xen tools.  Specifically, NetBSD (-7 and
--current) got an important fix affecting dom0/domU timesharing in
-November, 2015, and xentools46 got a fix to enable Ubuntu guests to
-boot in December, 2016.
-
 NetBSD as a dom0
 ================
 

Reduce the noise in the introduction, use a table.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.148
retrieving revision 1.149
diff -u -r1.148 -r1.149
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 10:49:59 -0000	1.148
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 11:00:10 -0000	1.149
@@ -6,42 +6,40 @@
 [![[Xen
 screenshot]](https://www.netbsd.org/gallery/in-Action/hubertf-xens.png)](https://www.netbsd.org/gallery/in-Action/hubertf-xen.png)
 
-Xen is a hypervisor (or virtual machine monitor) for x86 hardware
-(i686-class or higher), which supports running multiple guest
+Xen is a hypervisor for x86 hardware, which supports running multiple guest
 operating systems on a single physical machine.  Xen is a Type 1 or
 bare-metal hypervisor; one uses the Xen kernel to control the CPU,
 memory and console, a dom0 operating system which mediates access to
 other hardware (e.g., disks, network, USB), and one or more domU
 operating systems which operate in an unprivileged virtualized
 environment.  IO requests from the domU systems are forwarded by the
-hypervisor (Xen) to the dom0 to be fulfilled.
+Xen hypervisor to the dom0 to be fulfilled.
 
-Xen supports two styles of guests.  The original is Para-Virtualized
-(PV) which means that the guest OS does not attempt to access hardware
-directly, but instead makes hypercalls to the hypervisor.  This is
-analogous to a user-space program making system calls.  (The dom0
-operating system uses PV calls for some functions, such as updating
-memory mapping page tables, but has direct hardware access for disk
-and network.)   PV guests must be specifically coded for Xen.
-
-The more recent style is HVM, which means that the guest does not have
-code for Xen and need not be aware that it is running under Xen.
-Attempts to access hardware registers are trapped and emulated.  This
-style is less efficient but can run unmodified guests.
+Xen supports different styles of guest:
+
+[[!table data="""
+Style of guest	|Supported by NetBSD
+PV		|Yes
+HVM		|Yes
+PVHVM		|No
+PVH		|No
+"""]]
+
+In Para-Virtualized (PV) mode, the guest OS does not attempt to access
+hardware directly, but instead makes hypercalls to the hypervisor; PV
+guests must be specifically coded for Xen. In HVM mode, no guest
+modification is required; however, hardware support is required, such
+as VT-x on Intel CPUs and SVM on AMD CPUs.
 
-Generally any machine that runs NetBSD/amd64 will work with Xen and PV
-guests.  In theory i386 computers (without x86_64/amd64 support) can
-be used for Xen <= 4.2, but we have no recent reports of this working
-(this is a hint).  For HVM guests, hardware support is needed, but it
-is common on recent machines.  For Intel CPUs, one needs the VT-x
-extension, shown in "cpuctl identify 0" as VMX.  For AMD CPUs, one
-needs the AMD-V extensions, shown in "cpuctl identify 0" as SVM.
 There are further features for IOMMU virtualization, Intel's VT-d and
 AMD's AMD-Vi.  TODO: Explain whether Xen on NetBSD makes use of these
 features.  TODO: Review by someone who really understands this.
 
-Note that a FreeBSD dom0 requires VT-x and VT-d (or equivalent); this
-is because the FreeBSD dom0 does not run in PV mode.
+Generally any machine that runs NetBSD/amd64 will work with Xen and PV
+guests.  In theory i386 computers (without x86_64/amd64 support) can
+be used for Xen <= 4.2, but we have no recent reports of this working
+(this is a hint).  For HVM guests, hardware support is needed, but it
+is common on recent machines.
 
 At boot, the dom0 kernel is loaded as a module with Xen as the kernel.
 The dom0 can start one or more domUs.  (Booting is explained in detail

Remove the "Stability" section, it is useless.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.147
retrieving revision 1.148
diff -u -r1.147 -r1.148
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 10:47:25 -0000	1.147
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 10:49:59 -0000	1.148
@@ -194,16 +194,6 @@
 understood. On top of that caution, the post is about Linux, not
 NetBSD.  TODO: Include link to benchmarks, if someone posts them.
 
-Stability
----------
-
-Mostly, NetBSD as a dom0 or domU is quite stable. However, just like every
-other architecture, there are some open PRs indicating problems.
-
-Note also that there are issues with sparse vnd(4) instances, but
-these are not about Xen -- they just are noticed with sparse vnd(4)
-instances in support of virtual disks in a dom0.
-
 Recommendation
 --------------
 

reorg a little
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.146
retrieving revision 1.147
diff -u -r1.146 -r1.147
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 10:42:35 -0000	1.146
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 10:47:25 -0000	1.147
@@ -111,9 +111,6 @@
 
 Note: Xen 4.2 was the last version to support 32bit CPUs.
 
-Note that NetBSD support is called XEN3.  It works with Xen 3 and Xen
-4 because the hypercall interface has been stable.
-
 Xen command program
 -------------------
 
@@ -138,13 +135,13 @@
 been adequately tested for a complex custom setup with a large number
 of interfaces.
 
-NetBSD
-------
+NetBSD versions
+---------------
 
 The netbsd-7, netbsd-8, and -current branches are all reasonable
 choices, with more or less the same considerations for non-Xen use.
-Therefore, netbsd-8 is recommended as the stable version of the most
-recent release for production use.
+NetBSD 8 is recommended as the stable version of the most recent
+release for production use.
 
 For developing Xen, netbsd-current may be appropriate.
 
@@ -153,6 +150,9 @@
 need SMP for dom0 functions; the lack of support is really a problem
 when using a dom0 as a normal computer.)
 
+Note: NetBSD support is called XEN3. However, it does support Xen 4,
+because the hypercall interface has remained identical.
+
 Architecture
 ------------
 

Some more noise reduction: rename one section, recommend NetBSD-8, remove
references to xen 3.x.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.145
retrieving revision 1.146
diff -u -r1.145 -r1.146
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 10:36:26 -0000	1.145
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 10:42:35 -0000	1.146
@@ -88,8 +88,8 @@
 both Intel and AMD, and in 2016 a normal PC has this CPU
 architecture.)
 
-Xen
----
+Xen versions
+------------
 
 In NetBSD, Xen is provided in pkgsrc, via matching pairs of packages
 xenkernel and xentools.  We will refer only to the kernel versions,
@@ -125,7 +125,7 @@
 You must make a global choice to use xm or xl, because it affects not
 only which command you use, but the command used by rc.d scripts
 (specifically xendomains) and which daemons should be run.  The
-xentools packages provide xm for 3.1, 3.3 and 4.1 and xl for 4.2 and up.
+xentools packages provide xl for 4.2 and up.
 
 In 4.2, you can choose to use xm by simply changing the ctl_command
 variable and setting xend=YES in rc.conf.
@@ -143,14 +143,10 @@
 
 The netbsd-7, netbsd-8, and -current branches are all reasonable
 choices, with more or less the same considerations for non-Xen use.
-Therefore, netbsd-7 is recommended as the stable version of the most
-recent release for production use.  (Note that netbsd-7 (and therefore
-8/current) have a important scheduler fix (in November of 2015)
-affecting contention between dom0 and domUs; see
-https://releng.netbsd.org/cgi-bin/req-7.cgi?show=1040 for a
-description.)  For production, netbsd-7 is appropriate.  For learning,
-netbsd-8 is appropriate.  For developing Xen, netbsd-current may be
-appropriate.
+Therefore, netbsd-8 is recommended as the stable version of the most
+recent release for production use.
+
+For developing Xen, netbsd-current may be appropriate.
 
 As of NetBSD 6, a NetBSD domU will support multiple vcpus.  There is
 no SMP support for NetBSD as dom0.  (The dom0 itself doesn't really

Reduce the noise:
- Sum up the "Xen" section in a single, readable table.
- Remove the "Status" section, it is pointless and probably
inaccurate.
- Remove the "Using npf" section. We do have support for kernel
modules now, and basically, that kind of stuff shouldn't be in
a Xen howto.
- Remove the "missing kernel modules support" from the TODO list,
we do have that now. By the way, we should probably remove this
TODO section. This page is supposed to be a HowTo, not a page
where we put some random things.
 - Remove the "Status" section, it is pointless and probably
   inaccurate.

 - Remove the "Using npf" section. We do have support for kernel
   modules now, and basically, that kind of stuff shouldn't be in
   a Xen howto.

 - Remove the "missing kernel modules support" from the TODO list,
   we do have that now. By the way, we should probably remove this
   TODO section. This page is supposed to be a HowTo, not a page
   where we put some random things.

Members: 
	ports/xen/howto.mdwn:1.144->1.145 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.144
retrieving revision 1.145
diff -u -r1.144 -r1.145
--- wikisrc/ports/xen/howto.mdwn	26 Jul 2018 07:46:08 -0000	1.144
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 10:36:26 -0000	1.145
@@ -96,56 +96,21 @@
 but note that both packages must be installed together and must have
 matching versions.
 
-xenkernel3 provides Xen 3.1.  It is no longer maintained by Xen, and
-the last applied security patch was in 2011. Thus, it should not be
-used.  It supports PCI passthrough, which is why people use it anyway.
-Xen 3.1 runs on i386 (both non-PAE and PAE) and amd64 hardware.
-
-xenkernel33 provides Xen 3.3.  It is no longer maintained by Xen, and
-the last applied security patch was in 2012.  Thus, it should not be
-used.  Xen 3.3 runs on i386 PAE and amd64 hardware.  There are no good
-reasons to run this version.
-
-xenkernel41 provides Xen 4.1.  It is no longer maintained by Xen, but
-as of 2016-12 received backported security patches.  Xen 4.1 runs on
-i386 PAE and amd64 hardware.  There are no good reasons to run this
-version.
-
-Note that 3.1, 3.3 and 4.1 have been removed from pkgsrc-current, but
-are in 2016Q4.  They will be removed from this HOWTO sometime after
-2017Q1.
-
-xenkernel42 provides Xen 4.2.  It is no longer maintained by Xen, but
-as of 2016-12 received backported security patches.  Xen 4.2 runs on
-i386 PAE and amd64 hardware.  The only reason to run this is if you
-need to use xm instead of xl, or if you need to run on hardware that
-supports i386 but not amd64.  (This might also be useful if you need
-an i386 dom0, if it turns out that an amd64 Xen kernel and an i386
-dom0 is problematic.)
-
-xenkernel45 provides Xen 4.5.  Security advisories released in 2018-05
-did not include support for 4.5.  Xen 4.5 and newer runs on amd64
-hardware only.  While slightly old, 4.5 has been tested and run by
-others, so it is a very conservative choice.
-
-xenkernel46 provides Xen 4.6, and was added to pkgsrc as of 2016-05.
-As of 2018-05, security patches were released by Xen and are expected
-to be applied to pkgsrc.  Xen 4.6 runs on amd64 hardware only.  (If
-using Ubuntu guests, be sure to have the xentools46 from December,
-2016).  4.6 is perhaps an old choice, or perhaps the standard
-approach.
-
-Xen 4.7 was released in 2016-06 and is not in pkgsrc.
-
-xenkernel48 provides Xen 4.8, and was added to pkgsrc in 2017-03.  As
-of 2018-05, security patches were released by Xen and are expected to
-be applied to pkgsrc.  4.8 is perhaps the standard choice, or perhaps
-slightly new.
+Versions available in pkgsrc:
 
-Xen 4.9 and 4.10 are not in pkgsrc.
+[[!table data="""
+Xen Version	|Package Name	|Xen CPU Support	|EOL'ed By Upstream
+4.2		|xenkernel42	|32bit, 64bit		|Yes
+4.5		|xenkernel45	|64bit			|Yes
+4.6		|xenkernel46	|64bit			|Partially
+4.8		|xenkernel48	|64bit			|No
+4.11		|xenkernel411	|64bit			|No
+"""]]
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 
+Note: Xen 4.2 was the last version to support 32bit CPUs.
+
 Note that NetBSD support is called XEN3.  It works with Xen 3 and Xen
 4 because the hypercall interface has been stable.
 
@@ -261,65 +226,6 @@
 November, 2015, and xentools46 got a fix to enable Ubuntu guests to
 boot in December, 2016.
 
-Status
-------
-
-Ideally, all versions of Xen in pkgsrc would build on all supported
-versions of NetBSD/amd64, to the point where this section would be
-silly.  However, that has not always been the case.  Besides aging
-code and aging compilers, qemu (included in xentools for HVM support)
-is difficult to build.  Note that there is intentionally no data for
-4.5+ up for i386, and often omits xentools info if the corresponding
-kernel fails.
-
-The following table gives status, with the date last checked
-(generally on the most recent quarterly branch).  The first code is
-"builds" if it builds ok, and "FAIL" for a failure to build.  The
-second code/date only appears for xenkernel* and is "works" if it runs
-ok as a dom0 and can support a domU, and "FAIL" if it won't boot or
-run a domU.
-
-	xenkernel3 netbsd-6 i386 FAIL 201612
-	xenkernel33 netbsd-6 i386 FAIL 201612
-	xenkernel41 netbsd-6 i386 builds 201612
-	xenkernel42 netbsd-6 i386 builds 201612
-	xentools3 netbsd-6 i386 FAIL 201612
-	xentools33 netbsd-6 i386 FAIL 201612
-	xentools41 netbsd-6 i386 builds 201612
-	xentools42 netbsd-6 i386 FAIL 201612
-
-	xenkernel3 netbsd-7 i386 FAIL 201412
-	xenkernel33 netbsd-7 i386 FAIL 201412
-	xenkernel41 netbsd-7 i386 builds 201412
-	xenkernel42 netbsd-7 i386 builds 201412
-	xentools41 netbsd-7 i386 builds 201412
-	xentools42 netbsd-7 i386 ??FAIL 201412
-
-	xenkernel3 netbsd-6 amd64 FAIL 201612
-	xenkernel33 netbsd-6 amd64 FAIL 201612
-	xenkernel41 netbsd-6 amd64 builds 201612 works 201612
-	xenkernel42 netbsd-6 amd64 builds 201612 works 201612
-	xenkernel45 netbsd-6 amd64 builds 201612
-	xenkernel46 netbsd-6 amd64 builds 201612
-	xentools41 netbsd-6 amd64 builds 201612
-	xentools42 netbsd-6 amd64 builds 201612
-	xentools45 netbsd-6 amd64 builds 201612
-	xentools46 netbsd-6 amd64 FAIL 201612
-
-	xenkernel3 netbsd-7 amd64 builds 201612
-	xenkernel33 netbsd-7 amd64 builds 201612
-	xenkernel41 netbsd-7 amd64 builds 201612
-	xenkernel42 netbsd-7 amd64 builds 201612
-	xenkernel45 netbsd-7 amd64 builds 201612
-	xenkernel46 netbsd-7 amd64 builds 201612
-	xentools3 netbsd-7 amd64 builds 201612
-	xentools3-hvm netbsd-7 amd64 builds 201612
-	xentools33 netbsd-7 amd64 FAIL 201612
-	xentools41 netbsd-7 amd64 builds 201612
-	xentools42 netbsd-7 amd64 builds 201612
-	xentools45 netbsd-7 amd64 builds 201612
-	xentools46 netbsd-7 amd64 builds 201612
-
 NetBSD as a dom0
 ================
 
@@ -1172,17 +1078,6 @@
 
 See the [Amazon EC2 page](/amazon_ec2/).
 
-Using npf
----------
-
-In standard kernels, npf is a module, and thus cannot be loaded in a
-DOMU kernel.
-
-TODO: Explain how to compile npf into a custom kernel, answering (but
-note that the problem was caused by not booting the right kernel)
-[this email to
-netbsd-users](https://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html).
-
 TODO items for improving NetBSD/xen
 ===================================
 
@@ -1201,8 +1096,6 @@
   * Get UFS2 patches into pvgrub.
 * Add support for PV ops to a version of /boot, and make it usable as
   a kernel in Xen, similar to pvgrub.
-* Solve somehow the issue with modules for GENERIC not being loadable
-  in a Xen dom0 or domU kernel.
 
 Random pointers
 ===============

Give a title to the page, and remove reference to a closed PR. Frankly,
this page is a huge TLDR, 90% of the content is either inaccurate or
useless.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.143
retrieving revision 1.144
diff -u -r1.143 -r1.144
--- wikisrc/ports/xen/howto.mdwn	17 Jun 2018 21:11:00 -0000	1.143
+++ wikisrc/ports/xen/howto.mdwn	26 Jul 2018 07:46:08 -0000	1.144
@@ -1,3 +1,5 @@
+[[!meta title="Xen HowTo"]]
+
 Introduction
 ============
 
@@ -234,10 +236,8 @@
 Stability
 ---------
 
-Mostly, NetBSD as a dom0 or domU is quite stable.
-However, there are some open PRs indicating problems.
-
- - [PR 48125](http://gnats.netbsd.org/48125)
+Mostly, NetBSD as a dom0 or domU is quite stable. However, just like every
+other architecture, there are some open PRs indicating problems.
 
 Note also that there are issues with sparse vnd(4) instances, but
 these are not about Xen -- they just are noticed with sparse vnd(4)

Add a comment