Recent changes to this wiki:

fix typo in previous, and fold another line.
Index: wikisrc/ports/sparc64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:34:56 -0000	1.7
+++ wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:38:30 -0000	1.8
@@ -18,8 +18,7 @@
 low level kernel groveling tools. Additionally, NetBSD/sparc64 is able to run
 Solaris 64 and 32 bit binaries with emulation. See
 [compat_netbsd32(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_netbsd32+8+NetBSD-5.1+i386),
-[compat_solaris(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_solaris+8+NetBSD-5.1+i386) and the pkgsrc package [`emulators/netbs
-d32_compat16`](http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/netbsd32_compat16/README.html).
+[compat_solaris(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_solaris+8+NetBSD-5.1+i386) and the pkgsrc package [`emulators/netbsd32_compat16`](http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/netbsd32_compat16/README.html).
 
 Martin Husemann is the maintainer for NetBSD/sparc64.
 """
@@ -80,7 +79,7 @@
 * For older 32 bit SPARC-based machines, see [NetBSD/sparc](../sparc/).
 * [NetBSD/sparc64 FAQ](http://www.NetBSD.org/ports/sparc64/faq.html)
 * [Notes on System Models](http://www.NetBSD.org/ports/sparc64/models.html)
-* [NetBSD/sparc64 History](http://www.NetBSD.org/ports/sparct64/history.html)
+* [NetBSD/sparc64 History](http://www.NetBSD.org/ports/sparc64/history.html)
 * The [NetBSD Diskless HOWTO](http://www.NetBSD.org/docs/network/netboot/)
 * [Developers and Development Funding](http://www.NetBSD.org/ports/sparc64/development.html)
 * [NetBSD/sparc64 Projects](http://www.NetBSD.org/ports/sparc64/projects.html)

fix a bunch more links that got broken in the conversion to wikisrc,
prompted by a comment i just noticed (thanks, gareth!)
while here, fold some lines (uh...) to fix manpage links and update
text to reflect the fact that petrov is no longer around.
Members: 
	ports/sparc64.mdwn:1.6->1.7 

Index: wikisrc/ports/sparc64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:17:12 -0000	1.6
+++ wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:34:56 -0000	1.7
@@ -7,7 +7,7 @@
 thumbnail="http://www.netbsd.org/images/ports/sparc64/e250u10.gif"
 about="""
 NetBSD/sparc64 is a NetBSD port to Sun's 64-bit UltraSPARC machines. The first
-binary release for sparc64 was [NetBSD 1.5](../../releases/formal-1.5/).
+binary release for sparc64 was [NetBSD 1.5](http://www.NetBSD.org/releases/formal-1.5/).
 NetBSD/sparc64 supports many systems, including Sbus-based UltraSPARC systems
 and PCI-based UltraSPARC systems using UltraSPARC I, II, IIi, and IIe CPU
 types.
@@ -17,14 +17,11 @@
 support for running most 32-bit binaries as well, with the exception of some
 low level kernel groveling tools. Additionally, NetBSD/sparc64 is able to run
 Solaris 64 and 32 bit binaries with emulation. See
-[compat_netbsd32(8)](http://netbsd.gw.com/cgi-bin/man-
-cgi?compat_netbsd32+8+NetBSD-5.1+i386),
-[compat_solaris(8)](http://netbsd.gw.com/cgi-bin/man-
-cgi?compat_solaris+8+NetBSD-5.1+i386) and the pkgsrc package [`emulators/netbs
-d32_compat16`](http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/netbs
-d32_compat16/README.html).
+[compat_netbsd32(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_netbsd32+8+NetBSD-5.1+i386),
+[compat_solaris(8)](http://netbsd.gw.com/cgi-bin/man-cgi?compat_solaris+8+NetBSD-5.1+i386) and the pkgsrc package [`emulators/netbs
+d32_compat16`](http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/emulators/netbsd32_compat16/README.html).
 
-Martin Husemann and Andrey Petrov are the maintainers for NetBSD/sparc64.
+Martin Husemann is the maintainer for NetBSD/sparc64.
 """
 supported_hardware="""
 Clones based on any of these systems should also work
@@ -65,9 +62,9 @@
 * All on-board parallel ports 
 * Most input devices (keyboards, mice, trackballs). 
 * Audio 
-* Most Machine-independent [SBUS cards](../../support/hardware/sbus.html)
-* Most Machine-independent [PCI cards](../../support/hardware/pci.html)
-* Most Machine-independent [USB device](../../support/hardware/usb.html)
+* Most Machine-independent [SBUS cards](http://www.NetBSD.org/support/hardware/sbus.html)
+* Most Machine-independent [PCI cards](http://www.NetBSD.org/support/hardware/pci.html)
+* Most Machine-independent [USB device](http://www.NetBSD.org/support/hardware/usb.html)
 * FireWire 
 """
 unsupported_hardware="""
@@ -78,16 +75,16 @@
 """
 additional="""
 For frequently asked questions and links to Sun hardware information, see the
-[NetBSD/sparc64 FAQ](faq.html).
+[NetBSD/sparc64 FAQ](http://www.NetBSD.org/ports/sparc64/faq.html).
 
 * For older 32 bit SPARC-based machines, see [NetBSD/sparc](../sparc/).
-* [NetBSD/sparc64 FAQ](faq.html)
-* [Notes on System Models](models.html)
-* [NetBSD/sparc64 History](history.html)
-* The [NetBSD Diskless HOWTO](../../docs/network/netboot/)
-* [Developers and Development Funding](development.html)
-* [NetBSD/sparc64 Projects](projects.html)
-* [Running NetBSD on emulated hardware](../emulators.html)
+* [NetBSD/sparc64 FAQ](http://www.NetBSD.org/ports/sparc64/faq.html)
+* [Notes on System Models](http://www.NetBSD.org/ports/sparc64/models.html)
+* [NetBSD/sparc64 History](http://www.NetBSD.org/ports/sparct64/history.html)
+* The [NetBSD Diskless HOWTO](http://www.NetBSD.org/docs/network/netboot/)
+* [Developers and Development Funding](http://www.NetBSD.org/ports/sparc64/development.html)
+* [NetBSD/sparc64 Projects](http://www.NetBSD.org/ports/sparc64/projects.html)
+* [Running NetBSD on emulated hardware](http://www.NetBSD.org/ports/emulators.html)
 """
 ]]
 [[!tag tier1port]]

fix link to "notes on system models" that was broken in the wikification.
XXX this is now a direct link to the htdocs version. ideally that page
should be wikified.
Index: wikisrc/ports/sparc64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/sparc64.mdwn	6 Oct 2014 21:41:29 -0000	1.5
+++ wikisrc/ports/sparc64.mdwn	25 Mar 2015 20:17:12 -0000	1.6
@@ -48,7 +48,7 @@
 * SPARCengine Ultra AXi family (Netra X1, Fire v100, Fire v120, Netra 120, Netra AC 200, Netra DC 200) 
 * SPARCengine Ultra AXe system board 
 
-See the [Notes on System Models](models.html) page for a complete list.
+See the [Notes on System Models](http://www.NetBSD.org/ports/sparc64/models.html) page for a complete list.
 
 ### All on-board and most optional Sun brand framebuffers 
 

Index: wikisrc/users/billc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/billc.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/billc.mdwn	20 Mar 2015 00:45:34 -0000	1.2
+++ wikisrc/users/billc.mdwn	25 Mar 2015 00:52:41 -0000	1.3
@@ -4,3 +4,20 @@
 @Cryo on Twitter
 Cryo on irc.freenode.net
 Cryo+ on plus.google.com
+
+
+==Experience of getting NetBSD-7 running on eeepc900==
+
+VERY IMPORTANT
+*Can not configure network with WIFI with sysinst during install.  Configure network will not use wpa_supplicant or wiconfig and
+does not differentiate between ethernet in WIFI in displaying interfaces.  This gives a false impression that if you configure ath0
+that it will ask for SSID, Encryption Type, and Password and generate /etc/wpa_supplicant.conf as well as add the necessary
+parts to rc.conf.  The fact that wpa_supplicant can't accept this information from the command line and requires a conf file may
+be part of the problem.
+
+IMPORTANT
+*DRMKMS kernel will choose other display, I guess, because the LCD will go black or weird fade to black.
+
+NOT IMPORTANT
+*SDCard class 10, seems rather slow on the USB bus, like slower than on other OS I have run on it... is this not enough wakeups
+on the USB driver?

Use mainline U-Boot for A31
Index: wikisrc/ports/evbarm/allwinner.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/allwinner.mdwn,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- wikisrc/ports/evbarm/allwinner.mdwn	3 Feb 2015 10:11:59 -0000	1.47
+++ wikisrc/ports/evbarm/allwinner.mdwn	23 Mar 2015 18:46:00 -0000	1.48
@@ -71,8 +71,7 @@
 
 * Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *beagleboard.img*
 * Download a U-Boot build for your board
-  * A10/A20: Download from the linux-sunxi web site <http://dl.linux-sunxi.org/nightly/u-boot-sunxi/u-boot-sunxi-mainline/u-boot-sunxi-mainline-latest/>
-  * A31: The standard u-boot-sunxi tree doesn't support A31 yet. Until sun6i support is merged, a build is available at <http://www.invisible.ca/allwinner/a31/> 
+  * Download the correct build from the linux-sunxi web site <http://dl.linux-sunxi.org/nightly/u-boot-sunxi/u-boot-sunxi-mainline/u-boot-sunxi-mainline-latest/>.
 * Write the *u-boot-sunxi-with-spl.bin* loader to the empty space at the start of the base image:
 [[!template  id=programlisting text="""
 # dd if=u-boot-sunxi-with-spl.bin of=beagleboard.img bs=1k seek=8 conv=notrunc

Add RTC to supported hardware list
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 16:35:35 -0000	1.10
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 17:36:52 -0000	1.11
@@ -17,6 +17,7 @@
  - Gigabit Ethernet (GMAC)
    - RTL8211F PHY
  - Hardware random number generator
+ - RTC
 
 # TODO
  - USB device mode

Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 16:31:34 -0000	1.9
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 16:35:35 -0000	1.10
@@ -110,6 +110,10 @@
 
 # HDMI
 
+## Framebuffer console
+
+Simply add **console=fb** to the *bootargs* variable in *boot.ini*.
+
 ## Video mode
 
 HDMI video mode can be selected in U-Boot with the *video* command, e.g.:

Add video mode section
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 14:01:40 -0000	1.8
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 16:31:34 -0000	1.9
@@ -67,14 +67,10 @@
 """]]
 * Write the image to an SD card.
 * Copy the kernel (netbsd.ub) for your board to the root of the MS-DOS partition on the SD card.
-* Create or edit boot.ini on the MS-DOS partition:
+* Create or edit *boot.ini* on the MS-DOS partition:
 [[!template  id=programlisting text="""
 ODROIDC-UBOOT-CONFIG
 
-setenv m "1080p"
-setenv vout_mode "hdmi"
-setenv m_bpp "32"
-setenv disableuhs "disableuhs"
 setenv bootargs "root=ld0f awge0.mac-address=${ethaddr}"
 setenv bootcmd "fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
 run bootcmd
@@ -112,7 +108,23 @@
 # reboot
 """]]
 
-# Overscan compensation
+# HDMI
+
+## Video mode
+
+HDMI video mode can be selected in U-Boot with the *video* command, e.g.:
+
+[[!template  id=programlisting text="""
+odroidc#video dev open 1080P
+"""]]
+
+To make this change permanent, add it to the *bootcmd* variable in *boot.ini*:
+
+[[!template  id=programlisting text="""
+setenv bootcmd "video dev open 1080P; fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
+"""]]
+
+## Overscan compensation
 
 If you have ODROID-C1 plugged into a TV, the edges of the screen may not be visible. You can scale down the framebuffer console with the **hw.genfb0.scale** sysctl, e.g.:
 

Added a comment: NetBSD error
--- /dev/null	2015-03-22 14:32:00.000000000 +0000
+++ wikisrc/ports/evbarm/raspberry_pi/comment_5_e342e8f4927d08f4a1f9e22df21d1930._comment	2015-03-22 14:37:57.000000000 +0000
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmuLc-YNA2_8q6AkCIS1Ca0eims4YukCvw"
+ nickname="Youri"
+ subject="NetBSD error"
+ date="2015-03-22T14:36:38Z"
+ content="""
+if you get the following error while trying to fetch sets;
+
+ftp: Can't LOOKUP `nyftp.NetBSD.org:http': Temporary failure in name resolution
+
+
+Please use the nyftp's IP address instead: 128.59.23.63
+
+As reported by http://stackoverflow.com/questions/27690637/installing-netbsd-sets-via-http-on-raspberry-pi-fails
+"""]]

Overscan compensation
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/evbarm/odroid-c1.mdwn	21 Mar 2015 10:56:12 -0000	1.7
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	22 Mar 2015 14:01:40 -0000	1.8
@@ -112,6 +112,18 @@
 # reboot
 """]]
 
+# Overscan compensation
+
+If you have ODROID-C1 plugged into a TV, the edges of the screen may not be visible. You can scale down the framebuffer console with the **hw.genfb0.scale** sysctl, e.g.:
+
+[[!template  id=programlisting text="""
+# sysctl -w hw.genfb0.scale=95
+"""]]
+
+Setting *scale* to 100 disables scaling, any other value enables the scaler. Values between 10 and 100 are allowed.
+
+To set this value at boot, you can add **fb.scale=95** to the kernel cmdline options in *boot.ini*.
+
 # ODROID-C1 UART pins
 
 From [ODROID Forum](http://forum.odroid.com/viewtopic.php?f=115&t=7684):

Framebuffer console is supported
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports/evbarm/odroid-c1.mdwn	16 Mar 2015 21:42:59 -0000	1.6
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	21 Mar 2015 10:56:12 -0000	1.7
@@ -12,6 +12,7 @@
  - A5 global timer
  - SD/MMC controller (DMA)
  - Serial console
+ - Framebuffer console
  - USB host (OTG)
  - Gigabit Ethernet (GMAC)
    - RTL8211F PHY
@@ -21,10 +22,10 @@
  - USB device mode
  - Simultaneous SD card and eMMC usage
  - SD/MMC UHS-I support (needs sdmmc(4) changes)
- - HDMI / framebuffer
  - IR receiver
  - GPIO
  - I2C
+ - Audio
 
 # Installation
 

Index: wikisrc/users/billc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/billc.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/billc.mdwn	4 Jul 2010 13:28:25 -0000	1.1
+++ wikisrc/users/billc.mdwn	20 Mar 2015 00:45:34 -0000	1.2
@@ -1,3 +1,6 @@
 Otherwise known as &quot;Cryo&quot;.
 
 <http://cryo.ws>
+@Cryo on Twitter
+Cryo on irc.freenode.net
+Cryo+ on plus.google.com

Mention rpi2
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/ports/evbarm.mdwn	16 Mar 2015 21:42:15 -0000	1.16
+++ wikisrc/ports/evbarm.mdwn	18 Mar 2015 18:54:55 -0000	1.17
@@ -205,8 +205,8 @@
  * Other devices inserted into the PCI/mPCI slot
  * On-chip watchdog timer (_ixpwdog_)
 
-### Raspberry Pi Foundation **Raspberry Pi**
-The [[Raspberry Pi]] is a low-cost credit-card-sized computer from the Raspberry Pi Foundation.
+### Raspberry Pi Foundation **Raspberry Pi**/**Raspberry Pi 2**
+The [[Raspberry Pi]] is a low-cost credit-card-sized computer from the Raspberry Pi Foundation. Both the Raspberry Pi and Raspberry Pi 2 are supported.
 
 ### Rockchip PX2/RK3066/RK3188/RK3188+
 Various [[Rockchip]] family SoCs are supported by the ROCKCHIP kernel.

RPI2 is part of NetBSD 7 now
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.37
retrieving revision 1.38
diff -u -r1.37 -r1.38
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Mar 2015 10:45:15 -0000	1.37
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	18 Mar 2015 18:52:45 -0000	1.38
@@ -10,8 +10,7 @@
 
 # Installation
  - You may use the rpi.img file created by an evbarm build - evbarm-earmv6hf is recommended. This isn't optimized for Raspberry Pi 2, but allows a single image to be used for all boards.
-   - The Raspberry Pi port will be part of the NetBSD 7 release.
-   - The Raspberry Pi 2 port is only in HEAD at present.
+   - The Raspberry Pi and Pi 2 ports will be part of the NetBSD 7 release.
    - The automatic nightly builds can be found in the 'evbarm-earmv6hf/binary/gzimg/' directory on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).
      - The stable build will be under netbsd-7/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/
      - The HEAD/current build will be under HEAD/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/

add another page that needs updating
Index: wikisrc/releng/release-prep.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/release-prep.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/releng/release-prep.mdwn	24 Jan 2015 07:49:06 -0000	1.18
+++ wikisrc/releng/release-prep.mdwn	17 Mar 2015 05:10:22 -0000	1.19
@@ -151,6 +151,7 @@
     - Update htdocs/releases/formal-&lt;blah&gt;/index.xml
     - Update htdocs/mirrors/torrents/
     - Update htdocs/releases/formal.xml
+    - Update htdocs/about/history.xml
     - Top-level regen of everything
     - Update htdocs/changes/index.xml
     - Update htdocs/index.html

Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 15:48:58 -0000	1.5
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	16 Mar 2015 21:42:59 -0000	1.6
@@ -3,7 +3,7 @@
 [[!toc levels=2]]
 
 # Supported hardware
- - CPU: Cortex-A5: S805 (4-core) at 1.5GHz
+ - CPU: Cortex-A5: Amlogic S805 (4-core) at 1.5GHz
    - CPU frequency scaling is supported with machdep.cpu sysctl tree
    - SMP supported
    - PL310 L2 cache controller

xref odroid-c1
Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/ports/evbarm.mdwn	5 Jan 2015 11:05:36 -0000	1.15
+++ wikisrc/ports/evbarm.mdwn	16 Mar 2015 21:42:15 -0000	1.16
@@ -110,6 +110,10 @@
  * GPSstix (GPS not test)
  * tweener
 
+### Hardkernel ODROID-C1
+
+The [[ODROID-C1]] is a quad core Cortex-A5 small form-factor board from Hardkernel co., Ltd.
+
 ### Intel **DBPXA250** ("Lubbock") 
 
 DBPXA250 (a.k.a. Lubbock) is an evaluation and development platform for the

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	14 Mar 2015 13:57:21 -0000	1.18
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	16 Mar 2015 07:20:41 -0000	1.19
@@ -9,7 +9,7 @@
 First Last | `login@` | comment(s)
 Bernd Ernesti | `veego` |
 David Maxwell | `david` |
-Hiroki Suenaga | `hsuenaga` |
+Jun Ebihara | `jun` |
 Justin Cormack | `justin` |
 Kengo Nakahara | `knakahara` |
 Kenichi Hashimoto | `hkenken` | will be late.

alphabetical order by name
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	14 Mar 2015 13:54:20 -0000	1.17
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	14 Mar 2015 13:57:21 -0000	1.18
@@ -16,12 +16,12 @@
 Kimihiro NONAKA | `nonaka` |
 Makoto Fujiwara | `mef` |
 Masanobu SAITOH | `msaitoh` |
+Masao Uebayashi | `uebayasi` |
 Masaru OKI | `oki` |
 Martin Husemann | `martin` |
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |
 Taylor R Campbell | `riastradh` |
-Masao Uebayashi | `uebayasi` |
 """]]
 
 ## Planning to present something?

Added uebayasi.
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	11 Mar 2015 13:10:53 -0000	1.16
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	14 Mar 2015 13:54:20 -0000	1.17
@@ -21,6 +21,7 @@
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |
 Taylor R Campbell | `riastradh` |
+Masao Uebayashi | `uebayasi` |
 """]]
 
 ## Planning to present something?

adjust PAE comments
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.100
retrieving revision 1.101
diff -u -r1.100 -r1.101
--- wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:29:11 -0000	1.100
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 23:40:07 -0000	1.101
@@ -140,10 +140,10 @@
 should in theory work.  An amd64 xen/dom0 is known to support both
 i386 and amd64 domUs.
 
-Except for an odd case with Xen 3.1, i386 dom0 and domU kernels must
-be PAE; these are built by default.  (Note that emacs (at least) fails
-if run on i386 with PAE when built without, and vice versa, presumably
-due to bugs in the undump code.)
+i386 dom0 and domU kernels must be PAE (except for Xen 3.1); these are
+built by default.  (Note that emacs (at least) fails if run on i386
+with PAE when built without, and vice versa, presumably due to bugs in
+the undump code.)
 
 Because of the above, the standard approach is to use amd64 for the
 dom0.

Tweak previous
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -r1.99 -r1.100
--- wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:27:36 -0000	1.99
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:29:11 -0000	1.100
@@ -149,8 +149,9 @@
 dom0.
 
 Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify
-if this is about the CPU having to be amd64, or about the dom0 kernel
-having to be amd64.
+if this is about the CPU, the xen kernel, or the dom0 kernel having to
+be amd64.
+
 
 Stability
 ---------

Explain the i386/amd64 situation more clearly and more accurately.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -r1.98 -r1.99
--- wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:21:22 -0000	1.98
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:27:36 -0000	1.99
@@ -130,20 +130,28 @@
 ------------
 
 Xen itself can run on i386 or amd64 machines.  (Practically, almost
-any computer where one would want to run Xen supports amd64.)  If
-using an i386 NetBSD kernel for the dom0, PAE is required (PAE
-versions are built by default).  While i386 dom0 works fine, amd64 is
-recommended as more normal.
+any computer where one would want to run Xen today supports amd64.)
+
+Xen, the dom0 kernel, and each domU kernel can be either i386 or
+amd64.  When building a xenkernel package, one obtains i386 on an i386
+host, and amd64 on an amd64 host.  If the xen kernel is i386, then the
+dom0 kernel and all domU kernels must be i386.  With an amd64 xen
+kernel, an amd64 dom0 kernel is known to work, and an i386 dom0 kernel
+should in theory work.  An amd64 xen/dom0 is known to support both
+i386 and amd64 domUs.
+
+Except for an odd case with Xen 3.1, i386 dom0 and domU kernels must
+be PAE; these are built by default.  (Note that emacs (at least) fails
+if run on i386 with PAE when built without, and vice versa, presumably
+due to bugs in the undump code.)
+
+Because of the above, the standard approach is to use amd64 for the
+dom0.
 
 Xen 4.2 is the last version to support i386 as a host.  TODO: Clarify
 if this is about the CPU having to be amd64, or about the dom0 kernel
 having to be amd64.
 
-One can then run i386 domUs and amd64 domUs, in any combination.  If
-running an i386 NetBSD kernel as a domU, the PAE version is required.
-(Note that emacs (at least) fails if run on i386 with PAE when built
-without, and vice versa, presumably due to bugs in the undump code.)
-
 Stability
 ---------
 

fix spacing/tabs for literal text
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -r1.97 -r1.98
--- wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:20:17 -0000	1.97
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:21:22 -0000	1.98
@@ -533,7 +533,7 @@
 
 Older hardware:
 
-	Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2
+        Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2
 
 Running Xen under qemu
 ----------------------

Add some mobo/cpu combos
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.96
retrieving revision 1.97
diff -u -r1.96 -r1.97
--- wikisrc/ports/xen/howto.mdwn	11 Mar 2015 17:17:35 -0000	1.96
+++ wikisrc/ports/xen/howto.mdwn	12 Mar 2015 21:20:17 -0000	1.97
@@ -516,6 +516,24 @@
 correct set of daemons.  Ensure that the domU config files are valid
 for the new version.
 
+Hardware known to work
+----------------------
+
+Arguably, this section is misplaced, and there should be a page of
+hardware that runs NetBSD/amd64 well, with the mostly-well-founded
+assumption that NetBSD/xen runs fine on any modern hardware that
+NetBSD/amd64 runs well on.  Until then, we give motherboard/CPU/RAM
+triples to aid those choosing a motherboard.  Note that Xen systems
+usually do not run X, so a listing here does not imply that X works at
+all.
+
+        Supermicro X9SRL-F, Xeon E5-1650 v2, 96 GiB ECC
+        Supermicro ??, Atom C2758 (8 core), 32 GiB ECC
+        ASUS M5A78L-M/USB3 AM3+ microATX, AMD Piledriver X8 4000MHz, 16 GiB ECC
+
+Older hardware:
+
+	Intel D915GEV, Pentium4 CPU 3.40GHz, 4GB 533MHz Synchronous DDR2
 
 Running Xen under qemu
 ----------------------

Add XSA page.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -r1.95 -r1.96
--- wikisrc/ports/xen/howto.mdwn	5 Mar 2015 14:04:55 -0000	1.95
+++ wikisrc/ports/xen/howto.mdwn	11 Mar 2015 17:17:35 -0000	1.96
@@ -95,6 +95,8 @@
 xenkernel45 provides Xen 4.5.  This is new to pkgsrc as of 2015-01 and
 not yet recommended for other than experimental/testing use.
 
+See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
+
 Ideally newer versions of Xen will be added to pkgsrc.
 
 Note that NetBSD support is called XEN3.  It works with Xen 3 and Xen

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	11 Mar 2015 05:25:19 -0000	1.15
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	11 Mar 2015 13:10:53 -0000	1.16
@@ -30,7 +30,7 @@
 `all` | Self introduction (5minutes in each person)
 `msaitoh@` | New NetBSD developer candidates(10-15 minutes)
 `msaitoh@` | Current status and next step of MP capable network stack. (15 minutes?)
-`mef@` | (pkgsrc) New trial: Getting list of updated status (15 minutes)
+`mef@` | (pkgsrc) New trial: [Getting list of updated status](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html) (15 minutes)
 `login@` |_Very Interesting Thing_
 """]]
 

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/mef.mdwn	11 Mar 2015 13:03:40 -0000	1.5
+++ wikisrc/users/mef.mdwn	11 Mar 2015 13:06:33 -0000	1.6
@@ -1,3 +1,5 @@
 Makoto Fujiwara (pkgsrc)
 # project
 [check-update](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html)
+# PR not submitted
+# PR submitted or concerned

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/mef.mdwn	11 Mar 2015 13:02:03 -0000	1.4
+++ wikisrc/users/mef.mdwn	11 Mar 2015 13:03:40 -0000	1.5
@@ -1,2 +1,3 @@
 Makoto Fujiwara (pkgsrc)
-* [check-update](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html)
+# project
+[check-update](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html)

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/mef.mdwn	11 Mar 2015 13:00:53 -0000	1.3
+++ wikisrc/users/mef.mdwn	11 Mar 2015 13:02:03 -0000	1.4
@@ -1,2 +1,2 @@
 Makoto Fujiwara (pkgsrc)
-* [http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html](check-update)
+* [check-update](http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html)

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/mef.mdwn	11 Mar 2015 12:59:44 -0000	1.2
+++ wikisrc/users/mef.mdwn	11 Mar 2015 13:00:53 -0000	1.3
@@ -1,2 +1,2 @@
 Makoto Fujiwara (pkgsrc)
-* http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html[check-update]
+* [http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html](check-update)

Index: wikisrc/users/mef.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/mef.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/mef.mdwn	11 Mar 2015 12:58:04 -0000	1.1
+++ wikisrc/users/mef.mdwn	11 Mar 2015 12:59:44 -0000	1.2
@@ -1 +1,2 @@
 Makoto Fujiwara (pkgsrc)
+* http://www.ki.nu/~makoto/pkgsrc/check-update/00_Summary.html[check-update]

--- /dev/null	2015-03-11 12:50:01.000000000 +0000
+++ wikisrc/users/mef.mdwn	2015-03-11 12:58:08.000000000 +0000
@@ -0,0 +1 @@
+Makoto Fujiwara (pkgsrc)

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	9 Mar 2015 01:14:57 -0000	1.14
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	11 Mar 2015 05:25:19 -0000	1.15
@@ -9,7 +9,6 @@
 First Last | `login@` | comment(s)
 Bernd Ernesti | `veego` |
 David Maxwell | `david` |
-Hikaru Abe | `hikaru` |
 Hiroki Suenaga | `hsuenaga` |
 Justin Cormack | `justin` |
 Kengo Nakahara | `knakahara` |

Update qemu bug reference to refer to the sparc specific one.
Index: wikisrc/kernel_debugging_with_qemu.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/kernel_debugging_with_qemu.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/kernel_debugging_with_qemu.mdwn	19 Feb 2015 09:37:14 -0000	1.9
+++ wikisrc/kernel_debugging_with_qemu.mdwn	10 Mar 2015 07:36:40 -0000	1.10
@@ -31,8 +31,7 @@
 script.  The i386 port is the preferred test platform because the two
 other ports supported by anita are affected by known bugs: amd64 by
 [[PR 49276|http://gnats.NetBSD.org/49276]], and sparc by
-[[qemu bug 1335444|https://bugs.launchpad.net/qemu/+bug/1335444]].
-
+[[qemu bug 1399943|https://bugs.launchpad.net/qemu/+bug/1399943]].
 If you do the build in a directory other than /usr/src, 
 use the -fdebug-prefix-map option to ensure that the source file names embedded
 in the debug symbols point to /usr/src, which is where the sources will be

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Mar 2015 10:43:59 -0000	1.36
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Mar 2015 10:45:15 -0000	1.37
@@ -142,3 +142,4 @@
 
 # What needs work
  - USB (host); isochronous transfers.
+ - MULTIPROCESSOR support for Raspberry Pi 2

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	8 Feb 2015 21:10:46 -0000	1.35
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	9 Mar 2015 10:43:59 -0000	1.36
@@ -4,13 +4,14 @@
 
 [[!toc levels=2]]
 
-This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org).
+This page attempts to document and coordinate efforts towards NetBSD/evbarm on [Raspberry Pi](http://www.raspberrypi.org). All board variants are supported.
 
 <small>([Raspberry Pi image](http://www.flickr.com/photos/42325803@N07/8118758647/) by Christopher Lee used under CC-By-2.0 license)</small>
 
 # Installation
- - You may use the rpi.img file created by an evbarm build - evbarm-earmv6hf is recommended.
+ - You may use the rpi.img file created by an evbarm build - evbarm-earmv6hf is recommended. This isn't optimized for Raspberry Pi 2, but allows a single image to be used for all boards.
    - The Raspberry Pi port will be part of the NetBSD 7 release.
+   - The Raspberry Pi 2 port is only in HEAD at present.
    - The automatic nightly builds can be found in the 'evbarm-earmv6hf/binary/gzimg/' directory on [nyftp.netbsd.org](http://nyftp.netbsd.org/pub/NetBSD-daily/).
      - The stable build will be under netbsd-7/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/
      - The HEAD/current build will be under HEAD/YYYYMMDDHHMMZ/evbarm-earmv6hf/binary/gzimg/

Added a comment: Great job!
--- /dev/null	2015-03-09 05:50:01.000000000 +0000
+++ wikisrc/ports/evbarm/odroid-c1/comment_1_05bcc1009bf23342220dacdfe6e8dcc1._comment	2015-03-09 05:54:43.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnLCothbjAqByE8Ibp4T2U73QJAVPRvpQc"
+ nickname="Bo"
+ subject="Great job!"
+ date="2015-03-09T05:53:26Z"
+ content="""
+Really looking forward to the future of this port!  I'd love to build a fileserver with my C1 using NetBSD as the OS.
+"""]]

fix typo
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 22:37:14 -0000	1.13
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	9 Mar 2015 01:14:57 -0000	1.14
@@ -21,7 +21,7 @@
 Martin Husemann | `martin` |
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |
-Taylor R Campbell | `raiastradh` |
+Taylor R Campbell | `riastradh` |
 """]]
 
 ## Planning to present something?

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 18:21:19 -0000	1.12
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 22:37:14 -0000	1.13
@@ -8,6 +8,7 @@
 [[!table data="""
 First Last | `login@` | comment(s)
 Bernd Ernesti | `veego` |
+David Maxwell | `david` |
 Hikaru Abe | `hikaru` |
 Hiroki Suenaga | `hsuenaga` |
 Justin Cormack | `justin` |

Add NetBSD presentaion in work-in-progress session.
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 06:09:06 -0000	1.11
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 18:21:19 -0000	1.12
@@ -36,3 +36,4 @@
 
 ## Discussions
 * board voting procedure
+* NetBSD presentaion in work-in-progress session.

typo
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 15:44:02 -0000	1.4
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 15:48:58 -0000	1.5
@@ -78,7 +78,7 @@
 setenv bootcmd "fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
 run bootcmd
 """]]
-* On first boot, it will stopbecause of the wrong device in /etc/fstab. Take this opportunity to grow the root file-system:
+* On first boot, it will stop because of the wrong device in /etc/fstab. Take this opportunity to grow the root file-system:
 [[!template  id=programlisting text="""
 # fdisk -u ld0
 ...

Update ODROID-C1 installation instructions.
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 14:21:33 -0000	1.3
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 15:44:02 -0000	1.4
@@ -31,12 +31,39 @@
 * Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *beagleboard.img*
 * Build U-Boot for ODROID-C1 <https://github.com/hardkernel/u-boot/tree/odroidc-v2011.03>
   * Pre-built binaries here: <http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/odroidc1/u-boot-odroidc-v2011.03-20150308.tar.gz>
+* Note the location and size of the FFS partition in the *beagleboard.img* disklabel:
+[[!template  id=programlisting text="""
+# $TOOLDIR/bin/nbdisklabel -M evbarm -B le beagleboard.img
+...
+8 partitions:
+#        size    offset     fstype [fsize bsize cpg/sgs]
+ a:   1359312    385024     4.2BSD      0     0     0  # (Cyl.    188 -    851*)
+ b:    262144    122880       swap                     # (Cyl.     60 -    187)
+ c:   1744336         0     unused      0     0        # (Cyl.      0 -    851*)
+ d:   1744336         0     unused      0     0        # (Cyl.      0 -    851*)
+ e:    114688      8192      MSDOS                     # (Cyl.      4 -     59)
+"""]]
 * Write the bootloader to the empty space at the start of the base image:
 [[!template  id=programlisting text="""
 # dd if=bl1.bin.hardkernel of=beagleboard.img bs=1 count=442 conv=notrunc
 # dd if=bl1.bin.hardkernel of=beagleboard.img bs=512 skip=1 seek=1 conv=notrunc
 # dd if=u-boot.bin of=beagleboard.img bs=512 seek=64 conv=notrunc
 """]]
+* Since the bootloader has overwritten the disklabel, we need to re-add partition "a" from the disklabel to the MBR partition table:
+[[!template  id=programlisting text="""
+# $TOOLDIR/bin/armv7--netbsdelf-eabihf-fdisk -u beagleboard.img
+...
+Which partition do you want to change?: [none] 1
+The data for partition 1 is:
+<UNUSED>
+sysid: [0..255 default: 169] 
+start: [0..109cyl default: 63, 0cyl, 0MB] 385024
+size: [0..85cyl default: 1359312, 85cyl, 664MB] 1359312
+...
+Which partition do you want to change?: [none] 
+...
+Should we write new partition table? [n] y
+"""]]
 * Write the image to an SD card.
 * Copy the kernel (netbsd.ub) for your board to the root of the MS-DOS partition on the SD card.
 * Create or edit boot.ini on the MS-DOS partition:
@@ -47,11 +74,42 @@
 setenv vout_mode "hdmi"
 setenv m_bpp "32"
 setenv disableuhs "disableuhs"
-setenv bootargs "root=ld0a awge0.mac-address=${ethaddr}"
+setenv bootargs "root=ld0f awge0.mac-address=${ethaddr}"
 setenv bootcmd "fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
 run bootcmd
 """]]
-
+* On first boot, it will stopbecause of the wrong device in /etc/fstab. Take this opportunity to grow the root file-system:
+[[!template  id=programlisting text="""
+# fdisk -u ld0
+...
+Which partition do you want to change?: [none] 1
+The data for partition 1 is:
+NetBSD (sysid 169)
+    start 385024, size 1359312 (664 MB, Cyls 23/246/32-108/147/55)
+        PBR is not bootable: All bytes are identical (0x00)
+sysid: [0..255 default: 169]
+start: [0..966cyl default: 385024, 24cyl, 188MB]
+size: [0..942cyl default: 1359312, 85cyl, 664MB] $
+...
+Which partition do you want to change?: [none]
+...
+Should we write new partition table? [n] y
+# resize_ffs -y /dev/rld0f
+# reboot
+"""]]
+* Next boot, create a new /etc/fstab:
+[[!template  id=programlisting text="""
+# mount -u -o rw /dev/ld0f /
+# cat > /etc/fstab << EOF
+/dev/ld0f       /               ffs     rw      1 1
+/dev/ld0e       /boot           msdos   rw      1 1
+kernfs          /kern           kernfs  rw
+ptyfs           /dev/pts        ptyfs   rw
+procfs          /proc           procfs  rw
+tmpfs           /var/shm        tmpfs   rw,-m1777,-sram%25
+EOF
+# reboot
+"""]]
 
 # ODROID-C1 UART pins
 

Link to pre-build U-Boot binaries
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 13:34:37 -0000	1.2
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 14:21:33 -0000	1.3
@@ -30,6 +30,7 @@
 
 * Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *beagleboard.img*
 * Build U-Boot for ODROID-C1 <https://github.com/hardkernel/u-boot/tree/odroidc-v2011.03>
+  * Pre-built binaries here: <http://ftp.netbsd.org/pub/NetBSD/misc/jmcneill/odroidc1/u-boot-odroidc-v2011.03-20150308.tar.gz>
 * Write the bootloader to the empty space at the start of the base image:
 [[!template  id=programlisting text="""
 # dd if=bl1.bin.hardkernel of=beagleboard.img bs=1 count=442 conv=notrunc

ODROID-C1 installation notes, add supported hardware table and TODO list
Index: wikisrc/ports/evbarm/odroid-c1.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/odroid-c1.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/evbarm/odroid-c1.mdwn	27 Feb 2015 17:58:34 -0000	1.1
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	8 Mar 2015 13:34:37 -0000	1.2
@@ -2,6 +2,56 @@
 
 [[!toc levels=2]]
 
+# Supported hardware
+ - CPU: Cortex-A5: S805 (4-core) at 1.5GHz
+   - CPU frequency scaling is supported with machdep.cpu sysctl tree
+   - SMP supported
+   - PL310 L2 cache controller
+ - GIC
+ - A5 watchdog timer
+ - A5 global timer
+ - SD/MMC controller (DMA)
+ - Serial console
+ - USB host (OTG)
+ - Gigabit Ethernet (GMAC)
+   - RTL8211F PHY
+ - Hardware random number generator
+
+# TODO
+ - USB device mode
+ - Simultaneous SD card and eMMC usage
+ - SD/MMC UHS-I support (needs sdmmc(4) changes)
+ - HDMI / framebuffer
+ - IR receiver
+ - GPIO
+ - I2C
+
+# Installation
+
+* Start with an ARMv7 image from *evbarm-earmv7hf/binary/gzimg/* such as *beagleboard.img*
+* Build U-Boot for ODROID-C1 <https://github.com/hardkernel/u-boot/tree/odroidc-v2011.03>
+* Write the bootloader to the empty space at the start of the base image:
+[[!template  id=programlisting text="""
+# dd if=bl1.bin.hardkernel of=beagleboard.img bs=1 count=442 conv=notrunc
+# dd if=bl1.bin.hardkernel of=beagleboard.img bs=512 skip=1 seek=1 conv=notrunc
+# dd if=u-boot.bin of=beagleboard.img bs=512 seek=64 conv=notrunc
+"""]]
+* Write the image to an SD card.
+* Copy the kernel (netbsd.ub) for your board to the root of the MS-DOS partition on the SD card.
+* Create or edit boot.ini on the MS-DOS partition:
+[[!template  id=programlisting text="""
+ODROIDC-UBOOT-CONFIG
+
+setenv m "1080p"
+setenv vout_mode "hdmi"
+setenv m_bpp "32"
+setenv disableuhs "disableuhs"
+setenv bootargs "root=ld0a awge0.mac-address=${ethaddr}"
+setenv bootcmd "fatload mmc 0:1 0x21000000 netbsd.ub; bootm 0x21000000"
+run bootcmd
+"""]]
+
+
 # ODROID-C1 UART pins
 
 From [ODROID Forum](http://forum.odroid.com/viewtopic.php?f=115&t=7684):

Add mef's presentation
Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	7 Mar 2015 11:09:23 -0000	1.10
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	8 Mar 2015 06:09:06 -0000	1.11
@@ -30,6 +30,7 @@
 `all` | Self introduction (5minutes in each person)
 `msaitoh@` | New NetBSD developer candidates(10-15 minutes)
 `msaitoh@` | Current status and next step of MP capable network stack. (15 minutes?)
+`mef@` | (pkgsrc) New trial: Getting list of updated status (15 minutes)
 `login@` |_Very Interesting Thing_
 """]]
 

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	7 Mar 2015 11:01:55 -0000	1.9
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	7 Mar 2015 11:09:23 -0000	1.10
@@ -27,6 +27,7 @@
 
 [[!table data="""
 Speaker  |Title
+`all` | Self introduction (5minutes in each person)
 `msaitoh@` | New NetBSD developer candidates(10-15 minutes)
 `msaitoh@` | Current status and next step of MP capable network stack. (15 minutes?)
 `login@` |_Very Interesting Thing_

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 08:21:35 -0000	1.8
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	7 Mar 2015 11:01:55 -0000	1.9
@@ -1,7 +1,7 @@
 ## Details
 
 The NetBSD developer summit at AsiaBSDCon 2015 will be held Friday,
-09:30-12:30, March 13th.
+09:30-13:00, March 13th. Room E (see [here. The room is at "K"](http://2015.asiabsdcon.org/access.html.en))
 
 ## Planning to attend?
 
@@ -12,6 +12,7 @@
 Hiroki Suenaga | `hsuenaga` |
 Justin Cormack | `justin` |
 Kengo Nakahara | `knakahara` |
+Kenichi Hashimoto | `hkenken` | will be late.
 Kimihiro NONAKA | `nonaka` |
 Makoto Fujiwara | `mef` |
 Masanobu SAITOH | `msaitoh` |

Added a comment
--- /dev/null	2015-03-05 15:32:00.000000000 +0000
+++ wikisrc/pkgsrc/pkgsrc_64bit_osx/comment_3_40bf7235d6c6a251f28f6d9552ca2771._comment	2015-03-05 15:39:04.000000000 +0000
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawmW1g3pl05-P8w5AZNgCwrog-duzcDWucc"
+ nickname="Doug"
+ subject="comment 3"
+ date="2015-03-05T15:37:44Z"
+ content="""
+Thanks, Andrew. That worked.
+"""]]

Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/projects/gsoc.mdwn	17 Feb 2015 01:14:35 -0000	1.17
+++ wikisrc/projects/gsoc.mdwn	5 Mar 2015 14:43:23 -0000	1.18
@@ -10,8 +10,7 @@
 [2010](http://blog.netbsd.org/tnf/entry/google_summer_of_code_2010),
 [2011](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of),
 [2012](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of1),
-[2013](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2)) and
-we are hoping to once again participate as a mentoring organization in 2015.
+[2013](http://blog.netbsd.org/tnf/entry/netbsd_s_google_summer_of2)).
 
 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

Miscellaneous minor edits.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.94
retrieving revision 1.95
diff -u -r1.94 -r1.95
--- wikisrc/ports/xen/howto.mdwn	5 Mar 2015 13:38:10 -0000	1.94
+++ wikisrc/ports/xen/howto.mdwn	5 Mar 2015 14:04:55 -0000	1.95
@@ -761,7 +761,7 @@
 
         i386 XEN3_DOMU
         i386 XEN3PAE_DOMU
-	amd64 XEN3_DOMU
+        amd64 XEN3_DOMU
 
 Unless using Xen 3.1 (and you shouldn't) with i386-mode Xen, you must
 use the PAE version of the i386 kernel.
@@ -822,8 +822,6 @@
 obtained from the dom0, it is far more likely to be out of sync or
 missing with Xen.)
 
-Your domain should be now ready to work, enjoy.
-
 Creating an unprivileged Linux domain (domU)
 --------------------------------------------
 
@@ -1010,7 +1008,7 @@
 Amazon
 ------
 
-TODO: add link to NetBSD amazon howto.
+See the [Amazon EC2 page](../amazon_ec2/).
 
 Using npf
 ---------
@@ -1018,9 +1016,10 @@
 In standard kernels, npf is a module, and thus cannot be loaded in a
 DOMU kernel.
 
-TODO: explain how to compile npf into a custom kernel, answering (but
-note that the problem was caused by not booting the right kernel):
-http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html
+TODO: Explain how to compile npf into a custom kernel, answering (but
+note that the problem was caused by not booting the right kernel)
+[this email to
+netbsd-users](http://mail-index.netbsd.org/netbsd-users/2014/12/26/msg015576.html).
 
 TODO items for improving NetBSD/xen
 ===================================
@@ -1049,6 +1048,5 @@
 TODO: This section contains links from elsewhere not yet integrated
 into the HOWTO.
 
-* [Amazon EC2 (which uses Xen)](../amazon_ec2/).
 * http://www.lumbercartel.ca/library/xen/
 * http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html

capitalize HOWTO
Index: wikisrc/ports/xen.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/ports/xen.mdwn	24 Dec 2014 05:35:43 -0000	1.13
+++ wikisrc/ports/xen.mdwn	5 Mar 2015 13:38:58 -0000	1.14
@@ -15,7 +15,8 @@
 guest operating systems with unprecedented levels of performance and resource
 isolation. Xen is Open Source software.
 
-For instructions on how to install Xen with NetBSD, see the [[Xen Howto|/ports/xen/howto]].
+For instructions on how to install Xen with NetBSD, see the
+[[Xen HOWTO|/ports/xen/howto]].
 
 See [http://www.xenproject.org/](http://www.xenproject.org/) for
 more details on Xen.

add another pointer
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.93
retrieving revision 1.94
diff -u -r1.93 -r1.94
--- wikisrc/ports/xen/howto.mdwn	5 Mar 2015 13:27:37 -0000	1.93
+++ wikisrc/ports/xen/howto.mdwn	5 Mar 2015 13:38:10 -0000	1.94
@@ -1049,5 +1049,6 @@
 TODO: This section contains links from elsewhere not yet integrated
 into the HOWTO.
 
+* [Amazon EC2 (which uses Xen)](../amazon_ec2/).
 * http://www.lumbercartel.ca/library/xen/
 * http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html

Summary: punctuation
Index: wikisrc/xen.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/xen.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/xen.mdwn	5 Mar 2015 13:28:49 -0000	1.2
+++ wikisrc/xen.mdwn	5 Mar 2015 13:36:42 -0000	1.3
@@ -1,4 +1,4 @@
 # NetBSD on Xen Hypervisor
 
 For information about NetBSD and Xen, see the
-[Xen port page](http://www.netbsd.org/ports/xen/)
+[Xen port page](http://www.netbsd.org/ports/xen/).

Move links to howto. Turn into 302 to port page, basically.
Index: wikisrc/xen.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/xen.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/xen.mdwn	7 Jul 2010 19:14:16 -0000	1.1
+++ wikisrc/xen.mdwn	5 Mar 2015 13:28:49 -0000	1.2
@@ -1,10 +1,4 @@
 # NetBSD on Xen Hypervisor
 
-## Port page for Xen
-<http://www.netbsd.org/ports/xen/>
-
-## Other resources
-
-* <http://www.netbsd.org/ports/xen/howto.html>
-* <http://www.lumbercartel.ca/library/xen/>
-* <http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html>
+For information about NetBSD and Xen, see the
+[Xen port page](http://www.netbsd.org/ports/xen/)

Add a few links, and fix typos.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.92
retrieving revision 1.93
diff -u -r1.92 -r1.93
--- wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:36:07 -0000	1.92
+++ wikisrc/ports/xen/howto.mdwn	5 Mar 2015 13:27:37 -0000	1.93
@@ -226,7 +226,7 @@
 desktop or laptop.  Then, one can run domUs at will.  Purists will
 deride this as less secure than the previous approach, and for a
 computer whose purpose is to run domUs, they are right.  But Xen and a
-dom0 (without domUs) is not meaingfully less secure than the same
+dom0 (without domUs) is not meaningfully less secure than the same
 things running without Xen.  One can boot Xen or boot regular NetBSD
 alternately with little problems, simply refraining from starting the
 Xen daemons when not running Xen.
@@ -251,7 +251,7 @@
 partition; this is no different when booting Xen.
 
 There are 4 styles of providing backing storage for the virtual disks
-used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN,
+used by domUs: raw partitions, LVM, file-backed vnd(4), and SAN.
 
 With raw partitions, one has a disklabel (or gpt) partition sized for
 each virtual disk to be used by the domU.  (If you are able to predict
@@ -324,6 +324,11 @@
 to force only one vcpu to be provided (since NetBSD dom0 can't use
 more) and to pin that vcpu to a physical cpu.  TODO: benchmark this.
 
+Xen has [many boot
+options](http://xenbits.xenproject.org/docs/4.5-testing/misc/xen-command-line.html),
+and other tham dom0 memory and max_vcpus, they are generally not
+necessary.
+
 As with non-Xen systems, you should have a line to boot /netbsd (a
 kernel that works without Xen) and fallback versions of the non-Xen
 kernel, Xen, and the dom0 kernel.
@@ -1020,8 +1025,10 @@
 TODO items for improving NetBSD/xen
 ===================================
 
-* Package Xen 4.4.
-* Get PCI passthrough working on Xen 4.2 (or 4.4).
+* Make the NetBSD dom0 kernel work with SMP.
+* Test the Xen 4.5 packages adequately to be able to recommend them as
+  the standard approach.
+* Get PCI passthrough working on Xen 4.5
 * Get pvgrub into pkgsrc, either via xentools or separately.
 * grub
   * Check/add support to pkgsrc grub2 for UFS2 and arbitrary
@@ -1033,3 +1040,14 @@
   * Get UFS2 patches into pvgrub.
 * Add support for PV ops to a version of /boot, and make it usable as
   a kernel in Xen, similar to pvgrub.
+* Solve somehow the issue with modules for GENERIC not being loadable
+  in a Xen dom0 or domU kernel.
+
+Random pointers
+===============
+
+TODO: This section contains links from elsewhere not yet integrated
+into the HOWTO.
+
+* http://www.lumbercartel.ca/library/xen/
+* http://pbraun.nethence.com/doc/sysutils/xen_netbsd_dom0.html

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 01:49:37 -0000	1.7
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 08:21:35 -0000	1.8
@@ -7,6 +7,7 @@
 
 [[!table data="""
 First Last | `login@` | comment(s)
+Bernd Ernesti | `veego` |
 Hikaru Abe | `hikaru` |
 Hiroki Suenaga | `hsuenaga` |
 Justin Cormack | `justin` |
@@ -31,4 +32,4 @@
 """]]
 
 ## Discussions
-*
+* board voting procedure

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 01:13:46 -0000	1.6
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 01:49:37 -0000	1.7
@@ -14,6 +14,7 @@
 Kimihiro NONAKA | `nonaka` |
 Makoto Fujiwara | `mef` |
 Masanobu SAITOH | `msaitoh` |
+Masaru OKI | `oki` |
 Martin Husemann | `martin` |
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |

Note that /netbsd should exist in a domU for kmem.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.91
retrieving revision 1.92
diff -u -r1.91 -r1.92
--- wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:32:16 -0000	1.91
+++ wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:36:07 -0000	1.92
@@ -809,6 +809,14 @@
 in rc.conf. This way, the domain will be properly shut down if
 `xm shutdown -R` or `xm shutdown -H` is used on the dom0.
 
+It is not strictly necessary to have a kernel (as /netbsd) in the domU
+filesystem.  However, various programs (e.g. netstat) will use that
+kernel to look up symbols to read from kernel virtual memory.  If
+/netbsd is not the running kernel, those lookups will fail.  (This is
+not really a Xen-specific issue, but because the domU kernel is
+obtained from the dom0, it is far more likely to be out of sync or
+missing with Xen.)
+
 Your domain should be now ready to work, enjoy.
 
 Creating an unprivileged Linux domain (domU)

Turn PR links into real links.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.90
retrieving revision 1.91
diff -u -r1.90 -r1.91
--- wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:31:02 -0000	1.90
+++ wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:32:16 -0000	1.91
@@ -148,8 +148,8 @@
 Mostly, NetBSD as a dom0 or domU is quite stable.
 However, there are some open PRs indicating problems.
 
- - http://gnats.netbsd.org/48125
- - http://gnats.netbsd.org/47720
+ - [PR 48125](http://gnats.netbsd.org/48125)
+ - [PR 47720](http://gnats.netbsd.org/47720)
 
 Note also that there are issues with sparse vnd(4) instances, but
 these are not about Xen.
@@ -526,7 +526,8 @@
         dom0 kernel: NetBSD/amd64 6.1.5
         Xen tools: xentools42-4.2.5 from pkgsrc
 
-See http://gnats.netbsd.org/47720 for a problem with dom0 shutdown.
+See [PR 47720](http://gnats.netbsd.org/47720) for a problem with dom0
+shutdown.
 
 Unprivileged domains (domU)
 ===========================

fix spaces (cosmetic)
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.89
retrieving revision 1.90
diff -u -r1.89 -r1.90
--- wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:27:58 -0000	1.89
+++ wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:31:02 -0000	1.90
@@ -588,7 +588,7 @@
         xm console foo
         xm create -c foo
         xm shutdown foo
-	xm list
+        xm list
 
 Typing ^] will exit the console session.  Shutting down a domain is
 equivalent to pushing the power button; a NetBSD domU will receive a

Add stability notes.
Reference PRs from gson@ and caution against sparse vnd(4).
Members: 
	ports/xen/howto.mdwn:1.88->1.89 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.88
retrieving revision 1.89
diff -u -r1.88 -r1.89
--- wikisrc/ports/xen/howto.mdwn	10 Feb 2015 17:38:14 -0000	1.88
+++ wikisrc/ports/xen/howto.mdwn	4 Mar 2015 01:27:58 -0000	1.89
@@ -142,6 +142,18 @@
 (Note that emacs (at least) fails if run on i386 with PAE when built
 without, and vice versa, presumably due to bugs in the undump code.)
 
+Stability
+---------
+
+Mostly, NetBSD as a dom0 or domU is quite stable.
+However, there are some open PRs indicating problems.
+
+ - http://gnats.netbsd.org/48125
+ - http://gnats.netbsd.org/47720
+
+Note also that there are issues with sparse vnd(4) instances, but
+these are not about Xen.
+
 Recommendation
 --------------
 
@@ -636,6 +648,10 @@
 
         dd if=/dev/zero of=foo-xbd0 bs=1m count=4096
 
+Do not use qemu-img-xen, because this will create sparse file.  There
+have been recent (2015) reports of sparse vnd(4) devices causing
+lockups, but there is apparently no PR.
+
 With the lvm style, one creates logical devices.  They are then used
 similarly to vnds.  TODO: Add an example with lvm.
 

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 00:54:01 -0000	1.5
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 01:13:46 -0000	1.6
@@ -17,6 +17,7 @@
 Martin Husemann | `martin` |
 Ryota Ozaki | `ozaki-r` |
 Ryo Shimizu | `ryo` |
+Taylor R Campbell | `raiastradh` |
 """]]
 
 ## Planning to present something?

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	2 Mar 2015 09:44:59 -0000	1.4
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	4 Mar 2015 00:54:01 -0000	1.5
@@ -7,12 +7,16 @@
 
 [[!table data="""
 First Last | `login@` | comment(s)
+Hikaru Abe | `hikaru` |
+Hiroki Suenaga | `hsuenaga` |
 Justin Cormack | `justin` |
-kengo Nakahara | `knakahara` |
+Kengo Nakahara | `knakahara` |
+Kimihiro NONAKA | `nonaka` |
 Makoto Fujiwara | `mef` |
 Masanobu SAITOH | `msaitoh` |
 Martin Husemann | `martin` |
 Ryota Ozaki | `ozaki-r` |
+Ryo Shimizu | `ryo` |
 """]]
 
 ## Planning to present something?

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	2 Mar 2015 09:44:08 -0000	1.3
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	2 Mar 2015 09:44:59 -0000	1.4
@@ -8,6 +8,7 @@
 [[!table data="""
 First Last | `login@` | comment(s)
 Justin Cormack | `justin` |
+kengo Nakahara | `knakahara` |
 Makoto Fujiwara | `mef` |
 Masanobu SAITOH | `msaitoh` |
 Martin Husemann | `martin` |

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	2 Mar 2015 09:25:15 -0000	1.2
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	2 Mar 2015 09:44:08 -0000	1.3
@@ -1,7 +1,7 @@
 ## Details
 
 The NetBSD developer summit at AsiaBSDCon 2015 will be held Friday,
-March 13th.
+09:30-12:30, March 13th.
 
 ## Planning to attend?
 
@@ -18,6 +18,8 @@
 
 [[!table data="""
 Speaker  |Title
+`msaitoh@` | New NetBSD developer candidates(10-15 minutes)
+`msaitoh@` | Current status and next step of MP capable network stack. (15 minutes?)
 `login@` |_Very Interesting Thing_
 """]]
 

Index: wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	23 Feb 2015 10:21:08 -0000	1.1
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	2 Mar 2015 09:25:15 -0000	1.2
@@ -7,7 +7,11 @@
 
 [[!table data="""
 First Last | `login@` | comment(s)
-Masanobu SAITOH | `msaitoh` | 
+Justin Cormack | `justin` |
+Makoto Fujiwara | `mef` |
+Masanobu SAITOH | `msaitoh` |
+Martin Husemann | `martin` |
+Ryota Ozaki | `ozaki-r` |
 """]]
 
 ## Planning to present something?

Index: wikisrc/projects/project/atf-sql-backend.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/atf-sql-backend.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/atf-sql-backend.mdwn	19 Feb 2015 19:45:45 -0000	1.2
+++ wikisrc/projects/project/atf-sql-backend.mdwn	2 Mar 2015 07:39:12 -0000	1.3
@@ -17,9 +17,9 @@
 description="""
 We are currently running various regular [tests](http://releng.netbsd.org/test-results.html), both on emulators and real hardware.
 The results are generated in ATF (or maybe sometime later in Kuya) raw XML output format and then transformed via xslt into html.
-This is good enough to display single test run results, but does not provide any overview or comparison options accross different test runs or architectures.
+This is good enough to display single test run results, but does not provide any overview or comparison options across different test runs or architectures.
 
-The target of this project is to provide a simmple 'upload' utility, that takes the xml input and inserts it into a remote PostgresSQL database.
+The target of this project is to provide a simple 'upload' utility, that takes the xml input and inserts it into a remote PostgresSQL database.
 Creating a suitable database schema and the xml loader/upload tool is the first half.
 
 Second part is using the collected results to display some nice web pages showing statistics and allowing dedicated queries, comparable
@@ -37,6 +37,10 @@
 
 The result is planed to be deployed on TNF servers later, so it is of direct use for the community.
 This deployment is not part of the GSoC timeline.
+
+Note that item (4) above needs proper evaluation before the database schema is created. Kuya already stores test results in a SQLite database, so the extract and upload utility likely will be simple, but the database schema is incompatible and a good migration plan is needed upfront.
+
+During GSoC, this project will ignore deployment issues, which will need broader discussion and maybe changes to the tools - for example the finally deployed upload utility has to be part of the base installation, so may not be able to depend on PostgresSQL libraries. A pkgsrc based solution for milestone (2) is good enough for this project.
 """
 ]]
 

--- /dev/null	2015-02-27 17:50:00.000000000 +0000
+++ wikisrc/ports/evbarm/odroid-c1.mdwn	2015-02-27 17:58:37.000000000 +0000
@@ -0,0 +1,18 @@
+[[!meta title="NetBSD/evbarm on Hardkernel ODROID-C1"]]
+
+[[!toc levels=2]]
+
+# ODROID-C1 UART pins
+
+From [ODROID Forum](http://forum.odroid.com/viewtopic.php?f=115&t=7684):
+
+[[!template  id=programlisting text="""
+ ___UART____
+|Pin 4 - GND|
+|Pin 3 - RXD|
+|Pin 2 - TXD|
+|Pin 1 - VCC|
+\___________|
+
+3.3V LVTTL
+"""]]

--- /dev/null	2015-02-23 10:20:00.000000000 +0000
+++ wikisrc/summits/AsiaBSDCon_2015_NetBSD_Summit.mdwn	2015-02-23 10:21:11.000000000 +0000
@@ -0,0 +1,21 @@
+## Details
+
+The NetBSD developer summit at AsiaBSDCon 2015 will be held Friday,
+March 13th.
+
+## Planning to attend?
+
+[[!table data="""
+First Last | `login@` | comment(s)
+Masanobu SAITOH | `msaitoh` | 
+"""]]
+
+## Planning to present something?
+
+[[!table data="""
+Speaker  |Title
+`login@` |_Very Interesting Thing_
+"""]]
+
+## Discussions
+*

removed
--- wikisrc/projects/project/netbsd_on_microsoft_azure/comment_2_e5e7c434226f63fb28608330dbd22661._comment	2015-02-22 04:10:29.000000000 +0000
+++ /dev/null	2015-02-22 04:10:03.000000000 +0000
@@ -1,14 +0,0 @@
-[[!comment format=mdwn
- username="https://www.google.com/accounts/o8/id?id=AItOawno_FsM7bUgCzS526w5T3_CFxZ-413P3wY"
- nickname="Ross"
- subject="A few of useful resources.."
- date="2015-02-22T04:08:50Z"
- content="""
-Instructions on how to build a FreeBSD image: http://azure.microsoft.com/blog/2014/05/22/running-freebsd-in-azure/
-
-Instructions on how to build a Linux image: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-tutorial/
-
-Images can be published on http://vmdepot.msopentech.com when complete
-
-How to customize and republish an image once a base image is available in VM Depot: https://vmdepot.msopentech.com/tutorial/freeBSD.html
-"""]]

Added a comment: A few of useful resources..
--- /dev/null	2015-02-22 04:10:03.000000000 +0000
+++ wikisrc/projects/project/netbsd_on_microsoft_azure/comment_2_e5e7c434226f63fb28608330dbd22661._comment	2015-02-22 04:10:08.000000000 +0000
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawno_FsM7bUgCzS526w5T3_CFxZ-413P3wY"
+ nickname="Ross"
+ subject="A few of useful resources.."
+ date="2015-02-22T04:08:50Z"
+ content="""
+Instructions on how to build a FreeBSD image: http://azure.microsoft.com/blog/2014/05/22/running-freebsd-in-azure/
+
+Instructions on how to build a Linux image: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-tutorial/
+
+Images can be published on http://vmdepot.msopentech.com when complete
+
+How to customize and republish an image once a base image is available in VM Depot: https://vmdepot.msopentech.com/tutorial/freeBSD.html
+"""]]

Added a comment: A few of useful resources..
--- /dev/null	2015-02-22 04:00:01.000000000 +0000
+++ wikisrc/projects/project/netbsd_on_microsoft_azure/comment_1_6b35e01eee06c30c14dd5f4e79a50852._comment	2015-02-22 04:08:30.000000000 +0000
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawno_FsM7bUgCzS526w5T3_CFxZ-413P3wY"
+ nickname="Ross"
+ subject="A few of useful resources.."
+ date="2015-02-22T04:07:10Z"
+ content="""
+Instructions on how to build a FreeBSD image: http://azure.microsoft.com/blog/2014/05/22/running-freebsd-in-azure/
+
+Instructions on how to build a Linux image: http://azure.microsoft.com/en-us/documentation/articles/virtual-machines-linux-tutorial/
+
+Images can be published on http://vmdepot.msopentech.com when complete
+
+How to customize and republish an image once a base image is available in VM Depot: https://vmdepot.msopentech.com/tutorial/freeBSD.html
+"""]]

Index: wikisrc/projects/project/secureplt.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/secureplt.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/secureplt.mdwn	20 Feb 2015 19:21:44 -0000	1.3
+++ wikisrc/projects/project/secureplt.mdwn	20 Feb 2015 20:41:05 -0000	1.4
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Secure-PLT - supporting new PLT formats on alpha"
+title="Secure-PLT - supporting RELRO binaries"
 
 contact="""
 [tech-userlevel](mailto:tech-userlevel@NetBSD.org)
@@ -15,15 +15,19 @@
 duration="3 months"
 
 description="""
-Currently kernels with options PAX_MPROTECT can not execute dynamically linked binaries on most RISC architectures, because the PLT format defined by the ABI of these architectures uses self-modifying code.
+All architectures suffer from code injection issues because the only writable segment is the PLT/GOT. RELRO (RELocation Read Only) is a mitigation technique that is used during dynamic linking to prevent access to the PLT/GOT. There is partial RELRO which protects that GOT but leaves the PLT writable, and full RELRO that protects both at the expense of performing a full symbol resolution at startup time. The project is about making the necessary modifications to the dynamic loader (ld_elf.so) to make RELRO work.
+
+If that is completed, then we can also add the following improvement:
+Currently kernels with options PAX_MPROTECT can not execute dynamically linked binaries on most RISC architectures, because the PLT format defined by the ABI of these architectures uses self-modifying code. New binutils versions have introduced a different PLT format (enabled with --secureplt) for alpha and powerpc.
+
 
-New binutils versions have introduced a different PLT format (enabled with --secureplt) for alpha and powerpc.
 
 Milestones:
 
-* This project (for alpha) is to add support for the new PLT formats introduced in binutils 2.17 and gcc4.1 This will require changes to the dynamic loader (ld.elf_so), various assembly headers, and library files.
-* Support for both the old and new formats in the same invocation will be required.
 * For all architectures we can improve security by implementing [relro](http://tk-blog.blogspot.com/2009/02/relro-not-so-well-known-memory.html).
+* Once this is done, we can improve security for the RISC architectures by adding support for the new PLT formats introduced in binutils 2.17 and gcc4.1 This will require changes to the dynamic loader (ld.elf_so), various assembly headers, and library files.
+* Support for both the old and new formats in the same invocation will be required.
+
 """
 ]]
 

Index: wikisrc/projects/project/verify_netbsd32.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/verify_netbsd32.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/verify_netbsd32.mdwn	20 Feb 2015 19:21:44 -0000	1.3
+++ wikisrc/projects/project/verify_netbsd32.mdwn	20 Feb 2015 19:48:08 -0000	1.4
@@ -27,6 +27,7 @@
 This and the resulting padding introduced by the compiler can create hard to find bugs.
 
 goals/milestones:
+
 * replace the manual labour with an automatic tool
 > > This tool should allow both verification / generation of structure definitions for use in netbsd32 code 
 > > allow generation of system call stubs and conversion functions.

Index: wikisrc/projects/project/launchd-port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/launchd-port.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/launchd-port.mdwn	20 Feb 2015 17:12:46 -0000	1.3
+++ wikisrc/projects/project/launchd-port.mdwn	20 Feb 2015 19:46:57 -0000	1.4
@@ -35,6 +35,8 @@
 
 """
 
+(noted by edreyfus) A lot of mach functionality were added in COMPAT_MACH (src/sys/compat/mach), which has been removed from cvs, but it could be resurrected. 
+
 ]]
 
 [[!tag gsoc]]

removed
--- wikisrc/projects/project/launchd-port/comment_1_602ba74efd23ef50aa56bce1ebf7b189._comment	2015-02-20 19:45:49.000000000 +0000
+++ /dev/null	2015-02-20 19:40:01.000000000 +0000
@@ -1,8 +0,0 @@
-[[!comment format=mdwn
- username="https://openid.espci.fr/edreyfus"
- ip="213.41.141.172"
- subject="Mach feature"
- date="2012-11-07T02:18:04Z"
- content="""
-A lot of mach functionality were added in COMPAT_MACH (src/sys/compat/mach), which has been removed from cvs, but it could be resurrected.
-"""]]

Index: wikisrc/projects/project/libintl.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/libintl.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/libintl.mdwn	20 Feb 2015 17:12:46 -0000	1.3
+++ wikisrc/projects/project/libintl.mdwn	20 Feb 2015 19:44:31 -0000	1.4
@@ -23,6 +23,7 @@
 * Implement support for the extensions in the message catalog format. libintl should be able to process all .mo files from current gettext and return the same results via the API.
 * Provide a clean implementation of msgfmt.
 * Other components of gettext like msgmerge and the gettext frontend should be evaluated case-by-case if they are useful for the base system and whether third party software in pkgsrc depends on them.
+* demonstrate the elimination of GNU gettext dependencies
 
 """
 ]]

Index: wikisrc/projects/project/inetd-enhancements.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/inetd-enhancements.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/inetd-enhancements.mdwn	20 Feb 2015 16:42:42 -0000	1.5
+++ wikisrc/projects/project/inetd-enhancements.mdwn	20 Feb 2015 19:43:39 -0000	1.6
@@ -15,7 +15,7 @@
 duration="3 months"
 
 description="""
-Enhance inetd in NetBSD
+inetd is a classic method for launching network programs on-the-fly and some of its ideas are coming back into vogue.  Enhancing this daemon should include investigations into other similar systems in other operating systems.
 
 Primary milestones:
 

Index: wikisrc/projects/project/isdn-nt-asterisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/isdn-nt-asterisk.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/isdn-nt-asterisk.mdwn	20 Feb 2015 16:42:42 -0000	1.3
+++ wikisrc/projects/project/isdn-nt-asterisk.mdwn	20 Feb 2015 19:40:28 -0000	1.4
@@ -15,6 +15,9 @@
 duration="3 months"
 
 description="""
+NetBSD is a common target for asterisk installations and could use some improvements.
+Improving ISDN puts us back in the running as a high-end installation target.
+
 This project has three milestones:
 
 * add support for the NT (network) side of ISDN to the NetBSD ISDN stack
@@ -22,6 +25,9 @@
 * show this makes it easier to test new ISDN card drivers
 
 Previous work in this area can be found at the [alternative ISDN driver site](http://www.turbocat.net/~hselasky/isdn4bsd/).
+
+The student needs access to ISDN and telephony hardware for this project.
+
 """
 ]]
 

Index: wikisrc/projects/project/common-boot-cfg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/common-boot-cfg.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/common-boot-cfg.mdwn	20 Feb 2015 16:42:42 -0000	1.3
+++ wikisrc/projects/project/common-boot-cfg.mdwn	20 Feb 2015 19:38:28 -0000	1.4
@@ -21,6 +21,7 @@
 and the situation needs to be improved.
 
 The milestones of this project:
+
 * split the machine dependent parts out
 * provide generic, machine independent support for most of the /boot.cfg handling
 * leave configuration (like what commands are allowed) to the architecture specific code

remove gsoc tag since it was already worked in a previous year
Index: wikisrc/projects/project/virtual-box-guest-tools.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/virtual-box-guest-tools.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/projects/project/virtual-box-guest-tools.mdwn	19 Feb 2014 07:16:49 -0000	1.7
+++ wikisrc/projects/project/virtual-box-guest-tools.mdwn	20 Feb 2015 19:32:00 -0000	1.8
@@ -47,6 +47,3 @@
 """
 
 ]]
-
-
-[[!tag gsoc]]

add 'milestones' to a bunch of pojects, take 4
Index: wikisrc/projects/project/raidframe-raid6.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/raidframe-raid6.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/raidframe-raid6.mdwn	18 Feb 2015 22:51:55 -0000	1.2
+++ wikisrc/projects/project/raidframe-raid6.mdwn	20 Feb 2015 19:21:44 -0000	1.3
@@ -12,10 +12,26 @@
 
 category="filesystems"
 difficulty="medium"
-duration="unknown"
+duration="two months"
 
 description="""
 Test and debug the RAID 6 implementation in RAIDframe.
+
+NetBSD uses RAIDframe (raid(4)) and stub code exists for RAID6 but is not very
+documented or well tested.  Obviously, this code needs to be researched and
+vetted by an interested party.  Other BSD projects should be consulted freely.
+
+Milestones:
+* setup a working RAID 6 using RAIDFrame
+* document RAID6 in raid(4) manual page
+* port/develop a set of reliability and performance tests
+* fix bugs along the way
+* automate RAID testing in atf
+
+Bonus:
+* Document how to add new RAID levels to RAIDframe
+* (you're awesome bonus) add RAID 1+0, etc
+
 """
 ]]
 
Index: wikisrc/projects/project/rewrite-pkg_comp.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/rewrite-pkg_comp.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/rewrite-pkg_comp.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/rewrite-pkg_comp.mdwn	20 Feb 2015 19:21:44 -0000	1.3
@@ -23,7 +23,7 @@
 
 The language of choice for the reimplementation will be Python. The code will be hosted outside of pkgsrc to be able to distribute it as a standalone tool.
 
-The following items should be accomplished:
+The following milestones should be accomplished:
 
 * Implement a "sandbox" library with an interface to programmatically create and manage a sandboxed file system. The structure of the sandbox has to be configurable through a template, and templates have to be provided for a few systems. The sandbox itself will be constructed either by unpacking tarballs with the system contents (such as the NetBSD distfiles), by null-mounting directories of the host file system, or both.
 * Implement a command-line frontend utility for the "sandbox" library. This tool is completely unaware of pkgsrc but will be really nice to have (and trivial to write, as all the juicy bits are in the library). Will be useful as part of server administration, as it will allow isolating services in a fairly easy manner.
Index: wikisrc/projects/project/secureplt.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/secureplt.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/secureplt.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/secureplt.mdwn	20 Feb 2015 19:21:44 -0000	1.3
@@ -19,11 +19,11 @@
 
 New binutils versions have introduced a different PLT format (enabled with --secureplt) for alpha and powerpc.
 
-This project (for alpha) is to add support for the new PLT formats introduced in binutils 2.17 and gcc4.1 This will require changes to the dynamic loader (ld.elf_so), various assembly headers, and library files.
+Milestones:
 
-Support for both the old and new formats in the same invocation will be required.
-
-For all architectures we can improve security by implementing [relro](http://tk-blog.blogspot.com/2009/02/relro-not-so-well-known-memory.html).
+* This project (for alpha) is to add support for the new PLT formats introduced in binutils 2.17 and gcc4.1 This will require changes to the dynamic loader (ld.elf_so), various assembly headers, and library files.
+* Support for both the old and new formats in the same invocation will be required.
+* For all architectures we can improve security by implementing [relro](http://tk-blog.blogspot.com/2009/02/relro-not-so-well-known-memory.html).
 """
 ]]
 
Index: wikisrc/projects/project/sysinst-xinterface.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sysinst-xinterface.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/sysinst-xinterface.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/sysinst-xinterface.mdwn	20 Feb 2015 19:21:44 -0000	1.3
@@ -29,6 +29,12 @@
 
 An optional extension of the project is to modify the creation of one or more port's install CD to make use of the new xsysinst.
 
+Milestones include:
+* modify the "menuc" tool to support X
+* keep text/serial console installing
+* demonstrate a GUI install
+* demonstrate fallback to the text installer
+
 The candidate must have:
 
 * familiarity with the system installer. You should have used sysinst to install the system.
Index: wikisrc/projects/project/sysinst_pkgs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sysinst_pkgs.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/sysinst_pkgs.mdwn	14 Feb 2013 22:36:08 -0000	1.3
+++ wikisrc/projects/project/sysinst_pkgs.mdwn	20 Feb 2015 19:21:44 -0000	1.4
@@ -20,7 +20,7 @@
 The packages might be simple packages like screen or bigger ones like firefox.
 Configuration of the packages is not required to happen in sysinst.
 
-A short overview of the steps involved:
+A short overview of the milestones involved:
 
 * Improve sysinst so it can list a pkgsummary.gz file on the install media and offer to install a subset of them. There should be a chooser included in sysinst where the user can select the packages they want to install.
 
Index: wikisrc/projects/project/verify_netbsd32.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/verify_netbsd32.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/verify_netbsd32.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/verify_netbsd32.mdwn	20 Feb 2015 19:21:44 -0000	1.3
@@ -26,10 +26,13 @@
 On i386 uint64_t has a 32bit alignment, but on AMD64 it uses natural (64bit) alignment.
 This and the resulting padding introduced by the compiler can create hard to find bugs.
 
-The goal of this project is to replace the manual labour with an automatic tool.
-This tool should allow both verification / generation of structure definitions for use in netbsd32 code as well as allow generation of system call stubs and conversion functions.
+goals/milestones:
+* replace the manual labour with an automatic tool
+> > This tool should allow both verification / generation of structure definitions for use in netbsd32 code 
+> > allow generation of system call stubs and conversion functions.
+> > Generated stubs should also ensure that no kernel stack data is leaked in hidden padding without having to resort to unnecessary large memset calls.
+
 For this purpose, the [Clang C parser](http://clang.llvm.org) or the [libclang frontend](http://llvm.org/devmtg/2010-11/Gregor-libclang.pdf) can be used to analyse the C code.
-Generated stubs should also ensure that no kernel stack data is leaked in hidden padding without having to resort to unnecessary large memset calls.
 """
 ]]
 

add 'milestones' to a bunch of pojects, take 3
Index: wikisrc/projects/project/netbsd_on_microsoft_azure.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/netbsd_on_microsoft_azure.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/projects/project/netbsd_on_microsoft_azure.mdwn	18 Mar 2013 12:23:38 -0000	1.5
+++ wikisrc/projects/project/netbsd_on_microsoft_azure.mdwn	20 Feb 2015 17:42:22 -0000	1.6
@@ -3,10 +3,11 @@
 title="NetBSD/azure -- Bringing NetBSD to Microsoft Azure"
 
 contact="""
-[port-xen](mailto:port-xen@NetBSD.org) ???
+[port-xen](mailto:port-xen@NetBSD.org)
 """
 
 mentors="""
+[Christos Zoulas](mailto:christos@NetBSD.org)
 """
 
 category="kernel"
@@ -24,6 +25,11 @@
 
 [FreeBSD drivers for the Hyper-V virtual machine interface](http://freebsdonhyper-v.github.com/)
 
+Milestones for this project:
+
+* booting NetBSD on azure
+* process for automatically building azure-friendly images, similar to amazon AMI
+
 """
 
 ]]
Index: wikisrc/projects/project/opencrypto_swcrypto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/opencrypto_swcrypto.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/opencrypto_swcrypto.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/opencrypto_swcrypto.mdwn	20 Feb 2015 17:42:22 -0000	1.3
@@ -15,7 +15,17 @@
 duration="3 months"
 
 description="""
-Use multiple cores efficiently (that already works reasonably well for multiple request streams); actually use faster versions of complex transforms (CBC, counter modes) from our in-tree OpenSSL or elsewhere (eg libtomcrypt); add support for asymmetric operations (public key). Tie public-key operations into veriexec somehow for extra credit (probably a very good start towards an undergrad thesis project).
+swcrypto could use a variety of enhanacements
+
+Milestones/deliverables:
+
+* use multiple cores efficiently (that already works reasonably well for multiple request streams)
+* use faster versions of complex transforms (CBC, counter modes) from our in-tree OpenSSL or elsewhere (eg libtomcrypt)
+* add support for asymmetric operations (public key)
+
+Extra credit:
+
+* Tie public-key operations into veriexec somehow for extra credit (probably a very good start towards an undergrad thesis project).
 """
 ]]
 
Index: wikisrc/projects/project/pkgsrc_binpkg_depends.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_binpkg_depends.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/pkgsrc_binpkg_depends.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/pkgsrc_binpkg_depends.mdwn	20 Feb 2015 17:42:22 -0000	1.3
@@ -31,6 +31,12 @@
 It would be good to provide scripts that convert from the current state to the new one, and test it with a bulk build.
 
 Of course it's not expected that all packages be converted to the new framework in the course of this project, but the further steps should be made clear.
+
+goals/milestones:
+* invent a replacement for buildlink3.mk files, keeping current features
+* demonstrate your new tool as a buildlink3.mk replacement including new features
+* execute a bulk build with as many packages as possible using the new buildlink
+
 """
 ]]
 
Index: wikisrc/projects/project/pkgsrc_config_vcs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_config_vcs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/pkgsrc_config_vcs.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/pkgsrc_config_vcs.mdwn	20 Feb 2015 17:42:22 -0000	1.3
@@ -29,6 +29,15 @@
 * Regular automated check-ins of the entire live pkgsrc configuration should be easy to set up, but also manual check-ins of singular files so the local admin can use meaningful commit messages when they change their config, even if they are not experienced users of version control systems
 
 The actual commands to the version control system should be hidden behind an abstraction layer, and the vcs operations should be kept simple, so that other compatibility layers can be written, and eventually the user can pick their vcs of choice (and also a vcs location of choice, in case e.g. the enterprise configuration repository is on a central subversion server).
+
+milestones/goals:
+* choose a VCS system (BSD licensed is a nice-to-have)
+* write wrappers around it, or embed its functionality
+* demonstrate usage in upgrades
+
+bonus:
+* extend functionality into additional VCS systems
+
 """
 ]]
 
Index: wikisrc/projects/project/pkgsrc_installtasks.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_installtasks.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/pkgsrc_installtasks.mdwn	30 Jul 2013 19:43:46 -0000	1.3
+++ wikisrc/projects/project/pkgsrc_installtasks.mdwn	20 Feb 2015 17:42:22 -0000	1.4
@@ -17,7 +17,13 @@
 description="""
 Instead of including install scripts from the infrastructure into every binary package, just include the necessary information and split the scripts off into a separate package that is installed first (right after bootstrap, as soon as the first package needs it). This affects user creation, installation of tex packages, ...
 
-Also add support for actions that happen once after a big upgrade session, instead of once per package (e.g. ls-lR rebuild for tex).
+Milestones:
+
+* identify example packages installing users, groups, and documentation
+* demonstrate pkgsrc packages which add users, etc
+* Also add support for actions that happen once after a big upgrade session, instead of once per package (e.g. ls-lR rebuild for tex).
+* convert some existing packages to use this new framework
+* allow options framework to configure these resources per-package
 
 An intermediate step would be to replace various remaining INSTALL scripts by declarative statements and install script snippets using them.
 """
Index: wikisrc/projects/project/pkgsrc_precise_dependencies.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_precise_dependencies.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/pkgsrc_precise_dependencies.mdwn	17 Mar 2012 21:53:08 -0000	1.1
+++ wikisrc/projects/project/pkgsrc_precise_dependencies.mdwn	20 Feb 2015 17:42:22 -0000	1.2
@@ -28,6 +28,12 @@
 actually used to build new package. Ideally, the tool should
 report files used during configure, build, and test stages,
 and packages these files are provided by.
+
+Milestones:
+* find or develop a good dependency graph algorithm
+* implement and demonstrate your new system in pkgsrc by adding a make target
+* expose this algorithm for use by websites such as pkgsrc.se
+
 """
 ]]
 
Index: wikisrc/projects/project/pkgsrc_spawn_support.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/pkgsrc_spawn_support.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/projects/project/pkgsrc_spawn_support.mdwn	21 Mar 2012 10:00:36 -0000	1.9
+++ wikisrc/projects/project/pkgsrc_spawn_support.mdwn	20 Feb 2015 17:42:22 -0000	1.10
@@ -36,9 +36,11 @@
 
 Optionally, MinGW spawn support can be added as well.
 
-The main goal of this project is to support starting processes and
-subprocesses by posix_spawn in devel/bmake and in shells/pdksh,
-measure its efficiency and compare it to traditional fork+exec.
+Milestones:
+
+* support starting processes and subprocesses by posix_spawn in devel/bmake
+* support starting processes and subprocesses by posix_spawn in shells/pdksh,
+* measure its efficiency and compare it to traditional fork+exec.
 """
 ]]
 

add 'milestones' to a bunch of pojects, take 2
Index: wikisrc/projects/project/launchd-port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/launchd-port.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/launchd-port.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/launchd-port.mdwn	20 Feb 2015 17:12:46 -0000	1.3
@@ -16,7 +16,25 @@
 
 description="""
 [Launchd](http://en.wikipedia.org/wiki/Launchd) is a MacOS/X utility that is used to start and control daemons similar to init(8), but much more powerful. There was an effort to port launchd to FreeBSD, but it seems to be [abandoned](http://wiki.freebsd.org/launchd). We should first investigate what happened to the FreeBSD effort to avoid duplicating work. The port is not trivial because launchd uses a lot of mach features.
+
+Milestones:
+
+* report of FreeBSD efforts (past and present)
+* launchd port replacing: init
+* launchd port replacing: rc
+* launchd port compatible with: rc.d scripts
+* launchd port replacing: watchdogd
+
+
+Nice to have:
+
+* launchd port replacing/integrating: inetd
+* launchd port replacing: atd
+* launchd port replacing: crond
+* launchd port replacing: (the rest)
+
 """
+
 ]]
 
 [[!tag gsoc]]
Index: wikisrc/projects/project/ledapi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/ledapi.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/ledapi.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/ledapi.mdwn	20 Feb 2015 17:12:46 -0000	1.3
@@ -18,6 +18,14 @@
 Design and implement a general API for control of LED and LCD type devices on NetBSD. The API would allow devices to register individual LED and LCD devices, along with a set of capabilities for each one. Devices that wish to display status via an LED/LCD would also register themselves as an event provider. A userland program would control the wiring of each event provider, to each output indicator. The API would need to encompass all types of LCD displays, such as 3 segment LCDs, 7 segment alphanumerics, and simple on/off state LED's. A simple example is a keyboard LED, which is an output indicator, and the caps-lock key being pressed, which is an event provider.
 
 There is prior art in OpenBSD; it should be checked for suitability, and any resulting API should not differ from theirs without reason.
+
+Milestones:
+
+* a port of OpenBSD's LED tools
+* a userland tool to control LED
+* demonstration of functionality
+* integration into NetBSD
+
 """
 ]]
 
Index: wikisrc/projects/project/libcurses-automated-test.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/libcurses-automated-test.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/libcurses-automated-test.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/libcurses-automated-test.mdwn	20 Feb 2015 17:12:46 -0000	1.3
@@ -17,9 +17,14 @@
 description="""
 The curses library is an important part of the NetBSD operating system, many applications rely on the correct functioning of the library. Performing modifications on the curses library can be difficult because the effects of the change may be subtle and can introduce bugs that are not detected for a long time.
 
-The aim of this project is to produce a suite of high quality tests for the curses library.  These tests should exercise every aspect of the library functionality.
+The testing framework has been written to run under the atf framework but has not been committed to the tree yet.
 
-The testing framework has been written to run under the atf framework but has not been committed to the tree yet.  The student undertaking this project will be provided with the testing framework and will use this to generate test cases for curses library calls.  Most of the work will require analytical skills to verify the output of the test is actually correct before encapsulating that output into a validation file.
+The student undertaking this project will be provided with the testing framework and will use this to generate test cases for curses library calls.  Most of the work will require analytical skills to verify the output of the test is actually correct before encapsulating that output into a validation file.
+
+Milestones for this project:
+
+* produce a suite of high quality tests for the curses library
+* These tests should exercise every aspect of the library functionality.
 
 This project will need a good understanding of the curses library and will provide the student with a much deeper understanding of the operation of curses.
 """
Index: wikisrc/projects/project/libintl.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/libintl.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/libintl.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/libintl.mdwn	20 Feb 2015 17:12:46 -0000	1.3
@@ -17,7 +17,7 @@
 description="""
 NetBSD provides a BSD licensed implementation of libintl. This implementation is based on the specifications from GNU gettext. It has not kept up with the development of gettext in the last few years though, lacking e.g. support for context specific translations. NetBSD currently also has to depend on GNU gettext to recreate the message catalogs.
 
-Goals for this project include:
+Milestones for this project include:
 
 * Restore full API compatibility with current gettext. At the time of writing, this is gettext 0.18.1.1.
 * Implement support for the extensions in the message catalog format. libintl should be able to process all .mo files from current gettext and return the same results via the API.
Index: wikisrc/projects/project/live-upgrade.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/live-upgrade.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/live-upgrade.mdwn	14 Apr 2013 11:48:58 -0000	1.4
+++ wikisrc/projects/project/live-upgrade.mdwn	20 Feb 2015 17:12:46 -0000	1.5
@@ -15,7 +15,9 @@
 duration="3 months"
 
 description="""
-Updating an operating system image can be fraught with danger, an error could cause the system to be unbootable and require significant work to restore the system to operation.  The aim of this project is to permit a system to be updated while it is running only requiring a reboot to activate the updated system and provide the facility to rollback to a "known good" system in the event that the update causes regressions.  The project should do the following:
+Updating an operating system image can be fraught with danger, an error could cause the system to be unbootable and require significant work to restore the system to operation.  The aim of this project is to permit a system to be updated while it is running only requiring a reboot to activate the updated system and provide the facility to rollback to a "known good" system in the event that the update causes regressions.
+
+Milestones for this project:
 
 * Make a copy of the currently running system
 * Either apply patches, install binary sets, run a source build with the copy as the install target

add 'milestones' to a bunch of pojects, take 1
Index: wikisrc/projects/project/binary_compat_puffs_backend.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/binary_compat_puffs_backend.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/binary_compat_puffs_backend.mdwn	27 Feb 2014 04:52:33 -0000	1.3
+++ wikisrc/projects/project/binary_compat_puffs_backend.mdwn	20 Feb 2015 16:42:42 -0000	1.4
@@ -17,7 +17,7 @@
 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 time_t size change in NetBSD 6.0), old puffs servers must be recompiled.
 
-The purpose of the project is to:
+The project milestones are:
 
 * *define* a binary-independent protocol
 * *implement* support
Index: wikisrc/projects/project/common-boot-cfg.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/common-boot-cfg.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/common-boot-cfg.mdwn	27 Feb 2014 07:00:44 -0000	1.2
+++ wikisrc/projects/project/common-boot-cfg.mdwn	20 Feb 2015 16:42:42 -0000	1.3
@@ -20,9 +20,11 @@
 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 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).
+The milestones of this project:
+* split the machine dependent parts out
+* provide generic, machine independent support for most of the /boot.cfg handling
+* leave configuration (like what commands are allowed) to the architecture specific code
+* provide means for overriding command handlers (i.e. implement a common command differently)
 
 Due to the organization of the bootstrapping code this is not as easy as it sounds at first sight, but it does not require
 deep kernel hacking skills either. Having various hardware available for testing is a bonus, but not required.
Index: wikisrc/projects/project/disk-removal.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/disk-removal.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/disk-removal.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/disk-removal.mdwn	20 Feb 2015 16:42:42 -0000	1.3
@@ -15,7 +15,15 @@
 duration="3 months"
 
 description="""
-Make NetBSD behave gracefully when a "live" USB/FireWire disk drive is accidentally detached and re-attached by, for example, creating a virtual block device that receives block-read/write commands on behalf of the underlying disk driver. This device will delegate reads and writes to the disk driver, but it will keep a list of commands that are "outstanding," that is, reads that the disk driver has not completed, and writes that have not "hit the platter," so to speak. Following disk re-attachment, the virtual block device replays its list of outstanding commands. A correct solution will not replay commands to the wrong disk if the removable was replaced instead of re-attached. Provide a character device for userland to read indications that a disk in use was abruptly detached.
+Make NetBSD behave gracefully when a "live" USB/FireWire disk drive is accidentally detached and re-attached by, for example, creating a virtual block device that receives block-read/write commands on behalf of the underlying disk driver.
+
+This device will delegate reads and writes to the disk driver, but it will keep a list of commands that are "outstanding," that is, reads that the disk driver has not completed, and writes that have not "hit the platter," so to speak.
+
+
+Milestones:
+
+* Provide a character device for userland to read indications that a disk in use was abruptly detached.
+* Following disk re-attachment, the virtual block device replays its list of outstanding commands. A correct solution will not replay commands to the wrong disk if the removable was replaced instead of re-attached.
 
 Open questions: Prior art? Isn't this how the Amiga worked? How will this interact with mount/unmount—is there a use-count on devices? Can you leverage "wedges" in your solution? Does any/most/all removable storage indicate reliably when a block written has actually reached the medium?
 """
Index: wikisrc/projects/project/fast-time.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fast-time.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/fast-time.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/fast-time.mdwn	20 Feb 2015 16:42:42 -0000	1.3
@@ -15,7 +15,14 @@
 duration="3 months"
 
 description="""
-Design and implement a mechanism that allows for fast user level access to kernel time data structures for NetBSD. For certain types of small data structures the system call overhead is significant. This is especially true for frequently invoked system calls like [clock_gettime(2)](http://netbsd.gw.com/cgi-bin/man-cgi?clock_gettime+2+NetBSD-5.1+i386) and [gettimeofday(2)](http://netbsd.gw.com/cgi-bin/man-cgi?gettimeofday+2+NetBSD-5.1+i386). With the availability of user level readable high frequency counters it is possible to create fast implementations for precision time reading. Optimizing clock_gettime(2) and alike will reduce the strain from applications frequently calling these system calls and improves timing information quality for applications like NTP. The implementation would be based on a to be modified version of the timecounters implementation in NetBSD.
+Design and implement a mechanism that allows for fast user level access to kernel time data structures for NetBSD. For certain types of small data structures the system call overhead is significant. This is especially true for frequently invoked system calls like [clock_gettime(2)](http://netbsd.gw.com/cgi-bin/man-cgi?clock_gettime+2+NetBSD-5.1+i386) and [gettimeofday(2)](http://netbsd.gw.com/cgi-bin/man-cgi?gettimeofday+2+NetBSD-5.1+i386). With the availability of user level readable high frequency counters it is possible to create fast implementations for precision time reading. Optimizing clock_gettime(2) and alike will reduce the strain from applications frequently calling these system calls and improves timing information quality for applications like NTP. The implementation would be based on a to-be-modified version of the timecounters implementation in NetBSD.
+
+Milestones:
+
+* Produce optimizations for clock_gettime
+* Produce optimizations for gettimeofday
+* Show benchmarks before and after
+* start evolving timecounters in NetBSD, demonstrating your improvements
 
 See also the [Paper on Timecounters by Poul-Henning Kamp](http://phk.freebsd.dk/pubs/timecounter.pdf).
 """
Index: wikisrc/projects/project/fs-services.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fs-services.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/fs-services.mdwn	27 Feb 2014 07:20:54 -0000	1.4
+++ wikisrc/projects/project/fs-services.mdwn	20 Feb 2015 16:42:42 -0000	1.5
@@ -19,7 +19,7 @@
 
 This project investigates the first steps in turning file systems into network-transparent services by making it possible to mount any kernel file system type from any location on the network. The file system components to be used are [puffs](http://www.netbsd.org/docs/puffs/) and [rump](http://www.netbsd.org/docs/puffs/rump.html). puffs is used to forward local file system requests from the kernel to userspace and rump is used to facilitate running the kernel file system in userspace as a service daemon.
 
-The subtasks are the following:
+The milestones are the following:
 
 * Write the necessary code to be able to forward requests from one source to another. This involves most likely reworking a bit of the libpuffs option parsing code and creating an puffs client, say, mount_puffs to be able to forward requests from one location to another. The puffs protocol should be extended to include the necessary new features or another protocol defined.
 
Index: wikisrc/projects/project/improved-automounter-support.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/improved-automounter-support.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/projects/project/improved-automounter-support.mdwn	18 Feb 2015 20:46:18 -0000	1.9
+++ wikisrc/projects/project/improved-automounter-support.mdwn	20 Feb 2015 16:42:42 -0000	1.10
@@ -20,7 +20,13 @@
 * 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. FreeBSD has already implemented autofs, so we could port theirs and that should significantly simplify the project. 
+The milestones of this project are:
+
+* implement a new automounter solution which has configurable mount points
+* improve high I/O
+* show benchmarks and implement automated tests
+
+This could either be done via a Solaris/Linux compatible autofs(4) full in-kernel file system. FreeBSD has already implemented autofs, so we could port theirs and that should significantly simplify the project. 
 """
 ]]
 
Index: wikisrc/projects/project/inetd-enhancements.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/inetd-enhancements.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/projects/project/inetd-enhancements.mdwn	18 Feb 2015 20:49:57 -0000	1.4
+++ wikisrc/projects/project/inetd-enhancements.mdwn	20 Feb 2015 16:42:42 -0000	1.5
@@ -15,19 +15,21 @@
 duration="3 months"
 
 description="""
-The following features should be added to inetd:
+Enhance inetd in NetBSD
+
+Primary milestones:
 
 - Prefork: Support pre-forking multiple children and keeping them alive for multiple invocations.
 - Per service configuration file: Add a per-service configuration file similar to xinetd.
 - Make the rate-limiting feature configurable on a per-service basis.
 - Improve the logging and make logging modes configurable on a per-service basis.
-- Integrate with the new blacklist daemon.
 
-Perhaps also some of the following:
+Nice to have:
 
 - Add include directives to the configuration language to allow service definitions to be installed in /usr/share or /usr/pkg/share.
 - Add a separate way to turn services on and off, so they can be defined statically (such as in /usr/share) and turned on and off from /etc.
 - Allow non-privileged users to add/remove/change their own services using a separate utility.
+- Integrate with the new blacklist daemon.
 - Configuration compatibility for systemd socket activations
 
 """
Index: wikisrc/projects/project/isdn-nt-asterisk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/isdn-nt-asterisk.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/isdn-nt-asterisk.mdwn	6 Nov 2011 14:48:47 -0000	1.2
+++ wikisrc/projects/project/isdn-nt-asterisk.mdwn	20 Feb 2015 16:42:42 -0000	1.3
@@ -15,7 +15,11 @@
 duration="3 months"
 
 description="""
-This project has two subprojects: add support for the NT (network) side of ISDN to the NetBSD ISDN stack and interface ISDN (in NT mode) to the [Asterisk PBX](http://asterisk.org/), which would allow using existing ISDN PBXes as SIP/VoIP phones, as well as easier testing of new ISDN card drivers.
+This project has three milestones:
+
+* add support for the NT (network) side of ISDN to the NetBSD ISDN stack
+* interface ISDN (in NT mode) to the [Asterisk PBX](http://asterisk.org/), which would allow using existing ISDN PBXes as SIP/VoIP phones
+* show this makes it easier to test new ISDN card drivers
 
 Previous work in this area can be found at the [alternative ISDN driver site](http://www.turbocat.net/~hselasky/isdn4bsd/).
 """

Index: wikisrc/projects/project/u-boot-pkgsrc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/u-boot-pkgsrc.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/u-boot-pkgsrc.mdwn	20 Feb 2015 16:32:13 -0000	1.1
+++ wikisrc/projects/project/u-boot-pkgsrc.mdwn	20 Feb 2015 16:38:57 -0000	1.2
@@ -33,6 +33,15 @@
 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).
+
+Deliverables of this project:
+
+1. Make U-Boot build on NetBSD, using a bsd style makefile and environment variables pointing at ${TOOLDIR}
+2. Discuss the changes needed for [1] with U-Boot upstream developers, follow their advice and try to upstream the changes
+3. Create a pkgsrc entry for the native U-Boot
+4. Add a FFS module to U-Boot, using NetBSD system headers
+
+Items [2] and [4] will not be required for GSoC success.
 """
 ]]
 

rename projects/project/u-boot__95__pkgsrc.mdwn to projects/project/u-boot-pkgsrc.mdwn
--- /dev/null	2015-02-20 16:32:00.000000000 +0000
+++ wikisrc/projects/project/u-boot-pkgsrc.mdwn	2015-02-20 16:32:23.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="userland"
+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]]
--- wikisrc/projects/project/u-boot__95__pkgsrc.mdwn	2015-02-20 16:32:23.000000000 +0000
+++ /dev/null	2015-02-20 16:32:00.000000000 +0000
@@ -1,39 +0,0 @@
-[[!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="userland"
-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/atf-sql-backend.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/atf-sql-backend.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/atf-sql-backend.mdwn	19 Feb 2015 19:43:46 -0000	1.1
+++ wikisrc/projects/project/atf-sql-backend.mdwn	19 Feb 2015 19:45:45 -0000	1.2
@@ -23,7 +23,7 @@
 Creating a suitable database schema and the xml loader/upload tool is the first half.
 
 Second part is using the collected results to display some nice web pages showing statistics and allowing dedicated queries, comparable
-to then query pages of typical bug tracking systems.
+to the query pages of typical bug tracking systems.
 
 This project has the following milestones, in this order:
 
@@ -33,7 +33,7 @@
 4. Enhance the upload tool (or create a second variant) for Kuya output. This part is optional
 5. Document the database schema, web site setup, and tool created.
 
-A huge set of ATF xml data will be provided, we assume that the student creates the database enviroment for local testing themselves.
+A huge set of ATF xml data will be provided, we assume that the student creates the database environment for local testing themselves.
 
 The result is planed to be deployed on TNF servers later, so it is of direct use for the community.
 This deployment is not part of the GSoC timeline.

rename projects/project/atf__95__sql__95__backend.mdwn to projects/project/atf-sql-backend.mdwn
--- /dev/null	2015-02-19 19:40:45.000000000 +0000
+++ wikisrc/projects/project/atf-sql-backend.mdwn	2015-02-19 19:43:48.000000000 +0000
@@ -0,0 +1,43 @@
+[[!template id=project
+
+title="Create an SQL backend and statisticics/query page for ATF test results"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Martin Husemann](mailto:martin@NetBSD.org)
+"""
+
+category="userland"
+difficulty="medium"
+duration="3 months"
+
+description="""
+We are currently running various regular [tests](http://releng.netbsd.org/test-results.html), both on emulators and real hardware.
+The results are generated in ATF (or maybe sometime later in Kuya) raw XML output format and then transformed via xslt into html.
+This is good enough to display single test run results, but does not provide any overview or comparison options accross different test runs or architectures.
+
+The target of this project is to provide a simmple 'upload' utility, that takes the xml input and inserts it into a remote PostgresSQL database.
+Creating a suitable database schema and the xml loader/upload tool is the first half.
+
+Second part is using the collected results to display some nice web pages showing statistics and allowing dedicated queries, comparable
+to then query pages of typical bug tracking systems.
+
+This project has the following milestones, in this order:
+
+1. Create and test a database schema (suitable for multiple architectures, and later migration to Kuya)
+2. Create a tool to read the ATF xml data and insert it into a database. This will be the half term milestone.
+3. Create a web site providing basic browsing/search options for the database
+4. Enhance the upload tool (or create a second variant) for Kuya output. This part is optional
+5. Document the database schema, web site setup, and tool created.
+
+A huge set of ATF xml data will be provided, we assume that the student creates the database enviroment for local testing themselves.
+
+The result is planed to be deployed on TNF servers later, so it is of direct use for the community.
+This deployment is not part of the GSoC timeline.
+"""
+]]
+
+[[!tag gsoc]]
--- wikisrc/projects/project/atf__95__sql__95__backend.mdwn	2015-02-19 19:43:48.000000000 +0000
+++ /dev/null	2015-02-19 19:40:45.000000000 +0000
@@ -1,43 +0,0 @@
-[[!template id=project
-
-title="Create an SQL backend and statisticics/query page for ATF test results"
-
-contact="""
-[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
-"""
-
-mentors="""
-[Martin Husemann](mailto:martin@NetBSD.org)
-"""
-
-category="userland"
-difficulty="medium"
-duration="3 months"
-
-description="""
-We are currently running various regular [tests](http://releng.netbsd.org/test-results.html), both on emulators and real hardware.
-The results are generated in ATF (or maybe sometime later in Kuya) raw XML output format and then transformed via xslt into html.
-This is good enough to display single test run results, but does not provide any overview or comparison options accross different test runs or architectures.
-
-The target of this project is to provide a simmple 'upload' utility, that takes the xml input and inserts it into a remote PostgresSQL database.
-Creating a suitable database schema and the xml loader/upload tool is the first half.
-
-Second part is using the collected results to display some nice web pages showing statistics and allowing dedicated queries, comparable
-to then query pages of typical bug tracking systems.
-
-This project has the following milestones, in this order:
-
-1. Create and test a database schema (suitable for multiple architectures, and later migration to Kuya)
-2. Create a tool to read the ATF xml data and insert it into a database. This will be the half term milestone.
-3. Create a web site providing basic browsing/search options for the database
-4. Enhance the upload tool (or create a second variant) for Kuya output. This part is optional
-5. Document the database schema, web site setup, and tool created.
-
-A huge set of ATF xml data will be provided, we assume that the student creates the database enviroment for local testing themselves.
-
-The result is planed to be deployed on TNF servers later, so it is of direct use for the community.
-This deployment is not part of the GSoC timeline.
-"""
-]]
-
-[[!tag gsoc]]

Index: wikisrc/projects/project/atf__95__sql__95__backend.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/atf__95__sql__95__backend.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/atf__95__sql__95__backend.mdwn	19 Feb 2015 19:39:24 -0000	1.1
+++ wikisrc/projects/project/atf__95__sql__95__backend.mdwn	19 Feb 2015 19:40:57 -0000	1.2
@@ -1,6 +1,6 @@
 [[!template id=project
 
-title="Create an SQL backend and statisticics/query page"
+title="Create an SQL backend and statisticics/query page for ATF test results"
 
 contact="""
 [tech-userlevel](mailto:tech-userlevel@NetBSD.org)

--- /dev/null	2015-02-19 19:32:00.000000000 +0000
+++ wikisrc/projects/project/atf__95__sql__95__backend.mdwn	2015-02-19 19:39:29.000000000 +0000
@@ -0,0 +1,43 @@
+[[!template id=project
+
+title="Create an SQL backend and statisticics/query page"
+
+contact="""
+[tech-userlevel](mailto:tech-userlevel@NetBSD.org)
+"""
+
+mentors="""
+[Martin Husemann](mailto:martin@NetBSD.org)
+"""
+
+category="userland"
+difficulty="medium"
+duration="3 months"
+
+description="""
+We are currently running various regular [tests](http://releng.netbsd.org/test-results.html), both on emulators and real hardware.
+The results are generated in ATF (or maybe sometime later in Kuya) raw XML output format and then transformed via xslt into html.
+This is good enough to display single test run results, but does not provide any overview or comparison options accross different test runs or architectures.
+
+The target of this project is to provide a simmple 'upload' utility, that takes the xml input and inserts it into a remote PostgresSQL database.
+Creating a suitable database schema and the xml loader/upload tool is the first half.
+
+Second part is using the collected results to display some nice web pages showing statistics and allowing dedicated queries, comparable
+to then query pages of typical bug tracking systems.
+
+This project has the following milestones, in this order:
+
+1. Create and test a database schema (suitable for multiple architectures, and later migration to Kuya)
+2. Create a tool to read the ATF xml data and insert it into a database. This will be the half term milestone.
+3. Create a web site providing basic browsing/search options for the database
+4. Enhance the upload tool (or create a second variant) for Kuya output. This part is optional
+5. Document the database schema, web site setup, and tool created.
+
+A huge set of ATF xml data will be provided, we assume that the student creates the database enviroment for local testing themselves.
+
+The result is planed to be deployed on TNF servers later, so it is of direct use for the community.
+This deployment is not part of the GSoC timeline.
+"""
+]]
+
+[[!tag gsoc]]

Clarify terminology.
Index: wikisrc/kernel_debugging_with_qemu.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/kernel_debugging_with_qemu.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/kernel_debugging_with_qemu.mdwn	19 Feb 2015 08:32:23 -0000	1.8
+++ wikisrc/kernel_debugging_with_qemu.mdwn	19 Feb 2015 09:37:14 -0000	1.9
@@ -61,7 +61,7 @@
 ## Booting the VMs
 
 Next, start two qemu virtual machines, one to run the kernel being
-debugged (the "kgdb target") and another to run gdb (the "kgdb host").
+debugged (the "target VM") and another to run gdb (the "gdb VM").
 
 The two VMs could be run on separate physical machines, but in this
 example, they are run on the same physical machine and share the same
@@ -69,7 +69,7 @@
 option to qemu, which ensures that the disk image is not written to by
 either VM.
 
-First start the kgdb target, enabling qemu's built-in GDB target stub
+First start the target VM, enabling qemu's built-in GDB target stub
 on TCP port 1234:
 
 [[!template  id=programlisting text="""
@@ -80,20 +80,20 @@
 target, make sure incoming connections on port 1234 are blocked in
 your firewall.
 
-In a second terminal window, start the kgdb host:
+In a second terminal window, start the gdb VM:
 
 [[!template  id=programlisting text="""
  $ qemu-system-i386 -nographic -snapshot -hda work/wd0.img
 """]]
 
-Log in to the kgdb host as root and set up the network:
+Log in to the gdb VM as root and set up the network:
 
 [[!template  id=programlisting text="""
  login: root
  # dhcpcd
 """]]
 
-Start gdb on the kgdb host and connect to the target:
+Start gdb on the gdb VM and connect to the target:
 
 [[!template  id=programlisting text="""
  # gdb /netbsd
@@ -101,7 +101,7 @@
 """]]
 
 where my.host.name is the domain name or IP address of the
-physical machine running the kgdb target qemu VM.
+host system.
 
 Now you should be able to get a stack trace and start debugging
 with full debug symbols and access to the source code:

VMs, not VMS
Index: wikisrc/kernel_debugging_with_qemu.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/kernel_debugging_with_qemu.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/kernel_debugging_with_qemu.mdwn	18 Feb 2015 16:23:11 -0000	1.7
+++ wikisrc/kernel_debugging_with_qemu.mdwn	19 Feb 2015 08:32:23 -0000	1.8
@@ -63,7 +63,7 @@
 Next, start two qemu virtual machines, one to run the kernel being
 debugged (the "kgdb target") and another to run gdb (the "kgdb host").
 
-The two VMS could be run on separate physical machines, but in this
+The two VMs could be run on separate physical machines, but in this
 example, they are run on the same physical machine and share the same
 hard disk image.  This sharing is made possible by the "-snapshot"
 option to qemu, which ensures that the disk image is not written to by

Fix URL of presentation pages
Index: wikisrc/events.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/events.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/events.mdwn	26 Jun 2014 13:35:19 -0000	1.10
+++ wikisrc/events.mdwn	19 Feb 2015 07:06:37 -0000	1.11
@@ -3,7 +3,7 @@
 [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/).
+[presentation pages](http://www.netbsd.org/gallery/presentations/).
 
 [Conference Attendance and Organizations](conferences)
 

add gsoc tag
Index: wikisrc/projects/project/raidframe-raid6.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/raidframe-raid6.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/raidframe-raid6.mdwn	18 Feb 2015 22:51:27 -0000	1.1
+++ wikisrc/projects/project/raidframe-raid6.mdwn	18 Feb 2015 22:51:55 -0000	1.2
@@ -18,3 +18,5 @@
 Test and debug the RAID 6 implementation in RAIDframe.
 """
 ]]
+
+[[!tag gsoc]]

<christos> another SoC: test raid 6 on raidframe and fix it.
--- /dev/null	2015-02-18 22:50:00.000000000 +0000
+++ wikisrc/projects/project/raidframe-raid6.mdwn	2015-02-18 22:51:31.000000000 +0000
@@ -0,0 +1,20 @@
+[[!template id=project
+
+title="raid 6 in RAIDframe"
+
+contact="""
+[tech-kern](mailto:tech-kern@NetBSD.org)
+"""
+
+mentors="""
+[Christos Zoulas](mailto:christos@NetBSD.org)
+"""
+
+category="filesystems"
+difficulty="medium"
+duration="unknown"
+
+description="""
+Test and debug the RAID 6 implementation in RAIDframe.
+"""
+]]

mention systemd
Index: wikisrc/projects/project/inetd-enhancements.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/inetd-enhancements.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/inetd-enhancements.mdwn	16 Feb 2015 07:05:15 -0000	1.3
+++ wikisrc/projects/project/inetd-enhancements.mdwn	18 Feb 2015 20:49:57 -0000	1.4
@@ -28,6 +28,7 @@
 - Add include directives to the configuration language to allow service definitions to be installed in /usr/share or /usr/pkg/share.
 - Add a separate way to turn services on and off, so they can be defined statically (such as in /usr/share) and turned on and off from /etc.
 - Allow non-privileged users to add/remove/change their own services using a separate utility.
+- Configuration compatibility for systemd socket activations
 
 """
 ]]

Remove me as a mentor.
Index: wikisrc/projects/project/improved-automounter-support.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/improved-automounter-support.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/projects/project/improved-automounter-support.mdwn	18 Feb 2015 20:18:19 -0000	1.8
+++ wikisrc/projects/project/improved-automounter-support.mdwn	18 Feb 2015 20:46:18 -0000	1.9
@@ -8,7 +8,6 @@
 """
 
 mentors="""
-[Matthias Scheler](mailto:tron@NetBSD.org)
 """
 
 category="kernel"

removed
--- wikisrc/projects/project/ptyfs_multiple_mounts.mdwn	2015-02-18 20:19:27.000000000 +0000
+++ /dev/null	2015-02-18 20:16:00.000000000 +0000
@@ -1,30 +0,0 @@
-[[!template id=project
-
-title="Enhance ptyfs to handle multiple instances"
-
-contact="""
-[tech-kern](mailto:tech-kern@NetBSD.org)
-"""
-
-mentors="""
-[Christos Zoulas](mailto:christos@NetBSD.org)
-"""
-
-category="kernel"
-difficulty="easy"
-duration="3 months"
-
-description="""
-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 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 on each mount point (without gaps) is feasible without too much recoding, and implement it.
-"""
-]]
-
-[[!tag gsoc]]

Add a comment