Recent changes to this wiki:

Let's try that again.
Index: wikisrc/releng/release-prep.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/release-prep.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/releng/release-prep.mdwn	12 Apr 2014 18:57:36 -0000	1.10
+++ wikisrc/releng/release-prep.mdwn	12 Apr 2014 18:59:12 -0000	1.11
@@ -142,15 +142,15 @@
 
 15. Update the website.
 
-  - Commit release's HTML file in htdocs/releases/formal-<blah>
-  - Add htdocs/support/security/patches-<blah>
-  - Update htdocs/releases/formal-<blah>/index.xml
-  - Update htdocs/mirrors/torrents/
-  - Update htdocs/share/xml/misc.ent (release.*)
-  - Update htdocs/index.html
-  - Update htdocs/releases/formal.xml
-  - Update htdocs/changes/index.xml
-  - Top-level regen of everything
+    - Commit release's HTML file in htdocs/releases/formal-<blah>
+    - Add htdocs/support/security/patches-<blah>
+    - Update htdocs/releases/formal-<blah>/index.xml
+    - Update htdocs/mirrors/torrents/
+    - Update htdocs/share/xml/misc.ent (release.*)
+    - Update htdocs/index.html
+    - Update htdocs/releases/formal.xml
+    - Update htdocs/changes/index.xml
+    - Top-level regen of everything
 
 16. Update <code>/pub/NetBSD/README</code> to mention the new release
 

More formatting fixes. Hopefully.
Index: wikisrc/releng/release-prep.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/release-prep.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/releng/release-prep.mdwn	12 Apr 2014 18:47:26 -0000	1.9
+++ wikisrc/releng/release-prep.mdwn	12 Apr 2014 18:57:36 -0000	1.10
@@ -142,15 +142,15 @@
 
 15. Update the website.
 
-  Commit release's HTML file in htdocs/releases/formal-&lt;blah&gt;
-  Add htdocs/support/security/patches-&lt;blah&gt;
-  Update htdocs/releases/formal-&lt;blah&gt;/index.xml
-  Update htdocs/mirrors/torrents/
-  Update htdocs/share/xml/misc.ent (release.*)
-  Update htdocs/index.html
-  Update htdocs/releases/formal.xml
-  Update htdocs/changes/index.xml
-  Top-level regen of everything
+  - Commit release's HTML file in htdocs/releases/formal-&lt;blah&gt;
+  - Add htdocs/support/security/patches-&lt;blah&gt;
+  - Update htdocs/releases/formal-&lt;blah&gt;/index.xml
+  - Update htdocs/mirrors/torrents/
+  - Update htdocs/share/xml/misc.ent (release.*)
+  - Update htdocs/index.html
+  - Update htdocs/releases/formal.xml
+  - Update htdocs/changes/index.xml
+  - Top-level regen of everything
 
 16. Update <code>/pub/NetBSD/README</code> to mention the new release
 

Add a bit of useful info about updating the website that I forgot to commit
back in August. While here, attempt to fix some formatting.
Index: wikisrc/releng/release-prep.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/release-prep.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/releng/release-prep.mdwn	21 Jan 2014 01:40:55 -0000	1.8
+++ wikisrc/releng/release-prep.mdwn	12 Apr 2014 18:47:26 -0000	1.9
@@ -36,7 +36,7 @@
      distribution sets so they'll fit on floppies."
    - Update Dd (should be the day the release is tagged)
    - Update version numbers
-   - Add mention of the latest CHANGES-<version> file in the "Release
+   - Add mention of the latest CHANGES-&lt;version&gt; file in the "Release
      Contents" section
    - List changes present in this release
    - Adjust known issues section as necessary
@@ -46,35 +46,36 @@
      section from the notes entirely).
 
    Note: the "changes" part of this should be taken from an mdoc file that
-   is generated from <code>htdocs/releases/formal-<BLAH>/changes<VERSION>.xml</code>.
+   is generated from <code>htdocs/releases/formal-&lt;BLAH&gt;/changes&lt;VERSION&gt;.xml</code>.
    Look for ".Ss Changes Between the NetBSD" in distrib/notes/common/main
    and paste away!  You may have to make a few markup changes to the contents
    of the mdoc file, because the XML -> mdoc converter sucks.  Always check to
    make sure things are formatted as intended.
 
-   Basically, in htdocs/releases/formal-\<blah>, copy the previous release's
-   XML files, adjust Makefile as necessary, and start the dull process of
-   adding content.  Beware that this is a soul-sucking task, and you MUST
-   RESIST THE TEMPTATION TO MENTION EVERY LITTLE CHANGE.  Try to keep it
-   to a list of things that people will be excited about and will sell
-   NetBSD.  Release notes != changelog.
+   Basically, in htdocs/releases/formal-&lt;blah&gt;, copy the previous
+   release's XML files, adjust Makefile as necessary, and start the dull
+   process of adding content.  Beware that this is a soul-sucking task,
+   and you MUST RESIST THE TEMPTATION TO MENTION EVERY LITTLE CHANGE.  Try
+   to keep it to a list of things that people will be excited about and
+   will sell NetBSD.  Release notes != changelog.
 
-   Don't forget to edit <code>htdocs/layout.xml</code> and add an entry for the new page.
+   Don't forget to edit <code>htdocs/layout.xml</code> and add an entry for
+   the new page.
 
 2. Update version numbers in <code>gnu/usr.bin/groff/tmac/mdoc.local</code> and
    sys/sys/param.h.  Add new CHANGES file to doc/README.files, updating
    release numbers while there.  Make sure <code>doc/LAST_MINUTE</code> is zeroed out
    and adjust version number.
 
-3. Note changes from step 2 in doc/CHANGES-\<whatever>
+3. Note changes from steps 1 and 2 in doc/CHANGES-&lt;whatever&gt;
 
 4. <code>cvs -f rtag -a -rnetbsd-5 netbsd-5-0-RELEASE src xsrc</code>
 
    If something needs to be retagged after the fact:
 
-   - Change \<file> on the netbsd-5 branch.
-   - <code>cvs tag -d netbsd-5-0-RELEASE \<file></code>
-   - <code>cvs tag -rnetbsd-5 netbsd-5-0-RELEASE \<file></code>
+   - Change &lt;file&gt; on the netbsd-5 branch.
+   - <code>cvs tag -d netbsd-5-0-RELEASE &lt;file&gt;</code>
+   - <code>cvs tag -rnetbsd-5 netbsd-5-0-RELEASE &lt;file&gt;</code>
 
 5. Add tag (netbsd-5-0-RELEASE) to <code>~builds/etc/archlist</code> on build.netbsd.org
    Add tag to <code>AB_STICKY_TAG_LIST</code> in <code>~builds/etc/autobuild.conf</code>.  Note that
@@ -97,15 +98,15 @@
    and proceed.
 
 8. Create ISOs (macppc, mac68k, source).  See below for instructions.
-   Rename ISOs to blahcd-\<release>.iso
+   Rename ISOs to blahcd-&lt;release&gt;.iso
    Create hashes for ISOs (<code>cksum -a 512 *iso > SHA512</code>)
 
 9. rsync to nbftp.  It goes to a staging dir in /pub/NetBSD/misc/releng first.
 
-        rsync -avu --progress --port 874 --password-file /home/builds/.rsync \<path-to-top-level-release-dir> builds@ftp.netbsd.org::builds/
+        rsync -avu --progress --port 874 --password-file /home/builds/.rsync &lt;path-to-top-level-release-dir&gt; builds@ftp.netbsd.org::builds/
 This will upload the files to <code>ftp.NetBSD.org:/pub/NetBSD/misc/releng/</code>.
-   After that, get admins to create <code>/pub/NetBSD/NetBSD-\<release></code> and
-   <code>/pub/NetBSD/iso/<release></code> directories for you, owned by builds:builds.
+   After that, get admins to create <code>/pub/NetBSD/NetBSD-&lt;release&gt;</code> and
+   <code>/pub/NetBSD/iso/&lt;release&gt;</code> directories for you, owned by builds:builds.
    Once these have been made, move images/* to the iso directory and symlink to "iso" and "images" in the main release directory, and move the rest
    to the main release directory.
 
@@ -141,6 +142,16 @@
 
 15. Update the website.
 
+  Commit release's HTML file in htdocs/releases/formal-&lt;blah&gt;
+  Add htdocs/support/security/patches-&lt;blah&gt;
+  Update htdocs/releases/formal-&lt;blah&gt;/index.xml
+  Update htdocs/mirrors/torrents/
+  Update htdocs/share/xml/misc.ent (release.*)
+  Update htdocs/index.html
+  Update htdocs/releases/formal.xml
+  Update htdocs/changes/index.xml
+  Top-level regen of everything
+
 16. Update <code>/pub/NetBSD/README</code> to mention the new release
 
 17. Announce the release on netbsd-announce@ and the blog.

Convert from ISO-8859-1 to UTF-8.
Index: wikisrc/guide/index.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/guide/index.mdwn,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- wikisrc/guide/index.mdwn	21 Mar 2013 11:21:48 -0000	1.34
+++ wikisrc/guide/index.mdwn	12 Apr 2014 02:41:36 -0000	1.35
@@ -381,10 +381,10 @@
 * Jan Schaumann, for maintenance work and `www/htdocs` management.
 * Lubomir Sedlacik, for some details on using CGD for swap in
 [[Suggestions and Warnings|guide/cgd#suggestions]]
-* Dag-Erling Smørgrav, for the article on
+* Dag-Erling Smørgrav, for the article on
 [[Pluggable Authentication Modules (PAM)|guide/pam]]. See below for the
 accompanying license.
-* Florian Stöhr, for
+* Florian Stöhr, for
 [[Example: encrypted CDs/DVDs|guide/cgd#cryptocds]]
 
 
@@ -419,10 +419,10 @@
 
 #### The NetBSD Developers
 
-Copyright © 1999, 2000, 2001, 2002 Federico Lupi
+Copyright © 1999, 2000, 2001, 2002 Federico Lupi
 
-Copyright © 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 The NetBSD Foundation
+Copyright © 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 The NetBSD Foundation
 
 All brand and product names used in this guide are or may be trademarks or registered trademarks of their respective owners.
 
-NetBSD® is a registered trademark of The NetBSD Foundation, Inc.
+NetBSD® is a registered trademark of The NetBSD Foundation, Inc.
Index: wikisrc/guide/index_bare
===================================================================
RCS file: /cvsroot/wikisrc/guide/index_bare,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/guide/index_bare	14 Mar 2013 23:07:45 -0000	1.8
+++ wikisrc/guide/index_bare	12 Apr 2014 02:41:36 -0000	1.9
@@ -100,10 +100,10 @@
  * Jan Schaumann, for maintenance work and `www/htdocs` management.
  * Lubomir Sedlacik, for some details on using CGD for swap in
    [[Suggestions and Warnings|guide/cgd#suggestions]]
- * Dag-Erling Smørgrav, for the article on
+ * Dag-Erling Smørgrav, for the article on
    [[Pluggable Authentication Modules (PAM)|guide/pam]]. See below for the
    accompanying license.
- * Florian Stöhr, for
+ * Florian Stöhr, for
    [[Example: encrypted CDs/DVDs|guide/cgd#cryptocds]]
 
 
@@ -138,10 +138,10 @@
 
 #### The NetBSD Developers
 
-Copyright © 1999, 2000, 2001, 2002 Federico Lupi
+Copyright © 1999, 2000, 2001, 2002 Federico Lupi
 
-Copyright © 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 The NetBSD Foundation
+Copyright © 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 The NetBSD Foundation
 
 All brand and product names used in this guide are or may be trademarks or registered trademarks of their respective owners.
 
-NetBSD® is a registered trademark of The NetBSD Foundation, Inc.
+NetBSD® is a registered trademark of The NetBSD Foundation, Inc.

minor status changes on x86/uefiboot(8)
Index: wikisrc/users/jakllsch.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jakllsch.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/jakllsch.mdwn	30 Jul 2011 15:09:56 -0000	1.5
+++ wikisrc/users/jakllsch.mdwn	12 Apr 2014 02:28:11 -0000	1.6
@@ -26,9 +26,7 @@
 ## Unfinished Projects
 
 ### x86 UEFI kernel loader
-Building this for x64 UEFI requires the `ms_abi` function attribute introduced in GCC 4.4 or so.
-This project uses Intel UEFI headers and some existing FreeBSD work.
-Needs more work and cleanup, also toolchain updates.
+Needs more work and cleanup.
 Work has been done using the OVMF BIOS images for Qemu.
 
 ### bcm47xx for evbmips

link to logo image in protocol independent manner
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.24
retrieving revision 1.25
diff -u -r1.24 -r1.25
--- wikisrc/templates/page.tmpl	9 Jan 2014 02:40:45 -0000	1.24
+++ wikisrc/templates/page.tmpl	12 Apr 2014 02:18:09 -0000	1.25
@@ -26,7 +26,7 @@
 <body>
     <div id="centralHeader">
       <div id="logo">
-        <a href="http://www.NetBSD.org/"><img src="http://www.NetBSD.org/images/NetBSD-smaller.png" alt="[NetBSD Logo]"/></a>
+        <a href="http://www.NetBSD.org/"><img src="//www.NetBSD.org/images/NetBSD-smaller.png" alt="[NetBSD Logo]"/></a>
         <div id="name"><a href="http://www.NetBSD.org/">The NetBSD Project</a></div>
         <div id="slogan"><a href="http://www.NetBSD.org/">&ldquo;Of course it runs NetBSD&rdquo;</a></div>
       </div>

Write about ARM support
Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	4 Nov 2013 02:50:01 -0000	1.4
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	3 Apr 2014 11:55:12 -0000	1.5
@@ -1,10 +1,24 @@
 DTrace is a Dynamic Tracing framework developed by Sun and ported to NetBSD. It enables extensive instrumentation of the kernel and user space. See the [DTrace Community Page](http://dtrace.org) for more information. Also see [DTrace Introduction](http://dtrace.org/guide/preface.html). 
 
+# Current status
 
-DTrace is a work-in-progress effort and it is for x86 systems only currently (there is some arm support but it is completely untested). Two providers are available; the Statically Defined Tracing (SDT) provider and the Function Boundary Tracer (FBT) provider. 
+## Supported platforms
+
+DTrace is a work-in-progress effort and it is for x86 systems and some arm boards.
+
+* i386 and amd64
+* evbarm
+    * BEAGLEBONE and SHEEVAPLUG
+
+## Supported providers
+
+* SDT: Statically Defined Tracing
+* FBT: Function Boundary Tracing
 
 You can currently run a hello world DScript. 
 
+# How to use
+
 ##  Building DTrace 
 
 You need the following options in your kernel: 
@@ -101,4 +115,3 @@
     
 
 Start the script running (dtrace -s <scriptname.d>) and then execute a sleep 2 in another shell. 
-

Broken links
Index: wikisrc/tutorials/how_to_create_bootable_netbsd_image.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_create_bootable_netbsd_image.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/tutorials/how_to_create_bootable_netbsd_image.mdwn	5 Feb 2012 07:14:36 -0000	1.2
+++ wikisrc/tutorials/how_to_create_bootable_netbsd_image.mdwn	3 Apr 2014 03:27:42 -0000	1.3
@@ -112,7 +112,7 @@
 
 Then we edit the `Makefile`, to make sure that the `RAMDISKS` and `MDSETTARGETS` variables are set properly. After the modifications, mine looks like this: 
     
-    #       $NetBSD: how_to_create_bootable_netbsd_image.mdwn,v 1.2 2012/02/05 07:14:36 schmonz Exp $                  
+    #       $NetBSD: how_to_create_bootable_netbsd_image.mdwn,v 1.3 2014/04/03 03:27:42 wiki Exp $                  
     
     .include <bsd.own.mk>
     .include "${NETBSDSRCDIR}/distrib/common/Makefile.distrib"
@@ -174,30 +174,7 @@
     
     $ cd /usr/src/distrib/i386/floppies/bootfloppy-big
     $ qemu boot-big1.fs
-    
-
-#  Screenshots
-
-[![][18]][19]
-
-   [18]: /images/120px-Qemu_boot_1.png
-   [19]: /images/Qemu_boot_1.png (Qemu boot 1.png)
-
-Booting 
-
-[![][20]][21]
-
-   [20]: /images/120px-Qemu_boot_2.png
-   [21]: /images/Qemu_boot_2.png (Qemu boot 2.png)
-
-Booting 
-
-[![][22]][23]
-
-   [22]: /images/120px-Qemu_boot_3.png
-   [23]: /images/Qemu_boot_3.png (Qemu boot 3.png)
-
-Shell 
+ 
 
 #  Credits
 
@@ -206,7 +183,6 @@
 
 #  Additional related links
 
-  1. [Embedded NetBSD](http://brianrose.net/family/fetch.php?dir=Brian/NetBSD/Embedded&filename=content.html)
-  2. [Creating a custom install/boot floppies for i386](http://www.netbsd.org/docs/guide/en/chap-misc.html#chap-misc-creating-bootfloppies)
+  1. [Creating a custom install/boot floppies for i386](http://www.netbsd.org/docs/guide/en/chap-misc.html#chap-misc-creating-bootfloppies)
 
 

Resort the categories.
Index: wikisrc/projects/all.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/all.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/all.mdwn	2 Apr 2014 15:25:54 -0000	1.6
+++ wikisrc/projects/all.mdwn	2 Apr 2014 15:28:57 -0000	1.7
@@ -13,37 +13,37 @@
 ## Hard
 [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:filesystems) and tagged(difficulty:hard)"]]
 
-# Kernel-level projects
+# Networking projects
 ## Easy
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:kernel) and tagged(difficulty:easy)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:networking) and tagged(difficulty:easy)"]]
 ## Medium
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:kernel) and tagged(difficulty:medium)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:networking) and tagged(difficulty:medium)"]]
 ## Hard
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:kernel) and tagged(difficulty:hard)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:networking) and tagged(difficulty:hard)"]]
 
-# Miscellaneous projects
+# Port-related projects
 ## Easy
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:misc) and tagged(difficulty:easy)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:ports) and tagged(difficulty:easy)"]]
 ## Medium
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:misc) and tagged(difficulty:medium)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:ports) and tagged(difficulty:medium)"]]
 ## Hard
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:misc) and tagged(difficulty:hard)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:ports) and tagged(difficulty:hard)"]]
 
-# Networking projects
+# Other kernel-level projects
 ## Easy
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:networking) and tagged(difficulty:easy)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:kernel) and tagged(difficulty:easy)"]]
 ## Medium
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:networking) and tagged(difficulty:medium)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:kernel) and tagged(difficulty:medium)"]]
 ## Hard
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:networking) and tagged(difficulty:hard)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:kernel) and tagged(difficulty:hard)"]]
 
-# pkgsrc projects
+# Userland projects
 ## Easy
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:pkgsrc) and tagged(difficulty:easy)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:userland) and tagged(difficulty:easy)"]]
 ## Medium
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:pkgsrc) and tagged(difficulty:medium)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:userland) and tagged(difficulty:medium)"]]
 ## Hard
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:pkgsrc) and tagged(difficulty:hard)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:userland) and tagged(difficulty:hard)"]]
 
 # Desktop projects
 ## Easy
@@ -53,21 +53,21 @@
 ## Hard
 [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:desktop) and tagged(difficulty:hard)"]]
 
-# Port-related projects
+# pkgsrc projects
 ## Easy
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:ports) and tagged(difficulty:easy)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:pkgsrc) and tagged(difficulty:easy)"]]
 ## Medium
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:ports) and tagged(difficulty:medium)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:pkgsrc) and tagged(difficulty:medium)"]]
 ## Hard
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:ports) and tagged(difficulty:hard)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:pkgsrc) and tagged(difficulty:hard)"]]
 
-# Userland projects
+# Miscellaneous projects
 ## Easy
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:userland) and tagged(difficulty:easy)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:misc) and tagged(difficulty:easy)"]]
 ## Medium
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:userland) and tagged(difficulty:medium)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:misc) and tagged(difficulty:medium)"]]
 ## Hard
-[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:userland) and tagged(difficulty:hard)"]]
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:misc) and tagged(difficulty:hard)"]]
 
 # Unclassified projects
 

Add a category for desktop projects.
Index: wikisrc/projects/all.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/all.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/all.mdwn	9 Nov 2011 21:14:03 -0000	1.5
+++ wikisrc/projects/all.mdwn	2 Apr 2014 15:25:54 -0000	1.6
@@ -45,6 +45,14 @@
 ## Hard
 [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:pkgsrc) and tagged(difficulty:hard)"]]
 
+# Desktop projects
+## Easy
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:desktop) and tagged(difficulty:easy)"]]
+## Medium
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:desktop) and tagged(difficulty:medium)"]]
+## Hard
+[[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:desktop) and tagged(difficulty:hard)"]]
+
 # Port-related projects
 ## Easy
 [[!map show="title" pages="projects/project/* and tagged(status:active) and tagged(category:ports) and tagged(difficulty:easy)"]]
@@ -74,7 +82,7 @@
 
 ## Projects without a category definition
 
-[[!map show="title" pages="projects/project/* and tagged(status:active) 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)"]]
 
 ## Projects without a difficulty definition
 

Add four new desktop-related projects.
--- /dev/null	2014-04-02 15:20:00.000000000 +0000
+++ wikisrc/projects/project/desktop-infrastructure.mdwn	2014-04-02 15:25:01.000000000 +0000
@@ -0,0 +1,77 @@
+[[!template id=project
+
+title="Desktop infrastructure"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org),
+[tech-x11](mailto:tech-x11@NetBSD.org),
+"""
+
+category="desktop"
+difficulty="medium"
+
+description="""
+Support for "real" desktops on NetBSD is somewhat limited and also
+scattershot.
+Part of the reason for this is that most of the desktops are not
+especially well engineered, and they contain poorly designed
+infrastructure components that interact incestuously with system
+components that are specific to and/or make sense only on Linux.
+Providing the interfaces these infrastructure components wish to talk
+to is a large job, and Linux churn being what it is, such interfaces
+are usually moving targets anyway.
+Reimplementing them for NetBSD is also a large job and often
+presupposes things that aren't true or would require that NetBSD adopt
+system-level design decisions that we don't want.
+
+Rather than chase after Linux compatibility, we are better off
+designing the system layer and infrastructure components ourselves.
+It is easier to place poorly conceived interfaces on top of a solid
+design than to reimplement a poorly conceived design. Furthermore, if
+we can manage to do a few things right we should be able to get at
+least some uptake for them.
+
+The purpose of this project, per se, is not to implement any
+particular piece of infrastructure.
+It is to identify pieces of infrastructure that the desktop software
+stacks need from the operating system, or provide themselves but ought
+to get from the operating system, figure out solid designs that are
+compatible with Unix and traditional Unix values, and generate project
+descriptions for them in order to get them written and deployed.
+
+For example, GNOME and KDE rely heavily on dbus for sending
+notifications around.
+While dbus itself is a more or less terrible piece of software that
+completely fails to match the traditional Unix model (rather than
+doing one thing well, it does several things at once, pretty much all
+badly) it is used by GNOME and KDE because there are things a desktop
+needs to do that require sending messages around.
+We need a transport for such messages; not a reimplementation of dbus,
+but a solid and well-conceived way of sending notices around among
+running processes.
+
+Note that one of the other things dbus does is start services up; we
+already have inetd for that, but it's possible that inetd could use
+some strengthening in order to be suitable for the purpose.
+It will probably also need to be taught about whatever message scheme
+we come up with.
+And we might want to e.g. set up a method for starting per-user inetd
+at login time.
+
+(A third thing dbus does is serve as an RPC library. For this we
+already have XDR, but XDR sucks; it may be that in order to support
+existing applications we want a new RPC library that's more or less
+compatible with the RPC library parts of dbus. Or that may not be
+feasible.)
+
+This is, however, just one of the more obvious items that arises.
+
+Your goal working on this project is to find more.
+Please edit this page and make a list, and add some
+discussion/exposition of each issue and possible solutions.
+Ones that become fleshed out enough can be moved to their own project
+pages.
+
+
+"""
+]]
--- /dev/null	2014-04-02 15:20:00.000000000 +0000
+++ wikisrc/projects/project/move-beyond-twm.mdwn	2014-04-02 15:25:01.000000000 +0000
@@ -0,0 +1,68 @@
+[[!template id=project
+
+title="Move beyond TWM"
+
+contact="""
+[tech-x11](mailto:tech-x11@NetBSD.org)
+"""
+
+category="desktop"
+difficulty="medium"
+
+description="""
+Right now if you install NetBSD with native X11 you get the same
+default X session that X has shipped forever, complete with TWM. Just
+like it's 1989.
+
+Obviously this behavior can be improved after installation by adding
+suitable packages and choosing a different window manager, or
+installing one of the full desktop environments. Veteran NetBSD users
+know how to do this. Veteran Unix and X users who aren't veteran
+NetBSD users can figure it out pretty easily. Most such people have an
+X setup they've been using for years that they can and do just plop
+into place on a new machine.
+
+This project does not affect those users, even the ones who for some
+crazy reason *want* to use twm. It also does not affect users who just
+want to install GNOME, KDE, or whatever other desktop.
+
+The goal of this project is to provide a less knobby default X
+environment for users who are willing to run plain X rather than a
+full desktop but do not have their own X setup.
+
+The project is: choose a window manager suitable for replacing twm in
+base; import it into base; and update the default X config to provide
+a decent default session using it.
+
+Note that it needs to be a mainstream window manager; tiling window
+managers and other exotica are not really suitable for the purpose. It
+should also not depend on anything that isn't in base (that is, base
+with native X), it should be smallish and not a bloatmonster, and
+ideally it should be BSD-licensed.
+
+Based on the window managers in pkgsrc, there are two chief
+candidates: fluxbox and golem. Each has pluses and minuses. Some of
+these are:
+
+* golem is prettier and fully themeable
+* golem is written in C, fluxbox in C++
+* golem is a lot smaller (less than 1/10th the code size)
+* golem currently needs some work, chiefly on the config system; fluxbox appears to be ready to go
+* golem is just about dead upstream; fluxbox is not very active but is still getting occasional releases
+
+Currently it looks like golem is a better choice, especially since
+ideally we'd like to pick something that will run decently on
+older/slower ports. But it requires more work.
+
+Note that we could (AFAIK) become upstream for golem; this is not
+necessarily a bad thing.
+
+There might be other possible choices; these two are the ones in
+pkgsrc that seem viable.
+
+Note: this project is not listed as a GSoC project (although doing the
+needed work on golem maybe could be one) because much of it has to do
+with build system integration and ancient X things and other stuff
+that requires experience a student probably won't have.
+"""
+]]
--- /dev/null	2014-04-02 15:20:00.000000000 +0000
+++ wikisrc/projects/project/ui-plugins-for-games.mdwn	2014-04-02 15:25:01.000000000 +0000
@@ -0,0 +1,67 @@
+[[!template id=project
+
+title="User interface plugins for games"
+
+contact="""
+[tech-x11](mailto:tech-x11@NetBSD.org),
+[tech-toolchain](mailto:tech-toolchain@NetBSD.org),
+"""
+
+category="desktop"
+difficulty="medium"
+
+description="""
+Some of the games in base would be much more playable with even a
+simple graphic interface.
+The card games (e.g. canfield, cribbage) are particularly pointed
+examples; but quite a few others, e.g. atc, gomoku, hunt, and sail if
+anyone ever fixes its backend, would benefit as well.
+
+There are two parts to this project: the first and basically mostly
+easy part is to pick a game and write an alternate user interface for
+it, using SDL or gtk2 or tk or whatever seems appropriate.
+
+The hard part is to arrange the system-level infrastructure so that
+the new user interface appears as a plugin for the game that can be
+installed from pkgsrc but that gets found and run if appropriate when
+the game is invoked from /usr/games.
+The infrastructure should be sufficiently general that lots of
+programs in base can have plugins.
+
+Some things this entails:
+
+* possibly setting up a support library in the base system for program
+plugins, if it appears warranted;
+
+* setting up infrastructure in the build system for programs with
+plugins, if needed;
+
+* preferably also setting up infrastructure in the build system for
+building plugins;
+
+* choosing a place to put the header files needed to build external
+plugins;
+
+* choosing a place to put plugin libraries, too, as there isn't a
+common model out there yet;

(Diff truncated)
point to networking support
Index: wikisrc/features.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/features.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/features.mdwn	24 Dec 2013 09:45:42 -0000	1.1
+++ wikisrc/features.mdwn	2 Apr 2014 06:01:46 -0000	1.2
@@ -1,5 +1,10 @@
 #Features supported by NetBSD
 
+##Networking
+* [[TCP/IP|features/tcpip-networking]]
+* [[Layer-1|features/layer-1-networking]]
+* [[other|features/other-networking]]
+
 ##Hardware Support
 * [[Video|features/video-hardware]]
 * [[Audio|features/audio-hardware]]

Test commit.
Index: wikisrc/users/schmonz.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/schmonz.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/users/schmonz.mdwn	5 Jul 2013 16:02:06 -0000	1.21
+++ wikisrc/users/schmonz.mdwn	30 Mar 2014 15:40:23 -0000	1.22
@@ -1,2 +1,4 @@
 If you've got an idea about how this wiki ought to work, edit the
 [[wiki/todo]] list! Here's what's been [[wiki/todo/done]] so far.
+
+Pretty soon I'll have lots more time for wikistuff.

another test
Index: wikisrc/users/spz/foo.html
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/foo.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/spz/foo.html	29 Mar 2014 17:46:55 -0000	1.2
+++ wikisrc/users/spz/foo.html	29 Mar 2014 17:55:44 -0000	1.3
@@ -6,7 +6,7 @@
 <body>
 <table class="rahmen"><tr><td>
 <h1>Questions?</h1>
-<p>.. or cookies?</p>
+<p>.. or cookies and cream tea?</p>
 </td></tr></table>
 <table class="navigation"><tr>
 <td class="prev"></td>

bar
Index: wikisrc/users/spz/foo.html
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/foo.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/spz/foo.html	6 Mar 2013 19:24:04 -0000	1.1
+++ wikisrc/users/spz/foo.html	29 Mar 2014 17:46:55 -0000	1.2
@@ -6,7 +6,7 @@
 <body>
 <table class="rahmen"><tr><td>
 <h1>Questions?</h1>
-<p>.. or comments?</p>
+<p>.. or cookies?</p>
 </td></tr></table>
 <table class="navigation"><tr>
 <td class="prev"></td>

Smileys are being used (main page, kerberos/system, etc.). Without
the default smiley definitions, they're rendered as ASCII instead
of little icons. Remove this file, allowing the default definitions
to take effect again.
--- wikisrc/smileys.mdwn	2014-03-30 15:37:40.000000000 +0000
+++ /dev/null	2014-03-30 15:32:01.000000000 +0000
@@ -1,14 +0,0 @@
-This page is used to control what smileys are supported by the wiki.
-Just write the text of a smiley to display it.
-
-
-----
-
-To change the supported smileys, just edit the lists on this page.
-Note that the format is important; each list item should start with the
-text that is turned into the smiley, escaped so that users can see what
-produces it, followed by a [[ikiwiki/WikiLink]] to the image to display.
-
-/!\ Bear in mind that the link to the image needs to be written in a way that
-will work if it's copied to other pages on the wiki. So be sure to include the
-smileys directory in the path to the file.

markdown link
Index: wikisrc/rumpkernel.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/rumpkernel.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/rumpkernel.mdwn	27 Mar 2014 14:43:31 -0000	1.5
+++ wikisrc/rumpkernel.mdwn	27 Mar 2014 14:46:56 -0000	1.6
@@ -3,8 +3,9 @@
 [[!toc levels=2]]
 
 This page is about rump kernels in NetBSD and assumes the reader knows
-the basics of rump kernels.  See http://www.rumpkernel.org/ for general
-information about rump kernels.
+the basics of rump kernels.  See
+[rumpkernel.org](http://www.rumpkernel.org/) for general information
+about rump kernels.
 
 ## System security
 

NetBSD-specific information
Index: wikisrc/rumpkernel.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/rumpkernel.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/rumpkernel.mdwn	10 Feb 2014 15:25:04 -0000	1.4
+++ wikisrc/rumpkernel.mdwn	27 Mar 2014 14:43:31 -0000	1.5
@@ -2,225 +2,57 @@
 
 [[!toc levels=2]]
 
-# The Anykernel and Rump Kernels
+This page is about rump kernels in NetBSD and assumes the reader knows
+the basics of rump kernels.  See http://www.rumpkernel.org/ for general
+information about rump kernels.
+
+## System security
+
+File system drivers are vulnerable to consistency errors in
+file system images, see e.g.
+[here](http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.114.4312)
+
+What this vulnerability means is that whenever an untrusted file system
+image is mounted using an in-kernel driver, system compromise should be
+expected.  This untrusted images include for example ones on USB sticks.
+There are heavyweight workarounds for the problem, for example including
+virtual machines.
+
+NetBSD allows transparently mounting an untrusted file system image by
+running the kernel driver in a rump kernel in userspace.  The driver
+is thus isolated and any damage that a malicious file system image
+can directly cause is restricted to a userspace process.  From a user
+perspective, mounting with the `-o rump` option is the only change
+required, or `rump` in `/etc/fstab`.  Notably, even though interacting
+with untrusted file systems will suffer from a minor performance penalty,
+the performance of mounts from trusted file systems is completely
+unaffected.
+
+
+## Automated testing
+
+The problems of automated kernel testing are documented for example in
+[The Design and Implementation of the Anykernel and Rump Kernels](http://lib.tkk.fi/Diss/2012/isbn9789526049175/isbn9789526049175.pdf).
+Rump kernels are used in the continuous tests run by the NetBSD project.
+See http://releng.NetBSD.org/ for the results or the NetBSD source tree
+under `src/tests` for the test programs themselves.
+
+
+## Kernel development
+
+On the flipside of testing is kernel development.  Rump kernels allow
+developing kernel drivers in a test-driven manner, including both unit
+tests and integration tests.  Since the iteration time with a rump
+kernel is in the subsecond range, the development process is smoother
+than with a virtual machine.  Also, the tests written during development
+can be entered into the automated tests (see above), and later used
+for further development.  This method avoids "throw-away" tests that
+are hardcoded for one virtual machine environment and unusable in both
+automated testing and further development done in another environment.
 
-## About
-
-A driver abstracts an underlying entity. For example, a TCP/IP driver
-abstracts the details required to perform networking, the Fast File
-System (FFS) driver abstracts how the file system blocks are laid out on
-the storage medium, and a PCI network card driver abstracts how to
-access device registers to send and receive packets. The kernel
-architecture controls how kernel drivers run with respect to other
-system components. Some examples of kernel architectures are the
-monolithic kernel, microkernel and exokernel. In contrast to the above
-architectures, NetBSD is an *anykernel*. This means that some kernel
-drivers can be run according to any kernel architecture instead of being
-limited to a single one.
-
-<!--
-    TODO
-    ![](rumparch.png)
--->
-
-When a driver is not run as part of the monolithic kernel, e.g. when it
-is run as a microkernel style server, the driver is hosted in a *rump
-kernel*. A rump kernel is an ultralightweight virtualized kernel running
-on top of high-level hypercall interface. Instead of a low-level
-hypercall API typically seen with operating systems with operations such
-as "modify page table", the rump kernel hypercall API provides
-high-level operations such as "run this code in a thread".
-
-Currently, three implementations of the rump kernel hypercall interface
-exist.
-
--   The POSIX implementation is included in the NetBSD tree and allows
-    rump kernels to run as userspace processes on most operating systems
-    such as NetBSD, Linux and Solaris.
--   The Xen implementation allows running rump kernels directly as Xen
-    DomU's without an intermediate operating system.
--   The Linux kernel hypervisor allows rump kernels to run inside the
-    Linux kernel.
-
-Rump kernels are radically different from OS virtualization technologies
-such as KVM, containers and usermode operating systems. A rump kernel
-does not support hosting application processes because a rump kernel is
-aimed at virtualizing kernel drivers and application virtualization
-would be pure overhead. Instead, existing entities such as processes
-from a hosting OS are used as clients for the rump kernel ("application"
-in the figure).
-
-As a result of the above design choices, rump kernels are extremely
-lightweight. The bootstrap time for rump kernels on POSIX hosts is
-measured in milliseconds and memory footprint in 100kB's. This means
-that a rump kernel can be bootstrapped for example as part of a command
-line tool for virtually no cost or user impact. Rump kernels also
-mandate very little from the hypercall implementation meaning that
-rump kernels, and by extension NetBSD kernel drivers, can be hosted in
-virtually any environment -- for example, rump kernels do not require
-a platform with an MMU.
-
-Use cases for rump kernels include:
-
--   **Code reuse**: kernel drivers can be reused without having to run a
-    whole OS. For example, a full-featured TCP/IP stack (IPv6, IPSec,
-    etc.) can be included in an embedded appliance without having to
-    write the stack from scratch or waste resources on running an entire
-    OS.
--   **Kernel driver virtualization**: every rump kernel has its own
-    state. Furthermore, the functionality offered by multiple rump
-    kernels running on the same host does not need to be equal. For
-    example, multiple different networking stacks optimized for
-    different purposes are possible.
--   **Security**: when hosted on a POSIX system, a rump kernel runs in
-    its own instance of a userspace process. For example, it is widely
-    published that file system drivers are vulnerable to untrusted file
-    system images. Unlike on other general purpose operating systems, on
-    NetBSD it is possible to mount untrusted file systems, such as those
-    on a USB stick, in an isolated server with the kernel file system
-    driver. This isolates attacks and prevents kernel compromises while
-    not requiring to maintain separate userspace implementations of the
-    file system drivers or use other resource-intensive approaches such
-    as virtual machines.
--   **Easy prototyping and development**: kernel code can be developed
-    as a normal userspace application. Once development is finished, the
-    code can simply be complied into the kernel. This is a much more
-    convenient and straightforward approach to kernel development than
-    the use of virtual machines.
--   **Safe testing**: kernel code can be tested in userspace on any host
-    without risk of the test host being affected. Again, virtual
-    machines are not required.
-
-## Further Reading
-
-### Book
-
-The following book is the definitive guide to the anykernel and rump
-kernels and supercedes all earlier publications and terminology on
-the subject.
-
--   [Flexible Operating System Internals: The Design and Implementation
-    of the Anykernel and Rump
-    Kernels](http://lib.tkk.fi/Diss/2012/isbn9789526049175/isbn9789526049175.pdf)
-
-Note that the book was finalized in summer 2012, so while the fundamentals
-are still accurate, some of the problems described in "Future Work"
-have already been solved.  Check out the links below.
-
-
-### Software using rump kernels
-
-While the NetBSD source tree hosts the base kernel drivers and hypercall
-implementation, more I/O drivers, infrastructure scripts and hypercall
-implementations are hosted elsewhere.  Most of the code is hosted
-under the [rump kernels](https://github.com/rumpkernel/) organization
-on github.  Some highlights include:
-
--   [Scripts for building rump kernels for POSIX
-    systems](https://github.com/rumpkernel/buildrump.sh)
--   The [rumprun](https://github.com/rumpkernel/rumprun/) package
-    allows portable building and running of unmodified NetBSD userspace
-    applications -- extremely useful for configuring rump kernels (e.g.
-    network interfaces and routing tables)
--   [Rump kernel hypercall implementation for Xen; rump kernels as Xen
-    DomU's](https://github.com/rumpkernel/rumpuser-xen)
--   [fs-utils: File system image access
-    utilities](https://github.com/stacktic/fs-utils)
--   Fast userspace packet processing: TCP/IP stack for use with
-    [DPDK](https://github.com/rumpkernel/dpdk-rumptcpip), 
-    [netmap](https://github.com/rumpkernel/netmap-rumptcpip) or
-    [Snabb Switch](https://github.com/anttikantee/snabbswitch/tree/rumpkernel/)
-
-### Articles, Tutorials & Howtos
-
--   [Running rump kernels and applications on Xen without a full
-    OS](http://blog.NetBSD.org/tnf/entry/running_applications_on_the_xen)
--   [PCI device driver support in rump kernels on
-    Xen](http://blog.NetBSD.org/tnf/entry/pci_driver_support_for_rump)
--   [Experiment with a rump kernel hypervisor for the Linux
-    kernel](http://blog.NetBSD.org/tnf/entry/a_rump_kernel_hypervisor_for)
-    (allows rump kernels to run *in* the Linux kernel)
--   [Experiment on compiling rump kernels to javascript and running them
-    in the
-    browser](http://blog.NetBSD.org/tnf/entry/kernel_drivers_compiled_to_javascript)

(Diff truncated)
pandoc -f docbook -t markdown http://www.netbsd.org/gallery/events.xml
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/events.mdwn	4 Mar 2014 04:28:49 -0000	1.7
+++ wikisrc/events.mdwn	5 Mar 2014 06:52:32 -0000	1.8
@@ -1,6 +1,3 @@
-NetBSD Events
-=============
-
 This is an incomplete list of NetBSD-related events. If you know about
 some public event that fits and would like it to be listed here,
 [contact us.](http://www.NetBSD.org/cgi-bin/feedback.cgi)
@@ -8,501 +5,10 @@
 For a list of NetBSD-related presentations, please check out our
 [presentation pages](/gallery/presentations/).
 
-### Future Events
-
--   [Mar 2014 - AsiaBSDCon 2014](#asiabsdcon-tokyo-2014)
--   [Mar 2014 - Open Source Conference 2014
-    Hamanako](#opensourceconf2014-hamamatsu)
--   [Jun 2014 - Open Source Conference 2014
-    Hokkaido](#opensourceconf2014-DO)
--   [Jul 2014 - Open Source Conference 2014
-    Nagoya](#opensourceconf2014-Nagoya)
--   [Nov 2014 - Kansai OpenSource 2014](#kansai-os-jp-2014)
-
-### Past Events
-
--   [Feb 2014 - Open Source Conference 2014
-    Tokyo/Spring](#opensourceconf2014-tokyospring)
--   [Feb 2014 - NYC\*BSD Con 2014](#NYCBSDCon2014)
--   [Nov 2013 - Linux User Group of Mauritius - LinuxFest
-    2013](#LinuxFest2013Mauritius)
--   [Nov 2013 - Open Source Conference 2013
-    Oita](#opensourceconf2013-oita)
--   [Nov 2013 - Open Source Conference 2013
-    Fukuoka](#opensourceconf2013-fukuoka)
--   [Nov 2013 - Kansai OpenSource 2013](#kansai-os-jp-2013)
--   [Oct 2013 - Open Source Conference 2013
-    Tokyo/Fall](#opensourceconf2013-tokyofall)
--   [Oct 2013 - Open Source Conference 2013
-    Hiroshima](#opensourceconf2013-Hiroshima)
--   [Sep 2013 - Open Source Conference 2013
-    Hokkaido](#opensourceconf2013-DO)
--   [Aug 2013 - FrOSCon 2013](#froscon2013)
--   [Aug 2013 - Open Source Conference 2013
-    Shimane](#opensourceconf2013-Shimane)
--   [Aug 2013 - Open Source Conference 2013
-    Kansai@Kyoto](#opensourceconf2013-Kansai)
--   [Jul 2013 - Japan NetBSD Users' Group meeting & NetBSD
-    BOF](#jp-users-2013)
--   [Jul 2013 - Open Source Conference 2013
-    Okinawa](#opensourceconf2013-Okinawa)
--   [Jun 2013 - Open Source Conference 2013
-    Nagoya](#opensourceconf2013-Nagoya)
--   [May 2013 - Linuxtag Berlin](#linuxtagB2013)
--   [May 2013 - BSDCan 2013, Ottawa, Canada](#bsdcan2013)
--   [Apr 2013 - Central European BSD-Day 2013, Naples,
-    Italy](#bsdday_2013)
--   [Mar 2013 - pkgsrcCon 2013, Berlin, Germany](#pkgsrcCon-2013)
--   [Mar 2013 - Chemnitz Linux Days 2013, Chemnitz,
-    Germany](#chemnitzer-linuxtage-2013)
--   [Mar 2013 - AsiaBSDCon 2013](#asiabsdcon-tokyo-2013)
--   [Mar 2013 - Open Source Conference 2013
-    Tokushima](#opensourceconf2013-tokushima)
--   [Feb 2013 - Open Source Conference 2013
-    Tokyo/Spring](#opensourceconf2013-tokyospring)
--   [Feb 2013 - Open Source Conference 2013
-    Hamamatsu](#opensourceconf2013-hamamatsu)
--   [Feb 2013 - FOSDEM 2013, Brussels, Belgium](#fosdem2013)
--   [Dec 2012 - Open Source Conference 2012
-    Fukuoka](#opensourceconf2012-fukuoka)
--   [Nov 2012 - Open Source Conference 2012
-    Aizu](#opensourceconf2012-aizu)
--   [Oct 2012 - Open Source Conference 2012
-    Oita/Fall](#opensourceconf2012-oita-fall)
--   [Oct 2012 - Open Source Conference 2012
-    Hiroshima](#opensourceconf2012-Hiroshima)
--   [Oct 2012 - EuroBSDCon 2012, Warsaw, Poland](#eurobsdcon2012)
--   [Sep 2012 - Open Source Conference 2012
-    Okinawa](#opensourceconf2012-Okinawa)
--   [Sep 2012 - Open Source Conference 2012
-    Tokyo/Spring](#opensourceconf2012-tokyofall)
--   [Nov 2012 - Kansai OpenSource 2012](#kansai-os-jp-2012)
--   [Sep 2012 - Open Source Conference 2012
-    Shimane](#opensourceconf2012-Shimane)
--   [Aug 2012 - XenSummit North America 2012](#xensummit2012)
--   [Aug 2012 - FrOSCon 2012](#froscon2012)
--   [Aug 2012 - Open Source Conference 2012
-    Kansai@Kyoto](#opensourceconf2012-Kansai)
--   [Jul 2012 - Open Source Conference 2012
-    Sendai](#opensourceconf2012-sendai)
--   [Jul 2012 - Japan NetBSD Users' Group meeting & NetBSD
-    BOF](#jp-users-2012)
--   [Jun 2012 - 17th NetBSD Hackathon](#17th-hackathon)
--   [Jun 2012 - Open Source Conference 2012
-    Hokkaido](#opensourceconf2012-DO)
--   [May 2012 - Linuxtag Berlin](#linuxtagB2012)
--   [May 2012 - BSDCan 2012](#bsdcan2012)
--   [May 2012 - Open Source Conference 2012
-    Nagoya](#opensourceconf2012-Nagoya)
--   [May 2012 - Central European BSD-Day 2012 Vienna](#bsdday_2012)
--   [Apr 2012 - Open Source Conference 2012
-    Iwate](#opensourceconf2012-iwate)
--   [Mar 2012 - AsiaBSDCon 2012](#asiabsdcon-tokyo-2012)
--   [Mar 2012 - Open Source Conference 2012
-    Ehime](#opensourceconf2012-ehime)
--   [Mar 2012 - Chemnitzer Linux-Tage 2012](#chemnitzer-linuxtage-2012)
--   [Mar 2012 - Open Source Conference 2012
-    Tokyo/Spring](#opensourceconf2012-tokyospring)
--   [Feb 2012 - Open Source Conference 2012
-    Oita](#opensourceconf2012-oita)
--   [Feb 2012 - FOSDEM 2012](#fosdem2012)
--   [Dec 2011 - Open Source Conference 2011
-    Fukuoka](#opensourceconf2011-fukuoka)
--   [Nov 2011 - Open Source Conference 2011
-    Tokyo/Fall](#opensourceconf2011-tokyofall)
--   [Nov 2011 - Open Source Conference 2011
-    Shimane](#opensourceconf2011-Shimane)
--   [Nov 2011 - Kansai OpenSource 2011](#kansai-os-jp-2011)
--   [Nov 2011 - bsd\_day(2011)](#bsdday2011)
--   [Nov 2011 - BSDday Argentina 2011](#BSDdayArgentina2011)
--   [Oct 2011 - EuroBSDCon 2011](#eurobsdcon2011)
--   [Oct 2011 - Open Source Conference 2011
-    Hiroshima](#opensourceconf2011-Hiroshima)
--   [Sep 2011 - Open Source Conference 2011
-    Okinawa](#opensourceconf2011-Okinawa)
--   [Sep 2011 - Open Source Small Conference 2011
-    Aizu](#opensourcesmallconf2011-Aizu)
--   [Aug 2011 - Open Source Conference 2011
-    Nagoya](#opensourceconf2011-Nagoya)
--   [Aug 2011 - 15th NetBSD Hackathon](#15th-hackathon)
--   [Jul 2011 - Open Source Conference 2011
-    Kansai@Kyoto](#opensourceconf2011-Kansai)
--   [Jul 2011 - Japan NetBSD Users' Group meeting & NetBSD
-    BOF](#jp-users-2011)
--   [Jun 2011 - Open Source Conference 2011
-    Hokkaido](#opensourceconf2011-DO)
--   [May 2011 - Open Source Conference 2011
-    Sendai](#opensourceconf2011-sendai)
--   [May 2011 - BSDCan 2011](#bsdcan2011)
--   [Apr 2011 - Open Source Conference 2011
-    Kansai@Kobe](#opensourceconf2011-kobe)
--   [Mar 2011 - AsiaBSDCon 2011](#asiabsdcon-tokyo-2011)
--   [Mar 2011 - Open Source Conference 2011
-    Oita](#opensourceconf2011-oita)
--   [Mar 2011 - Open Source Conference 2011
-    Tokyo/Spring](#opensourceconf2011-spring)
--   [Feb 2011 - FOSDEM 2011 Brussels, Belgium](#fosdem2011)
--   [Feb 2011 - Open Source Conference 2011
-    Kagawa](#opensourceconf2011-kagawa)
--   [Dec 2010 - Open Source Conference 2010
-    Fukuoka](#opensourceconf2010-fukuoka)
--   [Nov 2010 - Journ�es M�dit�ran�ennes du Logiciel Libre in
-    Sophia-Antipolis.](#jm2l2010)
--   [Nov 2010 - Open Source Conference 2010
-    Shimane](#opensourceconf2010-Shimane)
--   [Nov 2010 - NYCBSDCon 2010](#nycbsdcon2010)
--   [Nov 2010 - Kansai OpenSource 2010](#kansai-os-jp-2010)
--   [Oct 2010 - Open Source Conference 2010
-    Niigata](#opensourceconf2010-Niigata)
--   [Oct 2010 - EuroBSDCon 2010](#eurobsdcon2010)
--   [Oct 2010 - Open Source Conference 2010
-    Okinawa](#opensourceconf2010-Okinawa)
--   [Sep 2010 - Open Source Conference 2010
-    Tokyo/Fall](#opensourceconf2010-tokyofall)
--   [Aug 2010 - Open Source Conference 2010
-    Nagoya](#opensourceconf2010-Nagoya)
--   [Jul 2010 - Open Source Conference 2010
-    Kansai](#opensourceconf2010-Kansai)
--   [Jul 2010 - Japan NetBSD Users' Group meeting & NetBSD
-    BOF](#jp-users-2010)
--   [Jun 2010 - Open Source Conference 2010
-    Hokkaido](#opensourceconf2010-DO)
--   [Jun 2010 - LinuxTag 2010](#linuxtag2010)
--   [May 2010 - pkgsrcCon 2010 Basel, Switzerland](#pkgsrcCon-2010)
--   [May 2010 - Open Source Conference 2010
-    Sendai](#opensourceconf2010-sendai)
--   [May 2010 - Rencontres Bretonnes du Logiciel Libre in
-    Rennes](#rmll2010)
--   [May 2010 - BSDCan 2010](#bsdcan2010)
--   [Mar 2010 - AsiaBSDCon 2010](#asiabsdcon-tokyo-2010)
--   [Mar 2010 - Open Source Conference 2010
-    Kansai@Kobe](#opensourceconf2010-kobe)
--   [Feb 2010 - Open Source Conference 2010
-    Tokyo/Spring](#opensourceconf2010-tokyo)
--   [Feb 2010 - Hackathon, February 2010](#hackathon-feb2010)
--   [Feb 2010 - FOSDEM 2010 Brussels, Belgium](#fosdem2010)
--   [Jan 2010 - Open Source Conference 2010
-    Oita](#opensourceconf2010-oita)
--   [Dec 2009 - Open Source Conference 2009
-    Fukuoka](#opensourceconf2009-fukuoka)
--   [Nov 2009 - Open Source Conference 2009
-    Kochi](#opensourceconf2009-kochi)
--   [Nov 2009 - OpenRheinRuhr 2009](#openrheinruhr2009)
--   [Nov 2009 - Kansai OpenSource 2009](#kansai-os-jp-2009)

(Diff truncated)
nit output format,delete {.code}
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/events.mdwn	4 Mar 2014 04:11:07 -0000	1.6
+++ wikisrc/events.mdwn	4 Mar 2014 04:28:49 -0000	1.7
@@ -502,7 +502,7 @@
 
 ### Future Events
 
-#### `Mar 2014`{.code} - AsiaBSDCon 2014 ([top](#future))
+#### `Mar 2014` - AsiaBSDCon 2014 ([top](#future))
 
 *Mar 13-16, 2014, Tokyo University of Science,Tokyo, Japan*
 
@@ -514,7 +514,7 @@
 presentations available to ensure that the latest developments in our
 open source community are shared with the widest possible audience.
 
-#### `Mar 2014`{.code} - Open Source Conference 2014 Hamanako ([top](#future))
+#### `Mar 2014` - Open Source Conference 2014 Hamanako ([top](#future))
 
 *Mar. 22, 2014, [Hamamatsu Shimin Kyodo
 Center](http://www.machien-hamamatsu.jp/) , Shizuoka, Japan*
@@ -526,7 +526,7 @@
 [hpcarm](../ports/hpcarm/), [hpcmips](../ports/hpcmips/),
 [hpcsh](../ports/hpcsh/)).
 
-#### `Jun 2014`{.code} - Open Source Conference 2014 Hokkaido ([top](#future))
+#### `Jun 2014` - Open Source Conference 2014 Hokkaido ([top](#future))
 
 *Jun. 13-14, 2014, [Sapporo Business Innovation Center, Sapporo,
 Japan](http://www.sapporosansin.jp/access/)*
@@ -538,7 +538,7 @@
 with NetBSD gadget demonstrations ( [hpcarm](../ports/hpcarm/),
 [hpcmips](../ports/hpcmips/), [hpcsh](../ports/hpcsh/)).
 
-#### `Jul 2014`{.code} - Open Source Conference 2014 Nagoya ([top](#future))
+#### `Jul 2014` - Open Source Conference 2014 Nagoya ([top](#future))
 
 *Jul. 4-5, 2014, [Nagoya International
 Center](http://www.nic-nagoya.or.jp/en/e/about-us/access-hours), Nagoya,
@@ -551,7 +551,7 @@
 (NBUG)](http://www.nagoya.bug.gr.jp/). There will be a gadget
 demonstration [BSD booth](http://twitpic.com/czat1r) and NBUG BOF.
 
-#### `Nov 2014`{.code} - Kansai OpenSource 2014 ([top](#future))
+#### `Nov 2014` - Kansai OpenSource 2014 ([top](#future))
 
 *Nov. 7-8, 2014, [Asia and Pacific Trade Center ITM
 Building](http://www.atc-co.com/), Osaka, Japan*
@@ -567,7 +567,7 @@
 
 ### Past Events
 
-#### `Feb 2014`{.code} - Open Source Conference 2014 Tokyo/Spring ([top](#past))
+#### `Feb 2014` - Open Source Conference 2014 Tokyo/Spring ([top](#past))
 
 *Feb. 28- Mar. 1, 2014, [MEISEI
 UNIVERSITY](http://www.meisei-u.ac.jp/access/hino.html), Tokyo, Japan*
@@ -583,21 +583,21 @@
 Users' Group got an award called "[Open Source Confernce
 Award](http://www.ospn.jp/press/20140218osc-award.html)".
 
-#### `Feb 2014`{.code} - NYC\*BSD Con 2014 ([top](#past))
+#### `Feb 2014` - NYC\*BSD Con 2014 ([top](#past))
 
 *Feb 8, 2014 Suspenders Bar and Restaurant*
 
 [NYC\*BSD Con 2014](http://www.nycbsdcon.org/2014/) NYCBSDCon is on as a
 day-long event with the theme of "The BSDs in Production."
 
-#### `Nov 2013`{.code} - Linux User Group of Mauritius - LinuxFest 2013 ([top](#past))
+#### `Nov 2013` - Linux User Group of Mauritius - LinuxFest 2013 ([top](#past))
 
 *Nov 25, 2013, Octave Wiehe Auditorium University of Mauritius*
 
 [Linux Fest 2013 in Mauritius](http://lugm.org/linuxfest/#) will feature
 some BSD thumb drives and other general IT and Open Source talks
 
-#### `Nov 2013`{.code} - Open Source Conference 2013 Oita ([top](#past))
+#### `Nov 2013` - Open Source Conference 2013 Oita ([top](#past))
 
 *Nov. 23, 2013, i-ness, Oita, Japan*
 
@@ -608,7 +608,7 @@
 [hpcarm](../ports/hpcarm/), [hpcmips](../ports/hpcmips/),
 [hpcsh](../ports/hpcsh/)).
 
-#### `Nov 2013`{.code} - Open Source Conference 2013 Fukuoka ([top](#past))
+#### `Nov 2013` - Open Source Conference 2013 Fukuoka ([top](#past))
 
 *Nov. 16, 2013, [Fukuoka Soft Research
 Park](http://www.fukuoka-srp.co.jp/access/index.html) , Fukuoka, Japan*
@@ -620,7 +620,7 @@
 [hpcarm](../ports/hpcarm/), [hpcmips](../ports/hpcmips/),
 [hpcsh](../ports/hpcsh/))
 
-#### `Nov 2013`{.code} - Kansai OpenSource 2013 ([top](#past))
+#### `Nov 2013` - Kansai OpenSource 2013 ([top](#past))
 
 *Nov. 8-9, 2013, [Asia and Pacific Trade Center ITM
 Building](http://www.atc-co.com/), Osaka, Japan*
@@ -632,7 +632,7 @@
 [hpcarm](../ports/hpcarm/), [hpcmips](../ports/hpcmips/),
 [hpcsh](../ports/hpcsh/) } and BSDBOF.
 
-#### `Oct 2013`{.code} - Open Source Conference 2013 Tokyo/Fall ([top](#past))
+#### `Oct 2013` - Open Source Conference 2013 Tokyo/Fall ([top](#past))
 
 *Oct. 19-20, 2013, [MEISEI
 UNIVERSITY](http://www.meisei-u.ac.jp/access/hino.html), Tokyo, Japan*
@@ -644,7 +644,7 @@
 [hpcarm](../ports/hpcarm/), [hpcmips](../ports/hpcmips/),
 [hpcsh](../ports/hpcsh/)) and BSDBOF.
 
-#### `Oct 2013`{.code} - Open Source Conference 2013 Hiroshima ([top](#past))
+#### `Oct 2013` - Open Source Conference 2013 Hiroshima ([top](#past))
 
 *Oct. 6, 2013, [Satellite Campus
 Hiroshima](http://www.pu-hiroshima.ac.jp/site/satellite/accessmap.html)
@@ -657,7 +657,7 @@
 [hpcarm](../ports/hpcarm/), [hpcmips](../ports/hpcmips/),
 [hpcsh](../ports/hpcsh/)).
 
-#### `Sep 2013`{.code} - Open Source Conference 2013 Hokkaido ([top](#past))
+#### `Sep 2013` - Open Source Conference 2013 Hokkaido ([top](#past))
 
 *Sep. 14, 2013, [Sapporo Convention Center, Sapporo,
 Japan](http://www.sora-scc.jp/access/index.html)*
@@ -669,7 +669,7 @@
 with NetBSD gadget demonstrations ( [hpcarm](../ports/hpcarm/),
 [hpcmips](../ports/hpcmips/), [hpcsh](../ports/hpcsh/)).
 
-#### `Aug 2013`{.code} - FrOSCon 2013 ([top](#past))
+#### `Aug 2013` - FrOSCon 2013 ([top](#past))
 
 *Aug. 24–25, 2013, [Bonn-Rhein-Sieg University of Applied Sciences,
 Campus
@@ -681,7 +681,7 @@
 with several "showcase" machines, handing out flyers and CDs and
 answering users' questions.
 
-#### `Aug 2013`{.code} - Open Source Conference 2013 Shimane ([top](#past))
+#### `Aug 2013` - Open Source Conference 2013 Shimane ([top](#past))
 
 *Aug. 24, 2013, [MATSUE
 TERRSA](http://www.sanbg.com/terrsa/e/index.html), Shimane, Japan*
@@ -699,7 +699,7 @@
 NetBSD/evbarmv6hf](http://mail-index.netbsd.org/port-arm/2013/08/23/msg001984.html)
 ). more reports on [togetter](http://togetter.com/li/553529).
 
-#### `Aug 2013`{.code} - Open Source Conference 2013 Kansai@Kyoto ([top](#past))
+#### `Aug 2013` - Open Source Conference 2013 Kansai@Kyoto ([top](#past))
 
 *Aug. 2-3, 2013, [KYOTO RESEARCH
 PARK](http://www.krp.co.jp/english/access/index.html), Kyoto, Japan*
@@ -718,7 +718,7 @@
 Sheep?,](http://www.ceres.dti.ne.jp/tsutsui/osc2013kyoto/NetBSD-luna68k_mlterm-fb_Twitter.html)
 ). more report on [togetter](http://togetter.com/li/542885).
 
-#### `Jul 2013`{.code} - Japan NetBSD Users' Group meeting & NetBSD BOF ([top](#past))
+#### `Jul 2013` - Japan NetBSD Users' Group meeting & NetBSD BOF ([top](#past))
 
 *Jul 13, 2013, [VLSI Design and Education Center University of
 Tokyo](http://www.vdec.u-tokyo.ac.jp/English/contact.html), Tokyo,
@@ -729,7 +729,7 @@
 for meeting information.[more detail on
 togetter](http://togetter.com/li/532926).
 
-#### `Jul 2013`{.code} - Open Source Conference 2013 Okinawa ([top](#past))
+#### `Jul 2013` - Open Source Conference 2013 Okinawa ([top](#past))
 
 *Jul. 6, 2013, [Okinawa Convention
 Center](http://www.oki-conven.jp/en/modules/tinyd7/page/page1.html) ,
@@ -744,7 +744,7 @@
 [XM6i](http://xm6i.org/)).[more detail on
 togetter](http://togetter.com/li/529669).
 
-#### `Jun 2013`{.code} - Open Source Conference 2013 Nagoya ([top](#past))
+#### `Jun 2013` - Open Source Conference 2013 Nagoya ([top](#past))
 
 *Jun. 21-22, 2013, [Nagoya International
 Center](http://www.nic-nagoya.or.jp/en/e/about-us/access-hours), Nagoya,
@@ -780,7 +780,7 @@
 See the [Linuxtag homepage](http://www.linuxtag.org/2013/en.html) for
 more information.
 
-#### `May 2013`{.code} - BSDCan 2013, Ottawa, Canada ([top](#past))
+#### `May 2013` - BSDCan 2013, Ottawa, Canada ([top](#past))
 
 *May 17-18, 2013, Ottawa, Canada.*
 
@@ -795,7 +795,7 @@
 papers](http://mail-index.NetBSD.org/netbsd-advocacy/2012/12/09/msg000506.html)
 for details.
 
-#### `Apr 2013`{.code} - Central European BSD-Day 2013, Naples, Italy ([top](#past))

(Diff truncated)
delete placeholder,oked by marc.
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/events.mdwn	4 Mar 2014 02:50:37 -0000	1.5
+++ wikisrc/events.mdwn	4 Mar 2014 04:11:07 -0000	1.6
@@ -1,7 +1,3 @@
-# This page is currently a placeholder for an upcoming listing of events
-
-For questions, ask [mbalmer](mailto:mbalmer@netbsd.org), as he's one reserving this space...
-
 NetBSD Events
 =============
 

delete footer
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/events.mdwn	4 Mar 2014 02:48:59 -0000	1.4
+++ wikisrc/events.mdwn	4 Mar 2014 02:50:37 -0000	1.5
@@ -4988,8 +4988,3 @@
 state, goals and future directions of the project, while Paul
 Kranenburg, Aaron Brown and Chris Demetriou answered questions about the
 sparc and the alpha ports respectively.
-
-[Contact](http://www.NetBSD.org/cgi-bin/feedback.cgi) |
-[Disclaimer](../about/disclaimer.html) | Copyright � 1994-2014 The
-NetBSD Foundation, Inc. ALL RIGHTS RESERVED.\
-NetBSD^�^ is a registered trademark of The NetBSD Foundation, Inc.

delete navigation bars.
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/events.mdwn	4 Mar 2014 02:34:29 -0000	1.3
+++ wikisrc/events.mdwn	4 Mar 2014 02:48:59 -0000	1.4
@@ -2,62 +2,6 @@
 
 For questions, ask [mbalmer](mailto:mbalmer@netbsd.org), as he's one reserving this space...
 
-[Skip to main content.](#mainContent)
-
-[![[NetBSD Logo]](../images/NetBSD-smaller.png)](../)
-
-[The NetBSD Project](../)
-
-[“Of course it runs NetBSD”](../)
-
-Google custom search
-
-Navigation:
-
--   [Home](../)
--   [News & Media](../)
-    -   [Recent changes](../changes/)
-    -   [NetBSD blog](http://blog.NetBSD.org/)
-    -   [Events](../gallery/events.html)
-    -   [Feeds](../changes/rss.html)
-
--   [About](../about/)
-    -   [NetBSD](../about/)
-    -   [The NetBSD Foundation](../foundation/)
-    -   [Advocacy](../gallery/)
-
--   [Documentation](../docs/)
-    -   [FAQ & HOWTOs](../docs/misc/index.html)
-    -   [The Guide](../docs/guide/en/)
-    -   [Manual pages](http://man.NetBSD.org/)
-    -   [Wiki](http://wiki.NetBSD.org/)
-
--   [Support](../support/)
-    -   [Problem report guide](../support/send-pr.html)
-    -   [Report a bug](../cgi-bin/sendpr.cgi?gndb=netbsd)
-    -   [Query bug database](../support/query-pr.html)
-    -   [Security](../support/security/)
-
--   [Community](../community/)
-    -   [Blogs](http://onetbsd.org/)
-    -   [Mailing lists](../mailinglists/)
-    -   [List archives](http://mail-index.NetBSD.org/)
-
--   [Developers](../developers/)
-    -   [Browse source](http://cvsweb.NetBSD.org/)
-    -   [Cross-reference](http://nxr.NetBSD.org/)
-    -   [Release engineering](http://releng.NetBSD.org/)
-    -   [Projects list](http://wiki.NetBSD.org/projects/)
-
--   [Ports](../ports/)
-    -   [History](../ports/history.html)
-    -   [Emulators](../ports/emulators.html)
-
--   [Packages](http://www.pkgsrc.org/)
-    -   [Browse packages](http://www.pkgsrc.se/)
-    -   [Release
-        engineering](http://releng.NetBSD.org/index-pkgsrc.html)
-
 NetBSD Events
 =============
 

sync from www.netbsd.org via pandoc
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/events.mdwn	27 Feb 2014 05:23:24 -0000	1.2
+++ wikisrc/events.mdwn	4 Mar 2014 02:34:29 -0000	1.3
@@ -70,8 +70,6 @@
 
 ### Future Events
 
--   [Feb 2014 - Open Source Conference 2014
-    Tokyo/Spring](#opensourceconf2014-tokyospring)
 -   [Mar 2014 - AsiaBSDCon 2014](#asiabsdcon-tokyo-2014)
 -   [Mar 2014 - Open Source Conference 2014
     Hamanako](#opensourceconf2014-hamamatsu)
@@ -83,6 +81,8 @@
 
 ### Past Events
 
+-   [Feb 2014 - Open Source Conference 2014
+    Tokyo/Spring](#opensourceconf2014-tokyospring)
 -   [Feb 2014 - NYC\*BSD Con 2014](#NYCBSDCon2014)
 -   [Nov 2013 - Linux User Group of Mauritius - LinuxFest
     2013](#LinuxFest2013Mauritius)
@@ -562,18 +562,6 @@
 
 ### Future Events
 
-#### `Feb 2014`{.code} - Open Source Conference 2014 Tokyo/Spring ([top](#future))
-
-*Feb. 28- Mar. 1, 2014, [MEISEI
-UNIVERSITY](http://www.meisei-u.ac.jp/access/hino.html), Tokyo, Japan*
-
-At the [Open Source Conference 2014
-Tokyo/Spring](http://www.ospn.jp/osc2014-spring/), there will be a
-NetBSD booth staffed by members of the [Japan NetBSD Users'
-Group](http://www.jp.NetBSD.org/) with NetBSD gadget demonstrations (
-[hpcarm](../ports/hpcarm/), [hpcmips](../ports/hpcmips/),
-[hpcsh](../ports/hpcsh/)).
-
 #### `Mar 2014`{.code} - AsiaBSDCon 2014 ([top](#future))
 
 *Mar 13-16, 2014, Tokyo University of Science,Tokyo, Japan*
@@ -639,6 +627,22 @@
 
 ### Past Events
 
+#### `Feb 2014`{.code} - Open Source Conference 2014 Tokyo/Spring ([top](#past))
+
+*Feb. 28- Mar. 1, 2014, [MEISEI
+UNIVERSITY](http://www.meisei-u.ac.jp/access/hino.html), Tokyo, Japan*
+
+At the [Open Source Conference 2014
+Tokyo/Spring](http://www.ospn.jp/osc2014-spring/), there was a NetBSD
+booth staffed by members of the [Japan NetBSD Users'
+Group](http://www.jp.NetBSD.org/) with NetBSD gadget demonstrations (
+[hpcarm](../ports/hpcarm/), [zaurus](../ports/zaurus/),
+[evbarm](../ports/evbarm/)). [2014-02-28-netbsd-raspi
+image](http://mail-index.netbsd.org/port-arm/2014/02/28/msg002243.html)).
+more reports on [togetter](http://togetter.com/li/635747). Japan NetBSD
+Users' Group got an award called "[Open Source Confernce
+Award](http://www.ospn.jp/press/20140218osc-award.html)".
+
 #### `Feb 2014`{.code} - NYC\*BSD Con 2014 ([top](#past))
 
 *Feb 8, 2014 Suspenders Bar and Restaurant*

Note the new mcp48x1dac driver.
Index: wikisrc/users/rkujawa.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/rkujawa.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/users/rkujawa.mdwn	26 Dec 2013 00:11:50 -0000	1.39
+++ wikisrc/users/rkujawa.mdwn	27 Feb 2014 19:58:24 -0000	1.40
@@ -25,6 +25,7 @@
 * [[xsh|http://netbsd.gw.com/cgi-bin/man-cgi?xsh+4.amiga+NetBSD-current]] - Driver for the Individual Computers X-Surf 100 ethernet card.
 * [[mpl115a|http://netbsd.gw.com/cgi-bin/man-cgi?mpl115a++NetBSD-current]] - Freescale MPL115A2 pressure sensor driver.
 * [[acafh|http://netbsd.gw.com/cgi-bin/man-cgi?acafh+4.amiga+NetBSD-current]] - Individual Computers ACA500 driver.
+* mcp48x1dac - Microchip MCP48x1 series DAC driver.
 
 ## Ongoing projects
 

that did not help, revert.
can someone who knows about markdown fix this? it's supposed to have
numbered paragraphs 1-5, two with small subparagraphs, and it would
really be better not to give the small bits top-level numbers.
Members: 
	projects/project/fonthandling.mdwn:1.5->1.6 

Index: wikisrc/projects/project/fonthandling.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fonthandling.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/fonthandling.mdwn	27 Feb 2014 09:12:54 -0000	1.5
+++ wikisrc/projects/project/fonthandling.mdwn	27 Feb 2014 09:24:14 -0000	1.6
@@ -25,13 +25,13 @@
 
 1. Figure out for certain if fontconfig is the right solution. Note that even if the code isn't, the model may be. If fontconfig is not the right solution, figure out what the right solution is. Also ascertain whether existing applications that use the fontconfig API can be supported easily/directly or if some kind of possibly messy wrapper layer is needed and doing things *right* requires changing applications. Convince the developer community that your conclusions are correct so that you can go on to step 2.
 
-1.1. Part of this is identifying exactly what is involved in "managing" and "handling" fonts and what applications require.
+1a. Part of this is identifying exactly what is involved in "managing" and "handling" fonts and what applications require.
 
 2. Implement the infrastructure. If fontconfig is the right solution, this entails moving it from the X sources to the base sources. Also, some of the functionality/configurability of fontconfig is probably not needed in a canonicalized environment. All of this should be disabled if possible. If fontconfig is not the right solution, implement something else in base.
 
 3. Integrate the new solution in base. Things in base that use fonts should use fontconfig or the replacement for fontconfig. This includes console font handling, groff, mandoc, and X11. Also, the existing fonts that are currently available only to subsets of things in base should be made available to all software through fontconfig or its replacement.
 
-3.1. It would also be useful to kill off the old xfontsel and replace it with something that interoperates fully with the new system and also has a halfway decent user interface.
+3a. It would also be useful to kill off the old xfontsel and replace it with something that interoperates fully with the new system and also has a halfway decent user interface.
 
 4. Deploy support in pkgsrc. If the new system does not itself provide the fontconfig API, provide support for that via a wrapper package. Teach applications in pkgsrc that use fontconfig to recognize and use the new system. (This should be fairly straightforward and not require patching anything.) Make pkgsrc font installation interoperate with the new system. (This should be fairly straightforward too.) Take an inventory of applications that use fonts but don't use fontconfig. Patch one or two of these to use the new system to show that it can be done easily. If the new system is not fontconfig and has its own better API, take an inventory of applications that would benefit from being patched to use the new API. Patch one or two of these to demonstrate that it can be done easily. (If the answers from step 1 are correct, it should be fairly easy for most ordinary applications.)
 

category misc
Index: wikisrc/projects/project/lua_bindings_chicken_and_egg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/lua_bindings_chicken_and_egg.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/lua_bindings_chicken_and_egg.mdwn	29 Sep 2013 23:42:57 -0000	1.4
+++ wikisrc/projects/project/lua_bindings_chicken_and_egg.mdwn	27 Feb 2014 09:21:31 -0000	1.5
@@ -6,7 +6,7 @@
 [tech-kern](mailto:tech-kern@NetBSD.org)
 """
 
-category="lua"
+category="misc"
 difficulty="medium"
 duration="3 months"
 

fix syntax error
Index: wikisrc/projects/project/pkgsrc_gnome_support.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_gnome_support.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/pkgsrc_gnome_support.mdwn	30 Jul 2013 19:44:21 -0000	1.1
+++ wikisrc/projects/project/pkgsrc_gnome_support.mdwn	27 Feb 2014 09:20:48 -0000	1.2
@@ -21,6 +21,7 @@
 
 A harder step is to port the devicekit and libudev parts of GNOME.
 
+"""
 ]]
 
 [[!tag gsoc]]

add a page for ZFS
(someone who knows what the current ZFS state is please expand this)
Members: 
	projects/project/zfs.mdwn:INITIAL->1.1 

--- /dev/null	2014-03-30 15:32:01.000000000 +0000
+++ wikisrc/projects/project/zfs.mdwn	2014-03-30 15:37:41.000000000 +0000
@@ -0,0 +1,20 @@
+[[!template id=project
+
+title="Finish ZFS"
+
+contact="""
+[tech-kern](mailto:tech-kern@NetBSD.org)
+"""
+
+category="filesystems"
+difficulty="medium"
+duration="3-9 months?"
+
+description="""
+The ZFS port to NetBSD is half-done, or maybe more than half. Finish
+it and get it really running.
+
+(This page is a stub. Someone who knows what the current state is,
+please expand it.)
+"""
+]]

mention cups as a negative example
Index: wikisrc/projects/project/lpr.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/lpr.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/lpr.mdwn	25 Mar 2012 21:22:32 -0000	1.3
+++ wikisrc/projects/project/lpr.mdwn	27 Feb 2014 09:16:40 -0000	1.4
@@ -18,5 +18,9 @@
 The current lpr/lpd system in NetBSD is ancient, and doesn't support modern printer systems very well. Interested parties would do a from scratch rewrite of a new, modular lpr/lpd system that would support both the old lpd protocol and newer, more modern protocols like IPP, and would be able to handle modern printers easily.
 
 This project is not intrinsically difficult, but will involve a rather large chunk of work to complete.
+
+Note that the goal of this exercise is not to reimplement cups -- cups
+already exists and one like it was enough.
+
 """
 ]]

let's see if this will make ikiwiki not destroy the paragraph numbering
Index: wikisrc/projects/project/fonthandling.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fonthandling.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/fonthandling.mdwn	26 Mar 2012 19:47:01 -0000	1.4
+++ wikisrc/projects/project/fonthandling.mdwn	27 Feb 2014 09:12:54 -0000	1.5
@@ -25,13 +25,13 @@
 
 1. Figure out for certain if fontconfig is the right solution. Note that even if the code isn't, the model may be. If fontconfig is not the right solution, figure out what the right solution is. Also ascertain whether existing applications that use the fontconfig API can be supported easily/directly or if some kind of possibly messy wrapper layer is needed and doing things *right* requires changing applications. Convince the developer community that your conclusions are correct so that you can go on to step 2.
 
-1a. Part of this is identifying exactly what is involved in "managing" and "handling" fonts and what applications require.
+1.1. Part of this is identifying exactly what is involved in "managing" and "handling" fonts and what applications require.
 
 2. Implement the infrastructure. If fontconfig is the right solution, this entails moving it from the X sources to the base sources. Also, some of the functionality/configurability of fontconfig is probably not needed in a canonicalized environment. All of this should be disabled if possible. If fontconfig is not the right solution, implement something else in base.
 
 3. Integrate the new solution in base. Things in base that use fonts should use fontconfig or the replacement for fontconfig. This includes console font handling, groff, mandoc, and X11. Also, the existing fonts that are currently available only to subsets of things in base should be made available to all software through fontconfig or its replacement.
 
-3a. It would also be useful to kill off the old xfontsel and replace it with something that interoperates fully with the new system and also has a halfway decent user interface.
+3.1. It would also be useful to kill off the old xfontsel and replace it with something that interoperates fully with the new system and also has a halfway decent user interface.
 
 4. Deploy support in pkgsrc. If the new system does not itself provide the fontconfig API, provide support for that via a wrapper package. Teach applications in pkgsrc that use fontconfig to recognize and use the new system. (This should be fairly straightforward and not require patching anything.) Make pkgsrc font installation interoperate with the new system. (This should be fairly straightforward too.) Take an inventory of applications that use fonts but don't use fontconfig. Patch one or two of these to use the new system to show that it can be done easily. If the new system is not fontconfig and has its own better API, take an inventory of applications that would benefit from being patched to use the new API. Patch one or two of these to demonstrate that it can be done easily. (If the answers from step 1 are correct, it should be fairly easy for most ordinary applications.)
 

Rewrite in light of the existence of mandoc. Rather than just "rewrite
groff", this project is now "solve the problem we have with
typesetting non-manpage docs". There are a bunch of options for that
but they're all pretty unappealing.
Index: wikisrc/projects/project/troff.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/troff.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/troff.mdwn	27 Feb 2014 08:41:03 -0000	1.3
+++ wikisrc/projects/project/troff.mdwn	27 Feb 2014 09:04:43 -0000	1.4
@@ -10,14 +10,74 @@
 difficulty="hard"
 
 description="""
-Write a replacement for groff that is BSD licensed.  Earlier versions of BSD
-UNIX had one, so maybe it could be revived from an earlier version of BSD UNIX,
-and updated to support newer groff-like features, at least enough to support our
-current mandoc macros.
-
-Note: In March, 2009, there was some discussion regarding a
-[groff/-mandoc replacement](http://mdocml.bsd.lv/) on the
-[tech-userlevel](http://mail-index.NetBSD.org/tech-userlevel/2009/03/01/msg001766.html)
-mailing list.
+
+While we now have mandoc for handling man pages, we currently still
+need groff in the tree to handle miscellaneous docs that are not man
+pages.
+
+This is itself an inadequate solution as the groff we have does not
+support PDF output (which in this day and age is highly desirable)
+... and while newer groff does support PDF output it does so via a
+Perl script. Also, importing a newer groff is problematic for assorted
+other reasons.
+
+We need a way to typeset miscellaneous articles that we can import
+into base and that ideally is BSD licensed. (And that can produce
+PDFs.) Currently it looks like there are three decent ways forward:
+
+* Design a new roff macro package that's comparable to mdoc (e.g.
+supports semantic markup) but is for miscellaneous articles rather
+than man pages, then teach mandoc to handle it.
+
+* Design a new set of markup tags comparable to mdoc (e.g. supports
+semantic markup) but for miscellaneous articles, and a different less
+ratty syntax for it, then teach mandoc to handle this.
+
+* Design a new set of markup tags comparable to mdoc (e.g. supports
+semantic markup) but for miscellaneous articles, and a different less
+ratty syntax for it, and write a new program akin to mandoc to handle
+it.
+
+These are all difficult and a lot of work, and in the case of new
+syntax are bound to cause a lot of shouting and stamping. Also, many
+of the miscellaneous documents use various roff preprocessors and it
+isn't clear how much of this mandoc can handle.
+
+None of these options is particularly appealing.
+
+There are also some less decent ways forward:
+
+* Pick one of the existing roff macro packages for miscellaneous
+articles (ms, me, ...) and teach mandoc to handle it. Unfortunately
+all of these macro packages are pretty ratty, they're underpowered
+compared to mdoc, and none of them support semantic markup.
+
+* Track down one of the other older roff implementations, that are now
+probably more or less free (e.g. ditroff), then stick to the existing
+roff macro packages as above. In addition to the drawbacks cited
+above, any of these programs are likely to be old nasty code that
+needs a lot of work.
+
+* Teach the groff we have how to emit PDFs, then stick to the existing
+roff macro packages as above. In addition to the drawbacks cited
+above, this will likely be pretty nasty work and it's still got the
+wrong license.
+
+* Rewrite groff as BSD-licensed code and provide support for
+generating PDFs, then stick to the existing roff macro packages as
+above. In addition to the drawbacks cited above, this is a horrific
+amount of work.
+
+* Try to make something else do what we want. Unfortunately, TeX is a
+nonstarter and the only other halfway realistic candidate is lout...
+which is GPLv3 and at least at casual inspection looks like a horrible
+mess of its own.
+
+These options are even less appealing.
+
+Maybe someone can think of a better idea. There are lots of choices if
+we give up on typeset output, but that doesn't seem like a good plan
+either.
+
 """
 ]]

Reimplementing groff is not EASY, it is HARD. Sheesh.
Index: wikisrc/projects/project/troff.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/troff.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/troff.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/troff.mdwn	27 Feb 2014 08:41:03 -0000	1.3
@@ -7,7 +7,7 @@
 """
 
 category="userland"
-difficulty="easy"
+difficulty="hard"
 
 description="""
 Write a replacement for groff that is BSD licensed.  Earlier versions of BSD

networking project (userland or not)
Index: wikisrc/projects/project/ipv6-stable-privacy-addresses.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ipv6-stable-privacy-addresses.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/ipv6-stable-privacy-addresses.mdwn	19 Apr 2013 05:46:43 -0000	1.3
+++ wikisrc/projects/project/ipv6-stable-privacy-addresses.mdwn	27 Feb 2014 08:38:59 -0000	1.4
@@ -8,7 +8,7 @@
 mentors="""
 [S.P.Zeidler](mailto:spz@NetBSD.org)
 """
-category="userland"
+category="networking"
 difficulty="easy"
 duration="3 months"
 

thinko in previous
Index: wikisrc/projects/project/bsdmake-enhancements.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/bsdmake-enhancements.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/bsdmake-enhancements.mdwn	27 Feb 2014 08:37:50 -0000	1.2
+++ wikisrc/projects/project/bsdmake-enhancements.mdwn	27 Feb 2014 08:38:07 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Suffix rules in BSD Make"
+title="Suffix and pattern rules in BSD make"
 
 contact="""
 [tech-toolchain](mailto:tech-toolchain@NetBSD.org)

Update title: this is about gmake pattern rules.
Mark project "medium", not "easy", as nothing in make is "easy".
Expand project scope a bit to avoid generating code for yet another
special case hack.
Also mention rules written in terms of $(.TARGET), which already work
and are more general than gmake pattern rules.
Also mention rules written in terms of $(.TARGET), which already work
and are more general than gmake pattern rules.

Members: 
	projects/project/bsdmake-enhancements.mdwn:1.1->1.2 

Index: wikisrc/projects/project/bsdmake-enhancements.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/bsdmake-enhancements.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/bsdmake-enhancements.mdwn	6 Nov 2011 19:58:46 -0000	1.1
+++ wikisrc/projects/project/bsdmake-enhancements.mdwn	27 Feb 2014 08:37:50 -0000	1.2
@@ -1,20 +1,38 @@
 [[!template id=project
 
-title="Make enhancements"
+title="Suffix rules in BSD Make"
 
 contact="""
 [tech-toolchain](mailto:tech-toolchain@NetBSD.org)
 """
 
 category="userland"
-difficulty="easy"
+difficulty="medium"
 duration="1 month"
 
 description="""
-BSD make (aka pmake) uses suffix rules (.c.o: ...)  instead of pattern rules
-(%.c:%.o: ...) which are more general and flexible. The suffix module should be
-re-written so that is based on pattern rules, and pattern rules should be
-implemented. This will gain 90% compatibility with GNU make, and the rest
-(variable manipulations) can easily be added.
+
+BSD make (aka bmake) uses traditional suffix rules (.c.o: ...) instead
+of pattern rules like gmake's (%.c:%.o: ...) which are more general
+and flexible.
+
+The suffix module should be re-written to work from a general
+match-and-transform function on targets, which is sufficient to
+implement not only traditional suffix rules and gmake pattern rules,
+but also whatever other more general transformation rule syntax comes
+down the pike next. Then the suffix rule syntax and pattern rule
+syntax can both be fed into this code.
+
+Note that it is already possible to write rules where the source is
+computed explicitly based on the target, simply by using $(.TARGET) in
+the right hand side of the rule. Investigate whether this logic should
+be rewritten using the match-and-transform code, or if the
+match-and-transform code should use the logic that makes these rules
+possible instead.
+
+Implementing pattern rules is widely desired in order to be able to
+read more makefiles written for gmake, even though gmake's pattern
+rules aren't well designed or particularly principled.
+
 """
 ]]

pkgsrc, not ports
Index: wikisrc/projects/project/qtopia.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/qtopia.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/qtopia.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/qtopia.mdwn	27 Feb 2014 08:24:30 -0000	1.3
@@ -6,7 +6,7 @@
 [tech-embed](mailto:tech-embed@NetBSD.org)
 """
 
-category="ports"
+category="pkgsrc"
 difficulty="hard"
 
 description="""

mention that this is underway
Index: wikisrc/projects/project/sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sun4v.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/sun4v.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/sun4v.mdwn	27 Feb 2014 08:23:21 -0000	1.3
@@ -13,5 +13,8 @@
 description="""
 It would be nice to support these newer highly SMP processors from Sun.  A Linux
 port already exists, and Sun has contributed code to the FOSS community.
+
+(Some work has already been done and committed.)
+
 """
 ]]

mention riastradh-drm2 branch
Index: wikisrc/projects/project/kms-gem.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/kms-gem.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/kms-gem.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/kms-gem.mdwn	27 Feb 2014 08:21:23 -0000	1.3
@@ -20,5 +20,8 @@
 The goal of this project is to add the missing bits inside NetBSD, most notably
 KMS and GEM. Testing the port using a recent driver like nouveau would be worth
 the effort.
+
+Work on this is underway on the riastradh-drm2 branch.
+
 """
 ]]

filesystems project
Index: wikisrc/projects/project/imapfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/imapfs.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/imapfs.mdwn	6 Nov 2011 19:58:46 -0000	1.1
+++ wikisrc/projects/project/imapfs.mdwn	27 Feb 2014 08:19:48 -0000	1.2
@@ -6,7 +6,7 @@
 [tech-userlevel](mailto:tech-userlevel@NetBSD.org)
 """
 
-category="misc"
+category="filesystems"
 difficulty="hard"
 
 description="""

based on history this should be "hard"
Index: wikisrc/projects/project/syspkgs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/syspkgs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/syspkgs.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/syspkgs.mdwn	27 Feb 2014 08:18:39 -0000	1.3
@@ -8,12 +8,15 @@
 """
 
 category="misc"
-difficulty="medium"
+difficulty="hard"
 
 description="""
 syspkgs is the concept of using pkgsrc's pkg_* tools to maintain the base
 system.  That is, allow users to register and components of the base system
-with more ease.  There has been a lot of work in this area already, but it
-has not yet been finalized.
+with more ease.
+
+There has been a lot of work in this area already, but it has not yet
+been finalized. Which is a diplomatic way of saying that this project
+has been attempted repeatedly and failed every time.
 """
 ]]

filesystems project
Index: wikisrc/projects/project/tcp-writing.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/tcp-writing.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/tcp-writing.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/tcp-writing.mdwn	27 Feb 2014 08:16:38 -0000	1.3
@@ -6,7 +6,7 @@
 [tech-kern](mailto:tech-kern@NetBSD.org)
 """
 
-category="kernel"
+category="filesystems"
 difficulty="hard"
 duration="2 months"
 

Remove another bad link pointing to the gsoc projects page.
Index: wikisrc/projects/project/improved-automounter-support.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/improved-automounter-support.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/improved-automounter-support.mdwn	27 Feb 2014 08:08:54 -0000	1.4
+++ wikisrc/projects/project/improved-automounter-support.mdwn	27 Feb 2014 08:09:16 -0000	1.5
@@ -20,7 +20,7 @@
 * File systems are not mounted directly on the desired mount point. As a result applications frequently use incorrect pathnames (e.g. `/amd/server/home/user` instead of `/home/user`) for automatically mounted directories or files beneath them. This is especially problematic in heterogeneous enviroments where not all machines use the same automounter.
 * The automounter daemon cannot handle high I/O load very well; file access occasionally fails with intermittent errors.
 
-The goal of this project is to implement a new automounter solution which addresses the above issues. This could either be done via a Solaris/Linux compatible autofs(4) full in-kernel file system or via a userland daemon using [puffs](http://www.netbsd.org/contrib/soc-projects.html). 
+The goal of this project is to implement a new automounter solution which addresses the above issues. This could either be done via a Solaris/Linux compatible autofs(4) full in-kernel file system or via a userland daemon using puffs. 
 """
 ]]
 

fix typo
Index: wikisrc/projects/project/improved-automounter-support.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/improved-automounter-support.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/improved-automounter-support.mdwn	27 Feb 2014 08:07:35 -0000	1.3
+++ wikisrc/projects/project/improved-automounter-support.mdwn	27 Feb 2014 08:08:54 -0000	1.4
@@ -18,7 +18,7 @@
 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:
 
 * File systems are not mounted directly on the desired mount point. As a result applications frequently use incorrect pathnames (e.g. `/amd/server/home/user` instead of `/home/user`) for automatically mounted directories or files beneath them. This is especially problematic in heterogeneous enviroments where not all machines use the same automounter.
-* The automounter daemon cannot handle high I/O load very well, file access occasionally fails with intermittent errors.
+* The automounter daemon cannot handle high I/O load very well; file access occasionally fails with intermittent errors.
 
 The goal of this project is to implement a new automounter solution which addresses the above issues. This could either be done via a Solaris/Linux compatible autofs(4) full in-kernel file system or via a userland daemon using [puffs](http://www.netbsd.org/contrib/soc-projects.html). 
 """

Remove broken link. Wherever "The Berkeley Automounter Suite of
Utilities" may have been intended to point to, it is currently
pointing to http://www.netbsd.org/contrib/soc-projects.html, which
isn't remotely useful.
Just write "amd" instead, it'll do for the time being.
Members: 
	projects/project/improved-automounter-support.mdwn:1.2->1.3 

Index: wikisrc/projects/project/improved-automounter-support.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/improved-automounter-support.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/improved-automounter-support.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/improved-automounter-support.mdwn	27 Feb 2014 08:07:35 -0000	1.3
@@ -15,7 +15,7 @@
 duration="3 months"
 
 description="""
-NetBSD currently uses [The Berkeley Automounter Suite of Utilities](http://www.netbsd.org/contrib/soc-projects.html) 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:
+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:
 
 * File systems are not mounted directly on the desired mount point. As a result applications frequently use incorrect pathnames (e.g. `/amd/server/home/user` instead of `/home/user`) for automatically mounted directories or files beneath them. This is especially problematic in heterogeneous enviroments where not all machines use the same automounter.
 * The automounter daemon cannot handle high I/O load very well, file access occasionally fails with intermittent errors.

Rewrite and expand.
This is not going to be as easy as the person who originally wrote the
page thought.
Members: 
	projects/project/improve-caching.mdwn:1.2->1.3 

Index: wikisrc/projects/project/improve-caching.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/improve-caching.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/improve-caching.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/improve-caching.mdwn	27 Feb 2014 08:04:16 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Improve caching"
+title="Coordinated caching and scheduling"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)
@@ -8,12 +8,70 @@
 
 category="kernel"
 difficulty="hard"
-duration="4 months"
+duration="4 months and up"
 
 description="""
-Replace all of the knobs and wacky algorithms for sizing the many separate LRU
-caches in our kernel (for pages and for various kinds of objects like metadata
-buffers, mbufs, etc.)  with a generalized (N-way) algorithm like IBM's ARC
-("Adaptive Replacement Cache") to size all the caches for optimal hit rate.
+
+There are many caches in the kernel. Most of these have knobs and
+adjustments, some exposed and some not, for sizing and writeback rate
+and flush behavior and assorted other voodoo, and most of the ones
+that aren't adjustable probably should be.
+
+Currently all or nearly all of these caches operate on autopilot
+independent of the others, which does not necessarily produce good
+results, especially if the system is operating in a performance regime
+different from when the behavior was tuned by the implementors.
+
+It would be nice if all these caches were instead coordinated, so that
+they don't end up fighting with one another. Integrated control of
+sizing, for example, would allow explicitly maintaining a sensible
+balance between different memory uses based on current conditions;
+right now you might get that, depending on whether the available
+voodoo happens to work adequately under the workload you have, or you
+might not. Also, it is probably possible to define some simple rules
+about eviction, like not evicting vnodes that have UVM pages still to
+be written out, that can help avoid unnecessary thrashing and other
+adverse dynamic behavior. And similarly, it is probably possible to
+prefetch some caches based on activity in others. It might even be
+possible to come up with one glorious unified cache management
+algorithm.
+
+Also note that cache eviction and prefetching is fundamentally a form
+of scheduling, so all of this material should also be integrated with
+the process scheduler to allow *it* to make more informed decisions.
+
+This is a nontrivial undertaking.
+
+Step 1 is to just find all the things in the kernel that ought to
+participate in a coordinated caching and scheduling scheme. This
+should not take all that long. Some examples include:
+* UVM pages
+* file system metadata buffers
+* VFS name cache
+* vnode cache
+* size of the mbuf pool
+
+Step 2 is to restructure and connect things up so that it is readily
+possible to get the necessary information from all the random places
+in the kernel that these things occupy, without making a horrible mess
+and without trashing system performance in the process or deadlocking
+out the wazoo. This is not going to be particularly easy or fast.
+
+Step 3 is to take some simple steps, like suggested above, to do
+something useful with the coordinated information, and hopefully to
+show via benchmarks that it has some benefit.
+
+Step 4 is to look into more elaborate algorithms for unified control
+of everything. The previous version of this project cited IBM's ARC
+("Adaptive Replacement Cache") as one thing to look at. (But note that
+ARC may be encumbered -- someone please check on that and update this
+page.) Another possibility is to deploy machine learning algorithms to
+look for and exploit patterns.
+
+Note: this is a serious research project. Step 3 will yield a
+publishable minor paper; step 4 will yield a publishable major paper
+if you manage to come up with something that works, and it quite
+possibly contains enough material for a PhD thesis.
+
 """
 ]]

This is a filesystems project; tag it accordingly.
(It is also crazy, IMO, but I'm not touching that part)
Members: 
	projects/project/fs-services.mdwn:1.3->1.4 

Index: wikisrc/projects/project/fs-services.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fs-services.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/fs-services.mdwn	6 Nov 2011 14:48:47 -0000	1.3
+++ wikisrc/projects/project/fs-services.mdwn	27 Feb 2014 07:20:54 -0000	1.4
@@ -10,7 +10,7 @@
 [Antti Kantee](mailto:pooka@NetBSD.org)
 """
 
-category="kernel"
+category="filesystems"
 difficulty="medium"
 duration="3 months"
 

Rewrite and expand. (this is actually something I know a bit about)
Index: wikisrc/projects/project/flash-translation.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/flash-translation.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/flash-translation.mdwn	6 Nov 2011 19:58:46 -0000	1.1
+++ wikisrc/projects/project/flash-translation.mdwn	27 Feb 2014 07:18:03 -0000	1.2
@@ -10,7 +10,26 @@
 difficulty="medium"
 
 description="""
-Implement flash-translation layer to handle bad-block management/wear leveling
-such that a FFS or LFS file system could be placed on above NAND flash chip.
+
+Implement a flash translation layer.
+
+A flash translation layer does block remapping, translating from
+visible block addresses used by a file system to physical cells on
+one or more flash chips.
+This provides wear leveling, which is essential for effective use of
+flash, and also typically some amount of read caching and write
+buffering.
+(And it takes care of excluding cells that have gone bad.)
+
+This allows FFS, LFS, msdosfs, or whatever other conventional file
+system to be used on raw flash chips. (Note that SSDs and USB flash
+drives and so forth contain their own FTLs.)
+
+FTLs involve quite a bit of voodoo and there is a lot of prior art and
+research; do not just sit down and start coding.
+
+There are also some research FTLs that we might be able to get the
+code for; it is probably worth looking into this.
+
 """
 ]]

very minor edits
Index: wikisrc/projects/project/common-boot-cfg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/common-boot-cfg.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/common-boot-cfg.mdwn	17 Mar 2013 19:12:13 -0000	1.1
+++ wikisrc/projects/project/common-boot-cfg.mdwn	27 Feb 2014 07:00:44 -0000	1.2
@@ -15,12 +15,12 @@
 duration="3 months"
 
 description="""
-Several architectures support a /boot.cfg file (examples are i386, amd64 (which share a bootloader) and sparc64).
+Several ports support a /boot.cfg file. Examples are i386, amd64 (which share a bootloader) and sparc64.
 
 However, they do not share code, nor even the basic command parser. Obviously this is not the NetBSD way to do things
 and the situation needs to be improved.
 
-The goal of this project is to split the machine dependend parts out and provide generic, machine independent support
+The goal of this project is to split the machine dependent parts out and provide generic, machine independent support
 for most of the /boot.cfg handling, leaving configuration (like what commands are allowed) to the architecture specific
 code, as well as provide means for overriding command handlers (i.e. implement a common command differently).
 

Mention MAXPHYS, allude to tls-maxphys. This project may be
superfluous once tls-maxphys is done, but I'm not sure -- I think
aggregating contiguous buffers will probably still be worthwhile.
Index: wikisrc/projects/project/buffer-queue.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/buffer-queue.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/buffer-queue.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/buffer-queue.mdwn	27 Feb 2014 06:57:54 -0000	1.3
@@ -11,18 +11,24 @@
 duration="2-3 months"
 
 description="""
-NetBSD has a fixed, kernel-wide upper limit on transfer size, which is currently
-set to 64k on most port.  This is too small to have good performances on modern
+NetBSD has a fixed, kernel-wide upper limit on transfer size, called MAXPHYS, which is currently
+set to 64k on most ports.  This is too small to perform well on modern
 IDE and SCSI hardware; on the other hand some devices can't do more than 64k,
-and in some case are even limited to less (the Xen virtual block device for
+and in some cases are even limited to less (the Xen virtual block device for
 example).  Software RAID will also cause requests to be split in multiple
 smaller requests.
 
-NetBSD would greatly benefit from a more intelligent buffer queue management
-between the block device drivers and the higher levels (the framework here
-currently only applies some selectable algorithm to sort the queue).  This
-framework should be able to split buffers too large for a device into smaller
-ones, or aggregate multiple contiguous requests into a larger one.  This will
-most probably require change to at last some block device drivers.
+There is currently work in progress to make MAXPHYS configured at
+runtime based on driver capability.
+
+This project originaly suggested instead to make the buffer queue
+management logic (which currently only sorts the queue, aka disksort)
+capable of splitting too-large buffers or aggregating small contiguous
+buffers in order to conform to device-level requirements.
+
+Once the MAXPHYS changes are finalized and committed, this project may
+be simply outdated. However, it may also be worthwhile to pursue this
+idea as well, particularly the aggregation part.
+
 """
 ]]

This is actually about extended attributes (not multi-stream files per
se) and we've had extended attribute support of sorts for some time.
There are things about the extended attributes we have that could
stand improvement, but this project itself is not useful to keep
around.
Members: 
	projects/project/addsubfiles.mdwn:1.2->1.3(DEAD) 

--- wikisrc/projects/project/addsubfiles.mdwn	2014-03-30 15:37:42.000000000 +0000
+++ /dev/null	2014-03-30 15:32:01.000000000 +0000
@@ -1,20 +0,0 @@
-[[!template id=project
-
-title="Add Subfiles to FFS"
-
-contact="""
-[tech-kern](mailto:tech-kern@NetBSD.org)
-"""
-
-category="kernel"
-difficulty="medium"
-
-description="""
-Subfiles are important for supporting the NT file model and will enhance Samba
-support. They are also important for NFSv4 (called Named Attributes) and are
-already supported by Sun Microsystems, Network Appliance, and EMC.
-
-For a detailed project description see
-[this post to tech-kern](http://mail-index.NetBSD.org/tech-kern/2006/04/15/0012.html).
-"""
-]]

add a project entry for nfsv4
--- /dev/null	2014-03-30 15:32:01.000000000 +0000
+++ wikisrc/projects/project/nfsv4.mdwn	2014-03-30 15:37:43.000000000 +0000
@@ -0,0 +1,25 @@
+[[!template id=project
+
+title="Port or implement NFSv4"
+
+contact="""
+[tech-kern](mailto:tech-kern@NetBSD.org),
+[David Holland](mailto:dholland@NetBSD.org)
+"""
+
+category="filesystems"
+difficulty="hard"
+duration="6-12 months"
+
+description="""
+Port or implement NFSv4.
+
+As of this writing the FreeBSD NFS code, including NFSv4, has been
+imported into the tree but no work has yet been done on it. The
+intended plan is to port it and eventually replace the existing NFS
+code, which nobody is particularly attached to.
+
+It is unlikely that writing new NFSv4 code is a good idea, but
+circumstances might change.
+"""
+]]

minor edits
Index: wikisrc/projects/project/ptyfs_multiple_mounts.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ptyfs_multiple_mounts.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/ptyfs_multiple_mounts.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/ptyfs_multiple_mounts.mdwn	27 Feb 2014 06:37:04 -0000	1.3
@@ -15,15 +15,15 @@
 duration="3 months"
 
 description="""
-Chrooted enviroments that need ptys cannot use ptyfs at this time because only one instance of ptyfs is supported. The task is to enhance ptyfs so that it can be mounted multiple times. The problems that need to be solved are:
+Chrooted enviroments that need ptys cannot currently use ptyfs because only one instance of ptyfs at a time is supported. The task is to enhance ptyfs so that it can be mounted multiple times. The problems that need to be solved are:
 
 * The ptyfs code needs to be modified so that the correct path is returned depending on the mount point in the TIOCPTMGET ioctl. There was code there to do this, but it was removed because it was not working properly.
-* Since there can be only one instance of major/minor pty in the system, each mount point should only display the ptys that were created for that mountpoint and not others.
-* Since ptyfs replaces the handlers for the traditional BSD style ptys when it is mounted and puts them back once it is unmounted, this handler hijacking will not work with multiple mounts. Perhaps a solution is to do it only for the first mount?
+* Since there can be only one instance of each major/minor pty in the system, each mount point should only display the ptys that were created on that mount point and not others.
+* ptyfs replaces the handlers for the traditional BSD style ptys when it is mounted and puts them back once it is unmounted. This handler hijacking will not work with multiple mounts. Perhaps a solution is to do it only for the first mount?
 
 This project is implemented all in the kernel and has no documentation requirements.
 
-For extra credit you can investigate if providing continuous numbers (without gaps) is feasible without too much recoding, and implement it.
+For extra credit you can investigate if providing continuous numbers on each mount point (without gaps) is feasible without too much recoding, and implement it.
 """
 ]]
 

Rework text, no substantive change
Index: wikisrc/projects/project/defrag_ffs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/defrag_ffs.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/defrag_ffs.mdwn	27 Feb 2014 06:30:24 -0000	1.3
+++ wikisrc/projects/project/defrag_ffs.mdwn	27 Feb 2014 06:33:07 -0000	1.4
@@ -11,9 +11,12 @@
 
 description="""
 Heavily used file systems tend to spread the blocks all over the disk,
-especially if free space is scarce. Traditionally dump/restore have been used to
-recreate the file system, but this is not acceptable for current disk
-sizes. Since resize_ffs has to relocate blocks during shrinking anyway, it
-should be possible to extend it to full reordering and defragmentation.
+especially if free space is scarce. The traditional fix for this is to
+use dump, newfs, and restore to rebuild a volume; however, this is not
+acceptable for current disk sizes.
+
+The resize_ffs code already contains logic for relocating blocks, as
+it needs to be able to do that to shrink a volume; it is likely that
+it would serve nicely as a starting point for a defragmenting tool.
 """
 ]]

this is a filesystems project; also it is not "easy", make it "medium".
Index: wikisrc/projects/project/defrag_ffs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/defrag_ffs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/defrag_ffs.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/defrag_ffs.mdwn	27 Feb 2014 06:30:24 -0000	1.3
@@ -6,8 +6,8 @@
 [tech-kern](mailto:tech-kern@NetBSD.org)
 """
 
-category="kernel"
-difficulty="easy"
+category="filesystems"
+difficulty="medium"
 
 description="""
 Heavily used file systems tend to spread the blocks all over the disk,

copyedit, minor clarification
Index: wikisrc/projects/project/aprint.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/aprint.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/aprint.mdwn	6 Nov 2011 19:58:46 -0000	1.1
+++ wikisrc/projects/project/aprint.mdwn	27 Feb 2014 06:29:03 -0000	1.2
@@ -12,11 +12,11 @@
 
 description="""
 Most of the NetBSD kernel tree still uses printf(9) to send messages to the
-console, primarily during boot and autoconfiguration.  Each printf during
-autoconfiguration should be audited, and replaced with the appropriate aprint_*
-function, to make the boot verbose option work properly.
+console, primarily during boot and device configuration.  Each printf during
+device configuration should be audited, and replaced with the appropriate aprint_*
+function, to make the verbose boot option work properly.
 
-Additionally, printfs in drivers that report status, or errors during normal
+Additionally, printfs in drivers that report status (or errors) during normal
 kernel operation should be converted to use the log(9) function instead.
 """
 ]]

delete; pooka did this project years ago.
--- wikisrc/projects/project/usermode-ffs.mdwn	2014-03-30 15:37:43.000000000 +0000
+++ /dev/null	2014-03-30 15:32:01.000000000 +0000
@@ -1,22 +0,0 @@
-[[!template id=project
-
-title="File system testing in usermode"
-
-contact="""
-[tech-kern](mailto:tech-kern@NetBSD.org)
-"""
-
-category="filesystems"
-difficulty="medium"
-duration="2-3 months"
-
-description="""
-Develop a set of libraries that permit compiling and running file system code in
-usermode. The primary purpose for these libraries is to permit running unit
-tests on the file system code.
-
-Also develop a test interface and a number of test cases to use the libraries
-for testing file systems. The initial test cases should demonstrate the
-functionality of the test system.
-"""
-]]

Clarify that this is really talking about a new filesystem, not (juts)
cleanup of the ffs code.
Index: wikisrc/projects/project/simplify-ffs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/simplify-ffs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/simplify-ffs.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/simplify-ffs.mdwn	27 Feb 2014 06:25:35 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Simplify FFS"
+title="Simpler, extent-based FFS"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)
@@ -14,7 +14,12 @@
 Remove the residual geometry code and datastructures from FFS (keep some kind of
 allocation groups but without most of what cylinder groups now have) and replace
 blocks and fragments with extents, yielding a much simpler filesystem well
-suited for modern disks.  The result would be useful to many operating systems
-beyond just NetBSD, since UFS/FFS is used in so many different kernels.
+suited for modern disks.
+
+Note that this results in a different on-disk format and will need to be a different file system type.
+
+The result would be potentially useful to other operating systems beyond just
+NetBSD, since UFS/FFS is used in so many different kernels.
+
 """
 ]]

Add a project entry for porting Hammer.
--- /dev/null	2014-03-30 15:32:01.000000000 +0000
+++ wikisrc/projects/project/hammer.mdwn	2014-03-30 15:37:43.000000000 +0000
@@ -0,0 +1,20 @@
+[[!template id=project
+
+title="Port Hammer"
+
+contact="""
+[tech-kern](mailto:tech-kern@NetBSD.org)
+"""
+
+category="filesystems"
+difficulty="hard"
+duration="3-6 months"
+
+description="""
+Port Dragonfly's Hammer file system to NetBSD.
+
+Note that because Dragonfly has made substantial changes (different
+from NetBSD's substantial changes) to the 4.4BSD vfs layer this port
+may be more difficult than it looks up front.
+"""
+]]

Improve title; clarify.
Index: wikisrc/projects/project/xfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/xfs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/xfs.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/xfs.mdwn	27 Feb 2014 06:18:44 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="BSD licensed XFS"
+title="Implement or port XFS"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)
@@ -12,9 +12,12 @@
 
 description="""
 
-Implement a BSD licensed XFS.  A GPL licensed implementation of XFS is available
-at <http://oss.sgi.com/projects/xfs/>.  It might be worthwhile to do a port of
-this filesystem and allow it to run as a LKM.  See also
-[FreeBSD's port](http://people.freebsd.org/~rodrigc/xfs/).
+Implement a BSD licensed XFS.  A GPL licensed implementation of XFS is
+available at <http://oss.sgi.com/projects/xfs/>.
+
+Alternatively, or additionally, it might be worthwhile to do a port of
+the GPL code and allow it to run as a kernel module.
+
+See also [FreeBSD's port](http://people.freebsd.org/~rodrigc/xfs/).
 """
 ]]

Improve title, clarify text.
Index: wikisrc/projects/project/jfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/jfs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/jfs.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/jfs.mdwn	27 Feb 2014 06:17:56 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="BSD licensed JFS"
+title="Implement or port JFS"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)
@@ -12,7 +12,9 @@
 
 description="""
 Implement a BSD licensed JFS.  A GPL licensed implementation of JFS is available
-at <http://jfs.sourceforge.net/>.  It might be worthwhile to do a port of this
-filesystem and allow it to run as a LKM.
+at <http://jfs.sourceforge.net/>.
+
+Alternatively, or additionally, it might be worthwhile to do a port of the
+GPL code and allow it to run as a kernel module.
 """
 ]]

difficulty -> medium.
There's no way this is *harder* than some of the other medium fs
projects, like rewriting procfs.
Members: 
	projects/project/dotdot.mdwn:1.4->1.5 

Index: wikisrc/projects/project/dotdot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/dotdot.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/dotdot.mdwn	27 Feb 2014 06:11:05 -0000	1.4
+++ wikisrc/projects/project/dotdot.mdwn	27 Feb 2014 06:12:05 -0000	1.5
@@ -7,7 +7,7 @@
 """
 
 category="filesystems"
-difficulty="hard"
+difficulty="medium"
 
 description="""
 In a file system with symlinks, the file system can be seen as a graph

Rewrite. Make it clear that the notion that there's a problem to be
"fixed" here at all is a minority opinion. Note that as a result, the
feature if implemented needs to be switchable on/off on a per-process
basis.
Index: wikisrc/projects/project/dotdot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/dotdot.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/dotdot.mdwn	7 Nov 2011 14:50:24 -0000	1.3
+++ wikisrc/projects/project/dotdot.mdwn	27 Feb 2014 06:11:05 -0000	1.4
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Fix .. semantics, once and for all"
+title="Semantics of .."
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)
@@ -10,12 +10,24 @@
 difficulty="hard"
 
 description="""
-In a file system with symlinks, the file system becomes a graph rather than a
-tree. The meaning of .. and the current working directory becomes somewhat
-ambiguous in such an environment.
-
-Rob Pike implemented a neat way of fixing this for Plan 9. It is described in
-<http://cm.bell-labs.com/sys/doc/lexnames.html>.  The project is simply to
-re-implement this for NetBSD.
+In a file system with symlinks, the file system can be seen as a graph
+rather than a tree. The meaning of .. potentially becomes complicated
+in this environment.
+
+There is a fairly substantial group of people, some of them big famous
+names, who think that the usual behavior (where crossing a symlink is
+different from entering a subdirectory) is a bug, and have made
+various efforts from time to time to "fix" it. One such fix can be seen
+in the -L and -P options to ksh's pwd.
+
+Rob Pike implemented a neat hack for this in Plan 9. It is described
+in <http://cm.bell-labs.com/sys/doc/lexnames.html>. This project is to
+implement that logic for NetBSD.
+
+Note however that there's another fairly substantial group of people,
+some of them also big famous names, who think that all of this is a
+load of dingo's kidneys, the existing behavior is correct, and
+changing it would be a bug. So it needs to be possible to switch the
+implementation on and off as per-process state.
 """
 ]]

Edit the text; rework parts of it. There are some issues that the
original author didn't think of, such as integrating with sysctl.
Also suggest an implementation that uses pointers to kernel data
rather than callbacks; it takes a bit more work but it's much tidier
and much less invasive. I have BSD-licensed prior art, too, if anyone
wants to look at it; unfortunately it's not really suitable for NetBSD
without a rewrite.
Make myself a contact. (Not a mentor, as regardless of this year's
issues in general I don't have time to GSOC mentor.)
Make myself a contact. (Not a mentor, as regardless of this year's
issues in general I don't have time to GSOC mentor.)

Members: 
	projects/project/kernfs-rewrite.mdwn:1.1->1.2 

Index: wikisrc/projects/project/kernfs-rewrite.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/kernfs-rewrite.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/kernfs-rewrite.mdwn	6 Nov 2011 19:58:46 -0000	1.1
+++ wikisrc/projects/project/kernfs-rewrite.mdwn	27 Feb 2014 05:59:11 -0000	1.2
@@ -3,7 +3,8 @@
 title="Rewrite kernfs and procfs"
 
 contact="""
-[tech-kern](mailto:tech-kern@NetBSD.org)
+[tech-kern](mailto:tech-kern@NetBSD.org),
+[David Holland](mailto:dholland@NetBSD.org)
 """
 
 mentors="""
@@ -15,43 +16,74 @@
 duration="2-3 months"
 
 description="""
-kernfs is a virtual file system that provides the user several information about
-the current system and, in some cases, allows him to configure some aspects of
-the kernel through those virtual files.  procfs is another virtual file system
-that provides information about the currently running processes.
-
-These two file systems are written in a non-extensible way.  For example, kernfs
-is built on a hardcoded table that always exposes the same set of files; there
-is no way for other system areas to add or remove entries from the kernfs
-contents.  procfs has similar issues as someone might think of a subsystem that
-could benefit from attaching information of its own to each running process.
-The current code is not modular, not well-designed and, as time has shown, there
-probably remain serious security bugs in them.
-
-Linux exposes some APIs that abstract procfs' contents and allow external code
-to manage its entries by adding or removing files and/ or directories.  This is
-a very interesting feature when writing loadable kernel modules as they can use
-this virtual file system to provide a way of interaction with the end user.
-
-NetBSD could benefit of similar APIs for both kernfs and procfs.  This project
-would consist on adding these APIs, which most likely requires (or suggests) a
-full rewrite of these file systems.  The developer should keep in mind the
-distinction between the two to avoid having a procfs similar to the one in
-Linux, which mixes system configuration and process management.
-
-In order to keep the new implementations simple, the developer should
-investigate the possibility of using tmpfs as a backend for kernfs and procfs.
-With some changes, one could create a kernel "library" that allowed the creation
-of virtual file systems with few code.  For example, it's unlikely that the
-directory management routines will change among the three file systems, so the
-code from tmpfs should be reused.  Similarly other features should be reusable,
-making procfs's and kernfs's code a lot simpler than currently is.
+kernfs is a virtual file system that reports information about the
+running system, and in some cases allows adjusting this information.
+procfs is a virtual file system that provides information about
+currently running processes. Both of these file systems work by
+exposing virtual files containing textual data.
+
+The current implementations of these file systems are redundant and
+both are non-extensible. For example, kernfs is a hardcoded table that
+always exposes the same set of files; there is no way to add or remove
+entries on the fly, and even adding new static entries is a nuisance.
+procfs is similarly limited; there is no way to add additional
+per-process data on the fly. Furthermore, the current code is not
+modular, not well designed, and has been a source of security bugs in
+the past.
+
+We would like to have a new implementation for both of these file
+systems that rectifies these problems and others, as outlined below:
+
+* kernfs and procfs should share most of their code, and in particular
+they should share all the code for managing lists of virtual
+files. They should remain separate entities, however, at least from
+the user perspective: community consensus is that mixing system and
+per-process data, as Linux always has, is ugly.
+
+* It should be possible to add and remove entries on the fly, e.g. as
+modules are loaded and unloaded.
+
+* Because userlevel programs can become dependent on the format of the
+virtual files (Linux has historically had compatibility problems
+because of this) they should if possible not have complex formats at
+all, and if they do the format should be clearly specifiable in some
+way that isn't procedural code. (This makes it easier to reason about,
+and harder for it to get changed by accident.)
+
+* There is an additional interface in the kernel for retrieving and
+adjusting arbitrary kernel information: sysctl. Currently the sysctl
+code is a third completely separate mechanism, on many points
+redundant with kernfs and/or procfs. It is somewhat less primitive,
+but the current implementation is cumbersome and not especially liked.
+Integrating kernfs and procfs with sysctl (perhaps somewhat like the
+Linux sysfs) is not automatically the right design choice, but it is
+likely to be a good idea. At a minimum we would like to be able to
+have one way to handle reportable/adjustable data within the kernel,
+so that kernfs, procfs, and/or sysctl can be attached to any
+particular data element as desired.
+
+* While most of the implementations of things like procfs and sysctl
+found in the wild (including the ones we currently have) work by
+attaching callbacks, and then writing code all over the kernel to
+implement the callback API, it is possible to design instead to attach
+data, that is, pointers to variables within the kernel, so that the
+kernfs/procfs or sysctl code itself takes responsibility for fetching
+that data. Please consider such a design strongly and pursue it if
+feasible, as it is much tidier. (Note that attaching data also in
+general requires specifying a locking model and, for writeable data,
+possibly a condition variable to signal on when the value changes.)
+
+It is possible that using tmpfs as a backend for kernfs and procfs, or
+sharing some code with tmpfs, would simplify the implementation. It
+also might not. Consider this possibility, and assess the tradeoffs;
+do not treat it as a requirement.
+
+Alternatively, investigate FreeBSD's pseudofs and see if this could be
+a useful platform for this project and base for all the file systems
+mentioned above.
 
-Alternatively, investigate FreeBSD's pseudofs and see if this could be a useful
-for this project and base for all the file systems mentioned above.
-
-When working in this project, it is very important to write a complete
+When working on this project, it is very important to write a complete
 regression test suite for procfs and kernfs beforehand to ensure that the
-rewrites do not add incompatibilities.
+rewrites do not create incompatibilities.
 """
 ]]

pandoc -f html -t markdown http://www.netbsd.org/gallery/events.html
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/events.mdwn	26 May 2013 17:18:39 -0000	1.1
+++ wikisrc/events.mdwn	27 Feb 2014 05:23:24 -0000	1.2
@@ -1,3 +1,5047 @@
 # This page is currently a placeholder for an upcoming listing of events
 
 For questions, ask [mbalmer](mailto:mbalmer@netbsd.org), as he's one reserving this space...
+
+[Skip to main content.](#mainContent)
+
+[![[NetBSD Logo]](../images/NetBSD-smaller.png)](../)
+
+[The NetBSD Project](../)
+
+[“Of course it runs NetBSD”](../)
+
+Google custom search
+
+Navigation:
+
+-   [Home](../)
+-   [News & Media](../)
+    -   [Recent changes](../changes/)
+    -   [NetBSD blog](http://blog.NetBSD.org/)
+    -   [Events](../gallery/events.html)
+    -   [Feeds](../changes/rss.html)
+
+-   [About](../about/)
+    -   [NetBSD](../about/)
+    -   [The NetBSD Foundation](../foundation/)
+    -   [Advocacy](../gallery/)
+
+-   [Documentation](../docs/)
+    -   [FAQ & HOWTOs](../docs/misc/index.html)
+    -   [The Guide](../docs/guide/en/)
+    -   [Manual pages](http://man.NetBSD.org/)
+    -   [Wiki](http://wiki.NetBSD.org/)
+
+-   [Support](../support/)
+    -   [Problem report guide](../support/send-pr.html)
+    -   [Report a bug](../cgi-bin/sendpr.cgi?gndb=netbsd)
+    -   [Query bug database](../support/query-pr.html)
+    -   [Security](../support/security/)
+
+-   [Community](../community/)
+    -   [Blogs](http://onetbsd.org/)
+    -   [Mailing lists](../mailinglists/)
+    -   [List archives](http://mail-index.NetBSD.org/)
+
+-   [Developers](../developers/)
+    -   [Browse source](http://cvsweb.NetBSD.org/)
+    -   [Cross-reference](http://nxr.NetBSD.org/)
+    -   [Release engineering](http://releng.NetBSD.org/)
+    -   [Projects list](http://wiki.NetBSD.org/projects/)
+
+-   [Ports](../ports/)
+    -   [History](../ports/history.html)
+    -   [Emulators](../ports/emulators.html)
+
+-   [Packages](http://www.pkgsrc.org/)
+    -   [Browse packages](http://www.pkgsrc.se/)
+    -   [Release
+        engineering](http://releng.NetBSD.org/index-pkgsrc.html)
+
+NetBSD Events
+=============
+
+This is an incomplete list of NetBSD-related events. If you know about
+some public event that fits and would like it to be listed here,
+[contact us.](http://www.NetBSD.org/cgi-bin/feedback.cgi)
+
+For a list of NetBSD-related presentations, please check out our
+[presentation pages](/gallery/presentations/).
+
+### Future Events
+
+-   [Feb 2014 - Open Source Conference 2014
+    Tokyo/Spring](#opensourceconf2014-tokyospring)
+-   [Mar 2014 - AsiaBSDCon 2014](#asiabsdcon-tokyo-2014)
+-   [Mar 2014 - Open Source Conference 2014
+    Hamanako](#opensourceconf2014-hamamatsu)
+-   [Jun 2014 - Open Source Conference 2014
+    Hokkaido](#opensourceconf2014-DO)
+-   [Jul 2014 - Open Source Conference 2014
+    Nagoya](#opensourceconf2014-Nagoya)
+-   [Nov 2014 - Kansai OpenSource 2014](#kansai-os-jp-2014)
+
+### Past Events
+
+-   [Feb 2014 - NYC\*BSD Con 2014](#NYCBSDCon2014)
+-   [Nov 2013 - Linux User Group of Mauritius - LinuxFest
+    2013](#LinuxFest2013Mauritius)
+-   [Nov 2013 - Open Source Conference 2013
+    Oita](#opensourceconf2013-oita)
+-   [Nov 2013 - Open Source Conference 2013
+    Fukuoka](#opensourceconf2013-fukuoka)
+-   [Nov 2013 - Kansai OpenSource 2013](#kansai-os-jp-2013)
+-   [Oct 2013 - Open Source Conference 2013
+    Tokyo/Fall](#opensourceconf2013-tokyofall)
+-   [Oct 2013 - Open Source Conference 2013
+    Hiroshima](#opensourceconf2013-Hiroshima)
+-   [Sep 2013 - Open Source Conference 2013
+    Hokkaido](#opensourceconf2013-DO)
+-   [Aug 2013 - FrOSCon 2013](#froscon2013)
+-   [Aug 2013 - Open Source Conference 2013
+    Shimane](#opensourceconf2013-Shimane)
+-   [Aug 2013 - Open Source Conference 2013
+    Kansai@Kyoto](#opensourceconf2013-Kansai)
+-   [Jul 2013 - Japan NetBSD Users' Group meeting & NetBSD
+    BOF](#jp-users-2013)
+-   [Jul 2013 - Open Source Conference 2013
+    Okinawa](#opensourceconf2013-Okinawa)
+-   [Jun 2013 - Open Source Conference 2013
+    Nagoya](#opensourceconf2013-Nagoya)
+-   [May 2013 - Linuxtag Berlin](#linuxtagB2013)
+-   [May 2013 - BSDCan 2013, Ottawa, Canada](#bsdcan2013)
+-   [Apr 2013 - Central European BSD-Day 2013, Naples,
+    Italy](#bsdday_2013)
+-   [Mar 2013 - pkgsrcCon 2013, Berlin, Germany](#pkgsrcCon-2013)
+-   [Mar 2013 - Chemnitz Linux Days 2013, Chemnitz,
+    Germany](#chemnitzer-linuxtage-2013)
+-   [Mar 2013 - AsiaBSDCon 2013](#asiabsdcon-tokyo-2013)
+-   [Mar 2013 - Open Source Conference 2013
+    Tokushima](#opensourceconf2013-tokushima)
+-   [Feb 2013 - Open Source Conference 2013
+    Tokyo/Spring](#opensourceconf2013-tokyospring)
+-   [Feb 2013 - Open Source Conference 2013
+    Hamamatsu](#opensourceconf2013-hamamatsu)
+-   [Feb 2013 - FOSDEM 2013, Brussels, Belgium](#fosdem2013)
+-   [Dec 2012 - Open Source Conference 2012
+    Fukuoka](#opensourceconf2012-fukuoka)
+-   [Nov 2012 - Open Source Conference 2012
+    Aizu](#opensourceconf2012-aizu)
+-   [Oct 2012 - Open Source Conference 2012
+    Oita/Fall](#opensourceconf2012-oita-fall)
+-   [Oct 2012 - Open Source Conference 2012
+    Hiroshima](#opensourceconf2012-Hiroshima)
+-   [Oct 2012 - EuroBSDCon 2012, Warsaw, Poland](#eurobsdcon2012)
+-   [Sep 2012 - Open Source Conference 2012
+    Okinawa](#opensourceconf2012-Okinawa)
+-   [Sep 2012 - Open Source Conference 2012
+    Tokyo/Spring](#opensourceconf2012-tokyofall)
+-   [Nov 2012 - Kansai OpenSource 2012](#kansai-os-jp-2012)
+-   [Sep 2012 - Open Source Conference 2012
+    Shimane](#opensourceconf2012-Shimane)
+-   [Aug 2012 - XenSummit North America 2012](#xensummit2012)
+-   [Aug 2012 - FrOSCon 2012](#froscon2012)
+-   [Aug 2012 - Open Source Conference 2012
+    Kansai@Kyoto](#opensourceconf2012-Kansai)
+-   [Jul 2012 - Open Source Conference 2012
+    Sendai](#opensourceconf2012-sendai)
+-   [Jul 2012 - Japan NetBSD Users' Group meeting & NetBSD
+    BOF](#jp-users-2012)
+-   [Jun 2012 - 17th NetBSD Hackathon](#17th-hackathon)
+-   [Jun 2012 - Open Source Conference 2012
+    Hokkaido](#opensourceconf2012-DO)
+-   [May 2012 - Linuxtag Berlin](#linuxtagB2012)
+-   [May 2012 - BSDCan 2012](#bsdcan2012)
+-   [May 2012 - Open Source Conference 2012
+    Nagoya](#opensourceconf2012-Nagoya)
+-   [May 2012 - Central European BSD-Day 2012 Vienna](#bsdday_2012)
+-   [Apr 2012 - Open Source Conference 2012
+    Iwate](#opensourceconf2012-iwate)
+-   [Mar 2012 - AsiaBSDCon 2012](#asiabsdcon-tokyo-2012)
+-   [Mar 2012 - Open Source Conference 2012
+    Ehime](#opensourceconf2012-ehime)
+-   [Mar 2012 - Chemnitzer Linux-Tage 2012](#chemnitzer-linuxtage-2012)
+-   [Mar 2012 - Open Source Conference 2012
+    Tokyo/Spring](#opensourceconf2012-tokyospring)
+-   [Feb 2012 - Open Source Conference 2012
+    Oita](#opensourceconf2012-oita)
+-   [Feb 2012 - FOSDEM 2012](#fosdem2012)
+-   [Dec 2011 - Open Source Conference 2011
+    Fukuoka](#opensourceconf2011-fukuoka)
+-   [Nov 2011 - Open Source Conference 2011
+    Tokyo/Fall](#opensourceconf2011-tokyofall)
+-   [Nov 2011 - Open Source Conference 2011
+    Shimane](#opensourceconf2011-Shimane)
+-   [Nov 2011 - Kansai OpenSource 2011](#kansai-os-jp-2011)
+-   [Nov 2011 - bsd\_day(2011)](#bsdday2011)
+-   [Nov 2011 - BSDday Argentina 2011](#BSDdayArgentina2011)
+-   [Oct 2011 - EuroBSDCon 2011](#eurobsdcon2011)
+-   [Oct 2011 - Open Source Conference 2011
+    Hiroshima](#opensourceconf2011-Hiroshima)
+-   [Sep 2011 - Open Source Conference 2011
+    Okinawa](#opensourceconf2011-Okinawa)
+-   [Sep 2011 - Open Source Small Conference 2011
+    Aizu](#opensourcesmallconf2011-Aizu)
+-   [Aug 2011 - Open Source Conference 2011
+    Nagoya](#opensourceconf2011-Nagoya)
+-   [Aug 2011 - 15th NetBSD Hackathon](#15th-hackathon)
+-   [Jul 2011 - Open Source Conference 2011
+    Kansai@Kyoto](#opensourceconf2011-Kansai)
+-   [Jul 2011 - Japan NetBSD Users' Group meeting & NetBSD
+    BOF](#jp-users-2011)

(Diff truncated)
Add "Apple" to the title so it's clearer up front what this is about.
XXX: it looks like the link in here needs updating.
XXX: Also, is this project still current? Does anything really still
XXX: care about MacOS 9 type and creator fields?
XXX: Also, is this project still current? Does anything really still
XXX: care about MacOS 9 type and creator fields?

Members: 
	projects/project/iso9660-extensions.mdwn:1.2->1.3 

Index: wikisrc/projects/project/iso9660-extensions.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/iso9660-extensions.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/iso9660-extensions.mdwn	6 Nov 2011 21:08:23 -0000	1.2
+++ wikisrc/projects/project/iso9660-extensions.mdwn	27 Feb 2014 05:21:12 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="ISO9660 extensions"
+title="Apple ISO9660 extensions"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)

pandoc -f html -t markdown http://www.netbsd.org/gallery/events.html
--- /dev/null	2014-03-30 15:32:01.000000000 +0000
+++ wikisrc/users/eventtomarkdowntest.mdwn	2014-03-30 15:37:44.000000000 +0000
@@ -0,0 +1,5043 @@
+[Skip to main content.](#mainContent)
+
+[![[NetBSD Logo]](../images/NetBSD-smaller.png)](../)
+
+[The NetBSD Project](../)
+
+[“Of course it runs NetBSD”](../)
+
+Google custom search
+
+Navigation:
+
+-   [Home](../)
+-   [News & Media](../)
+    -   [Recent changes](../changes/)
+    -   [NetBSD blog](http://blog.NetBSD.org/)
+    -   [Events](../gallery/events.html)
+    -   [Feeds](../changes/rss.html)
+
+-   [About](../about/)
+    -   [NetBSD](../about/)
+    -   [The NetBSD Foundation](../foundation/)
+    -   [Advocacy](../gallery/)
+
+-   [Documentation](../docs/)
+    -   [FAQ & HOWTOs](../docs/misc/index.html)
+    -   [The Guide](../docs/guide/en/)
+    -   [Manual pages](http://man.NetBSD.org/)
+    -   [Wiki](http://wiki.NetBSD.org/)
+
+-   [Support](../support/)
+    -   [Problem report guide](../support/send-pr.html)
+    -   [Report a bug](../cgi-bin/sendpr.cgi?gndb=netbsd)
+    -   [Query bug database](../support/query-pr.html)
+    -   [Security](../support/security/)
+
+-   [Community](../community/)
+    -   [Blogs](http://onetbsd.org/)
+    -   [Mailing lists](../mailinglists/)
+    -   [List archives](http://mail-index.NetBSD.org/)
+
+-   [Developers](../developers/)
+    -   [Browse source](http://cvsweb.NetBSD.org/)
+    -   [Cross-reference](http://nxr.NetBSD.org/)
+    -   [Release engineering](http://releng.NetBSD.org/)
+    -   [Projects list](http://wiki.NetBSD.org/projects/)
+
+-   [Ports](../ports/)
+    -   [History](../ports/history.html)
+    -   [Emulators](../ports/emulators.html)
+
+-   [Packages](http://www.pkgsrc.org/)
+    -   [Browse packages](http://www.pkgsrc.se/)
+    -   [Release
+        engineering](http://releng.NetBSD.org/index-pkgsrc.html)
+
+NetBSD Events
+=============
+
+This is an incomplete list of NetBSD-related events. If you know about
+some public event that fits and would like it to be listed here,
+[contact us.](http://www.NetBSD.org/cgi-bin/feedback.cgi)
+
+For a list of NetBSD-related presentations, please check out our
+[presentation pages](/gallery/presentations/).
+
+### Future Events
+
+-   [Feb 2014 - Open Source Conference 2014
+    Tokyo/Spring](#opensourceconf2014-tokyospring)
+-   [Mar 2014 - AsiaBSDCon 2014](#asiabsdcon-tokyo-2014)
+-   [Mar 2014 - Open Source Conference 2014
+    Hamanako](#opensourceconf2014-hamamatsu)
+-   [Jun 2014 - Open Source Conference 2014
+    Hokkaido](#opensourceconf2014-DO)
+-   [Jul 2014 - Open Source Conference 2014
+    Nagoya](#opensourceconf2014-Nagoya)
+-   [Nov 2014 - Kansai OpenSource 2014](#kansai-os-jp-2014)
+
+### Past Events
+
+-   [Feb 2014 - NYC\*BSD Con 2014](#NYCBSDCon2014)
+-   [Nov 2013 - Linux User Group of Mauritius - LinuxFest
+    2013](#LinuxFest2013Mauritius)
+-   [Nov 2013 - Open Source Conference 2013
+    Oita](#opensourceconf2013-oita)
+-   [Nov 2013 - Open Source Conference 2013
+    Fukuoka](#opensourceconf2013-fukuoka)
+-   [Nov 2013 - Kansai OpenSource 2013](#kansai-os-jp-2013)
+-   [Oct 2013 - Open Source Conference 2013
+    Tokyo/Fall](#opensourceconf2013-tokyofall)
+-   [Oct 2013 - Open Source Conference 2013
+    Hiroshima](#opensourceconf2013-Hiroshima)
+-   [Sep 2013 - Open Source Conference 2013
+    Hokkaido](#opensourceconf2013-DO)
+-   [Aug 2013 - FrOSCon 2013](#froscon2013)
+-   [Aug 2013 - Open Source Conference 2013
+    Shimane](#opensourceconf2013-Shimane)
+-   [Aug 2013 - Open Source Conference 2013
+    Kansai@Kyoto](#opensourceconf2013-Kansai)
+-   [Jul 2013 - Japan NetBSD Users' Group meeting & NetBSD
+    BOF](#jp-users-2013)
+-   [Jul 2013 - Open Source Conference 2013
+    Okinawa](#opensourceconf2013-Okinawa)
+-   [Jun 2013 - Open Source Conference 2013
+    Nagoya](#opensourceconf2013-Nagoya)
+-   [May 2013 - Linuxtag Berlin](#linuxtagB2013)
+-   [May 2013 - BSDCan 2013, Ottawa, Canada](#bsdcan2013)
+-   [Apr 2013 - Central European BSD-Day 2013, Naples,
+    Italy](#bsdday_2013)
+-   [Mar 2013 - pkgsrcCon 2013, Berlin, Germany](#pkgsrcCon-2013)
+-   [Mar 2013 - Chemnitz Linux Days 2013, Chemnitz,
+    Germany](#chemnitzer-linuxtage-2013)
+-   [Mar 2013 - AsiaBSDCon 2013](#asiabsdcon-tokyo-2013)
+-   [Mar 2013 - Open Source Conference 2013
+    Tokushima](#opensourceconf2013-tokushima)
+-   [Feb 2013 - Open Source Conference 2013
+    Tokyo/Spring](#opensourceconf2013-tokyospring)
+-   [Feb 2013 - Open Source Conference 2013
+    Hamamatsu](#opensourceconf2013-hamamatsu)
+-   [Feb 2013 - FOSDEM 2013, Brussels, Belgium](#fosdem2013)
+-   [Dec 2012 - Open Source Conference 2012
+    Fukuoka](#opensourceconf2012-fukuoka)
+-   [Nov 2012 - Open Source Conference 2012
+    Aizu](#opensourceconf2012-aizu)
+-   [Oct 2012 - Open Source Conference 2012
+    Oita/Fall](#opensourceconf2012-oita-fall)
+-   [Oct 2012 - Open Source Conference 2012
+    Hiroshima](#opensourceconf2012-Hiroshima)
+-   [Oct 2012 - EuroBSDCon 2012, Warsaw, Poland](#eurobsdcon2012)
+-   [Sep 2012 - Open Source Conference 2012
+    Okinawa](#opensourceconf2012-Okinawa)
+-   [Sep 2012 - Open Source Conference 2012
+    Tokyo/Spring](#opensourceconf2012-tokyofall)
+-   [Nov 2012 - Kansai OpenSource 2012](#kansai-os-jp-2012)
+-   [Sep 2012 - Open Source Conference 2012
+    Shimane](#opensourceconf2012-Shimane)
+-   [Aug 2012 - XenSummit North America 2012](#xensummit2012)
+-   [Aug 2012 - FrOSCon 2012](#froscon2012)
+-   [Aug 2012 - Open Source Conference 2012
+    Kansai@Kyoto](#opensourceconf2012-Kansai)
+-   [Jul 2012 - Open Source Conference 2012
+    Sendai](#opensourceconf2012-sendai)
+-   [Jul 2012 - Japan NetBSD Users' Group meeting & NetBSD
+    BOF](#jp-users-2012)
+-   [Jun 2012 - 17th NetBSD Hackathon](#17th-hackathon)
+-   [Jun 2012 - Open Source Conference 2012
+    Hokkaido](#opensourceconf2012-DO)
+-   [May 2012 - Linuxtag Berlin](#linuxtagB2012)
+-   [May 2012 - BSDCan 2012](#bsdcan2012)
+-   [May 2012 - Open Source Conference 2012
+    Nagoya](#opensourceconf2012-Nagoya)
+-   [May 2012 - Central European BSD-Day 2012 Vienna](#bsdday_2012)
+-   [Apr 2012 - Open Source Conference 2012
+    Iwate](#opensourceconf2012-iwate)
+-   [Mar 2012 - AsiaBSDCon 2012](#asiabsdcon-tokyo-2012)
+-   [Mar 2012 - Open Source Conference 2012
+    Ehime](#opensourceconf2012-ehime)
+-   [Mar 2012 - Chemnitzer Linux-Tage 2012](#chemnitzer-linuxtage-2012)
+-   [Mar 2012 - Open Source Conference 2012
+    Tokyo/Spring](#opensourceconf2012-tokyospring)
+-   [Feb 2012 - Open Source Conference 2012
+    Oita](#opensourceconf2012-oita)
+-   [Feb 2012 - FOSDEM 2012](#fosdem2012)
+-   [Dec 2011 - Open Source Conference 2011
+    Fukuoka](#opensourceconf2011-fukuoka)
+-   [Nov 2011 - Open Source Conference 2011
+    Tokyo/Fall](#opensourceconf2011-tokyofall)
+-   [Nov 2011 - Open Source Conference 2011
+    Shimane](#opensourceconf2011-Shimane)
+-   [Nov 2011 - Kansai OpenSource 2011](#kansai-os-jp-2011)
+-   [Nov 2011 - bsd\_day(2011)](#bsdday2011)
+-   [Nov 2011 - BSDday Argentina 2011](#BSDdayArgentina2011)
+-   [Oct 2011 - EuroBSDCon 2011](#eurobsdcon2011)
+-   [Oct 2011 - Open Source Conference 2011
+    Hiroshima](#opensourceconf2011-Hiroshima)
+-   [Sep 2011 - Open Source Conference 2011
+    Okinawa](#opensourceconf2011-Okinawa)
+-   [Sep 2011 - Open Source Small Conference 2011
+    Aizu](#opensourcesmallconf2011-Aizu)
+-   [Aug 2011 - Open Source Conference 2011
+    Nagoya](#opensourceconf2011-Nagoya)
+-   [Aug 2011 - 15th NetBSD Hackathon](#15th-hackathon)
+-   [Jul 2011 - Open Source Conference 2011
+    Kansai@Kyoto](#opensourceconf2011-Kansai)
+-   [Jul 2011 - Japan NetBSD Users' Group meeting & NetBSD
+    BOF](#jp-users-2011)
+-   [Jun 2011 - Open Source Conference 2011
+    Hokkaido](#opensourceconf2011-DO)
+-   [May 2011 - Open Source Conference 2011
+    Sendai](#opensourceconf2011-sendai)
+-   [May 2011 - BSDCan 2011](#bsdcan2011)
+-   [Apr 2011 - Open Source Conference 2011
+    Kansai@Kobe](#opensourceconf2011-kobe)
+-   [Mar 2011 - AsiaBSDCon 2011](#asiabsdcon-tokyo-2011)
+-   [Mar 2011 - Open Source Conference 2011
+    Oita](#opensourceconf2011-oita)

(Diff truncated)
event.xml to markdown via pandoc
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/users/jun.mdwn	5 May 2013 03:12:46 -0000	1.13
+++ wikisrc/users/jun.mdwn	27 Feb 2014 05:18:59 -0000	1.14
@@ -13,6 +13,7 @@
 -  [[http://www.facebook.com/NetBSD.jp]]
 
 ## Tips
+- [[eventtomarkdowntest]]
 - [[KOBO]]
 - [[qemu and sparc]]
 - [[wlan]]

Note that it would also be useful to audit the ext2 code for MPSAFE.
Index: wikisrc/projects/project/ext3fs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ext3fs.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/ext3fs.mdwn	27 Feb 2014 05:11:38 -0000	1.3
+++ wikisrc/projects/project/ext3fs.mdwn	27 Feb 2014 05:15:23 -0000	1.4
@@ -21,5 +21,7 @@
 The ext3 support should be implemented by extending the existing ext2 support (which is in src/sys/ufs/ext2fs), not by rewriting the whole thing over from scratch. It is possible that some of the ostensibly filesystem-independent code that was added along with the ffs WAPBL journaling extensions might be also useable as part of an ext3 implementation; but it also might not be.
 
 The full requirements for this project include complete support for ext3 in both the kernel and the userland tools. It is possible that a reduced version of this project with a clearly defined subset of these requirements could still be a viable GSOC project; if this appeals to you please coordinate with a prospective mentor.
+
+An additional useful add-on goal would be to audit the locking in the existing ext2 code; the ext2 code is not tagged MPSAFE, meaning it uses a biglock on multiprocessor machines, but it is likely that either it is in fact already safe and just needs to be tagged, or can be easily fixed. (Note that while this is not itself directly related to implementing ext3, auditing the existing ext2 code is a good way to become familiar with it.)
 """
 ]]

Increase duration and bump to "hard". Prior negative experience shows
that this project is not a trivial undertaking.
Index: wikisrc/projects/project/ext3fs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ext3fs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/ext3fs.mdwn	27 Feb 2014 05:10:58 -0000	1.2
+++ wikisrc/projects/project/ext3fs.mdwn	27 Feb 2014 05:11:38 -0000	1.3
@@ -7,8 +7,8 @@
 """
 
 category="filesystems"
-difficulty="medium"
-duration="1-2 months"
+difficulty="hard"
+duration="2-3 months"
 
 description="""
 The ext2 file system is the lowest common denominator Unix-like file system in the Linux world, as ffs is in the BSD world. NetBSD has had kernel support for ext2 for quite some time.

Rework text. The new text isn't really any different from the old text,
it's just a bit more specific and I hope clearer.
Index: wikisrc/projects/project/ext3fs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ext3fs.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/ext3fs.mdwn	6 Nov 2011 19:58:46 -0000	1.1
+++ wikisrc/projects/project/ext3fs.mdwn	27 Feb 2014 05:10:58 -0000	1.2
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Implement Ext3 file system support"
+title="Implement ext3 file system support"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)
@@ -11,22 +11,15 @@
 duration="1-2 months"
 
 description="""
-The Ext2 file system is the de-facto standard, Unix-like file system used on
-Linux installations.  Ext2 does not have journaling capabilities, so Ext3 was
-built on top of it to add them without breaking compatibility with Ext2.  Ext3
-is now a stable journaled file system used on lots of Linux installations.
-
-NetBSD currently fully supports the Ext2 file system at the kernel level.
-Unfortunately there is no support for the new features included in Ext3,
-although Ext3 file systems can be mounted provided that their journal is clean.
-It would be very nice if NetBSD had Ext3 file system support because the system
-could immediately gain a journaled file system as well as compatibility with
-Linux (imagine having both systems installed on a single partition!).
-
-Therefore, the aim of this project is to add Ext3 support to the NetBSD kernel
-accompanied by any userland code required to support it.  This shouldn't be too
-difficult because, as we already mentioned, Ext2 is implemented in the NetBSD
-kernel (see src/sys/ufs/ext2fs/) and Ext3 is an extension of it.  Also, WAPBL
-recently added journalling to FFS; maybe parts of the code could be reused.
+The ext2 file system is the lowest common denominator Unix-like file system in the Linux world, as ffs is in the BSD world. NetBSD has had kernel support for ext2 for quite some time.
+
+However, the Linux world has moved on, with ext3 and now to some extent also ext4 superseding ext2 as the baseline. NetBSD has no support for ext3; the goal of this project is to implement that support.
+
+Since ext3 is a backward-compatible extension that adds journaling to ext2, NetBSD can mount clean ext3 volumes as ext2 volumes. However, NetBSD cannot mount ext3 volumes with journaling and it cannot handle recovery for crashed volumes.
+As ext2 by itself provides no crash recovery guarantees whatsoever, this journaling support is highly desirable.
+
+The ext3 support should be implemented by extending the existing ext2 support (which is in src/sys/ufs/ext2fs), not by rewriting the whole thing over from scratch. It is possible that some of the ostensibly filesystem-independent code that was added along with the ffs WAPBL journaling extensions might be also useable as part of an ext3 implementation; but it also might not be.
+
+The full requirements for this project include complete support for ext3 in both the kernel and the userland tools. It is possible that a reduced version of this project with a clearly defined subset of these requirements could still be a viable GSOC project; if this appeals to you please coordinate with a prospective mentor.
 """
 ]]

adjust text for it being a couple years later now
Index: wikisrc/projects/project/binary_compat_puffs_backend.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/binary_compat_puffs_backend.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/binary_compat_puffs_backend.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/binary_compat_puffs_backend.mdwn	27 Feb 2014 04:52:33 -0000	1.3
@@ -15,7 +15,7 @@
 duration="3 months"
 
 description="""
-Currently, the [puffs(3)](http://netbsd.gw.com/cgi-bin/man-cgi?puffs+3+NetBSD-5.1+i386) interface between the kernel and userspace uses various system structures for passing information. Examples are `struct stat` and `struct uucred`. If these change in layout (such as with the recent time_t size change), old puffs servers must be recompiled.
+Currently, the [puffs(3)](http://netbsd.gw.com/cgi-bin/man-cgi?puffs+3+NetBSD-5.1+i386) interface between the kernel and userspace uses various system structures for passing information. Examples are `struct stat` and `struct uucred`. If these change in layout (such as with the time_t size change in NetBSD 6.0), old puffs servers must be recompiled.
 
 The purpose of the project is to:
 

Rewrite this project in sane terms.
Index: wikisrc/projects/project/xmlif.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/xmlif.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/xmlif.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/xmlif.mdwn	27 Feb 2014 04:38:47 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Research converting system interfaces to XML"
+title="Language-neutral interface specifications (research)"
 
 contact="""
 [tech-kern](mailto:tech-kern@NetBSD.org)
@@ -15,13 +15,39 @@
 duration="3 months"
 
 description="""
-System interfaces are currently specified as C prototypes, C preprocessor macros and C structures. This limits the ability to do automatic processing with them. There are some cases in the tree which implement an ad-hoc domain specific language and a script producing a C representation of the data, for example vnode_if.src and namei.src.
+Programmatic interfaces in the system (at various levels) are currently specified in C: functions are declared with C prototypes, constants with C preprocessor macros, etc. While this is a reasonable choice for a project written in C, and good enough for most general programming, it falls down on some points, especially for published/supported interfaces. The system call interface is the most prominent such interface, and the one where these issues are most visible; however, other more internal interfaces are also candidates.
 
-The goal of the project is to come up with a specification language and test it by rewriting a considerable subset of the current C headers in it. A translator for generating the C representations and documentation should also be implemented. Finally, the student should suggest and implement any other use for the translator. An example is autogenerating code to print structures in a human-readable form from the ddb kernel debugger.
+Declaring these interfaces in some other form, presumably some kind of interface description language intended for the purpose, and then generating the corresponding C declarations from that form, solves some of these problems. The goal of this project is to investigate the costs and benefits of this scheme, and various possible ways to pursue it sanely, and produce a proof-of-concept implementation for a selected interface that solves a real problem.
 
-This is more of a research project than a simple implementation. The goals are very loosely set now, but should be exactly specified by the student in the application.
+Note that as of this writing many candidate internal interfaces do not really exist in practice or are not adequately structured enough to support this treatment.
 
-For honors, a static analyzer examining if calls are made with the correct type of flag arguments can be written as the third requirement. It would warn about for example `malloc(s, M_TEMP, PR_WAITOK);`.
+Problems that have been observed include:
+
+* Using system calls from languages that aren't C. While many compilers and interpreters have runtimes written in C, or C-oriented foreign function interfaces, many do not, and rely on munging system headers in (typically) ad hoc ways to extract necessary declarations.
+
+* Generating test or validation code. For example, there is some rather bodgy code attached to the vnode interface that allows crosschecking the locking behavior observed at runtime against a specification. This code is currently generated from the existing vnode interface specification in vnode_if.src; however, the specification, the generator, and the output code all leave a good deal to be desired. Other interfaces where this kind of validation might be helpful are not handled at all.
+
+* Generating marshalling code. The code for (un)marshalling system call arguments within the kernel is all handwritten; this is laborious and error-prone, especially for the various compat modules. A code generator for this would save a lot of work. Note that there is already an interface specification of sorts in syscalls.master; this would need to be extended or converted to a better description language. Similarly, the code used by puffs and refuse to ship file system operations off to userland is largely or totally handwritten and in a better world would be automatically generated.
+
+* Generating trace or debug code. The code for tracing system calls and decoding the trace results (ktrace and kdump) is partly hand-written and partly generated with some fairly ugly shell scripts. This could be systematized; and also, given a complete specification to work from, a number of things that kdump doesn't capture very well could be improved. (For example, kdump doesn't decode the binary values of flags arguments to most system calls.)
+
+* Add your own here. (If proposing this project for GSOC, your proposal should be specific about what problem you're trying to solve and how the use of an interface definition language will help solve it. Please consult ahead of time to make sure the problem you're trying to solve is considered interesting/worthwhile.)
+
+The project requires: (1) choose a target interface and problem; (2) evaluate existing IDLs (there are many) for suitability; (3) choose one, as roll your own should be only a last resort; (4) prepare a definition for the target interface in your selected IDL; (5) implement the code generator to produce the corresponding C declarations; (6) integrate the code generator and its output into the system (this should require minimal changes); (7) implement the code generator and other material to solve your target problem.
+
+Note that while points 5, 6, and 7 are a reasonably simple matter of programming, parts 1-3 and possibly 4 constitute research -- these parts are as important as the code is, maybe more so, and doing them well is critical to success.
+
+The IDL chosen should if at all possible be suitable for repeating steps 4-7 for additional choices of target interface and problem, as there are a lot of such choices and many of them are probably worth pursuing in the long run.
+
+Some things to be aware of:
+
+* syscalls.master contains a partial specification of the functions in the system call interface. (But not the types or constants.)
+* vnode_if.src contains a partial specification of the vnode interface.
+* There is no specification, partial or otherwise, of the other parts of the VFS interface, other than the code and the (frequently outdated) section 9 man pages.
+* There are very few other interfaces within the kernel that are (as of this writing) structured enough or stable enough to permit using an IDL without regretting it. The bus interface might be one.
+* Another possible candidate is to pursue a specification language for handling all the conditional visibility and namespace control material in the userspace header files. This requires a good deal of familiarity with the kinds of requirements imposed by standards and the way these requirements are generally understood and may be too large a project for the GSOC time frame.
+
+Note: the original form of this project description was written assuming that the interface description language would be XML. The belief that plain XML would be an adequate IDL probably arose from too much koolaid. It is unlikely that an XML-based IDL will be accepted by the community as the general consensus is that XML is not human readable and is not suitable as a source format.
 """
 ]]
 

Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/projects/gsoc.mdwn	13 Feb 2014 21:36:46 -0000	1.14
+++ wikisrc/projects/gsoc.mdwn	24 Feb 2014 20:05:12 -0000	1.15
@@ -1,6 +1,6 @@
 [[!meta title="Google Summer of Code project proposals"]]
 
-NetBSD participated successfully in all of Google's Summer of Code
+<!-- NetBSD participated successfully in all of Google's Summer of Code
 programs to date (see our results of
 [2005](http://www.netbsd.org/foundation/press/soc-summary.html),
 [2006](http://www.netbsd.org/foundation/press/soc2006-summary.html),
@@ -11,7 +11,8 @@
 [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
-we are hope to once again participate as a mentoring organization in 2014.
+we are hope to once again participate as a mentoring organization in 2014. -->
+*** NetBSD is not participating as a mentoring organisation in 2014. ***
 
 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

Index: wikisrc/projects/project/u-boot__95__pkgsrc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/u-boot__95__pkgsrc.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/u-boot__95__pkgsrc.mdwn	19 Feb 2014 07:35:04 -0000	1.1
+++ wikisrc/projects/project/u-boot__95__pkgsrc.mdwn	19 Feb 2014 07:37:10 -0000	1.2
@@ -10,7 +10,7 @@
 [Martin Husemann](mailto:martin@NetBSD.org)
 """
 
-category="uesrland"
+category="userland"
 difficulty="medium"
 duration="3 months"
 

--- /dev/null	2014-03-30 15:32:01.000000000 +0000
+++ wikisrc/projects/project/u-boot__95__pkgsrc.mdwn	2014-03-30 15:37:44.000000000 +0000
@@ -0,0 +1,39 @@
+[[!template id=project
+
+title="Make u-boot compilable on NetBSD"
+
+contact="""
+[tech-toolchain](mailto:tech-toolchain@NetBSD.org)
+"""
+
+mentors="""
+[Martin Husemann](mailto:martin@NetBSD.org)
+"""
+
+category="uesrland"
+difficulty="medium"
+duration="3 months"
+
+description="""
+The U-Boot bootloader is being used by an increasing number of devices, including lots which run NetBSD.
+The NetBSD ${TOOLDIR} infrastructure even includes the mkubootimage program, which is used to wrap
+binaries (e.g. a kernel) into a packet understood by U-Boot.
+
+While the ${TOOLDIR} provides all toolchain bits needed (cross-compiler, assembler, linker, ...) and can
+be created by the build.sh script automatically for any supported architecture, U-Boot itself needs
+to be compiled natively on a Linux machine.
+
+The purpose of this project is to fix this, and feed as much as possible of the resulting
+changes upstream to the U-Boot developers.
+
+If possible, the result should be a pkgsrc package, that only needs to be pointed at a
+pre-populated tooldir for building. But a simple bsd style makefile would be good enough as well.
+
+An optional extension (but unlikely to be doable within the GSoC timescale): add support
+for loading from FFS file system to U-Boot. This would allow devices with SATA or USB disks to
+load the kernel directly from the root file system (while currently a wrappd .ub copy of the kernel
+has to be put into flash or on SD card).
+"""
+]]
+
+[[!tag gsoc]]

Index: wikisrc/projects/project/virtual-box-guest-tools.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/virtual-box-guest-tools.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/projects/project/virtual-box-guest-tools.mdwn	19 Feb 2014 07:14:20 -0000	1.6
+++ wikisrc/projects/project/virtual-box-guest-tools.mdwn	19 Feb 2014 07:16:49 -0000	1.7
@@ -16,7 +16,7 @@
 duration="3 months"
 
 description="""
-NOTE: this project has mostly been partly completed during GSoC 2013, the remaining cleanup work and tidying is likely not enough work for another GSoC!
+NOTE: this project has been partly completed during GSoC 2013, the remaining cleanup work and tidying is likely not enough work for another GSoC!
 
 [Oracle VM Virtualbox](http://www.virtualbox.org/) is a virtualization platform that already runs NetBSD guest machines fine.
 

Index: wikisrc/projects/project/virtual-box-guest-tools.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/virtual-box-guest-tools.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/virtual-box-guest-tools.mdwn	3 Oct 2013 14:17:26 -0000	1.5
+++ wikisrc/projects/project/virtual-box-guest-tools.mdwn	19 Feb 2014 07:14:20 -0000	1.6
@@ -16,6 +16,8 @@
 duration="3 months"
 
 description="""
+NOTE: this project has mostly been partly completed during GSoC 2013, the remaining cleanup work and tidying is likely not enough work for another GSoC!
+
 [Oracle VM Virtualbox](http://www.virtualbox.org/) is a virtualization platform that already runs NetBSD guest machines fine.
 
 However, there are a few fine tunings missing: mouse and graphics support, better integration via client tools (clipboard sharing, time synchronization), and maybe

removed
--- wikisrc/projects/project/makefs-udf.mdwn	2014-03-30 15:37:44.000000000 +0000
+++ /dev/null	2014-03-30 15:32:01.000000000 +0000
@@ -1,37 +0,0 @@
-[[!template id=project
-
-title="Add UDF support to makefs"
-
-contact="""
-[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
-"""
-
-mentors="""
-[Martin Husemann](mailto:martin@NetBSD.org)
-"""
-
-category="userland"
-difficulty="easy"
-duration="3 months"
-
-description="""
-The makefs tool is a very versatile userland application used for various tasks
-during the build of a NetBSD release.
-It can also be used to create CD or DVD images, not only for building NetBSD install
-media, but also for backup purposes.
-
-Unfortunately it does not currently support creating blue ray images in UDF format.
-
-NetBSD does support UDF, even writable, but using mount_udf for image creation requires
-running on NetBSD (while makefs is very portable and part of the cross-building environment),
-and also requires pre-allocation of space to the created image.
-
-Adding support for UDF to makefs is easy. The existing NetBSD header files can be
-used and the file system format is well documented.
-
-Note that you do not need a BlueRay burner for this project, you can create (small) test
-images from arbitrary data and verify them with tools readily available in pkgsrc.
-"""
-]]
-
-[[!tag gsoc]]

Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/projects/gsoc.mdwn	13 Feb 2014 21:32:45 -0000	1.13
+++ wikisrc/projects/gsoc.mdwn	13 Feb 2014 21:36:46 -0000	1.14
@@ -46,7 +46,7 @@
 many questions from our [[project application guidelines|application]] as
 possible.  The interested developers will be glad to respond to you there.
 
-**<span style="color:red">Please note that Google Summer-of-Code projects are a full (day-) time job.</span>**
+**Please note that Google Summer-of-Code projects are a full (day-) time job.**
 
 A positive mid-term evaluation is only possible if usable code has been
 committed by that time.  Make sure your schedule allows for this.

Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/projects/gsoc.mdwn	13 Feb 2014 21:16:24 -0000	1.12
+++ wikisrc/projects/gsoc.mdwn	13 Feb 2014 21:32:45 -0000	1.13
@@ -46,8 +46,7 @@
 many questions from our [[project application guidelines|application]] as
 possible.  The interested developers will be glad to respond to you there.
 
-**Please note that Google Summer-of-Code projects are a full (day-) time
-job.**
+**<span style="color:red">Please note that Google Summer-of-Code projects are a full (day-) time job.</span>**
 
 A positive mid-term evaluation is only possible if usable code has been
 committed by that time.  Make sure your schedule allows for this.

update dates and links
Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/projects/gsoc.mdwn	8 Apr 2013 19:25:43 -0000	1.11
+++ wikisrc/projects/gsoc.mdwn	13 Feb 2014 21:16:24 -0000	1.12
@@ -8,8 +8,10 @@
 [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)) and
-we are once again participating as a mentoring organization in 2013.
+[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
+we are hope to once again participate as a mentoring organization in 2014.
 
 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

removed
--- wikisrc/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/comment_4_7e9716d3c206b9b72e9db863d717121c._comment	2014-03-30 15:37:45.000000000 +0000
+++ /dev/null	2014-03-30 15:32:01.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawl5MKJXZOcQk7m7jSddfFUzGXdnrJ4oyD8"
- nickname="Michel"
- subject="dd: shouldn't you &quot;zero&quot; the usb device first?"
- date="2014-02-10T21:20:53Z"
- content="""
-Shouldn't it be part of the procedure using dd to \"zero\" the pendrive before actually dd'ing the image?
-"""]]

Added a comment: dd: shouldn't you "zero" the usb device first?
--- /dev/null	2014-03-30 15:32:01.000000000 +0000
+++ wikisrc/tutorials/how_to_install_netbsd_from_an_usb_memory_stick/comment_4_7e9716d3c206b9b72e9db863d717121c._comment	2014-03-30 15:37:45.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawl5MKJXZOcQk7m7jSddfFUzGXdnrJ4oyD8"
+ nickname="Michel"
+ subject="dd: shouldn't you &quot;zero&quot; the usb device first?"
+ date="2014-02-10T21:20:53Z"
+ content="""
+Shouldn't it be part of the procedure using dd to \"zero\" the pendrive before actually dd'ing the image?
+"""]]

link this years fosdem presentation
Index: wikisrc/rumpkernel.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/rumpkernel.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/rumpkernel.mdwn	30 Jan 2014 00:00:32 -0000	1.3
+++ wikisrc/rumpkernel.mdwn	10 Feb 2014 15:25:04 -0000	1.4
@@ -152,6 +152,11 @@
 
 ### Conference publications and talks
 
+-   "Rump Kernels, Just Components" talks about rump kernels as reusable
+    and platform-agnostic drivers.  The intended audience is developers.  The
+    [video](http://video.fosdem.org/2014/H2214/Sunday/Rump_Kernels_Just_Components.webm)
+    and [slides](https://fosdem.org/2014/schedule/event/01_uk_rump_kernels/attachments/slides/398/export/events/attachments/01_uk_rump_kernels/slides/398/fosdem2014.pdf) are available.
+    Presented at FOSDEM 2014 (Microkernel devroom).
 -   "The Anykernel and Rump Kernels" gives a general overview and
     demonstrates rump kernels on Windows and in Firefox. The
     [video](http://video.fosdem.org/2013/maintracks/K.1.105/The_Anykernel_and_Rump_Kernels.webm),

update for 6.1.3 release
Index: wikisrc/ports/acorn26.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn26.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/acorn26.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/acorn26.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=port
 port="acorn26"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.1"
 changes_cur="6.0"
Index: wikisrc/ports/acorn32.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn32.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/acorn32.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/acorn32.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=port
 port="acorn32"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.1"
 changes_cur="6.0"
Index: wikisrc/ports/algor.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/algor.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/ports/algor.mdwn	18 Jan 2014 00:11:19 -0000	1.3
+++ wikisrc/ports/algor.mdwn	9 Feb 2014 20:45:20 -0000	1.4
@@ -1,6 +1,6 @@
 [[!template id=port
 port="algor"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.0"
 changes_cur="6.0"
Index: wikisrc/ports/alpha.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/alpha.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/alpha.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/alpha.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=port
 port="alpha"
-cur_rel="6.1.2"
+cur_rel="6.1.3"
 pkg_rel="5.1"
 future_rel="7.0"
 changes_cur="6.0"
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports/amiga.mdwn	18 Jan 2014 00:11:19 -0000	1.6
+++ wikisrc/ports/amiga.mdwn	9 Feb 2014 20:45:20 -0000	1.7
@@ -1,6 +1,6 @@
 [[!template id=port
 port="amiga"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.0"
 changes_cur="6.0"
Index: wikisrc/ports/amigappc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amigappc.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/amigappc.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/amigappc.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,7 +1,7 @@
 [[!template id=port
 port="amigappc"
 port_alt="powerpc"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 pkg_rel="6.0"
 future_rel="7.0"
 changes_cur="6.0"
Index: wikisrc/ports/arc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/arc.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/arc.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/arc.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=port
 port="arc"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.0"
 changes_cur="6.0"
Index: wikisrc/ports/atari.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/atari.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/atari.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/atari.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=port
 port="atari"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.0"
 changes_cur="6.0"
Index: wikisrc/ports/bebox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/bebox.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/bebox.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/bebox.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=port
 port="bebox"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.0"
 changes_cur="6.0"
Index: wikisrc/ports/cats.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cats.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/cats.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/cats.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=port
 port="cats"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.1"
 changes_cur="6.0"
Index: wikisrc/ports/cesfic.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cesfic.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/cesfic.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/cesfic.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,7 +1,7 @@
 [[!template id=port
 port="cesfic"
 port_alt="m68k"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.0"
 changes_cur="6.0"
Index: wikisrc/ports/cobalt.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cobalt.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/cobalt.mdwn	18 Jan 2014 00:11:19 -0000	1.2
+++ wikisrc/ports/cobalt.mdwn	9 Feb 2014 20:45:20 -0000	1.3
@@ -1,6 +1,6 @@
 [[!template id=port
 port="cobalt"
-cur_rel="6.1.2"  
+cur_rel="6.1.3"  
 future_rel="7.0"
 pkg_rel="6.0"
 changes_cur="6.0"
Index: wikisrc/ports/dreamcast.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/dreamcast.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3

(Diff truncated)
Added a comment: Problem booting from USB
--- /dev/null	2014-03-30 15:32:01.000000000 +0000
+++ wikisrc/users/ryoon/how_to_install_netbsd_amd64_to_macbook_air_11_inch/comment_1_049537beb1ad9345627732e10671023d._comment	2014-03-30 15:37:47.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawk7EkT0SzXdMfPrh5GnsucfYp4BGYGu0pI"
+ nickname="Simon"
+ subject="Problem booting from USB"
+ date="2014-02-05T23:30:14Z"
+ content="""
+It would be awesome if you could elaborate the part when you boot from the USB. I have tried multiple options and just cannot get my Macbook Air to boot. 
+"""]]

Index: wikisrc/projects/project/system-upgrade.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/system-upgrade.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/system-upgrade.mdwn	15 Apr 2013 22:34:02 -0000	1.2
+++ wikisrc/projects/project/system-upgrade.mdwn	4 Feb 2014 10:35:09 -0000	1.3
@@ -13,6 +13,7 @@
 category="userland"
 difficulty="easy"
 duration="3 months"
+done_by="gnrp"
 
 description="""
 Currently, the update process of NetBSD is rather tiring, though it could be 

Index: wikisrc/projects/project/fs_scrub_flags.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fs_scrub_flags.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/fs_scrub_flags.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/fs_scrub_flags.mdwn	4 Feb 2014 10:34:12 -0000	1.3
@@ -13,6 +13,7 @@
 category="kernel"
 difficulty="easy"
 duration="3 months"
+done_by="Przemyslaw Sierocinski"
 
 description="""
 This project requires the implementation of a new mount option, and a new system and user file system flag, which, when set, will write random data over file system blocks before they are to be deleted. In the NetBSD kernel, this will take place at the time of the last unlink of a file, and when ftruncate is called.

note snabb switch support
Index: wikisrc/rumpkernel.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/rumpkernel.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/rumpkernel.mdwn	24 Jan 2014 13:28:42 -0000	1.2
+++ wikisrc/rumpkernel.mdwn	30 Jan 2014 00:00:32 -0000	1.3
@@ -127,8 +127,9 @@
 -   [fs-utils: File system image access
     utilities](https://github.com/stacktic/fs-utils)
 -   Fast userspace packet processing: TCP/IP stack for use with
-    [DPDK](https://github.com/rumpkernel/dpdk-rumptcpip) or
-    [netmap](https://github.com/rumpkernel/netmap-rumptcpip)
+    [DPDK](https://github.com/rumpkernel/dpdk-rumptcpip), 
+    [netmap](https://github.com/rumpkernel/netmap-rumptcpip) or
+    [Snabb Switch](https://github.com/anttikantee/snabbswitch/tree/rumpkernel/)
 
 ### Articles, Tutorials & Howtos
 

Add newly released images: 5.1.4, 5.2.2, 6.0.4, 6.1.3
Index: wikisrc/amazon_ec2/amis.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/amazon_ec2/amis.mdwn,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- wikisrc/amazon_ec2/amis.mdwn	29 Sep 2013 23:17:48 -0000	1.34
+++ wikisrc/amazon_ec2/amis.mdwn	26 Jan 2014 20:03:56 -0000	1.35
@@ -46,6 +46,17 @@
   <td>ami-2141e63c</td><!-- sa-east-1 -->
 </tr>
 <tr>
+  <th>NetBSD 5.1.4</th>
+  <td>ami-738eb31a</td><!-- us-east-1 -->
+  <td>ami-8cc5f7c9</td><!-- us-west-1 -->
+  <td>ami-6e16765e</td><!-- us-west-2 -->
+  <td>ami-226e9a55</td><!-- eu-west-1 -->
+  <td>ami-4e31671c</td><!-- ap-southeast-1 -->
+  <td>ami-815ec0bb</td><!-- ap-southeast-2 -->
+  <td>ami-75c8a174</td><!-- ap-northeast-1 -->
+  <td>ami-c96dcdd4</td><!-- sa-east-1 -->
+</tr>
+<tr>
   <th>NetBSD 5.2</th>
   <td>ami-097cfc60</td><!-- us-east-1 -->
   <td>ami-7ae8c93f</td><!-- us-west-1 -->
@@ -68,6 +79,17 @@
   <td>ami-4f41e652</td><!-- sa-east-1 -->
 </tr>
 <tr>
+  <th>NetBSD 5.2.2</th>
+  <td>ami-198cb170</td><!-- us-east-1 -->
+  <td>ami-20c5f765</td><!-- us-west-1 -->
+  <td>ami-841575b4</td><!-- us-west-2 -->
+  <td>ami-106d9967</td><!-- eu-west-1 -->
+  <td>ami-643f6936</td><!-- ap-southeast-1 -->
+  <td>ami-b15ec08b</td><!-- ap-southeast-2 -->
+  <td>ami-d1f79ed0</td><!-- ap-northeast-1 -->
+  <td>ami-876dcd9a</td><!-- sa-east-1 -->
+</tr>
+<tr>
   <th>NetBSD 6.0</th>
   <td>ami-1400bf7d</td><!-- us-east-1 -->
   <td>ami-9bac8bde</td><!-- us-west-1 -->
@@ -112,6 +134,17 @@
   <td>ami-7541e668</td><!-- sa-east-1 -->
 </tr>
 <tr>
+  <th>NetBSD 6.0.4</th>
+  <td>ami-e192af88</td><!-- us-east-1 -->
+  <td>ami-5cc5f719</td><!-- us-west-1 -->
+  <td>ami-48157578</td><!-- us-west-2 -->
+  <td>ami-6c6d991b</td><!-- eu-west-1 -->
+  <td>ami-0830665a</td><!-- ap-southeast-1 -->
+  <td>ami-695ec053</td><!-- ap-southeast-2 -->
+  <td>ami-81f59c80</td><!-- ap-northeast-1 -->
+  <td>ami-936dcd8e</td><!-- sa-east-1 -->
+</tr>
+<tr>
   <th>NetBSD 6.1</th>
   <td>ami-8b751ce2</td><!-- us-east-1 -->
   <td>ami-1185aa54</td><!-- us-west-1 -->
@@ -144,6 +177,17 @@
   <td>ami-8d930d8c</td><!-- ap-northeast-1 -->
   <td>ami-9f44e382</td><!-- sa-east-1 -->
 </tr>
+<tr>
+  <th>NetBSD 6.1.3</th>
+  <td>ami-1d90ad74</td><!-- us-east-1 -->
+  <td>ami-aea092eb</td><!-- us-west-1 -->
+  <td>ami-30076700</td><!-- us-west-2 -->
+  <td>ami-6a7d891d</td><!-- eu-west-1 -->
+  <td>ami-dc34628e</td><!-- ap-southeast-1 -->
+  <td>ami-a1a33d9b</td><!-- ap-southeast-2 -->
+  <td>ami-93e68f92</td><!-- ap-northeast-1 -->
+  <td>ami-6b6dcd76</td><!-- sa-east-1 -->
+</tr>
 </table>
 
 ## i386 -- 32 bit AMIs
@@ -186,6 +230,17 @@
   <td>ami-5541e648</td><!-- sa-east-1 -->
 </tr>
 <tr>
+  <th>NetBSD 5.1.4</th>
+  <td>ami-0d82bf64</td><!-- us-east-1 -->
+  <td>ami-50c8fa15</td><!-- us-west-1 -->
+  <td>ami-7e1a7a4e</td><!-- us-west-2 -->
+  <td>ami-206a9e57</td><!-- eu-west-1 -->
+  <td>ami-223e6870</td><!-- ap-southeast-1 -->
+  <td>ami-b95fc183</td><!-- ap-southeast-2 -->
+  <td>ami-bbd9b0ba</td><!-- ap-northeast-1 -->
+  <td>ami-776ece6a</td><!-- sa-east-1 -->
+</tr>
+<tr>
   <th>NetBSD 5.2</th><!-- Version -->
   <td>ami-637fff0a</td><!-- us-east-1 -->
   <td>ami-9ce8c9d9</td><!-- us-west-1 -->
@@ -208,6 +263,17 @@
   <td>ami-4141e65c</td><!-- sa-east-1 -->
 </tr>
 <tr>
+  <th>NetBSD 5.2.2</th>
+  <td>ami-3583be5c</td><!-- us-east-1 -->
+  <td>ami-cccefc89</td><!-- us-west-1 -->
+  <td>ami-fa1979ca</td><!-- us-west-2 -->
+  <td>ami-ca699dbd</td><!-- eu-west-1 -->
+  <td>ami-1a3e6848</td><!-- ap-southeast-1 -->
+  <td>ami-4f5fc175</td><!-- ap-southeast-2 -->
+  <td>ami-03d9b002</td><!-- ap-northeast-1 -->
+  <td>ami-476ece5a</td><!-- sa-east-1 -->
+</tr>
+<tr>
   <th>NetBSD 6.0</th>
   <td>ami-68ff4101</td><!-- us-east-1 -->
   <td>ami-59b4931c</td><!-- us-west-1 -->
@@ -252,6 +318,17 @@
   <td>ami-6b41e676</td><!-- sa-east-1 -->
 </tr>
 <tr>
+  <th>NetBSD 6.0.4</th>
+  <td>ami-8b87bae2</td><!-- us-east-1 -->
+  <td>ami-30cbf975</td><!-- us-west-1 -->
+  <td>ami-7c19794c</td><!-- us-west-2 -->
+  <td>ami-14689c63</td><!-- eu-west-1 -->
+  <td>ami-ac3167fe</td><!-- ap-southeast-1 -->
+  <td>ami-6f5fc155</td><!-- ap-southeast-2 -->
+  <td>ami-f1c4adf0</td><!-- ap-northeast-1 -->
+  <td>ami-236ece3e</td><!-- sa-east-1 -->
+</tr>
+<tr>
   <th>NetBSD 6.1</th>
   <td>ami-815138e8</td><!-- us-east-1 -->
   <td>ami-db80af9e</td><!-- us-west-1 -->
@@ -284,4 +361,15 @@
   <td>ami-d3930dd2</td><!-- ap-northeast-1 -->
   <td>ami-c944e3d4</td><!-- sa-east-1 -->
 </tr>
+<tr>
+  <th>NetBSD 6.1.3</th>
+  <td>ami-a185b8c8</td><!-- us-east-1 -->
+  <td>ami-e4cefca1</td><!-- us-west-1 -->
+  <td>ami-50187860</td><!-- us-west-2 -->
+  <td>ami-7e689c09</td><!-- eu-west-1 -->
+  <td>ami-fa3167a8</td><!-- ap-southeast-1 -->
+  <td>ami-1f5fc125</td><!-- ap-southeast-2 -->
+  <td>ami-13c2ab12</td><!-- ap-northeast-1 -->
+  <td>ami-016ece1c</td><!-- sa-east-1 -->
+</tr>
 </table>

Fix commands. and style
Index: wikisrc/users/ryoon/updating_openjdk7.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/ryoon/updating_openjdk7.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/ryoon/updating_openjdk7.mdwn	27 Jun 2013 14:09:09 -0000	1.3
+++ wikisrc/users/ryoon/updating_openjdk7.mdwn	25 Jan 2014 07:32:57 -0000	1.4
@@ -77,8 +77,10 @@
 using mercurial-2.x.
 
 For example,
+
     $ cd jdk
-    $ hg checkout tip
+    $ hg pull && hg update
+
 You should do in each directory in bsd-port/.
 
 In this case, I will use tip version.

Update URLs, also some minor edits.
Index: wikisrc/rumpkernel.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/rumpkernel.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/rumpkernel.mdwn	5 Jan 2014 14:53:58 -0000	1.1
+++ wikisrc/rumpkernel.mdwn	24 Jan 2014 13:28:42 -0000	1.2
@@ -34,7 +34,7 @@
 Currently, three implementations of the rump kernel hypercall interface
 exist.
 
--   The POSIX implementation is included in the NetBSD tree and makes
+-   The POSIX implementation is included in the NetBSD tree and allows
     rump kernels to run as userspace processes on most operating systems
     such as NetBSD, Linux and Solaris.
 -   The Xen implementation allows running rump kernels directly as Xen
@@ -55,9 +55,10 @@
 measured in milliseconds and memory footprint in 100kB's. This means
 that a rump kernel can be bootstrapped for example as part of a command
 line tool for virtually no cost or user impact. Rump kernels also
-mandate very little from the hypercall implementation meaning that rump
-kernels, and by extension NetBSD kernel drivers, can be hosted in
-virtually any environment.
+mandate very little from the hypercall implementation meaning that
+rump kernels, and by extension NetBSD kernel drivers, can be hosted in
+virtually any environment -- for example, rump kernels do not require
+a platform with an MMU.
 
 Use cases for rump kernels include:
 
@@ -92,29 +93,42 @@
 
 ## Further Reading
 
-### Dissertation
+### Book
 
-The following is the definitive guide to the anykernel and rump kernels
-and supercedes all earlier publications and terminology on the subject.
+The following book is the definitive guide to the anykernel and rump
+kernels and supercedes all earlier publications and terminology on
+the subject.
 
 -   [Flexible Operating System Internals: The Design and Implementation
     of the Anykernel and Rump
     Kernels](http://lib.tkk.fi/Diss/2012/isbn9789526049175/isbn9789526049175.pdf)
 
+Note that the book was finalized in summer 2012, so while the fundamentals
+are still accurate, some of the problems described in "Future Work"
+have already been solved.  Check out the links below.
+
+
 ### Software using rump kernels
 
-These links are interesting for people who want to use rump kernels in
-addition to reading about them.
+While the NetBSD source tree hosts the base kernel drivers and hypercall
+implementation, more I/O drivers, infrastructure scripts and hypercall
+implementations are hosted elsewhere.  Most of the code is hosted
+under the [rump kernels](https://github.com/rumpkernel/) organization
+on github.  Some highlights include:
 
 -   [Scripts for building rump kernels for POSIX
-    systems](https://github.com/anttikantee/buildrump.sh)
+    systems](https://github.com/rumpkernel/buildrump.sh)
+-   The [rumprun](https://github.com/rumpkernel/rumprun/) package
+    allows portable building and running of unmodified NetBSD userspace
+    applications -- extremely useful for configuring rump kernels (e.g.
+    network interfaces and routing tables)
 -   [Rump kernel hypercall implementation for Xen; rump kernels as Xen
-    DomU's](https://github.com/anttikantee/rumpuser-xen)
+    DomU's](https://github.com/rumpkernel/rumpuser-xen)
 -   [fs-utils: File system image access
     utilities](https://github.com/stacktic/fs-utils)
 -   Fast userspace packet processing: TCP/IP stack for use with
-    [DPDK](https://github.com/anttikantee/dpdk-rumptcpip) or
-    [netmap](https://github.com/anttikantee/netmap-rumptcpip)
+    [DPDK](https://github.com/rumpkernel/dpdk-rumptcpip) or
+    [netmap](https://github.com/rumpkernel/netmap-rumptcpip)
 
 ### Articles, Tutorials & Howtos
 

Fix list numbering
Index: wikisrc/releng/release-prep.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/release-prep.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/releng/release-prep.mdwn	22 Sep 2013 22:33:11 -0000	1.7
+++ wikisrc/releng/release-prep.mdwn	21 Jan 2014 01:40:55 -0000	1.8
@@ -111,24 +111,25 @@
 
 10. create torrents
 
-In the images directory:
+    In the images directory:
 
         for i in NetBSD-* ; do
         maketorrent-console http://tracker.netbsd.org:6969/announce $i
         done
-Get admins@ to add the torrent directory to <code>~torrent/runbt</code>.  
-*NOTE FROM SPZ, 2010-11-15:*
->it turns out that bittorrent can't do more than one 'allowed_dir'.
->
->Thus, we now have /ftp/pub/NetBSD/torrent. Please keep the permissions
->so that mirrors can't read the contents, since the contents are duplicate.
->
->(This should go into releng docs probably:)
->If you add a file that should be picked up by torrents, put it and its
->torrent control file where it belongs and hard-link the two into the
->appropriate directory in the torrent tree.
->Please note that the torrent tree cannot be used to publish the torrent
->control file via http or ftp.
+
+11.    Get admins@ to add the torrent directory to <code>~torrent/runbt</code>.  
+    *NOTE FROM SPZ, 2010-11-15:*
+    >it turns out that bittorrent can't do more than one 'allowed_dir'.
+    >
+    >Thus, we now have /ftp/pub/NetBSD/torrent. Please keep the permissions
+    >so that mirrors can't read the contents, since the contents are duplicate.
+    >
+    >(This should go into releng docs probably:)
+    >If you add a file that should be picked up by torrents, put it and its
+    >torrent control file where it belongs and hard-link the two into the
+    >appropriate directory in the torrent tree.
+    >Please note that the torrent tree cannot be used to publish the torrent
+    >control file via http or ftp.
 
 12. Get security-officer@ to sign binaries and ISOs.
     <code>localsrc/security/programs/rel-hashes.sh</code>

Fix boards links
Index: wikisrc/ports/mvme68k.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/mvme68k.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/ports/mvme68k.mdwn	18 Jan 2014 00:11:19 -0000	1.3
+++ wikisrc/ports/mvme68k.mdwn	19 Jan 2014 02:54:38 -0000	1.4
@@ -21,11 +21,11 @@
 These are the Motorola Single Board Computers that NetBSD/mvme68k
 supports.
 
--   [MVME147 family](#MVME147%20family)
--   [MVME162 family](#MVME162%20family)
--   [MVME167 family](#MVME167%20family)
--   [MVME172 family](#MVME172%20family)
--   [MVME177 family](#MVME177%20family)
+-   [MVME147 family](http://www.NetBSD.org/ports/mvme68k/boards.html#MVME147%20family)
+-   [MVME162 family](http://www.NetBSD.org/ports/mvme68k/boards.html#MVME162%20family)
+-   [MVME167 family](http://www.NetBSD.org/ports/mvme68k/boards.html#MVME167%20family)
+-   [MVME172 family](http://www.NetBSD.org/ports/mvme68k/boards.html#MVME172%20family)
+-   [MVME177 family](http://www.NetBSD.org/ports/mvme68k/boards.html#MVME177%20family)
 
 ## Boot options
 

* Introduce pkg_rel for pre-build binary package release link etc.
* Bump to 6.1.2 release
Index: wikisrc/ports/acorn26.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn26.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/acorn26.mdwn	17 Dec 2012 23:03:30 -0000	1.1
+++ wikisrc/ports/acorn26.mdwn	18 Jan 2014 00:11:19 -0000	1.2
@@ -1,7 +1,8 @@
 [[!template id=port
 port="acorn26"
-cur_rel="6.0"  
+cur_rel="6.1.2"  
 future_rel="7.0"
+pkg_rel="6.1"
 changes_cur="6.0"
 changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/arm26/arch310.gif"
Index: wikisrc/ports/acorn32.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn32.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/acorn32.mdwn	18 Dec 2012 16:18:49 -0000	1.1
+++ wikisrc/ports/acorn32.mdwn	18 Jan 2014 00:11:19 -0000	1.2
@@ -1,7 +1,8 @@
 [[!template id=port
 port="acorn32"
-cur_rel="6.0"  
+cur_rel="6.1.2"  
 future_rel="7.0"
+pkg_rel="6.1"
 changes_cur="6.0"
 changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/acorn32/riscpc.gif"
Index: wikisrc/ports/algor.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/algor.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/algor.mdwn	15 Mar 2013 00:40:32 -0000	1.2
+++ wikisrc/ports/algor.mdwn	18 Jan 2014 00:11:19 -0000	1.3
@@ -1,7 +1,8 @@
 [[!template id=port
 port="algor"
-cur_rel="6.0"  
+cur_rel="6.1.2"  
 future_rel="7.0"
+pkg_rel="6.0"
 changes_cur="6.0"
 changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/algor/alogo2.gif"
Index: wikisrc/ports/alpha.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/alpha.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/alpha.mdwn	18 Dec 2012 16:18:49 -0000	1.1
+++ wikisrc/ports/alpha.mdwn	18 Jan 2014 00:11:19 -0000	1.2
@@ -1,6 +1,7 @@
 [[!template id=port
 port="alpha"
-cur_rel="6.0"  
+cur_rel="6.1.2"
+pkg_rel="5.1"
 future_rel="7.0"
 changes_cur="6.0"
 changes_future="7.0"
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/amiga.mdwn	22 Dec 2013 11:56:00 -0000	1.5
+++ wikisrc/ports/amiga.mdwn	18 Jan 2014 00:11:19 -0000	1.6
@@ -1,7 +1,8 @@
 [[!template id=port
 port="amiga"
-cur_rel="6.0"  
+cur_rel="6.1.2"  
 future_rel="7.0"
+pkg_rel="6.0"
 changes_cur="6.0"
 changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/amiga/header.gif"
Index: wikisrc/ports/amigappc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amigappc.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/amigappc.mdwn	18 Dec 2012 16:18:49 -0000	1.1
+++ wikisrc/ports/amigappc.mdwn	18 Jan 2014 00:11:19 -0000	1.2
@@ -1,6 +1,8 @@
 [[!template id=port
 port="amigappc"
-cur_rel="6.0"  
+port_alt="powerpc"
+cur_rel="6.1.2"  
+pkg_rel="6.0"
 future_rel="7.0"
 changes_cur="6.0"
 changes_future="7.0"
Index: wikisrc/ports/arc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/arc.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/arc.mdwn	18 Dec 2012 21:32:59 -0000	1.1
+++ wikisrc/ports/arc.mdwn	18 Jan 2014 00:11:19 -0000	1.2
@@ -1,7 +1,8 @@
 [[!template id=port
 port="arc"
-cur_rel="6.0"  
+cur_rel="6.1.2"  
 future_rel="7.0"
+pkg_rel="6.0"
 changes_cur="6.0"
 changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/arc/2200.gif"
Index: wikisrc/ports/atari.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/atari.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/atari.mdwn	18 Dec 2012 21:32:59 -0000	1.1
+++ wikisrc/ports/atari.mdwn	18 Jan 2014 00:11:19 -0000	1.2
@@ -1,7 +1,8 @@
 [[!template id=port
 port="atari"
-cur_rel="6.0"  
+cur_rel="6.1.2"  
 future_rel="7.0"
+pkg_rel="6.0"
 changes_cur="6.0"
 changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/atari/atari.gif"
Index: wikisrc/ports/bebox.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/bebox.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/bebox.mdwn	18 Dec 2012 21:32:59 -0000	1.1
+++ wikisrc/ports/bebox.mdwn	18 Jan 2014 00:11:19 -0000	1.2
@@ -1,7 +1,8 @@
 [[!template id=port
 port="bebox"
-cur_rel="6.0"  
+cur_rel="6.1.2"  
 future_rel="7.0"
+pkg_rel="6.0"
 changes_cur="6.0"
 changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/bebox/bebox.gif"
Index: wikisrc/ports/cats.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cats.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/cats.mdwn	18 Dec 2012 21:32:59 -0000	1.1
+++ wikisrc/ports/cats.mdwn	18 Jan 2014 00:11:19 -0000	1.2
@@ -1,7 +1,8 @@
 [[!template id=port
 port="cats"
-cur_rel="6.0"  
+cur_rel="6.1.2"  
 future_rel="7.0"
+pkg_rel="6.1"
 changes_cur="6.0"
 changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/cats/cats.gif"
Index: wikisrc/ports/cesfic.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cesfic.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/cesfic.mdwn	18 Dec 2012 21:32:59 -0000	1.1
+++ wikisrc/ports/cesfic.mdwn	18 Jan 2014 00:11:19 -0000	1.2
@@ -1,7 +1,9 @@
 [[!template id=port
 port="cesfic"
-cur_rel="6.0"  
+port_alt="m68k"
+cur_rel="6.1.2"  
 future_rel="7.0"
+pkg_rel="6.0"
 changes_cur="6.0"
 changes_future="7.0"
 about="""
Index: wikisrc/ports/cobalt.mdwn
===================================================================

(Diff truncated)
Add missing command
Index: wikisrc/ports/evbarm/qemu_arm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/qemu_arm.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/ports/evbarm/qemu_arm.mdwn	12 Jan 2014 00:26:13 -0000	1.4
+++ wikisrc/ports/evbarm/qemu_arm.mdwn	18 Jan 2014 00:09:19 -0000	1.5
@@ -61,6 +61,7 @@
     # ifconfig tap0 create
     # ifconfig tap0 0.0.0.0 up
     # brconfig bridge0 add tap0
+    $ cp /usr/obj/evbearm-el/sys/arch/evbarm/compile/INTEGRATOR_CP/netbsd.gz.ub .
     $ qemu-system-arm -M integratorcp -cpu arm1136 -m 512m -kernel netbsd.gz.ub -serial stdio -net nic -net tap,fd=3 3<>/dev/tap0
 
 # After booted

Fix style
Index: wikisrc/ports/zaurus.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/zaurus.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/zaurus.mdwn	21 Dec 2012 02:12:57 -0000	1.1
+++ wikisrc/ports/zaurus.mdwn	18 Jan 2014 00:07:23 -0000	1.2
@@ -29,13 +29,13 @@
 ###Supported Peripherals
 
 * Serial and infrared ports ([[!template id=man name="com" section="4"]])
-* LCD display panel (lcd,w100lcd)
-* Native keyboard (zkbd)
-* PCMCIA port (pxapcic)
+* LCD display panel (*lcd*, *w100lcd*)
+* Native keyboard (*zkbd*)
+* PCMCIA port (*pxapcic*)
 * On-board microdrive ([[!template id=man name="wd" section="4"]])
-* Remote control (zrc)
-* Sound chip (zaudio)
-* Touch panel (ztp)
+* Remote control (*zrc*)
+* Sound chip (*zaudio*)
+* Touch panel (*ztp*)
 * MMC/SD/SDHC card ([[!template id=man name="sdmmc" section="4"]], [[!template id=man name="ld" section="4"]])
 * USB Controller ([[!template id=man name="ohci" section="4"]])
 
@@ -46,9 +46,10 @@
 
 """
 additional="""
-[some install tips](http://mail-index.netbsd.org/port-zaurus/2011/05/20/msg000045.html)
-[SHARP Zaurus support station - Developer information (including Linux source code)](http://support.ezaurus.com/developer/)
-[OpenBSD Zaurus port](http://www.openbsd.org/zaurus.html)
+* [some install tips](http://mail-index.netbsd.org/port-zaurus/2011/05/20/msg000045.html)
+* [SHARP Zaurus support station - Developer information (including Linux source code)](http://support.ezaurus.com/developer/)
+* [OpenBSD Zaurus port](http://www.openbsd.org/zaurus.html)
+* [NetBSD/zaurus FAQ](http://www.NetBSD.org/ports/zaurus/faq.html)
 """
 
 ]]

Fix style
Index: wikisrc/ports/x68k.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/x68k.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/x68k.mdwn	21 Dec 2012 02:12:57 -0000	1.1
+++ wikisrc/ports/x68k.mdwn	18 Jan 2014 00:00:22 -0000	1.2
@@ -6,19 +6,28 @@
 changes_future="7.0"
 thumbnail="http://www.netbsd.org/images/ports/x68k/super.gif"
 about="""
-NetBSD/x68k is the port of NetBSD for the Japanese personal computer [SHARP](http://www.sharp.co.jp/) X68000/X68030 series. It runs on some models of X680x0 with MMU and FPU. When you use NetBSD/x68k, you may have to replace your machine settings (e.g. changing MC68EC30 with MC68030).
+NetBSD/x68k is the port of NetBSD for the Japanese personal computer
+[SHARP](http://www.sharp.co.jp/) X68000/X68030 series.
+It runs on some models of X680x0 with MMU and FPU.
+When you use NetBSD/x68k, you may have to replace your machine settings
+(e.g. changing MC68EC30 with MC68030).
 
 ###The History of NetBSD/x68k
 
-The NetBSD/x68k port was [started in 1993 by OKI Masaru](http://www.sra.co.jp/public/doc/bsd/NetBSD/NetBSD-x68k). At first, it was ported from NetBSD/amiga, and tracked NetBSD 0.9, NetBSD 1.0, and NetBSD 1.1. NetBSD/x68k has been included in the official release of NetBSD from 1.2 onwards.
+The NetBSD/x68k port was [started in 1993 by OKI Masaru](http://www.sra.co.jp/public/doc/bsd/NetBSD/NetBSD-x68k).
+At first, it was ported from NetBSD/amiga, and tracked NetBSD 0.9,
+NetBSD 1.0, and NetBSD 1.1.
+NetBSD/x68k has been included in the official release of NetBSD
+from 1.2 onwards.
 
 Since April 2002, Nishimura Takeshi is maintaining the NetBSD/x68k port.
 
 """
 supported_hardware="""
-Supported System Models
+### Supported System Models
 
-It is necessary to install Xellent30 or Jupiter-X MPU accelerator for X68000 series.
+It is necessary to install Xellent30 or Jupiter-X MPU accelerator
+for X68000 series.
 
 040turbo and 060turbo are also supported for X68030.
 
@@ -30,11 +39,13 @@
 * X68000PRO/X68000PRO HD
 * X68000ACE/X68000ACE HD
 
-Supported Peripherals
+### Supported Peripherals
 
-NetBSD/x68k requires Motorola 680[346]0 processor (with MMU), SCSI board and harddisks, and over 4MByte memory and 100MByte of disk space.
+NetBSD/x68k requires Motorola 680[346]0 processor (with MMU),
+SCSI board and harddisks, and over 4MByte memory and 100MByte of disk space.
 
-Although the in-kernel FPU emulator can be built into the kernel for 68030-based systems, we recommend to install a FPU.
+Although the in-kernel FPU emulator can be built into the kernel
+for 68030-based systems, we recommend to install a FPU.
 
 * Sharp genuine MB89352 SCSI host adapter and their compatibles
 * Most SCSI devices
@@ -55,15 +66,15 @@
 
 """
 unsupported_hardware="""
- Hardware that we do NOT currently support, but get many questions about:
+Hardware that we do NOT currently support, but get many questions about:
 
 * Old (SASI compatible) hard disk interface
 
 We are planning future support for many of these devices. Contributions are welcomed!
 """
 additional="""
-[How to install in Japanese](http://www.ceres.dti.ne.jp/tsutsui/netbsd/x68k/NetBSD-x68k-on-XM6i.html)
-[XM6i can emulate an X68030 running](http://xm6i.org/)
+* [How to install in Japanese](http://www.ceres.dti.ne.jp/tsutsui/netbsd/x68k/NetBSD-x68k-on-XM6i.html)
+* [XM6i can emulate an X68030 running](http://xm6i.org/)
 """
 
 ]]

Fix links
Index: wikisrc/ports/vax-models.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/vax-models.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/vax-models.mdwn	22 Dec 2012 04:03:19 -0000	1.1
+++ wikisrc/ports/vax-models.mdwn	17 Jan 2014 23:55:28 -0000	1.2
@@ -1,5 +1,6 @@
-Notes on System Models
-======================
+[[!meta title="NetBSD/vax Notes on System Models"]]
+
+# Notes on System Models
 
 Starting in the mid-late 1980's, most VAX systems were based on VAX
 microprocessors (the exceptions were the VAX 9000 and all VAX 8xxx
@@ -27,42 +28,24 @@
     the fastest of all VAX systems, the VAX 7000 model 800. It was used
     in the VAX 6000 model 600, all VAX 7000 and VAX 10000 systems, all
     VAX 4000 systems except for the (already mentioned) models 200 and
-    300, MicroVAX 3100 model 9x, and VAXstation 4000 models 90, 90A, and
-    96.
+    300, MicroVAX 3100 model 9x, and VAXstation 4000 models 90, 90A, and 96.
 
 * * * * *
 
-Contents
---------
+# Contents
 
 These are a few of the many systems that NetBSD/vax supports.
 
--   [VAX-11/780 Systems](#star)
--   [VAX-11/750 System](#comet)
--   [VAX 8600 and 8650 Systems](#venus)
--   [VAX 8200-family Systems](#scorpio)
--   [MicroVAX II and MicroVAX III Systems](#mayflower)
--   [MicroVAX 3200, 3300, 3400 and 3500 Systems](#mayfair)
--   [MicroVAX 3600, 3800 and 3900 Systems](#mayfair2)
--   [VAXstation 2000/MicroVAX 2000 Systems](#vaxstar)
--   [MicroVAX 3100 Systems](#teammate2)
--   [VAXstation 3100 Systems](#pvax)
--   [VAXstation 4000/VLC](#pvax2)
--   [VAXstation 4000 model 60](#pmariah)
--   [MicroVAX 3100 model 80](#waverley)
--   [VAXstation 4000 model 90](#cougar)
--   [VAX 4000/200 Systems](#spitfire)
--   [VAX 4000/300 Systems](#pele)
+[[!toc startlevel=1 levels=2]]
 
 * * * * *
 
-VAX-11/780 Systems
-------------------
+# VAX-11/780 Systems<a name="star"></a>
 
 CPU-specific support for the VAX-11/780 family of systems originates
 from 4.4BSD, and was modified for NetBSD by Anders Magnusson.
 
-### Supported Hardware
+## Supported Hardware
 
 The VAX-11/780 family is Digital's oldest VAX product, it was initially
 announced in 1977. It includes the following models:
@@ -96,22 +79,21 @@
 for these unsupported devices are unlikely to ever be written.*
 
 NetBSD/vax also supports devices that can be connected to both the
-Unibus and Massbus, as described on the [Massbus](massbus.html) and
-[Unibus](unibus.html) hardware support pages.
+Unibus and Massbus, as described on the [Massbus](http://www.NetBSD.org/ports/vax/massbus.html) and
+[Unibus](http://www.NetBSD.org/ports/vax/unibus.html) hardware support pages.
 
-### Known Bugs for the VAX-11/780 port:
+## Known Bugs for the VAX-11/780 port:
 
 -   NetBSD/vax can only use one CPU on multi-CPU machines
 
 * * * * *
 
-VAX-11/750 System
------------------
+# VAX-11/750 System<a name="comet"></a>
 
 CPU-specific support for the VAX-11/750 originates from 4.4BSD, and was
 modified for NetBSD by Anders Magnusson.
 
-### Supported Hardware
+## Supported Hardware
 
 The VAX-11/750 minicomputer was announced in 1981. It was sold as a
 cheaper variant of the expensive VAX-11/780 systems.
@@ -135,23 +117,22 @@
 for the CI750 is unlikely to ever be written.*
 
 NetBSD/vax also supports devices that can be connected to both the
-Unibus and Massbus, as described on the [Massbus](massbus.html) and
-[Unibus](unibus.html) hardware support pages.
+Unibus and Massbus, as described on the [Massbus](http://www.NetBSD.org/ports/vax/massbus.html) and
+[Unibus](http://www.NetBSD.org/ports/vax/unibus.html) hardware support pages.
 
-### Known Bugs for the VAX-11/750 port:
+## Known Bugs for the VAX-11/750 port:
 
 -   The TU58 can only read tapes, and sometimes hangs the machine when
     accessed.
 
 * * * * *
 
-VAX 8600 and 8650 Systems
--------------------------
+# VAX 8600 and 8650 Systems<a name="venus"></a>
 
 CPU-specific support for the VAX 8600 family of systems originates from
 4.4BSD, and was modified for NetBSD by Anders Magnusson.
 
-### Supported Hardware
+## Supported Hardware
 
 The VAX 8600 was announced in 1984 as a successor of the VAX-11/785. It
 uses the same system bus as the VAX-11/780. The models are:
@@ -174,18 +155,17 @@
 -   CI780 Computer Interconnect adapter
 
 NetBSD/vax also supports devices that can be connected to both the
-Unibus and Massbus, as described on the [Massbus](massbus.html) and
-[Unibus](unibus.html) hardware support pages.
+Unibus and Massbus, as described on the [Massbus](http://www.NetBSD.org/ports/vax/massbus.html) and
+[Unibus](http://www.NetBSD.org/ports/vax/unibus.html) hardware support pages.
 
 * * * * *
 
-VAX 8200-family Systems
------------------------
+# VAX 8200-family Systems<a name="scorpio"></a>
 
 CPU-specific support for the VAX 8200 family of systems originates from
 4.4BSD, and was modified for NetBSD by Anders Magnusson.
 
-### Supported Hardware
+## Supported Hardware
 
 The VAX 8200 family was announced in 1984. It was the low-end of VAX
 systems to support the new BI bus. The family includes the following
@@ -202,22 +182,21 @@
 console media.
 
 NetBSD/vax also supports devices that can be connected to the BI bus, as
-described on the [BI bus](bibus.html) support page.
+described on the [BI bus](http://www.NetBSD.org/ports/vax/bibus.html) support page.
 
-### Known Bugs for the VAX 8200 port:
+## Known Bugs for the VAX 8200 port:
 
 -   NetBSD/vax can only make use of one CPU on multi-CPU machines
 
 * * * * *
 
-MicroVAX II and MicroVAX III Systems
-------------------------------------
+# MicroVAX II and MicroVAX III Systems<a name="mayflower"></a>
 
 CPU-specific support for the MicroVAX II and MicroVAX III systems
 originates from 4.4BSD. MicroVAX II was ported to NetBSD by Rick
 Macklem, and MicroVAX III was ported by Anders Magnusson.
 
-### Supported Hardware
+## Supported Hardware
 
 The MicroVAX II was based on the first one-chip VAX, the 78032. It was
 the successor to the MicroVAX I. In fact, at the time the 78032 was the
@@ -236,14 +215,13 @@
 -   RD5x disk attached to the Q bus
 
 NetBSD/vax also supports devices that can be connected to the Q-bus as
-described on the [Q-bus](qbus.html) hardware support page.
+described on the [Q-bus](http://www.NetBSD.org/ports/vax/qbus.html) hardware support page.
 
 * * * * *
 
-MicroVAX 3200, 3300, 3400 and 3500 Systems
-------------------------------------------
+# MicroVAX 3200, 3300, 3400 and 3500 Systems<a name="mayfair"></a>
 
-### Supported Hardware
+## Supported Hardware
 
 The MicroVAX 3200, 3300, 3400 and 3500 have a motherboard with a Q bus
 adapter attached to it. On the board the following devices may be
@@ -260,23 +238,22 @@
 -   SII DSSI adapter
 
 NetBSD/vax also supports devices that can be connected to the Q-bus as
-described on the [Q-bus](qbus.html) hardware support page.
+described on the [Q-bus](http://www.NetBSD.org/ports/vax/qbus.html) hardware support page.
 
-### Known Bugs for the MicroVAX 3500 port:
+## Known Bugs for the MicroVAX 3500 port:
 

(Diff truncated)
Add a comment