Recent changes to this wiki:

Instead of referring to FreeBSD and OpenBSD ports add a reference to
wip/chromium package and its TODO file.
Index: wikisrc/projects/project/pkgsrc-chromium.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc-chromium.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/pkgsrc-chromium.mdwn	15 Feb 2016 22:57:22 -0000	1.3
+++ wikisrc/projects/project/pkgsrc-chromium.mdwn	23 Feb 2017 15:31:02 -0000	1.4
@@ -16,9 +16,9 @@
 [Chromium web browser](http://www.chromium.org/Home) is open source
 edition of Google Chrome.
 
-A good starting point can be the www/chromium package available in
-[FreeBSD Ports](https://svnweb.freebsd.org/ports/head/www/chromium/)
-and
-[OpenBSD Ports](http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/www/chromium/).
+Currently Chromium is present in [pkgsrc-wip](https://www.pkgsrc.org/wip/) as
+[[!template id=pkg category="wip" name="chromium"]]. Please see
+[wip/chromium/TODO](https://wip.pkgsrc.org/cgi-bin/gitweb.cgi?p=pkgsrc-wip.git;a=blob_plain;f=chromium/TODO;hb=HEAD)
+for a TODO list about it.
 """
 ]]

Added a comment: NetBrowser
--- /dev/null	2017-02-23 05:10:01.000000000 +0000
+++ wikisrc/projects/project/pkgsrc-chromium/comment_1_934e3961b6ab5d13d8897ab49bdfbb38._comment	2017-02-23 05:11:28.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/GQ5YrGI3hZzMZ82jtEJdgIUwv3AqDstcTZQWjI0tt4DUcuMbpLZ49C7A7RrcesICn1WQf1g-#01938"
+ nickname="jaypatelani"
+ subject="NetBrowser"
+ date="2017-02-23T05:11:12Z"
+ content="""
+Community might take https://github.com/conformal/xombrero?files=1 and make NetBrowser.
+"""]]

Added a comment: Lumina DE
--- /dev/null	2017-02-23 05:00:36.000000000 +0000
+++ wikisrc/projects/project/desktop-infrastructure/comment_2_a3ac0c57d5235df43377e255b387b1f1._comment	2017-02-23 05:07:54.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/GQ5YrGI3hZzMZ82jtEJdgIUwv3AqDstcTZQWjI0tt4DUcuMbpLZ49C7A7RrcesICn1WQf1g-#01938"
+ nickname="jaypatelani"
+ subject="Lumina DE"
+ date="2017-02-23T05:07:39Z"
+ content="""
+Agreed. And Lumina doesn't rely on dbus.
+"""]]

Sort future events by ascending order similarly to htdocs/gallery/events.xml
(this will hopefully help in order to not miss any next NetBSD related events!)
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- wikisrc/events.mdwn	21 Feb 2017 08:57:52 -0000	1.42
+++ wikisrc/events.mdwn	21 Feb 2017 09:01:23 -0000	1.43
@@ -7,17 +7,18 @@
 
 Future Events
 -------------
-### `Sep 2017 - EuroBSDCon 2017 Paris, France` ###
+### `Mar 2017` - AsiaBSDCon 2017
 
-*September 21 - 24, 2017, Paris, France*
+*March 9 - 12, Tokyo University of Science, Tokyo, Japan*
 
-[EuroBSDCon](https://2017.eurobsdcon.org/) is the premier European
-conference on the open source BSD operating systems attracting
-about 250 highly skilled engineering professionals, software
-developers, computer science students and professors, and users
-from all over Europe and other parts of the world. The goal of
-EuroBSDcon is to exchange knowledge about the BSD operating systems,
-facilitate coordination and cooperation among users and developers.
+[AsiaBSDCon](https://2017.asiabsdcon.org/) is a
+conference for users and developers on BSD based systems.
+The conference is for anyone developing, deploying and using systems
+based on FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Darwin, and MacOS X.
+AsiaBSDCon is a technical conference and aims to collect the best
+technical papers and presentations available to ensure that the latest
+developments in our open source community are shared with the widest
+possible audience.
 
 ### `Jun 2017` - BSDCAN 2017, Ottawa, Canada
 
@@ -31,18 +32,17 @@
 [website](https://www.bsdcan.org/2017/)
 for details.
 
-### `Mar 2017` - AsiaBSDCon 2017
+### `Sep 2017 - EuroBSDCon 2017 Paris, France`
 
-*March 9 - 12, Tokyo University of Science, Tokyo, Japan*
+*September 21 - 24, 2017, Paris, France*
 
-[AsiaBSDCon](https://2017.asiabsdcon.org/) is a
-conference for users and developers on BSD based systems.
-The conference is for anyone developing, deploying and using systems
-based on FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Darwin, and MacOS X.
-AsiaBSDCon is a technical conference and aims to collect the best
-technical papers and presentations available to ensure that the latest
-developments in our open source community are shared with the widest
-possible audience.
+[EuroBSDCon](https://2017.eurobsdcon.org/) is the premier European
+conference on the open source BSD operating systems attracting
+about 250 highly skilled engineering professionals, software
+developers, computer science students and professors, and users
+from all over Europe and other parts of the world. The goal of
+EuroBSDcon is to exchange knowledge about the BSD operating systems,
+facilitate coordination and cooperation among users and developers.
 
 
 Past Events

Add EuroBSDCon 2017
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- wikisrc/events.mdwn	6 Feb 2017 09:40:08 -0000	1.41
+++ wikisrc/events.mdwn	21 Feb 2017 08:57:52 -0000	1.42
@@ -7,6 +7,18 @@
 
 Future Events
 -------------
+### `Sep 2017 - EuroBSDCon 2017 Paris, France` ###
+
+*September 21 - 24, 2017, Paris, France*
+
+[EuroBSDCon](https://2017.eurobsdcon.org/) is the premier European
+conference on the open source BSD operating systems attracting
+about 250 highly skilled engineering professionals, software
+developers, computer science students and professors, and users
+from all over Europe and other parts of the world. The goal of
+EuroBSDcon is to exchange knowledge about the BSD operating systems,
+facilitate coordination and cooperation among users and developers.
+
 ### `Jun 2017` - BSDCAN 2017, Ottawa, Canada
 
 *June 7 - 10, Ottawa, Canada*

Added a comment: /boot.cfg entry
--- /dev/null	2017-02-20 02:30:02.000000000 +0000
+++ wikisrc/tutorials/how_to_set_up_a_xen_dom0/comment_3_4869b54ac386c98c7ef8a6d3159d2315._comment	2017-02-20 02:31:10.000000000 +0000
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="schnoebe"
+ subject="/boot.cfg entry"
+ date="2017-02-20T02:30:54Z"
+ content="""
+I can't imagine the specified /boot.cfg entry, with a path going into /usr/pkg/... can really be found by boot.  All previous tutorials and how-to's specify copying .../xen*-kernel/xen.gz into the root directory.
+
+The number of users having problems following the advice on the boot.cfg entry suggests that /boot can't traverse the directory tree deep enough to find xen.gz, even assuming /usr/pkg is on the same filesystem as /.
+"""]]

Hopefully it's really fixed now...
Index: wikisrc/projects/project/valgrind.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/valgrind.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/project/valgrind.mdwn	19 Feb 2017 15:45:51 -0000	1.6
+++ wikisrc/projects/project/valgrind.mdwn	19 Feb 2017 15:47:17 -0000	1.7
@@ -14,7 +14,7 @@
 leakage.
 
 See also <http://valgrind.org> and
-[http://vg4nbsd.berlios.de](http://web.archive.org/web/20131216184750/http://vg4nbsd.berlios.de/]
+[http://vg4nbsd.berlios.de](http://web.archive.org/web/20131216184750/http://vg4nbsd.berlios.de/)
 for work in progress.
 """
 ]]

fix url archive link
Index: wikisrc/projects/project/valgrind.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/valgrind.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/valgrind.mdwn	15 Feb 2016 22:48:55 -0000	1.5
+++ wikisrc/projects/project/valgrind.mdwn	19 Feb 2017 15:45:51 -0000	1.6
@@ -14,7 +14,7 @@
 leakage.
 
 See also <http://valgrind.org> and
-[http://web.archive.org/web/20131216184750/http://vg4nbsd.berlios.de/](http://vg4nbsd.berlios.de)
+[http://vg4nbsd.berlios.de](http://web.archive.org/web/20131216184750/http://vg4nbsd.berlios.de/]
 for work in progress.
 """
 ]]

make the security warning bold
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:15:16 -0000	1.5
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:18:51 -0000	1.6
@@ -26,8 +26,7 @@
 
 5. ASan can be wrong about which function is faulting, if we're talking about functions internal to the library. Running it on a separate file or in GDB can be helpful. Worth trying if the failure doesn't make sense.
 
-Important note: ASan should not be run on production systems. [It can pose a
-security risk](http://www.openwall.com/lists/oss-security/2016/02/17/9).
+**Important note: ASan should not be run on production systems. [It can pose a security risk](http://www.openwall.com/lists/oss-security/2016/02/17/9).**
 
 ## Coverity ##
 

More markdown.
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:10:22 -0000	1.4
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:15:16 -0000	1.5
@@ -51,7 +51,7 @@
 - Library or other code you know well already
 - Drivers for hardware you actually own and can test
 
-Future ideas:
+## Future ideas: ##
 
 - GCC could be told to add ASan flags for all shared objects, making it easier to build world with those flags
 - We could run all of NetBSD with ASan for some real world tests.

oops, made the markdown worse.
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:08:58 -0000	1.3
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:10:22 -0000	1.4
@@ -44,6 +44,7 @@
 
 Some suggestions for things to focus on, as there are many defects
 reported:
+
 - Setuid programs
 - Anything kernel
 - Stuff that runs as root

More improve markdown. Mention that it can be wrong about the offending
function and that it's possible to run it in GDB.
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:06:15 -0000	1.2
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:08:58 -0000	1.3
@@ -2,31 +2,29 @@
 
 ## Address Sanitizer (+UBsan) (preliminary) ##
 
-ASan reports memory violations, and detects many off-by-ones. It seems
-to produce very high quality reports.
+ASan reports memory violations, and detects many off-by-ones. It seems to produce very high quality reports.
 
-It only needs to be compiled on the resulting binary[1]. It cannot compile
-static objects so requires some fiddling with makefiles to disable those.
+It only needs to be compiled on the resulting binary[1]. It cannot compile static objects so requires some fiddling with makefiles to disable those.
 
 I've been running it on netbsd tests in the following manner[2]:
 
     cd /usr/src/tests/lib/libc
     env USETOOLS=never MK_SSP=no HAVE_SSP=no CFLAGS="-fno-omit-frame-pointer -O0 -g -ggdb -U_FORTIFY_SOURCE -fsanitize=address -fsanitize=undefined" LDFLAGS="-lasan -lubsan" make -j20
 
-    env ASAN_OPTIONS=alloc_dealloc_mismatch=0 LD_PRELOAD="/usr/lib/libasan.so /usr/lib/libubsan.so" atf-run
+    env ASAN_OPTIONS=alloc_dealloc_mismatch=0 LD_PRELOAD="/usr/lib/libasan.so /usr/lib/libubsan.so" atf-run # [3]
 
-    sysctl -w security.pax.aslr.enabled=0 # [3]
+    sysctl -w security.pax.aslr.enabled=0 # [4]
 
 1. Seems like this is a cause of worse reports, as in-library functions
 are not intercepted.
 
 2. Not even close to canonical commands, should probably be improved.
 
-3. To workaround "Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly". An alternative is to LD_PRELOAD and LD_LIBRARY_PATH an entirely separate libc, ld.elf_so, etc.
+3. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself triggers a bug. Should have a look at it so this option doesn't need to be disabled.
 
-4. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself
-    triggers a bug. Should have a look at it so this option doesn't
-    need to be disabled.
+4. To workaround "Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly". An alternative is to LD_PRELOAD and LD_LIBRARY_PATH an entirely separate libc, ld.elf_so, etc.
+
+5. ASan can be wrong about which function is faulting, if we're talking about functions internal to the library. Running it on a separate file or in GDB can be helpful. Worth trying if the failure doesn't make sense.
 
 Important note: ASan should not be run on production systems. [It can pose a
 security risk](http://www.openwall.com/lists/oss-security/2016/02/17/9).

Improve markdown, mention conflict with ASLR.
Index: wikisrc/users/maya.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/maya.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/maya.mdwn	16 Feb 2017 00:01:14 -0000	1.1
+++ wikisrc/users/maya.mdwn	16 Feb 2017 00:06:15 -0000	1.2
@@ -15,12 +15,16 @@
 
     env ASAN_OPTIONS=alloc_dealloc_mismatch=0 LD_PRELOAD="/usr/lib/libasan.so /usr/lib/libubsan.so" atf-run
 
+    sysctl -w security.pax.aslr.enabled=0 # [3]
+
 1. Seems like this is a cause of worse reports, as in-library functions
 are not intercepted.
 
 2. Not even close to canonical commands, should probably be improved.
 
-3. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself
+3. To workaround "Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly". An alternative is to LD_PRELOAD and LD_LIBRARY_PATH an entirely separate libc, ld.elf_so, etc.
+
+4. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself
     triggers a bug. Should have a look at it so this option doesn't
     need to be disabled.
 
@@ -42,19 +46,15 @@
 
 Some suggestions for things to focus on, as there are many defects
 reported:
-
 - Setuid programs
 - Anything kernel
 - Stuff that runs as root
-
 - Library or other code you know well already
 - Drivers for hardware you actually own and can test
 
 Future ideas:
 
-- GCC could be told to add ASan flags for all shared objects, making
-  it easier to build world with those flags
+- GCC could be told to add ASan flags for all shared objects, making it easier to build world with those flags
 - We could run all of NetBSD with ASan for some real world tests.
-- ASan for kernel? (subr_kmem.c has some flags which do some of the
-  work, could it do more?)
+- ASan for kernel? (subr_kmem.c has some flags which do some of the work, could it do more?)
 - Fuzzers are cool.

Some info on how I've been using asan and coverity
(Not sure if this is sane markdown)
--- /dev/null	2017-02-16 00:00:33.000000000 +0000
+++ wikisrc/users/maya.mdwn	2017-02-16 00:01:28.000000000 +0000
@@ -0,0 +1,60 @@
+# Tips for using analyzers on NetBSD #
+
+## Address Sanitizer (+UBsan) (preliminary) ##
+
+ASan reports memory violations, and detects many off-by-ones. It seems
+to produce very high quality reports.
+
+It only needs to be compiled on the resulting binary[1]. It cannot compile
+static objects so requires some fiddling with makefiles to disable those.
+
+I've been running it on netbsd tests in the following manner[2]:
+
+    cd /usr/src/tests/lib/libc
+    env USETOOLS=never MK_SSP=no HAVE_SSP=no CFLAGS="-fno-omit-frame-pointer -O0 -g -ggdb -U_FORTIFY_SOURCE -fsanitize=address -fsanitize=undefined" LDFLAGS="-lasan -lubsan" make -j20
+
+    env ASAN_OPTIONS=alloc_dealloc_mismatch=0 LD_PRELOAD="/usr/lib/libasan.so /usr/lib/libubsan.so" atf-run
+
+1. Seems like this is a cause of worse reports, as in-library functions
+are not intercepted.
+
+2. Not even close to canonical commands, should probably be improved.
+
+3. ASAN_OPTIONS=alloc_dealloc_mismatch=0 is because atf-run itself
+    triggers a bug. Should have a look at it so this option doesn't
+    need to be disabled.
+
+Important note: ASan should not be run on production systems. [It can pose a
+security risk](http://www.openwall.com/lists/oss-security/2016/02/17/9).
+
+## Coverity ##
+
+Coverity is a static analyzer.
+
+You can see a part of its output in coverity-updates@, and a lot more
+if you go to the website (sign up with your netbsd email or poke someone
+for access).
+
+A lot of the reports are about strncpy/strcpy or in code that belongs
+to GCC (in the case of userland), you can tackle this by limiting
+results to a particular directory (click the folder icon). You can
+also sort by issue.
+
+Some suggestions for things to focus on, as there are many defects
+reported:
+
+- Setuid programs
+- Anything kernel
+- Stuff that runs as root
+
+- Library or other code you know well already
+- Drivers for hardware you actually own and can test
+
+Future ideas:
+
+- GCC could be told to add ASan flags for all shared objects, making
+  it easier to build world with those flags
+- We could run all of NetBSD with ASan for some real world tests.
+- ASan for kernel? (subr_kmem.c has some flags which do some of the
+  work, could it do more?)
+- Fuzzers are cool.

AsiaBSDCon 2017 NetBSD develoer summit and BoF.
--- /dev/null	2017-02-13 06:30:02.000000000 +0000
+++ wikisrc/summits/AsiaBSDCon_2017_NetBSD_BoF.mdwn	2017-02-13 06:30:10.000000000 +0000
@@ -0,0 +1,22 @@
+<!-- we are supposed to use all lowercase letters in the link, so set a proper title for the page: -->
+[[!meta title="AsiaBSDCon 2017 NetBSD BoF"]]
+
+
+# ~~Net~~BSD BoF 2017
+------------------------------------------------------
+* Let's run a ~~Net~~BSD BoF on AsiaBSDCon2017.
+* All BSD speakers are welcome. Please contact to jun@ or msaitoh@ if you'd like to give a talk.
+* Day 2: IIJ 2017/3/10(Friday)
+  * 19:00-21:30(JST)
+  * 10:00-12:30(UTC)
+  * 05:00-07:30(EST)
+  * 02:00-04:30(PST)
+* Live streaming URL: TBD
+
+[[!table data="""
+Name						|Title								|Time		|Notes
+XXX                                             |YYY                                                            | ZZ minutes    |
+"""]]
+
+# Dinner
+* After the BoF, we usually go to a bar or a restaurant near the venue.
--- /dev/null	2017-02-13 06:30:02.000000000 +0000
+++ wikisrc/summits/asiabsdcon_2017_netbsd_summit.mdwn	2017-02-13 06:30:10.000000000 +0000
@@ -0,0 +1,30 @@
+<!-- we are supposed to use all lowercase letters in the link, so set a proper title for the page: -->
+[[!meta title="AsiaBSDCon 2017 NetBSD Summit"]]
+
+## Details
+
+* The NetBSD developer summit at AsiaBSDCon 2017 will be held on Friday,
+10:00-16:30(JST) 01:00-07:30(UTC). (TBD)
+* ROOM XXX
+
+## Planning to attend?
+
+[[!table data="""
+First Last | `login@` | comment(s)
+Masanobu SAITOH | `msaitoh` |
+"""]]
+
+
+## Planning to present something?
+
+[[!table data="""
+Speaker  |Title
+`all` | Self introduction (5minutes in each person)
+`msaitoh@` | Annual summary of IIJ's work.
+`login@` |_Very Interesting Thing_
+"""]]
+
+## Discussions
+* about WIP session's presentation.
+
+## Varia

This tutorial is for pkg_comp 1.x, so refert to pkgtools/pkg_comp1.
Index: wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn	19 Jul 2014 04:03:21 -0000	1.5
+++ wikisrc/tutorials/pkgsrc/pkg_comp_pkg_chk.mdwn	12 Feb 2017 10:51:54 -0000	1.6
@@ -8,7 +8,7 @@
 
 Let's install *pkg_comp*
 
-	# cd /usr/pkgsrc/pkgtools/pkg_comp
+	# cd /usr/pkgsrc/pkgtools/pkg_comp1
 	# make install clean
 
 Once done, we will create the *chroot*ed environment:

Mention future work in sysinst(8)
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:08:32 -0000	1.13
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:10:53 -0000	1.14
@@ -76,6 +76,8 @@
 
 It is also possible to boot a Xen DOM0 system with root filesystem encryption. However, Xen-enabled NetBSD kernels currently do not support loading modules at boot-time. The memory disk has to be placed directly inside the kernel instead (with [[!template id=man name="mdconfig" section="8"]] or a new kernel configuration).
 
+It should really be possible to install NetBSD this way with [[!template id=man name="sysinst" section="8"]]. Unfortunately this is not supported yet.
+
 References
 ----------
 

Clarify where cgdroot.kmod gets built
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:02:28 -0000	1.12
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:08:32 -0000	1.13
@@ -65,6 +65,8 @@
 src/distrib/amd64/kmod-cgdroot$ /path/to/tooldir/bin/nbmake-amd64
 """]]
 
+It will be found in `/path/to/objdir/distrib/amd64/kmod-cgdroot/cgdroot.kmod`.
+
 Caveats
 -------
 

s/eg/e.g./
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:00:40 -0000	1.11
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:02:28 -0000	1.12
@@ -70,7 +70,7 @@
 
 The biggest (known) issue with this setup occurs when firmware needs to be loaded early in the boot process (such as graphics drivers for the console). At the moment they need to be provided as part of the memory disk. Some network interfaces, of which some wireless devices in particular, also require loading firmware to work properly.
 
-This setup is not entirely safe against physical attacks. An attacker can modify the boot process to store the passphrase for later retrieval, or insert a backdoor while booting. To defend against such attacks, the bootloader, kernel and ramdisk all need to be signed and their integrity checked before booting (eg with [[!template id=man name="tpm" section="4"]]). Alternatively, it is possible to boot from a removable medium (eg USB stick), which can be protected against tampering attacks (eg secure storage, read-only volume...).
+This setup is not entirely safe against physical attacks. An attacker can modify the boot process to store the passphrase for later retrieval, or insert a backdoor while booting. To defend against such attacks, the bootloader, kernel and ramdisk all need to be signed and their integrity checked before booting (e.g. with [[!template id=man name="tpm" section="4"]]). Alternatively, it is possible to boot from a removable medium (e.g. USB stick), which can be protected against tampering attacks (e.g. secure storage, read-only volume...).
 
 It is also possible to boot a Xen DOM0 system with root filesystem encryption. However, Xen-enabled NetBSD kernels currently do not support loading modules at boot-time. The memory disk has to be placed directly inside the kernel instead (with [[!template id=man name="mdconfig" section="8"]] or a new kernel configuration).
 

Fix a link
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:55:36 -0000	1.10
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:00:40 -0000	1.11
@@ -29,7 +29,7 @@
 Obtaining the kernel module
 ---------------------------
 
-The `cgdroot.kmod` kernel module is part of the regular NetBSD releases since NetBSD 7.0. It can be found in the `<arch>/installation/miniroot` folder from the release. For instance, for the amd64 architecture on the German mirror for the 7.0.1 release, download it at (ftp://ftp.de.netbsd.org/pub/NetBSD/NetBSD-7.0.1/amd64/installation/miniroot/cgdroot.kmod).
+The `cgdroot.kmod` kernel module is part of the regular NetBSD releases since NetBSD 7.0. It can be found in the `<arch>/installation/miniroot` folder from the release. For instance, for the amd64 architecture on the German mirror for the 7.0.1 release, download it at [ftp.de.netbsd.org/pub/NetBSD/NetBSD-7.0.1/amd64/installation/miniroot/cgdroot.kmod](ftp://ftp.de.netbsd.org/pub/NetBSD/NetBSD-7.0.1/amd64/installation/miniroot/cgdroot.kmod).
 
 Configuring the kernel module
 -----------------------------

Link to the NetBSD Guide
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:54:56 -0000	1.9
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:55:36 -0000	1.10
@@ -5,6 +5,8 @@
 
 The mechanism described here still requires one unencrypted partition to boot from (typically `wd0a`). Full disk encryption would make it more difficult for an attacker to modify the unencrypted part of the disk to plant a backdoor. With only partial encryption, the original [[!template id=man name="cgdconfig" section="8"]] binary may be modified to send the passphrase away, allowing an attacker with a disk dump to recover the data.
 
+The NetBSD Guide contains [an entire section about CGD][2].
+
 The boot process
 ----------------
 
@@ -76,5 +78,7 @@
 ----------
 
 * [Full Disk Encryption with cgd (well, almost)][1]
+* [The cryptographic device driver (CGD)][2]
 
 [1]: https://mail-index.netbsd.org/current-users/2013/03/21/msg022311.html "Full Disk Encryption with cgd (well, almost)"
+[2]: http://www.netbsd.org/docs/guide/en/chap-cgd.html "The cryptographic device driver (CGD)"

Wording
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:42:44 -0000	1.8
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:54:56 -0000	1.9
@@ -3,16 +3,14 @@
 
 It is possible to run NetBSD with [complete root filesystem encryption][1], thanks to the `cgdroot.kmod` kernel module. It really is a memory disk (also knows as RAM disk) that is expected to be loaded in the kernel while booting. It is named after CGD, the "cryptographic device driver", which implements encryption for storage in the NetBSD kernel.
 
-Full disk encryption makes it more difficult for an attacker to modify the unencrypted part of the disk to plant a backdoor. With only partial encryption, the original [[!template id=man name="cgdconfig" section="8"]] binary may be modified to send the passphrase away, allowing an attacker with a disk dump to recover the data.
-
-The mechanism described here still requires one unencrypted partition to boot from (typically `wd0a`).
+The mechanism described here still requires one unencrypted partition to boot from (typically `wd0a`). Full disk encryption would make it more difficult for an attacker to modify the unencrypted part of the disk to plant a backdoor. With only partial encryption, the original [[!template id=man name="cgdconfig" section="8"]] binary may be modified to send the passphrase away, allowing an attacker with a disk dump to recover the data.
 
 The boot process
 ----------------
 
-Instead of booting normally the GENERIC kernel and using the root filesystem, a kernel module is loaded at boot-time containing a memory disk. This minimal filesystem image is then considered the actual root filesystem.
+Instead of booting the GENERIC kernel normally and using the root filesystem directly as usual, a special kernel module containing a memory disk is loaded at boot-time. This minimal filesystem image will then be the actual root filesystem, where the decryption process takes place.
 
-The boot partition on disk only needs to contain:
+The boot partition on disk needs to contain:
 
 * [[!template id=man name="boot" section="8"]], the second-stage bootloader
 * [[!template id=man name="boot.cfg" section="5"]], the configuration file for the bootloader (optional)

Try to clarify a bit more
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/security/cgdroot.mdwn	22 Jun 2016 09:08:50 -0000	1.7
+++ wikisrc/security/cgdroot.mdwn	10 Feb 2017 10:42:44 -0000	1.8
@@ -1,7 +1,7 @@
 Root filesystem encryption
 ==========================
 
-It is possible to run NetBSD with [complete root filesystem encryption][1], thanks to the `cgdroot.kmod` kernel module. It really is a memory disk (also knows as RAM disk) that is expected to be loaded in the kernel while booting.
+It is possible to run NetBSD with [complete root filesystem encryption][1], thanks to the `cgdroot.kmod` kernel module. It really is a memory disk (also knows as RAM disk) that is expected to be loaded in the kernel while booting. It is named after CGD, the "cryptographic device driver", which implements encryption for storage in the NetBSD kernel.
 
 Full disk encryption makes it more difficult for an attacker to modify the unencrypted part of the disk to plant a backdoor. With only partial encryption, the original [[!template id=man name="cgdconfig" section="8"]] binary may be modified to send the passphrase away, allowing an attacker with a disk dump to recover the data.
 
@@ -18,7 +18,8 @@
 * [[!template id=man name="boot.cfg" section="5"]], the configuration file for the bootloader (optional)
 * a GENERIC kernel
 * the `cgdroot.kmod` kernel module
-* configuration and encryption key for the encrypted volume to start from (`cgd.conf`)
+* the configuration file for CGD, `cgd.conf`
+* the encryption key for the volume to start from, named after its partition (like `wd0f`)
 
 Once loaded the memory disk mounts the `wd0a` partition onto `/etc/cgd`, and asks for the encryption passphrase as usual (with [[!template id=man name="cgdconfig" section="8"]]). If successful, the `cgd0a` volume configured is mounted on `/altroot`, and [[!template id=man name="init" section="8"]] is told via [[!template id=man name="sysctl" section="7"]] to chroot into this volume before actually booting. The system then starts normally.
 

This was basically done for GSoC last year.
Index: wikisrc/projects/project/u-boot-pkgsrc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/u-boot-pkgsrc.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/u-boot-pkgsrc.mdwn	20 Feb 2015 16:38:57 -0000	1.2
+++ wikisrc/projects/project/u-boot-pkgsrc.mdwn	9 Feb 2017 15:43:39 -0000	1.3
@@ -13,6 +13,7 @@
 category="userland"
 difficulty="medium"
 duration="3 months"
+done_by="Joe Davis"
 
 description="""
 The U-Boot bootloader is being used by an increasing number of devices, including lots which run NetBSD.

Remove pkg_comp rewrite project proposal.
I have finally done this myself and should publish the new tool within the
next few weeks, so I don't want to waste potential GSoC students reading
this proposal.
Members: 
	projects/project/rewrite-pkg_comp.mdwn:1.3->1.4(DEAD) 

--- wikisrc/projects/project/rewrite-pkg_comp.mdwn	2017-02-09 15:19:44.000000000 +0000
+++ /dev/null	2017-02-09 15:16:00.000000000 +0000
@@ -1,37 +0,0 @@
-[[!template id=project
-
-title="Rewrite pkg_comp with portability as a major goal"
-
-contact="""
-[tech-pkg](mailto:tech-pkg@NetBSD.org)
-"""
-
-mentors="""
-[Julio Merino](mailto:jmmv@NetBSD.org), [Aleksej Saushev](mailto:asau@NetBSD.org)
-"""
-
-category="pkgsrc"
-difficulty="medium"
-duration="3 months"
-
-description="""
-pkg_comp is a shell script that allows building packages inside a sandbox in an automated manner. The goal is to allow the user to build packages in a controller manner and to provide a simple mechanism to build packages for a host running a specific NetBSD release (e.g building packages for NetBSD 5.x while running NetBSD-current).
-
-The [current version](http://www.netbsd.org/contrib/soc-projects.html) of pkg_comp is written as a pretty big shell script that has grown out of control. It is hard to maintain and hard to extend. And, more importantly, it is not portable at all.
-
-The goal of this project is to rewrite pkg_comp from scratch with portability being the main goal: it has to be possible to use the script in different Unix variants (including Mac OS X).
-
-The language of choice for the reimplementation will be Python. The code will be hosted outside of pkgsrc to be able to distribute it as a standalone tool.
-
-The following milestones should be accomplished:
-
-* Implement a "sandbox" library with an interface to programmatically create and manage a sandboxed file system. The structure of the sandbox has to be configurable through a template, and templates have to be provided for a few systems. The sandbox itself will be constructed either by unpacking tarballs with the system contents (such as the NetBSD distfiles), by null-mounting directories of the host file system, or both.
-* Implement a command-line frontend utility for the "sandbox" library. This tool is completely unaware of pkgsrc but will be really nice to have (and trivial to write, as all the juicy bits are in the library). Will be useful as part of server administration, as it will allow isolating services in a fairly easy manner.
-* Implement the "pkg_comp" application, building it on top of the "sandbox" module. It has to provide most of the current functionality, if not all. More specifically, these are a must: unattended builds of a predefined set of packages and use of libkver to override the system version.
-* Implement detailed unit tests for the modules and integration tests for the front-end tools. At this point, the former will most likely be implemented using JUnit and the latter will be implemented using ATF.
-
-As part of this project, the student will get familiar with pkgsrc, construction of sandboxes for different operating systems, unit testing, ATF and Python.
-"""
-]]
-
-[[!tag gsoc]]

Move FOSDEM 2017 to Past Events
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- wikisrc/events.mdwn	26 Dec 2016 16:24:57 -0000	1.40
+++ wikisrc/events.mdwn	6 Feb 2017 09:40:08 -0000	1.41
@@ -32,17 +32,21 @@
 developments in our open source community are shared with the widest
 possible audience.
 
+
+Past Events
+-----------
+
 ### `Feb 2017` - FOSDEM 2017 Brussels, Belgium
 
 *February 4 - 5, Brussels, Belgium*
 
-[FOSDEM](https://fosdem.org/2017/) is a
+[FOSDEM](https://fosdem.org/2017/) was a
 free event for software developers to meet, share ideas
 and collaborate. Every year, thousands of developers of
 free and open source software from all over the world gather
 at the event in Brussels.
 
-There is a special developer's room reserved for BSD licensed
+There was a special developer's room reserved for BSD licensed
 operating systems and their talks.
 
 Please see
@@ -50,9 +54,6 @@
 for details.
 
 
-Past Events
------------
-
 ### `Sep 2016` - EuroBSDCon 2016 Belgrade, Serbia
 
 *September 22 - 25, 2016, Belgrade Serbia*

Added a comment: Lots of useful info regarding NetBSD on RPI collected by Jun Ebihara
--- /dev/null	2017-02-04 20:33:38.000000000 +0000
+++ wikisrc/ports/evbarm/raspberry_pi/comment_19_82864947fcb8737650f36e90ed1ed9b8._comment	2017-02-04 20:35:44.000000000 +0000
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UM0fy451yPQ9iZSVKjtjNcPifA--#1f032"
+ nickname="Fredrik Pettai"
+ subject="Lots of useful info regarding NetBSD on RPI collected by Jun Ebihara"
+ date="2017-02-04T20:35:28Z"
+ content="""
+See Jun Ebihara's GitHub page where lots of stuff regarding NetBSD on RPI is collected:
+<https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README>
+"""]]

Fix broken links
Index: wikisrc/ports/sh3.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sh3.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/ports/sh3.mdwn	22 May 2015 02:41:35 -0000	1.4
+++ wikisrc/ports/sh3.mdwn	28 Jan 2017 05:06:59 -0000	1.5
@@ -17,9 +17,9 @@
     -   [7709A evaluation
         board](http://www.computex.co.jp/products/board/board.htm#7709a)
         ([Computex](http://www.computex.co.jp/))
-    -   [T-SH7706LAN](http://web.kyoto-inet.or.jp/people/takagaki/T-SH7706/T-SH7706.htm)
+    -   [T-SH7706LAN](http://www.itrinity.jp/products/tac_board/sh7706lan/sh7706_spec.html)
         ([TAC Inc.](http://www.tacinc.jp/))
-    -   [T-SH7706LSR](http://www.tacinc.jp/T-SH7706/T-SH7706LSR.htm)
+    -   [T-SH7706LSR](http://tacinc.jp/products/sh3-linux/t-7706lsr)
         ([TAC Inc.](http://www.tacinc.jp/))
 
 -   [NetBSD/evbsh3](../evbsh3/): SH4 chip evaluation boards

Make command invocation as block
Index: wikisrc/users/ryoon/how_to_update_www_firefox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/ryoon/how_to_update_www_firefox.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/users/ryoon/how_to_update_www_firefox.mdwn	22 Jan 2017 13:00:58 -0000	1.10
+++ wikisrc/users/ryoon/how_to_update_www_firefox.mdwn	22 Jan 2017 13:02:09 -0000	1.11
@@ -12,6 +12,7 @@
 
 You should follow "Working with the Unified Repo" section.
 In short, run:
+
 	$ hg clone https://hg.mozilla.org/mozilla-unified
 
 # Update trees to latest

Explain pkgsrc/www/firefox update instruction with recent example
Index: wikisrc/users/ryoon/how_to_update_www_firefox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/ryoon/how_to_update_www_firefox.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/users/ryoon/how_to_update_www_firefox.mdwn	19 Jun 2016 09:21:40 -0000	1.9
+++ wikisrc/users/ryoon/how_to_update_www_firefox.mdwn	22 Jan 2017 13:00:58 -0000	1.10
@@ -1,24 +1,21 @@
 [[!meta title="How to update pkgsrc/www/firefox"]]
 
-This article shows how to update pkgsrc/www/firefox package to latest release.
+This article shows you how to update pkgsrc/www/firefox package to latest
+release.
 You can use Mozilla's Mercurial (hg) repositories to track upstream changes.
 
-You should have pkgsrc/meta-pkgs/pkg_developer package.
+You should have pkgsrc/meta-pkgs/pkg_developer package
+and pkgsrc/devel/py-mercurial package.
 
 # Clone hg tree
-See <https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Source_Code/Mercurial>.
-
-You should follow "Using Bookmarks to Manage Multiple Repositories from a Single Clone" section.
+See <http://mozilla-version-control-tools.readthedocs.io/en/latest/hgmozilla/unifiedrepo.html>
 
+You should follow "Working with the Unified Repo" section.
+In short, run:
+	$ hg clone https://hg.mozilla.org/mozilla-unified
 
 # Update trees to latest
 
-	$ hg pull central
-	$ hg pull inbound
-	$ hg pull aurora
-	$ hg pull beta
-	$ hg pull release
-
 	$ hg update
 
 
@@ -26,19 +23,19 @@
 
 Find latest release.
 
-	$ hg tags|grep 46_
+	$ hg tags|grep 50_
 	(snip)
-	FIREFOX_46_0_1_RELEASE		341775:0b8492c110be
+	FIREFOX_50_1_0_RELEASE         359965:8612c3320053
 	(snip)
 
 Checkout the branch.
 
-	$ hg checkout FIREFOX_46_0_1_RELEASE
+	$ hg checkout FIREFOX_50_1_0_RELEASE
 
 Create named branch for applying pkgsrc patches
 
-	$ hg branch pkgsrc_firefox-46.0.1
-	$ hg commit -m "Create pkgsrc_firefox-46.0.1 branch for applying pkgsrc patches"
+	$ hg branch pkgsrc_firefox-50.1.0
+	$ hg commit -m "Create pkgsrc_firefox-50.1.0 branch for applying pkgsrc patches"
 
 Add .*\.orig$ to .hgignore, and commit this change
 
@@ -52,26 +49,26 @@
 	$ popd
 	$ cat /usr/pkgsrc/www/firefox/patches/patch-*|patch -p0
 	$ hg add ...(necessary files)
-	$ hg commit -m "Apply pkgsrc patches for firefox-46.0.1nb1"
+	$ hg commit -m "Apply pkgsrc patches for firefox-50.1.0nb3"
 
 
 # Checkout latest beta source, and create your branch
 
 Find latest branch.
 
-	$ hg tags | grep 47_
+	$ hg tags | grep 51_
 	(snip)
-	FIREFOX_47_0b9_RELEASE		341367:2ee4473c729a
+	FIREFOX_51_0b14_RELEASE        364880:09142d07fd73
 	(snip)
 
 Checkout the branch.
 
-	$ hg checkout FIREFOX_47_0b9_RELEASE
+	$ hg checkout FIREFOX_51_0b14_RELEASE
 
 Create named branch for working.
 
-	$ hg branch ryoon_firefox-47.0b9
-	$ hg commit -m "Create ryoon_firefox-47.0 branch for merging pkgsrc patches"
+	$ hg branch ryoon_firefox-51.0
+	$ hg commit -m "Create ryoon_firefox-51.0 branch for merging pkgsrc patches"
 
 Add .*\.orig$ to .hgignore, and commit this change
 
@@ -79,19 +76,19 @@
 
 # Merge your patches
 
-	$ hg merge pkgsrc_firefox-46.0.1
+	$ hg merge pkgsrc_firefox-50.1.0
 	$ hg resolve -l
 	$ vi file/marked/as/U
 	$ hg resolve --mark file/marked/as/U
 	(loop)
-	$ hg commit -m "Merge pkgsrc_firefox-46.0.1 branch to 47.0"
+	$ hg commit -m "Merge pkgsrc_firefox-50.1.0 branch to 51.0"
 
 
 # Create patch file for patch -p0
 
-	$ hg diff -r (revision of first commit in ryoon_firefox-47.0b9) | \
-	sed -e 's!^--- a/!--- !' -e 's!^+++ b/!+++ !' > ~/firefox-47.0.diff
-	$ vi ~/firefox-47.0.diff
+	$ hg diff -r (revision of first commit in ryoon_firefox-51.0) | \
+	sed -e 's!^--- a/!--- !' -e 's!^+++ b/!+++ !' > ~/firefox-51.0.diff
+	$ vi ~/firefox-51.0.diff
 	(Remove patch to .hgignore)
 	(Remove patch to .hgtags)
 
@@ -103,8 +100,8 @@
 	(Remove PKGREVISION)
 	$ make mdi
 	$ make extract
-	$ pushd ${WRKOBJDIR}/www/firefox/work/mozilla-beta
-	$ patch -p0 < ~/firefox-47.0.diff
+	$ pushd ${WRKOBJDIR}/www/firefox/work/${DISTNAME}
+	$ patch -p0 < ~/firefox-51.0.diff
 	$ popd
 	$ mkpatches
 	$ patchdiff

Use pkg template to add anchors to ircII and irssi packages
Index: wikisrc/netbsd-code-chat.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/netbsd-code-chat.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/netbsd-code-chat.mdwn	20 Jan 2017 07:08:24 -0000	1.1
+++ wikisrc/netbsd-code-chat.mdwn	20 Jan 2017 08:32:11 -0000	1.2
@@ -4,5 +4,5 @@
 
  #NetBSD-code is pretty quiet when no-one has a question; that is a feature.
 
-[freenode](http://freenode.net/) has a list of servers. If you have never used IRC before, start with the Webchat at the Freenode website, and we recommend ircII or irssi (both in pkgsrc, try what fits you better) for later.
+[freenode](http://freenode.net/) has a list of servers. If you have never used IRC before, start with the Webchat at the Freenode website, and we recommend [[!template id=pkg category="chat" name="ircII"]] or [[!template id=pkg category="chat" name="irssi"]] (both in pkgsrc, try what fits you better) for later.
 For general hanging out and meeting the community, join #NetBSD or #pkgsrc instead.

also done
Index: wikisrc/projects/project/npf_web_ui.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/npf_web_ui.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/npf_web_ui.mdwn	3 Feb 2016 16:58:29 -0000	1.5
+++ wikisrc/projects/project/npf_web_ui.mdwn	20 Jan 2017 07:23:40 -0000	1.6
@@ -10,6 +10,10 @@
 TBD
 """
 
+done_by="""
+maya@NetBSD.org
+"""
+
 category="userland"
 difficulty="hard"
 duration="3 months"

initialize page about #NetBSD-code for the GSoC 2017 application
--- /dev/null	2017-01-20 07:00:33.000000000 +0000
+++ wikisrc/netbsd-code-chat.mdwn	2017-01-20 07:08:37.000000000 +0000
@@ -0,0 +1,8 @@
+# The Freenode channel #NetBSD-code
+
+This IRC channel was created as a resource for Google Summer of Code students, and expanded as a general resource for people doing programming on NetBSD or pkgsrc, because not only GSoC students can use a hand finding which Fine Manual page will help them with the latest snag on the way to done, or how they should best use an API. Design questions are better discussed on the mailing lists.
+
+ #NetBSD-code is pretty quiet when no-one has a question; that is a feature.
+
+[freenode](http://freenode.net/) has a list of servers. If you have never used IRC before, start with the Webchat at the Freenode website, and we recommend ircII or irssi (both in pkgsrc, try what fits you better) for later.
+For general hanging out and meeting the community, join #NetBSD or #pkgsrc instead.

retry
Index: wikisrc/community.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/community.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/community.mdwn	20 Jan 2017 06:46:50 -0000	1.4
+++ wikisrc/community.mdwn	20 Jan 2017 06:48:52 -0000	1.5
@@ -21,7 +21,7 @@
 * Channel #NetBSD on [IRCnet](http://www.ircnet.info/)
 * Channel #NetBSD on [EFnet](http://www.efnet.org/)
 * Channel #NetBSD on [freenode](http://freenode.net/)
-* Channel [[#NetBSD-code]] on [freenode](http://freenode.net/)
+* Channel [[#NetBSD-code|netbsd-code-chat]] on [freenode](http://freenode.net/)
 * SILC - [SILCNet](http://silcnet.org/) has a netbsd channel for secure chats.
 
 ## Internet forums, discussion groups, etc

Index: wikisrc/community.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/community.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/community.mdwn	20 Jan 2017 06:45:47 -0000	1.3
+++ wikisrc/community.mdwn	20 Jan 2017 06:46:50 -0000	1.4
@@ -21,7 +21,7 @@
 * Channel #NetBSD on [IRCnet](http://www.ircnet.info/)
 * Channel #NetBSD on [EFnet](http://www.efnet.org/)
 * Channel #NetBSD on [freenode](http://freenode.net/)
-* Channel [#NetBSD-code] on [freenode](http://freenode.net/)
+* Channel [[#NetBSD-code]] on [freenode](http://freenode.net/)
 * SILC - [SILCNet](http://silcnet.org/) has a netbsd channel for secure chats.
 
 ## Internet forums, discussion groups, etc

add a reference to #NetBSD-code
Index: wikisrc/community.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/community.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/community.mdwn	26 May 2013 12:56:16 -0000	1.2
+++ wikisrc/community.mdwn	20 Jan 2017 06:45:47 -0000	1.3
@@ -21,6 +21,7 @@
 * Channel #NetBSD on [IRCnet](http://www.ircnet.info/)
 * Channel #NetBSD on [EFnet](http://www.efnet.org/)
 * Channel #NetBSD on [freenode](http://freenode.net/)
+* Channel [#NetBSD-code] on [freenode](http://freenode.net/)
 * SILC - [SILCNet](http://silcnet.org/) has a netbsd channel for secure chats.
 
 ## Internet forums, discussion groups, etc

add reference to 2016
Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/projects/gsoc.mdwn	16 Feb 2016 17:40:53 -0000	1.20
+++ wikisrc/projects/gsoc.mdwn	20 Jan 2017 06:27:36 -0000	1.21
@@ -1,7 +1,7 @@
 [[!meta title="Google Summer of Code project proposals"]]
 
-NetBSD participated successfully in all of Google's Summer of Code
-programs up to 2013 (see our results of
+NetBSD participated successfully in the following Google's Summer of Code
+programs (see our results of
 [2005](http://www.netbsd.org/foundation/press/soc-summary.html),
 [2006](http://www.netbsd.org/foundation/press/soc2006-summary.html),
 [2007](http://www.netbsd.org/foundation/press/soc2007-summary.html),
@@ -10,7 +10,8 @@
 [2010](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2010),
 [2011](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of),
 [2012](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of1),
-[2013](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2)).
+[2013](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2) and
+[2016](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2016)).
 
 This page contains a list of concrete suggestions for projects we would
 like to see applications for in the next Summer of Code. Note that they

fix magic
Index: wikisrc/projects/project/posix_suite_compliance.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/posix_suite_compliance.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/posix_suite_compliance.mdwn	19 Jan 2017 23:46:20 -0000	1.5
+++ wikisrc/projects/project/posix_suite_compliance.mdwn	19 Jan 2017 23:48:26 -0000	1.6
@@ -8,7 +8,7 @@
 mentors="""
 [Christos Zoulas](mailto:christos@NetBSD.org)
 """
-completed_by="""
+done_by="""
 charles cui
 """
 

done in 2016
Index: wikisrc/projects/project/posix_suite_compliance.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/posix_suite_compliance.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/posix_suite_compliance.mdwn	21 Feb 2016 20:06:48 -0000	1.4
+++ wikisrc/projects/project/posix_suite_compliance.mdwn	19 Jan 2017 23:46:20 -0000	1.5
@@ -8,6 +8,9 @@
 mentors="""
 [Christos Zoulas](mailto:christos@NetBSD.org)
 """
+completed_by="""
+charles cui
+"""
 
 category="kernel"
 difficulty="easy"

test edit
Index: wikisrc/users/spz/sandbox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/sandbox.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/users/spz/sandbox.mdwn	9 Dec 2016 12:16:00 -0000	1.9
+++ wikisrc/users/spz/sandbox.mdwn	18 Jan 2017 20:03:18 -0000	1.10
@@ -1,3 +1,3 @@
 help, I'm caught in a cookie factory .. on second thought, send help later. Much later :)
 
-*blip*
+fussel

Define `no_install_notes' for all ports that do not have INSTALL notes
Index: wikisrc/ports/algor.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/algor.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/ports/algor.mdwn	26 Oct 2016 20:16:33 -0000	1.11
+++ wikisrc/ports/algor.mdwn	13 Jan 2017 16:06:02 -0000	1.12
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/algor/alogo2.gif"
+no_install_notes="defined"
 about="""
 NetBSD/algor is the port of NetBSD to the Algorithmics, Ltd. MIPS evaluation
 boards. Algorithmics was a long-time supplier of MIPS evaluation/prototyping
Index: wikisrc/ports/amigappc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amigappc.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/amigappc.mdwn	26 Oct 2016 20:16:33 -0000	1.10
+++ wikisrc/ports/amigappc.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -7,6 +7,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/arm26/arch310.gif"
+no_install_notes="defined"
 about="""
 NetBSD/amigappc is a very experimental port to the PowerPC-based Amiga expansion
 boards as manufactured by Phase 5.
Index: wikisrc/ports/cesfic.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cesfic.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/cesfic.mdwn	26 Oct 2016 20:16:33 -0000	1.9
+++ wikisrc/ports/cesfic.mdwn	13 Jan 2017 16:06:02 -0000	1.10
@@ -6,6 +6,7 @@
 pkg_rel="6.0"
 changes_cur="7.0"
 changes_future="8.0"
+no_install_notes="defined"
 about="""
 NetBSD/cesfic is a port to the m68040 based FIC8234 VME processor board, made by
 the swiss company CES (Geneve). These boards were popular in high energy physics
Index: wikisrc/ports/cobalt.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cobalt.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/cobalt.mdwn	26 Oct 2016 20:16:33 -0000	1.9
+++ wikisrc/ports/cobalt.mdwn	13 Jan 2017 16:06:02 -0000	1.10
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/cobalt/quberaq.gif"
+no_install_notes="defined"
 about="""
 NetBSD/cobalt is the port of NetBSD to Cobalt Networks' MIPS-based Microservers,
 now known as Sun Server Appliances.
Index: wikisrc/ports/ibmnws.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/ibmnws.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/ports/ibmnws.mdwn	26 Oct 2016 20:16:33 -0000	1.8
+++ wikisrc/ports/ibmnws.mdwn	13 Jan 2017 16:06:02 -0000	1.9
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/ibmnws/nws1000.png"
+no_install_notes="defined"
 about="""
 NetBSD/ibmnws is the port of NetBSD to [IBM](http://www.ibm.com/)
 Network Station Series 1000 PowerPC-based computers.
Index: wikisrc/ports/iyonix.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/iyonix.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/iyonix.mdwn	26 Oct 2016 20:16:33 -0000	1.10
+++ wikisrc/ports/iyonix.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -5,6 +5,7 @@
 pkg_rel="6.1"
 changes_cur="7.0"
 changes_future="8.0"
+no_install_notes="defined"
 about="""
 NetBSD/iyonix is a port of NetBSD to Castle Technology's [Iyonix](http://www.iyonix.com/32bit/)
 computers, an ARM based PC. It was first committed to the NetBSD source tree on
Index: wikisrc/ports/luna68k.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/luna68k.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/luna68k.mdwn	26 Oct 2016 20:16:34 -0000	1.10
+++ wikisrc/ports/luna68k.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/luna68k/luna.gif"
+no_install_notes="defined"
 about="""
 NetBSD/luna68k is a port of NetBSD to the LUNA product line of OMRON Tateisi
 Electronics, Japan. The LUNA was a 20MHz/m68030 desktop computer at the age of
Index: wikisrc/ports/mipsco.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/mipsco.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/mipsco.mdwn	26 Oct 2016 20:16:34 -0000	1.7
+++ wikisrc/ports/mipsco.mdwn	13 Jan 2017 16:06:02 -0000	1.8
@@ -5,6 +5,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/mipsco/rc3230.gif"
+no_install_notes="defined"
 about="""
 NetBSD/mipsco is a port of NetBSD to the MIPS Computer Systems Inc. family of
 workstations and servers. The Mips Magnum 3000 was a popular workstation that
Index: wikisrc/ports/mvmeppc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/mvmeppc.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/mvmeppc.mdwn	26 Oct 2016 20:16:34 -0000	1.10
+++ wikisrc/ports/mvmeppc.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/mvmeppc/mvme2600.gif"
+no_install_notes="defined"
 about="""
 NetBSD/mvmeppc is the port of NetBSD to Motorola's PowerPC VME Single Board
 Computers (SBC). The first Motorola SBC (68k-based) was introduced in 1988.
Index: wikisrc/ports/netwinder.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/netwinder.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/netwinder.mdwn	26 Oct 2016 20:16:34 -0000	1.9
+++ wikisrc/ports/netwinder.mdwn	13 Jan 2017 16:06:02 -0000	1.10
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/netwinder/2100.gif"
+no_install_notes="defined"
 about="""
 NetBSD/netwinder is a port of NetBSD to StrongARM based NetWinder machines.
 """
Index: wikisrc/ports/zaurus.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/zaurus.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/zaurus.mdwn	26 Oct 2016 20:16:34 -0000	1.10
+++ wikisrc/ports/zaurus.mdwn	13 Jan 2017 16:06:02 -0000	1.11
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/zaurus/zaurus.gif"
+no_install_notes="defined"
 about="""
 NetBSD/zaurus is a port of NetBSD to the ARM processor based PDAs by
 [Sharp](http://www.sharpusa.com/).

NetBSD/dreamcast packages for 6.0 no longer available. Switch to the 7.0 ones.
Pointed out by <sevan> via port-dreamcast/51836.
Members: 
	ports/dreamcast.mdwn:1.10->1.11 

Index: wikisrc/ports/dreamcast.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/dreamcast.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/dreamcast.mdwn	13 Jan 2017 10:09:08 -0000	1.10
+++ wikisrc/ports/dreamcast.mdwn	13 Jan 2017 10:15:11 -0000	1.11
@@ -2,7 +2,7 @@
 port="dreamcast"
 cur_rel="7.0.2"
 future_rel="8.0"
-pkg_rel="6.0"
+pkg_rel="7.0"
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/dreamcast/dreamcast2.gif"

NetBSD/dreamcast currently does not have INSTALL notes, define no_install_notes
to address that.
Pointed out by <sevan> via port-dreamcast/51836.
Members: 
	ports/dreamcast.mdwn:1.9->1.10 

Index: wikisrc/ports/dreamcast.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/dreamcast.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/dreamcast.mdwn	26 Oct 2016 20:16:33 -0000	1.9
+++ wikisrc/ports/dreamcast.mdwn	13 Jan 2017 10:09:08 -0000	1.10
@@ -6,6 +6,7 @@
 changes_cur="7.0"
 changes_future="8.0"
 thumbnail="http://www.netbsd.org/images/ports/dreamcast/dreamcast2.gif"
+no_install_notes="defined"
 about="""
 NetBSD/dreamcast is the port of NetBSD for the Japanese game console
 [SEGA](http://www.sega.co.jp) Dreamcast.

Add support for no_install_notes variable that if defined will not add the
`INSTALL notes' link for ports that does not have install notes available.
Should fix part of port-dreamcast/51836 problem reported by <sevan>.
Members: 
	templates/port.mdwn:1.16->1.17 

Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/templates/port.mdwn	22 Mar 2016 22:10:23 -0000	1.16
+++ wikisrc/templates/port.mdwn	13 Jan 2017 10:06:34 -0000	1.17
@@ -15,8 +15,8 @@
 <TMPL_IF port_var6>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var6> <TMPL_VAR cur_rel> via FTP](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>-<TMPL_VAR port_var6>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var6> FTP")</TMPL_IF>
 <TMPL_IF port_var7>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var7> <TMPL_VAR cur_rel> via FTP](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>-<TMPL_VAR port_var7>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var7> FTP")</TMPL_IF>
 <TMPL_ELSE>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> via FTP](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/ "NetBSD/<TMPL_VAR port> FTP")</TMPL_IF></TMPL_IF>
-<TMPL_IF cur_rel><TMPL_IF port_var1><TMPL_IF port_var_install_notes>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port_var_install_notes>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes")</TMPL_IF>
-<TMPL_ELSE>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes")</TMPL_IF></TMPL_IF>
+<TMPL_UNLESS no_install_notes><TMPL_IF cur_rel><TMPL_IF port_var1><TMPL_IF port_var_install_notes>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port_var_install_notes>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes")</TMPL_IF>
+<TMPL_ELSE>* [NetBSD/<TMPL_VAR port> <TMPL_VAR cur_rel> INSTALL notes](http://ftp.NetBSD.org/pub/NetBSD/NetBSD-<TMPL_VAR cur_rel>/<TMPL_VAR port>/INSTALL.html "NetBSD/<TMPL_VAR port> INSTALL notes")</TMPL_IF></TMPL_IF></TMPL_UNLESS>
 <TMPL_IF pkg_rel><TMPL_IF port_var1>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var1> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc](http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var1>/<TMPL_VAR pkg_rel>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var1> pkgsrc binary packages")
 <TMPL_IF port_var2>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var2> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc](http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var2>/<TMPL_VAR pkg_rel>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var2> pkgsrc binary packages")</TMPL_IF>
 <TMPL_IF port_var3>* [NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var3> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc](http://ftp.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var3>/<TMPL_VAR pkg_rel>/ "NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var3> pkgsrc binary packages")</TMPL_IF>
@@ -83,6 +83,7 @@
 - thumbnail (optional)
 - supported_hardware (optional)
 - unsupported_hardware (optional)
+- no_install_notes (optional)
 - additional (optional)
 
 </TMPL_IF>

Make the text about using a serial console for the dom0 more consistent
with reality.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.138
retrieving revision 1.139
diff -u -r1.138 -r1.139
--- wikisrc/ports/xen/howto.mdwn	29 Dec 2016 19:32:51 -0000	1.138
+++ wikisrc/ports/xen/howto.mdwn	4 Jan 2017 10:25:16 -0000	1.139
@@ -435,11 +435,16 @@
 which specifies that the dom0 should have 256M, leaving the rest to be
 allocated for domUs.  To use a serial console, use
 
-        menu=Xen:load /netbsd-XEN3_DOM0.gz console=com0;multiboot /xen.gz dom0_mem=256M console=com1 com1=9600,8n1
+        menu=Xen:load /netbsd-XEN3_DOM0.gz;multiboot /xen.gz dom0_mem=256M console=com1 com1=9600,8n1
 
 which will use the first serial port for Xen (which counts starting
-from 1), forcing speed/parity, and also for NetBSD (which counts
-starting at 0).  In an attempt to add performance, one can also add
+from 1, unlike NetBSD which counts starting from 0), forcing
+speed/parity.  Because the NetBSD command line lacks a
+"console=pc" argument, it will use the default "xencons" console device,
+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
 
         dom0_max_vcpus=1 dom0_vcpus_pin
 

Added a comment: Encryption PS
--- /dev/null	2017-01-04 09:52:03.000000000 +0000
+++ wikisrc/projects/project/transparent-cgd/comment_2_db7fddc05f1196353a702f21fce70d70._comment	2017-01-04 09:56:24.000000000 +0000
@@ -0,0 +1,22 @@
+[[!comment format=mdwn
+ username="https://openid.stackexchange.com/user/9e1973a3-233c-4f35-8b87-56c7ef1cd21d"
+ nickname="Sam"
+ subject="Encryption PS"
+ date="2017-01-04T09:56:08Z"
+ content="""
+I forgot to add that Truecrypt had a version for Linux and at one time had a BSD version which I believe no longer is around or operative. Truecrypt was anonymously written and he closed up shop and just disappeared one day. Truecrypt has also had extensive code verification leading to additions in Veracrypt.
+
+Here's a link for tcplay(derivative or Truecrypt).
+
+https://github.com/bwalex/tc-play
+
+Veracrypt
+
+https://veracrypt.codeplex.com/
+
+and the Dragonfly BSD I linked above where it's use of tcplay is described.
+
+I hope this is helpful All the questions that you asked in the summary have been answered on other systems with TC and VC. I know they're not Net but it could be a good start on how they've managed it.
+
+
+"""]]

Added a comment: Encryption
--- /dev/null	2017-01-04 09:32:00.000000000 +0000
+++ wikisrc/projects/project/transparent-cgd/comment_1_c816f012ad042401a47885ee192981e0._comment	2017-01-04 09:32:03.000000000 +0000
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="https://openid.stackexchange.com/user/9e1973a3-233c-4f35-8b87-56c7ef1cd21d"
+ nickname="Sam"
+ subject="Encryption"
+ date="2017-01-04T09:31:47Z"
+ content="""
+I think you should do something that no one wants to do. Take as much as you can from a long term existing system. There's a program that started on win98(name change)(scramdisk) and moved to Win 2000(ECM) then on Win XP,...etc(Truecrpyt). It now is rewritten and called (Veracrypt) for Windows, Linux, Mac OS and Raspberry Pi ARMv7. The only thing stopping me from moving to one of the BSD's is reading truecrypt files. DragonflyBSD reads Truecrypt through tcplay a rewrite of truecrypt but DF is a little more experimental than I want for a desktop.
+ 
+https://www.dragonflybsd.org/features/#index5h2
+
+ So there's two versions from the same Truecrypt source. Tcplay and Veracrypt. Veracrypt is a newer version that is audited and has corrected some small deficiencies of TC so is better but bigger, more complete and complex. The MacOS works through FUSE specifically OSXFUSE 2.5. Linux I think through DMcrypt. Here's what so good about Veracrypt/Truecrypt. It has encryption on the fly for not only regular drives but the OS system drive also, after it's running. This means not setting up encryption but encrypting the drive as the OS runs, then writing the boot with password enabled. It's very, very nice. I'm not saying that all these things need to be in place at once but using the code they have already written shows a pathway. Too start just use the code for equivalent encryption to Veracrypt(which has a compatibility function for Truecrypt). The important thing is Truecrypt has been around a long, long time and lots of people have this format and it works. For some reason people keep reinventing the wheel 
+"""]]

Remove preapproved funding designations.
Per discussion between board and core, these stale designations will
be replaced by something we hope to be more lively and maintained.
Members: 
	projects/project/atomic_fifo_lifo_queues.mdwn:1.1->1.2 
	projects/project/atomic_radix_patricia_trees.mdwn:1.1->1.2 
	projects/project/fast_protocol.mdwn:1.1->1.2 
	projects/project/if_poll.mdwn:1.1->1.2 
	projects/project/kernel_continuations.mdwn:1.3->1.4 
	projects/project/lazy_receive.mdwn:1.1->1.2 
	projects/project/nexthop_cache.mdwn:1.1->1.2 
	projects/project/optional_tcp_syncache.mdwn:1.1->1.2 

Index: wikisrc/projects/project/atomic_fifo_lifo_queues.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/atomic_fifo_lifo_queues.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/atomic_fifo_lifo_queues.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/atomic_fifo_lifo_queues.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -10,11 +10,9 @@
 
 category="kernel"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to implement lockless and atomic FIFO/LIFO
 queues in the kernel.  The routines to be implemented allow for commonly
Index: wikisrc/projects/project/atomic_radix_patricia_trees.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/atomic_radix_patricia_trees.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/atomic_radix_patricia_trees.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/atomic_radix_patricia_trees.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -10,11 +10,9 @@
 
 category="kernel"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to implement lockless, atomic and generic Radix
 and Patricia trees.  BSD systems have always used a radix tree for their
Index: wikisrc/projects/project/fast_protocol.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fast_protocol.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/fast_protocol.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/fast_protocol.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to enhance the networking protocols to process
 incoming packets more efficiently.  The basic idea is the following: when a
Index: wikisrc/projects/project/if_poll.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/if_poll.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/if_poll.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/if_poll.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to implement interrupt handling at the
 granularity of a networking interface.  When a network device gets an
Index: wikisrc/projects/project/kernel_continuations.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/kernel_continuations.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/kernel_continuations.mdwn	16 Feb 2015 06:46:30 -0000	1.3
+++ wikisrc/projects/project/kernel_continuations.mdwn	3 Jan 2017 20:51:24 -0000	1.4
@@ -10,11 +10,9 @@
 
 category="kernel"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to implement continuations at the kernel level.
 Most of the pieces are already available in the kernel, so this can be
Index: wikisrc/projects/project/lazy_receive.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/lazy_receive.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/lazy_receive.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/lazy_receive.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to improve the way the processing of incoming
 packets is handled.
Index: wikisrc/projects/project/nexthop_cache.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/nexthop_cache.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/nexthop_cache.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/nexthop_cache.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to remove the ARP, AARP, ISO SNPA, and IPv6
 Neighbors from the routing table.  Instead, the `ifnet` structure should
Index: wikisrc/projects/project/optional_tcp_syncache.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/optional_tcp_syncache.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/optional_tcp_syncache.mdwn	10 Nov 2011 03:06:51 -0000	1.1
+++ wikisrc/projects/project/optional_tcp_syncache.mdwn	3 Jan 2017 20:51:24 -0000	1.2
@@ -11,11 +11,9 @@
 
 category="networking"
 difficulty="hard"
-funded="The NetBSD Foundation"
 
 description="""
-This project proposal is a subtask of [[smp_networking]] and is elegible
-for funding independently.
+This project proposal is a subtask of [[smp_networking]].
 
 The goal of this project is to make the SYN cache optional.  For small systems,
 this is complete overkill and should be made optional.

goodbye 2016, hello 2017
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- wikisrc/templates/page.tmpl	15 Apr 2016 17:39:25 -0000	1.32
+++ wikisrc/templates/page.tmpl	1 Jan 2017 07:09:15 -0000	1.33
@@ -279,7 +279,7 @@
       <span class="footcopy"><a href="about/disclaimer.html">
         Disclaimer</a> |
         <span class="copyright">
-          Copyright &copy; 1994-2016 The NetBSD Foundation, Inc.
+          Copyright &copy; 1994-2017 The NetBSD Foundation, Inc.
         </span>
         ALL
         RIGHTS RESERVED. <br /> NetBSD<sup>&reg;</sup> is a registered

calendar update
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1 @@
+[[!calendar type=year year=2017 pages="internal(blog/*)"]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/01.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=01 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(01) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/02.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=02 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(02) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/03.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=03 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(03) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/04.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=04 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(04) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/05.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=05 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(05) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/06.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=06 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(06) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/07.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=07 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(07) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/08.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=08 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(08) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/09.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=09 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(09) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/10.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=10 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(10) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/11.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=11 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(11) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]
--- /dev/null	2017-01-01 00:00:02.000000000 +0000
+++ wikisrc/archives/2017/12.mdwn	2017-01-01 00:00:17.000000000 +0000
@@ -0,0 +1,5 @@
+[[!sidebar content="""
+[[!calendar type=month month=12 year=2017 pages="internal(blog/*)"]]
+"""]]
+
+[[!inline pages="creation_month(12) and creation_year(2017) and internal(blog/*)" show=0 feeds=no reverse=yes]]

Spam
--- wikisrc/wiki/news/no_longer_pre-release__44___but.../comment_1_ffb400c52c1902a31c1f140e3fa3cd80._comment	2016-12-30 12:26:31.000000000 +0000
+++ /dev/null	2016-12-30 12:24:05.000000000 +0000
@@ -1,29 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
- nickname="harsh"
- subject="Describe 1…800…204…4122 @@@@ Lexmark printer customer Support phone number usa "
- date="2016-12-29T23:18:08Z"
- content="""
-((moti))Call @@@++ USA 18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t
-p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r
-n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1
-18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r
-u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER
-s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1844-848-1262 USA, LEXMARK  PRINTER 
-Tech Support phone number,LEXMARK  PRINTER technical support phone number 1 18002044122
-.LEXMARK  PRINTER Tech Support Number LEXMARK  PRINTER Tech LEXMARK  PRINTER tech support, LEXMARK  PRINTER tech support
-number, LEXMARK  PRINTER tech support phone number, LEXMARK  PRINTER technical support, LEXMARK  PRINTER
-technical support number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER tech
-support number, LEXMARK  PRINTER support number, LEXMARK  PRINTER Tech support phone number, LEXMARK  PRINTER
-support phone number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER technical
-support number,Support Phone Number for LEXMARK  PRINTER  Phone Number for LEXMARK  PRINTER
-CustomerService Technical Support Telephone Number LEXMARK  PRINTER  support number
-LEXMARK  PRINTER LEXMARK  PRINTER  tech support number LEXMARK  PRINTER LEXMARK  PRINTER  technical support
-number LEXMARK  PRINTER LEXMARK  PRINTER  technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER 
-customer service number LEXMARK  PRINTER LEXMARK  PRINTER internet security technical support LEXMARK  PRINTER
-technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
-LEXMARK  PRINTER customer support phone number I-844-848-1262 LEXMARK  PRINTER LEXMARK  PRINTER  support
-phone number LEXMARK  PRINTER LEXMARK  PRINTER support phone LEXMARK  PRINTER tech support LEXMARK  PRINTER customer
-support LEXMARK  PRINTER phone support LEXMARK  PRINTER support number LEXMARK  PRINTER LEXMARK  PRINTER technical support
-LEXMARK  PRINTER  customer support phone 
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_1_2e85048f0cd0ba602ae62c2706fe4159._comment	2016-12-30 12:26:31.000000000 +0000
+++ /dev/null	2016-12-30 12:24:05.000000000 +0000
@@ -1,93 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
- nickname="harsh"
- subject="(((((((1800 204 4122)))))))))@@.@ Lexmark printer tech support number Lexmark printer customer service number"
- date="2016-12-29T23:14:06Z"
- content="""
-((moti))Call @@@++ USA 18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t
-p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r
-n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1
-18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r
-u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER
-s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1844-848-1262 USA, LEXMARK  PRINTER 
-Tech Support phone number,LEXMARK  PRINTER technical support phone number 1 18002044122
-.LEXMARK  PRINTER Tech Support Number LEXMARK  PRINTER Tech LEXMARK  PRINTER tech support, LEXMARK  PRINTER tech support
-number, LEXMARK  PRINTER tech support phone number, LEXMARK  PRINTER technical support, LEXMARK  PRINTER
-technical support number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER tech
-support number, LEXMARK  PRINTER support number, LEXMARK  PRINTER Tech support phone number, LEXMARK  PRINTER
-support phone number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER technical
-support number,Support Phone Number for LEXMARK  PRINTER  Phone Number for LEXMARK  PRINTER
-CustomerService Technical Support Telephone Number LEXMARK  PRINTER  support number
-LEXMARK  PRINTER LEXMARK  PRINTER  tech support number LEXMARK  PRINTER LEXMARK  PRINTER  technical support
-number LEXMARK  PRINTER LEXMARK  PRINTER  technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER 
-customer service number LEXMARK  PRINTER LEXMARK  PRINTER internet security technical support LEXMARK  PRINTER
-technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
-LEXMARK  PRINTER customer support phone number I-844-848-1262 LEXMARK  PRINTER LEXMARK  PRINTER  support
-phone number LEXMARK  PRINTER LEXMARK  PRINTER support phone LEXMARK  PRINTER tech support LEXMARK  PRINTER customer
-support LEXMARK  PRINTER phone support LEXMARK  PRINTER support number LEXMARK  PRINTER LEXMARK  PRINTER technical support
-LEXMARK  PRINTER  customer support phone number LEXMARK  PRINTER LEXMARK  PRINTER  tech support
-phone number LEXMARK  PRINTER contact LEXMARK  PRINTER support LEXMARK  PRINTER  technical support phone
-number ~!~18002044122++ LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER tech support LEXMARK  PRINTER
-support ticket LEXMARK  PRINTER customer support number LEXMARK  PRINTER LEXMARK  PRINTER tech support number
-LEXMARK  PRINTER LEXMARK  PRINTER technical support number LEXMARK  PRINTER LEXMARK  PRINTER support center LEXMARK  PRINTER telephone
-support call LEXMARK  PRINTER support LEXMARK  PRINTER  support support LEXMARK  PRINTER LEXMARK  PRINTER billing
-support LEXMARK  PRINTER  technical support number LEXMARK  PRINTER support LEXMARK  PRINTER 
-LEXMARK  PRINTER online support LEXMARK  PRINTER contasct support LEXMARK  PRINTER  support number LEXMARK  PRINTER
-LEXMARK  PRINTER  customer support number LEXMARK  PRINTER LEXMARK  PRINTER  tech support number
-LEXMARK  PRINTER support for LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone
-number LEXMARK  PRINTER LEXMARK  PRINTER contact phone number LEXMARK  PRINTER LEXMARK  PRINTER  phone number LEXMARK  PRINTER
-LEXMARK  PRINTER  customer service phone number LEXMARK  PRINTER phone number LEXMARK  PRINTER for LEXMARK  PRINTER
-customer service LEXMARK  PRINTER software phone number LEXMARK  PRINTER phone number LEXMARK  PRINTER for LEXMARK  PRINTER
-LEXMARK  PRINTER customer service telephone number LEXMARK  PRINTER LEXMARK  PRINTER helpline phone number LEXMARK  PRINTER
-LEXMARK  PRINTER contact number LEXMARK  PRINTER LEXMARK  PRINTER customer service number LEXMARK  PRINTER LEXMARK  PRINTER customer
-service phone number ~!~18002044122++ LEXMARK  PRINTER us LEXMARK  PRINTER customer service phone
-number LEXMARK  PRINTER usa LEXMARK  PRINTER telephone number LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER usa
-LEXMARK  PRINTER  contact number LEXMARK  PRINTER LEXMARK  PRINTER number LEXMARK  PRINTER LEXMARK  PRINTER contact number
-LEXMARK  PRINTER usa LEXMARK  PRINTER  helpline number LEXMARK  PRINTER LEXMARK  PRINTER helpline number LEXMARK  PRINTER LEXMARK  PRINTER
-customer number LEXMARK  PRINTER LEXMARK  PRINTER  customer service number LEXMARK  PRINTER LEXMARK  PRINTER contact
-telephone number LEXMARK  PRINTER contact number LEXMARK  PRINTER for LEXMARK  PRINTER LEXMARK  PRINTER software contact
-number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER LEXMARK  PRINTER telephone number LEXMARK  PRINTER uk LEXMARK  PRINTER
-registration number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER usa LEXMARK  PRINTER customer
-service LEXMARK  PRINTER software customer service contact LEXMARK  PRINTER customer service LEXMARK  PRINTER
-customer service phone LEXMARK  PRINTER  customer service LEXMARK  PRINTER service LEXMARK  PRINTER
- technical support LEXMARK  PRINTER  customer support LEXMARK  PRINTER technical
-support reviews telephone LEXMARK  PRINTER  LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
-LEXMARK  PRINTER  tech support phone number LEXMARK  PRINTER LEXMARK  PRINTER  customer service
-LEXMARK  PRINTER technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER  free  support
-LEXMARK  PRINTER customer service billing LEXMARK  PRINTER customer service email address LEXMARK  PRINTER
-customer service reviews contact LEXMARK  PRINTER customer service LEXMARK  PRINTER tech support
-number LEXMARK  PRINTER usa LEXMARK  PRINTER  support number LEXMARK  PRINTER LEXMARK  PRINTER  contact
-number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone number LEXMARK  PRINTER LEXMARK  PRINTER technical support
-usa LEXMARK  PRINTER technical support number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone LEXMARK  PRINTER tech
-support number LEXMARK  PRINTER LEXMARK  PRINTER customer service telephone number LEXMARK  PRINTER LEXMARK  PRINTER
- customer support number LEXMARK  PRINTER LEXMARK  PRINTER  phone number LEXMARK  PRINTER LEXMARK  PRINTER
- online support LEXMARK  PRINTER customer service number LEXMARK  PRINTER LEXMARK  PRINTER tech support
-center LEXMARK  PRINTER customer service LEXMARK  PRINTER software customer service LEXMARK  PRINTER customer
-care number LEXMARK  PRINTER usa LEXMARK  PRINTER customer number LEXMARK  PRINTER LEXMARK  PRINTER customer support number
-LEXMARK  PRINTER LEXMARK  PRINTER customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care toll free number
-LEXMARK  PRINTER LEXMARK  PRINTER tech support LEXMARK  PRINTER technical support LEXMARK  PRINTER  support LEXMARK  PRINTER
- tech support LEXMARK  PRINTER support center LEXMARK  PRINTER.com customer service LEXMARK  PRINTER
- customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care LEXMARK  PRINTER phone number LEXMARK  PRINTER
-phone number LEXMARK  PRINTER for LEXMARK  PRINTER customer service LEXMARK  PRINTER phone support LEXMARK  PRINTER phone
-number LEXMARK  PRINTER tech support LEXMARK  PRINTER support phone number LEXMARK  PRINTER contact LEXMARK  PRINTER by
-phone LEXMARK  PRINTER contact phone number LEXMARK  PRINTER LEXMARK  PRINTER helpline phone number LEXMARK  PRINTER LEXMARK  PRINTER
- phone LEXMARK  PRINTER  for phone LEXMARK  PRINTER contact number LEXMARK  PRINTER LEXMARK  PRINTER contact
-support contact LEXMARK  PRINTER  LEXMARK  PRINTER contact number LEXMARK  PRINTER usa LEXMARK  PRINTER toll free
-number LEXMARK  PRINTER LEXMARK  PRINTER telephone number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER usa
-LEXMARK  PRINTER  support services technical support for  LEXMARK  PRINTER LEXMARK  PRINTER
-customer service phone number LEXMARK  PRINTER usa LEXMARK  PRINTER  customer care number
-LEXMARK  PRINTER usa LEXMARK  PRINTER customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care center LEXMARK  PRINTER
-customer support LEXMARK  PRINTER customer support phone LEXMARK  PRINTER customer help LEXMARK  PRINTER
-customer & technical support LEXMARK  PRINTER customer portal LEXMARK  PRINTER customer care phone
-number LEXMARK  PRINTER usa LEXMARK  PRINTER customer care email LEXMARK  PRINTER helpline LEXMARK  PRINTER tech support
-contact LEXMARK  PRINTER customer care toll free LEXMARK  PRINTER  customer service number
-LEXMARK  PRINTER LEXMARK  PRINTER  protection norton  customer service number LEXMARK  PRINTER
-LEXMARK  PRINTER software customer service number LEXMARK  PRINTER LEXMARK  PRINTER hotline customer service
-phone number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone number LEXMARK  PRINTER us how to contact
-LEXMARK  PRINTER by email LEXMARK  PRINTER free phone support LEXMARK  PRINTER  technical support number
-LEXMARK  PRINTER LEXMARK  PRINTER  technical support help desk phone number LEXMARK  PRINTER LEXMARK  PRINTER
-technical support number LEXMARK  PRINTER toll free number LEXMARK  PRINTER LEXMARK  PRINTER  customer
-support phone number LEXMARK  PRINTER LEXMARK  PRINTER  customer
-
-
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_2_4a48aa610335921245f39a8641cca5da._comment	2016-12-30 12:26:31.000000000 +0000
+++ /dev/null	2016-12-30 12:24:05.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
- nickname="harsh"
- subject="HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell Pr"
- date="2016-12-29T23:19:26Z"
- content="""
-HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_3_14b1e5237919f09714489f6e79123ad4._comment	2016-12-30 12:26:31.000000000 +0000
+++ /dev/null	2016-12-30 12:24:05.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
- nickname="harsh"
- subject="USA))))@.@@.@1*800~204-4122 Lexmark printer technical support number,Lexmar"
- date="2016-12-29T23:20:26Z"
- content="""
-HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer
-"""]]

Added a comment: USA))))@.@@.@1*800~204-4122 Lexmark printer technical support number,Lexmar
--- /dev/null	2016-12-30 12:24:05.000000000 +0000
+++ wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_3_14b1e5237919f09714489f6e79123ad4._comment	2016-12-30 12:26:32.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
+ nickname="harsh"
+ subject="USA))))@.@@.@1*800~204-4122 Lexmark printer technical support number,Lexmar"
+ date="2016-12-29T23:20:26Z"
+ content="""
+HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer
+"""]]

Added a comment: HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell Pr
--- /dev/null	2016-12-30 12:24:05.000000000 +0000
+++ wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_2_4a48aa610335921245f39a8641cca5da._comment	2016-12-30 12:26:32.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
+ nickname="harsh"
+ subject="HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell Pr"
+ date="2016-12-29T23:19:26Z"
+ content="""
+HeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer Tech Support number, dell PrHeLp@dEsk@uSa.@=1~800~204~4122$$$ dell Printer
+"""]]

Added a comment: Describe 1…800…204…4122 @@@@ Lexmark printer customer Support phone number usa
--- /dev/null	2016-12-30 12:24:05.000000000 +0000
+++ wikisrc/wiki/news/no_longer_pre-release__44___but.../comment_1_ffb400c52c1902a31c1f140e3fa3cd80._comment	2016-12-30 12:26:32.000000000 +0000
@@ -0,0 +1,29 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
+ nickname="harsh"
+ subject="Describe 1…800…204…4122 @@@@ Lexmark printer customer Support phone number usa "
+ date="2016-12-29T23:18:08Z"
+ content="""
+((moti))Call @@@++ USA 18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t
+p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r
+n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1
+18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r
+u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER
+s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1844-848-1262 USA, LEXMARK  PRINTER 
+Tech Support phone number,LEXMARK  PRINTER technical support phone number 1 18002044122
+.LEXMARK  PRINTER Tech Support Number LEXMARK  PRINTER Tech LEXMARK  PRINTER tech support, LEXMARK  PRINTER tech support
+number, LEXMARK  PRINTER tech support phone number, LEXMARK  PRINTER technical support, LEXMARK  PRINTER
+technical support number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER tech
+support number, LEXMARK  PRINTER support number, LEXMARK  PRINTER Tech support phone number, LEXMARK  PRINTER
+support phone number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER technical
+support number,Support Phone Number for LEXMARK  PRINTER  Phone Number for LEXMARK  PRINTER
+CustomerService Technical Support Telephone Number LEXMARK  PRINTER  support number
+LEXMARK  PRINTER LEXMARK  PRINTER  tech support number LEXMARK  PRINTER LEXMARK  PRINTER  technical support
+number LEXMARK  PRINTER LEXMARK  PRINTER  technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER 
+customer service number LEXMARK  PRINTER LEXMARK  PRINTER internet security technical support LEXMARK  PRINTER
+technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
+LEXMARK  PRINTER customer support phone number I-844-848-1262 LEXMARK  PRINTER LEXMARK  PRINTER  support
+phone number LEXMARK  PRINTER LEXMARK  PRINTER support phone LEXMARK  PRINTER tech support LEXMARK  PRINTER customer
+support LEXMARK  PRINTER phone support LEXMARK  PRINTER support number LEXMARK  PRINTER LEXMARK  PRINTER technical support
+LEXMARK  PRINTER  customer support phone 
+"""]]

Added a comment: (((((((1800 204 4122)))))))))@@.@ Lexmark printer tech support number Lexmark printer customer service number
--- /dev/null	2016-12-29 23:10:01.000000000 +0000
+++ wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_1_2e85048f0cd0ba602ae62c2706fe4159._comment	2016-12-29 23:14:21.000000000 +0000
@@ -0,0 +1,93 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/UrExJeYXzttcXvhslLFcUi9w0_8_RXuqj4SGGV.P9O3ypqjNwWLM9PjXgnB15f4T9HZeOlo-#7322f"
+ nickname="harsh"
+ subject="(((((((1800 204 4122)))))))))@@.@ Lexmark printer tech support number Lexmark printer customer service number"
+ date="2016-12-29T23:14:06Z"
+ content="""
+((moti))Call @@@++ USA 18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t
+p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r
+n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1
+18002044122 LEXMARK  PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r
+u.s.a. C.a.l.l LEXMARK  PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a LEXMARK  PRINTER
+s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1844-848-1262 USA, LEXMARK  PRINTER 
+Tech Support phone number,LEXMARK  PRINTER technical support phone number 1 18002044122
+.LEXMARK  PRINTER Tech Support Number LEXMARK  PRINTER Tech LEXMARK  PRINTER tech support, LEXMARK  PRINTER tech support
+number, LEXMARK  PRINTER tech support phone number, LEXMARK  PRINTER technical support, LEXMARK  PRINTER
+technical support number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER tech
+support number, LEXMARK  PRINTER support number, LEXMARK  PRINTER Tech support phone number, LEXMARK  PRINTER
+support phone number, LEXMARK  PRINTER technical support phone number, LEXMARK  PRINTER technical
+support number,Support Phone Number for LEXMARK  PRINTER  Phone Number for LEXMARK  PRINTER
+CustomerService Technical Support Telephone Number LEXMARK  PRINTER  support number
+LEXMARK  PRINTER LEXMARK  PRINTER  tech support number LEXMARK  PRINTER LEXMARK  PRINTER  technical support
+number LEXMARK  PRINTER LEXMARK  PRINTER  technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER 
+customer service number LEXMARK  PRINTER LEXMARK  PRINTER internet security technical support LEXMARK  PRINTER
+technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
+LEXMARK  PRINTER customer support phone number I-844-848-1262 LEXMARK  PRINTER LEXMARK  PRINTER  support
+phone number LEXMARK  PRINTER LEXMARK  PRINTER support phone LEXMARK  PRINTER tech support LEXMARK  PRINTER customer
+support LEXMARK  PRINTER phone support LEXMARK  PRINTER support number LEXMARK  PRINTER LEXMARK  PRINTER technical support
+LEXMARK  PRINTER  customer support phone number LEXMARK  PRINTER LEXMARK  PRINTER  tech support
+phone number LEXMARK  PRINTER contact LEXMARK  PRINTER support LEXMARK  PRINTER  technical support phone
+number ~!~18002044122++ LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER tech support LEXMARK  PRINTER
+support ticket LEXMARK  PRINTER customer support number LEXMARK  PRINTER LEXMARK  PRINTER tech support number
+LEXMARK  PRINTER LEXMARK  PRINTER technical support number LEXMARK  PRINTER LEXMARK  PRINTER support center LEXMARK  PRINTER telephone
+support call LEXMARK  PRINTER support LEXMARK  PRINTER  support support LEXMARK  PRINTER LEXMARK  PRINTER billing
+support LEXMARK  PRINTER  technical support number LEXMARK  PRINTER support LEXMARK  PRINTER 
+LEXMARK  PRINTER online support LEXMARK  PRINTER contasct support LEXMARK  PRINTER  support number LEXMARK  PRINTER
+LEXMARK  PRINTER  customer support number LEXMARK  PRINTER LEXMARK  PRINTER  tech support number
+LEXMARK  PRINTER support for LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone
+number LEXMARK  PRINTER LEXMARK  PRINTER contact phone number LEXMARK  PRINTER LEXMARK  PRINTER  phone number LEXMARK  PRINTER
+LEXMARK  PRINTER  customer service phone number LEXMARK  PRINTER phone number LEXMARK  PRINTER for LEXMARK  PRINTER
+customer service LEXMARK  PRINTER software phone number LEXMARK  PRINTER phone number LEXMARK  PRINTER for LEXMARK  PRINTER
+LEXMARK  PRINTER customer service telephone number LEXMARK  PRINTER LEXMARK  PRINTER helpline phone number LEXMARK  PRINTER
+LEXMARK  PRINTER contact number LEXMARK  PRINTER LEXMARK  PRINTER customer service number LEXMARK  PRINTER LEXMARK  PRINTER customer
+service phone number ~!~18002044122++ LEXMARK  PRINTER us LEXMARK  PRINTER customer service phone
+number LEXMARK  PRINTER usa LEXMARK  PRINTER telephone number LEXMARK  PRINTER LEXMARK  PRINTER phone number LEXMARK  PRINTER usa
+LEXMARK  PRINTER  contact number LEXMARK  PRINTER LEXMARK  PRINTER number LEXMARK  PRINTER LEXMARK  PRINTER contact number
+LEXMARK  PRINTER usa LEXMARK  PRINTER  helpline number LEXMARK  PRINTER LEXMARK  PRINTER helpline number LEXMARK  PRINTER LEXMARK  PRINTER
+customer number LEXMARK  PRINTER LEXMARK  PRINTER  customer service number LEXMARK  PRINTER LEXMARK  PRINTER contact
+telephone number LEXMARK  PRINTER contact number LEXMARK  PRINTER for LEXMARK  PRINTER LEXMARK  PRINTER software contact
+number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER LEXMARK  PRINTER telephone number LEXMARK  PRINTER uk LEXMARK  PRINTER
+registration number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER usa LEXMARK  PRINTER customer
+service LEXMARK  PRINTER software customer service contact LEXMARK  PRINTER customer service LEXMARK  PRINTER
+customer service phone LEXMARK  PRINTER  customer service LEXMARK  PRINTER service LEXMARK  PRINTER
+ technical support LEXMARK  PRINTER  customer support LEXMARK  PRINTER technical
+support reviews telephone LEXMARK  PRINTER  LEXMARK  PRINTER tech support phone number LEXMARK  PRINTER
+LEXMARK  PRINTER  tech support phone number LEXMARK  PRINTER LEXMARK  PRINTER  customer service
+LEXMARK  PRINTER technical support phone number LEXMARK  PRINTER LEXMARK  PRINTER  free  support
+LEXMARK  PRINTER customer service billing LEXMARK  PRINTER customer service email address LEXMARK  PRINTER
+customer service reviews contact LEXMARK  PRINTER customer service LEXMARK  PRINTER tech support
+number LEXMARK  PRINTER usa LEXMARK  PRINTER  support number LEXMARK  PRINTER LEXMARK  PRINTER  contact
+number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone number LEXMARK  PRINTER LEXMARK  PRINTER technical support
+usa LEXMARK  PRINTER technical support number LEXMARK  PRINTER LEXMARK  PRINTER tech support phone LEXMARK  PRINTER tech
+support number LEXMARK  PRINTER LEXMARK  PRINTER customer service telephone number LEXMARK  PRINTER LEXMARK  PRINTER
+ customer support number LEXMARK  PRINTER LEXMARK  PRINTER  phone number LEXMARK  PRINTER LEXMARK  PRINTER
+ online support LEXMARK  PRINTER customer service number LEXMARK  PRINTER LEXMARK  PRINTER tech support
+center LEXMARK  PRINTER customer service LEXMARK  PRINTER software customer service LEXMARK  PRINTER customer
+care number LEXMARK  PRINTER usa LEXMARK  PRINTER customer number LEXMARK  PRINTER LEXMARK  PRINTER customer support number
+LEXMARK  PRINTER LEXMARK  PRINTER customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care toll free number
+LEXMARK  PRINTER LEXMARK  PRINTER tech support LEXMARK  PRINTER technical support LEXMARK  PRINTER  support LEXMARK  PRINTER
+ tech support LEXMARK  PRINTER support center LEXMARK  PRINTER.com customer service LEXMARK  PRINTER
+ customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care LEXMARK  PRINTER phone number LEXMARK  PRINTER
+phone number LEXMARK  PRINTER for LEXMARK  PRINTER customer service LEXMARK  PRINTER phone support LEXMARK  PRINTER phone
+number LEXMARK  PRINTER tech support LEXMARK  PRINTER support phone number LEXMARK  PRINTER contact LEXMARK  PRINTER by
+phone LEXMARK  PRINTER contact phone number LEXMARK  PRINTER LEXMARK  PRINTER helpline phone number LEXMARK  PRINTER LEXMARK  PRINTER
+ phone LEXMARK  PRINTER  for phone LEXMARK  PRINTER contact number LEXMARK  PRINTER LEXMARK  PRINTER contact
+support contact LEXMARK  PRINTER  LEXMARK  PRINTER contact number LEXMARK  PRINTER usa LEXMARK  PRINTER toll free
+number LEXMARK  PRINTER LEXMARK  PRINTER telephone number LEXMARK  PRINTER LEXMARK  PRINTER toll free number LEXMARK  PRINTER usa
+LEXMARK  PRINTER  support services technical support for  LEXMARK  PRINTER LEXMARK  PRINTER
+customer service phone number LEXMARK  PRINTER usa LEXMARK  PRINTER  customer care number
+LEXMARK  PRINTER usa LEXMARK  PRINTER customer care number LEXMARK  PRINTER LEXMARK  PRINTER customer care center LEXMARK  PRINTER
+customer support LEXMARK  PRINTER customer support phone LEXMARK  PRINTER customer help LEXMARK  PRINTER
+customer & technical support LEXMARK  PRINTER customer portal LEXMARK  PRINTER customer care phone
+number LEXMARK  PRINTER usa LEXMARK  PRINTER customer care email LEXMARK  PRINTER helpline LEXMARK  PRINTER tech support
+contact LEXMARK  PRINTER customer care toll free LEXMARK  PRINTER  customer service number
+LEXMARK  PRINTER LEXMARK  PRINTER  protection norton  customer service number LEXMARK  PRINTER
+LEXMARK  PRINTER software customer service number LEXMARK  PRINTER LEXMARK  PRINTER hotline customer service
+phone number LEXMARK  PRINTER LEXMARK  PRINTER customer service phone number LEXMARK  PRINTER us how to contact
+LEXMARK  PRINTER by email LEXMARK  PRINTER free phone support LEXMARK  PRINTER  technical support number
+LEXMARK  PRINTER LEXMARK  PRINTER  technical support help desk phone number LEXMARK  PRINTER LEXMARK  PRINTER
+technical support number LEXMARK  PRINTER toll free number LEXMARK  PRINTER LEXMARK  PRINTER  customer
+support phone number LEXMARK  PRINTER LEXMARK  PRINTER  customer
+
+
+"""]]

Fix typo.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.137
retrieving revision 1.138
diff -u -r1.137 -r1.138
--- wikisrc/ports/xen/howto.mdwn	29 Dec 2016 19:24:16 -0000	1.137
+++ wikisrc/ports/xen/howto.mdwn	29 Dec 2016 19:32:51 -0000	1.138
@@ -111,7 +111,7 @@
 
 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
-12017Q1.
+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

Note removal of 3.1, 3.3 and 4.1 from pkgsrc-current
Threaten purging them from the HOWTO after 2017Q1 is cut.
Members: 
	ports/xen/howto.mdwn:1.136->1.137 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.136
retrieving revision 1.137
diff -u -r1.136 -r1.137
--- wikisrc/ports/xen/howto.mdwn	21 Dec 2016 17:03:03 -0000	1.136
+++ wikisrc/ports/xen/howto.mdwn	29 Dec 2016 19:24:16 -0000	1.137
@@ -109,6 +109,10 @@
 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
+12017Q1.
+
 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

Indent code fragments properly.
Index: wikisrc/features/uvm_hotplug.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/features/uvm_hotplug.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/features/uvm_hotplug.mdwn	29 Dec 2016 16:59:58 -0000	1.2
+++ wikisrc/features/uvm_hotplug.mdwn	29 Dec 2016 17:02:27 -0000	1.3
@@ -7,8 +7,10 @@
      [[!template id=man name=uvm_hotplug section=9]] change.
 
      Early boot code of every port is affected. Global variables:
-     struct vm_physseg vm_physmem;
-     int vm_nphysmem;
+
+     	   struct vm_physseg vm_physmem;
+     	   int vm_nphysmem;
+
      are no longer visible. They need to be replaced by appropriate
      accessor calls in [[!template id=man name=uvm_hotplug section=9]]
 

Formatting.
Index: wikisrc/features/uvm_hotplug.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/features/uvm_hotplug.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/features/uvm_hotplug.mdwn	29 Dec 2016 16:54:37 -0000	1.1
+++ wikisrc/features/uvm_hotplug.mdwn	29 Dec 2016 16:59:58 -0000	1.2
@@ -1,65 +1,63 @@
 # [[!template id=man name=uvm_hotplug section=9]] port-masters' FAQ.
 
-1. Why does it matter?
+  1. Why does it matter?
 
-As a port maintainer any architecture that needs to use the virtual memory
-sub-system of NetBSD aka uvm is affected by the
-[[!template id=man name=uvm_hotplug section=9]] change.
+     As a port maintainer any architecture that needs to use the virtual memory
+     sub-system of NetBSD aka uvm is affected by the
+     [[!template id=man name=uvm_hotplug section=9]] change.
 
-Early boot code of every port is affected. Global variables:
-struct vm_physseg vm_physmem;
-int vm_nphysmem;
-are no longer visible. They need to be replaced by appropriate
-accessor calls in [[!template id=man name=uvm_hotplug section=9]]
+     Early boot code of every port is affected. Global variables:
+     struct vm_physseg vm_physmem;
+     int vm_nphysmem;
+     are no longer visible. They need to be replaced by appropriate
+     accessor calls in [[!template id=man name=uvm_hotplug section=9]]
 
-These calls are documented as "Utility Functions" in the
-[[!template id=man name=uvm_hotplug section=9]] manual.
+     These calls are documented as "Utility Functions" in the
+     [[!template id=man name=uvm_hotplug section=9]] manual.
 
+     The "switchover" CVS commit log is here:
+     [http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html](http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html)
 
-The "switchover" CVS commit log is here:
-[http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html](http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html)
+  2. What files may be affected?
 
+     In most of the architectures the "sys/arch/<arch_name>/<arch_name>/machdep.c"
+     and "sys/arch/<arch_name>/<arch_name>/pmap.c" if they exist are usually
+     affected.
 
-2. What files may be affected?
+     But this may not be a exhaustive list. Any other files that deals with pmap and
+     stealing pages might also be affected.
 
-In most of the architectures the "sys/arch/<arch_name>/<arch_name>/machdep.c"
-and "sys/arch/<arch_name>/<arch_name>/pmap.c" if they exist are usually
-affected.
+  3. What does it do ?
 
-But this may not be a exhaustive list. Any other files that deals with pmap and
-stealing pages might also be affected.
+     [[!template id=man name=uvm_hotplug section=9]] manages the previously exposed "vm_physmem" static array which
+     used to keep track of the memory segments.
 
-3. What does it do ?
+     In the current implementation, the array has been replaced with a
+     [[!template id=man name=rbtree section=3]] backing which makes the
+     data structure dynamic.
 
-[[!template id=man name=uvm_hotplug section=9]] manages the previously exposed "vm_physmem" static array which
-used to keep track of the memory segments.
+     An array based implementation is also provided, for backwards
+     compatibility. This is the default implementation and does not provide
+     hot pluggability. It is also used without 'options UVM_HOTPLUG'
+     However the API itself is implementation agnostic.
 
-In the current implementation, the array has been replaced with a
-[[!template id=man name=rbtree section=3]] backing which makes the
-data structure dynamic.
+  4. Why is it needed?
 
-An array based implementation is also provided, for backwards
-compatibility. This is the default implementation and does not provide
-hot pluggability. It is also used without 'options UVM_HOTPLUG'
-However the API itself is implementation agnostic.
+     With the [[!template id=man name=rbtree section=3]] backing
+     implementation, the list of physical pages 
+     in the system is no longer in a static array and can dynamically
+     expand or collapse, hence adding new pages to the freelist from newly
+     available RAM / physical memory (plug) or removing retired pages
+     (unplug) via taking them off the freelist and the old vm_physmem.
 
-4. Why is it needed?
+  5. What should I do?
 
-With the [[!template id=man name=rbtree section=3]] backing
-implementation, the list of physical pages 
-in the system is no longer in a static array and can dynamically
-expand or collapse, hence adding new pages to the freelist from newly
-available RAM / physical memory (plug) or removing retired pages
-(unplug) via taking them off the freelist and the old vm_physmem.
+     Review the changes to your port due to this new feature. The changes
+     may have been made without direct knowledge of your port architecture.
 
-5. What should I do?
+     See if your port has hotpluggable hardware. If it does, write a driver
+     to use the [[!template id=man name=uvm_hotplug section=9]] api.
 
-Review the changes to your port due to this new feature. The changes
-may have been made without direct knowledge of your port architecture.
-
-See if your port has hotpluggable hardware. If it does, write a driver
-to use the [[!template id=man name=uvm_hotplug section=9]] api.
-
-An example of [[!template id=man name=uvm_hotplug section=9]] api's
-application can be found in
-[[!template id=man name=balloon section=4]].
\ No newline at end of file
+     An example of [[!template id=man name=uvm_hotplug section=9]] api's
+     application can be found in
+     [[!template id=man name=balloon section=4]].
\ No newline at end of file

Add an FAQ about uvm_hotplug(9)
Index: wikisrc/features.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/features.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/features.mdwn	2 Apr 2014 06:01:46 -0000	1.2
+++ wikisrc/features.mdwn	29 Dec 2016 16:54:37 -0000	1.3
@@ -8,3 +8,6 @@
 ##Hardware Support
 * [[Video|features/video-hardware]]
 * [[Audio|features/audio-hardware]]
+
+##Memory
+* [[Hotplug|features/uvm_hotplug]]
\ No newline at end of file
--- /dev/null	2016-12-29 16:51:46.000000000 +0000
+++ wikisrc/features/uvm_hotplug.mdwn	2016-12-29 16:54:50.000000000 +0000
@@ -0,0 +1,65 @@
+# [[!template id=man name=uvm_hotplug section=9]] port-masters' FAQ.
+
+1. Why does it matter?
+
+As a port maintainer any architecture that needs to use the virtual memory
+sub-system of NetBSD aka uvm is affected by the
+[[!template id=man name=uvm_hotplug section=9]] change.
+
+Early boot code of every port is affected. Global variables:
+struct vm_physseg vm_physmem;
+int vm_nphysmem;
+are no longer visible. They need to be replaced by appropriate
+accessor calls in [[!template id=man name=uvm_hotplug section=9]]
+
+These calls are documented as "Utility Functions" in the
+[[!template id=man name=uvm_hotplug section=9]] manual.
+
+
+The "switchover" CVS commit log is here:
+[http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html](http://mail-index.netbsd.org/source-changes/2016/12/23/msg080110.html)
+
+
+2. What files may be affected?
+
+In most of the architectures the "sys/arch/<arch_name>/<arch_name>/machdep.c"
+and "sys/arch/<arch_name>/<arch_name>/pmap.c" if they exist are usually
+affected.
+
+But this may not be a exhaustive list. Any other files that deals with pmap and
+stealing pages might also be affected.
+
+3. What does it do ?
+
+[[!template id=man name=uvm_hotplug section=9]] manages the previously exposed "vm_physmem" static array which
+used to keep track of the memory segments.
+
+In the current implementation, the array has been replaced with a
+[[!template id=man name=rbtree section=3]] backing which makes the
+data structure dynamic.
+
+An array based implementation is also provided, for backwards
+compatibility. This is the default implementation and does not provide
+hot pluggability. It is also used without 'options UVM_HOTPLUG'
+However the API itself is implementation agnostic.
+
+4. Why is it needed?
+
+With the [[!template id=man name=rbtree section=3]] backing
+implementation, the list of physical pages 
+in the system is no longer in a static array and can dynamically
+expand or collapse, hence adding new pages to the freelist from newly
+available RAM / physical memory (plug) or removing retired pages
+(unplug) via taking them off the freelist and the old vm_physmem.
+
+5. What should I do?
+
+Review the changes to your port due to this new feature. The changes
+may have been made without direct knowledge of your port architecture.
+
+See if your port has hotpluggable hardware. If it does, write a driver
+to use the [[!template id=man name=uvm_hotplug section=9]] api.
+
+An example of [[!template id=man name=uvm_hotplug section=9]] api's
+application can be found in
+[[!template id=man name=balloon section=4]].

Sync with htdocs/gallery/events.xml (add BSDCan 2017 and AsiaBSDCan 2017)
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/events.mdwn	14 Nov 2016 13:31:18 -0000	1.39
+++ wikisrc/events.mdwn	26 Dec 2016 16:24:57 -0000	1.40
@@ -7,6 +7,30 @@
 
 Future Events
 -------------
+### `Jun 2017` - BSDCAN 2017, Ottawa, Canada
+
+*June 7 - 10, Ottawa, Canada*
+
+BSDCan hosts talks and tutorials on a range of topics based
+around the BSD family of operating systems. The event is held over a
+four day period at the University of Ottawa.
+
+Please see
+[website](https://www.bsdcan.org/2017/)
+for details.
+
+### `Mar 2017` - AsiaBSDCon 2017
+
+*March 9 - 12, Tokyo University of Science, Tokyo, Japan*
+
+[AsiaBSDCon](https://2017.asiabsdcon.org/) is a
+conference for users and developers on BSD based systems.
+The conference is for anyone developing, deploying and using systems
+based on FreeBSD, NetBSD, OpenBSD, DragonFly BSD, Darwin, and MacOS X.
+AsiaBSDCon is a technical conference and aims to collect the best
+technical papers and presentations available to ensure that the latest
+developments in our open source community are shared with the widest
+possible audience.
 
 ### `Feb 2017` - FOSDEM 2017 Brussels, Belgium
 

Advise staying up to date
Mention the 2016-12 ubuntu/46 fix.
Members: 
	ports/xen/howto.mdwn:1.135->1.136 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.135
retrieving revision 1.136
diff -u -r1.135 -r1.136
--- wikisrc/ports/xen/howto.mdwn	21 Dec 2016 16:57:10 -0000	1.135
+++ wikisrc/ports/xen/howto.mdwn	21 Dec 2016 17:03:03 -0000	1.136
@@ -126,7 +126,8 @@
 of 2016-12, security patches were released by Xen and applied to
 pkgsrc.  Xen 4.6 runs on amd64 hardware only For new installations,
 4.6 is probably the appropriate choice and it will likely soon be the
-standard approach.
+standard approach.  (If using Ubuntu guests, be sure to have the
+xentools46 from December, 2016).
 
 Xen 4.7 (released 2016-06) and 4.8 (released 2016-12) are not yet in
 pkgsrc.
@@ -243,6 +244,14 @@
 dom0.  Either the i386PAE or amd64 version of NetBSD may be used as
 domUs.
 
+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.
+
 Status
 ------
 

Adjust architecture section
Add link to "expensive syscalls on amd64" xen-devel message.
Make assorted minor improvements, including explaining how machine
size relates to sum of dom[0U] sizes.
Members: 
	ports/xen/howto.mdwn:1.134->1.135 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.134
retrieving revision 1.135
diff -u -r1.134 -r1.135
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 21:22:57 -0000	1.134
+++ wikisrc/ports/xen/howto.mdwn	21 Dec 2016 16:57:10 -0000	1.135
@@ -150,7 +150,7 @@
 xentools packages provide xm for 3.1, 3.3 and 4.1 and xl for 4.2 and up.
 
 In 4.2, you can choose to use xm by simply changing the ctl_command
-variable.
+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
@@ -197,19 +197,30 @@
 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
-versions 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.)
-
-Because of the above, the standard approach is to use NetBSD/amd64 for
-the dom0 and therefore an amd64 Xen kernel, and to use PAE kernels for
-i386 domUs.
+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.)
+
+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
+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
-an amd64 Xen kernel and install that on the system.  One must also use
-a PAE i386 kernel.  There is no good reason to undertake these
-contortions; you should use a NetBSD/amd64 dom0 system.
+(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.
+
+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.  TODO: Include link to benchmarks, if someone posts them.
 
 Stability
 ---------
@@ -247,7 +258,8 @@
 (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 "FAIL" if it won't boot or run a domU.
+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
@@ -303,7 +315,10 @@
 
 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.
+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.
 
 Styles of dom0 operation
 ------------------------
@@ -390,13 +405,13 @@
 should not use Xen 3.1.)  Both xen and the NetBSD kernel may be (and
 typically are) left compressed.
 
-In a dom0 kernel, kernfs is mandatory for xend to communicate with the
-kernel, so ensure that /kern is in fstab.  TODO: Say this is default,
-or file a PR and give a reference.
+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, /boot present, and likely
+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
@@ -441,13 +456,14 @@
 
 Before NetBSD's native bootloader could support Xen, the use of
 grub was recommended.  If necessary, see the
-[old grub information](/ports/xen/howto-grub/).
+[old grub information](/ports/xen/howto-grub).
 
 The [HowTo on Installing into
 RAID-1](http://mail-index.NetBSD.org/port-xen/2006/03/01/0010.html)
 explains how to set up booting a dom0 with Xen using grub with
 NetBSD's RAIDframe.  (This is obsolete with the use of NetBSD's native
-boot.)
+boot.  Now, just create a system with RAID-1, and alter /boot.cfg as
+described above.)
 
 Configuring Xen
 ---------------

Add missing space. Completely different feeling compared to the usual removals.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.133
retrieving revision 1.134
diff -u -r1.133 -r1.134
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 20:59:49 -0000	1.133
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 21:22:57 -0000	1.134
@@ -190,7 +190,7 @@
 
 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 anamd64 Xen kernel on an amd64 host.  If
+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

Explain xen/dom0 arch better
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.132
retrieving revision 1.133
diff -u -r1.132 -r1.133
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:59:38 -0000	1.132
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 20:59:49 -0000	1.133
@@ -81,6 +81,11 @@
 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 made by
+both Intel and AMD, and in 2016 a normal PC has this CPU
+architecture.)
+
 Xen
 ---
 
@@ -89,38 +94,39 @@
 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 supports i386, both PAE and
-non-PAE.
+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 supports i386, but only in PAE mode.  There are no good
+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 supports
-i386, but only in PAE mode.  There are no good reasons to run this
+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.
 
 xenkernel42 provides Xen 4.2.  It is no longer maintained by Xen, but
-as of 2016-12 received backported security patches.  Xen 4.2 supports
-i386, but only in PAE mode.  The only reason to run this is if you
-need to use xm instead of xl, or if you need to run an i386 dom0
-(because your hardware is i386 only).
+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.  As of 2016-12, security patches were
-released by Xen and applied to pkgsrc.  Xen 4.5 requires using a dom0
-running NetBSD's amd64 port (Intel or AMD hardware is fine), but domUs
-can be amd64 or i386 PAE.  While slightly old, n4.5 has been tested and
-run by others, so it is the conservative choice.
+released by Xen and applied to pkgsrc.  Xen 4.5 runs on amd64 hardware
+only.  While slightly old, 4.5 has been tested and run by others, so
+it is the conservative choice.
 
 xenkernel46 provides Xen 4.6.  It is new to pkgsrc as of 2016-05.  As
 of 2016-12, security patches were released by Xen and applied to
-pkgsrc.  Xen 4.6 similarly requires a NetBSD/amd64 dom0, but domUs can
-be amd64 or i386 PAE.  For new installations, 4.6 is probably the
-appropriate choice and it will likely soon be the standard approach.
+pkgsrc.  Xen 4.6 runs on amd64 hardware only For new installations,
+4.6 is probably the appropriate choice and it will likely soon be the
+standard approach.
 
 Xen 4.7 (released 2016-06) and 4.8 (released 2016-12) are not yet in
 pkgsrc.
@@ -178,30 +184,32 @@
 Architecture
 ------------
 
-Xen itself can run on i386 (Xen < 3.1) or amd64 machines (all Xen
+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 kernel, and each domU kernel can be either i386 or
-amd64.  When building a xenkernel package, one obtains i386 on an i386
-host, and amd64 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 i386PAE dom0
-kernel should in theory work.  An amd64 Xen/dom0 is known to support
-both i386PAE and amd64 domUs.
-
-i386 dom0 and domU kernels must be PAE (except for Xen 3.1); these are
-built by default.  (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.)
-
-Because of the above, the standard approach is to use amd64 for the
-dom0.
-
-Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify
-if this is about the CPU, the Xen kernel, or the dom0 kernel having to
-be 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 anamd64 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 (except for an i386 Xen 3.1
+kernel, where one can use non-PAE for dom0 and all domUs); PAE
+versions 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.)
+
+Because of the above, the standard approach is to use NetBSD/amd64 for
+the dom0 and therefore an amd64 Xen kernel, and to use PAE kernels for
+i386 domUs.
+
+Note that to use an i386 dom0 with Xen 4.5 or higher, one must build
+an amd64 Xen kernel and install that on the system.  One must also use
+a PAE i386 kernel.  There is no good reason to undertake these
+contortions; you should use a NetBSD/amd64 dom0 system.
 
 Stability
 ---------

Resolve which-daemon confusion
There are two issues: 3 vs 4, and xm vs xl. Resolve after discussion
with bouyer@.
Members: 
	ports/xen/howto.mdwn:1.131->1.132 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.131
retrieving revision 1.132
diff -u -r1.131 -r1.132
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:51:53 -0000	1.131
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:59:38 -0000	1.132
@@ -456,18 +456,17 @@
 4.2 and up packages use xl.  To use xm with 4.2, edit xendomains to
 use xm instead.
 
-For "xm", you should enable xend and xenbackendd:
+For 3.1 and 3.3, you should enable xend and xenbackendd:
 
         xend=YES
         xenbackendd=YES
 
-For "xl", you should enable xend and xencommons (xenstored).  Trying
-to use xl without xencommons=YES will result in a hang; it is
-necessary to hit ^C on the console to let the machine finish booting.
-TODO: Check if xend really should be used, and if not why it is
-installed.
+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
+        xend=YES # only if using xm, and only installed <= 4.2
         xencommons=YES
 
 TODO: Recommend for/against xen-watchdog.

Clarify 45/46 recommendation
(Based on bouyer@ input.)
Members: 
	ports/xen/howto.mdwn:1.130->1.131 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.130
retrieving revision 1.131
diff -u -r1.130 -r1.131
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:47:35 -0000	1.130
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:51:53 -0000	1.131
@@ -113,14 +113,14 @@
 xenkernel45 provides Xen 4.5.  As of 2016-12, security patches were
 released by Xen and applied to pkgsrc.  Xen 4.5 requires using a dom0
 running NetBSD's amd64 port (Intel or AMD hardware is fine), but domUs
-can be amd64 or i386 PAE.  TODO: It is either a conservative choice or
-somewhat old.
+can be amd64 or i386 PAE.  While slightly old, n4.5 has been tested and
+run by others, so it is the conservative choice.
 
 xenkernel46 provides Xen 4.6.  It is new to pkgsrc as of 2016-05.  As
 of 2016-12, security patches were released by Xen and applied to
 pkgsrc.  Xen 4.6 similarly requires a NetBSD/amd64 dom0, but domUs can
-be amd64 or i386 PAE.  TODO: It is either a somewhat aggressive choice
-or the standard choice.
+be amd64 or i386 PAE.  For new installations, 4.6 is probably the
+appropriate choice and it will likely soon be the standard approach.
 
 Xen 4.7 (released 2016-06) and 4.8 (released 2016-12) are not yet in
 pkgsrc.

Tone down xl/parallel fear
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.129
retrieving revision 1.130
diff -u -r1.129 -r1.130
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:37:13 -0000	1.129
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:47:35 -0000	1.130
@@ -148,10 +148,11 @@
 
 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 xl startup, but as of 201612 it has not been
-adequately tested.
+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
 ------

update hardware
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.128
retrieving revision 1.129
diff -u -r1.128 -r1.129
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:31:46 -0000	1.128
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:37:13 -0000	1.129
@@ -604,10 +604,10 @@
 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/RAM
-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.
+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
@@ -616,6 +616,8 @@
 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
 ----------------------

Add more xentools3* data on netbsd-6 i386
(Yes, I realize this doesn't really matter, but I am cleaning up old
data.)
Members: 
	ports/xen/howto.mdwn:1.127->1.128 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.127
retrieving revision 1.128
diff -u -r1.127 -r1.128
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:25:35 -0000	1.127
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:31:46 -0000	1.128
@@ -245,8 +245,7 @@
 	xenkernel41 netbsd-6 i386 builds 201612
 	xenkernel42 netbsd-6 i386 builds 201612
 	xentools3 netbsd-6 i386 FAIL 201612
-	xentools3-hvm netbsd-6 i386 FAIL 201412
-	xentools33 netbsd-6 i386 builds 201412
+	xentools33 netbsd-6 i386 FAIL 201612
 	xentools41 netbsd-6 i386 builds 201612
 	xentools42 netbsd-6 i386 FAIL 201612
 
@@ -456,7 +455,6 @@
 4.2 and up packages use xl.  To use xm with 4.2, edit xendomains to
 use xm instead.
 
-
 For "xm", you should enable xend and xenbackendd:
 
         xend=YES

Update xm/xl info
Also, explain /dev file creattion better.
Members: 
	ports/xen/howto.mdwn:1.126->1.127 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.126
retrieving revision 1.127
diff -u -r1.126 -r1.127
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 18:53:23 -0000	1.126
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 19:25:35 -0000	1.127
@@ -136,11 +136,22 @@
 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
-choose one or the other, because it affects which daemons you run.
-However, the rc.d scripts provided by xentools packages expect a
-particular version, and you should use the version used by the
-scripts.
+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 xm for 3.1, 3.3 and 4.1 and xl for 4.2 and up.
+
+In 4.2, you can choose to use xm by simply changing the ctl_command
+variable.
+
+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 xl startup, but as of 201612 it has not been
+adequately tested.
 
 NetBSD
 ------
@@ -349,9 +360,11 @@
 -------------------
 
 In the dom0, install sysutils/xenkernel42 and sysutils/xentools42 from
-pkgsrc (or another matching pair).
-See [the pkgsrc
-documentation](http://www.NetBSD.org/docs/pkgsrc/) for help with pkgsrc.
+pkgsrc (or another matching pair).  See [the pkgsrc
+documentation](http://www.NetBSD.org/docs/pkgsrc/) for help with
+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
@@ -403,8 +416,14 @@
 necessary.
 
 As with non-Xen systems, you should have a line to boot /netbsd (a
-kernel that works without Xen) and fallback versions of the non-Xen
-kernel, Xen, and the dom0 kernel.
+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.
+
+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.
@@ -433,30 +452,25 @@
 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 and 3.3 packages use xm.  Xen 4.1
-and higher packages use xl.  While is is possible to use xm with some
-4.x versions (TODO: 4.1 and 4.2?), the pkgsrc-provided rc.d scripts do
-not support this as of 2014-12-26, and thus the HOWTO does not support
-it either.  (Make sure your packages are reasonably recent.)
+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 "xm" (3.1 and 3.3), you should enable xend and xenbackendd (but
-note that you should be using 4.x):
+For "xm", you should enable xend and xenbackendd:
 
         xend=YES
         xenbackendd=YES
 
-For "xl" (4.x), you should enabled xend and xencommons (xenstored).
-Trying to boot 4.x without xencommons=YES will result in a hang; it is
+For "xl", you should enable xend and xencommons (xenstored).  Trying
+to use xl without xencommons=YES will result in a hang; it is
 necessary to hit ^C on the console to let the machine finish booting.
-TODO: explain why xend is installed by the package.
+TODO: Check if xend really should be used, and if not why it is
+installed.
 
+        xend=YES
         xencommons=YES
 
-The installation of NetBSD should already have created devices for xen
-(xencons, xenevt), but if they are not present, create them:
-
-        cd /dev && sh MAKEDEV xen
-
 TODO: Recommend for/against xen-watchdog.
 
 After you have configured the daemons and either started them (in the
@@ -483,6 +497,13 @@
 (and thus xencommons).  There is currently no reason to expect that
 this will get fixed any time soon.
 
+### No-longer needed advice about devices
+
+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
+
 anita (for testing NetBSD)
 --------------------------
 
@@ -730,10 +751,10 @@
 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.  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
+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
 
@@ -767,6 +788,13 @@
 The third element is "w" for writable disks, and "r" for read-only
 disks.
 
+Note that NetBSD by default creates only vnd[0123].  If you need more
+than 4 total virtual disks at a time, run e.g. "./MAKEDEV vnd4" in the
+dom0.
+
+Note that NetBSD by default creates only xbd[0123].  If you need more
+virtual disks in a domU, run e.g. "./MAKEDEV xbd4" in the domU.
+
 Virtual Networking
 ------------------
 

Add more build info
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.125
retrieving revision 1.126
diff -u -r1.125 -r1.126
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 18:26:11 -0000	1.125
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 18:53:23 -0000	1.126
@@ -233,11 +233,11 @@
 	xenkernel33 netbsd-6 i386 FAIL 201612
 	xenkernel41 netbsd-6 i386 builds 201612
 	xenkernel42 netbsd-6 i386 builds 201612
-	xentools3 netbsd-6 i386 builds 201412
+	xentools3 netbsd-6 i386 FAIL 201612
 	xentools3-hvm netbsd-6 i386 FAIL 201412
 	xentools33 netbsd-6 i386 builds 201412
 	xentools41 netbsd-6 i386 builds 201612
-	xentools42 netbsd-6 i386 ? 201412
+	xentools42 netbsd-6 i386 FAIL 201612
 
 	xenkernel3 netbsd-7 i386 FAIL 201412
 	xenkernel33 netbsd-7 i386 FAIL 201412
@@ -249,7 +249,7 @@
 	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
+	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

Rototill build section again
Add a notation if what builds actually works. (It's not clear if this
is really useful; perhaps it is just a public note-to-self.)
Members: 
	ports/xen/howto.mdwn:1.124->1.125 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.124
retrieving revision 1.125
diff -u -r1.124 -r1.125
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 17:48:53 -0000	1.124
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 18:26:11 -0000	1.125
@@ -212,58 +212,64 @@
 dom0.  Either the i386PAE or amd64 version of NetBSD may be used as
 domUs.
 
-Build problems
---------------
+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 and up for i386.  The following are known to be ok or FAIL, with
-the date last checked (generally on the most recent quarterly branch):
+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 "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 ok 201612
-	xenkernel42 netbsd-6 i386 ok 201612
-	xentools3 netbsd-6 i386 ok 201412
+	xenkernel41 netbsd-6 i386 builds 201612
+	xenkernel42 netbsd-6 i386 builds 201612
+	xentools3 netbsd-6 i386 builds 201412
 	xentools3-hvm netbsd-6 i386 FAIL 201412
-	xentools33 netbsd-6 i386 ok 201412
-	xentools41 netbsd-6 i386 ok 201412
-	xentools42 netbsd-6 i386 mixed 201412
+	xentools33 netbsd-6 i386 builds 201412
+	xentools41 netbsd-6 i386 builds 201612
+	xentools42 netbsd-6 i386 ? 201412
 
 	xenkernel3 netbsd-7 i386 FAIL 201412
 	xenkernel33 netbsd-7 i386 FAIL 201412
-	xenkernel41 netbsd-7 i386 ok 201412
-	xenkernel42 netbsd-7 i386 ok 201412
-	xentools41 netbsd-7 i386 ok 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 ok 201612
-	xenkernel42 netbsd-6 amd64 ok 201612
-	xenkernel45 netbsd-6 amd64 ok 201612
-	xenkernel46 netbsd-6 amd64 ok 201612
-	xentools41 netbsd-6 amd64 ok 201612
-	xentools42 netbsd-6 amd64 ok 201612
-	xentools45 netbsd-6 amd64 ok 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 ok 201612
-	xenkernel33 netbsd-7 amd64 ok 201612
-	xenkernel41 netbsd-7 amd64 ok 201612
-	xenkernel42 netbsd-7 amd64 ok 201612
-	xenkernel45 netbsd-7 amd64 ok 201612
-	xenkernel46 netbsd-7 amd64 ok 201612
-	xentools3 netbsd-7 amd64 ok 201612
-	xentools3-hvm netbsd-7 amd64 ok 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 ok 201612
-	xentools42 netbsd-7 amd64 ok 201612
-	xentools45 netbsd-7 amd64 ok 201612
-	xentools46 netbsd-7 amd64 ok 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
 ================

Update build list
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.123
retrieving revision 1.124
diff -u -r1.123 -r1.124
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:53:40 -0000	1.123
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 17:48:53 -0000	1.124
@@ -219,31 +219,37 @@
 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.  The following are known to be ok or FAIL, with
-the date last checked:
-
-	xenkernel3 netbsd-6 i386 FAIL 201412
-	xenkernel33 netbsd-6 i386 ok 201412
-	xenkernel41 netbsd-6 i386 ok 201412
-	xenkernel42 netbsd-6 i386 ok 201412
+is difficult to build.  Note that there is intentionally no data for
+4.5 and up for i386.  The following are known to be ok or FAIL, with
+the date last checked (generally on the most recent quarterly branch):
+
+	xenkernel3 netbsd-6 i386 FAIL 201612
+	xenkernel33 netbsd-6 i386 FAIL 201612
+	xenkernel41 netbsd-6 i386 ok 201612
+	xenkernel42 netbsd-6 i386 ok 201612
 	xentools3 netbsd-6 i386 ok 201412
 	xentools3-hvm netbsd-6 i386 FAIL 201412
 	xentools33 netbsd-6 i386 ok 201412
 	xentools41 netbsd-6 i386 ok 201412
 	xentools42 netbsd-6 i386 mixed 201412
 
-	(all 3 and 33 seem to FAIL)
+	xenkernel3 netbsd-7 i386 FAIL 201412
+	xenkernel33 netbsd-7 i386 FAIL 201412
 	xenkernel41 netbsd-7 i386 ok 201412
 	xenkernel42 netbsd-7 i386 ok 201412
 	xentools41 netbsd-7 i386 ok 201412
 	xentools42 netbsd-7 i386 ??FAIL 201412
 
-	xenkernel33 netbsd-6 amd64 ok 201612
+	xenkernel3 netbsd-6 amd64 FAIL 201612
+	xenkernel33 netbsd-6 amd64 FAIL 201612
+	xenkernel41 netbsd-6 amd64 ok 201612
 	xenkernel42 netbsd-6 amd64 ok 201612
 	xenkernel45 netbsd-6 amd64 ok 201612
 	xenkernel46 netbsd-6 amd64 ok 201612
+	xentools41 netbsd-6 amd64 ok 201612
 	xentools42 netbsd-6 amd64 ok 201612
 	xentools45 netbsd-6 amd64 ok 201612
+	xentools46 netbsd-6 amd64 FAIL 201612
 
 	xenkernel3 netbsd-7 amd64 ok 201612
 	xenkernel33 netbsd-7 amd64 ok 201612

Clarify "amd64" in more places
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.122
retrieving revision 1.123
diff -u -r1.122 -r1.123
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:32:10 -0000	1.122
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:53:40 -0000	1.123
@@ -27,19 +27,19 @@
 Attempts to access hardware registers are trapped and emulated.  This
 style is less efficient but can run unmodified guests.
 
-Generally any amd64 machine will work with Xen and PV guests.  In
-theory i386 computers without 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.
+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 a FreeBSD dom0 requires VT-x and VT-d (or equivalent); this is
-because the FreeBSD dom0 does not run in PV mode.
+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.
 
 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
@@ -51,7 +51,7 @@
 and running domUs under it (NetBSD and other), and also running NetBSD
 as a domU in a VPS.
 
-Some versions of Xen support "PCI passthrough", which means that
+Xen 3.1 in pkgsrc supports "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.
@@ -69,9 +69,9 @@
 path when there are no known good reasons to stray.
 
 This HOWTO presumes a basic familiarity with the Xen system
-architecture.  This HOWTO presumes familiarity with installing NetBSD
-on i386/amd64 hardware and installing software from pkgsrc.
-See also the [Xen website](http://www.xenproject.org/).
+architecture, with installing NetBSD on i386/amd64 hardware, and with
+installing software from pkgsrc.  See also the [Xen
+website](http://www.xenproject.org/).
 
 Versions of Xen and NetBSD
 ==========================

Tabify build list
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.121
retrieving revision 1.122
diff -u -r1.121 -r1.122
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:30:32 -0000	1.121
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:32:10 -0000	1.122
@@ -222,21 +222,21 @@
 is difficult to build.  The following are known to be ok or FAIL, with
 the date last checked:
 
-        xenkernel3 netbsd-6 i386 FAIL 201412
-        xenkernel33 netbsd-6 i386 ok 201412
-        xenkernel41 netbsd-6 i386 ok 201412
-        xenkernel42 netbsd-6 i386 ok 201412
-        xentools3 netbsd-6 i386 ok 201412
-        xentools3-hvm netbsd-6 i386 FAIL 201412
-        xentools33 netbsd-6 i386 ok 201412
-        xentools41 netbsd-6 i386 ok 201412
-        xentools42 netbsd-6 i386 mixed 201412
+	xenkernel3 netbsd-6 i386 FAIL 201412
+	xenkernel33 netbsd-6 i386 ok 201412
+	xenkernel41 netbsd-6 i386 ok 201412
+	xenkernel42 netbsd-6 i386 ok 201412
+	xentools3 netbsd-6 i386 ok 201412
+	xentools3-hvm netbsd-6 i386 FAIL 201412
+	xentools33 netbsd-6 i386 ok 201412
+	xentools41 netbsd-6 i386 ok 201412
+	xentools42 netbsd-6 i386 mixed 201412
 
 	(all 3 and 33 seem to FAIL)
-        xenkernel41 netbsd-7 i386 ok 201412
-        xenkernel42 netbsd-7 i386 ok 201412
-        xentools41 netbsd-7 i386 ok 201412
-        xentools42 netbsd-7 i386 ??FAIL 201412
+	xenkernel41 netbsd-7 i386 ok 201412
+	xenkernel42 netbsd-7 i386 ok 201412
+	xentools41 netbsd-7 i386 ok 201412
+	xentools42 netbsd-7 i386 ??FAIL 201412
 
 	xenkernel33 netbsd-6 amd64 ok 201612
 	xenkernel42 netbsd-6 amd64 ok 201612

Rototill build problems section
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.120
retrieving revision 1.121
diff -u -r1.120 -r1.121
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:21:21 -0000	1.120
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:30:32 -0000	1.121
@@ -216,26 +216,48 @@
 --------------
 
 Ideally, all versions of Xen in pkgsrc would build on all supported
-versions of NetBSD/amd64.  However, that isn't always the case.
-Besides aging code and aging compilers, qemu (included in xentools for
-HVM support) is difficult to build.  The following are known to be ok
-or FAIL, with the date last checked.:
-
-        xenkernel3 netbsd-6 i386 FAIL
-        xentools3 netbsd-6 i386
-        xentools3-hvm netbsd-6 i386 FAIL (dependencies fail)
-        xenkernel33 netbsd-6 i386
-        xentools33 netbsd-6 i386
-        xenkernel41 netbsd-6 i386
-        xentools41 netbsd-6 i386
-        xenkernel42 netbsd-6 i386
-        xentools42 netbsd-6 i386 *MIXED
+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.  The following are known to be ok or FAIL, with
+the date last checked:
+
+        xenkernel3 netbsd-6 i386 FAIL 201412
+        xenkernel33 netbsd-6 i386 ok 201412
+        xenkernel41 netbsd-6 i386 ok 201412
+        xenkernel42 netbsd-6 i386 ok 201412
+        xentools3 netbsd-6 i386 ok 201412
+        xentools3-hvm netbsd-6 i386 FAIL 201412
+        xentools33 netbsd-6 i386 ok 201412
+        xentools41 netbsd-6 i386 ok 201412
+        xentools42 netbsd-6 i386 mixed 201412
 
 	(all 3 and 33 seem to FAIL)
-        xenkernel41 netbsd-7 i386
-        xentools41 netbsd-7 i386
-        xenkernel42 netbsd-7 i386
-        xentools42 netbsd-7 i386 ??FAIL
+        xenkernel41 netbsd-7 i386 ok 201412
+        xenkernel42 netbsd-7 i386 ok 201412
+        xentools41 netbsd-7 i386 ok 201412
+        xentools42 netbsd-7 i386 ??FAIL 201412
+
+	xenkernel33 netbsd-6 amd64 ok 201612
+	xenkernel42 netbsd-6 amd64 ok 201612
+	xenkernel45 netbsd-6 amd64 ok 201612
+	xenkernel46 netbsd-6 amd64 ok 201612
+	xentools42 netbsd-6 amd64 ok 201612
+	xentools45 netbsd-6 amd64 ok 201612
+
+	xenkernel3 netbsd-7 amd64 ok 201612
+	xenkernel33 netbsd-7 amd64 ok 201612
+	xenkernel41 netbsd-7 amd64 ok 201612
+	xenkernel42 netbsd-7 amd64 ok 201612
+	xenkernel45 netbsd-7 amd64 ok 201612
+	xenkernel46 netbsd-7 amd64 ok 201612
+	xentools3 netbsd-7 amd64 ok 201612
+	xentools3-hvm netbsd-7 amd64 ok 201612
+	xentools33 netbsd-7 amd64 FAIL 201612
+	xentools41 netbsd-7 amd64 ok 201612
+	xentools42 netbsd-7 amd64 ok 201612
+	xentools45 netbsd-7 amd64 ok 201612
+	xentools46 netbsd-7 amd64 ok 201612
 
 NetBSD as a dom0
 ================

Drop netbsd-5 build info
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.119
retrieving revision 1.120
diff -u -r1.119 -r1.120
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:06:08 -0000	1.119
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:21:21 -0000	1.120
@@ -215,20 +215,11 @@
 Build problems
 --------------
 
-Ideally, all versions of Xen in pkgsrc would build on all versions of
-NetBSD on both i386 and amd64.  However, that isn't the case.  Besides
-aging code and aging compilers, qemu (included in xentools for HVM
-support) is difficult to build.  The following are known to work or FAIL:
-
-        xenkernel3 netbsd-5 amd64
-        xentools3 netbsd-5 amd64
-        xentools3=hvm netbsd-5 amd64 ????
-        xenkernel33 netbsd-5 amd64
-        xentools33 netbsd-5 amd64
-        xenkernel41 netbsd-5 amd64
-        xentools41 netbsd-5 amd64
-        xenkernel42 netbsd-5 amd64
-        xentools42 netbsd-5 amd64
+Ideally, all versions of Xen in pkgsrc would build on all supported
+versions of NetBSD/amd64.  However, that isn't always the case.
+Besides aging code and aging compilers, qemu (included in xentools for
+HVM support) is difficult to build.  The following are known to be ok
+or FAIL, with the date last checked.:
 
         xenkernel3 netbsd-6 i386 FAIL
         xentools3 netbsd-6 i386
@@ -246,9 +237,6 @@
         xenkernel42 netbsd-7 i386
         xentools42 netbsd-7 i386 ??FAIL
 
-(*On netbsd-6 i386, there is a xentools42 in the 2014Q3 official builds,
-but it does not build for gdt.)
-
 NetBSD as a dom0
 ================
 

Clarify that "amd64 dom0" is about NetBSD version, not brand
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.118
retrieving revision 1.119
diff -u -r1.118 -r1.119
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 15:07:56 -0000	1.118
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 16:06:08 -0000	1.119
@@ -111,15 +111,16 @@
 (because your hardware is i386 only).
 
 xenkernel45 provides Xen 4.5.  As of 2016-12, security patches were
-released by Xen and applied to pkgsrc.  Xen 4.5 requires an amd64
-dom0, but domUs can be amd64 or i386 PAE.  TODO: It is either a
-conservative choice or somewhat old.
+released by Xen and applied to pkgsrc.  Xen 4.5 requires using a dom0
+running NetBSD's amd64 port (Intel or AMD hardware is fine), but domUs
+can be amd64 or i386 PAE.  TODO: It is either a conservative choice or
+somewhat old.
 
 xenkernel46 provides Xen 4.6.  It is new to pkgsrc as of 2016-05.  As
 of 2016-12, security patches were released by Xen and applied to
-pkgsrc.  Xen 4.6 requires an amd64 dom0, but domUs can be amd64 or
-i386 PAE.  TODO: It is either a somewhat aggressive choice or the
-standard choice
+pkgsrc.  Xen 4.6 similarly requires a NetBSD/amd64 dom0, but domUs can
+be amd64 or i386 PAE.  TODO: It is either a somewhat aggressive choice
+or the standard choice.
 
 Xen 4.7 (released 2016-06) and 4.8 (released 2016-12) are not yet in
 pkgsrc.

Explain that FreeBSD needing VT-x does not apply
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -r1.117 -r1.118
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 15:05:36 -0000	1.117
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 15:07:56 -0000	1.118
@@ -38,6 +38,9 @@
 TODO: Explain whether Xen on NetBSD makes use of these features.
 TODO: Review by someone who really understands this.
 
+Note a FreeBSD dom0 requires VT-x and VT-d (or equivalent); this is
+because the FreeBSD dom0 does not run in PV mode.
+
 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.)

Recommend recent netbsd-7
Add link to 2015-11 pullup of scheduler fix.
Add link to another HOWTO.
Members: 
	ports/xen/howto.mdwn:1.116->1.117 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.116
retrieving revision 1.117
diff -u -r1.116 -r1.117
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 14:52:43 -0000	1.116
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 15:05:36 -0000	1.117
@@ -144,10 +144,15 @@
 The netbsd-6, netbsd-7, 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.  For those wanting to learn Xen or
-without production stability concerns, netbsd-7 is still likely most
-appropriate, but -current is also a reasonable choice.  Xen runs fine
-on netbsd-5, but the xentools packages are likely difficult to build.
+recent release for production use.  In addition, netbsd-7 and -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 those wanting to learn Xen or without production
+stability concerns, netbsd-7 is still likely most appropriate, but
+-current is also a reasonable choice.  (Xen runs ok on netbsd-5, but
+the xentools packages are likely difficult to build, and netbsd-5 is
+not supported.)
 
 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
@@ -1097,8 +1102,9 @@
 Random pointers
 ===============
 
-TODO: This section contains links from elsewhere not yet integrated
-into the HOWTO.
+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

Update HW support for HVM section
(From bouyer@ on port-xen.0
Members: 
	ports/xen/howto.mdwn:1.115->1.116 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.115
retrieving revision 1.116
diff -u -r1.115 -r1.116
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 13:16:43 -0000	1.115
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 14:52:43 -0000	1.116
@@ -30,9 +30,13 @@
 Generally any amd64 machine will work with Xen and PV guests.  In
 theory i386 computers without 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, the VT or VMX CPU feature (Intel) or SVM/HVM/VT
-(amd64) is needed; "cpuctl identify 0" will show this.  TODO: Clean up
-and check the above features.
+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.
 
 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

Fix confusing typo in Xen version
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.114
retrieving revision 1.115
diff -u -r1.114 -r1.115
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 13:15:37 -0000	1.114
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 13:16:43 -0000	1.115
@@ -108,7 +108,7 @@
 dom0, but domUs can be amd64 or i386 PAE.  TODO: It is either a
 conservative choice or somewhat old.
 
-xenkernel45 provides Xen 4.6.  It is new to pkgsrc as of 2016-05.  As
+xenkernel46 provides Xen 4.6.  It is new to pkgsrc as of 2016-05.  As
 of 2016-12, security patches were released by Xen and applied to
 pkgsrc.  Xen 4.6 requires an amd64 dom0, but domUs can be amd64 or
 i386 PAE.  TODO: It is either a somewhat aggressive choice or the

Update supported Xen versions
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.113
retrieving revision 1.114
diff -u -r1.113 -r1.114
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 13:09:58 -0000	1.113
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 13:15:37 -0000	1.114
@@ -103,18 +103,19 @@
 need to use xm instead of xl, or if you need to run an i386 dom0
 (because your hardware is i386 only).
 
-xenkernel45 provides Xen 4.5.  It is no longer maintained by Xen, but
-as of 2016-12 it received security patches.  Xen 4.5 requires an amd64
+xenkernel45 provides Xen 4.5.  As of 2016-12, security patches were
+released by Xen and applied to pkgsrc.  Xen 4.5 requires an amd64
 dom0, but domUs can be amd64 or i386 PAE.  TODO: It is either a
 conservative choice or somewhat old.
 
-xenkernel45 provides Xen 4.6.  It is new to pkgsrc in 2016-05.  It is
-no longer maintained by Xen, but as of 2016-12 it received security
-patches.  Xen 4.6 requires an amd64 dom0, but domUs can be amd64 or
+xenkernel45 provides Xen 4.6.  It is new to pkgsrc as of 2016-05.  As
+of 2016-12, security patches were released by Xen and applied to
+pkgsrc.  Xen 4.6 requires an amd64 dom0, but domUs can be amd64 or
 i386 PAE.  TODO: It is either a somewhat aggressive choice or the
 standard choice
 
-Xen 4.7 and 4.8 are not in pkgsrc.
+Xen 4.7 (released 2016-06) and 4.8 (released 2016-12) are not yet in
+pkgsrc.
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 

Note versions not in pkgsrc
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.112
retrieving revision 1.113
diff -u -r1.112 -r1.113
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 12:53:06 -0000	1.112
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 13:09:58 -0000	1.113
@@ -114,9 +114,9 @@
 i386 PAE.  TODO: It is either a somewhat aggressive choice or the
 standard choice
 
-See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
+Xen 4.7 and 4.8 are not in pkgsrc.
 
-Ideally newer versions of Xen will be added to pkgsrc.
+See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 
 Note that NetBSD support is called XEN3.  It works with Xen 3 and Xen
 4 because the hypercall interface has been stable.

Note 41/42/45/46 patch date.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.111
retrieving revision 1.112
diff -u -r1.111 -r1.112
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 08:18:01 -0000	1.111
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 12:53:06 -0000	1.112
@@ -93,23 +93,23 @@
 reasons to run this version.
 
 xenkernel41 provides Xen 4.1.  It is no longer maintained by Xen, but
-as of 2016-11 received backported security patches.  Xen 4.1 supports
+as of 2016-12 received backported security patches.  Xen 4.1 supports
 i386, but only in PAE mode.  There are no good reasons to run this
 version.
 
 xenkernel42 provides Xen 4.2.  It is no longer maintained by Xen, but
-as of 2016-11 received backported security patches.  Xen 4.2 supports
+as of 2016-12 received backported security patches.  Xen 4.2 supports
 i386, but only in PAE mode.  The only reason to run this is if you
 need to use xm instead of xl, or if you need to run an i386 dom0
 (because your hardware is i386 only).
 
 xenkernel45 provides Xen 4.5.  It is no longer maintained by Xen, but
-as of 2016-11 it received security patches.  Xen 4.5 requires an amd64
+as of 2016-12 it received security patches.  Xen 4.5 requires an amd64
 dom0, but domUs can be amd64 or i386 PAE.  TODO: It is either a
 conservative choice or somewhat old.
 
 xenkernel45 provides Xen 4.6.  It is new to pkgsrc in 2016-05.  It is
-no longer maintained by Xen, but as of 2016-11 it received security
+no longer maintained by Xen, but as of 2016-12 it received security
 patches.  Xen 4.6 requires an amd64 dom0, but domUs can be amd64 or
 i386 PAE.  TODO: It is either a somewhat aggressive choice or the
 standard choice

Spelling/capitalization fixes.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.110
retrieving revision 1.111
diff -u -r1.110 -r1.111
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:09:54 -0000	1.110
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 08:18:01 -0000	1.111
@@ -30,7 +30,7 @@
 Generally any amd64 machine will work with Xen and PV guests.  In
 theory i386 computers without 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, the VT or VMX cpu feature (Intel) or SVM/HVM/VT
+For HVM guests, the VT or VMX CPU feature (Intel) or SVM/HVM/VT
 (amd64) is needed; "cpuctl identify 0" will show this.  TODO: Clean up
 and check the above features.
 
@@ -49,7 +49,7 @@
 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 fro NetBSD
+NetBSD 6 and earlier supported Xen 2; support was removed from NetBSD
 7.  Xen 2 has been removed from pkgsrc.
 
 Prerequisites
@@ -77,7 +77,7 @@
 Xen
 ---
 
-In NetBSD, xen is provided in pkgsrc, via matching pairs of packages
+In NetBSD, Xen is provided in pkgsrc, via matching pairs of packages
 xenkernel and xentools.  We will refer only to the kernel versions,
 but note that both packages must be installed together and must have
 matching versions.
@@ -158,10 +158,10 @@
 
 Xen, the dom0 kernel, and each domU kernel can be either i386 or
 amd64.  When building a xenkernel package, one obtains i386 on an i386
-host, and amd64 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
+host, and amd64 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 i386PAE dom0
-kernel should in theory work.  An amd64 xen/dom0 is known to support
+kernel should in theory work.  An amd64 Xen/dom0 is known to support
 both i386PAE and amd64 domUs.
 
 i386 dom0 and domU kernels must be PAE (except for Xen 3.1); these are
@@ -173,7 +173,7 @@
 dom0.
 
 Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify
-if this is about the CPU, the xen kernel, or the dom0 kernel having to
+if this is about the CPU, the Xen kernel, or the dom0 kernel having to
 be amd64.
 
 
@@ -284,7 +284,7 @@
 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 filesystem within a RAID
+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
@@ -300,7 +300,7 @@
 and more flexible.  Hence raw disk partitions should typically not
 be used.
 
-One can use files in the dom0 filesystem, typically created by dd'ing
+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.
@@ -333,13 +333,13 @@
 should not use Xen 3.1.)  Both xen and the NetBSD kernel may be (and
 typically are) left compressed.
 
-In a dom0 kernel, kernfs is mandatory for xend to comunicate with the
+In a dom0 kernel, kernfs is mandatory for xend to communicate with the
 kernel, so ensure that /kern is in fstab.  TODO: Say this is default,
 or file a PR and give a reference.
 
 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 filesystem, /boot present, and likely
+beginning of your root file system, /boot present, and likely
 /boot.cfg.  (If not, fix before continuing!)
 
 Add a line to to /boot.cfg to boot Xen.  See boot.cfg(5) for an
@@ -359,11 +359,11 @@
         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.
+more) and to pin that vcpu to a physical CPU.  TODO: benchmark this.
 
 Xen has [many boot
 options](http://xenbits.xenproject.org/docs/4.5-testing/misc/xen-command-line.html),
-and other tham dom0 memory and max_vcpus, they are generally not
+and other than dom0 memory and max_vcpus, they are generally not
 necessary.
 
 As with non-Xen systems, you should have a line to boot /netbsd (a
@@ -411,7 +411,7 @@
 
 For "xl" (4.x), you should enabled xend and xencommons (xenstored).
 Trying to boot 4.x without xencommons=YES will result in a hang; it is
-necessary to hig ^C on the console to let the machine finish booting.
+necessary to hit ^C on the console to let the machine finish booting.
 TODO: explain why xend is installed by the package.
 
         xencommons=YES
@@ -465,7 +465,7 @@
 There are (at least) two additional things different about NetBSD as a
 dom0 kernel compared to hardware.
 
-One is that the module ABI is different because some of the #ddefines
+One is that the module ABI is different because some of the #defines
 change, so one must build modules for Xen.  As of netbsd-7, the build
 system does this automatically.  TODO: check this.  (Before building
 Xen modules was added, it was awkward to use modules to the point
@@ -497,7 +497,7 @@
 4.1 and grub, much like the message linked earlier in the grub
 section.
 
-        # Install mbr bootblocks on both disks. 
+        # Install MBR bootblocks on both disks. 
         fdisk -i /dev/rwd0d
         fdisk -i /dev/rwd1d
         # Install NetBSD primary boot loader (/ is FFSv1) into RAID1 components.
@@ -505,7 +505,7 @@
         installboot -v /dev/rwd1d /usr/mdec/bootxx_ffsv1
         # Install secondary boot loader
         cp -p /usr/mdec/boot /
-        # Create boog.cfg following earlier guidance:
+        # Create boot.cfg following earlier guidance:
         menu=Xen:load /netbsd-XEN3PAE_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=256M
         menu=Xen.ok:load /netbsd-XEN3PAE_DOM0.ok.gz console=pc;multiboot /xen.ok.gz dom0_mem=256M
         menu=GENERIC:boot
@@ -590,7 +590,7 @@
 typically named so that the file name, domU name and the domU's host
 name match.
 
-The domU is provided with cpu and memory by Xen, configured by the
+The domU is provided with CPU and memory by Xen, configured by the
 dom0.  The domU is provided with disk and network by the dom0,
 mediated by Xen, and configured in the dom0.
 
@@ -627,7 +627,7 @@
 with a specific mac address (do not reuse MAC addresses!), in bridge
 mode.  Two disks are provided, and they are both writable; the bits
 are stored in files and Xen attaches them to a vnd(4) device in the
-dom0 on domain creation.  The system treates xbd0 as the boot device
+dom0 on domain creation.  The system treats xbd0 as the boot device
 without needing explicit configuration.
 
 By default xm looks for domain config files in /usr/pkg/etc/xen.  Note
@@ -653,9 +653,9 @@
 
 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
-filesystem.  With Xen domUs, the process is totally different.  The
+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
-filesystem.  At the request of the dom0, Xen loads that kernel into a
+file system.  At the request of the dom0, Xen loads that kernel into a
 new domU instance and starts execution.  While domU kernels can be
 anyplace, reasonable places to store domU kernels on the dom0 are in /
 (so they are near the dom0 kernel), in /usr/pkg/etc/xen (near the
@@ -670,7 +670,7 @@
 --------------
 
 A domain is provided with some number of vcpus, less than the number
-of cpus seen by the hypervisor.  (For a dom0, this is controlled by
+of CPUs seen by the hypervisor.  (For a dom0, this is controlled by
 the boot argument "dom0_max_vcpus=1".)  For a domU, it is controlled
 from the config file by the "vcpus = N" directive.
 
@@ -734,11 +734,11 @@
 Virtual Networking
 ------------------
 
-Xen provides virtual ethernets, each of which connects the dom0 and a
+Xen provides virtual Ethernets, each of which connects the dom0 and a
 domU.  For each virtual network, there is an interface "xvifN.M" in
 the dom0, and in domU index N, a matching interface xennetM (NetBSD
 name).  The interfaces behave as if there is an Ethernet with two
-adaptors connected.  From this primitive, one can construct various
+adapters connected.  From this primitive, one can construct various
 configurations.  We focus on two common and useful cases for which
 there are existing scripts: bridging and NAT.
 
@@ -782,8 +782,8 @@
 
         xendomains="foo bar"
 
-Note that earlier versions of the xentools41 xendomains rc.d scripth

(Diff truncated)
Enhance xen upgrade section
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -r1.109 -r1.110
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:07:39 -0000	1.109
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:09:54 -0000	1.110
@@ -521,10 +521,15 @@
 Upgrading Xen versions
 ---------------------
 
-Updating Xen is conceptually not difficult, but can run into all the
-issues found when installing Xen.  Assuming migration from 4.1 to 4.2,
-remove the xenkernel41 and xentools41 packages and install the
-xenkernel42 and xentools42 packages.  Copy the 4.2 xen.gz to /.
+Minor version upgrades are trivial.  Just rebuild/replace the
+xenkernel version and copy the new xen.gz to / (where /boot.cfg
+references it), and reboot.
+
+Major version upgrades are conceptually not difficult, but can run
+into all the issues found when installing Xen.  Assuming migration
+from 4.1 to 4.2, remove the xenkernel41 and xentools41 packages and
+install the xenkernel42 and xentools42 packages.  Copy the 4.2 xen.gz
+to /.
 
 Ensure that the contents of /etc/rc.d/xen* are correct.  Specifically,
 they must match the package you just installed and not be left over
@@ -534,9 +539,9 @@
 (Upgrading from 3.x to 4.x without doing this will result in a hang.)
 
 Ensure that the domU config files are valid for the new version.
-Specifically: remove autorestart=True, and ensure that disks are
-specified with numbers as the second argument, as the examples above
-show, and not NetBSD device names.
+Specifically, for 4.x remove autorestart=True, and ensure that disks
+are specified with numbers as the second argument, as the examples
+above show, and not NetBSD device names.
 
 Hardware known to work
 ----------------------

Change module notion.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -r1.108 -r1.109
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:03:12 -0000	1.108
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:07:39 -0000	1.109
@@ -465,12 +465,11 @@
 There are (at least) two additional things different about NetBSD as a
 dom0 kernel compared to hardware.
 
-One is that modules are not usable in DOM0 kernels, so one must
-compile in what's needed.  It's not really that modules cannot work,
-but that modules must be built for XEN3_DOM0 because some of the
-defines change and the normal module builds don't do this.  Basically,
-enabling Xen changes the kernel ABI, and the module build system
-doesn't cope with this.
+One is that the module ABI is different because some of the #ddefines
+change, so one must build modules for Xen.  As of netbsd-7, the build
+system does this automatically.  TODO: check this.  (Before building
+Xen modules was added, it was awkward to use modules to the point
+where it was considered that it did not work.)
 
 The other difference is that XEN3_DOM0 does not have exactly the same
 options as GENERIC.  While it is debatable whether or not this is a

Clarify versions/i386 as being Xen, not CPU versions
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -r1.107 -r1.108
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:02:27 -0000	1.107
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:03:12 -0000	1.108
@@ -152,7 +152,7 @@
 Architecture
 ------------
 
-Xen itself can run on i386 (some versions) or amd64 machines (all
+Xen itself can run on i386 (Xen < 3.1) or amd64 machines (all Xen
 versions).  (Practically, almost any computer where one would want to
 run Xen today supports amd64.)
 

Allow that -current is ok for hacking
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -r1.106 -r1.107
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:01:34 -0000	1.106
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:02:27 -0000	1.107
@@ -141,8 +141,8 @@
 Therefore, netbsd-7 is recommended as the stable version of the most
 recent release for production use.  For those wanting to learn Xen or
 without production stability concerns, netbsd-7 is still likely most
-appropriate.  Xen runs fine on netbsd-5, but the xentools packages are
-likely difficult to build.
+appropriate, but -current is also a reasonable choice.  Xen runs fine
+on netbsd-5, but the xentools packages are likely difficult to build.
 
 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

Caution against using xm.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -r1.105 -r1.106
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 03:57:26 -0000	1.105
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 04:01:34 -0000	1.106
@@ -129,6 +129,9 @@
 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
 choose one or the other, because it affects which daemons you run.
+However, the rc.d scripts provided by xentools packages expect a
+particular version, and you should use the version used by the
+scripts.
 
 NetBSD
 ------

Update recommendations
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -r1.104 -r1.105
--- wikisrc/ports/xen/howto.mdwn	20 Dec 2016 03:50:04 -0000	1.104
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 03:57:26 -0000	1.105
@@ -133,31 +133,33 @@
 NetBSD
 ------
 
-The netbsd-5, netbsd-6, netbsd-7, and -current branches are all
-reasonable choices, with more or less the same considerations for
-non-Xen use.  Therefore, netbsd-6 is recommended as the stable version
-of the most recent release for production use.  For those wanting to
-learn Xen or without production stability concerns, netbsd-7 is likely
-most appropriate.
+The netbsd-6, netbsd-7, 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.  For those wanting to learn Xen or
+without production stability concerns, netbsd-7 is still likely most
+appropriate.  Xen runs fine on netbsd-5, but the xentools packages are
+likely difficult to build.
 
 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; the lack of support is really a problem when using a dom0 as
-a normal computer.)
+need SMP for dom0 functions; the lack of support is really a problem
+when using a dom0 as a normal computer.)
 
 Architecture
 ------------
 
-Xen itself can run on i386 or amd64 machines.  (Practically, almost
-any computer where one would want to run Xen today supports amd64.)
+Xen itself can run on i386 (some versions) or amd64 machines (all
+versions).  (Practically, almost any computer where one would want to
+run Xen today supports amd64.)
 
 Xen, the dom0 kernel, and each domU kernel can be either i386 or
 amd64.  When building a xenkernel package, one obtains i386 on an i386
 host, and amd64 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.
+kernel, an amd64 dom0 kernel is known to work, and an i386PAE dom0
+kernel should in theory work.  An amd64 xen/dom0 is known to support
+both i386PAE and amd64 domUs.
 
 i386 dom0 and domU kernels must be PAE (except for Xen 3.1); these are
 built by default.  (Note that emacs (at least) fails if run on i386
@@ -182,14 +184,16 @@
  - [PR 47720](http://gnats.netbsd.org/47720)
 
 Note also that there are issues with sparse vnd(4) instances, but
-these are not about Xen.
+these are not about Xen -- they just are noticed with sparse vnd(4)
+instances in support of virtual disks in a dom0.
 
 Recommendation
 --------------
 
-Therefore, this HOWTO recommends running xenkernel42 (and xentools42),
-xl, the NetBSD 6 stable branch, and to use an amd64 kernel as the
-dom0.  Either the i386 or amd64 of NetBSD may be used as domUs.
+Therefore, this HOWTO recommends running xenkernel45 or xenkernel46,
+xl, the NetBSD 7 stable branch, and to use an amd64 kernel as the
+dom0.  Either the i386PAE or amd64 version of NetBSD may be used as
+domUs.
 
 Build problems
 --------------

Rototill versions
Add security patch data.
Members: 
	ports/xen/howto.mdwn:1.103->1.104 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.103
retrieving revision 1.104
diff -u -r1.103 -r1.104
--- wikisrc/ports/xen/howto.mdwn	19 Dec 2016 21:48:53 -0000	1.103
+++ wikisrc/ports/xen/howto.mdwn	20 Dec 2016 03:50:04 -0000	1.104
@@ -49,7 +49,8 @@
 of the dom0.  This can be useful to let a domU run X11, or access some
 network interface or other peripheral.
 
-NetBSD used to support Xen2; this has been removed.
+NetBSD 6 and earlier supported Xen 2; support was removed fro NetBSD
+7.  Xen 2 has been removed from pkgsrc.
 
 Prerequisites
 -------------
@@ -81,27 +82,38 @@
 but note that both packages must be installed together and must have
 matching versions.
 
-xenkernel3 provides Xen 3.1.  This no longer receives security patches
-and should not be used.  It supports PCI passthrough, which is why
-people use it anyway. Xen 3.1 supports non-PAE on i386.
-
-xenkernel33 provides Xen 3.3.  This no longer receives security
-patches and should not be used.  Xen 3.3 supports non-PAE on i386.
-
-xenkernel41 provides Xen 4.1.  This is no longer maintained by Xen,
-but as of 2014-12 receives backported security patches.  There are no
-good reasons to run this version.
-
-xenkernel42 provides Xen 4.2. This is no longer maintained by Xen, but
-as of 2014-12 receives backported security patches.  The only reason
-to run this is if you need to use xm instead of xl.
-
-xenkernel45 provides Xen 4.5.  This is new to pkgsrc as of 2015-01 and
-recommended for use as a conservative choice.
-
-xenkernel46 provides Xen 4.6.  TODO: Probably this is the recommended
+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 supports i386, both PAE and
+non-PAE.
+
+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 supports i386, but only in PAE mode.  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-11 received backported security patches.  Xen 4.1 supports
+i386, but only in PAE mode.  There are no good reasons to run this
 version.
 
+xenkernel42 provides Xen 4.2.  It is no longer maintained by Xen, but
+as of 2016-11 received backported security patches.  Xen 4.2 supports
+i386, but only in PAE mode.  The only reason to run this is if you
+need to use xm instead of xl, or if you need to run an i386 dom0
+(because your hardware is i386 only).
+
+xenkernel45 provides Xen 4.5.  It is no longer maintained by Xen, but
+as of 2016-11 it received security patches.  Xen 4.5 requires an amd64
+dom0, but domUs can be amd64 or i386 PAE.  TODO: It is either a
+conservative choice or somewhat old.
+
+xenkernel45 provides Xen 4.6.  It is new to pkgsrc in 2016-05.  It is
+no longer maintained by Xen, but as of 2016-11 it received security
+patches.  Xen 4.6 requires an amd64 dom0, but domUs can be amd64 or
+i386 PAE.  TODO: It is either a somewhat aggressive choice or the
+standard choice
+
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 
 Ideally newer versions of Xen will be added to pkgsrc.

Prune stray sentence
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -r1.102 -r1.103
--- wikisrc/ports/xen/howto.mdwn	19 Dec 2016 21:11:03 -0000	1.102
+++ wikisrc/ports/xen/howto.mdwn	19 Dec 2016 21:48:53 -0000	1.103
@@ -90,8 +90,7 @@
 
 xenkernel41 provides Xen 4.1.  This is no longer maintained by Xen,
 but as of 2014-12 receives backported security patches.  There are no
-good reasons to run this version.  reasonable although trailing-edge
-choice.
+good reasons to run this version.
 
 xenkernel42 provides Xen 4.2. This is no longer maintained by Xen, but
 as of 2014-12 receives backported security patches.  The only reason

Adjust version info
Add cautions about upgrade issues.
Members: 
	ports/xen/howto.mdwn:1.101->1.102 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -r1.101 -r1.102
--- wikisrc/ports/xen/howto.mdwn	12 Mar 2015 23:40:07 -0000	1.101
+++ wikisrc/ports/xen/howto.mdwn	19 Dec 2016 21:11:03 -0000	1.102
@@ -81,19 +81,27 @@
 but note that both packages must be installed together and must have
 matching versions.
 
-xenkernel3 and xenkernel33 provide Xen 3.1 and 3.3.  These no longer
-receive security patches and should not be used.  Xen 3.1 supports PCI
-passthrough.  Xen 3.1 supports non-PAE on i386.
+xenkernel3 provides Xen 3.1.  This no longer receives security patches
+and should not be used.  It supports PCI passthrough, which is why
+people use it anyway. Xen 3.1 supports non-PAE on i386.
 
-xenkernel41 provides Xen 4.1.  This is no longer maintained by Xen,
-but as of 2014-12 receives backported security patches.  It is a
-reasonable although trailing-edge choice.
+xenkernel33 provides Xen 3.3.  This no longer receives security
+patches and should not be used.  Xen 3.3 supports non-PAE on i386.
 
-xenkernel42 provides Xen 4.2.  This is maintained by Xen, but old as
-of 2014-12.
+xenkernel41 provides Xen 4.1.  This is no longer maintained by Xen,
+but as of 2014-12 receives backported security patches.  There are no
+good reasons to run this version.  reasonable although trailing-edge
+choice.
+
+xenkernel42 provides Xen 4.2. This is no longer maintained by Xen, but
+as of 2014-12 receives backported security patches.  The only reason
+to run this is if you need to use xm instead of xl.
 
 xenkernel45 provides Xen 4.5.  This is new to pkgsrc as of 2015-01 and
-not yet recommended for other than experimental/testing use.
+recommended for use as a conservative choice.
+
+xenkernel46 provides Xen 4.6.  TODO: Probably this is the recommended
+version.
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 
@@ -368,67 +376,47 @@
 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 tools.  The daemons which should be run vary
-with Xen version and with whether one is using xm or xl.  Note that
-xend is for supporting "xm", and should only be used if you plan on
-using "xm".  Do NOT enable xend if you plan on using "xl" as it will
-cause problems.  Running xl without xencommons=YES (and starting it)
-will result in a hang (so don't do that; follow the HOWTO!).
+to configure the dom0 daemons.
 
-The installation of NetBSD should already have created devices for xen
-(xencons, xenevt), but if they are not present, create them:
+The daemons which should be run vary with Xen version and with whether
+one is using xm or xl.  The Xen 3.1 and 3.3 packages use xm.  Xen 4.1
+and higher packages use xl.  While is is possible to use xm with some
+4.x versions (TODO: 4.1 and 4.2?), the pkgsrc-provided rc.d scripts do
+not support this as of 2014-12-26, and thus the HOWTO does not support
+it either.  (Make sure your packages are reasonably recent.)
 
-        cd /dev && sh MAKEDEV xen
-
-TODO: Give 3.1 advice (or remove it from pkgsrc).
-
-For 3.3 (and thus xm), add to rc.conf (but note that you should have
-installed 4.1 or 4.2):
+For "xm" (3.1 and 3.3), you should enable xend and xenbackendd (but
+note that you should be using 4.x):
 
         xend=YES
         xenbackendd=YES
 
-For 4.1 (and thus xm; xl is believed not to work well), add to rc.conf:
-
-        xencommons=YES
-        xend=YES
-
-(If you are using xentools41 from before 2014-12-26, change
-rc.d/xendomains to use xm rather than xl.)
-
-For 4.2 with xm, add to rc.conf
-
-        xencommons=YES
-        xend=YES
-
-For 4.2 with xl, add to rc.conf:
+For "xl" (4.x), you should enabled xend and xencommons (xenstored).
+Trying to boot 4.x without xencommons=YES will result in a hang; it is
+necessary to hig ^C on the console to let the machine finish booting.
+TODO: explain why xend is installed by the package.
 
         xencommons=YES
-        TODO: explain if there is a xend replacement
 
-For 4.5 (and thus with xl), add to rc.conf:
+The installation of NetBSD should already have created devices for xen
+(xencons, xenevt), but if they are not present, create them:
 
-        xencommons=YES
-        TODO: explain if there is a xend replacement
+        cd /dev && sh MAKEDEV xen
 
 TODO: Recommend for/against xen-watchdog.
 
 After you have configured the daemons and either started them (in the
 order given) or rebooted, use xm or xl to inspect Xen's boot messages,
-available resources, and running domains.  An example with xm follows:
+available resources, and running domains.  An example with xl follows:
 
-        # xm dmesg
+        # xl dmesg
 	[xen's boot info]
-        # xm info
+        # xl info
 	[available memory, etc.]
-        # xm list
+        # xl list
         Name              Id  Mem(MB)  CPU  State  Time(s)  Console
         Domain-0           0       64    0  r----     58.1
 
-With xl, the commands are the same, and the output may be slightly
-different.  TODO: add example output for xl before the xm example,
-after confirming on 4.2 and resolving the TODO about rc.conf.
-
 ### Issues with xencommons
 
 xencommons starts xenstored, which stores data on behalf of dom0 and
@@ -513,7 +501,7 @@
 
 TODO: actually do this and fix it if necessary.
 
-Updating Xen versions
+Upgrading Xen versions
 ---------------------
 
 Updating Xen is conceptually not difficult, but can run into all the
@@ -521,9 +509,17 @@
 remove the xenkernel41 and xentools41 packages and install the
 xenkernel42 and xentools42 packages.  Copy the 4.2 xen.gz to /.
 
-Ensure that the contents of /etc/rc.d/xen* are correct.  Enable the
-correct set of daemons.  Ensure that the domU config files are valid
-for the new version.
+Ensure that the contents of /etc/rc.d/xen* are correct.  Specifically,
+they must match the package you just installed and not be left over
+from some previous installation.
+
+Enable the correct set of daemons; see the configuring section above.
+(Upgrading from 3.x to 4.x without doing this will result in a hang.)
+
+Ensure that the domU config files are valid for the new version.
+Specifically: remove autorestart=True, and ensure that disks are
+specified with numbers as the second argument, as the examples above
+show, and not NetBSD device names.
 
 Hardware known to work
 ----------------------

Spam
--- wikisrc/users/agc/comment_1_0f653a47814e72f88b5bb26c72d9ee03._comment	2016-12-16 21:46:54.000000000 +0000
+++ /dev/null	2016-12-16 21:46:18.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
- nickname="hanuman"
- subject="@TOLL FREE@''*1-800-2044-122*'' Epson    Printer Tech SuPpOrt NumBeR | Epso"
- date="2016-12-16T19:05:47Z"
- content="""
-((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number
-"""]]
--- wikisrc/wiki/new_page/comment_1_a1ca85a41303bc3c0a187bac2b21d341._comment	2016-12-16 21:46:54.000000000 +0000
+++ /dev/null	2016-12-16 21:46:18.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
- nickname="hanuman"
- subject="@TOLL FREE@''*1-800-2044-122*'' Epson    Printer Tech SuPpOrt NumBeR | Epso"
- date="2016-12-16T19:07:42Z"
- content="""
-((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number
-"""]]
--- wikisrc/wiki/news/new_mini-blog_for_major_wiki_updates/comment_1_1c628028a5f84cf855ffb86a6cef02f3._comment	2016-12-16 21:46:54.000000000 +0000
+++ /dev/null	2016-12-16 21:46:18.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
- nickname="hanuman"
- subject="Cool Jazz $$$!!#I8002044122!!!#***  EPSON printer  tech  support phone  number  usa"
- date="2016-12-16T19:01:55Z"
- content="""
-((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number, EPSON PRINTER tech support phone number, EPSON PRINTER technical support, EPSON PRINTER technical support number, EPSON PRINTER technical support phone number, EPSON PRINTER tech support number, EPSON PRINTER support number, EPSON PRINTER Tech support phone number, EPSON PRINTER support phone number, EPSON PRINTER technical support phone
-"""]]
--- wikisrc/wiki/news/no_longer_pre-release__44___but.../comment_1_2f531ad3eb088587a3ae82be5b1a1de7._comment	2016-12-16 21:46:54.000000000 +0000
+++ /dev/null	2016-12-16 21:46:18.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
- nickname="hanuman"
- subject="Cool Jazz $$$!!#I8002044122!!!#***  EPSON printer  tech  support phone  number  usa"
- date="2016-12-16T19:09:37Z"
- content="""
-((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_1_35dce5e46e9c01ff4e4fcbab79b79457._comment	2016-12-16 21:46:54.000000000 +0000
+++ /dev/null	2016-12-16 21:46:18.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
- nickname="hanuman"
- subject="Topline>Call++++ ++I~800~204~4122++ EPSON  printer  Tech Support Phone Number     tech Helpline Number"
- date="2016-12-16T18:15:16Z"
- content="""
-((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number, EPSON PRINTER tech support phone number, EPSON PRINTER technical support, EPSON 
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_2_b9f8c19b3dbf79a2a57b732e63682e13._comment	2016-12-16 21:46:54.000000000 +0000
+++ /dev/null	2016-12-16 21:46:18.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
- nickname="hanuman"
- subject="Cool Jazz $$$!!#I8002044122!!!#***  EPSON printer  tech  support phone  number  usa"
- date="2016-12-16T19:02:31Z"
- content="""
-((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number, EPSON PRINTER tech support phone number, EPSON PRINTER technical support, EPSON PRINTER technical support number, EPSON PRINTER technical support phone number, EPSON PRINTER tech support number, EPSON PRINTER support number, EPSON PRINTER Tech support phone number, EPSON PRINTER support phone number, EPSON PRINTER technical support phone
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_3_add2a50a0f94863a161b7407beb423d3._comment	2016-12-16 21:46:54.000000000 +0000
+++ /dev/null	2016-12-16 21:46:18.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
- nickname="hanuman"
- subject="Cool Jazz $$$!!#I8002044122!!!#***  EPSON printer  tech  support phone  number  usa"
- date="2016-12-16T19:03:16Z"
- content="""
-((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_4_cdaa389bae953ae4e4e85013e7bf05c6._comment	2016-12-16 21:46:54.000000000 +0000
+++ /dev/null	2016-12-16 21:46:18.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
- nickname="hanuman"
- subject="@TOLL FREE@''*1-800-2044-122*'' Epson    Printer Tech SuPpOrt NumBeR | Epso"
- date="2016-12-16T19:04:30Z"
- content="""
-((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number
-"""]]
--- wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_5_a42e758a0ac3140e8889abba219e36e0._comment	2016-12-16 21:46:54.000000000 +0000
+++ /dev/null	2016-12-16 21:46:18.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
- nickname="hanuman"
- subject="Uk @@ 18OO2044122 @$$@$$*** Lexmark printer tech support number AUS 1800 059 "
- date="2016-12-16T19:14:04Z"
- content="""
-1800-204-4122*Customer Care Number LEXMARK printer Customer Service Phone number usa ::LEXMARK printer help desk phone number,LEXMARK printer helpline phone number here. Describe LEXMARK printer help desk phone number,LEXMARK printer helpline phone number here.LEXMARK printer support phone number Call, *1800-204-4122* for all type help by LEXMARK PRINTER tech support phone number, *1800-204-4122* LEXMARK PRINTER Tech Support Phone Number, *1800-204-4122*LEXMARK PRINTER Help Desk Phone Number, *1800-204-4122*LEXMARK PRINTER tech support number, LEXMARK PRINTER technical support phone number, *1800-204-4122
-"""]]

Added a comment: Uk @@ 18OO2044122 @$$@$$*** Lexmark printer tech support number AUS 1800 059
--- /dev/null	2016-12-16 21:46:18.000000000 +0000
+++ wikisrc/wiki/news/wiki_edits_go_to_www-changes__64__/comment_5_a42e758a0ac3140e8889abba219e36e0._comment	2016-12-16 21:46:54.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
+ nickname="hanuman"
+ subject="Uk @@ 18OO2044122 @$$@$$*** Lexmark printer tech support number AUS 1800 059 "
+ date="2016-12-16T19:14:04Z"
+ content="""
+1800-204-4122*Customer Care Number LEXMARK printer Customer Service Phone number usa ::LEXMARK printer help desk phone number,LEXMARK printer helpline phone number here. Describe LEXMARK printer help desk phone number,LEXMARK printer helpline phone number here.LEXMARK printer support phone number Call, *1800-204-4122* for all type help by LEXMARK PRINTER tech support phone number, *1800-204-4122* LEXMARK PRINTER Tech Support Phone Number, *1800-204-4122*LEXMARK PRINTER Help Desk Phone Number, *1800-204-4122*LEXMARK PRINTER tech support number, LEXMARK PRINTER technical support phone number, *1800-204-4122
+"""]]

Added a comment: Cool Jazz $$$!!#I8002044122!!!#*** EPSON printer tech support phone number usa
--- /dev/null	2016-12-16 21:46:18.000000000 +0000
+++ wikisrc/wiki/news/no_longer_pre-release__44___but.../comment_1_2f531ad3eb088587a3ae82be5b1a1de7._comment	2016-12-16 21:46:54.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
+ nickname="hanuman"
+ subject="Cool Jazz $$$!!#I8002044122!!!#***  EPSON printer  tech  support phone  number  usa"
+ date="2016-12-16T19:09:37Z"
+ content="""
+((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number
+"""]]

Added a comment: @TOLL FREE@''*1-800-2044-122*'' Epson Printer Tech SuPpOrt NumBeR | Epso
--- /dev/null	2016-12-16 21:46:18.000000000 +0000
+++ wikisrc/wiki/new_page/comment_1_a1ca85a41303bc3c0a187bac2b21d341._comment	2016-12-16 21:46:54.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://me.yahoo.com/a/sID_hTIVmufYlKdpzprnY7vl4_UrzeACxJTpimA7fZsQTjo8tkaqv4lhXx3ax7nwCdAR9y8-#0f0d3"
+ nickname="hanuman"
+ subject="@TOLL FREE@''*1-800-2044-122*'' Epson    Printer Tech SuPpOrt NumBeR | Epso"
+ date="2016-12-16T19:07:42Z"
+ content="""
+((moti))Call @@@++ USA I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa USA 1 I8002044122 EPSON PRINTER  t.e.c.h s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.e.r u.s.a. C.a.l.l EPSON PRINTER h.e.l.p d.e.s.k n.u.m.b.e.r n.u.m.b.e.r C.a.n.a.d.a EPSON PRINTER s.u.p.p.o.r.t p.h.o.n.e n.u.m.b.r usa canada 1-1855-709-2847 USA, EPSON PRINTER  Tech Support phone number,EPSON PRINTER technical support phone number 1 I8002044122 .EPSON PRINTER Tech Support Number EPSON PRINTER Tech EPSON PRINTER tech support, EPSON PRINTER tech support number
+"""]]

Add a comment
Contact | Disclaimer | Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.
NetBSD® is a registered trademark of The NetBSD Foundation, Inc.