Recent changes to this wiki:

add Venue
Index: wikisrc/summits/AsiaBSDCon_2018_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2018_NetBSD_Summit.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/summits/AsiaBSDCon_2018_NetBSD_Summit.mdwn	19 Feb 2018 01:41:32 -0000	1.2
+++ wikisrc/summits/AsiaBSDCon_2018_NetBSD_Summit.mdwn	20 Feb 2018 03:36:54 -0000	1.3
@@ -6,10 +6,11 @@
 * The NetBSD developer summit at AsiaBSDCon 2018 will be held on Friday,
 14:00-17:00(JST) 05:00-08:00(UTC). (TBD)
 
-### NetBSD Dinner
-
-more description
-
+* Venue:
+  * TOKYO UNIVERSITY OF SCIENCE: Building No.11: Room 11-7
+  * [Kagurazaka Campus | Tokyo University of Science](http://www.tus.ac.jp/en/campus/kagurazaka.html)
+  * [Kagurazaka Campus Google Map](http://www.tus.ac.jp/en/campus/kag_gmap.html)
+ 
 ## Planning to attend?
 
 [[!table data="""

Index: wikisrc/summits/AsiaBSDCon_2018_BSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2018_BSD_BoF.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/summits/AsiaBSDCon_2018_BSD_BoF.mdwn	19 Feb 2018 01:43:48 -0000	1.2
+++ wikisrc/summits/AsiaBSDCon_2018_BSD_BoF.mdwn	20 Feb 2018 03:34:50 -0000	1.3
@@ -13,9 +13,10 @@
   * 05:00-07:30(EST)
   * 02:00-04:30(PST)
 * Venue:
-  * [Route from the Morito Memorial Hall to Iidabashi Grand Bloom](https://goo.gl/maps/4ZgD8UX7UL12)
-
-
+  * TOKYO UNIVERSITY OF SCIENCE: Building No.11: Room 11-7
+  * [Kagurazaka Campus | Tokyo University of Science](http://www.tus.ac.jp/en/campus/kagurazaka.html)
+  * [Kagurazaka Campus Google Map](http://www.tus.ac.jp/en/campus/kag_gmap.html)
+ 
 # Dinner
 * After the BoF, we usually go to a bar or a restaurant near the venue.
 

Index: wikisrc/summits/AsiaBSDCon_2018_BSD_BoF.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2018_BSD_BoF.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/summits/AsiaBSDCon_2018_BSD_BoF.mdwn	19 Feb 2018 01:27:30 -0000	1.1
+++ wikisrc/summits/AsiaBSDCon_2018_BSD_BoF.mdwn	19 Feb 2018 01:43:48 -0000	1.2
@@ -32,6 +32,7 @@
 
 [[!table data="""
 First Last | `login@` | join dinner? | comment(s)
+Jun Ebihara | jun@ |join|
 """]]
 
 ## Planning to present something?
@@ -39,6 +40,7 @@
 [[!table data="""
 Speaker  |Title
 `login@` |_Very Interesting Thing_
+jun@ |Japan NetBSD Users Group booth reports
 """]]
 
 ## Discussions

Index: wikisrc/summits/AsiaBSDCon_2018_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2018_NetBSD_Summit.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/summits/AsiaBSDCon_2018_NetBSD_Summit.mdwn	19 Feb 2018 01:33:44 -0000	1.1
+++ wikisrc/summits/AsiaBSDCon_2018_NetBSD_Summit.mdwn	19 Feb 2018 01:41:32 -0000	1.2
@@ -14,6 +14,7 @@
 
 [[!table data="""
 First Last | `login@` | join dinner? | comment(s)
+Jun Ebihara  | jun@ | join | 
 """]]
 
 ## Planning to present something?
@@ -21,6 +22,7 @@
 [[!table data="""
 Speaker  |Title
 `login@` |_Very Interesting Thing_
+jun@ | NetBSD Raspberry Pi Image
 """]]
 
 ## Discussions

--- /dev/null	2018-02-19 01:32:00.000000000 +0000
+++ wikisrc/summits/AsiaBSDCon_2018_NetBSD_Summit.mdwn	2018-02-19 01:33:59.000000000 +0000
@@ -0,0 +1,28 @@
+<!-- we are supposed to use all lowercase letters in the link, so set a proper title for the page: -->
+[[!meta title="AsiaBSDCon 2018 NetBSD Summit"]]
+
+## Details
+
+* The NetBSD developer summit at AsiaBSDCon 2018 will be held on Friday,
+14:00-17:00(JST) 05:00-08:00(UTC). (TBD)
+
+### NetBSD Dinner
+
+more description
+
+## Planning to attend?
+
+[[!table data="""
+First Last | `login@` | join dinner? | comment(s)
+"""]]
+
+## Planning to present something?
+
+[[!table data="""
+Speaker  |Title
+`login@` |_Very Interesting Thing_
+"""]]
+
+## Discussions
+
+## Varia

--- /dev/null	2018-02-19 01:25:15.000000000 +0000
+++ wikisrc/summits/AsiaBSDCon_2018_BSD_BoF.mdwn	2018-02-19 01:27:44.000000000 +0000
@@ -0,0 +1,46 @@
+<!-- we are supposed to use all lowercase letters in the link, so set a proper title for the page: -->
+
+[[!meta title="AsiaBSDCon 2018 BSD BoF"]]
+
+
+# BSD BoF 2018
+------------------------------------------------------
+* Let's run a BSD BoF on AsiaBSDCon2018.
+* All BSD speakers are welcome (No AsiaBSDCon registration is required).
+* Day & time: 2018/3/9(Friday)
+  * 19:00-21:30(JST)
+  * 10:00-12:30(UTC)
+  * 05:00-07:30(EST)
+  * 02:00-04:30(PST)
+* Venue:
+  * [Route from the Morito Memorial Hall to Iidabashi Grand Bloom](https://goo.gl/maps/4ZgD8UX7UL12)
+
+
+# Dinner
+* After the BoF, we usually go to a bar or a restaurant near the venue.
+
+
+## Details
+
+add description here
+
+### NetBSD Dinner
+
+more description
+
+## Planning to attend?
+
+[[!table data="""
+First Last | `login@` | join dinner? | comment(s)
+"""]]
+
+## Planning to present something?
+
+[[!table data="""
+Speaker  |Title
+`login@` |_Very Interesting Thing_
+"""]]
+
+## Discussions
+
+## Varia

Add testing of Linux emulation
--- /dev/null	2018-02-15 12:12:16.000000000 +0000
+++ wikisrc/projects/project/linuxtest.mdwn	2018-02-15 12:19:24.000000000 +0000
@@ -0,0 +1,40 @@
+[[!template id=project
+
+title="Test Linux emulation"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Stephen Borrill](mailto:sborrill@NetBSD.org)
+"""
+
+category="userland"
+difficulty="easy"
+duration="2 months"
+
+description="""
+
+NetBSD has an extensive test suite that tests native kernel and userland
+code. NetBSD can run Linux binaries under emulation (notably on x86,
+but other platforms such as ARM have some support too). The Linux emulation
+is not covered by the test suite. It should be possible to run an
+appropriate subset of the tests when compiled as Linux binaries.
+
+The project could be completed in a number of steps:
+
+* Determine tests that make sense to run under Linux emulation (e.g. syscalls)
+* Compile tests on Linux and then run on NetBSD
+* Add new/altered tests for Linux-specific APIs or features
+* Build cross-compilation environment to build Linux binaries on NetBSD, to make the test-suite self-hosting
+* Fix Linux emulation for tests that fail
+* Use tests to add Linux emulation for syscalls missing (e.g.timer_*)
+
+It may also be instructive to look at the [Linux Test Project](http://linux-test-project.github.io/).
+
+The project would initially be focussed on x86 (amd64 and i386).
+"""
+]]
+
+[[!tag gsoc]]

Fast ethernet driver applies to certain sun5i models as well
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.79
retrieving revision 1.80
diff -u -r1.79 -r1.80
--- wikisrc/ports/evbarm/allwinner.mdwn	15 Feb 2018 11:58:02 -0000	1.79
+++ wikisrc/ports/evbarm/allwinner.mdwn	15 Feb 2018 11:59:22 -0000	1.80
@@ -60,7 +60,7 @@
     <tr><td>Crypto engine</td><td>-</td><td></td></tr>
     <tr><td>CSI</td><td>-</td><td></td></tr>
     <tr><td>DMA</td><td>Yes</td><td></td></tr>
-    <tr><td>Fast Ethernet (sun4i/sun7i)</td><td>Yes</td><td></td></tr>
+    <tr><td>Fast Ethernet (sun4i/sun5i/sun7i)</td><td>Yes</td><td></td></tr>
     <tr><td>Framebuffer</td><td>Yes</td><td>Uses simplefb configured by bootloader</td></tr>
     <tr><td>Gigabit Ethernet (sun6i/sun7i/sun9i)</td><td>Yes</td><td></td></tr>
     <tr><td>Gigabit Ethernet (sun8i/sun50i)</td><td>Yes</td><td></td></tr>

Links to H6 boards
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -r1.78 -r1.79
--- wikisrc/ports/evbarm/allwinner.mdwn	27 Jan 2018 20:02:57 -0000	1.78
+++ wikisrc/ports/evbarm/allwinner.mdwn	15 Feb 2018 11:58:02 -0000	1.79
@@ -38,7 +38,7 @@
     <tr><td>sun9i</td><td>A80</td><td>8.0 and later</td><td><a href="http://linux-sunxi.org/Cubietech_Cubieboard4">Cubietech Cubieboard 4</a></td><td></td></tr>
     <tr><td>sun50i</td><td>A64</td><td>8.99.2 and later</td><td><a href="https://www.pine64.org/?page_id=1194">Pine64</a>, <a href="https://www.pine64.org/?page_id=3707">Pinebook</a></td><td>aarch32 mode</td></tr>
     <tr><td>sun50i</td><td>H5</td><td>8.99.4 and later</td><td><a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180">FriendlyARM NanoPi NEO2, <a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=196">FriendlyARM NanoPi NEO Plus2</a></td><td>aarch32 mode</td></tr>
-    <tr><td>sun50i</td><td>H6</td><td>-</td><td></td></tr>
+    <tr><td>sun50i</td><td>H6</td><td>-</td><td><a href="http://www.orangepi.org/OrangePiOneplus/">Orange Pi One Plus</a>, <a href="https://www.pine64.org/?product_cat=pine-h64-boards">Pine H64</a></td></tr>
   </tbody>
 </table>
 

swap leading tab with spaces as originally set. fight up markdown
Index: wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn	15 Feb 2018 01:52:59 -0000	1.9
+++ wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn	15 Feb 2018 01:55:26 -0000	1.10
@@ -176,11 +176,11 @@
 
 * Edit /mnt/etc/fstab (to use vi, add /mnt/[usr/]bin and relevant libraries to your [ld] path, and export TERM=vt100). Make sure that you at least have
 
-	/dev/dk2        /               ffs     rw              1 1 
-	/dev/dk3        none            none    sw              0 0 
-	ptyfs           /dev/pts        ptyfs   rw              0 0 
-	kernfs          /kern           kernfs  rw,noauto       0 0 
-	procfs          /proc           procfs  rw,noauto       0 0 
+        /dev/dk2        /               ffs     rw              1 1 
+        /dev/dk3        none            none    sw              0 0 
+        ptyfs           /dev/pts        ptyfs   rw              0 0 
+        kernfs          /kern           kernfs  rw,noauto       0 0 
+        procfs          /proc           procfs  rw,noauto       0 0 
 
 * Install the bootcode: 
 

Missing markdown linebreaks (trailing space)
Index: wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn	15 Feb 2018 01:45:46 -0000	1.8
+++ wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn	15 Feb 2018 01:52:59 -0000	1.9
@@ -176,11 +176,11 @@
 
 * Edit /mnt/etc/fstab (to use vi, add /mnt/[usr/]bin and relevant libraries to your [ld] path, and export TERM=vt100). Make sure that you at least have
 
-	/dev/dk2        /               ffs     rw              1 1
-	/dev/dk3        none            none    sw              0 0
-	ptyfs           /dev/pts        ptyfs   rw              0 0
-	kernfs          /kern           kernfs  rw,noauto       0 0
-	procfs          /proc           procfs  rw,noauto       0 0
+	/dev/dk2        /               ffs     rw              1 1 
+	/dev/dk3        none            none    sw              0 0 
+	ptyfs           /dev/pts        ptyfs   rw              0 0 
+	kernfs          /kern           kernfs  rw,noauto       0 0 
+	procfs          /proc           procfs  rw,noauto       0 0 
 
 * Install the bootcode: 
 

I forgot to remove the original reference to disk in gpt commands when I adjusted it.
Add the stock fstab file from distrib/common/bootimage/fstab.in
as the example, need ptyfs so X11 works.
Index: wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn	13 Feb 2018 01:13:18 -0000	1.7
+++ wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn	15 Feb 2018 01:45:46 -0000	1.8
@@ -132,8 +132,8 @@
 
 * Add an FFS partition and a 4GB swap partition by: 
 
-        gpt add wd0 -b 195770624 -i 3 -s 186562702 -t ffs wd0
-        gpt add wd0 -b 382333327 -i 4 -s 8388608 -t swap wd0
+        gpt add -b 195770624 -i 3 -s 186562702 -t ffs wd0
+        gpt add -b 382333327 -i 4 -s 8388608 -t swap wd0
         gpt label -i 3 -l "NetBSD-root" wd0
         gpt label -i 4 -l "NetBSD-swap" wd0
 
@@ -174,10 +174,13 @@
         cd /mnt2/amd64/binary/sets
         for F in $SETS; do (cd /mnt && tar xzpf - ) < $F; done
 
-* Edit /mnt/etc/fstab (to use vi, add /mnt/[usr/]bin and relevant libraries to your [ld] path, and export TERM=vt100). Make sure that you at least have (XXX present a better fstab) 
+* Edit /mnt/etc/fstab (to use vi, add /mnt/[usr/]bin and relevant libraries to your [ld] path, and export TERM=vt100). Make sure that you at least have
 
-        /dev/dk2        /         ffs     rw     1 1 
-        /dev/dk3        none  swap     0 0
+	/dev/dk2        /               ffs     rw              1 1
+	/dev/dk3        none            none    sw              0 0
+	ptyfs           /dev/pts        ptyfs   rw              0 0
+	kernfs          /kern           kernfs  rw,noauto       0 0
+	procfs          /proc           procfs  rw,noauto       0 0
 
 * Install the bootcode: 
 

Unmark a GSoC project - needs to be updated to reflect work done.
Index: wikisrc/projects/project/secureplt.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/secureplt.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/secureplt.mdwn	20 Feb 2015 20:41:05 -0000	1.4
+++ wikisrc/projects/project/secureplt.mdwn	15 Feb 2018 00:58:05 -0000	1.5
@@ -30,5 +30,3 @@
 
 """
 ]]
-
-[[!tag gsoc]]

Marking this inactive failed, revert to avoid future confusion.
Index: wikisrc/projects/project/ledapi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ledapi.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/ledapi.mdwn	15 Feb 2018 00:30:11 -0000	1.5
+++ wikisrc/projects/project/ledapi.mdwn	15 Feb 2018 00:56:34 -0000	1.6
@@ -28,5 +28,3 @@
 
 """
 ]]
-
-[[!tag status:inactive]]

This project got less relevant with the introduction of WSL.
--- wikisrc/projects/project/pkgsrc_porting.mdwn	2018-02-15 00:55:05.000000000 +0000
+++ /dev/null	2018-02-15 00:52:01.000000000 +0000
@@ -1,38 +0,0 @@
-[[!template id=project
-
-title="Port pkgsrc to MinGW"
-
-contact="""
-[tech-pkg](mailto:tech-pkg@NetBSD.org)
-"""
-
-mentors="""
-[Aleksej Saushev](mailto:asau@NetBSD.org)
-"""
-
-category="pkgsrc"
-difficulty="medium"
-duration="3 months"
-
-description="""
-There existed (in past) an option to deploy portable software on
-Microsoft Windows systems through the use of Interix.
-However deploying Interix is tricky, sometimes it is impossible.
-Third-party software usually doesn't support running under Interix too,
-which reduces its utility.
-
-MinGW present easier way to deploy familiar Unix-like environment.
-It is supported much better than Interix by upstream developers,
-and thus software is easier to get running correctly.
-It is easier than Interix to setup too.
-
-Microsoft Windows is perhaps the only widespread platform that
-isn't supported by pkgsrc well enough. Unfortunately, pkgsrc needs
-to be adapted to run on MinGW. Note that [[obache]] has [ported
-pkgsrc to
-Cygwin](http://mail-index.netbsd.org/pkgsrc-users/2013/03/08/msg017803.html).
-
-The goal of this project is to port pkgsrc tools to MinGW
-to the extent of building at least infrastructural packages.
-"""
-]]

remove this project:
- maxv is basically doing this
- poor project description:
- "audit" can be open ended
- no clear plan for improvements to the API
Members: 
	projects/project/mbuf-audit.mdwn:1.2->1.3(DEAD) 

--- wikisrc/projects/project/mbuf-audit.mdwn	2018-02-15 00:49:29.000000000 +0000
+++ /dev/null	2018-02-15 00:48:00.000000000 +0000
@@ -1,17 +0,0 @@
-[[!template id=project
-
-title="mbuf audit"
-
-contact="""
-[tech-net](mailto:tech-net@NetBSD.org)
-"""
-
-category="networking"
-difficulty="hard"
-
-description="""
-Audit NetBSD for misuse of shared/read-only mbuf storage, and fix bugs as you
-find them.  Improve the mbufs API to help developers protect against misuse in
-the future.
-"""
-]]

Change title. forgot.
Index: wikisrc/projects/project/debpkg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/debpkg.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/debpkg.mdwn	12 Feb 2018 23:40:15 -0000	1.4
+++ wikisrc/projects/project/debpkg.mdwn	15 Feb 2018 00:47:14 -0000	1.5
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="pkgin improvements"
+title="Creating .deb packages"
 
 contact="""
 [tech-pkg](mailto:tech-pkg@NetBSD.org)

Mark this project as done by tomohiro kasumi for dragonflybsd.
Index: wikisrc/projects/project/new-automounter.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/new-automounter.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/new-automounter.mdwn	26 Aug 2016 07:58:45 -0000	1.4
+++ wikisrc/projects/project/new-automounter.mdwn	15 Feb 2018 00:45:04 -0000	1.5
@@ -12,6 +12,7 @@
 category="filesystems"
 difficulty="medium"
 duration="3 months"
+done_by="Tomohiro Kasumi (for DragonflyBSD)"
 
 description="""
 NetBSD currently uses amd for automatically mounting (network) file systems. This software package implements an automounter file system as a userland NFS daemon. While this generally works it has major drawbacks:
@@ -42,5 +43,3 @@
 scheme and these desires are rather at odds.
 """
 ]]
-
-[[!tag gsoc]]

This is less difficult as more work has been done.
(Actually runs as MULTIPROCESSOR, but needs some review/fixes)
Members: 
	projects/project/xen-dom0-smp.mdwn:1.1->1.2 

Index: wikisrc/projects/project/xen-dom0-smp.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/xen-dom0-smp.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/xen-dom0-smp.mdwn	19 Aug 2015 00:12:08 -0000	1.1
+++ wikisrc/projects/project/xen-dom0-smp.mdwn	15 Feb 2018 00:40:11 -0000	1.2
@@ -10,7 +10,7 @@
 """
 
 category="kernel"
-difficulty="hard"
+difficulty="medium"
 duration="64 hours"
 
 description="""

CAPITALIZE!
Index: wikisrc/projects/project/raidframe-raid6.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/raidframe-raid6.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/raidframe-raid6.mdwn	20 Feb 2015 19:21:44 -0000	1.3
+++ wikisrc/projects/project/raidframe-raid6.mdwn	15 Feb 2018 00:37:53 -0000	1.4
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="raid 6 in RAIDframe"
+title="RAID 6 in RAIDframe"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)

Typo fix.
Index: wikisrc/projects/project/static-analyzers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/static-analyzers.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/static-analyzers.mdwn	27 Jan 2018 15:22:49 -0000	1.2
+++ wikisrc/projects/project/static-analyzers.mdwn	15 Feb 2018 00:35:06 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Reseearch and integrate the static code analyzers with the NetBSD codebase"
+title="Research and integrate the static code analyzers with the NetBSD codebase"
 
 contact="""
 [tech-userlevel](mailto:tech-userlevel@NetBSD.org)

Mention we use softfloat on 64bitters, that's a huge performance hit.
Index: wikisrc/projects/project/sgimipsr10k.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sgimipsr10k.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/sgimipsr10k.mdwn	16 Feb 2015 06:04:56 -0000	1.2
+++ wikisrc/projects/project/sgimipsr10k.mdwn	15 Feb 2018 00:33:13 -0000	1.3
@@ -14,6 +14,9 @@
 example speculative loads are not handled correctly.  It is unclear if this is
 pure kernel work or the toolchain needs to be changed too.
 
+Currently softfloat is used, and bugs seem to exist in the hardware float support.
+Resolving these bugs and switching to hardware float would improve performance.
+
 See also [NetBSD/sgimips](../../ports/sgimips/).
 """
 ]]

Try to mark this inactive.
Same reasons: -mentor likely won't have time - not high priority
Members: 
	projects/project/ledapi.mdwn:1.4->1.5 

Index: wikisrc/projects/project/ledapi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ledapi.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/ledapi.mdwn	12 Feb 2018 20:50:05 -0000	1.4
+++ wikisrc/projects/project/ledapi.mdwn	15 Feb 2018 00:30:11 -0000	1.5
@@ -28,3 +28,5 @@
 
 """
 ]]
+
+[[!tag status:inactive]]

List benchmark automation as an extended goal.
Index: wikisrc/projects/project/benchmark.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/benchmark.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/benchmark.mdwn	13 Feb 2018 12:36:22 -0000	1.2
+++ wikisrc/projects/project/benchmark.mdwn	13 Feb 2018 13:26:02 -0000	1.3
@@ -32,6 +32,8 @@
 * Compare with other OSes (candidates: Linux and FreeBSD).
 * Write new tests to detect bottle-necks.
 * Report performance and/or scaling issues to developers.
+
+**Extended goals:**
 * Automate performance regression tests
 
 

Add myself as a mentor.
Index: wikisrc/projects/project/wine_amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/wine_amd64.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/wine_amd64.mdwn	13 Feb 2018 07:18:25 -0000	1.3
+++ wikisrc/projects/project/wine_amd64.mdwn	13 Feb 2018 12:50:20 -0000	1.4
@@ -9,6 +9,7 @@
 
 mentors="""
 [Maxime Villard](mailto:maxv@NetBSD.org)
+[Maya Rashish](mailto:maya@NetBSD.org)
 """
 
 category="userland"

Add 'automate benchmark tests' as a goal. from maxv
Index: wikisrc/projects/project/benchmark.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/benchmark.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/benchmark.mdwn	12 Feb 2018 21:22:07 -0000	1.1
+++ wikisrc/projects/project/benchmark.mdwn	13 Feb 2018 12:36:22 -0000	1.2
@@ -24,7 +24,7 @@
 
 Compare the results with FreeBSD and Linux.
 
-Milestones:
+**Milestones:**
 
 * Prepare the environment (native NetBSD installation) and install
 benchmarking tools.
@@ -32,6 +32,8 @@
 * Compare with other OSes (candidates: Linux and FreeBSD).
 * Write new tests to detect bottle-necks.
 * Report performance and/or scaling issues to developers.
+* Automate performance regression tests
+
 
 """
 ]]

Index: wikisrc/projects/project/u-boot-ffs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/u-boot-ffs.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/u-boot-ffs.mdwn	13 Feb 2018 11:32:48 -0000	1.3
+++ wikisrc/projects/project/u-boot-ffs.mdwn	13 Feb 2018 11:37:33 -0000	1.4
@@ -36,6 +36,11 @@
 * Compatibility with FreeBSD UFS
 * Submit U-Boot FFS driver for inclusion with mainline U-Boot
 
+**References:**
+
+* [NetBSD libsa (standalone) UFS driver](https://nxr.netbsd.org/xref/src/sys/lib/libsa/ufs.c)
+* [U-Boot fstype_info struct](https://github.com/u-boot/u-boot/blob/master/fs/fs.c#L109)
+
 """
 ]]
 

Index: wikisrc/projects/project/u-boot-ffs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/u-boot-ffs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/u-boot-ffs.mdwn	13 Feb 2018 11:28:46 -0000	1.2
+++ wikisrc/projects/project/u-boot-ffs.mdwn	13 Feb 2018 11:32:48 -0000	1.3
@@ -24,7 +24,7 @@
 
 * Add an ffs driver to U-Boot (read-only)
 * Add the following commands to U-Boot: *ffssize*, *ffsload*, *ffsls*
-* Add this new driver to existing U-Boot packages (sysutils/u-boot*) in pkgsrc
+* Integrate changes with existing U-Boot packages (sysutils/u-boot*) in pkgsrc
 * Update armv7.img to support booting directly from FFS.
 * Modify sysinst to allow for installation without an MSDOS partition.
   * Some of this will be SoC-specific. Need to detect the SoC type and select the correct kernel/dtb and adjust partition layout to not interfere with U-Boot / SoC specific bootloaders.

Index: wikisrc/projects/project/u-boot-ffs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/u-boot-ffs.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/u-boot-ffs.mdwn	13 Feb 2018 11:05:32 -0000	1.1
+++ wikisrc/projects/project/u-boot-ffs.mdwn	13 Feb 2018 11:28:46 -0000	1.2
@@ -23,6 +23,7 @@
 **Milestones:**
 
 * Add an ffs driver to U-Boot (read-only)
+* Add the following commands to U-Boot: *ffssize*, *ffsload*, *ffsls*
 * Add this new driver to existing U-Boot packages (sysutils/u-boot*) in pkgsrc
 * Update armv7.img to support booting directly from FFS.
 * Modify sysinst to allow for installation without an MSDOS partition.
@@ -31,6 +32,8 @@
 **Extended goals:**
 
 * Add write support to the U-Boot ffs driver
+* Add an *ffswrite* command
+* Compatibility with FreeBSD UFS
 * Submit U-Boot FFS driver for inclusion with mainline U-Boot
 
 """

--- /dev/null	2018-02-13 11:04:13.000000000 +0000
+++ wikisrc/projects/project/u-boot-ffs.mdwn	2018-02-13 11:05:47.000000000 +0000
@@ -0,0 +1,39 @@
+[[!template id=project
+
+title="Add FFS support to U-Boot"
+
+contact="""
+[port-arm](mailto:port-arm@NetBSD.org)
+"""
+
+mentors="""
+[Jared McNeill](mailto:port-arm@NetBSD.org)
+"""
+
+category="kernel"
+difficulty="easy"
+duration="3 months"
+
+description="""
+
+Add support for reading files from a BSD Fast File System from within U-Boot. Typically, on ARM boards where we boot NetBSD with U-Boot we require the kernel to live on an MSDOS or Linux Ext2/3/4 file-system. It would be nice if we could load a kernel directly from FFSv1 or FFSv2 instead.
+
+This project requires access to an ARM board that is supported by mainline U-Boot and NetBSD.
+
+**Milestones:**
+
+* Add an ffs driver to U-Boot (read-only)
+* Add this new driver to existing U-Boot packages (sysutils/u-boot*) in pkgsrc
+* Update armv7.img to support booting directly from FFS.
+* Modify sysinst to allow for installation without an MSDOS partition.
+  * Some of this will be SoC-specific. Need to detect the SoC type and select the correct kernel/dtb and adjust partition layout to not interfere with U-Boot / SoC specific bootloaders.
+
+**Extended goals:**
+
+* Add write support to the U-Boot ffs driver
+* Submit U-Boot FFS driver for inclusion with mainline U-Boot
+
+"""
+]]
+
+[[!tag gsoc]]

whitespaces
Index: wikisrc/projects/project/wine_amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/wine_amd64.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/wine_amd64.mdwn	13 Feb 2018 07:12:10 -0000	1.2
+++ wikisrc/projects/project/wine_amd64.mdwn	13 Feb 2018 07:18:25 -0000	1.3
@@ -28,11 +28,9 @@
  * Make Wine32 work on amd64. As a first shot, it should be possible to compile
    Wine32 on NetBSD-i386, and launch it on NetBSD-amd64 (which supports running
    native 32bit binaries). At this stage, old Windows video games should work.
-
  * Make Wine32+Wine64 work on amd64. See the WineHQ wiki on how to achieve
    this. At this stage, 64bit Windows binaries that use 32bit libraries should
    work.
-
  * Package Wine32+Wine64 for pkgsrc.
 """
 ]]

Tag for GSoC.
Index: wikisrc/projects/project/wine_amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/wine_amd64.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/wine_amd64.mdwn	13 Feb 2018 07:10:20 -0000	1.1
+++ wikisrc/projects/project/wine_amd64.mdwn	13 Feb 2018 07:12:10 -0000	1.2
@@ -36,3 +36,5 @@
  * Package Wine32+Wine64 for pkgsrc.
 """
 ]]
+
+[[!tag gsoc]]

Add a "Port Wine to amd64" project.
I've put myself as mentor, but it would be nice if someone else (from
the pkgsrc world) could join.
Members: 
	projects/project/wine_amd64.mdwn:INITIAL->1.1 

--- /dev/null	2018-02-13 07:10:16.000000000 +0000
+++ wikisrc/projects/project/wine_amd64.mdwn	2018-02-13 07:10:34.000000000 +0000
@@ -0,0 +1,38 @@
+[[!template id=project
+
+title="Port Wine to amd64"
+
+contact="""
+[port-amd64](mailto:port-amd64@NetBSD.org),
+[tech-kern](mailto:tech-kern@NetBSD.org)
+"""
+
+mentors="""
+[Maxime Villard](mailto:maxv@NetBSD.org)
+"""
+
+category="userland"
+difficulty="easy"
+
+description="""
+The Wine program is made of two components, Wine32 and Wine64, that respectively
+allow 32bit or 64bit Windows binaries to run on UNIX-like systems.
+
+Until now, Wine32 could not work on NetBSD-amd64, because the USER_LDT option
+was not available in the kernel.
+
+This option was recently added, so Wine32 can now be ported to NetBSD-amd64.
+
+Milestones:
+
+ * Make Wine32 work on amd64. As a first shot, it should be possible to compile
+   Wine32 on NetBSD-i386, and launch it on NetBSD-amd64 (which supports running
+   native 32bit binaries). At this stage, old Windows video games should work.
+
+ * Make Wine32+Wine64 work on amd64. See the WineHQ wiki on how to achieve
+   this. At this stage, 64bit Windows binaries that use 32bit libraries should
+   work.
+
+ * Package Wine32+Wine64 for pkgsrc.
+"""
+]]

Adjust the syntax for the gpt command
Add dump frequency and pass number to fstab snippet
Index: wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn	4 Jul 2016 06:00:14 -0000	1.6
+++ wikisrc/tutorials/how_to_install_netbsd_on_an_apple_macbook_with_core2duo.mdwn	13 Feb 2018 01:13:18 -0000	1.7
@@ -132,10 +132,10 @@
 
 * Add an FFS partition and a 4GB swap partition by: 
 
-        gpt add wd0 -b 195770624 -i 3 -s 186562702 -t ufs wd0
+        gpt add wd0 -b 195770624 -i 3 -s 186562702 -t ffs wd0
         gpt add wd0 -b 382333327 -i 4 -s 8388608 -t swap wd0
-        gpt label wd0 -i 3 -l "NetBSD-root"
-        gpt label wd0 -i 4 -l "NetBSD-swap"
+        gpt label -i 3 -l "NetBSD-root" wd0
+        gpt label -i 4 -l "NetBSD-swap" wd0
 
 * Dynamically add the relevant wedges using dkctl(8). The output of gpt add should show you the needed parameters (you can use ffs and swap, respectively, for the types). 
 
@@ -176,8 +176,8 @@
 
 * Edit /mnt/etc/fstab (to use vi, add /mnt/[usr/]bin and relevant libraries to your [ld] path, and export TERM=vt100). Make sure that you at least have (XXX present a better fstab) 
 
-        /dev/dk2        /         ffs     rw      
-        /dev/dk3        none  swap
+        /dev/dk2        /         ffs     rw     1 1 
+        /dev/dk3        none  swap     0 0
 
 * Install the bootcode: 
 

Reword
Index: wikisrc/projects/project/debpkg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/debpkg.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/debpkg.mdwn	12 Feb 2018 23:37:49 -0000	1.3
+++ wikisrc/projects/project/debpkg.mdwn	12 Feb 2018 23:40:15 -0000	1.4
@@ -19,7 +19,7 @@
 It's also the native packaging format in several systems, and would improve user experience on those systems.  
 It would be nice to generate pkgsrc packages to this format.
 
-Prior work exists has been done on generating packages in other formats.
+Prior work exists for generating packages in other formats.
 
 **Milestones**
 

End sentence with dot
Index: wikisrc/projects/project/debpkg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/debpkg.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/debpkg.mdwn	12 Feb 2018 23:35:55 -0000	1.2
+++ wikisrc/projects/project/debpkg.mdwn	12 Feb 2018 23:37:49 -0000	1.3
@@ -19,7 +19,7 @@
 It's also the native packaging format in several systems, and would improve user experience on those systems.  
 It would be nice to generate pkgsrc packages to this format.
 
-Prior work exists has been done on generating packages in other formats
+Prior work exists has been done on generating packages in other formats.
 
 **Milestones**
 

Try to markdown better.
Index: wikisrc/projects/project/debpkg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/debpkg.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/debpkg.mdwn	12 Feb 2018 22:47:55 -0000	1.1
+++ wikisrc/projects/project/debpkg.mdwn	12 Feb 2018 23:35:55 -0000	1.2
@@ -15,8 +15,8 @@
 duration="3 months"
 
 description="""
-Debian's .deb packaging format is supported by mature and user-friendly packaging tools.
-It's also the native packaging format in several systems, and would improve user experience on those systems.
+Debian's .deb packaging format is supported by mature and user-friendly packaging tools.  
+It's also the native packaging format in several systems, and would improve user experience on those systems.  
 It would be nice to generate pkgsrc packages to this format.
 
 Prior work exists has been done on generating packages in other formats

More style
Index: wikisrc/projects/project/pkgsrc-sanitizers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc-sanitizers.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/pkgsrc-sanitizers.mdwn	12 Feb 2018 22:52:47 -0000	1.3
+++ wikisrc/projects/project/pkgsrc-sanitizers.mdwn	12 Feb 2018 22:56:25 -0000	1.4
@@ -18,7 +18,7 @@
 
 Add support in the pkgsrc framework for building packages with sanitizers.
 
-Expected sanitizer options:
+**Expected sanitizer options:**
 
 - Address (ASan),
 - Memory (MSan),

More style.
Index: wikisrc/projects/project/efi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/efi.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/efi.mdwn	12 Feb 2018 19:26:59 -0000	1.5
+++ wikisrc/projects/project/efi.mdwn	12 Feb 2018 22:52:47 -0000	1.6
@@ -19,13 +19,13 @@
 Add support for booting EFI on ARM machines, and improve EFI support
 
 
-Milestones:
+**Milestones:**
 
 * Separate the x86 code out from the EFI implementation
 * Run EFI bootloader using U-Boot EFI services on ARM
 * Add support for booting ARM images using ARM FDT boot protocol
 
-Extended goals:
+**Extended goals:**
 
 * Add EFI loader to armv7.img and switch it from MBR to GPT or hybrid partition table
 * Machine-independent EFI framebuffer support
Index: wikisrc/projects/project/pkgsrc-sanitizers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc-sanitizers.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/pkgsrc-sanitizers.mdwn	27 Jan 2018 15:22:49 -0000	1.2
+++ wikisrc/projects/project/pkgsrc-sanitizers.mdwn	12 Feb 2018 22:52:47 -0000	1.3
@@ -28,7 +28,7 @@
 - Address;Undefined (ASan & UBSan)
 - "" (empty string) - the default option
 
-Milestones:
+**Milestones:**
 
 * Ensure the availability of the toolchain and prebuilt userland with the sanitizers.
 * Add new option in pkgsrc to build the packages with a each sanitizer.

Add '.deb packages' project.
jperkin has proposed it & offered to mentor.
Members: 
	projects/project/debpkg.mdwn:INITIAL->1.1 

--- /dev/null	2018-02-12 22:48:00.000000000 +0000
+++ wikisrc/projects/project/debpkg.mdwn	2018-02-12 22:48:11.000000000 +0000
@@ -0,0 +1,34 @@
+[[!template id=project
+
+title="pkgin improvements"
+
+contact="""
+[tech-pkg](mailto:tech-pkg@NetBSD.org)
+"""
+
+mentors="""
+[Jonathan Perkin](mailto:jperkin@joyent.com)
+"""
+
+category="pkgsrc"
+difficulty="easy"
+duration="3 months"
+
+description="""
+Debian's .deb packaging format is supported by mature and user-friendly packaging tools.
+It's also the native packaging format in several systems, and would improve user experience on those systems.
+It would be nice to generate pkgsrc packages to this format.
+
+Prior work exists has been done on generating packages in other formats
+
+**Milestones**
+
+* Lookup .deb format documentation and experiment with tooling
+* Investigate differences between pkgsrc's pkg and deb format
+* Import necessary tools to generate .deb packages
+* Build many packages and look for bugs
+
+"""
+]]
+
+[[!tag gsoc]]

Add new project "benchmark netbsd" from kamil
--- /dev/null	2018-02-12 21:20:01.000000000 +0000
+++ wikisrc/projects/project/benchmark.mdwn	2018-02-12 21:22:21.000000000 +0000
@@ -0,0 +1,39 @@
+[[!template id=project
+
+title="Benchmark NetBSD"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Kamil Rytarowski](mailto:kamil@NetBSD.org)
+"""
+
+category="userland"
+difficulty="easy"
+duration="3 months"
+
+description="""
+
+Find and execute benchmarks of various kernel features and userland
+libraries on NetBSD (installed natively). Check the scaling issue over
+multiple CPUs.
+
+Prepare new benchmarks for untested subsystems like tmpfs performance.
+
+Compare the results with FreeBSD and Linux.
+
+Milestones:
+
+* Prepare the environment (native NetBSD installation) and install
+benchmarking tools.
+* Collect the results of benchmarks (modes: 1-CPU, 2-CPU, etc).
+* Compare with other OSes (candidates: Linux and FreeBSD).
+* Write new tests to detect bottle-necks.
+* Report performance and/or scaling issues to developers.
+
+"""
+]]
+
+[[!tag gsoc]]

Better title. first impressions count!
Index: wikisrc/projects/project/madwifi-ng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/madwifi-ng.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/madwifi-ng.mdwn	4 Feb 2018 19:47:37 -0000	1.4
+++ wikisrc/projects/project/madwifi-ng.mdwn	12 Feb 2018 20:51:53 -0000	1.5
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Updated Atheros WiFi support"
+title="Port FreeBSD's updated Atheros WiFi driver"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)

Don't list this as a GSoC Project
(not high priority, mentor might be unavailable)
Index: wikisrc/projects/project/ledapi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ledapi.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/ledapi.mdwn	20 Feb 2015 17:12:46 -0000	1.3
+++ wikisrc/projects/project/ledapi.mdwn	12 Feb 2018 20:50:05 -0000	1.4
@@ -28,5 +28,3 @@
 
 """
 ]]
-
-[[!tag gsoc]]

Unlist from GSoC projects. ISDN is not so hot any more.
Could be rewritten to Asterisk only.
Members: 
	projects/project/isdn-nt-asterisk.mdwn:1.4->1.5 

Index: wikisrc/projects/project/isdn-nt-asterisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/isdn-nt-asterisk.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/isdn-nt-asterisk.mdwn	20 Feb 2015 19:40:28 -0000	1.4
+++ wikisrc/projects/project/isdn-nt-asterisk.mdwn	12 Feb 2018 20:20:40 -0000	1.5
@@ -30,5 +30,3 @@
 
 """
 ]]
-
-[[!tag gsoc]]

drop interop with openssh, goal->goals
Index: wikisrc/projects/project/netpgpverify.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/netpgpverify.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/netpgpverify.mdwn	12 Feb 2018 19:36:43 -0000	1.2
+++ wikisrc/projects/project/netpgpverify.mdwn	12 Feb 2018 19:39:17 -0000	1.3
@@ -19,10 +19,10 @@
 
 * Adapt existing ed25519 and salsa20 implementations to netpgp, netpgpverify
 * Maintain compatibility and interoperability with gpg2's usage
-* Maintain compatibility and interoperability with openssh's keys
+* Maintain compatibility with openssh's keys
 * Extend tests to cover new algorithms
 
-Extended goal:
+Extended goals:
 
 * provide a standalone netpgp signing utility, to mirror the netpgpverify verification utility
 

List netpgpverify explicitly in title. syntatic changes.
Index: wikisrc/projects/project/netpgpverify.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/netpgpverify.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/netpgpverify.mdwn	12 Feb 2018 19:33:22 -0000	1.1
+++ wikisrc/projects/project/netpgpverify.mdwn	12 Feb 2018 19:36:43 -0000	1.2
@@ -1,9 +1,9 @@
 [[!template id=project
 
-title="Modern cryptographic algorithms to netpgp"
+title="Modern cryptographic algorithms to netpgp, netpgpverify"
 
 contact="""
-[Alistair G. Crooks](mailto:agc@NetBSD.org)
+[Alistair G. Crooks](mailto:agc@NetBSD.org),
 [tech-crypto](mailto:tech-crypto@NetBSD.org)
 """
 
@@ -23,6 +23,7 @@
 * Extend tests to cover new algorithms
 
 Extended goal:
+
 * provide a standalone netpgp signing utility, to mirror the netpgpverify verification utility
 
 """

typo
Index: wikisrc/projects/project/altq.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/altq.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/altq.mdwn	15 Sep 2017 08:45:57 -0000	1.2
+++ wikisrc/projects/project/altq.mdwn	12 Feb 2018 19:33:29 -0000	1.3
@@ -20,14 +20,16 @@
 queueing disciplines and other quality of service (QoS) related
 components required to control resource usage.
 
-It is currently it is integrated
+It is currently integrated in
 [[!template id=man name="pf" section="4"]]
+.
 
 Unfortunately it was written a long time ago and it suffers from a lot
 of code duplication, dangerous code practices and can use improvements
 both in the API and implementation. After these problems have been addressed
 it should be integrated with
 [[!template id=man name="npf" section="4"]]
+.
 
 """
 ]]

Add netpgpverify project. Mentored by agc.
Draft for sharing.
Members: 
	projects/project/netpgpverify.mdwn:INITIAL->1.1 

--- /dev/null	2018-02-12 19:32:24.000000000 +0000
+++ wikisrc/projects/project/netpgpverify.mdwn	2018-02-12 19:33:39.000000000 +0000
@@ -0,0 +1,31 @@
+[[!template id=project
+
+title="Modern cryptographic algorithms to netpgp"
+
+contact="""
+[Alistair G. Crooks](mailto:agc@NetBSD.org)
+[tech-crypto](mailto:tech-crypto@NetBSD.org)
+"""
+
+mentors="""
+[Alistair G. Crooks](mailto:agc@NetBSD.org)
+"""
+
+category="userland"
+difficulty="easy"
+duration="2 months"
+
+description="""
+
+* Adapt existing ed25519 and salsa20 implementations to netpgp, netpgpverify
+* Maintain compatibility and interoperability with gpg2's usage
+* Maintain compatibility and interoperability with openssh's keys
+* Extend tests to cover new algorithms
+
+Extended goal:
+* provide a standalone netpgp signing utility, to mirror the netpgpverify verification utility
+
+"""
+]]
+
+[[!tag gsoc]]

Index: wikisrc/projects/project/efi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/efi.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/efi.mdwn	12 Feb 2018 19:19:55 -0000	1.4
+++ wikisrc/projects/project/efi.mdwn	12 Feb 2018 19:26:59 -0000	1.5
@@ -22,11 +22,12 @@
 Milestones:
 
 * Separate the x86 code out from the EFI implementation
-* Add support for booting EFI ARM images
-* Support building ARM images with GPT and using EFI
+* Run EFI bootloader using U-Boot EFI services on ARM
+* Add support for booting ARM images using ARM FDT boot protocol
 
 Extended goals:
 
+* Add EFI loader to armv7.img and switch it from MBR to GPT or hybrid partition table
 * Machine-independent EFI framebuffer support
 
 """

more template typos
Index: wikisrc/projects/project/efi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/efi.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/efi.mdwn	12 Feb 2018 19:17:51 -0000	1.3
+++ wikisrc/projects/project/efi.mdwn	12 Feb 2018 19:19:55 -0000	1.4
@@ -1,4 +1,4 @@
-[!template id=project
+[[!template id=project
 
 title="Machine-independent EFI bootloader (for ARM)"
 

Typo breaks template.
Index: wikisrc/projects/project/efi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/efi.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/efi.mdwn	12 Feb 2018 19:15:29 -0000	1.2
+++ wikisrc/projects/project/efi.mdwn	12 Feb 2018 19:17:51 -0000	1.3
@@ -1,4 +1,4 @@
-e[!template id=project
+[!template id=project
 
 title="Machine-independent EFI bootloader (for ARM)"
 

More better title. point to port-arm, jmcneill reads it more than his own email.
Index: wikisrc/projects/project/efi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/efi.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/efi.mdwn	12 Feb 2018 19:12:47 -0000	1.1
+++ wikisrc/projects/project/efi.mdwn	12 Feb 2018 19:15:29 -0000	1.2
@@ -1,13 +1,13 @@
 e[!template id=project
 
-title="Machine-independent EFI code"
+title="Machine-independent EFI bootloader (for ARM)"
 
 contact="""
-[tech-kern](mailto:tech-kern@NetBSD.org)
+[port-arm](mailto:port-arm@NetBSD.org)
 """
 
 mentors="""
-[Jared McNeill](mailto:jmcneill@NetBSD.org)
+[Jared McNeill](mailto:port-arm@NetBSD.org)
 """
 
 category="kernel"

Add an easy kernel project: MI (aka ARM) EFI support.
jmcneill can mentor it.
Members: 
	projects/project/efi.mdwn:INITIAL->1.1 

--- /dev/null	2018-02-12 19:10:06.000000000 +0000
+++ wikisrc/projects/project/efi.mdwn	2018-02-12 19:13:01.000000000 +0000
@@ -0,0 +1,35 @@
+e[!template id=project
+
+title="Machine-independent EFI code"
+
+contact="""
+[tech-kern](mailto:tech-kern@NetBSD.org)
+"""
+
+mentors="""
+[Jared McNeill](mailto:jmcneill@NetBSD.org)
+"""
+
+category="kernel"
+difficulty="easy"
+duration="2 months"
+
+description="""
+
+Add support for booting EFI on ARM machines, and improve EFI support
+
+
+Milestones:
+
+* Separate the x86 code out from the EFI implementation
+* Add support for booting EFI ARM images
+* Support building ARM images with GPT and using EFI
+
+Extended goals:
+
+* Machine-independent EFI framebuffer support
+
+"""
+]]
+
+[[!tag gsoc]]

removed
--- wikisrc/ports/evbarm/rockchip.mdwn	2018-02-08 00:17:56.000000000 +0000
+++ /dev/null	2018-02-08 00:17:13.000000000 +0000
@@ -1,23 +0,0 @@
-[[!meta title="NetBSD/evbarm on Rockchip SoCs"]]
-
-[[!toc levels=2]]
-
-# Supported boards
- - [MINIX NEO X7](http://www.minix.com.hk/Products/MINIX-NEOX7-ANDROID-TV.html)
- - [Radxa Rock 2013/Pro/Lite](http://radxa.com/Rock#Radxa_Rock.28Pro.2FLite.29)
- - [Rayeager PX2](http://emall.chipspark.com/goods/Rayeager+PX2+1GB+Enhanced+Board/13#.Veb1KNOqqkp)
-
-# Supported hardware
- - SoCs
-   - Cortex-A9: PX2/RK3066 (dual core), RK3188/RK3188+ (quad core)
- - CPU frequency/voltage scaling (RK3188/RK3188+)
- - SD/MMC controller
- - GPIO
- - UART
- - I2C
- - PMU
-   - ACT8834
- - Watchdog timer
- - USB host (DWC2)
- - Ethernet
- - RTC

Rockchip port is gone
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- wikisrc/ports/evbarm.mdwn	28 Dec 2017 06:15:13 -0000	1.45
+++ wikisrc/ports/evbarm.mdwn	8 Feb 2018 00:16:55 -0000	1.46
@@ -254,9 +254,6 @@
 ### Raspberry Pi Foundation **Raspberry Pi**/**Raspberry Pi 2**/**Raspberry Pi 3**
 The [[Raspberry Pi]] is a low-cost credit-card-sized computer from the Raspberry Pi Foundation.  The Raspberry Pi, Pi 2, and Pi 3 are supported.
 
-### Rockchip PX2/RK3066/RK3188/RK3188+
-Various [[Rockchip]] family SoCs are supported by the ROCKCHIP kernel.
-
 ### Samsung **SMDK2410**
 
 The SMDK2410 is the reference platform for the Samsung **S3C2410** processor,

Move FOSDEM 2018 to past events.
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- wikisrc/events.mdwn	7 Dec 2017 22:05:50 -0000	1.54
+++ wikisrc/events.mdwn	5 Feb 2018 09:01:25 -0000	1.55
@@ -9,16 +9,6 @@
 Future Events
 -------------
 
-### `Feb 2018` - FOSDEM 2018, Brussels, Belgium
-
-*February 3 - 4, 2018, ULB Solbosch Campus, Brussels, Belgium*
-
-[FOSDEM](https://fosdem.org/2018/) is a free event for software developers to
-meet, share ideas and collaborate. Every year, thousands of developers of
-free and open source software from all over the world gather at the event in
-Brussels.
-
-
 ### `Mar 2018` - AsiaBSDCon 2018, Tokyo, Japan
 
 *March 8 - 11, Tokyo University of Science, Tokyo, Japan*
@@ -48,6 +38,16 @@
 Past Events
 -----------
 
+### `Feb 2018` - FOSDEM 2018, Brussels, Belgium
+
+*February 3 - 4, 2018, ULB Solbosch Campus, Brussels, Belgium*
+
+[FOSDEM](https://fosdem.org/2018/) 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.
+
+
 ### `Nov 2017` - BSDTW 2017, Taipei, Taiwan
 
 *November 11 - 12, 2017, Taipei, Taiwan*

This is probably OK for GSoC.
Actual hardware is a problem, but the first step is lots of build issues,
so it'll be OK to delay by 2-3 weeks.
Members: 
	projects/project/madwifi-ng.mdwn:1.3->1.4 

Index: wikisrc/projects/project/madwifi-ng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/madwifi-ng.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/madwifi-ng.mdwn	4 Feb 2018 19:09:47 -0000	1.3
+++ wikisrc/projects/project/madwifi-ng.mdwn	4 Feb 2018 19:47:37 -0000	1.4
@@ -14,3 +14,5 @@
 would be nice to have these devices supported in NetBSD.
 """
 ]]
+
+[[!tag gsoc]]

Add userland sanitizers as a project.
--- /dev/null	2018-02-04 19:42:20.000000000 +0000
+++ wikisrc/projects/project/userland-san.mdwn	2018-02-04 19:46:36.000000000 +0000
@@ -0,0 +1,37 @@
+[[!template id=project
+
+title="Building userland with sanitizers"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Maya Rashish](mailto:maya@NetBSD.org)
+"""
+
+category="analyzers"
+difficulty="easy"
+duration="3 months"
+
+description="""
+
+Sanitizers such as Address Sanitizers are very good at finding
+memory-related bugs in code. Unfortunately building everything
+with them isn't trivial, as some code (statically built programs)
+cannot be compiled with them.
+
+Additionally, running a userland built entirely with sanitizers
+poses difficulties, which would be nice to resolve.
+
+Milestones:
+
+* Build parts of the testsuite with sanitizers
+* Build most of userland with sanitizers
+* Report bugs
+* Resolve issues with running a full sanitizer userland
+
+"""
+]]
+
+[[!tag gsoc]]

Mark done by chuq, though it needs more work - maybe the extra work can be
its own project.
Index: wikisrc/projects/project/zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/zfs.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/zfs.mdwn	28 Dec 2014 19:51:26 -0000	1.3
+++ wikisrc/projects/project/zfs.mdwn	4 Feb 2018 19:11:57 -0000	1.4
@@ -8,7 +8,7 @@
 
 category="filesystems"
 difficulty="medium"
-duration="3-9 months?"
+done_by="Chuck Silvers"
 
 description="""
 The ZFS port to NetBSD is half-done, or maybe more than half. Finish

Talk about importing freebsd ath(4) code instead of linux.
I think that's easier than making sense and converting the linux driver,
so mark this project easy.
Members: 
	projects/project/madwifi-ng.mdwn:1.2->1.3 

Index: wikisrc/projects/project/madwifi-ng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/madwifi-ng.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/madwifi-ng.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/madwifi-ng.mdwn	4 Feb 2018 19:09:47 -0000	1.3
@@ -7,11 +7,10 @@
 """
 
 category="kernel"
-difficulty="medium"
+difficulty="easy"
 
 description="""
-The latest Linux code in madwifi-ng includes a major code overhaul and support
-for advanced features (SuperAG @ 108Mbps, eXtended Range) available in these
-parts.  It would be nice to have these features in NetBSD, under a BSD license.
+The latest FreeBSD code for ath(4) includes support for newer cards, it
+would be nice to have these devices supported in NetBSD.
 """
 ]]

Badly rewrite to only be about brcmsmac. update linux URL.
brcmfmac part is done. it needs to use PCI/SDIO, but this will happen anyway.
see bwfm(4).
Members: 
	projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn:1.2->1.3 

Index: wikisrc/projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn	27 Jan 2018 18:31:21 -0000	1.2
+++ wikisrc/projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn	31 Jan 2018 20:25:56 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Support Broadcom BCM43* WiFi adapters"
+title="Support Broadcom SoftMAC WiFi adapters"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)
@@ -10,12 +10,8 @@
 difficulty="hard"
 
 description="""
-brcmsmac and brcmfmac WiFi device drivers for Linux supports
-BCM43XX and BCM43XXX based WiFi adapters.
+Linux provides an ISC-licensed Broadcom SoftMAC driver.
+Source code is included in [Linux kernel tree](https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/broadcom/brcm80211),
 
-And source code is included in [Linux kernel tree](http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/brcm80211),
-but it is licensed under ISC license.
-
-You can find these devices on Apple MacBook.
 """
 ]]

Add NanoPi NEO Plus2 to H5 example boards list
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -r1.77 -r1.78
--- wikisrc/ports/evbarm/allwinner.mdwn	18 Nov 2017 18:32:37 -0000	1.77
+++ wikisrc/ports/evbarm/allwinner.mdwn	27 Jan 2018 20:02:57 -0000	1.78
@@ -37,7 +37,7 @@
     <tr><td>sun8i</td><td>V3s</td><td>-</td><td><a href="https://www.indiegogo.com/projects/licheepi-zero-6-extensible-linux-module-on-finger-wifi-diy#/">Lichee Pi Zero</a></td><td></td></tr>
     <tr><td>sun9i</td><td>A80</td><td>8.0 and later</td><td><a href="http://linux-sunxi.org/Cubietech_Cubieboard4">Cubietech Cubieboard 4</a></td><td></td></tr>
     <tr><td>sun50i</td><td>A64</td><td>8.99.2 and later</td><td><a href="https://www.pine64.org/?page_id=1194">Pine64</a>, <a href="https://www.pine64.org/?page_id=3707">Pinebook</a></td><td>aarch32 mode</td></tr>
-    <tr><td>sun50i</td><td>H5</td><td>8.99.4 and later</td><td><a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180">FriendlyARM NanoPi NEO2</td><td>aarch32 mode</td></tr>
+    <tr><td>sun50i</td><td>H5</td><td>8.99.4 and later</td><td><a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=180">FriendlyARM NanoPi NEO2, <a href="http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=196">FriendlyARM NanoPi NEO Plus2</a></td><td>aarch32 mode</td></tr>
     <tr><td>sun50i</td><td>H6</td><td>-</td><td></td></tr>
   </tbody>
 </table>

Use an existing category tag.
Index: wikisrc/projects/project/xenboot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/xenboot.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/xenboot.mdwn	29 Dec 2012 04:12:41 -0000	1.2
+++ wikisrc/projects/project/xenboot.mdwn	27 Jan 2018 18:33:50 -0000	1.3
@@ -10,7 +10,7 @@
 [John Nemeth](mailto:jnemeth@NetBSD.org)
 """
 
-category="xen"
+category="ports"
 difficulty="medium"
 duration="2 days (for initial support)"
 

Add missing difficulty tags.
(if these are your projects or you have a stake in them, please review
and/or update as necessary)
I marked the broadcomm drivers hard because of broadcomm's history
wrt drivers; change if these devices are believed to be easier...
Members: 
	projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn:1.1->1.2 
	projects/project/dtrace-syscall.mdwn:1.2->1.3 
	projects/project/microblaze.mdwn:1.1->1.2 
	projects/project/pkgsrc_gnome_support.mdwn:1.2->1.3 

Index: wikisrc/projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn	14 Feb 2015 07:01:22 -0000	1.1
+++ wikisrc/projects/project/brcmsmac-brcmfmac-wifi-driver.mdwn	27 Jan 2018 18:31:21 -0000	1.2
@@ -7,6 +7,7 @@
 """
 
 category="kernel"
+difficulty="hard"
 
 description="""
 brcmsmac and brcmfmac WiFi device drivers for Linux supports
Index: wikisrc/projects/project/dtrace-syscall.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/dtrace-syscall.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/dtrace-syscall.mdwn	27 Jan 2018 17:50:17 -0000	1.2
+++ wikisrc/projects/project/dtrace-syscall.mdwn	27 Jan 2018 18:31:21 -0000	1.3
@@ -7,6 +7,7 @@
 """
 
 category="kernel"
+difficulty="medium"
 
 description="""
 NetBSD has preliminary DTrace support, so it supports SDT and FBT provider
Index: wikisrc/projects/project/microblaze.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/microblaze.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/microblaze.mdwn	14 Feb 2015 07:00:22 -0000	1.1
+++ wikisrc/projects/project/microblaze.mdwn	27 Jan 2018 18:31:21 -0000	1.2
@@ -7,6 +7,7 @@
 """
 
 category="ports"
+difficulty="hard"
 
 description="""
 Xilinx MicroBlaze is RISC processort for Xilinx's FPGA chip.
Index: wikisrc/projects/project/pkgsrc_gnome_support.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_gnome_support.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/pkgsrc_gnome_support.mdwn	27 Feb 2014 09:20:48 -0000	1.2
+++ wikisrc/projects/project/pkgsrc_gnome_support.mdwn	27 Jan 2018 18:31:21 -0000	1.3
@@ -11,7 +11,7 @@
 """
 
 category="pkgsrc"
-difficulty="high"
+difficulty="hard"
 duration="6 months"
 
 description="""

Fix incomplete category add
Index: wikisrc/projects/all.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/all.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/projects/all.mdwn	27 Jan 2018 14:49:06 -0000	1.10
+++ wikisrc/projects/all.mdwn	27 Jan 2018 18:22:24 -0000	1.11
@@ -90,7 +90,7 @@
 
 ## Projects without a category definition
 
-[[!map show="title" pages="projects/project/* and tagged(status:active) and !tagged(category:desktop) and !tagged(category:filesystems) and !tagged(category:kernel) and !tagged(category:misc) and !tagged(category:networking) and !tagged(category:pkgsrc) and !tagged(category:ports) and !tagged(category:userland)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and !tagged(category:desktop) and !tagged(category:filesystems) and !tagged(category:kernel) and !tagged(category:misc) and !tagged(category:networking) and !tagged(category:pkgsrc) and !tagged(category:ports) and !tagged(category:userland) and !tagged(category:analyzers)"]]
 
 ## Projects without a difficulty definition
 

Fix category: it's "kernel", not "kern".
Index: wikisrc/projects/project/dtrace-syscall.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/dtrace-syscall.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/dtrace-syscall.mdwn	14 Feb 2015 07:14:12 -0000	1.1
+++ wikisrc/projects/project/dtrace-syscall.mdwn	27 Jan 2018 17:50:17 -0000	1.2
@@ -6,7 +6,7 @@
 [tech-kern](mailto:tech-kern@NetBSD.org),
 """
 
-category="kern"
+category="kernel"
 
 description="""
 NetBSD has preliminary DTrace support, so it supports SDT and FBT provider

Add Code Quality Improvement projects to GSOC
Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/projects/gsoc.mdwn	21 Jan 2018 12:56:44 -0000	1.22
+++ wikisrc/projects/gsoc.mdwn	27 Jan 2018 16:48:19 -0000	1.23
@@ -74,6 +74,14 @@
 ## Hard
 [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(gsoc) and tagged(category:userland) and tagged(difficulty:hard)"]]
 
+# Code Quality Improvement projects
+## Easy
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:analyzers) and tagged(difficulty:easy)"]]
+## Medium
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:analyzers) and tagged(difficulty:medium)"]]
+## Hard
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:analyzers) and tagged(difficulty:hard)"]]
+
 # pkgsrc projects
 
 ## Easy

Mark kasan as hard
Index: wikisrc/projects/project/kasan.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/kasan.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/kasan.mdwn	27 Jan 2018 15:19:45 -0000	1.2
+++ wikisrc/projects/project/kasan.mdwn	27 Jan 2018 16:43:18 -0000	1.3
@@ -11,7 +11,7 @@
 """
 
 category="analyzers"
-difficulty="medium"
+difficulty="hard"
 duration="3 months"
 
 description="""

done
Index: wikisrc/projects/project/x86_smap_smep.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/x86_smap_smep.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/x86_smap_smep.mdwn	12 Oct 2014 08:15:38 -0000	1.1
+++ wikisrc/projects/project/x86_smap_smep.mdwn	27 Jan 2018 15:35:09 -0000	1.2
@@ -9,6 +9,7 @@
 
 category="ports"
 difficulty="medium"
+done_by="Maxime Villard"
 
 description="""
 On x86 CPUs, NetBSD currently maps the currently running userland process inside kernel VA.

change # to *
Index: wikisrc/projects/project/libfuzzer.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/libfuzzer.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/libfuzzer.mdwn	27 Jan 2018 15:15:39 -0000	1.1
+++ wikisrc/projects/project/libfuzzer.mdwn	27 Jan 2018 15:22:49 -0000	1.2
@@ -21,9 +21,9 @@
 
 Milestones:
 
-# Ensure completeness of the toolchain in the basesystem.
-# Add a new option for building the basesystem utilities with libFuzzer.
-# Finish the integration and report bugs.
+* Ensure completeness of the toolchain in the basesystem.
+* Add a new option for building the basesystem utilities with libFuzzer.
+* Finish the integration and report bugs.
 
 """
 ]]
Index: wikisrc/projects/project/pkgsrc-sanitizers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc-sanitizers.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/pkgsrc-sanitizers.mdwn	27 Jan 2018 15:15:39 -0000	1.1
+++ wikisrc/projects/project/pkgsrc-sanitizers.mdwn	27 Jan 2018 15:22:49 -0000	1.2
@@ -30,9 +30,9 @@
 
 Milestones:
 
-# Ensure the availability of the toolchain and prebuilt userland with the sanitizers.
-# Add new option in pkgsrc to build the packages with a each sanitizer.
-# Build the packages and report problems and bugs.
+* Ensure the availability of the toolchain and prebuilt userland with the sanitizers.
+* Add new option in pkgsrc to build the packages with a each sanitizer.
+* Build the packages and report problems and bugs.
 
 """
 ]]
Index: wikisrc/projects/project/safestack.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/safestack.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/safestack.mdwn	27 Jan 2018 15:15:40 -0000	1.1
+++ wikisrc/projects/project/safestack.mdwn	27 Jan 2018 15:22:49 -0000	1.2
@@ -21,10 +21,10 @@
 
 Milestones:
 
-# Ensure completeness of the toolchain in the basesystem.
-# Add a new option for building the basesystem utilities with SafeStack.
-# Finish the integration and report bugs.
-# Research SafeStack for pkgsrc.
+* Ensure completeness of the toolchain in the basesystem.
+* Add a new option for building the basesystem utilities with SafeStack.
+* Finish the integration and report bugs.
+* Research SafeStack for pkgsrc.
 
 """
 ]]
Index: wikisrc/projects/project/scudo.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/scudo.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/scudo.mdwn	27 Jan 2018 15:15:40 -0000	1.1
+++ wikisrc/projects/project/scudo.mdwn	27 Jan 2018 15:22:49 -0000	1.2
@@ -21,10 +21,10 @@
 
 Milestones:
 
-# Ensure completeness of the toolchain in the basesystem.
-# Add a new option for building the basesystem utilities with Scudo.
-# Finish the integration and report bugs.
-# Research Scudo for pkgsrc.
+* Ensure completeness of the toolchain in the basesystem.
+* Add a new option for building the basesystem utilities with Scudo.
+* Finish the integration and report bugs.
+* Research Scudo for pkgsrc.
 
 """
 ]]
Index: wikisrc/projects/project/static-analyzers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/static-analyzers.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/static-analyzers.mdwn	27 Jan 2018 15:15:40 -0000	1.1
+++ wikisrc/projects/project/static-analyzers.mdwn	27 Jan 2018 15:22:49 -0000	1.2
@@ -21,9 +21,9 @@
 
 Milestones:
 
-# Consult and research the available tools.
-# Integrate the tools for the purposes of the NetBSD project.
-# Scan the sources, report bugs, if possible fix the problems, or file bug reports
+* Consult and research the available tools.
+* Integrate the tools for the purposes of the NetBSD project.
+* Scan the sources, report bugs, if possible fix the problems, or file bug reports
 
 """
 ]]
Index: wikisrc/projects/project/syzkaller.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/syzkaller.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/syzkaller.mdwn	27 Jan 2018 15:15:40 -0000	1.1
+++ wikisrc/projects/project/syzkaller.mdwn	27 Jan 2018 15:22:49 -0000	1.2
@@ -21,9 +21,9 @@
 
 Milestones:
 
-# Ensure completeness of the current support.
-# Execute the fuzzer and gather reports, narrow down problems, translate to C reproducers.
-# Add missing features, fix bugs in the NetBSD support.
+* Ensure completeness of the current support.
+* Execute the fuzzer and gather reports, narrow down problems, translate to C reproducers.
+* Add missing features, fix bugs in the NetBSD support.
 
 """
 ]]
Index: wikisrc/projects/project/ubsan.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ubsan.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/ubsan.mdwn	27 Jan 2018 15:15:40 -0000	1.1
+++ wikisrc/projects/project/ubsan.mdwn	27 Jan 2018 15:22:49 -0000	1.2
@@ -24,12 +24,12 @@
 
 Milestones:
 
-# Build manually the NetBSD kernel against UBSan. Port the needed code from Linux (don't violate the license).
-# Ensure that we don't violate the license - either ask for relicense or reimplement the needed code. There is little code for KUBSan.
-# Integrate KUBSan with the kernel configuration.
-# Execute the kernel, attempt to boot to shell.
-# Run ATF tests against the kernel.
-# Report bugs.
+* Build manually the NetBSD kernel against UBSan. Port the needed code from Linux (don't violate the license).
+* Ensure that we don't violate the license - either ask for relicense or reimplement the needed code. There is little code for KUBSan.
+* Integrate KUBSan with the kernel configuration.
+* Execute the kernel, attempt to boot to shell.
+* Run ATF tests against the kernel.
+* Report bugs.
 
 """
 ]]

Index: wikisrc/projects/project/kasan.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/kasan.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/kasan.mdwn	27 Jan 2018 15:15:39 -0000	1.1
+++ wikisrc/projects/project/kasan.mdwn	27 Jan 2018 15:19:45 -0000	1.2
@@ -24,12 +24,12 @@
 
 Milestones:
 
-# Build manually the NetBSD kernel against KASan.
-# Ensure that we don't violate the license - either ask for relicense or reimplement the needed code. There are around 2k LOC. This code should be relicensed.
-# Integrate KASan with the kernel configuration.
-# Execute the kernel, attempt to boot to shell.
-# Run ATF tests against the kernel.
-# Report bugs.
+* Build manually the NetBSD kernel against KASan.
+* Ensure that we don't violate the license - either ask for relicense or reimplement the needed code. There are around 2k LOC. This code should be relicensed.
+* Integrate KASan with the kernel configuration.
+* Execute the kernel, attempt to boot to shell.
+* Run ATF tests against the kernel.
+* Report bugs.
 
 """
 ]]

add analyzer category projects
--- /dev/null	2018-01-27 15:15:24.000000000 +0000
+++ wikisrc/projects/project/kasan.mdwn	2018-01-27 15:15:57.000000000 +0000
@@ -0,0 +1,37 @@
+[[!template id=project
+
+title="Kernel Address SANitizer"
+
+contact="""
+[tech-kern](mailto:tech-kern@NetBSD.org)
+"""
+
+mentors="""
+[Kamil Rytarowski](mailto:kamil@NetBSD.org)
+"""
+
+category="analyzers"
+difficulty="medium"
+duration="3 months"
+
+description="""
+
+Port LLVM and/or GCC kernel ASan pieces to the NetBSD/amd64 kernel.
+Integrate the support with the toolchain inside src/.
+Add support for a new kernel option (and perhaps configuration) KASAN.
+
+The toolchain support on the LLVM side is done. GCC should work too.
+
+Milestones:
+
+# Build manually the NetBSD kernel against KASan.
+# Ensure that we don't violate the license - either ask for relicense or reimplement the needed code. There are around 2k LOC. This code should be relicensed.
+# Integrate KASan with the kernel configuration.
+# Execute the kernel, attempt to boot to shell.
+# Run ATF tests against the kernel.
+# Report bugs.
+
+"""
+]]
+
+[[!tag gsoc]]
--- /dev/null	2018-01-27 15:15:24.000000000 +0000
+++ wikisrc/projects/project/libfuzzer.mdwn	2018-01-27 15:15:57.000000000 +0000
@@ -0,0 +1,31 @@
+[[!template id=project
+
+title="Integrate libFuzzer with the basesystem"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Kamil Rytarowski](mailto:kamil@NetBSD.org)
+"""
+
+category="analyzers"
+difficulty="medium"
+duration="3 months"
+
+description="""
+
+Integrate the LLVM libFuzzer with the basesystem framework.
+Build and execute base programs against libFuzzer.
+
+Milestones:
+
+# Ensure completeness of the toolchain in the basesystem.
+# Add a new option for building the basesystem utilities with libFuzzer.
+# Finish the integration and report bugs.
+
+"""
+]]
+
+[[!tag gsoc]]
--- /dev/null	2018-01-27 15:15:24.000000000 +0000
+++ wikisrc/projects/project/pkgsrc-sanitizers.mdwn	2018-01-27 15:15:57.000000000 +0000
@@ -0,0 +1,40 @@
+[[!template id=project
+
+title="Integrate LLVM/GCC Sanitizers with pkgsrc"
+
+contact="""
+[tech-pkg](mailto:tech-pkg@NetBSD.org)
+"""
+
+mentors="""
+[Kamil Rytarowski](mailto:kamil@NetBSD.org)
+"""
+
+category="analyzers"
+difficulty="medium"
+duration="3 months"
+
+description="""
+
+Add support in the pkgsrc framework for building packages with sanitizers.
+
+Expected sanitizer options:
+
+- Address (ASan),
+- Memory (MSan),
+- MemoryWithOrigin (MSan with tracking the origin)
+- Undefined (UBSan),
+- Thread (TSan),
+- Address;Undefined (ASan & UBSan)
+- "" (empty string) - the default option
+
+Milestones:
+
+# Ensure the availability of the toolchain and prebuilt userland with the sanitizers.
+# Add new option in pkgsrc to build the packages with a each sanitizer.
+# Build the packages and report problems and bugs.
+
+"""
+]]
+
+[[!tag gsoc]]
--- /dev/null	2018-01-27 15:15:24.000000000 +0000
+++ wikisrc/projects/project/safestack.mdwn	2018-01-27 15:15:57.000000000 +0000
@@ -0,0 +1,32 @@
+[[!template id=project
+
+title="Integrate SafeStack with the basesystem"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Kamil Rytarowski](mailto:kamil@NetBSD.org)
+"""
+
+category="analyzers"
+difficulty="medium"
+duration="3 months"
+
+description="""
+
+Integrate the LLVM SafeStack with the basesystem framework.
+Build and execute base programs against libFuzzer.
+
+Milestones:
+
+# Ensure completeness of the toolchain in the basesystem.
+# Add a new option for building the basesystem utilities with SafeStack.
+# Finish the integration and report bugs.
+# Research SafeStack for pkgsrc.
+
+"""
+]]
+
+[[!tag gsoc]]
--- /dev/null	2018-01-27 15:15:24.000000000 +0000
+++ wikisrc/projects/project/scudo.mdwn	2018-01-27 15:15:57.000000000 +0000
@@ -0,0 +1,32 @@
+[[!template id=project
+
+title="Integrate Scudo with the basesystem"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Kamil Rytarowski](mailto:kamil@NetBSD.org)
+"""
+
+category="analyzers"
+difficulty="medium"
+duration="3 months"
+
+description="""
+
+Integrate the LLVM Scudo with the basesystem framework.
+Build and execute base programs against Scudo.
+
+Milestones:
+
+# Ensure completeness of the toolchain in the basesystem.
+# Add a new option for building the basesystem utilities with Scudo.
+# Finish the integration and report bugs.
+# Research Scudo for pkgsrc.
+
+"""
+]]
+
+[[!tag gsoc]]
--- /dev/null	2018-01-27 15:15:24.000000000 +0000
+++ wikisrc/projects/project/static-analyzers.mdwn	2018-01-27 15:15:57.000000000 +0000
@@ -0,0 +1,31 @@
+[[!template id=project
+
+title="Reseearch and integrate the static code analyzers with the NetBSD codebase"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Christos Zoulas](mailto:christos@NetBSD.org)

(Diff truncated)
Index: wikisrc/projects/all.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/all.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/projects/all.mdwn	23 Aug 2016 21:10:03 -0000	1.9
+++ wikisrc/projects/all.mdwn	27 Jan 2018 14:49:06 -0000	1.10
@@ -53,6 +53,14 @@
 ## Hard
 [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:desktop) and tagged(difficulty:hard)"]]
 
+# Code Quality Improvement projects
+## Easy
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:analyzers) and tagged(difficulty:easy)"]]
+## Medium
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:analyzers) and tagged(difficulty:medium)"]]
+## Hard
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:analyzers) and tagged(difficulty:hard)"]]
+
 # pkgsrc projects
 ## Easy
 [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:pkgsrc) and tagged(difficulty:easy)"]]

add 2017 results and update Google GSoC link
Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/projects/gsoc.mdwn	20 Jan 2017 06:27:36 -0000	1.21
+++ wikisrc/projects/gsoc.mdwn	21 Jan 2018 12:56:44 -0000	1.22
@@ -2,16 +2,17 @@
 
 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),
-[2008](http://www.netbsd.org/foundation/press/soc2008-summary.html),
-[2009](http://www.netbsd.org/foundation/press/soc2009.html),
-[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) and
-[2016](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2016)).
+[2005](https://www.netbsd.org/foundation/press/soc-summary.html),
+[2006](https://www.netbsd.org/foundation/press/soc2006-summary.html),
+[2007](https://www.netbsd.org/foundation/press/soc2007-summary.html),
+[2008](https://www.netbsd.org/foundation/press/soc2008-summary.html),
+[2009](https://www.netbsd.org/foundation/press/soc2009.html),
+[2010](https://blog.netbsd.org/tnf/entry/google_summer_of_code_2010),
+[2011](https://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of),
+[2012](https://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of1),
+[2013](https://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2),
+[2016](https://blog.netbsd.org/tnf/entry/google_summer_of_code_2016) and
+[2017](https://blog.netbsd.org/tnf/entry/google_summer_of_code_2017)).
 
 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

we already ran this
Index: wikisrc/projects/project/anita-vms.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/anita-vms.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/project/anita-vms.mdwn	3 Apr 2017 14:34:31 -0000	1.6
+++ wikisrc/projects/project/anita-vms.mdwn	21 Jan 2018 12:05:19 -0000	1.7
@@ -8,6 +8,7 @@
 
 mentors="""
 """
+done_by=utkarsh009
 
 category="userland"
 difficulty="medium"

add comments about kernel options for wm
Index: wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn	18 Jan 2018 08:58:02 -0000	1.9
+++ wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn	18 Jan 2018 23:11:56 -0000	1.10
@@ -22,7 +22,7 @@
   <td>TX_LOCK(spin mutex) + sc_stopping flag</td>
   <td>CORE_LOCK(spin mutex)+sc_stopping flag</td>
   <td>use CORE_LOCK(spin mutex) and TX_LOCK(spin mutex) partially</td>
-  <td>Yes</td>
+  <td>Yes by default. It can be changed by kernel options. See wm.4.</td>
   <td>TX and RX differently</td>
   <td>TX_LOCK(mutex) and check sc_stopping in the beginning</td>
   <td>Yes</td>

wm(4) already use softint-based TX and RX.
Index: wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn	20 Jul 2016 04:14:25 -0000	1.8
+++ wikisrc/users/msaitoh/Comparison_of_implementations_of_Ethernet_drivers.mdwn	18 Jan 2018 08:58:02 -0000	1.9
@@ -22,7 +22,7 @@
   <td>TX_LOCK(spin mutex) + sc_stopping flag</td>
   <td>CORE_LOCK(spin mutex)+sc_stopping flag</td>
   <td>use CORE_LOCK(spin mutex) and TX_LOCK(spin mutex) partially</td>
-  <td>No</td>
+  <td>Yes</td>
   <td>TX and RX differently</td>
   <td>TX_LOCK(mutex) and check sc_stopping in the beginning</td>
   <td>Yes</td>

Rephrase so it doesn't sound like the key is stored on the disk.
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/security/cgdroot.mdwn	10 Feb 2017 11:10:53 -0000	1.14
+++ wikisrc/security/cgdroot.mdwn	14 Jan 2018 04:12:25 -0000	1.15
@@ -19,7 +19,7 @@
 * a GENERIC kernel
 * the `cgdroot.kmod` kernel module
 * the configuration file for CGD, `cgd.conf`
-* the encryption key for the volume to start from, named after its partition (like `wd0f`)
+* the CGD parameters file for the volume, named after its partition (like `wd0f`), which determines how the encryption key is derived and verified
 
 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.
 

Add a few words about what has been done already
Index: wikisrc/projects/project/cross-bootstrapping.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/cross-bootstrapping.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/cross-bootstrapping.mdwn	6 Nov 2011 14:48:47 -0000	1.3
+++ wikisrc/projects/project/cross-bootstrapping.mdwn	13 Jan 2018 15:29:25 -0000	1.4
@@ -32,5 +32,8 @@
 This project requires good understanding of cross-development,
 some knowledge of NetBSD build process or ability to create cross-development toolchain,
 and familiarity with pkgsrc bootstrapping.
+
+Note: basic infrastructure for this exists as part of various previous
+GSoC projects. General testing is lacking.
 """
 ]]

user-destdir has been the default for a long time and most packages use it
Index: wikisrc/projects/project/pkgsrc-unpriv.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc-unpriv.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/pkgsrc-unpriv.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/pkgsrc-unpriv.mdwn	13 Jan 2018 15:27:00 -0000	1.3
@@ -8,6 +8,7 @@
 
 category="pkgsrc"
 difficulty="medium"
+done_by="joerg"
 
 description="""
 To create packages that are usable by anyone, pkgsrc currently requires that

Index: wikisrc/projects/project/scsipi-locking.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/scsipi-locking.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/scsipi-locking.mdwn	16 Feb 2015 05:16:15 -0000	1.1
+++ wikisrc/projects/project/scsipi-locking.mdwn	13 Jan 2018 15:07:11 -0000	1.2
@@ -9,6 +9,7 @@
 category="filesystems"
 difficulty="medium"
 duration="1 month"
+done_by="mlelstv"
 
 description="""
 Currently the scsipi subsystem is kernel-locked.

Index: wikisrc/projects/project/pkgsrc-test-depends.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc-test-depends.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/pkgsrc-test-depends.mdwn	2 Jun 2016 05:26:30 -0000	1.1
+++ wikisrc/projects/project/pkgsrc-test-depends.mdwn	13 Jan 2018 12:50:12 -0000	1.2
@@ -9,6 +9,7 @@
 category="pkgsrc"
 difficulty="medium"
 duration="3-6 weeks"
+done_by="joerg"
 
 description="""
 

add link to head llvm builds
Index: wikisrc/tutorials/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/clang.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/tutorials/clang.mdwn	31 Dec 2017 13:52:57 -0000	1.3
+++ wikisrc/tutorials/clang.mdwn	4 Jan 2018 20:45:01 -0000	1.4
@@ -37,3 +37,10 @@
 you can refrain from building gcc, by additionally adding:
 
     MKGCC=no
+
+# status
+
+On NetBSD-current, clang builds successfully on several architectures.
+These builds are with all three of the above flags enabled.
+
+https://releng.netbsd.org/builds/HEAD-llvm/

Add data. Promote sections
Index: wikisrc/pkgsrc/gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/gcc.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/pkgsrc/gcc.mdwn	1 Jan 2018 23:27:13 -0000	1.11
+++ wikisrc/pkgsrc/gcc.mdwn	4 Jan 2018 20:37:58 -0000	1.12
@@ -10,7 +10,7 @@
 freely takes content from extensive mailinglist discussions, and
 attempts to follow the rough consensus that has emerged.
 
-## Base system gcc vs pkgsrc gcc
+# Base system gcc vs pkgsrc gcc
 
 Systems using gcc (e.g. NetBSD) have a compiler as /usr/bin/gcc, and
 this is usable by pkgsrc without any bootstrapping activity.  One can
@@ -36,7 +36,7 @@
     should be linked with the higher version because the support
     library is backwards compatible but not forward compatible.
 
-## Specific constraints and requirements
+# Specific constraints and requirements
 
 This section attempts to gather all the requirements.
 
@@ -71,7 +71,7 @@
 
   - The compiler selection logic should be understandable and not brittle.
 
-## Design
+# Design
 
 The above requirements could in theory be satisfied in many ways, but
 most of them are too complicated.  We present a design that aims to be
@@ -156,9 +156,9 @@
     linking with a C++ compiler.  This is not a change from the
     current situation.
 
-## Remaining issues
+# Remaining issues
 
-### gcc dependencies introduction
+## gcc dependencies introduction
 
 Because gcc can have dependencies, there could be packages built with
 the system compiler that are then later used with the chosen version.
@@ -179,14 +179,14 @@
 \todo: Consider failing if optins that we want one way are another,
 when bootstrapping.
 
-### managing gcc dependencies
+## managing gcc dependencies
 
 There are multiple paths forward.
 
 \todo Choose one.  Straw proposal is "Don't worry" and recursive
 variable for the initial implementation.
 
-#### Separate prefix
+### Separate prefix
 
 Build compilers in a separate prefix, or a subprefix, so that the
 compiler and the packages needed to build it will not be used by any
@@ -194,7 +194,7 @@
 package one way in bootstrap and another not in bootstrap, at the cost
 of two builds and writing the separate-prefix code.
 
-#### Don't worry
+### Don't worry
 
 Don't worry that packages used to bootstrap the needed compiler are
 compiled with an older compiler.  Don't worry that they might be
@@ -202,7 +202,7 @@
 deal with it.  This requires choosing an approach to omit compiler
 selection logic when building the compiler:
 
-##### Mark bootstrap packages
+#### Mark bootstrap packages
 
 Mark packages used to build gcc as PKGSRC_GCC_BOOTSTRAP=yes.
 Conditionalize this on OPSYS if necessary.  Don't force the compiler
@@ -210,14 +210,14 @@
 
 Alternatively, manage a per-OS list of packages in a central mk file.
 
-##### Pass a recursive variable
+#### Pass a recursive variable
 
 As above, but set PKGSRC_GCC_BOOTSTRAP=yes in the evniroment of the
 call to build the compiler, so that all dependencies inherit
 permission to skip compiler selection logic.  (Alternatively, use some
 other mechanism such as passing a make variable explicitly.)
 
-### Differing GCC and GXX versions
+## Differing GCC and GXX versions
 
 Perhaps it is a mistake to allow the chosen GCC and GXX versions to
 differ.  If we require them to be the same, then essentially all
@@ -225,7 +225,7 @@
 bootstrap the compiler.  For now, we allow them to differ and will
 permit the defaults to differ.
 
-### gcc versions and number of buildable packages
+## gcc versions and number of buildable packages
 
 A gcc version that is too old will not build a number of packages.
 Anything older than 4.8 fails for c++11.  4.8 fails on some c++11
@@ -246,7 +246,7 @@
 Therefore, the current answer to "What is the best version to use" is
 5.
 
-### Default versions for various systems
+## Default versions for various systems
 
 Note that if for any particular system's set of installed packages (or
 bulk build), a newer gcc has to be built, it does not hurt to have
@@ -278,7 +278,7 @@
 that it supports (almost all) C++14 programs.  Our current definiton
 of new enough is gcc 5.
 
-### Limited mixed versions
+## Limited mixed versions
 
 One approach would be to allow limited mixed versions, where
 individual programs could force a specific version to be bootstrapped
@@ -290,7 +290,7 @@
 too much complexity for avoiding building a newer compiler in limited
 situations.
 
-### Fortran
+## Fortran
 
 Fortran support is currently somewhat troubled..  It seems obvious to
 extend to PGKSRC_GFORTRAN_VERSION, and have that match
@@ -302,7 +302,7 @@
 
 \todo Discuss.
 
-### C++ libraries used by C programs
+## C++ libraries used by C programs
 
 The choice of one version for C++ and one for C (e.g. 5, 4.8 on
 netbsd-7) breaks down if a C program links against a library that is
@@ -314,7 +314,7 @@
 PKGSRC_GXX_VERSION to be used.  Or decide that this is a good reason
 to really just have one compiler version.
 
-## Path forward
+# Path forward
 
 (This assumes per-package marking of bootstrap packages, but is
 reasonably obviously extended to the other schemes.)
@@ -336,8 +336,22 @@
    and that PKGSRC_GXX_VERSION is the base system version if >= 5, and
    otherwise 5.  Implement these in platform.mk as they are tested.
 
-### Later steps
+## Later steps
 
  - Address fortran.  Probably add PKGSRC_GFORTRAN_VERSION, after
    determining how Fortran, C and C++ interact with library ABI
    compatibility.
+
+# Data
+
+This section has data points that are relevant to the discussion.
+
+## amd64/i386
+
+It is believed that pkgsrc gcc generally builds on these systems.
+gcc6 builds on netbsd-5/i386.
+
+## macppc
+
+On macppc, [lang/gcc5 fails on netsbd-6 and netbsd-7, but succeeds on
+netbsd-8](https://mail-index.netbsd.org/tech-pkg/2018/01/03/msg019260.html).

adjust nits about acceptbale versions
Index: wikisrc/pkgsrc/gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/gcc.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/pkgsrc/gcc.mdwn	1 Jan 2018 23:18:19 -0000	1.10
+++ wikisrc/pkgsrc/gcc.mdwn	1 Jan 2018 23:27:13 -0000	1.11
@@ -255,12 +255,10 @@
 When the base system is old (e.g., gcc 4.5 in NetBSD 6, or 4.1, in
 NetBSD 5), then it is clear that a newer version must be built.  For
 these, PKGSRC_GXX_VERSION should default to a newish gcc, avoiding
-being so new as to cause building issues.  Currently, gcc5 is probably
-a good choice, with gcc6 compiling significantly but not vastly fewer
-packages.  PKGSRC_GCC_VERSION should probably default to the system
-version if it can build all C99 programs, or match PKGSRC_GXX_VERSION,
-if the system version is too old.  Perhaps gcc 4.5 would be used, but
-4.1 not used.  \todo Discuss.
+being so new as to cause building issues.  PKGSRC_GCC_VERSION should
+probably default to the system version if it can build all C99
+programs, or match PKGSRC_GXX_VERSION, if the system version is too
+old.  Perhaps gcc 4.5 would be used, but 4.1 not used.  \todo Discuss.
 
 When the base system is almost new enough, the decision about the
 default is more complicated.  A key example is gcc 4.8, found in
@@ -269,7 +267,7 @@
 firefox failing, as well as all c++14 programs.  Another is to choose
 4.9, but this makes little sense because c++14 programs will still
 fail, and the general rule of moving to the most recent
-generally-acceptable version applies, which currently leads to gcc6.
+generally-acceptable version applies, which currently leads to gcc5.
 This is in effect a declaration that "almost new enough" does not
 count as new enough.  Thus the plan for NetBSD 7 is to set
 PKGSRC_GCC_VERSION to 4.8 and PKGSRC_GXX_VERSION to 5.

Add Jason's package count data
Index: wikisrc/pkgsrc/gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/gcc.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/pkgsrc/gcc.mdwn	31 Dec 2017 17:15:37 -0000	1.9
+++ wikisrc/pkgsrc/gcc.mdwn	1 Jan 2018 23:18:19 -0000	1.10
@@ -231,10 +231,17 @@
 Anything older than 4.8 fails for c++11.  4.8 fails on some c++11
 packages, such as firefox and glibmm.
 
-A version that is too new also fails to build packages.  Analyses
-posted to tech-pkg indicate that 5 is close to 4.9 in the number of
-packages built, and that moving to 6 causes hundreds of additional
-failures.
+A version that is too new also fails to build packages.  Jason Bacon
+posted counts to tech-pkg indicate that 5 is close to 4.8 in the
+number of packages built, and that moving to 6 causes hundreds of
+additional failures.  (Keep in mind that currently, building with 4.8
+will build 4.9 for firefox, but in the future will not.)
+
+    www/pkgsrc/packages/sharedapps/pkg-2017Q3/RHEL6-gcc48/All	16461
+    www/pkgsrc/packages/sharedapps/pkg-2017Q3/RHEL6-gcc6/All	15849
+
+    www/pkgsrc/packages/sharedapps/pkg-2017Q3/RHEL7-gcc48/All	16414
+    www/pkgsrc/packages/sharedapps/pkg-2017Q3/RHEL7-gcc5/All	16338
 
 Therefore, the current answer to "What is the best version to use" is
 5.

missed 2018 update
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- wikisrc/templates/page.tmpl	18 Jun 2017 20:07:00 -0000	1.34
+++ wikisrc/templates/page.tmpl	1 Jan 2018 03:51:04 -0000	1.35
@@ -279,7 +279,7 @@
       <span class="footcopy"><a href="about/disclaimer.html">
         Disclaimer</a> |
         <span class="copyright">
-          Copyright &copy; 1994-2017 The NetBSD Foundation, Inc.
+          Copyright &copy; 1994-2018 The NetBSD Foundation, Inc.
         </span>
         ALL
         RIGHTS RESERVED. <br /> NetBSD<sup>&reg;</sup> is a registered

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

Adjust based on list discussion
Index: wikisrc/pkgsrc/gcc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc/gcc.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/pkgsrc/gcc.mdwn	30 Dec 2017 02:01:59 -0000	1.8
+++ wikisrc/pkgsrc/gcc.mdwn	31 Dec 2017 17:15:37 -0000	1.9
@@ -18,7 +18,7 @@
 in a compiler within ${PREFIX}, e.g. /usr/pkg/gcc6/bin/gcc.  This
 compiler can then be used to compile other packages.
 
-The Issue with using base system gcc is typically that it is too old,
+The issue with using base system gcc is typically that it is too old,
 such as gcc 4.5 with NetBSD 6, which cannot compile c++11.  Another
 example is gcc 4.8 with NetBSD 7.  While this can compile most c++11
 programs, it cannot be used for firefox or glibmm (and therefore any
@@ -26,6 +26,7 @@
 
 Issues when using pkgsrc gcc are that
 
+  - on some platforms, pkgsrc gcc does not build and work
   - it must be bootstrapped, requiring compiling a number of packages
     with the system compiler
   - C++ packages that are linked together should be built with the
@@ -65,6 +66,9 @@
     clang, when set to use GCC, at least as well as the current
     scheme.  It is desirable for this logic to work on NetBSD 5.
 
+  - All systems should work at least as well as they do before
+    implementation of new compiler selection logic.
+
   - The compiler selection logic should be understandable and not brittle.
 
 ## Design
@@ -84,14 +88,20 @@
     4.9.
 
   - A user-settable variable PKGSRC_GCC_VERSION will declare the
-    version of gcc to be used for C programs, with an OS- and
-    version--specific default.
+    version of gcc to be used for C programs, with an OS-,
+    version- and architeture- specific default.
 
   - A user-settable variable PKGSRC_GXX_VERSION will declare the
-    version of gcc to be used for all C++ programs, again with an OS-
-    and version-specific default.  It must be at least
+    version of gcc to be used for all C++ programs, again with an OS-,
+    version- and architeture-specific default.  It must be at least
     PKGSRC_GCC_VERSION.
 
+  - If PKGSRC_GCC_VERSION and PKGSRC_GXX_VERSION are not set, the
+    system will behave much as before.  As a possible exception,
+    builds may still fail if the required version is greater than the
+    base system version.  So far the only known reason to avoid
+    setting these variable is if pkgsrc gcc cannot be built.
+
   - Each of c99, c++, c++11, and c++14 will be associated with a
     minimum gcc version, such that almost all programs declaring that
     language can be built with that version.  (This avoids issues of
@@ -132,6 +142,13 @@
     approach is possible inconsistency with gcc's dependencies being
     built with the base compiler and used later.
 
+    As an alternative, we store lists of bootstrap packages in a
+    variable, because it will vary with OS and version, and with
+    PREFER_PKGSRC settings.
+
+    As a third alternative, we pass a GCC_BOOTSTRAPPING variable
+    recursively.  This is easier but less consistent.
+
   - We hope that the chosen version can be built using the base system
     version, and hope to avoid multi-stage bootstrapping.
 
@@ -149,7 +166,9 @@
 will be less serious than the current situation where all c++11
 programs fail to build on NetBSD 6).
 
-\todo: Change gcc 4.8 and 4.9 to enable gcc-inplace-math by default.
+\todo: Perhaps change gcc 4.8 and 4.9 to enable gcc-inplace-math by
+default.  Perhaps decide that if we want to build gcc, we want to
+build 5 or 6, and 4.9 is no longer of interest as a bootstrap target.
 
 \todo: Analyze what build-time and install-time dependencies actually
 exist.  Include old GNU/Linux in this analysis.
@@ -220,8 +239,6 @@
 Therefore, the current answer to "What is the best version to use" is
 5.
 
-\todo Check this with Jason Bacon.
-
 ### Default versions for various systems
 
 Note that if for any particular system's set of installed packages (or
@@ -280,7 +297,7 @@
 
 \todo Discuss.
 
-### C++ programs used by C programs
+### C++ libraries used by C programs
 
 The choice of one version for C++ and one for C (e.g. 5, 4.8 on
 netbsd-7) breaks down if a C program links against a library that is
@@ -294,6 +311,9 @@
 
 ## Path forward
 
+(This assumes per-package marking of bootstrap packages, but is
+reasonably obviously extended to the other schemes.)
+
  - Modify all gcc packages to have minimal dependencies, and to add
    PKGSRC_GCC_BOOTSTRAP.
 
@@ -303,14 +323,16 @@
  - Modify the compiler selection logic for LANGUAGES= to fail if
    PKGSRC_GCC_VERSION/PKGSRC_GXX_VERSION is not new enough.
 
- - Modify the compiler selection logic for GCC_REQD to fail if the
-   version of GCC/GXX is not new enough.
+ - Modify the compiler selection logic for GCC_REQD to fail if
+   PKGSRC_GCC_VERSION/PKGSRC_GXX_VERSION is not new enough.
 
  - Decide on defaults.  The straw proposal is that PKGSRC_GCC_VERSION
    is the base system version if >= 4.5 (or 4.4?), and otherwise 5,
    and that PKGSRC_GXX_VERSION is the base system version if >= 5, and
-   otherwise 5.
+   otherwise 5.  Implement these in platform.mk as they are tested.
 
 ### Later steps
 
- - Address fortran.
+ - Address fortran.  Probably add PKGSRC_GFORTRAN_VERSION, after
+   determining how Fortran, C and C++ interact with library ABI
+   compatibility.

Fix typo. Remove todo, setting HAVE_LLVM is enough.
Index: wikisrc/tutorials/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/clang.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/tutorials/clang.mdwn	30 Dec 2017 18:40:29 -0000	1.2
+++ wikisrc/tutorials/clang.mdwn	31 Dec 2017 13:52:57 -0000	1.3
@@ -1,4 +1,4 @@
-This page explainsse how to use clang with the NetBSD base system.
+This page explains how to use clang with the NetBSD base system.
 See also [how to use clang to build packages](../pkgsrc/clang/).
 
 \todo: review this entire page.
@@ -31,9 +31,6 @@
 
 to cause clang to be used instead of gcc.
 
-\todo It is not 100% clear if this stage works, vs having to set
-MKGCC=no also.
-
 # Not building gcc
 
 On a system that builds clang and uses it to build the base system,

Fix wiki link
Index: wikisrc/tutorials/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/clang.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/tutorials/clang.mdwn	30 Dec 2017 18:34:03 -0000	1.1
+++ wikisrc/tutorials/clang.mdwn	30 Dec 2017 18:40:29 -0000	1.2
@@ -1,5 +1,5 @@
 This page explainsse how to use clang with the NetBSD base system.
-See also [how to use clang to build packages](tutorials/pkgsrc/clang/).
+See also [how to use clang to build packages](../pkgsrc/clang/).
 
 \todo: review this entire page.
 

fix wiki link harder
Index: wikisrc/tutorials/pkgsrc/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/clang.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 18:38:31 -0000	1.7
+++ wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 18:39:12 -0000	1.8
@@ -1,6 +1,6 @@
 # Using clang from the base system
 
-See [clang and the base system](../clang/).
+See [clang and the base system](../../clang/).
 
 When you have a NetBSD built with at least MKLLVM=yes, you can set
 

fix wiki link
Index: wikisrc/tutorials/pkgsrc/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/clang.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 18:37:57 -0000	1.6
+++ wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 18:38:31 -0000	1.7
@@ -1,6 +1,6 @@
 # Using clang from the base system
 
-See [clang and the base system](tutorials/clang/).
+See [clang and the base system](../clang/).
 
 When you have a NetBSD built with at least MKLLVM=yes, you can set
 

Clarify base requirements
Index: wikisrc/tutorials/pkgsrc/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/clang.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 18:36:47 -0000	1.5
+++ wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 18:37:57 -0000	1.6
@@ -17,9 +17,9 @@
 # Using clang from pkgsrc
 
 You can build clang from pkgsrc (lang/clang).  However, it needs
-libstdc++ from the base system, at least from gcc 4.8 or higher.  It
-also depends on cmake, which requires c++11, which needs gcc 4.8 or
-higher.  So this will not work on NetBSD <= 6.
+libstdc++ from the base system, and needs gcc 4.8 or higher.  It also
+depends on cmake, which requires c++11, which needs gcc 4.8 or higher.
+So this will not work on NetBSD <= 6.
 
 Once built, you should (\todo test this) be able to set:
 

Refer to base clang directions
Index: wikisrc/tutorials/pkgsrc/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/clang.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 17:58:58 -0000	1.4
+++ wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 18:36:47 -0000	1.5
@@ -1,17 +1,8 @@
 # Using clang from the base system
 
-When building NetBSD, you can set
+See [clang and the base system](tutorials/clang/).
 
-    MKLLVM=yes
-
-to also build clang and install it, and additionally
-
-    HAVE_LLVM=yes
-    MKGCC=no
-
-if you want to use it to compile NetBSD itself during build.sh.
-
-When you have a NetBSD compiled this way, you can set
+When you have a NetBSD built with at least MKLLVM=yes, you can set
 
     PKGSRC_COMPILER=       clang
     CLANGBASE=             /usr

move clang page to tutorials
--- wikisrc/clang.mdwn	2018-01-17 03:45:24.000000000 +0000
+++ /dev/null	2018-01-17 03:40:50.000000000 +0000
@@ -1,42 +0,0 @@
-This page explainsse how to use clang with the NetBSD base system.
-See also [how to use clang to build packages](tutorials/pkgsrc/clang/).
-
-\todo: review this entire page.
-
-Since NetBSD 6, the base system has included clang, but it is not
-built or used by default.
-
-\todo Explain if there are or aren't plans to enable it by default, or
-to switch, keeping in mind that compiler support varies by architecture.
-
-There are three steps that can be taken with clang; each depends on the previous.
-
-# Building clang
-
-To build clang as part of the build, set
-
-    MKLLVM=yes
-
-in mk.conf before running "build.sh release".
-
-This will build clang, which will appear in /usr/bin/clang and also
-build libraries that clang needs.  NetBSD itself will not be built
-with clang, but you will be able to use clang to build programs.
-
-# Using clang to build the NetBSD base system
-
-In addition, set
-
-    HAVE_LLVM=yes
-
-to cause clang to be used instead of gcc.
-
-\todo It is not 100% clear if this stage works, vs having to set
-MKGCC=no also.
-
-# Not building gcc
-
-On a system that builds clang and uses it to build the base system,
-you can refrain from building gcc, by additionally adding:
-
-    MKGCC=no
--- /dev/null	2018-01-17 03:40:50.000000000 +0000
+++ wikisrc/tutorials/clang.mdwn	2018-01-17 03:45:24.000000000 +0000
@@ -0,0 +1,42 @@
+This page explainsse how to use clang with the NetBSD base system.
+See also [how to use clang to build packages](tutorials/pkgsrc/clang/).
+
+\todo: review this entire page.
+
+Since NetBSD 6, the base system has included clang, but it is not
+built or used by default.
+
+\todo Explain if there are or aren't plans to enable it by default, or
+to switch, keeping in mind that compiler support varies by architecture.
+
+There are three steps that can be taken with clang; each depends on the previous.
+
+# Building clang
+
+To build clang as part of the build, set
+
+    MKLLVM=yes
+
+in mk.conf before running "build.sh release".
+
+This will build clang, which will appear in /usr/bin/clang and also
+build libraries that clang needs.  NetBSD itself will not be built
+with clang, but you will be able to use clang to build programs.
+
+# Using clang to build the NetBSD base system
+
+In addition, set
+
+    HAVE_LLVM=yes
+
+to cause clang to be used instead of gcc.
+
+\todo It is not 100% clear if this stage works, vs having to set
+MKGCC=no also.
+
+# Not building gcc
+
+On a system that builds clang and uses it to build the base system,
+you can refrain from building gcc, by additionally adding:
+
+    MKGCC=no

Add page about clang and the base system
--- /dev/null	2018-01-17 03:40:50.000000000 +0000
+++ wikisrc/clang.mdwn	2018-01-17 03:45:24.000000000 +0000
@@ -0,0 +1,42 @@
+This page explainsse how to use clang with the NetBSD base system.
+See also [how to use clang to build packages](tutorials/pkgsrc/clang/).
+
+\todo: review this entire page.
+
+Since NetBSD 6, the base system has included clang, but it is not
+built or used by default.
+
+\todo Explain if there are or aren't plans to enable it by default, or
+to switch, keeping in mind that compiler support varies by architecture.
+
+There are three steps that can be taken with clang; each depends on the previous.
+
+# Building clang
+
+To build clang as part of the build, set
+
+    MKLLVM=yes
+
+in mk.conf before running "build.sh release".
+
+This will build clang, which will appear in /usr/bin/clang and also
+build libraries that clang needs.  NetBSD itself will not be built
+with clang, but you will be able to use clang to build programs.
+
+# Using clang to build the NetBSD base system
+
+In addition, set
+
+    HAVE_LLVM=yes
+
+to cause clang to be used instead of gcc.
+
+\todo It is not 100% clear if this stage works, vs having to set
+MKGCC=no also.
+
+# Not building gcc
+
+On a system that builds clang and uses it to build the base system,
+you can refrain from building gcc, by additionally adding:
+
+    MKGCC=no

update notes
Index: wikisrc/tutorials/pkgsrc/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/clang.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 17:51:05 -0000	1.3
+++ wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 17:58:58 -0000	1.4
@@ -25,13 +25,18 @@
 
 # Using clang from pkgsrc
 
-You can build clang from pkgsrc (lang/clang).  However, it need
-libstdc++ from the base system, and thus this will only work on
-systems that natively have gcc if the version is 4.8 or higher.
+You can build clang from pkgsrc (lang/clang).  However, it needs
+libstdc++ from the base system, at least from gcc 4.8 or higher.  It
+also depends on cmake, which requires c++11, which needs gcc 4.8 or
+higher.  So this will not work on NetBSD <= 6.
 
 Once built, you should (\todo test this) be able to set:
 
     PKGSRC_COMPILER=       clang
     CLANGBASE=             /usr/pkg
 
+and perhaps
+
+    HAVE_LLVM=             yes
+
 The caveats above about using a consistent compiler apply.

Add notes about pkgsrc clang
Index: wikisrc/tutorials/pkgsrc/clang.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/clang.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/tutorials/pkgsrc/clang.mdwn	4 Dec 2017 00:43:22 -0000	1.2
+++ wikisrc/tutorials/pkgsrc/clang.mdwn	30 Dec 2017 17:51:05 -0000	1.3
@@ -1,3 +1,5 @@
+# Using clang from the base system
+
 When building NetBSD, you can set
 
     MKLLVM=yes
@@ -18,3 +20,18 @@
 in your /etc/mk.conf to use it. You must do that before building
 packages, especially libtool. It's usually fine to link binaries
 generated from gcc to those generated with clang or vice versa.
+
+\todo: Explain why HAVE_LLVM is set to use clang for pkgsrc.
+
+# Using clang from pkgsrc
+
+You can build clang from pkgsrc (lang/clang).  However, it need
+libstdc++ from the base system, and thus this will only work on
+systems that natively have gcc if the version is 4.8 or higher.
+
+Once built, you should (\todo test this) be able to set:
+
+    PKGSRC_COMPILER=       clang
+    CLANGBASE=             /usr/pkg
+
+The caveats above about using a consistent compiler apply.

Add tutorials links
Index: wikisrc/pkgsrc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/pkgsrc.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/pkgsrc.mdwn	26 Nov 2017 00:05:58 -0000	1.6
+++ wikisrc/pkgsrc.mdwn	30 Dec 2017 17:38:29 -0000	1.7
@@ -17,6 +17,10 @@
 
 pkgsrc supports a [number of exploit mitigation techniques](hardening/)
 
+## Unordered list of pkgsrc tutorials
+
+[[!map pages="tutorials/pkgsrc/* and !*.css"]]
+
 ## Unordered list of all pkgsrc wiki pages
 
 [[!map pages="pkgsrc/* and !*.css"]]

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