Recent changes to this wiki:

Index: wikisrc/projects/project/donations.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/donations.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/donations.mdwn	10 Mar 2022 16:19:03 -0000	1.1
+++ wikisrc/projects/project/donations.mdwn	18 Mar 2024 22:30:42 -0000	1.2
@@ -10,11 +10,14 @@
 [Christos Zoulas](mailto:christos@NetBSD.org)
 """
 
+done_by="Vivek Kumar Sah, Ahmet Goksu"
 category="misc"
 difficulty="medium"
 duration="350h"
 
+
 description="""
+***Update***: This project has been completed and it is currently being integrated to the donation system.
 
 Currently electronic donations from Paypal and Stripe are emailed
 to Request Tracker. A ticket gets opened and each donation is

Update test status and timeline, note RC6
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.108
retrieving revision 1.109
diff -u -r1.108 -r1.109
--- wikisrc/releng/netbsd-10.mdwn	5 Mar 2024 10:49:38 -0000	1.108
+++ wikisrc/releng/netbsd-10.mdwn	13 Mar 2024 19:20:06 -0000	1.109
@@ -2,16 +2,15 @@
 
 ## Hard Release Blockers
 
-Open bind(8) issues require fixing.
+* __NONE__
 
 We consider the magnitude of DRM/KMS bugs (see below) as bad, but this is
 as good as it will realistically get for a 10.0 release.
 
 ## Current status and timeline
 
-* [10.0 release candidate 5](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
-* Unfortunately the new named(8) version has a few issues, which requires fixing and will cause a RC6, planned Mar 10
-* The final 10.0 release is planned around Mar 25
+* [10.0 release candidate 6](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
+* The final 10.0 release is planned around Mar 22 - 25
 
 
 ## Showstopper bugs and PRs
@@ -133,19 +132,19 @@
   <tbody>
     <tr>
         <td><a href="//www.netbsd.org/~martin/aarch64-atf-netbsd10/">aarch64</a>, real hardware</td>
-        <td>2024-02-29</td><td>2</td><td> </td>
+        <td>2024-03-12</td><td>1</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/sparc64-atf-netbsd10/">sparc64</a>, real hardware</td>
-        <td>2024-02-28</td><td>4</td><td> </td>
+        <td>2024-03-13</td><td>5</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/netbsd-10/">xen</a></td>
-        <td>2024-03-01</td> <td>3</td><td></td>
+        <td>2024-03-06</td> <td>4</td><td></td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/evbarm-atf-netbsd10/">evbarm</a>, real hardware</td>
-        <td>2024-02-28</td><td>77</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
+        <td>2024-03-12</td><td>80</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
     </tr>
   </tbody>
 </table>

move past:Open Source Conference 2024 Tokyo/Spring NetBSD Booth thanx tsutsui@ san for ATARI TT030
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.143
retrieving revision 1.144
diff -u -r1.143 -r1.144
--- wikisrc/users/jun.mdwn	6 Mar 2024 06:21:04 -0000	1.143
+++ wikisrc/users/jun.mdwn	11 Mar 2024 04:31:50 -0000	1.144
@@ -4,14 +4,6 @@
 
 #2024
 
-
-## Open Source Conference 2024 Tokyo/Spring NetBSD Booth
-- Booth: 2024 Mar.10 Sun 10:00-16:00 JST (UTC+9)
-- Toritsu Sangyo Boueki Center Taito-kan [[https://www.sanbo.metro.tokyo.lg.jp/taito/access/]] Asakusa,Tokyo
-- [[https://event.ospn.jp/osc2024-spring/]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2024tokyospring.pdf]]
-- togetter [[https://togetter.com/li/2314715]]
-
 ## Open Source Conference 2024 Nagoya NetBSD Booth&BoF
 - Booth: 2024 May.25 Sat XX:00-XX:00 JST (UTC+9)
 - BoF:  2024 May.25 Sat XX:00-XX:45 JST (UTC+9)
@@ -32,6 +24,13 @@
 
 # Past Events in 2024
 
+## Open Source Conference 2024 Tokyo/Spring NetBSD Booth
+- Booth: 2024 Mar.10 Sun 10:00-16:00 JST (UTC+9)
+- Toritsu Sangyo Boueki Center Taito-kan [[https://www.sanbo.metro.tokyo.lg.jp/taito/access/]] Asakusa,Tokyo
+- [[https://event.ospn.jp/osc2024-spring/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2024tokyospring.pdf]]
+- togetter [[https://togetter.com/li/2314715]]
+
 ## Open Source Conference 2024 Online/Spring NetBSD BoF
 - Zoom/YoutubeLive BoF:  2024 Mar.2 Sat 14:00-14:45 JST (UTC+9)
 - [[https://event.ospn.jp/osc2024-online-spring/]]

move past and add Youtube: Open Source Conference 2024 Online/Spring NetBSD BoF
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.142
retrieving revision 1.143
diff -u -r1.142 -r1.143
--- wikisrc/users/jun.mdwn	29 Jan 2024 22:02:29 -0000	1.142
+++ wikisrc/users/jun.mdwn	6 Mar 2024 06:21:04 -0000	1.143
@@ -4,18 +4,13 @@
 
 #2024
 
-## Open Source Conference 2024 Online/Spring NetBSD BoF
-- Zoom/YoutubeLive BoF:  2024 Mar.2 Sat 14:00-14:45 JST (UTC+9)
-- [[https://event.ospn.jp/osc2024-online-spring/]]
-- Tour Guide [[]]
-- togetter [[]]
 
 ## Open Source Conference 2024 Tokyo/Spring NetBSD Booth
 - Booth: 2024 Mar.10 Sun 10:00-16:00 JST (UTC+9)
 - Toritsu Sangyo Boueki Center Taito-kan [[https://www.sanbo.metro.tokyo.lg.jp/taito/access/]] Asakusa,Tokyo
 - [[https://event.ospn.jp/osc2024-spring/]]
-- Tour Guide [[]]
-- togetter [[]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2024tokyospring.pdf]]
+- togetter [[https://togetter.com/li/2314715]]
 
 ## Open Source Conference 2024 Nagoya NetBSD Booth&BoF
 - Booth: 2024 May.25 Sat XX:00-XX:00 JST (UTC+9)
@@ -35,9 +30,15 @@
 ## Nagoya *BSD Users' Group monthly meeting
 - [[http://nagoya.bug.gr.jp/]]
 
-
 # Past Events in 2024
 
+## Open Source Conference 2024 Online/Spring NetBSD BoF
+- Zoom/YoutubeLive BoF:  2024 Mar.2 Sat 14:00-14:45 JST (UTC+9)
+- [[https://event.ospn.jp/osc2024-online-spring/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2024tokyospring.pdf]]
+- togetter [[https://togetter.com/li/2314715]]
+- Youtube [[https://youtu.be/qiQ_op6ro00]]
+
 ## Open Source Conference 2024 Osaka NetBSD Booth&BoF
 - Booth: 2024 Jan.27 Sat 10:00-16:00 JST (UTC+9)
 - BoF:  2024 Jan.27 Sat 10:00-10:45 JST (UTC+9)

Update test status and timeline
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.107
retrieving revision 1.108
diff -u -r1.107 -r1.108
--- wikisrc/releng/netbsd-10.mdwn	3 Mar 2024 15:36:27 -0000	1.107
+++ wikisrc/releng/netbsd-10.mdwn	5 Mar 2024 10:49:38 -0000	1.108
@@ -2,23 +2,22 @@
 
 ## Hard Release Blockers
 
-Waiting for security pullups (see below).
+Open bind(8) issues require fixing.
 
 We consider the magnitude of DRM/KMS bugs (see below) as bad, but this is
 as good as it will realistically get for a 10.0 release.
 
 ## Current status and timeline
 
-* [10.0 release candidate 4](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
-* A few security fixes (for 3rd party applications, bind(8) and wpa_supplicant(8)) just landed in -current and will be pulled up to netbsd-10 afer being tested there for a few days. We have not finally decided if this will force a fifth(!) release candidate - but tend to avoid the extra release candidate step. 
-* The 10.0 release is planned before the end of February.
+* [10.0 release candidate 5](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
+* Unfortunately the new named(8) version has a few issues, which requires fixing and will cause a RC6, planned Mar 10
+* The final 10.0 release is planned around Mar 25
 
 
 ## Showstopper bugs and PRs
 
 * **Any issues found by [syzbot](https://syzkaller.appspot.com/netbsd) may potentially crash
   the kernel and should be investigated and fixed.**
-* [[!template id=pr number=55272]]: userland watchdog processes may be outstalled (regression since -9)
 * ~~[[!template id=pr number=55466]]: rump_server processes busy looping can stall a machine (regression since -9)~~
 * ~~[[!template id=pr number=56329]]: nvme(4) takes long time to umount~~ analyzed: the number of dirty vnodes has been bumped, no real performance regression
 *  ~~autoconfig API changes need to be backed out or made type-safe see this [backout request](https://mail-index.netbsd.org/tech-kern/2021/05/11/msg027374.html)~~
@@ -26,7 +25,6 @@
 * ~~[[!template id=pr number=56713]]: kqueue/kevent does not work with null mounts~~
 * ~~[[!template id=pr number=55707]]: xcalls storm or pgdaemon high CPU consumption~~
 * ~~[[!template id=pr number=56737]]: WDCTL_RST errors in 9.99.92 and 9.99.93~~
-* [[!template id=pr number=57127]]: ptyfs fails
 
 ## Open issues with new DRM/KMS
 
@@ -53,6 +51,7 @@
 
 ## Regressions since netbsd-9
 
+* [[!template id=pr number=55272]]: userland watchdog processes may be outstalled
 * ~~[[!template id=pr number=54913]]: fexecve(2) panics in chroot(8)~~
 * ~~[[!template id=pr number=55370]]: Invalid modification/connection time with mount_null(8)~~
 * ~~[[!template id=pr number=55489]]: Infinite loop in "rump ifconfig bridge0 create"~~
@@ -72,6 +71,7 @@
 
 ## PRs worth fixing
 
+* [[!template id=pr number=57127]]: ptyfs fails
 * ~~[[!template id=pr number=51734]]: hdaudio(4) "RIRB timeout" interrupt storm on boot~~
 * ~~[[!template id=pr number=53173]]: "go test net/http" locks up the machine~~
 * [[!template id=pr number=53155]]: Wedge after <12h uptime when >2 bnx network interfaces in use
@@ -133,19 +133,19 @@
   <tbody>
     <tr>
         <td><a href="//www.netbsd.org/~martin/aarch64-atf-netbsd10/">aarch64</a>, real hardware</td>
-        <td>2024-02-08</td><td>1</td><td> </td>
+        <td>2024-02-29</td><td>2</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/sparc64-atf-netbsd10/">sparc64</a>, real hardware</td>
-        <td>2024-02-09</td><td>4</td><td> </td>
+        <td>2024-02-28</td><td>4</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/netbsd-10/">xen</a></td>
-        <td>2024-02-09</td> <td>3</td><td></td>
+        <td>2024-03-01</td> <td>3</td><td></td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/evbarm-atf-netbsd10/">evbarm</a>, real hardware</td>
-        <td>2024-02-08</td><td>77</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
+        <td>2024-02-28</td><td>77</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
     </tr>
   </tbody>
 </table>

releng/netbsd-10: cross off a couple closed PRs
Not sure the rest listed under showstoppers are actually
showstoppers.
Members: 
	releng/netbsd-10.mdwn:1.106->1.107 

Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.106
retrieving revision 1.107
diff -u -r1.106 -r1.107
--- wikisrc/releng/netbsd-10.mdwn	21 Feb 2024 17:08:43 -0000	1.106
+++ wikisrc/releng/netbsd-10.mdwn	3 Mar 2024 15:36:27 -0000	1.107
@@ -22,10 +22,10 @@
 * ~~[[!template id=pr number=55466]]: rump_server processes busy looping can stall a machine (regression since -9)~~
 * ~~[[!template id=pr number=56329]]: nvme(4) takes long time to umount~~ analyzed: the number of dirty vnodes has been bumped, no real performance regression
 *  ~~autoconfig API changes need to be backed out or made type-safe see this [backout request](https://mail-index.netbsd.org/tech-kern/2021/05/11/msg027374.html)~~
-* [[!template id=pr number=56653]]: kernel crash in ipv6 fragment reassembly
+* ~~[[!template id=pr number=56653]]: kernel crash in ipv6 fragment reassembly~~
 * ~~[[!template id=pr number=56713]]: kqueue/kevent does not work with null mounts~~
 * ~~[[!template id=pr number=55707]]: xcalls storm or pgdaemon high CPU consumption~~
-* [[!template id=pr number=56737]]: WDCTL_RST errors in 9.99.92 and 9.99.93
+* ~~[[!template id=pr number=56737]]: WDCTL_RST errors in 9.99.92 and 9.99.93~~
 * [[!template id=pr number=57127]]: ptyfs fails
 
 ## Open issues with new DRM/KMS

mention how to unblock hosts
Index: wikisrc/tutorials/setting_up_blocklistd.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/setting_up_blocklistd.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/setting_up_blocklistd.mdwn	27 Feb 2024 08:19:16 -0000	1.4
+++ wikisrc/tutorials/setting_up_blocklistd.mdwn	1 Mar 2024 21:18:29 -0000	1.5
@@ -83,3 +83,10 @@
 You can check the current state with
 
 	blocklistctl dump -a
+
+## Unblocking hosts
+
+Find the host in the `blocklistctl dump -a` output. The second column
+(`id`) is a hex number. Pass this as argument to npfctl:
+
+	/sbin/npfctl rule blocklistd rem-id $ID

Remove my name as mentor
Index: wikisrc/projects/project/linux_timer.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/linux_timer.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/linux_timer.mdwn	12 Mar 2022 18:27:25 -0000	1.3
+++ wikisrc/projects/project/linux_timer.mdwn	29 Feb 2024 09:01:56 -0000	1.4
@@ -6,10 +6,6 @@
 [tech-kern](mailto:tech-kern@NetBSD.org)
 """
 
-mentors="""
-[Stephen Borrill](mailto:sborrill@NetBSD.org)
-"""
-
 category="kernel"
 difficulty="easy"
 duration="350h"

manual npflog creation is necessary
Index: wikisrc/tutorials/setting_up_blocklistd.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/setting_up_blocklistd.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/tutorials/setting_up_blocklistd.mdwn	9 Feb 2024 02:48:47 -0000	1.3
+++ wikisrc/tutorials/setting_up_blocklistd.mdwn	27 Feb 2024 08:19:16 -0000	1.4
@@ -23,7 +23,7 @@
 
 	ifconfig npflog0 create
 
-If this doesn't happen automatically after a reboot, like it should, do:
+So this happens after a reboot too, you have to run:
 
 	echo create > /etc/ifconfig.npflog0
 

Added a comment: distcc and USE_CWRAPPERS
--- /dev/null	2024-02-22 05:19:02.876119365 +0000
+++ wikisrc/tutorials/pkgsrc/build_ccache_distcc/comment_2_6f170c154512e0bba26a2dd5729c0b7d._comment	2024-02-22 05:19:54.909496534 +0000
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="imil"
+ subject="distcc and USE_CWRAPPERS"
+ date="2024-02-22T05:19:08Z"
+ content="""
+As mentionned in this post <https://mail-index.netbsd.org/netbsd-users/2017/06/29/msg019761.html>, `distcc`does not seem work with cwrappers, if the build work is not showing in other machine than `localhost`, try adding
+
+```
+USE_CWRAPPERS=no
+```
+
+to `/etc/mk.conf`
+"""]]

Fix a typo.
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.105
retrieving revision 1.106
diff -u -r1.105 -r1.106
--- wikisrc/releng/netbsd-10.mdwn	14 Feb 2024 10:55:00 -0000	1.105
+++ wikisrc/releng/netbsd-10.mdwn	21 Feb 2024 17:08:43 -0000	1.106
@@ -11,7 +11,7 @@
 
 * [10.0 release candidate 4](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
 * A few security fixes (for 3rd party applications, bind(8) and wpa_supplicant(8)) just landed in -current and will be pulled up to netbsd-10 afer being tested there for a few days. We have not finally decided if this will force a fifth(!) release candidate - but tend to avoid the extra release candidate step. 
-* The 10.0 release is planed before the end of February.
+* The 10.0 release is planned before the end of February.
 
 
 ## Showstopper bugs and PRs

RPI: adjust trad/UEFI boot, xhci
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.154
retrieving revision 1.155
diff -u -r1.154 -r1.155
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	5 Feb 2024 00:58:20 -0000	1.154
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	18 Feb 2024 18:32:33 -0000	1.155
@@ -50,7 +50,7 @@
 
 ## NetBSD 10
 
- - RPI4 general support
+ - RPI4 general support (but there are issues)
  - RPI4 ethernet (Broadcom GENETv5) (but the man page for genet(4) is missing)
  - RPI3/RPI4 audio with aarch64 kernels (Previously the driver was only included with 32-bit (ARMv7/ARMv6) kernels, and now works [due to dma-ranges](//mail-index.NetBSD.org/source-changes-d/2021/01/22/msg013133.html).
  - builtin bluetooth on RPI3 (RPI0W? RPI4?) 
@@ -73,6 +73,8 @@
  - USB (host); isochronous transfers.
  - RPI0W Bluetooth Low Energy (probably)
  - DRM/KMS
+ - RPI4 xhci does not work with a straight netbsd-10 install
+ - RPI4 hardware rng does not work with a straight netbsd-10 install
 
 # CPU types
 
@@ -165,33 +167,54 @@
 
 ### boot methods
 
-\todo Validate and remove this caveat!
+There are (at least) two boot methods: the tradtional RPI method and UEFI.
 
-There are two boot methods: the tradtional RPI method and UEFI.
-(The traditional one might be ACPI, and there might be three!)
-
-The RPI expects an MSDOS filesystem.  Through RPI3, MBR is ok.  With
+The RPI expects an MSDOS filesystem on the uSD.  Through RPI3, MBR is ok.  With
 RPI4, GPT is ok.
 
 ### Traditional booting
 
-\todo Write
-
-### UEFI booting
-
-At least as of NetBSD 10, the standard approach for GENERIC64 kernels is to boot via UEFI.
+This is the method used if one uses arm.img or arm64.img from the
+release build, without trying to convert to UEFI.
 
-The boot partition contains `EFI/BOOT/bootaa64.efi`.
+Boot code in some kind of processor EEPROM loads some of the files
+from the uSD, probably start.elf or start4.elf.  The file config.txt
+then controls the next steps.
+
+This is the method that has traditionally been used for NetBSD on RPI.
+One can configure a serial console by editing files in the uSD, and
+never having a monitor.
 
-At least until this document is straightened out, see this 
-[page about UEFI on RPI](https://washbear.neocities.org/rpi3-netbsd-uefi.html).
+### UEFI booting
 
-See also the [UEFI firmware page](https://github.com/pftf/RPi4/releases). Write the UEFI firmware to the SD card, and then insert an USB drive with the standard NetBSD `arm64.img` written to it. The Pi will then boot from USB.
+With UEFI, one first boots "UEFI firmware" that then loads the NetBSD
+kernel and provides a UEFI interface.  This makes the RPI seem more
+like a PC, and of course whether that's a good thing depends on your
+perspective.  There is richer support for configuring where to boot
+from.
+
+The netbsd-10 image boot partition contains `EFI/BOOT/bootaa64.efi`.
+
+This is called "UEFI firmware" even though the bits are on uSD rather
+than EEPROM/flash.  However, it functions like a UEFI BIOS in a PC.
+
+See the [UEFI firmware
+page](https://github.com/pftf/RPi4/releases). Write the UEFI firmware
+to the SD card.  Then either insert a USB drive with the standard
+NetBSD `arm64.img` written to it, or have the FFS partition from that
+image on the rest of the uSD card. The RPI will then boot from that
+filesystem.
+
+See also this [page about UEFI on
+RPI](https://washbear.neocities.org/rpi3-netbsd-uefi.html) which is
+from an unknown time.
 
 ## Console approaches
 
 The standard approach is to use a USB keyboard and an HDMI monitor for installation.
 
+This section was written for the traditional boot process. 
+
 ### Serial Console
 
 By default NetBSD images are set to use HDMI.  If you wish to use a serial console, mount the FAT32 partition on another system and edit cmdline.txt and remove '"console=fb"'.
@@ -239,6 +262,27 @@
 
  - <https://www.cambus.net/netbsd-on-the-raspberry-pi/>
 
+# Issues and Workarounds
+
+## RPI4 xhci
+
+With the netbsd-10 arm64.img on a RPI4 (most of them), the pci driver
+is missing and therefore xhci will not attach, so the USB ports will
+not work.  One workaround is to switch to UEFI, but that leads to a
+3GB memory limit and needing a monitor.  Another is to add kernel
+config.  One can also add the hardware rng.  Adding the following to
+GENERIC64.local results in both working; you likely also need a dtb
+that includes the RNG.  \todo Explain why this isn't in GENERIC64 or
+link to a PR.
+
+[[!template id=filecontent name="GENERIC64" text="""
+bcm2838pcie* at fdt?                    # STB PCIe host controller
+bcm2838rng* at fdt?                     # RPI4 RNG
+"""]]
+
+There is some need to load firmware for the xhci driver, but
+apparently that works, once the above is added.
+
 # Maintaining a system
 
 ## Booting single user
@@ -267,6 +311,13 @@
 
 \todo Explain if updating firmware is necessary when e.g. moving from 8 to 9, or 9 to current.
 
+## RPI4 UEFI 3 GB
+
+To work around bugs in hardware (that may or may not be fixed in
+recent RPI4) and because not all OSes have workarounds, the UEFI
+firmware's default is to limit RAM to 3GB.  NetBSD 10 can be used with
+more, so this needs to be configured in UEFI.
+
 ## Updating dtb files
 
 ### NetBSD 8

Update test status and timeline
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.104
retrieving revision 1.105
diff -u -r1.104 -r1.105
--- wikisrc/releng/netbsd-10.mdwn	7 Feb 2024 16:26:13 -0000	1.104
+++ wikisrc/releng/netbsd-10.mdwn	14 Feb 2024 10:55:00 -0000	1.105
@@ -2,7 +2,7 @@
 
 ## Hard Release Blockers
 
-*None*
+Waiting for security pullups (see below).
 
 We consider the magnitude of DRM/KMS bugs (see below) as bad, but this is
 as good as it will realistically get for a 10.0 release.
@@ -10,7 +10,8 @@
 ## Current status and timeline
 
 * [10.0 release candidate 4](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
-* the 10.0 release is planed before February 15.
+* A few security fixes (for 3rd party applications, bind(8) and wpa_supplicant(8)) just landed in -current and will be pulled up to netbsd-10 afer being tested there for a few days. We have not finally decided if this will force a fifth(!) release candidate - but tend to avoid the extra release candidate step. 
+* The 10.0 release is planed before the end of February.
 
 
 ## Showstopper bugs and PRs
@@ -132,19 +133,19 @@
   <tbody>
     <tr>
         <td><a href="//www.netbsd.org/~martin/aarch64-atf-netbsd10/">aarch64</a>, real hardware</td>
-        <td>2024-01-01</td><td>0</td><td> </td>
+        <td>2024-02-08</td><td>1</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/sparc64-atf-netbsd10/">sparc64</a>, real hardware</td>
-        <td>2024-01-02</td><td>6</td><td> </td>
+        <td>2024-02-09</td><td>4</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/netbsd-10/">xen</a></td>
-        <td>2024-01-09</td> <td>2</td><td></td>
+        <td>2024-02-09</td> <td>3</td><td></td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/evbarm-atf-netbsd10/">evbarm</a>, real hardware</td>
-        <td>2024-01-01</td><td>76</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
+        <td>2024-02-08</td><td>77</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
     </tr>
   </tbody>
 </table>

Index: wikisrc/users/tm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/tm.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/tm.mdwn	20 Mar 2016 07:53:24 -0000	1.1
+++ wikisrc/users/tm.mdwn	10 Feb 2024 22:10:38 -0000	1.2
@@ -1 +1 @@
-test
+

mention that npf.conf needs to be edited to use the correct interface
Index: wikisrc/tutorials/setting_up_blocklistd.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/setting_up_blocklistd.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/tutorials/setting_up_blocklistd.mdwn	9 Feb 2024 01:01:58 -0000	1.2
+++ wikisrc/tutorials/setting_up_blocklistd.mdwn	9 Feb 2024 02:48:47 -0000	1.3
@@ -17,6 +17,8 @@
 
 	cp /usr/share/examples/blocklist/npf.conf /etc/npf.conf
 
+Edit it so `$ext_if` points to your external network interface.
+
 If you don't want to reboot, you'll also need to create an npflog device:
 
 	ifconfig npflog0 create

simplify
Index: wikisrc/tutorials/setting_up_blocklistd.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/setting_up_blocklistd.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/tutorials/setting_up_blocklistd.mdwn	9 Feb 2024 00:50:42 -0000	1.1
+++ wikisrc/tutorials/setting_up_blocklistd.mdwn	9 Feb 2024 01:01:58 -0000	1.2
@@ -45,7 +45,7 @@
 
 Again, start with the example config:
 
-	cp -pi /usr/share/examples/blocklist/blocklistd.conf /etc/blocklistd.conf
+	cp /usr/share/examples/blocklist/blocklistd.conf /etc/blocklistd.conf
 
 Edit the file. In the `[local]` section you can add services and after
 how many tries a remote host should be blocked. In the `[remote]`

add a tutorial how to set up blocklistd
'looks great' christos@
Members: 
	tutorials/setting_up_blocklistd.mdwn:INITIAL->1.1 

--- /dev/null	2024-02-09 00:51:03.139567286 +0000
+++ wikisrc/tutorials/setting_up_blocklistd.mdwn	2024-02-09 00:51:39.264245211 +0000
@@ -0,0 +1,83 @@
+**Contents**
+
+[[!toc]]
+
+# How to set up blocklistd
+
+`blocklistd` uses `npf` for blocking connections on the network layer
+after remote hosts had too many failed tries at connecting to a
+service.
+
+So as a first step, we have to set up npf. This tutorial assumes that
+this hasn't happened yet.
+
+## Configuring npf
+
+Just use the example config file:
+
+	cp /usr/share/examples/blocklist/npf.conf /etc/npf.conf
+
+If you don't want to reboot, you'll also need to create an npflog device:
+
+	ifconfig npflog0 create
+
+If this doesn't happen automatically after a reboot, like it should, do:
+
+	echo create > /etc/ifconfig.npflog0
+
+Enable the bpfjit kernel module:
+
+	modload bpfjit
+
+and make the setting persistent:
+
+	echo bpfjit >> /etc/modules
+	echo modules=yes >> /etc/rc.conf
+
+Increase/set some npf sysctl settings:
+
+	sysctl -w net.bpf.jit=1
+	sysctl -w net.bpf.maxbufsize=4194304
+	echo net.bpf.jit=1 >> /etc/sysctl.conf
+	echo net.bpf.maxbufsize=4194304 >> /etc/sysctl.conf
+
+## Configuring blocklistd
+
+Again, start with the example config:
+
+	cp -pi /usr/share/examples/blocklist/blocklistd.conf /etc/blocklistd.conf
+
+Edit the file. In the `[local]` section you can add services and after
+how many tries a remote host should be blocked. In the `[remote]`
+section you can whitelist hosts. For more details, see
+`blocklistd.conf(5)`.
+
+## Starting the services
+
+After everything is configured, you can start the services:
+
+	service npfd restart
+	service npf reload
+	service blocklistd restart
+
+and make them persistent:
+
+	echo npf=yes >> /etc/rc.conf
+	echo npfd=yes >> /etc/rc.conf
+	echo blocklistd=yes >> /etc/rc.conf
+	echo blocklistd_flags=-r >> /etc/rc.conf
+
+Restart the services which you've added to blocklistd, e.g.
+
+	service sshd restart
+	service postfix restart
+
+You probably also need to tell npf to start filtering based on the entries:
+
+	npfctl start
+
+## Checking the current state
+
+You can check the current state with
+
+	blocklistctl dump -a

Add some note for possible non-English contributors
If for any reason English can be a barrier (at least some little English is
needed though!) we will try to do our best and trying to support with mentors
speaking the same languages of contributor when possible.
Should solve board@ RT ticket #85860.
Should solve board@ RT ticket #85860.

Members: 
	projects/gsoc.mdwn:1.29->1.30 

Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- wikisrc/projects/gsoc.mdwn	31 Jan 2024 19:42:13 -0000	1.29
+++ wikisrc/projects/gsoc.mdwn	7 Feb 2024 19:59:28 -0000	1.30
@@ -113,4 +113,4 @@
 
 We have not yet failed a student who worked hard and actually talked (and listened) to their mentors and the community. If unexpected roadblocks make your project goals too hard to reach in the time given, the goals can be re-negotiated. They will not be for rampant slacking, though.
 
-What we expect from contributors (both GSoC students and generally) is that they cooperate, that they are able to communicate (this will mean some English skills, sorry), and that they meet a minimum of good manners towards other people on our lists and other venues. Note that being a specific color, gender, nationality, religion, etc is not listed: If you are willing and able to contribute in a constructive manner, you are welcome.
+What we expect from contributors (both GSoC students and generally) is that they cooperate, that they are able to communicate (this will mean some English skills, sorry; we will try to support with mentors speaking the same contributor language if that can be a problem), and that they meet a minimum of good manners towards other people on our lists and other venues. Note that being a specific color, gender, nationality, religion, etc is not listed: If you are willing and able to contribute in a constructive manner, you are welcome.

Update for RC4
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.103
retrieving revision 1.104
diff -u -r1.103 -r1.104
--- wikisrc/releng/netbsd-10.mdwn	4 Feb 2024 16:28:35 -0000	1.103
+++ wikisrc/releng/netbsd-10.mdwn	7 Feb 2024 16:26:13 -0000	1.104
@@ -9,8 +9,7 @@
 
 ## Current status and timeline
 
-* [10.0 release candidate 3](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
-* RC4 will be ready in the next few days and should be the last before final release.
+* [10.0 release candidate 4](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
 * the 10.0 release is planed before February 15.
 
 
@@ -49,6 +48,7 @@
 * ~~[[!template id=pr number=57268]]: i915 GPU hangs~~
 * ~~[[!template id=pr number=57402]]: null pointer dereference in i915_gem_busy_ioctl~~
 * ~~[[!template id=pr number=57833]]: kernel panic on xorg exit~~
+* ~~[[!template id=pr number=57878]]: i915 calls agp_i810_chipset_flush with spin lock held but agp_i810_chipset_flush waits for xcall~~
 
 ## Regressions since netbsd-9
 

Kansai Open Forum 2023 https://youtu.be/PIoWNTQwlSo by tsutsui@
Index: wikisrc/users/jun/2023.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun/2023.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/jun/2023.mdwn	25 Dec 2023 05:44:44 -0000	1.1
+++ wikisrc/users/jun/2023.mdwn	5 Feb 2024 10:48:24 -0000	1.2
@@ -28,6 +28,7 @@
 - Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/KOF2023.pdf]]
 - togetter [[https://togetter.com/li/2254094]]
 - [[https://speakerdeck.com/tsutsui/kof2023]]
+- [[https://youtu.be/PIoWNTQwlSo]] Video Archive by tsutsui@
 
 ## Open Source Conference 2023 Shimane NetBSD Booth
 - 2023 Oct.28 Sat 10:00-17:30 JST (UTC+9)

RPI: rototill boot methods
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.153
retrieving revision 1.154
diff -u -r1.153 -r1.154
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	5 Feb 2024 00:41:54 -0000	1.153
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	5 Feb 2024 00:58:20 -0000	1.154
@@ -140,26 +140,28 @@
 
 Multiple kernels are provided in `releasedir/binary/kernels`.
 
-In netbsd-8, there are only GENERIC and GENERIC.bin.  RPI uses GENERIC.bin version, and GENERIC (regular ELF) is not used.
+In netbsd-8, there are only GENERIC and GENERIC.bin.  RPI uses the GENERIC.bin version as kernel.img/kernel7.img, and does not use GENERIC (regular ELF).
 
-In netbsd-9, 4 versions are provided and GENERIC.img is used.
+In netbsd-9, 4 versions are provided and GENERIC.img is used as kernel.img/kernel7.img.
+
+In netbsd-9, there are only GENERIC and GENERIC.img.
 
 #### netbsd-GENERIC.gz
 
 This is regular ELF and not used on RPI.  However it is installed as /netbsd.
 
-#### netbsd-GENERIC.bin.gz
-
-This is like .img, but without the trailer for DTB.  This file should be used on -8.   Do not install it as kernel7.img on -9: it will not boot.
-
 #### netbsd-GENERIC.img.gz
 
 On NetBSD >=9, the kernel with the .img suffix has the trailer to cause the bootloader to load DTB files.  Without DTBs, very little useful will happen!
 On NetBSD 10 aarch64, this is /boot/netbsd.img.
 
+#### netbsd-GENERIC.bin.gz
+
+This is like .img, but without the trailer for DTB.  This file should be used on -8.   Do not install it as kernel7.img on -9: it will not boot.
+
 #### netbsd-GENERIC.ub.gz
 
-This is for u-boot and not used on RPI.
+This is for u-boot, not used on RPI and present only for NetBSD 9 (not 8, not 10).
 
 ### boot methods
 

flip aarch64 links to 10
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.152
retrieving revision 1.153
diff -u -r1.152 -r1.153
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	5 Feb 2024 00:37:25 -0000	1.152
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	5 Feb 2024 00:41:54 -0000	1.153
@@ -96,8 +96,8 @@
 
 - The Raspberry Pi 1 requires the ARMv6 [rpi.img.gz](http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-earmv6hf/binary/gzimg/rpi.img.gz).
 - The Raspberry Pi 2-3 can use the standard ARMv7 [armv7.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-earmv7hf/binary/gzimg/armv7.img.gz) image.
-- The Raspberry Pi 2-1.2 and 3 can also use [arm64.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz).
-- The Raspberry Pi 4 uses [arm64.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz).
+- The Raspberry Pi 2-1.2 and 3 can also use [arm64.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-10/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz).
+- The Raspberry Pi 4 uses [arm64.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-10/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz).
 
 Decompress it and write it to the SD card:
 

RPI howto: rototill a bunch
- coalesce similar sections
- gc ancient stuff
- add some todos
Members: 
	ports/evbarm/raspberry_pi.mdwn:1.151->1.152 

Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.151
retrieving revision 1.152
diff -u -r1.151 -r1.152
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	4 Feb 2024 22:09:46 -0000	1.151
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	5 Feb 2024 00:37:25 -0000	1.152
@@ -14,11 +14,16 @@
 
 # What works
 
-Note that NetBSD 8 is very out of date relative to RPI.  Asking about
-it will surely result in advice to upgrade.
+Note that NetBSD 8 is very out of date; asking about it will surely
+result in advice to upgrade.  The HOWTO only address NetBSD 9, 10, and current.
+
+In general, many aspects of NetBSD on RPI are not different from
+NetBSD on any other computer and the HOWTO tends to not discuss them.
 
 ## NetBSD 8
 
+While NetBSD 8 is of historic interest only, we document what was working in 8.
+
  - RPI1, RPI2, RPI2-1.2, RPI3, RPI3+ (except RPI3 builtin WiFi and bluetooth)
  - RPI0 and RPI0W are expected to work (without WiFi, and one needs fdt files \todo where from?)
  - multiple processors on RPI2/RPI3
@@ -35,8 +40,8 @@
  - RNG
  - Audio - [vcaudio(4)](//man.netbsd.org/evbarm/vcaudio.4])
  - GPIO - [bcmgpio(4)](//man.netbsd.org/evbarm/bcmgpio.4)
- - I²C: works, could use enhancements, man page
- - SPI: could use enhancements, man page
+ - I²C: works, could use enhancements, see man page
+ - SPI: could use enhancements, see man page
 
 ## NetBSD 9
 
@@ -45,24 +50,23 @@
 
 ## NetBSD 10
 
- - RPI4 (using EDK2 UEFI firmware)
-	- RPI4 Ethernet (Broadcom GENETv5) - genet(4); needs man page
- - RPI3/RPI4 audio with aarch64 kernels
-	- Previously the driver was only included with 32-bit (ARMv7/ARMv6)
-	  kernels, now works [due to dma-ranges](//mail-index.NetBSD.org/source-changes-d/2021/01/22/msg013133.html).
- - RPI3 builtin bluetooth
- - RPI3 and RPI0W builtin WiFi - [bwfm(4)](//man.netbsd.org/bwfm.4)
- - Big endian support
+ - RPI4 general support
+ - RPI4 ethernet (Broadcom GENETv5) (but the man page for genet(4) is missing)
+ - RPI3/RPI4 audio with aarch64 kernels (Previously the driver was only included with 32-bit (ARMv7/ARMv6) kernels, and now works [due to dma-ranges](//mail-index.NetBSD.org/source-changes-d/2021/01/22/msg013133.html).
+ - builtin bluetooth on RPI3 (RPI0W? RPI4?) 
+ - builtin WiFi on RPI0W, RPI3 and RPI4 - [bwfm(4)](//man.netbsd.org/bwfm.4)
+ - Big endian support, meaning using the CPU in BE mode.
 
 ## NetBSD current
 
- - \todo Is anything supported in current that doesn't work in 10?  RPI5???
+ - \todo Is anything supported in current that doesn't work in 10?
 
 ## What needs documenting if it works
 
  - CM1
  - CM3
  - CM3lite
+ - RPI02W
 
 ## What needs work
 
@@ -82,6 +86,8 @@
 
 Note that one can run a build of earmv6hf on the 2 and 3.  There will still be a kernel7, built to use the 2/3 hardware, but with the armv6 instruction set.  In theory the code compiled for earmv7hf will be faster, but anecdotal experience is that it doesn't matter that much.  Builds of NetBSD for earlier revisions of ARM are unsupported.
 
+\todo Explain if one can run earmv7hf on RPI4 (not that there is any reason to do so).
+
 # Installation
 
 ## Using standard images
@@ -90,8 +96,8 @@
 
 - The Raspberry Pi 1 requires the ARMv6 [rpi.img.gz](http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-earmv6hf/binary/gzimg/rpi.img.gz).
 - The Raspberry Pi 2-3 can use the standard ARMv7 [armv7.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-earmv7hf/binary/gzimg/armv7.img.gz) image.
-- The Raspberry Pi 3 can also use [arm64.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz).
-- \todo RPI4 NetBSD 10 image
+- The Raspberry Pi 2-1.2 and 3 can also use [arm64.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz).
+- The Raspberry Pi 4 uses [arm64.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz).
 
 Decompress it and write it to the SD card:
 
@@ -100,19 +106,6 @@
 
 If you're not using NetBSD, your operating system's dd command's arguments may vary. On Windows, try [Rawrite32](https://www.netbsd.org/~martin/rawrite32/).
 
-The Raspberry Pi 4 requires the [UEFI firmware](https://github.com/pftf/RPi4/releases). Write the UEFI firmware to the SD card, and then insert an USB drive with the standard NetBSD `arm64.img` written to it. The Pi will then boot from USB.
-
-The Raspberry Pi 3 can also [boot NetBSD from UEFI firmware](https://washbear.neocities.org/rpi3-netbsd-uefi.html), but the installation process is currently more complicated. However, there are some advantages, so you might want to try anyway.
-
-## SD card structure
-
-The RPI1 looks for firmware and kernel.img on the first FAT32 MBR partition of the uSD card.  A separate kernel (kernel7.img) is used on RPI2 and RPI3.
-The NetBSD kernel will then find NetBSD MBR partition and within that the root disklabel partition, and use that FFS partition as the root filesystem.
-
-A 2 GB card is the smallest workable size that the installation image will fit on.  After the first boot, the system resizes the NetBSD root partition to fill the card.  Note that swap is after /boot and before /, and not contained in the NetBSD fdisk partition.  However, if you don't try to change the partition structure, this should not cause you any trouble.
-
-Note that SD cards generally have limited write tolerance, so you may wish to disable atime updates via the noatime option, as is done by the default installation.
-
 ## Building yourself
 
 Getting sources and building a release with build.sh is not special for evbarm.  However, the evbarm port has a very large number of CPU types, compared to i386 and amd64 which have one each.  The standard approach is to use -m to define MACHINE and -a to define MACHINE_ARCH.  build.sh supports aliases that can be passed as a MACHINE value, but denote both MACHINE and a MACHINE_ARCH.   The third line uses an alias and is equal to the second, for RPI2/3.  Note that the aliases start with "evb" while the MACHINE_ARCH values do not, and that aliases have "-el" or "-eb", while the MACHINE_ARCH values have no suffix or "eb".
@@ -123,55 +116,16 @@
 
 Consider setting RELEASEMACHINEDIR if you wish to build multiple MACHINE_ARCH values for a MACHINE; see build.sh.  Use something like "evbarm-earmv7hf", so that 1) earvm6 and earmv7 don't collide and 2) anita will recognize it as a type of evbarm.
 
-## Console approaches
-
-The standard approach is to use a USB keyboard and an HDMI monitor for installation.
-
-### Serial Console
-
-By default the rpi.img is set to use the HDMI output.  If you wish to use a serial console, mount the FAT32 partition on another system and edit cmdline.txt and remove '"console=fb"'.
-
- - Most (all?) USB-to-TTL serial adapters have wires for TX, RX and ground, and not RTS/CTS or other flow control lines.   Thus, your terminal program (or terminal) must be configured to not require flow control; a symptom of misconfiguration is that you see console output, but cannot type anything.  If so, adjust your serial console application's flow control settings to "none".   The serial port is at 115200 baud.
-
-   - In Kermit, the commands are "set flow none", "set carrier-watch off", "set baud 115200", and, often on NetBSD, "set line /dev/dtyU0".
-   - In minicom, run "minicom -s" and set hardware flow control to "no".
-
-### Enabling ssh for installation without any console
-
-(Note that this section is more broadly applicable than RPI.)
-
-If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, you can edit the configuration of a uSD card before booting.   On another computer, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf.  Besides having to find the IP address (e.g. from DHCP server logs), you will have to wait for the partition resizing and reboot.
-
-As a likely preferred alternative, see creds_msdos(8) which describes a way to install a key via /boot/creds.txt.  Note that creds_msdos is not part of a normal system installation and is only present on install media.
-As of 10.0_RC3, the sshkey option is broken, and sshkeyfile will not work with a file containing spaces (but this is Unix and files should not have spaces :-).
-
-### Installation with sshramdisk image
-
-\todo Verify if this is still accurate.  If only for earmv6, explain why or file bug to have the rest support it.  If rpi_inst is historical, gc this section.
-
-build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console, when built for earmv6hf.  Note that this image is much smaller and that you will need to fetch the sets over the network.  To use this method, write that image to a uSD card as above, and then:
-
- - Connect an Ethernet cable from the RPI to a LAN with a DHCP server, and another host you can use for ssh.
- - Power on the RPI, and wait.  Watch the logs on the DHCP server, and find the IP address assigned to the RPI.
- - Use ssh to log in to the address you found with user "sysinst", and password "netbsd".
- - When installing, ensure that you enable DHCP and ssh, so that you can log in again after the system is installed.
+## SD card structure and booting process
 
-The rpi_inst.img.gz image will only work for systems that use earmv6hf kernels (so not RPI2/3).  See [this port-arm message](https://mail-index.netbsd.org/port-arm/2017/08/18/msg004374.html) for details.
-
-## Installation via ebijun's image
-
-As an alternative to the standard installation images, Jun Ebihara
-provides an install image for Raspberry Pi that includes packages.  It
-is based on NetBSD-current and is built for earmv6hf, and thus will
-work on Raspberry Pi 1, 2 and 3.  This image is typically updated
-every few weeks.
+The RPI1 looks for firmware and kernel.img on the first FAT32 MBR partition of the uSD card.  A separate kernel (kernel7.img) is used on RPI2 and RPI3.
+The NetBSD kernel will then find a NetBSD MBR partition and within that the root disklabel partition, and use that FFS partition as the root filesystem.
 
- - <https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/README>
+The RPI4 is similar, but can (only?) look in the first FAT32 partition within the GPT. \todo Explain more.
 
-## Boot Process
+A 2 GB card is the smallest workable size that the installation image will fit on.  After the first boot, the system resizes the NetBSD root partition to fill the card.  Note that swap is after /boot and before /, and not contained in the NetBSD fdisk partition.  However, if you don't try to change the partition structure, this should not cause you any trouble.
 
-Note that evbarm supports multiple kinds of computers, not just RPI,
-but that this HOWTO page is only about RPI.
+Note that SD cards generally have limited write tolerance, so you may wish to disable atime updates via the noatime option, as is done by the default installation.
 
 https://www.raspberrypi.org/documentation/configuration/config-txt/boot.md
 
@@ -230,13 +184,52 @@
 At least until this document is straightened out, see this 
 [page about UEFI on RPI](https://washbear.neocities.org/rpi3-netbsd-uefi.html).
 
-## Configuring 802.11
+See also the [UEFI firmware page](https://github.com/pftf/RPi4/releases). Write the UEFI firmware to the SD card, and then insert an USB drive with the standard NetBSD `arm64.img` written to it. The Pi will then boot from USB.
+
+## Console approaches
+
+The standard approach is to use a USB keyboard and an HDMI monitor for installation.
+
+### Serial Console
+
+By default NetBSD images are set to use HDMI.  If you wish to use a serial console, mount the FAT32 partition on another system and edit cmdline.txt and remove '"console=fb"'.
 
-After installation, the Ethernet will function as on any other NetBSD system; simply enable dhcpcd or configure a static address.  USB WiFi devices will also function as on any other NetBSD system; in addition to dhcpcd or static, configure and enable wpa_supplicant.
+  - Most (all?) USB-to-TTL serial adapters have wires for TX, RX and ground, and not RTS/CTS or other flow control lines.   Thus, your terminal program (or terminal) must be configured to not require flow control; a symptom of misconfiguration is that you see console output, but cannot type anything.  If so, adjust your serial console application's flow control settings to "none".   The serial port is at 115200 baud.
 
-Note that the built-in WiFi in the RPI3 is not yet supported.   USB WiFi interfaces (that work on NetBSD in general) should all work.  In particular, the following are known to work:
+    - In Kermit, the commands are "set flow none", "set carrier-watch off", "set baud 115200", and, often on NetBSD, "set line /dev/dtyU0".
+    - In minicom, run "minicom -s" and set hardware flow control to "no".
 
- - urtwn0: Realtek (0xbda) 802.11n WLAN Adapter (0x8176), rev 2.00/2.00, addr 5, MAC/BB RTL8188CUS, RF 6052 1T1R
+### Enabling ssh for installation without any console

(Diff truncated)
RPI: improve boot discussion
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.150
retrieving revision 1.151
diff -u -r1.150 -r1.151
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	2 Jan 2024 16:42:12 -0000	1.150
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	4 Feb 2024 22:09:46 -0000	1.151
@@ -138,9 +138,12 @@
 
 ### Enabling ssh for installation without any console
 
+(Note that this section is more broadly applicable than RPI.)
+
 If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, you can edit the configuration of a uSD card before booting.   On another computer, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf.  Besides having to find the IP address (e.g. from DHCP server logs), you will have to wait for the partition resizing and reboot.
 
 As a likely preferred alternative, see creds_msdos(8) which describes a way to install a key via /boot/creds.txt.  Note that creds_msdos is not part of a normal system installation and is only present on install media.
+As of 10.0_RC3, the sshkey option is broken, and sshkeyfile will not work with a file containing spaces (but this is Unix and files should not have spaces :-).
 
 ### Installation with sshramdisk image
 
@@ -189,7 +192,7 @@
 
 #### netbsd-GENERIC.gz
 
-This is regular ELF and not used on RPI.
+This is regular ELF and not used on RPI.  However it is installed as /netbsd.
 
 #### netbsd-GENERIC.bin.gz
 
@@ -198,17 +201,34 @@
 #### netbsd-GENERIC.img.gz
 
 On NetBSD >=9, the kernel with the .img suffix has the trailer to cause the bootloader to load DTB files.  Without DTBs, very little useful will happen!
+On NetBSD 10 aarch64, this is /boot/netbsd.img.
 
 #### netbsd-GENERIC.ub.gz
 
 This is for u-boot and not used on RPI.
 
-### UEFI
+### boot methods
+
+\todo Validate and remove this caveat!
+
+There are two boot methods: the tradtional RPI method and UEFI.
+(The traditional one might be ACPI, and there might be three!)
+
+The RPI expects an MSDOS filesystem.  Through RPI3, MBR is ok.  With
+RPI4, GPT is ok.
+
+### Traditional booting
+
+\todo Write
+
+### UEFI booting
+
+At least as of NetBSD 10, the standard approach for GENERIC64 kernels is to boot via UEFI.
 
-\todo Explain UEFI on RPI4.
+The boot partition contains `EFI/BOOT/bootaa64.efi`.
 
-One can use [use UEFI on RPI3](https://washbear.neocities.org/rpi3-netbsd-uefi.html).
-\todo Explain the status of integrating this into upstream sources.
+At least until this document is straightened out, see this 
+[page about UEFI on RPI](https://washbear.neocities.org/rpi3-netbsd-uefi.html).
 
 ## Configuring 802.11
 

Note a couple more DRM bugs are now closed.
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.102
retrieving revision 1.103
diff -u -r1.102 -r1.103
--- wikisrc/releng/netbsd-10.mdwn	4 Feb 2024 11:57:17 -0000	1.102
+++ wikisrc/releng/netbsd-10.mdwn	4 Feb 2024 16:28:35 -0000	1.103
@@ -46,9 +46,9 @@
 * [[!template id=pr number=57143]]: Screen rotation causes loss of acceleration on i915
 * [[!template id=pr number=57182]]: nouveau doesn't switches LVDS on
 * [[!template id=pr number=57207]]: Unable to get display from a NetBSD system through a DP 1.4 KVM switch
-* [[!template id=pr number=57268]]: i915 GPU hangs
-* ~~[[!template id=pr number=57402]]: null pointer dereference in i915_gem_busy_ioctl~~ (needs pullup)
-* [[!template id=pr number=57833]]: kernel panic on xorg exit
+* ~~[[!template id=pr number=57268]]: i915 GPU hangs~~
+* ~~[[!template id=pr number=57402]]: null pointer dereference in i915_gem_busy_ioctl~~
+* ~~[[!template id=pr number=57833]]: kernel panic on xorg exit~~
 
 ## Regressions since netbsd-9
 

update RC state and timeline
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.101
retrieving revision 1.102
diff -u -r1.101 -r1.102
--- wikisrc/releng/netbsd-10.mdwn	14 Jan 2024 19:58:18 -0000	1.101
+++ wikisrc/releng/netbsd-10.mdwn	4 Feb 2024 11:57:17 -0000	1.102
@@ -9,9 +9,9 @@
 
 ## Current status and timeline
 
-* [10.0 release candidate 2](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available
-* There will be another RC in the next few days
-* the 10.0 release is planed by the end of January 2024
+* [10.0 release candidate 3](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
+* RC4 will be ready in the next few days and should be the last before final release.
+* the 10.0 release is planed before February 15.
 
 
 ## Showstopper bugs and PRs

Also list 2023
Index: wikisrc/projects/gsoc.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/gsoc.mdwn,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- wikisrc/projects/gsoc.mdwn	16 Feb 2023 10:22:02 -0000	1.28
+++ wikisrc/projects/gsoc.mdwn	31 Jan 2024 19:42:13 -0000	1.29
@@ -17,7 +17,8 @@
 2019,
 [2020](https://blog.netbsd.org/tnf/entry/google_summer_of_code_2020),
 2021,
-2022
+2022,
+2023
 )
 
 This page contains a list of concrete suggestions for projects we would

move past: OSC2024Osaka and add https://speakerdeck.com/tsutsui/osc2024osaka
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.141
retrieving revision 1.142
diff -u -r1.141 -r1.142
--- wikisrc/users/jun.mdwn	25 Jan 2024 06:05:23 -0000	1.141
+++ wikisrc/users/jun.mdwn	29 Jan 2024 22:02:29 -0000	1.142
@@ -4,15 +4,6 @@
 
 #2024
 
-## Open Source Conference 2024 Osaka NetBSD Booth&BoF
-- Booth: 2024 Jan.27 Sat 10:00-16:00 JST (UTC+9)
-- BoF:  2024 Jan.27 Sat 10:00-10:45 JST (UTC+9)
-- Osaka Sangyo Sozoukan  [[https://www.sansokan.jp/map/]]
-- [[https://event.ospn.jp/osc2024-osaka/]]
-- [[https://ospn.connpass.com/event/302339/]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2024osaka.pdf]]
-- togetter [[https://togetter.com/li/2298407]]
-
 ## Open Source Conference 2024 Online/Spring NetBSD BoF
 - Zoom/YoutubeLive BoF:  2024 Mar.2 Sat 14:00-14:45 JST (UTC+9)
 - [[https://event.ospn.jp/osc2024-online-spring/]]
@@ -47,6 +38,16 @@
 
 # Past Events in 2024
 
+## Open Source Conference 2024 Osaka NetBSD Booth&BoF
+- Booth: 2024 Jan.27 Sat 10:00-16:00 JST (UTC+9)
+- BoF:  2024 Jan.27 Sat 10:00-10:45 JST (UTC+9)
+- Osaka Sangyo Sozoukan  [[https://www.sansokan.jp/map/]]
+- [[https://event.ospn.jp/osc2024-osaka/]]
+- [[https://ospn.connpass.com/event/302339/]]
+- [[https://speakerdeck.com/tsutsui/osc2024osaka]] NetBSD/vax by tsutsui@
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2024osaka.pdf]]
+- togetter [[https://togetter.com/li/2298407]]
+
 # Current my job mission
 - SOUM Corporation [[http://www.soum.co.jp]],TOKYO
 - Support Open Science Framework in Japan

Add OSC2024Osaka Guide & OSC2024Online/Spling timefix.
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.140
retrieving revision 1.141
diff -u -r1.140 -r1.141
--- wikisrc/users/jun.mdwn	19 Jan 2024 21:16:21 -0000	1.140
+++ wikisrc/users/jun.mdwn	25 Jan 2024 06:05:23 -0000	1.141
@@ -10,11 +10,11 @@
 - Osaka Sangyo Sozoukan  [[https://www.sansokan.jp/map/]]
 - [[https://event.ospn.jp/osc2024-osaka/]]
 - [[https://ospn.connpass.com/event/302339/]]
-- Tour Guide [[]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2024osaka.pdf]]
 - togetter [[https://togetter.com/li/2298407]]
 
 ## Open Source Conference 2024 Online/Spring NetBSD BoF
-- BoF:  2024 Mar.1-2 XXX XX:00-XX:45 JST (UTC+9)
+- Zoom/YoutubeLive BoF:  2024 Mar.2 Sat 14:00-14:45 JST (UTC+9)
 - [[https://event.ospn.jp/osc2024-online-spring/]]
 - Tour Guide [[]]
 - togetter [[]]
@@ -32,7 +32,6 @@
 - Tour Guide [[]]
 - togetter [[]]
 
-
 ## Kansai Open Forum 2024
 - [[https://www.k-of.jp/]]
 - 2024 Nov.8 Fri. - Nov.9 Sat.

adapt for rename to blocklistd
Index: wikisrc/projects/project/inetd-enhancements.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/inetd-enhancements.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/projects/project/inetd-enhancements.mdwn	1 Mar 2022 10:38:49 -0000	1.7
+++ wikisrc/projects/project/inetd-enhancements.mdwn	23 Jan 2024 19:49:15 -0000	1.8
@@ -29,7 +29,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.
-- Integrate with the new blacklist daemon.
+- Integrate with the new blocklist daemon.
 - Configuration compatibility for systemd socket activations
 
 """

fullfs: Note possibility of further/more general fault injection.
Index: wikisrc/projects/project/fullfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fullfs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/projects/project/fullfs.mdwn	21 Jan 2024 23:03:05 -0000	1.2
+++ wikisrc/projects/project/fullfs.mdwn	22 Jan 2024 00:36:12 -0000	1.3
@@ -46,5 +46,8 @@
 applied to the root directory of (or perhaps any file on) the fullfs
 volume.
 
+There are many ways this could be extended further to provide for more
+general fault injection.
+
 """
 ]]

Add a duration (which is a wild guess)
Index: wikisrc/projects/project/fullfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/fullfs.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/fullfs.mdwn	21 Jan 2024 22:59:29 -0000	1.1
+++ wikisrc/projects/project/fullfs.mdwn	21 Jan 2024 23:03:05 -0000	1.2
@@ -8,6 +8,7 @@
 
 category="filesystems"
 difficulty="easy"
+duration="~1 month"
 
 description="""
 

Add a "fullfs" project.
--- /dev/null	2024-01-21 23:00:05.436692513 +0000
+++ wikisrc/projects/project/fullfs.mdwn	2024-01-21 23:00:20.515497907 +0000
@@ -0,0 +1,49 @@
+[[!template id=project
+
+title="Fullfs file system"
+
+contact="""
+[tech-kern](mailto:tech-kern@NetBSD.org)
+"""
+
+category="filesystems"
+difficulty="easy"
+
+description="""
+
+Implement a fullfs, that is, a filesystem where writes fail with disk
+full.
+This is useful for testing applications and tools that often don't
+react well to this situation because it rarely occurs any more.
+
+The basic fullfs would be just a layerfs layer that you can mount
+(like nullfs) to get a copy of an existing subtree or volume where
+writes are rejected with ENOSPC.
+This is the first thing to get running.
+
+However, for testing it is good to have more than that, so the
+complete project includes the ability to control the behavior on the
+fly and a fullfsctl(8) binary that can be used to adjust it.
+
+These are some things (feel free to brainstorm others) that it would
+be useful for fullfsctl to be able to do:
+
+- Turn on and off the fail state (so for example you can start up a
+program, let it run for a while, then have the disk appear to fill up
+under it)
+- Arm a "doom counter" that allows the next N writes to succeed and then
+switches to the fail state (to test what happens if the disk fills partway
+through a write or save operation)
+- Change what error it fails with (ENOSPC is the basic error, but at
+least EDQUOT and possibly other errors, such as NFS-related ones, are
+also interesting)
+
+fullfs itself should be implented as a layerfs layer, not a whole
+filesystem.
+
+fullfsctl should operate via one or more file-system-specific ioctls
+applied to the root directory of (or perhaps any file on) the fullfs
+volume.
+
+"""
+]]

OSC2024Osaka add togetter link
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.139
retrieving revision 1.140
diff -u -r1.139 -r1.140
--- wikisrc/users/jun.mdwn	11 Jan 2024 10:25:06 -0000	1.139
+++ wikisrc/users/jun.mdwn	19 Jan 2024 21:16:21 -0000	1.140
@@ -11,7 +11,7 @@
 - [[https://event.ospn.jp/osc2024-osaka/]]
 - [[https://ospn.connpass.com/event/302339/]]
 - Tour Guide [[]]
-- togetter [[]]
+- togetter [[https://togetter.com/li/2298407]]
 
 ## Open Source Conference 2024 Online/Spring NetBSD BoF
 - BoF:  2024 Mar.1-2 XXX XX:00-XX:45 JST (UTC+9)

Link describes basic Markdown + ikiwiki directives
Index: wikisrc/index.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/index.mdwn,v
retrieving revision 1.77
retrieving revision 1.78
diff -u -r1.77 -r1.78
--- wikisrc/index.mdwn	15 Jan 2024 00:21:42 -0000	1.77
+++ wikisrc/index.mdwn	15 Jan 2024 00:29:27 -0000	1.78
@@ -23,5 +23,5 @@
 
 ## Meta-wiki
 * [[How to edit|wiki/start]]
-* [[Markdown formatting|ikiwiki/formatting]]
+* [[Markdown formatting + ikiwiki-specific directives|ikiwiki/formatting]]
 * [[Sitemap|wiki/sitemap]]

index.mdwn: one click from front page to markdown documentation
Index: wikisrc/index.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/index.mdwn,v
retrieving revision 1.76
retrieving revision 1.77
diff -u -r1.76 -r1.77
--- wikisrc/index.mdwn	30 May 2023 14:46:20 -0000	1.76
+++ wikisrc/index.mdwn	15 Jan 2024 00:21:42 -0000	1.77
@@ -23,4 +23,5 @@
 
 ## Meta-wiki
 * [[How to edit|wiki/start]]
+* [[Markdown formatting|ikiwiki/formatting]]
 * [[Sitemap|wiki/sitemap]]

Note PR kern/57833: kernel panic on xorg exit
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.100
retrieving revision 1.101
diff -u -r1.100 -r1.101
--- wikisrc/releng/netbsd-10.mdwn	14 Jan 2024 12:38:51 -0000	1.100
+++ wikisrc/releng/netbsd-10.mdwn	14 Jan 2024 19:58:18 -0000	1.101
@@ -48,6 +48,7 @@
 * [[!template id=pr number=57207]]: Unable to get display from a NetBSD system through a DP 1.4 KVM switch
 * [[!template id=pr number=57268]]: i915 GPU hangs
 * ~~[[!template id=pr number=57402]]: null pointer dereference in i915_gem_busy_ioctl~~ (needs pullup)
+* [[!template id=pr number=57833]]: kernel panic on xorg exit
 
 ## Regressions since netbsd-9
 

Update status and timeline
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.99
retrieving revision 1.100
diff -u -r1.99 -r1.100
--- wikisrc/releng/netbsd-10.mdwn	11 Nov 2023 11:28:31 -0000	1.99
+++ wikisrc/releng/netbsd-10.mdwn	14 Jan 2024 12:38:51 -0000	1.100
@@ -7,11 +7,12 @@
 We consider the magnitude of DRM/KMS bugs (see below) as bad, but this is
 as good as it will realistically get for a 10.0 release.
 
-The entropy issues have been resolved by restoring the estimator from netbsd-9. Machines without HWRNG will continue to print a warning on boot.
+## Current status and timeline
 
-We have pulled up OpenSSL 3.x, bind, heimdahl, libfido and also bumped a lot of shared library revisions (which usually is not allowed on a release branch).
+* [10.0 release candidate 2](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available
+* There will be another RC in the next few days
+* the 10.0 release is planed by the end of January 2024
 
-Trust anchors (for https) are now shipped with the system.
 
 ## Showstopper bugs and PRs
 
@@ -120,11 +121,6 @@
 * ~~[File system corruption due to UFS2 extended attributes](https://mail-index.netbsd.org/tech-kern/2022/05/24/msg028105.html)~~
 	- ~~NetBSD 10 will be the first official release with full extended attribute support in FFS, additional docs needed (wiki) and extensions of the install docs (pointing at wiki)~~
 
-## Current status and timeline
-
-* 10.0 release candidate 1 is available
-* the 10.0 release is planed for the last week of november if nothing bad happens and we would need another RC
-
 ## Last netbsd-10 Test Results overview
 For all tests, see [releng's tests page](//releng.netbsd.org/test-results.html).
 
@@ -135,19 +131,19 @@
   <tbody>
     <tr>
         <td><a href="//www.netbsd.org/~martin/aarch64-atf-netbsd10/">aarch64</a>, real hardware</td>
-        <td>2023-11-03</td><td>0</td><td> </td>
+        <td>2024-01-01</td><td>0</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/sparc64-atf-netbsd10/">sparc64</a>, real hardware</td>
-        <td>2023-11-03</td><td>4</td><td> </td>
+        <td>2024-01-02</td><td>6</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/netbsd-10/">xen</a></td>
-        <td>2023-11-07</td> <td>3</td><td></td>
+        <td>2024-01-09</td> <td>2</td><td></td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/evbarm-atf-netbsd10/">evbarm</a>, real hardware</td>
-        <td>2023-11-03</td><td>75</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
+        <td>2024-01-01</td><td>76</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
     </tr>
   </tbody>
 </table>

xen solaris howto: add warning that it is 10 years old
Index: wikisrc/ports/xen/howto-solaris.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto-solaris.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/xen/howto-solaris.mdwn	26 Dec 2014 20:28:45 -0000	1.1
+++ wikisrc/ports/xen/howto-solaris.mdwn	13 Jan 2024 20:46:08 -0000	1.2
@@ -1,6 +1,11 @@
 Solaris domU creation
 =====================
 
+NB: This text was moved to its own page in 2014 and thus was written
+before that, perhaps well before that.  It should be read only as a
+hint at how things used to be, for those attempting to figure out how
+they are now.
+
 Download an Opensolaris [release](http://opensolaris.org/os/downloads/)
 or [development snapshot](http://genunix.org/) DVD image. Attach the DVD
 image to a MAN.VND.4 device. Copy the kernel and ramdisk filesystem

xen howto: Rototill console section harder
Based on input from Greg Woods, and me reading docs.
Members: 
	ports/xen/howto.mdwn:1.237->1.238 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.237
retrieving revision 1.238
diff -u -r1.237 -r1.238
--- wikisrc/ports/xen/howto.mdwn	9 Jan 2024 13:31:07 -0000	1.237
+++ wikisrc/ports/xen/howto.mdwn	13 Jan 2024 20:13:55 -0000	1.238
@@ -216,16 +216,28 @@
 
 ### Configuring booting
 
+Read the [Xen command-line
+options](https://xenbits.xenproject.org/docs/4.18-testing/misc/xen-command-line.html)
+documentation.
+
 Read boot.cfg(8) carefully.  Add lines to /boot.cfg to boot Xen,
 adjusting for your root filesystem:
 
 [[!template id=filecontent name="/boot.cfg" text="""
-menu=Xen:load /netbsd-XEN3_DOM0.gz root=wd0a console=pc;multiboot /xen.gz dom0_mem=512M
-menu=Xen single user:load /netbsd-XEN3_DOM0.gz root=wd0a console=pc -s;multiboot /xen.gz dom0_mem=512M
+menu=Xen:load /netbsd-XEN3_DOM0.gz bootdev=wd0a rndseed=/var/db/entropy-file console=pc;multiboot /xen.gz dom0_mem=512M
+menu=Xen single user:load /netbsd-XEN3_DOM0.gz rndseed=/var/db/entropy-file bootdev=wd0a console=pc -s;multiboot /xen.gz dom0_mem=512M
 """]]
 
-This specifies that the dom0 should have 512MB of ram, leaving the rest
-to be allocated for domUs.
+"dom0_mem" is mandatory. This example specifies that the dom0 should
+have 512MB of ram, leaving the rest to be allocated for domUs.
+
+"bootdev" (or the earlier form "root") is also in general required,
+because the boot device from /boot is not passed via Xen to the dom0
+kernel.
+
+"userconf" statements intended for NetBSD should be attached to the
+load statement, not the multiboot statement.  (\todo Validate and test
+an example.)
 
 NB: This says add, not replace, so that you will be able to more
 easily boot a NetBSD kernel without Xen.  Once Xen boots ok, you may
@@ -233,85 +245,94 @@
 trouble at some point, and keeping an up-to-date GENERIC for use in
 fixing problems is the standard prudent approach.
 
-\todo Explain why rndseed is not set with Xen as part of the dom0
-subconfiguration.
+### Selecting the console for the boot blocks
+
+See boot_console(8).  Understand that you should start from a place of
+having the console setup correct for booting GENERIC before trying to
+configure Xen.
 
-Note that you are likely to have to set root= because the boot device
-from /boot is not passed via Xen to the dom0 kernel.  With one disk,
-it will work, but e.g. plugging in USB disk to a machine with root on
-wd0a causes boot to fail.
-
-Beware that userconf statements must be attached to the dom0 load, and
-may not be at top-level, because then they would try to configure the
-hypervisor, if there is a way to pass them via multiboot.  It appears
-that adding `userconf=pckbc` to `/boot.cfg` causes Xen to crash very
-early with a heap overflow.
+Generally, one sets the console in bootxx_ffsv1 or equivalent, and
+this is passed on to /boot (where one typically does not set the
+console).  This configuration should also be in place for Xen systems,
+to allow seeing messages and typing to /boot.  It is necessary for
+proper booting of GENERIC as a rescue/fallback.
 
 ### Selecting the console for Xen
 
-With GENERIC, the boot options are passed on to /netbsd, but there is
-currently no mechanism to pass these via multiboot to the hypervisor.
-Thus, in addition to configuring the console in the boot blocks, one
-must also configure it for Xen.
-
-By default, the hypervisor (Xen itself) will use some sort of vga
-device as the console, much like GENERIC uses by default.  The vga
-console is relinquished at the conclusion of hypervisor boot, before
-the dom0 is started.  In this case, Xen runs without a console.
-
-\todo Explain if one can +++ and interact with Xen while the hypervisor is booting.
+There is currently no mechanism to pass console configuration from
+boot blocksto the hypervisor (via multiboot).  Thus, in addition to
+configuring the console in the boot blocks (for operation during
+loading Xen and the dom0, before Xen starts, and for GENERIC), one
+must also configure it for Xen (if non-default behavior is desired).
+
+See the console= xen command line option in xen-command-line(7), which
+says it defaults to "com1,vga".  This means that Xen will use both the
+VGA device and the first serial port (which it calls "com1"; NetBSD
+calls it "com0") as the console, sending output to both
+simultaneously.  (UART settings should be configured by boot blocks,
+but see the com1 argument for unusual sitautions.)
+
+When Xen uses a serial console, it manages the serial port and, after
+booting, forwards it it to the dom0's xencons(4) device.  An exception
+is that when Xen receives the "comswitch" character (<CTRL-A> by
+default) three times in quick succession, it will take over serial I/O
+until three more presses.  Xen console interactions can be used for
+various debugging features which are not usually present in the
+default /xen kernel.
+
+When Xen uses vga as a console, the vga console is relinquished at the
+conclusion of hypervisor boot, before the dom0 is started.  See also
+"vga=keep".  See also "vga=current" to prevent Xen from
+re-initialising the VGA hardware.
 
-The hypervisor can be configured to use a serial port console, e.g.
+Xen can be configured to explicitly use only a serial port console, e.g.
 [[!template id=filecontent name="/boot.cfg" text="""
-menu=Xen:load /netbsd-XEN3_DOM0.gz; multiboot /xen.gz dom0_mem=512M console=com1
+menu=Xen:load /netbsd-XEN3_DOM0.gz rndseed=/var/db/entropy-file bootdev=sd0; multiboot /xen.gz dom0_mem=512M console=com1
 """]]
-This example uses the first serial port (Xen counts from 1; this is
-what NetBSD would call com0), and sets speed and parity.
 
-If using a serial console the Xen kernel manages the serial port and
-connects it to the NetBSD-XEN3_DOM0 xencons(4) device.  The UART
-settings can be explicitly reset by the Xen kernel (see
-xen-command-line(7)), such as "com1=9600,8n1", but the settings done
-by the NetBSD /boot program should persist and will be used by Xen.
-
-\todo Explain "The default is vga,com1 and console=com1 can be left out."
-
-### Selecting the console for NetBSD
-
-See boot_console(8).  Understand that you should start from a place of
-having console setup correct for booting GENERIC before trying to
-configure Xen.
+On Xen's console, one can type the escape character (default ^A) three
+times to switch input from Xen to the dom0.  (See ddb(4) for how to
+get into DDB, which differs from non-Xen amd64.)
+\todo Xen's vga console is probably output only, but this needs clarifying.
 
-Generally for GENERIC, one sets the console in bootxx_ffsv1 or
-equivalent, and this is passed on to /boot (where one typically does
-not set the console).  This configuration of bootxx_ffsv1 should also
-be in place for Xen systems, to allow seeing messages from /boot and
-use of a keyboard to select a line from the menu.  And, one should
-have a working boot path to GENERIC for rescue situations.
+### Selecting the console for NetBSD dom0
 
 Note that com0 is never available to a NetBSD dom0; it is instead
 claimed by Xen, whether or not Xen uses it for a console.
+\todo Validate this and reference the Xen documentation.
 
-There are two paths: serial console and vga console.
+There are two paths: serial console and vga console.  By default
+XEN3_DOM0 uses xencons(4) as its console.  It will use vga if
+console=pc has been passed.
+
+Using xencons(4) is only sensible if Xen is using appp serial console,
+because Xen will have relinquished the vga console.  NetBSD will
+connect its console(4) device to xencons(4) and console I/O will
+happen there, and thus on the console Xen is using.  To use the
+default xencons(4) for NetBSD and force Xen to serial only:
 
-If using a VGA console for the Xen server, pass "console=pc" to the
-NetBSD/XEN3_DOM0 command line:
+[[!template id=filecontent name="/boot.cfg" text="""
+menu=Xen:load /netbsd-XEN3_DOM0.gz rndseed=/var/db/entropy-file bootdev=sd0; multiboot /xen.gz dom0_mem=512M console=com1
+"""]]
+
+To have NetBSD use VGA for a console, add "console=pc" to the NetBSD
+part of the boot command.  The following example also forces Xen to
+VGA only.
+
+[[!template id=filecontent name="/boot.cfg" text="""
+menu=Xen:load /netbsd-XEN3_DOM0.gz rndseed=/var/db/entropy-file bootdev=sd0 console=pc; multiboot /xen.gz dom0_mem=512M console=vga
+"""]]
 
-  menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=512M
+If using serial console with Xen, the default of xencons will be
+correct.  NetBSD will obtain input from xencons(4) and send output
+there.  Xen will pass the output to the serial port, and will pass
+input from the serial port to NetBSD, except for commands for the
+hypervisor.  Thus configure
 
-If using serial console with Xen, then pass console=xencons.  NetBSD
-will obtain input from xencons(4) and send output there.  Xen will
-pass the output to the serial port, and will pass input from the
-serial port to NetBSD, except for commands for the hypervisor.  See
-[this mailing list
-post](http://mail-index.netbsd.org/port-xen/2021/05/01/msg010149.html).
-
-It is not actually necessary to pass console=xencons, for NetBSD >= 9
-(earlier?), as it will default to that.
-\todo Explain why this default happens.
+  menu=Xen:load /netbsd-XEN3_DOM0.gz bootdev=sd0; multiboot /xen.gz console=com1 dom0_mem=512M
 
-\todo Document what happens by default in both situations, but for a
-recommendation for explicit configuration seems robust.
+to force Xen to use serial only, and for NetBSD implicitly to use
+xencons(4).
 
 ### Older NetBSD kernels

(Diff truncated)
2024 OSC Osaka-Tokyo-Nagoya
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.138
retrieving revision 1.139
diff -u -r1.138 -r1.139
--- wikisrc/users/jun.mdwn	25 Dec 2023 05:37:49 -0000	1.138
+++ wikisrc/users/jun.mdwn	11 Jan 2024 10:25:06 -0000	1.139
@@ -2,11 +2,6 @@
 
 [[jun/2020]]-[[jun/2021]]-[[jun/2022]]-[[jun/2023]]
 
-# Monthly
-
-## Nagoya *BSD Users' Group monthly meeting
-- [[http://nagoya.bug.gr.jp/]]
-
 #2024
 
 ## Open Source Conference 2024 Osaka NetBSD Booth&BoF
@@ -14,9 +9,30 @@
 - BoF:  2024 Jan.27 Sat 10:00-10:45 JST (UTC+9)
 - Osaka Sangyo Sozoukan  [[https://www.sansokan.jp/map/]]
 - [[https://event.ospn.jp/osc2024-osaka/]]
+- [[https://ospn.connpass.com/event/302339/]]
+- Tour Guide [[]]
+- togetter [[]]
+
+## Open Source Conference 2024 Online/Spring NetBSD BoF
+- BoF:  2024 Mar.1-2 XXX XX:00-XX:45 JST (UTC+9)
+- [[https://event.ospn.jp/osc2024-online-spring/]]
+- Tour Guide [[]]
+- togetter [[]]
+
+## Open Source Conference 2024 Tokyo/Spring NetBSD Booth
+- Booth: 2024 Mar.10 Sun 10:00-16:00 JST (UTC+9)
+- Toritsu Sangyo Boueki Center Taito-kan [[https://www.sanbo.metro.tokyo.lg.jp/taito/access/]] Asakusa,Tokyo
+- [[https://event.ospn.jp/osc2024-spring/]]
 - Tour Guide [[]]
 - togetter [[]]
 
+## Open Source Conference 2024 Nagoya NetBSD Booth&BoF
+- Booth: 2024 May.25 Sat XX:00-XX:00 JST (UTC+9)
+- BoF:  2024 May.25 Sat XX:00-XX:45 JST (UTC+9)
+- Tour Guide [[]]
+- togetter [[]]
+
+
 ## Kansai Open Forum 2024
 - [[https://www.k-of.jp/]]
 - 2024 Nov.8 Fri. - Nov.9 Sat.
@@ -24,6 +40,12 @@
 - Tour Guide [[]]
 - togetter [[]]
 
+# Monthly
+
+## Nagoya *BSD Users' Group monthly meeting
+- [[http://nagoya.bug.gr.jp/]]
+
+
 # Past Events in 2024
 
 # Current my job mission

xen howto: Clarify that amazon does not document NetBSD support
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.236
retrieving revision 1.237
diff -u -r1.236 -r1.237
--- wikisrc/ports/xen/howto.mdwn	9 Jan 2024 12:11:46 -0000	1.236
+++ wikisrc/ports/xen/howto.mdwn	9 Jan 2024 13:31:07 -0000	1.237
@@ -1019,6 +1019,7 @@
 The intent is to list providers only if they document support for
 running NetBSD, and to point to their resources briefly.
 
+
 ### panix.com
 
 [Panix](http://www.panix.com/) provides NetBSD as an OS option.  See
@@ -1051,6 +1052,9 @@
 page](https://www.precedence.co.uk/internet/dedicated/) for some
 details.
 
-### Amazon
+### Providers that do not document support for NetBSD.
+
+This section contains links to pages explaining how to run NetBSD via
+Xen at providers that do not document support for NetBSD.
 
-See the [Amazon EC2 page](/amazon_ec2/).
+ - [NetBSD wiki Amazon EC2 instructions (old)](/amazon_ec2/)

amazon ec2: prune dead link
Index: wikisrc/amazon_ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/amazon_ec2.mdwn,v
retrieving revision 1.56
retrieving revision 1.57
diff -u -r1.56 -r1.57
--- wikisrc/amazon_ec2.mdwn	10 Sep 2020 09:30:39 -0000	1.56
+++ wikisrc/amazon_ec2.mdwn	9 Jan 2024 13:03:33 -0000	1.57
@@ -4,7 +4,6 @@
 
 * [Subscribe to Amazon EC2, and understand its vocabulary](first_steps)
 * [Launching your first NetBSD instance in 5 minutes](netbsd_in_5_min)
-* [Building your own NetBSD AMI - Xen PV](build_your_own_ami)
 * [Build instructions for NetBSD AMI with ENA support - HVM](http://www.netbsd.org/~ryoon/ena/how-to-create-ami-for-aws-c5.txt)
 * [NetBSD AMIs identifiers, by region](amis)
 * [Using bsdec2-image-upload to create an AMI](bsdec2_image_upload)

xen howto: Add Precedence Technologies.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.235
retrieving revision 1.236
diff -u -r1.235 -r1.236
--- wikisrc/ports/xen/howto.mdwn	7 Jan 2024 01:10:28 -0000	1.235
+++ wikisrc/ports/xen/howto.mdwn	9 Jan 2024 12:11:46 -0000	1.236
@@ -1043,6 +1043,14 @@
 
 As of 2023-12, NetBSD 10 kernels booting in PV mode crash during booting.
 
+### precedence.co.uk
+
+[Precedence Technologies](https://www.precedence.co.uk/) provide
+Xen-based NetBSD hosting.
+See their [dedicated hosting
+page](https://www.precedence.co.uk/internet/dedicated/) for some
+details.
+
 ### Amazon
 
 See the [Amazon EC2 page](/amazon_ec2/).

xen howto: Extend description of panix operation modes
(From a private discussion forked from the HOWTO update public
thread.)
Expand on booth methods
Expand on booth methods

Members: 
	ports/xen/howto.mdwn:1.234->1.235 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.234
retrieving revision 1.235
diff -u -r1.234 -r1.235
--- wikisrc/ports/xen/howto.mdwn	7 Jan 2024 00:57:21 -0000	1.234
+++ wikisrc/ports/xen/howto.mdwn	7 Jan 2024 01:10:28 -0000	1.235
@@ -979,6 +979,12 @@
 
 ## Boot methods
 
+### PVHVM
+
+With PVHVM (or HVM), the domU is started running the boot code on the
+domU disk and will load a kernel from the domU root filesystem, just
+like a physical machine or qemu.  As of early 2024 this is seeming like it might become the preferred method.
+
 ### pvgrub
 
 pvgrub is a version of grub that uses PV operations instead of BIOS
@@ -1004,6 +1010,10 @@
 dom0. For both these reasons, pygrub should not be used, and is only
 still present so that historical DomU images using it still work.
 
+### Kernel in dom0
+
+If you run your own dom0, putting the domU kernel there might be ok.
+
 ## Specific Providers
 
 The intent is to list providers only if they document support for

xen howto: Extend description of panix operation modes
(From a private discussion forked from the HOWTO update public
thread.)
Members: 
	ports/xen/howto.mdwn:1.233->1.234 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.233
retrieving revision 1.234
diff -u -r1.233 -r1.234
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:56:41 -0000	1.233
+++ wikisrc/ports/xen/howto.mdwn	7 Jan 2024 00:57:21 -0000	1.234
@@ -1013,8 +1013,13 @@
 
 [Panix](http://www.panix.com/) provides NetBSD as an OS option.  See
 their [Colocated Virtual Servers](https://www.panix.com/v-colo/) page
-for more information.  NetBSD 9 is available in PV mode, and NetBSD 10
-is available in PVHVM mode.
+for more information.  NetBSD 9 is available in PV mode,
+straightforwardly for amd64 and using the pvh/pvshim=1 technique
+described above for i386.  NetBSD 10 amd64 is available to customers
+in PVHVM mode, enabling booting a kernel from the VPS's filesystem.
+(NetBSD 10 also runs in PV and PVH mode on Panix's infrastructure, but
+PVHVM mode is preferred because it allows easy user control over the
+kernel.)
 
 ### tornadovps.com
 

xen howto: formatting
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.232
retrieving revision 1.233
diff -u -r1.232 -r1.233
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:54:45 -0000	1.232
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:56:41 -0000	1.233
@@ -1016,7 +1016,7 @@
 for more information.  NetBSD 9 is available in PV mode, and NetBSD 10
 is available in PVHVM mode.
 
-### Tornadovps.com
+### tornadovps.com
 
 [tornadovps.com](http://tornadovps.com/) provides 9.3, 9.1 and 8.2
 (amd64) and 9.1 and 8.2 (i386) netboot installers.  Users can use

xen howto: minor wording
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.231
retrieving revision 1.232
diff -u -r1.231 -r1.232
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:51:08 -0000	1.231
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:54:45 -0000	1.232
@@ -1012,9 +1012,9 @@
 ### panix.com
 
 [Panix](http://www.panix.com/) provides NetBSD as an OS option.  See
-their [Colocated Virtual Servers](https://www.panix.com/v-colo/) for
-more information.  NetBSD 9 is available in PV mode, and NetBSD 10 is
-available in PVHVM mode.
+their [Colocated Virtual Servers](https://www.panix.com/v-colo/) page
+for more information.  NetBSD 9 is available in PV mode, and NetBSD 10
+is available in PVHVM mode.
 
 ### Tornadovps.com
 

xen howto: adjust panix section
Use panix's preferred link and gc pvgrub stuff.
Members: 
	ports/xen/howto.mdwn:1.230->1.231 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.230
retrieving revision 1.231
diff -u -r1.230 -r1.231
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:43:17 -0000	1.230
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:51:08 -0000	1.231
@@ -1012,15 +1012,9 @@
 ### panix.com
 
 [Panix](http://www.panix.com/) provides NetBSD as an OS option.  See
-[the panix.com NetBSD upgrade instructions](https://www.panix.com/v-colo/nupgrade.html)
-for some information.
-Users can use pvgrub.  Panix reports that pvgrub works with FFsv2 with
-16K/2K and 32K/4K block/frag sizes (and hence with defaults from
-"newfs -O 2").  See [Panix's pvgrub
-page](http://www.panix.com/v-colo/grub.html) which describes how to
-boot NetBSD.
-
-As of early 2024, one can have a NetBSD 10 domU in PVHVM mode.
+their [Colocated Virtual Servers](https://www.panix.com/v-colo/) for
+more information.  NetBSD 9 is available in PV mode, and NetBSD 10 is
+available in PVHVM mode.
 
 ### Tornadovps.com
 

xen howto: enhance grant table
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.229
retrieving revision 1.230
diff -u -r1.229 -r1.230
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:40:20 -0000	1.229
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:43:17 -0000	1.230
@@ -893,6 +893,10 @@
 \todo Explain version 1 and 2 grant tables.  Explain which versions
 are needed by which NetBSD versions and what is default.
 
+See the gnttab Xen command line option.
+
+https://wiki.xenproject.org/wiki/Grant_Table
+
 ## Configuration of non-NetBSD dom0s to run NetBSD domUs
 
 Apparently one must have "pv-linear-pt=true" in the dom0 circumstances

xen howto: Add todo about grant tables
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.228
retrieving revision 1.229
diff -u -r1.228 -r1.229
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:38:33 -0000	1.228
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:40:20 -0000	1.229
@@ -888,6 +888,11 @@
 
 # Miscellaneous Information
 
+## Grant Table Versions
+
+\todo Explain version 1 and 2 grant tables.  Explain which versions
+are needed by which NetBSD versions and what is default.
+
 ## Configuration of non-NetBSD dom0s to run NetBSD domUs
 
 Apparently one must have "pv-linear-pt=true" in the dom0 circumstances

xen howto: rewrite console section
note netbsd 5 domUs are troubled.
mention pv-linear-pt option
mention pv-linear-pt option

Members: 
	ports/xen/howto.mdwn:1.227->1.228 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.227
retrieving revision 1.228
diff -u -r1.227 -r1.228
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:10:38 -0000	1.227
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:38:33 -0000	1.228
@@ -257,23 +257,24 @@
 By default, the hypervisor (Xen itself) will use some sort of vga
 device as the console, much like GENERIC uses by default.  The vga
 console is relinquished at the conclusion of hypervisor boot, before
-the dom0 is started.  Xen when using a vga console does not process
-console input.
+the dom0 is started.  In this case, Xen runs without a console.
+
+\todo Explain if one can +++ and interact with Xen while the hypervisor is booting.
 
 The hypervisor can be configured to use a serial port console, e.g.
 [[!template id=filecontent name="/boot.cfg" text="""
-menu=Xen:load /netbsd-XEN3_DOM0.gz console=com0;multiboot /xen.gz dom0_mem=512M console=com1 com1=9600,8n1
+menu=Xen:load /netbsd-XEN3_DOM0.gz; multiboot /xen.gz dom0_mem=512M console=com1
 """]]
 This example uses the first serial port (Xen counts from 1; this is
-what NetBSD would call com0), and sets speed and parity.  (The dom0 is
-then configured to use the same serial port in this example.)
-It is not clear that this is still a good approach (two opens of the serial port).
-
-If using serial console, then Xen will manage the serial port, and
-content (absent escape to the hypervisor) will be presented to the
-dom0 via xencons(4).
-See [this mailing list post](http://mail-index.netbsd.org/port-xen/2021/05/01/msg010149.html).
+what NetBSD would call com0), and sets speed and parity.
+
+If using a serial console the Xen kernel manages the serial port and
+connects it to the NetBSD-XEN3_DOM0 xencons(4) device.  The UART
+settings can be explicitly reset by the Xen kernel (see
+xen-command-line(7)), such as "com1=9600,8n1", but the settings done
+by the NetBSD /boot program should persist and will be used by Xen.
 
+\todo Explain "The default is vga,com1 and console=com1 can be left out."
 
 ### Selecting the console for NetBSD
 
@@ -288,14 +289,26 @@
 use of a keyboard to select a line from the menu.  And, one should
 have a working boot path to GENERIC for rescue situations.
 
+Note that com0 is never available to a NetBSD dom0; it is instead
+claimed by Xen, whether or not Xen uses it for a console.
+
 There are two paths: serial console and vga console.
 
-If using vga console with Xen, then pass console=pc via multiboot.
+If using a VGA console for the Xen server, pass "console=pc" to the
+NetBSD/XEN3_DOM0 command line:
+
+  menu=Xen:load /netbsd-XEN3_DOM0.gz console=pc;multiboot /xen.gz dom0_mem=512M
 
 If using serial console with Xen, then pass console=xencons.  NetBSD
-will obtain input from that virtual device and send output there.  Xen
-will pass the output to the serial port, and will pass input from the
-serial port to NetBSD, except for commands for the hypervisor. 
+will obtain input from xencons(4) and send output there.  Xen will
+pass the output to the serial port, and will pass input from the
+serial port to NetBSD, except for commands for the hypervisor.  See
+[this mailing list
+post](http://mail-index.netbsd.org/port-xen/2021/05/01/msg010149.html).
+
+It is not actually necessary to pass console=xencons, for NetBSD >= 9
+(earlier?), as it will default to that.
+\todo Explain why this default happens.
 
 \todo Document what happens by default in both situations, but for a
 recommendation for explicit configuration seems robust.
@@ -307,6 +320,8 @@
 "dom0=msr-relaxed=1" on the boof.cfg line.  (See
 /src/sys/arch/x86/x86/pmap.c revision 1.410.)
 
+(NetBSD 5 domUs appear to be troubled with recent Xen and NetBSD dom0.)
+
 ### Tuning
 
 With NetBSD 9 and below, one could add `dom0_max_vcpus=1
@@ -530,6 +545,11 @@
 sum of the the memory allocated to the dom0 and all domUs must be less
 than the available memory.
 
+## Console
+
+A domU with PV support will use xencons(4) as the console, and one can
+access this from the dom0 with "xl console".
+
 ## Virtual disks
 
 In domU config files, the disks are defined as a sequence of 3-tuples:
@@ -868,6 +888,14 @@
 
 # Miscellaneous Information
 
+## Configuration of non-NetBSD dom0s to run NetBSD domUs
+
+Apparently one must have "pv-linear-pt=true" in the dom0 circumstances
+in order for NetBSD domUs to run.  This is default, but only available
+if Xen is compiled with CONFIG_PV_LINEAR_PT.
+
+https://xenbits.xen.org/docs/unstable/misc/xen-command-line.html#pv-linear-pt-x86
+
 ## Nesting under Linux KVM
 
 It is possible to run Xen and a NetBSD dom0 under Linux KVM.  One

Link directly to Xen hosting providers' NetBSD docs.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.226
retrieving revision 1.227
diff -u -r1.226 -r1.227
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:03:47 -0000	1.226
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:10:38 -0000	1.227
@@ -975,7 +975,8 @@
 ### panix.com
 
 [Panix](http://www.panix.com/) provides NetBSD as an OS option.  See
-https://www.panix.com/v-colo/nupgrade.html for some information.
+[the panix.com NetBSD upgrade instructions](https://www.panix.com/v-colo/nupgrade.html)
+for some information.
 Users can use pvgrub.  Panix reports that pvgrub works with FFsv2 with
 16K/2K and 32K/4K block/frag sizes (and hence with defaults from
 "newfs -O 2").  See [Panix's pvgrub
@@ -990,7 +991,7 @@
 (amd64) and 9.1 and 8.2 (i386) netboot installers.  Users can use
 grub2 or pvgrub to boot their own kernel (pvgrub needs a small FAT32
 /boot).  See the [tornadovps.com NetBSD
-instructions](https://tornadovps.com/).
+instructions](https://tornadovps.com/documentation/netbsd).
 
 The main path for NetBSD is PV mode, but HVM modes might also work.
 

xen howto: detangle xen console and netbsd console
no real change, just detangle.
Members: 
	ports/xen/howto.mdwn:1.225->1.226 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.225
retrieving revision 1.226
diff -u -r1.225 -r1.226
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 18:46:01 -0000	1.225
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 19:03:47 -0000	1.226
@@ -247,27 +247,13 @@
 that adding `userconf=pckbc` to `/boot.cfg` causes Xen to crash very
 early with a heap overflow.
 
-### Console selection
-
-See boot_console(8).  Understand that you should start from a place of
-having console setup correct for booting GENERIC before trying to
-configure Xen.
-
-Generally for GENERIC, one sets the console in bootxx_ffsv1 or
-equivalent, and this is passed on to /boot (where one typically does
-not set the console).  This configuration of bootxx_ffsv1 should also
-be in place for Xen systems, to allow seeing messages from /boot and
-use of a keyboard to select a line from the menu.  And, one should
-have a working boot path to GENERIC for rescue situations.
+### Selecting the console for Xen
 
 With GENERIC, the boot options are passed on to /netbsd, but there is
 currently no mechanism to pass these via multiboot to the hypervisor.
 Thus, in addition to configuring the console in the boot blocks, one
 must also configure it for Xen.
 
-There are two paths: serial console and vga console.
-The NetBSD dom0 will attach xencons(4) and may attach vga(4).
-
 By default, the hypervisor (Xen itself) will use some sort of vga
 device as the console, much like GENERIC uses by default.  The vga
 console is relinquished at the conclusion of hypervisor boot, before
@@ -287,14 +273,32 @@
 content (absent escape to the hypervisor) will be presented to the
 dom0 via xencons(4).
 See [this mailing list post](http://mail-index.netbsd.org/port-xen/2021/05/01/msg010149.html).
-\todo Is it necessary to pass console=xencons, or is this reliably defaulted?
 
-If using vga console, pass console=pc via multiboot.
 
-While one might expect console=pc to be default, following behavior of
-GENERIC, a hasty read of the code suggests there is no default and
-booting without a selected console might lead to a panic.
-\todo Update this for 9/10 and up.
+### Selecting the console for NetBSD
+
+See boot_console(8).  Understand that you should start from a place of
+having console setup correct for booting GENERIC before trying to
+configure Xen.
+
+Generally for GENERIC, one sets the console in bootxx_ffsv1 or
+equivalent, and this is passed on to /boot (where one typically does
+not set the console).  This configuration of bootxx_ffsv1 should also
+be in place for Xen systems, to allow seeing messages from /boot and
+use of a keyboard to select a line from the menu.  And, one should
+have a working boot path to GENERIC for rescue situations.
+
+There are two paths: serial console and vga console.
+
+If using vga console with Xen, then pass console=pc via multiboot.
+
+If using serial console with Xen, then pass console=xencons.  NetBSD
+will obtain input from that virtual device and send output there.  Xen
+will pass the output to the serial port, and will pass input from the
+serial port to NetBSD, except for commands for the hypervisor. 
+
+\todo Document what happens by default in both situations, but for a
+recommendation for explicit configuration seems robust.
 
 ### Older NetBSD kernels
 

Note PVHVM netbsd 10 at panix
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.224
retrieving revision 1.225
diff -u -r1.224 -r1.225
--- wikisrc/ports/xen/howto.mdwn	6 Jan 2024 18:40:37 -0000	1.224
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 18:46:01 -0000	1.225
@@ -978,7 +978,9 @@
 page](http://www.panix.com/v-colo/grub.html) which describes how to
 boot NetBSD.
 
-### tornadovps.com
+As of early 2024, one can have a NetBSD 10 domU in PVHVM mode.
+
+### Tornadovps.com
 
 [tornadovps.com](http://tornadovps.com/) provides 9.3, 9.1 and 8.2
 (amd64) and 9.1 and 8.2 (i386) netboot installers.  Users can use

xen howto: explain pvhvm benefits
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.223
retrieving revision 1.224
diff -u -r1.223 -r1.224
--- wikisrc/ports/xen/howto.mdwn	1 Jan 2024 23:09:30 -0000	1.223
+++ wikisrc/ports/xen/howto.mdwn	6 Jan 2024 18:40:37 -0000	1.224
@@ -61,18 +61,8 @@
 guests must be specifically coded for Xen.  See
 [PV](https://wiki.xen.org/wiki/Paravirtualization_(PV\)).
 
-In HVM (Hardware Virtual Machine) mode, guest operating systems with
-no knowledge of or accomodation for Xen can be run.  However, hardware
-support is required, such as VT-x on Intel CPUs and SVM on AMD CPUs to
-assist with the processor emulation.  The dom0 runs qemu to emulate
-hardware other than the processor.  It is therefore non-sensical to
-have an HVM dom0, because there is no underlying system to provide
-emulation.
-
-In PVHVM mode, the guest runs as HVM, but additionally uses PV
-drivers for efficiency.  Therefore it is non-sensical for to have a
-PVHVM dom0.  See [PV on HVM](https://wiki.xen.org/wiki/PV_on_HVM).
-
+PVH is substantially more efficient than PV because it uses hardware
+assisted virtualization.
 There have been two PVH modes: original PVH and PVHv2.  Original PVH
 was based on PV mode and is no longer relevant at all.  Therefore
 PVHv2 is written as PVH, here and elsewhere.  PVH is basically
@@ -82,9 +72,21 @@
 config files use pvh -- these refer to PVHv2.  See
 [PVH(v2)](https://wiki.xenproject.org/wiki/PVH_(v2\)_Domu).
 
-PVH is substantially more efficient than PV because it uses hardware
-assisted virtualization.  \todo Say how HVM, PVHVM and PVH compare.
-Explain if there is any reason to choose HVM or PVHVM if PVH works.
+In HVM (Hardware Virtual Machine) mode, guest operating systems with
+no knowledge of or accomodation for Xen can be run.  However, hardware
+support is required, such as VT-x on Intel CPUs and SVM on AMD CPUs to
+assist with the processor emulation.  The dom0 runs qemu to emulate
+hardware other than the processor.  It is therefore non-sensical to
+have an HVM dom0, because there is no underlying system to provide
+emulation.  HVM can be useful to work around bugs even if some other
+mode could be used.
+
+In PVHVM mode, the guest runs as HVM, but additionally uses PV drivers
+for efficiency.  Therefore it is non-sensical for to have a PVHVM
+dom0.  See [PV on HVM](https://wiki.xen.org/wiki/PV_on_HVM).  PCI
+passthrough works on PVHVM.  Booting uses the domU's boot blocks and a
+kernel stored in the domU's filesystem.  This can be useful in VPS
+situations where the owner of the domU has no access to the dom0.
 
 At system boot, the dom0 kernel is loaded as a module with Xen as the
 kernel.  The dom0 can start one or more domUs.  (Booting is explained

RPI howto: Note creds_msdos(8).
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.149
retrieving revision 1.150
diff -u -r1.149 -r1.150
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	2 Jan 2024 13:37:58 -0000	1.149
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	2 Jan 2024 16:42:12 -0000	1.150
@@ -140,6 +140,8 @@
 
 If you want to enable ssh with the standard image, so that you can log in over the net without either a serial or HDMI console, you can edit the configuration of a uSD card before booting.   On another computer, mount the ffs partition, place /root/.ssh/authorized_keys, uncomment PermitRootLogin in /etc/ssh/sshd_config, and comment out the rc_configure=NO in /etc/rc.conf.  Besides having to find the IP address (e.g. from DHCP server logs), you will have to wait for the partition resizing and reboot.
 
+As a likely preferred alternative, see creds_msdos(8) which describes a way to install a key via /boot/creds.txt.  Note that creds_msdos is not part of a normal system installation and is only present on install media.
+
 ### Installation with sshramdisk image
 
 \todo Verify if this is still accurate.  If only for earmv6, explain why or file bug to have the rest support it.  If rpi_inst is historical, gc this section.
@@ -230,7 +232,7 @@
 
 ## vcgencmd
 
-The program vcgencmd, referenced in the boot section,  can be found in pkgsrc/misc/raspberrypi-userland.
+The program vcgencmd, referenced in the boot section, can be found in pkgsrc/misc/raspberrypi-userland.
 
 ## Updating the kernel
 
@@ -262,13 +264,13 @@
 
 It seems that some systems, including RPI, require dtb files in /boot, and some expect them in /boot/dtb.
 
-### NetBSD current
+### NetBSD 10
 
 When updating, ensure that /boot is mounted and that you unpack the dtb set.
 
 ## Updating the firmware
 
-It is highly likely that running NetBSD from a given branch X with firmware from a branch Y < X will not go well.  It is unclear if firmware from a branch Y > X will work.  It is standard practice to use firmware from the right branch.
+It is somewhat likely that running NetBSD from a given branch X with firmware from a branch Y < X will not go well.  It is unclear if firmware from a branch Y > X will work.  It is standard practice to use firmware from the right branch.   An alternative view is that newer firmware is usually better, and the the firmware needs to be new enough for the hardware.
 
 A section below describes the process of updating NetBSD's copy of the firmware from upstream, with testing, by NetBSD developers.  This section is about updating a system's firmware from the firmware in a version of NetBSD.
 

rpi howto: Note lack of RPI5 support
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.148
retrieving revision 1.149
diff -u -r1.148 -r1.149
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	2 Jan 2024 00:21:46 -0000	1.148
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	2 Jan 2024 13:37:58 -0000	1.149
@@ -1,10 +1,8 @@
 [[!meta title="NetBSD/evbarm on Raspberry Pi"]]
 
-This page describes the NetBSD/evbarm port on [Raspberry Pi](http://www.raspberrypi.org) hardware.  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are believed supported, and specific boards known to work are listed.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
+This page describes the NetBSD/evbarm and NetBSD/evbarm64 (sometimes written /aarch64) ports on [Raspberry Pi](http://www.raspberrypi.org) hardware.  Most [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are believed supported, and specific boards known to work are listed on this page.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
 
-\todo Explain if RPI5 works or not!!!
-
-This page also describes the aarch64 cpu flavor of evbarm, also written evbarm64 or NetBSD/aarch64.
+As of early 2024, NetBSD does not support the Raspberry Pi 5.
 
 Initial Raspberry Pi support was introduced in NetBSD 6.0.  NetBSD 7.0 added complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board.  Raspberry Pi 3 support was added for NetBSD 8.  NetBSD 9 supports aarch64, meaning using the newer processors in 64-bit mode.   NetBSD 10 supports the RPI 4.
 

Welcome to 2024!
Index: wikisrc/templates/page.tmpl
===================================================================
RCS file: /cvsroot/wikisrc/templates/page.tmpl,v
retrieving revision 1.74
retrieving revision 1.75
diff -u -r1.74 -r1.75
--- wikisrc/templates/page.tmpl	2 Jan 2023 07:55:26 -0000	1.74
+++ wikisrc/templates/page.tmpl	2 Jan 2024 08:02:22 -0000	1.75
@@ -262,7 +262,7 @@
     <span class="footcopy"><a href="//www.NetBSD.org/about/disclaimer.html">
       Disclaimer</a> |
       <span class="copyright">
-        Copyright &copy; 1994-2023 The NetBSD Foundation, Inc.
+        Copyright &copy; 1994-2024 The NetBSD Foundation, Inc.
       </span>
       ALL
       RIGHTS RESERVED. <br /> NetBSD<sup>&reg;</sup> is a registered

rpi: minor updates to reality
Index: wikisrc/ports/evbarm/raspberry_pi.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm/raspberry_pi.mdwn,v
retrieving revision 1.147
retrieving revision 1.148
diff -u -r1.147 -r1.148
--- wikisrc/ports/evbarm/raspberry_pi.mdwn	5 Jun 2022 11:53:19 -0000	1.147
+++ wikisrc/ports/evbarm/raspberry_pi.mdwn	2 Jan 2024 00:21:46 -0000	1.148
@@ -2,9 +2,11 @@
 
 This page describes the NetBSD/evbarm port on [Raspberry Pi](http://www.raspberrypi.org) hardware.  All [board variants](https://en.wikipedia.org/wiki/Raspberry_Pi#Specifications) are believed supported, and specific boards known to work are listed.  We use e.g. "RPI2" to refer to "Raspberry Pi 2" to save precious bytes on this page.
 
-This page also describes the aarch64 cpu flavor of evbarm, also written NetBSD/aarch64.
+\todo Explain if RPI5 works or not!!!
 
-Initial Raspberry Pi support was introduced in NetBSD 6.0.  NetBSD 7.0 added complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board.  Raspberry Pi 3 support was added for NetBSD 8.  NetBSD 9 supports aarch64, meaning using the newer processors in 64-bit mode.   NetBSD 10 (today, -current) supports the RPI 4.
+This page also describes the aarch64 cpu flavor of evbarm, also written evbarm64 or NetBSD/aarch64.
+
+Initial Raspberry Pi support was introduced in NetBSD 6.0.  NetBSD 7.0 added complete support for the board, along with introducing support for the quad-core Raspberry Pi 2 board.  Raspberry Pi 3 support was added for NetBSD 8.  NetBSD 9 supports aarch64, meaning using the newer processors in 64-bit mode.   NetBSD 10 supports the RPI 4.
 
 [[images/raspberrypi.jpg]]
 
@@ -14,6 +16,9 @@
 
 # What works
 
+Note that NetBSD 8 is very out of date relative to RPI.  Asking about
+it will surely result in advice to upgrade.
+
 ## NetBSD 8
 
  - RPI1, RPI2, RPI2-1.2, RPI3, RPI3+ (except RPI3 builtin WiFi and bluetooth)
@@ -40,7 +45,7 @@
  - aarch64 support (RPI3, and should work on all supported systems with 64-bit CPUs, but not audio)
  - RPI3 new SD host controller driver
 
-## NetBSD current
+## NetBSD 10
 
  - RPI4 (using EDK2 UEFI firmware)
 	- RPI4 Ethernet (Broadcom GENETv5) - genet(4); needs man page
@@ -51,6 +56,10 @@
  - RPI3 and RPI0W builtin WiFi - [bwfm(4)](//man.netbsd.org/bwfm.4)
  - Big endian support
 
+## NetBSD current
+
+ - \todo Is anything supported in current that doesn't work in 10?  RPI5???
+
 ## What needs documenting if it works
 
  - CM1
@@ -84,6 +93,7 @@
 - The Raspberry Pi 1 requires the ARMv6 [rpi.img.gz](http://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-earmv6hf/binary/gzimg/rpi.img.gz).
 - The Raspberry Pi 2-3 can use the standard ARMv7 [armv7.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-earmv7hf/binary/gzimg/armv7.img.gz) image.
 - The Raspberry Pi 3 can also use [arm64.img.gz](https://nycdn.netbsd.org/pub/NetBSD-daily/netbsd-9/latest/evbarm-aarch64/binary/gzimg/arm64.img.gz).
+- \todo RPI4 NetBSD 10 image
 
 Decompress it and write it to the SD card:
 
@@ -134,6 +144,8 @@
 
 ### Installation with sshramdisk image
 
+\todo Verify if this is still accurate.  If only for earmv6, explain why or file bug to have the rest support it.  If rpi_inst is historical, gc this section.
+
 build.sh (and hence the FTP site) also creates an image 'rpi_inst.img.gz' specifically for installation without HDMI or a serial console, when built for earmv6hf.  Note that this image is much smaller and that you will need to fetch the sets over the network.  To use this method, write that image to a uSD card as above, and then:
 
  - Connect an Ethernet cable from the RPI to a LAN with a DHCP server, and another host you can use for ssh.

xen howto: Explain dom0=pvh and rototill serial console section
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.222
retrieving revision 1.223
diff -u -r1.222 -r1.223
--- wikisrc/ports/xen/howto.mdwn	1 Jan 2024 16:14:14 -0000	1.222
+++ wikisrc/ports/xen/howto.mdwn	1 Jan 2024 23:09:30 -0000	1.223
@@ -263,6 +263,9 @@
 Thus, in addition to configuring the console in the boot blocks, one
 must also configure it for Xen.
 
+There are two paths: serial console and vga console.
+The NetBSD dom0 will attach xencons(4) and may attach vga(4).
+
 By default, the hypervisor (Xen itself) will use some sort of vga
 device as the console, much like GENERIC uses by default.  The vga
 console is relinquished at the conclusion of hypervisor boot, before
@@ -276,24 +279,27 @@
 This example uses the first serial port (Xen counts from 1; this is
 what NetBSD would call com0), and sets speed and parity.  (The dom0 is
 then configured to use the same serial port in this example.)
+It is not clear that this is still a good approach (two opens of the serial port).
 
-With the hypervisor configured for a serial console, it can get input,
-and there is a notion of passing this input to the dom0.  \todo
-Explain why, if Xen has a serial console, the dom0 console is
-typically also configured to open that same serial port, instead of
-getting the passthrough input via the xen console.
-
-One also configures the console for the dom0.  While one might expect
-console=pc to be default, following behavior of GENERIC, a hasty read
-of the code suggests there is no default and booting without a
-selected console might lead to a panic.  Also, there is merit in
-explicit configuration.  Therefore the standard approach is to place
-console=pc as part of the load statement for the dom0 kernel, or
-alternatively console=com0.
-
-The NetBSD dom0 kernel will attach xencons(4) (the man page does not
-exist), but this is not used as a console.  It is used to obtain the
-messages from the hypervisor's console; run `xl dmesg` to see them.
+If using serial console, then Xen will manage the serial port, and
+content (absent escape to the hypervisor) will be presented to the
+dom0 via xencons(4).
+See [this mailing list post](http://mail-index.netbsd.org/port-xen/2021/05/01/msg010149.html).
+\todo Is it necessary to pass console=xencons, or is this reliably defaulted?
+
+If using vga console, pass console=pc via multiboot.
+
+While one might expect console=pc to be default, following behavior of
+GENERIC, a hasty read of the code suggests there is no default and
+booting without a selected console might lead to a panic.
+\todo Update this for 9/10 and up.
+
+### Older NetBSD kernels
+
+When the dom0 kernel is NetBSD 8 and earlier, or NetBSD 9 before
+2021-04-17 (9.3 is ok), Xen 4.15 and later require
+"dom0=msr-relaxed=1" on the boof.cfg line.  (See
+/src/sys/arch/x86/x86/pmap.c revision 1.410.)
 
 ### Tuning
 
@@ -704,7 +710,9 @@
 
 This is only supported for NetBSD 10 and up as the guest.
 
-Use type='pvh'.  Configure GENERIC instead of XEN3_DOMU.
+Use type='pvh'.  Configure GENERIC instead of XEN3_DOMU.  In boot.cfg,
+add dom0=pvh.  (dom0=pv is the default, which is why this expression
+has not been previously discussed.)
 
 Operation of i386 PVH guests is not reliable.
 See [PR 57199](https://gnats.netbsd.org/57199).

xen howto: prune some old text about i386 being maybe faster.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.221
retrieving revision 1.222
diff -u -r1.221 -r1.222
--- wikisrc/ports/xen/howto.mdwn	1 Jan 2024 16:04:53 -0000	1.221
+++ wikisrc/ports/xen/howto.mdwn	1 Jan 2024 16:14:14 -0000	1.222
@@ -61,17 +61,17 @@
 guests must be specifically coded for Xen.  See
 [PV](https://wiki.xen.org/wiki/Paravirtualization_(PV\)).
 
-In HVM (Hardware Virtual Machine) mode, no guest modification is
-required.  However, hardware support is required, such as VT-x on
-Intel CPUs and SVM on AMD CPUs to assist with the processor emulation.
-The dom0 runs qemu to emulate hardware other than the processor.  It
-is therefore non-sensical to have an HVM dom0, because there is no
-underlying system to provide emulation.
+In HVM (Hardware Virtual Machine) mode, guest operating systems with
+no knowledge of or accomodation for Xen can be run.  However, hardware
+support is required, such as VT-x on Intel CPUs and SVM on AMD CPUs to
+assist with the processor emulation.  The dom0 runs qemu to emulate
+hardware other than the processor.  It is therefore non-sensical to
+have an HVM dom0, because there is no underlying system to provide
+emulation.
 
 In PVHVM mode, the guest runs as HVM, but additionally uses PV
 drivers for efficiency.  Therefore it is non-sensical for to have a
 PVHVM dom0.  See [PV on HVM](https://wiki.xen.org/wiki/PV_on_HVM).
-\todo Explain why someone would run PVHVM instead of PVH.
 
 There have been two PVH modes: original PVH and PVHv2.  Original PVH
 was based on PV mode and is no longer relevant at all.  Therefore
@@ -83,7 +83,8 @@
 [PVH(v2)](https://wiki.xenproject.org/wiki/PVH_(v2\)_Domu).
 
 PVH is substantially more efficient than PV because it uses hardware
-assisted virtualization.  \todo Say how HVM and PVH compare.
+assisted virtualization.  \todo Say how HVM, PVHVM and PVH compare.
+Explain if there is any reason to choose HVM or PVHVM if PVH works.
 
 At system boot, the dom0 kernel is loaded as a module with Xen as the
 kernel.  The dom0 can start one or more domUs.  (Booting is explained
@@ -95,11 +96,9 @@
 
 There is a concept of Xen running on ARM, but there are no reports of this working with NetBSD.
 
-The dom0 system should be amd64.  (Instructions for i386PAE dom0 have been removed from the HOWTO.)
+The dom0 system must be amd64.
 
-The domU can be i386 PAE or amd64.
-i386 PAE at one point was considered as [faster](https://lists.xen.org/archives/html/xen-devel/2012-07/msg00085.html) than amd64.
-However, as of 2021 it is normal to use amd64 as the domU architecture, and use of i386 is dwindling.
+The domU can be i386 PAE or amd64.  It can be various operating systems.
 
 ## Xen Versions
 
@@ -716,6 +715,12 @@
 ## Creating a NetBSD HVM domU
 
 Use type='hvm', probably.  Use a GENERIC kernel within the disk image.
+\todo Confirm and fix text.
+
+## Creating a NetBSD PVHVM domU
+
+Use type='pvhvm', guessing wildly.  Use a GENERIC kernel within the disk image.
+\todo Confirm and fix text.
 
 ## Creating a FreeBSD domU
 

xen howto: tweak pvh
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.220
retrieving revision 1.221
diff -u -r1.220 -r1.221
--- wikisrc/ports/xen/howto.mdwn	1 Jan 2024 16:02:39 -0000	1.220
+++ wikisrc/ports/xen/howto.mdwn	1 Jan 2024 16:04:53 -0000	1.221
@@ -623,7 +623,7 @@
 file should be present in the domU as /netbsd so that tools like
 savecore(8) can work.   (This is helpful but not necessary.)
 
-The kernel must be specifically built for Xen, to use PV interfacesas
+The kernel must be specifically built for Xen, to use PV interfaces as
 a domU.  NetBSD release builds provide the following kernels:
 
         i386 XEN3PAE_DOMU
@@ -690,15 +690,15 @@
 
 ## Creating a NetBSD PV Shim domU
 
-This is like a PV domU, but has a shim between dom0 and domU.
+This is like a PV domU, but has a second copy of xen (shim) between
+dom0 and domU.
 
 Configure as for pv, but add
 
     type="pvh"
     pvshim=1
 
-This runs another copy of Xen in the domU which then runs the NetBSD kernel.
-The domU system itself is unchanged; it still uses a PV (XEN3_DOMU) kernel,
+The domU system itself is unchanged; it still uses a PV (XEN3_DOMU or XEN3PAE_DOMU) kernel,
 and still sees the same devices.
 
 ## Creating a NetBSD PVH domU

xen howto: updates and fixes
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.219
retrieving revision 1.220
diff -u -r1.219 -r1.220
--- wikisrc/ports/xen/howto.mdwn	1 Jan 2024 14:55:58 -0000	1.219
+++ wikisrc/ports/xen/howto.mdwn	1 Jan 2024 16:02:39 -0000	1.220
@@ -71,6 +71,7 @@
 In PVHVM mode, the guest runs as HVM, but additionally uses PV
 drivers for efficiency.  Therefore it is non-sensical for to have a
 PVHVM dom0.  See [PV on HVM](https://wiki.xen.org/wiki/PV_on_HVM).
+\todo Explain why someone would run PVHVM instead of PVH.
 
 There have been two PVH modes: original PVH and PVHv2.  Original PVH
 was based on PV mode and is no longer relevant at all.  Therefore
@@ -81,6 +82,9 @@
 config files use pvh -- these refer to PVHv2.  See
 [PVH(v2)](https://wiki.xenproject.org/wiki/PVH_(v2\)_Domu).
 
+PVH is substantially more efficient than PV because it uses hardware
+assisted virtualization.  \todo Say how HVM and PVH compare.
+
 At system boot, the dom0 kernel is loaded as a module with Xen as the
 kernel.  The dom0 can start one or more domUs.  (Booting is explained
 in detail in the dom0 section.)
@@ -599,6 +603,17 @@
 
 Of course, this section presumes that you have a working dom0.
 
+Many of the following examples advise adding lines to config files.
+While it (mostly?) doesn't matter how lines are ordered, best practice
+is to keep "type" lines near "kernel" lines, as they tend to require
+being changed aat the same time.
+
+## Stub domains
+
+Xen has a concept of stub domains, where the qemu part of HVM is in a
+domU.  \todo Explain better, and once understood, migrate this section
+to where it belongs.
+
 ## Creating a NetBSD PV domU
 
 See the earlier config file, and adjust memory.  Decide on how much
@@ -676,15 +691,15 @@
 ## Creating a NetBSD PV Shim domU
 
 This is like a PV domU, but has a shim between dom0 and domU.
-\todo Is it valid to say that "shim" and "stub domain" are the same thing?
 
 Configure as for pv, but add
 
     type="pvh"
     pvshim=1
 
-The domU itself is unchanged; it still uses a PV (XEN3_DOMU) kernel,
-and still sees the same kernel.
+This runs another copy of Xen in the domU which then runs the NetBSD kernel.
+The domU system itself is unchanged; it still uses a PV (XEN3_DOMU) kernel,
+and still sees the same devices.
 
 ## Creating a NetBSD PVH domU
 
@@ -702,11 +717,20 @@
 
 Use type='hvm', probably.  Use a GENERIC kernel within the disk image.
 
+## Creating a FreeBSD domU
+
+For pvh: use type='pvh'.  Configure a generic kernel.
+
+For others: \todo
+
 ## Creating a Linux PV domU
 
 Creating unprivileged Linux domains isn't much different from
 unprivileged NetBSD domains, but there are some details to know.
 
+NOTE: This is old text, and aparently Linux no longer supports PV.
+Instead, use pvh.
+
 First, the second parameter passed to the disk declaration (the '0x1' in
 the example below)
 

xen howto: Add in PVH shim description
Adjust a bunch of other sections based on my increased understanding.
Thanks to Brad for offlist hints.
Members: 
	ports/xen/howto.mdwn:1.218->1.219 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.218
retrieving revision 1.219
diff -u -r1.218 -r1.219
--- wikisrc/ports/xen/howto.mdwn	1 Jan 2024 01:07:07 -0000	1.218
+++ wikisrc/ports/xen/howto.mdwn	1 Jan 2024 14:55:58 -0000	1.219
@@ -117,9 +117,12 @@
 As of December 2023, 4.15 has been working well on NetBSD 8 through
 current with both i386 and amd64 guests and is the standard approach.
 
-4.18 works well for amd64 PV guests, when the dom0 is NetBSD 10 and
-has had some testing on NetBSD-current.  It runs a NetBSD 9 PV domU
-well.  \todo Describe i386 and amd64 HVM guest status.
+4.18 works well, when the dom0 is NetBSD 10 and has had some testing
+on NetBSD-current.  It runs a NetBSD 9 PV domU well.  Note that i386
+PV guests are no longer supported; see the "PVH shim" section below
+for the required adjustment.
+
+\todo Describe i386 and amd64 PVH and HVM guest status.
 
 It is not clear if 4.18 will run well or not on NetBSD 9 as a dom0.
 It is likely to be troubled on NetBSD 8 as a dom0 (which is expected
@@ -138,9 +141,12 @@
 NetBSD Xen has always supported PV, in both dom0 and domU -- this used
 to be the only way.  NetBSD 8 and later as a dom0 supports HVM mode in domUs.
 
-Support for PVHVM and PVH is available in NetBSD 10; this is
-currently somewhat experimental, although PVHVM appears reasonably
-solid.
+Support for PVHVM and PVH is available in NetBSD 10; this is currently
+somewhat experimental, although PVHVM appears reasonably solid.  Note
+that these require newer CPU features than just PV, but as of 2023
+most hardware that one intends to actually use with Xen is likely to
+have support.  \todo Describe the CPU flags or provide a link to
+upstream.
 
 NetBSD up to and including NetBSD 9 as a dom0 cannot safely run SMP.
 Even if one added "options MULTIPROCESSOR" and configured multiple
@@ -667,6 +673,35 @@
 Note that NetBSD by default creates only xbd[0123].  If you need more
 virtual disks in a domU, run e.g. "./MAKEDEV xbd4" in the domU.
 
+## Creating a NetBSD PV Shim domU
+
+This is like a PV domU, but has a shim between dom0 and domU.
+\todo Is it valid to say that "shim" and "stub domain" are the same thing?
+
+Configure as for pv, but add
+
+    type="pvh"
+    pvshim=1
+
+The domU itself is unchanged; it still uses a PV (XEN3_DOMU) kernel,
+and still sees the same kernel.
+
+## Creating a NetBSD PVH domU
+
+This is only supported for NetBSD 10 and up as the guest.
+
+Use type='pvh'.  Configure GENERIC instead of XEN3_DOMU.
+
+Operation of i386 PVH guests is not reliable.
+See [PR 57199](https://gnats.netbsd.org/57199).
+
+\todo Verify if one can have netbsd-10 PVH domU on a 9 dom0, and
+adjust the dom0 pvh text.
+
+## Creating a NetBSD HVM domU
+
+Use type='hvm', probably.  Use a GENERIC kernel within the disk image.
+
 ## Creating a Linux PV domU
 
 Creating unprivileged Linux domains isn't much different from
@@ -710,21 +745,6 @@
 to your configuration since not all Linux distributions auto-attach a
 tty to the xen console.
 
-## Creating a NetBSD HVM domU
-
-Use type='hvm', probably.  Use a GENERIC kernel within the disk image.
-
-## Creating a NetBSD PVH domU
-
-This only works with a current kernel in the domU.
-
-Use type='pvh'.  Probably, use a GENERIC kernel within the disk image,
-which in current has PV support.
-
-\todo Verify.
-
-\todo Verify if one can have current PVH domU on a 9 dom0.
-
 ## Creating a Solaris domU
 
 See possibly outdated

xen: Revise downward 4.18 status to reflect no-PV-i386 reality.
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.217
retrieving revision 1.218
diff -u -r1.217 -r1.218
--- wikisrc/ports/xen/howto.mdwn	8 Dec 2023 15:44:17 -0000	1.217
+++ wikisrc/ports/xen/howto.mdwn	1 Jan 2024 01:07:07 -0000	1.218
@@ -115,10 +115,15 @@
 """]]
 
 As of December 2023, 4.15 has been working well on NetBSD 8 through
-current and is the standard approach.  4.18 works well on NetBSD 10
-and has had some testing on NetBSD-current.  It is not clear if it
-will run well or not on NetBSD 9.  It is likely to be troubled on
-NetBSD 8 (which is expected to be no longer relevant very soon).
+current with both i386 and amd64 guests and is the standard approach.
+
+4.18 works well for amd64 PV guests, when the dom0 is NetBSD 10 and
+has had some testing on NetBSD-current.  It runs a NetBSD 9 PV domU
+well.  \todo Describe i386 and amd64 HVM guest status.
+
+It is not clear if 4.18 will run well or not on NetBSD 9 as a dom0.
+It is likely to be troubled on NetBSD 8 as a dom0 (which is expected
+to be no longer relevant very soon).
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 

2023,Thanx for your kindly supports to our NetBSD Booth and BoFs all around Japan.See you 2024.
--- /dev/null	2023-12-25 05:45:04.850232334 +0000
+++ wikisrc/users/jun/2023.mdwn	2023-12-25 05:45:27.798447872 +0000
@@ -0,0 +1,144 @@
+## Open Source Conference 2023 Fukuoka NetBSD Booth&BoF
+- 2023 Dec.9 Sat 10:00-18:00 JST (UTC+9) 
+- Fukuoka Soft Research Park [[https://www.fukuoka-srp.co.jp/]]
+- [[https://event.ospn.jp/osc2023-fukuoka/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023fukuoka.pdf]]
+- togetter [[https://togetter.com/li/2271317]]
+
+## Open Source Conference 2023 Niigata NetBSD Booth&BoF
+- 2022 Nov.12 Sun 10:00-18:00 JST (UTC+9) 
+- Niigata City Public Library [[https://www.niigatacitylib.jp/?page_id=166]]
+- [[https://event.ospn.jp/osc2023-niigata/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023niigata.pdf]]
+- togetter [[https://togetter.com/li/2260623]]
+
+## Open Source Conference 2023 Hiroshima NetBSD Booth&BoF
+- 2022 Nov.12 Sun 10:00-18:00 JST (UTC+9) 
+- Satellite Campus Hiroshima [[https://www.pu-hiroshima.ac.jp/site/satellite/accessmap.html]]
+- [[https://event.ospn.jp/osc2023-hiroshima/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023hiroshima.pdf]]
+- togetter [[https://togetter.com/li/2254094]]
+- [[https://speakerdeck.com/tsutsui/kof2023]]
+- [[http://www.pastel-flower.jp/~isaki/NetBSD/osc23hi/]]
+
+## Kansai Open Forum 2023
+- [[https://www.k-of.jp/]]
+- 2023 Nov.10 Fri. - Nov.11 Sat.
+- Booth and BSD BoF
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/KOF2023.pdf]]
+- togetter [[https://togetter.com/li/2254094]]
+- [[https://speakerdeck.com/tsutsui/kof2023]]
+
+## Open Source Conference 2023 Shimane NetBSD Booth
+- 2023 Oct.28 Sat 10:00-17:30 JST (UTC+9)
+- Matsue Terrsa 4f, Shimane ,Japan
+- [[https://event.ospn.jp/osc2023-shimane/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023shimane.pdf]]
+- togetter [[https://togetter.com/li/2247549]]
+
+## Open Source Conference 2023 Tokyo/Fall NetBSD Booth
+- 2023 Oct.21 Sat 10:00-16:00 JST (UTC+9)
+- Ota City Industrial Plaza (PiO) [[https://www.pio-ota.net/english-access/]]
+- [[https://event.ospn.jp/osc2023-fall/]]
+- [[https://ospn.connpass.com/event/295184]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyofall.pdf]]
+- togetter [[https://togetter.com/li/2240886]]
+
+## Open Source Conference 2023 Online/Fall BSD BoF
+- 2022 Sep.30 Sat 14:00-14:45 JST (UTC+9) 
+- [[https://event.ospn.jp/osc2023-online-fall/session/1098479]]
+- [[https://event.ospn.jp/osc2023-online-fall/]]
+- Youtube video [[https://youtu.be/ACcbr-JRNyk]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyofall.pdf]]
+- togetter [[https://togetter.com/li/2231931]]
+
+## Open Developers Conference 2023 NetBSD BoF
+- 2023 Aug.26 Sat 12:00-12:45 JST (UTC+9)
+- docomo R&D OPEN LAB ODAIBA [[https://docomo-openlab.jp/about/#access]]
+- [[https://event.ospn.jp/odc2023/]]
+- [[https://ospn.connpass.com/event/291437/]]
+- Youtube video [[https://youtu.be/QkVPOQZnzh8]] c2k by yamori
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/ODC2023.pdf]]
+- togetter [[https://togetter.com/li/2208216]]
+
+## Open Source Conference 2023 Online/Kyoto NetBSD BoF
+- 2023 Jul.29 Sat 14:00-14:45 JST (UTC+9) 
+- [[https://event.ospn.jp/osc2023-online-kyoto/session/992861]]
+- [[https://event.ospn.jp/osc2023-online-kyoto/]]
+- Youtube video [[https://youtu.be/TnviEtERcVw]]
+- Join meeting via ZOOM [[https://ospn.connpass.com/event/287988]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023kyoto.pdf]]
+- togetter [[https://togetter.com/li/2189221]]
+
+## Open Source Conference 2023 Kyoto NetBSD Booth
+- 2023 Jul.22 Sat 10:00-16:00 JST (UTC+9) 
+- Kyoto Research Park [[https://www.krp.co.jp/access/map.html]]
+- [[https://event.ospn.jp/osc2023-kyoto/]]
+- [[https://ospn.connpass.com/event/287987]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023kyoto.pdf]]
+- togetter [[https://togetter.com/li/2189221]]
+
+
+## Open Source Conference 2023 Hokkaido NetBSD Booth
+- 2023 Jun.24 Sat 11:00-16:00 JST (UTC+9) 
+- Sapporo Business Innovation Center [[https://www.sapporosansin.jp/access/]]
+- with [[https://www.no.bug.gr.jp/]]
+- [[https://event.ospn.jp/osc2023-do/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023hokkaido.pdf]]
+- togetter [[https://togetter.com/li/2165257]]
+
+## Open Source Conference 2023 Online/Hokkaido NetBSD BoF
+- 2023 Jun.17 Sat 15:00-15:45 JST (UTC+9) 
+- [[https://event.ospn.jp/osc2023-online-do/]]
+- [[https://event.ospn.jp/osc2023-online-do/session/908792]]
+- Youtube video [[https://youtu.be/_zgEhsywxaM]] Amiga A1200 by hamajima@
+- Join meeting via ZOOM [[https://ospn.connpass.com/event/281181/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023hokkaido.pdf]]
+- togetter [[https://togetter.com/li/2165257]]
+
+## Open Source Conference 2023 Nagoya NetBSD Booth
+- 2023 May.28 Sun 11:00-16:00 JST (UTC+9)
+- Nagoya Trade & Industry Center [[https://www.nipc.or.jp/fukiage/sub/visitor-access.html#around]]
+- with [[http://nagoya.bug.gr.jp/]]
+- [[https://event.ospn.jp/osc2023-nagoya/]]
+- [[https://ospn.connpass.com/event/278668/]] Join offline event
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023nagoya.pdf]]
+- togetter [[https://togetter.com/li/2142714]]
+
+## Open Source Conference 2023 Online/Nagoya NetBSD BoF
+- 2023 May.20 Sat 13:00-13:45 JST (UTC+9) 
+- [[https://event.ospn.jp/osc2023-online-nagoya/]]
+- [[https://event.ospn.jp/osc2023-online-nagoya/session/852896]] 
+- [[https://ospn.connpass.com/event/278665/]] Join via ZOOM 
+- Youtube video [[https://youtu.be/aqE2wy9l6Ps]] OpenBSD7.3/LUNA88K by aoyama@openbsd
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023nagoya.pdf]]
+- togetter [[https://togetter.com/li/2142714]]
+
+## Open Source Conference 2023 Tokyo/Spring NetBSD Booth
+- 2023 Apr.1 Sat 10:00-16:00 JST (UTC+9) 
+- [[https://event.ospn.jp/osc2023-spring/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyospring.pdf]]
+- togetter [[https://togetter.com/li/2112458]]
+
+## AsiaBSDCon2023
+- 2023 Mar.30 to Apr.2 
+- Tokyo University of Science, Tokyo, Japan
+- Sponsorship Application Guidelines: [[https://2023.asiabsdcon.org/sponsorship.pdf]] 
+- NetBSD Booth.
+- togetter [[https://togetter.com/li/2112458]]
+
+## Open Source Conference 2023 Online/Spring NetBSD BoF
+- 2023 Mar.11 Sat 15:00-15:45 JST (UTC+9) 
+- [[https://event.ospn.jp/osc2023-online-spring/]]
+- [[https://event.ospn.jp/osc2023-online-spring/session/764152]]
+- Youtube video archive [[https://youtu.be/WHZ8Tn9LiB4]] 
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyospring.pdf]]
+- togetter [[https://togetter.com/li/2094211]]
+
+## Open Source Conference 2023 Online/Osaka NetBSD BoF
+- 2023 Jan.28 Sat 14:00-14:45 JST (UTC+9) 
+- [[https://event.ospn.jp/osc2023-online-osaka/]]
+- [[https://event.ospn.jp/osc2023-online-osaka/session/737009]]
+- Youtube video archive [[https://youtu.be/5VRQ97MyWUA]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023osaka.pdf]]
+- togetter [[https://togetter.com/li/2060234]]

2024
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.137
retrieving revision 1.138
diff -u -r1.137 -r1.138
--- wikisrc/users/jun.mdwn	27 Nov 2023 04:06:16 -0000	1.137
+++ wikisrc/users/jun.mdwn	25 Dec 2023 05:37:49 -0000	1.138
@@ -1,23 +1,17 @@
 [[!meta  title="Jun Ebihara"]]
 
-[[jun/2020]]-[[jun/2021]]-[[jun/2022]]
+[[jun/2020]]-[[jun/2021]]-[[jun/2022]]-[[jun/2023]]
 
-# 2023
+# Monthly
 
-## Open Source Conference 2023 Fukuoka NetBSD Booth&BoF
-- 2023 Dec.9 Sat 10:00-18:00 JST (UTC+9) 
-- Fukuoka Soft Research Park [[https://www.fukuoka-srp.co.jp/]]
-- [[https://event.ospn.jp/osc2023-fukuoka/]]
-- Tour Guide [[]]
-- togetter [[]]
-
-# Nagoya *BSD Users' Group monthly meeting
+## Nagoya *BSD Users' Group monthly meeting
 - [[http://nagoya.bug.gr.jp/]]
 
 #2024
 
 ## Open Source Conference 2024 Osaka NetBSD Booth&BoF
-- 2024 Jan.27 Sat 10:00-18:00 JST (UTC+9) 
+- Booth: 2024 Jan.27 Sat 10:00-16:00 JST (UTC+9)
+- BoF:  2024 Jan.27 Sat 10:00-10:45 JST (UTC+9)
 - Osaka Sangyo Sozoukan  [[https://www.sansokan.jp/map/]]
 - [[https://event.ospn.jp/osc2024-osaka/]]
 - Tour Guide [[]]
@@ -30,145 +24,7 @@
 - Tour Guide [[]]
 - togetter [[]]
 
-# Past Events in 2023
-
-## Open Source Conference 2023 Niigata NetBSD Booth&BoF
-- 2022 Nov.12 Sun 10:00-18:00 JST (UTC+9) 
-- Niigata City Public Library [[https://www.niigatacitylib.jp/?page_id=166]]
-- [[https://event.ospn.jp/osc2023-niigata/]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023niigata.pdf]]
-- togetter [[https://togetter.com/li/2260623]]
-
-## Open Source Conference 2023 Hiroshima NetBSD Booth&BoF
-- 2022 Nov.12 Sun 10:00-18:00 JST (UTC+9) 
-- Satellite Campus Hiroshima [[https://www.pu-hiroshima.ac.jp/site/satellite/accessmap.html]]
-- [[https://event.ospn.jp/osc2023-hiroshima/]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023hiroshima.pdf]]
-- togetter [[https://togetter.com/li/2254094]]
-- [[https://speakerdeck.com/tsutsui/kof2023]]
-- [[http://www.pastel-flower.jp/~isaki/NetBSD/osc23hi/]]
-
-## Kansai Open Forum 2023
-- [[https://www.k-of.jp/]]
-- 2023 Nov.10 Fri. - Nov.11 Sat.
-- Booth and BSD BoF
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/KOF2023.pdf]]
-- togetter [[https://togetter.com/li/2254094]]
-- [[https://speakerdeck.com/tsutsui/kof2023]]
-
-## Open Source Conference 2023 Shimane NetBSD Booth
-- 2023 Oct.28 Sat 10:00-17:30 JST (UTC+9)
-- Matsue Terrsa 4f, Shimane ,Japan
-- [[https://event.ospn.jp/osc2023-shimane/]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023shimane.pdf]]
-- togetter [[https://togetter.com/li/2247549]]
-
-## Open Source Conference 2023 Tokyo/Fall NetBSD Booth
-- 2023 Oct.21 Sat 10:00-16:00 JST (UTC+9)
-- Ota City Industrial Plaza (PiO) [[https://www.pio-ota.net/english-access/]]
-- [[https://event.ospn.jp/osc2023-fall/]]
-- [[https://ospn.connpass.com/event/295184]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyofall.pdf]]
-- togetter [[https://togetter.com/li/2240886]]
-
-## Open Source Conference 2023 Online/Fall BSD BoF
-- 2022 Sep.30 Sat 14:00-14:45 JST (UTC+9) 
-- [[https://event.ospn.jp/osc2023-online-fall/session/1098479]]
-- [[https://event.ospn.jp/osc2023-online-fall/]]
-- Youtube video [[https://youtu.be/ACcbr-JRNyk]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyofall.pdf]]
-- togetter [[https://togetter.com/li/2231931]]
-
-## Open Developers Conference 2023 NetBSD BoF
-- 2023 Aug.26 Sat 12:00-12:45 JST (UTC+9)
-- docomo R&D OPEN LAB ODAIBA [[https://docomo-openlab.jp/about/#access]]
-- [[https://event.ospn.jp/odc2023/]]
-- [[https://ospn.connpass.com/event/291437/]]
-- Youtube video [[https://youtu.be/QkVPOQZnzh8]] c2k by yamori
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/ODC2023.pdf]]
-- togetter [[https://togetter.com/li/2208216]]
-
-## Open Source Conference 2023 Online/Kyoto NetBSD BoF
-- 2023 Jul.29 Sat 14:00-14:45 JST (UTC+9) 
-- [[https://event.ospn.jp/osc2023-online-kyoto/session/992861]]
-- [[https://event.ospn.jp/osc2023-online-kyoto/]]
-- Youtube video [[https://youtu.be/TnviEtERcVw]]
-- Join meeting via ZOOM [[https://ospn.connpass.com/event/287988]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023kyoto.pdf]]
-- togetter [[https://togetter.com/li/2189221]]
-
-## Open Source Conference 2023 Kyoto NetBSD Booth
-- 2023 Jul.22 Sat 10:00-16:00 JST (UTC+9) 
-- Kyoto Research Park [[https://www.krp.co.jp/access/map.html]]
-- [[https://event.ospn.jp/osc2023-kyoto/]]
-- [[https://ospn.connpass.com/event/287987]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023kyoto.pdf]]
-- togetter [[https://togetter.com/li/2189221]]
-
-
-## Open Source Conference 2023 Hokkaido NetBSD Booth
-- 2023 Jun.24 Sat 11:00-16:00 JST (UTC+9) 
-- Sapporo Business Innovation Center [[https://www.sapporosansin.jp/access/]]
-- with [[https://www.no.bug.gr.jp/]]
-- [[https://event.ospn.jp/osc2023-do/]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023hokkaido.pdf]]
-- togetter [[https://togetter.com/li/2165257]]
-
-## Open Source Conference 2023 Online/Hokkaido NetBSD BoF
-- 2023 Jun.17 Sat 15:00-15:45 JST (UTC+9) 
-- [[https://event.ospn.jp/osc2023-online-do/]]
-- [[https://event.ospn.jp/osc2023-online-do/session/908792]]
-- Youtube video [[https://youtu.be/_zgEhsywxaM]] Amiga A1200 by hamajima@
-- Join meeting via ZOOM [[https://ospn.connpass.com/event/281181/]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023hokkaido.pdf]]
-- togetter [[https://togetter.com/li/2165257]]
-
-## Open Source Conference 2023 Nagoya NetBSD Booth
-- 2023 May.28 Sun 11:00-16:00 JST (UTC+9)
-- Nagoya Trade & Industry Center [[https://www.nipc.or.jp/fukiage/sub/visitor-access.html#around]]
-- with [[http://nagoya.bug.gr.jp/]]
-- [[https://event.ospn.jp/osc2023-nagoya/]]
-- [[https://ospn.connpass.com/event/278668/]] Join offline event
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023nagoya.pdf]]
-- togetter [[https://togetter.com/li/2142714]]
-
-## Open Source Conference 2023 Online/Nagoya NetBSD BoF
-- 2023 May.20 Sat 13:00-13:45 JST (UTC+9) 
-- [[https://event.ospn.jp/osc2023-online-nagoya/]]
-- [[https://event.ospn.jp/osc2023-online-nagoya/session/852896]] 
-- [[https://ospn.connpass.com/event/278665/]] Join via ZOOM 
-- Youtube video [[https://youtu.be/aqE2wy9l6Ps]] OpenBSD7.3/LUNA88K by aoyama@openbsd
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023nagoya.pdf]]
-- togetter [[https://togetter.com/li/2142714]]
-
-## Open Source Conference 2023 Tokyo/Spring NetBSD Booth
-- 2023 Apr.1 Sat 10:00-16:00 JST (UTC+9) 
-- [[https://event.ospn.jp/osc2023-spring/]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyospring.pdf]]
-- togetter [[https://togetter.com/li/2112458]]
-
-## AsiaBSDCon2023
-- 2023 Mar.30 to Apr.2 
-- Tokyo University of Science, Tokyo, Japan
-- Sponsorship Application Guidelines: [[https://2023.asiabsdcon.org/sponsorship.pdf]] 
-- NetBSD Booth.
-- togetter [[https://togetter.com/li/2112458]]
-
-## Open Source Conference 2023 Online/Spring NetBSD BoF
-- 2023 Mar.11 Sat 15:00-15:45 JST (UTC+9) 
-- [[https://event.ospn.jp/osc2023-online-spring/]]
-- [[https://event.ospn.jp/osc2023-online-spring/session/764152]]
-- Youtube video archive [[https://youtu.be/WHZ8Tn9LiB4]] 
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyospring.pdf]]
-- togetter [[https://togetter.com/li/2094211]]
-
-## Open Source Conference 2023 Online/Osaka NetBSD BoF
-- 2023 Jan.28 Sat 14:00-14:45 JST (UTC+9) 
-- [[https://event.ospn.jp/osc2023-online-osaka/]]
-- [[https://event.ospn.jp/osc2023-online-osaka/session/737009]]
-- Youtube video archive [[https://youtu.be/5VRQ97MyWUA]]
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023osaka.pdf]]
-- togetter [[https://togetter.com/li/2060234]]
+# Past Events in 2024
 
 # Current my job mission
 - SOUM Corporation [[http://www.soum.co.jp]],TOKYO

xen howto: Update tornadovps comments
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.216
retrieving revision 1.217
diff -u -r1.216 -r1.217
--- wikisrc/ports/xen/howto.mdwn	8 Dec 2023 15:37:57 -0000	1.216
+++ wikisrc/ports/xen/howto.mdwn	8 Dec 2023 15:44:17 -0000	1.217
@@ -109,7 +109,7 @@
 a subset are available in pkgsrc:
 
 [[!table data="""
-Xen Version	|Package Name	|Xen CPU Support	|Security EOL |feature EOL | 
+Xen Version	|Package Name	|Xen CPU Support	|Security EOL |Feature EOL | 
 4.15		|xenkernel415	|x86_64			|2024-04-08   |2022-10-08  |
 4.18		|xenkernel415	|x86_64			|2026-11-16   |2025-05-16  |
 """]]
@@ -914,14 +914,17 @@
 page](http://www.panix.com/v-colo/grub.html) which describes how to
 boot NetBSD.
 
-### prgmr.com
+### tornadovps.com
 
-[prgmr.com](http://prgmr.com/) provides released versions of
-NetBSD/amd64 as installation options.  Users can use pvgrub to boot
-their own kernel, and a small FAT32 /boot is encouraged.  See the
-[prgmr.com NetBSD
-HOWTO](http://wiki.prgmr.com/mediawiki/index.php/NetBSD_as_a_DomU)
-(which is in need of updating).
+[tornadovps.com](http://tornadovps.com/) provides 9.3, 9.1 and 8.2
+(amd64) and 9.1 and 8.2 (i386) netboot installers.  Users can use
+grub2 or pvgrub to boot their own kernel (pvgrub needs a small FAT32
+/boot).  See the [tornadovps.com NetBSD
+instructions](https://tornadovps.com/).
+
+The main path for NetBSD is PV mode, but HVM modes might also work.
+
+As of 2023-12, NetBSD 10 kernels booting in PV mode crash during booting.
 
 ### Amazon
 

xen howto: typo fix
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.215
retrieving revision 1.216
diff -u -r1.215 -r1.216
--- wikisrc/ports/xen/howto.mdwn	7 Dec 2023 20:26:33 -0000	1.215
+++ wikisrc/ports/xen/howto.mdwn	8 Dec 2023 15:37:57 -0000	1.216
@@ -115,7 +115,7 @@
 """]]
 
 As of December 2023, 4.15 has been working well on NetBSD 8 through
-current and is the standard appraoch.  4.18 works well on NetBSD 10
+current and is the standard approach.  4.18 works well on NetBSD 10
 and has had some testing on NetBSD-current.  It is not clear if it
 will run well or not on NetBSD 9.  It is likely to be troubled on
 NetBSD 8 (which is expected to be no longer relevant very soon).

xen howto: Update 4.18 status
markd@ reports it runs well on netbsd-10
Members: 
	ports/xen/howto.mdwn:1.214->1.215 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.214
retrieving revision 1.215
diff -u -r1.214 -r1.215
--- wikisrc/ports/xen/howto.mdwn	7 Dec 2023 17:25:52 -0000	1.214
+++ wikisrc/ports/xen/howto.mdwn	7 Dec 2023 20:26:33 -0000	1.215
@@ -114,11 +114,11 @@
 4.18		|xenkernel415	|x86_64			|2026-11-16   |2025-05-16  |
 """]]
 
-As of December 2023, 4.18 was relatively new and 4.15 is known to work
-well.  In particular, 4.18 has only been tested on -current, is
-expected to work on netbsd-10, may be problematic on netbsd-9 and
-probably will not work on netbsd-8.  Therefore, using 4.15 is the
-standard approach.
+As of December 2023, 4.15 has been working well on NetBSD 8 through
+current and is the standard appraoch.  4.18 works well on NetBSD 10
+and has had some testing on NetBSD-current.  It is not clear if it
+will run well or not on NetBSD 9.  It is likely to be troubled on
+NetBSD 8 (which is expected to be no longer relevant very soon).
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 

xen howto: Declare 4.15 as the standard approach
There are no known reports of it working on netbsd-10, only current,
and it likely does not work on netsd-9 and netbsd-8. (per port-xen@
message)
Members: 
	ports/xen/howto.mdwn:1.213->1.214 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.213
retrieving revision 1.214
diff -u -r1.213 -r1.214
--- wikisrc/ports/xen/howto.mdwn	7 Dec 2023 12:54:50 -0000	1.213
+++ wikisrc/ports/xen/howto.mdwn	7 Dec 2023 17:25:52 -0000	1.214
@@ -115,7 +115,10 @@
 """]]
 
 As of December 2023, 4.18 was relatively new and 4.15 is known to work
-well.
+well.  In particular, 4.18 has only been tested on -current, is
+expected to work on netbsd-10, may be problematic on netbsd-9 and
+probably will not work on netbsd-8.  Therefore, using 4.15 is the
+standard approach.
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 

xen howto: Update versions
Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.212
retrieving revision 1.213
diff -u -r1.212 -r1.213
--- wikisrc/ports/xen/howto.mdwn	24 Aug 2023 23:08:39 -0000	1.212
+++ wikisrc/ports/xen/howto.mdwn	7 Dec 2023 12:54:50 -0000	1.213
@@ -104,21 +104,23 @@
 but note that both packages must be installed together and must have
 matching versions.
 
-Versions available in pkgsrc:
+Of the [versions released by
+upstream](https://xenbits.xen.org/docs/unstable/support-matrix.html),
+a subset are available in pkgsrc:
 
 [[!table data="""
-Xen Version	|Package Name	|Xen CPU Support	|EOL'ed By Upstream
-4.13		|xenkernel413	|x86_64			|YES - last update 2022-12-19
-4.15		|xenkernel415	|x86_64			|NO
+Xen Version	|Package Name	|Xen CPU Support	|Security EOL |feature EOL | 
+4.15		|xenkernel415	|x86_64			|2024-04-08   |2022-10-08  |
+4.18		|xenkernel415	|x86_64			|2026-11-16   |2025-05-16  |
 """]]
 
-4.13 is EOL and will be removed from pkgsrc soon after 2023Q3 is
-branched.  Anyone using it should immediately begin migrating to 4.15.
+As of December 2023, 4.18 was relatively new and 4.15 is known to work
+well.
 
 See also the [Xen Security Advisory page](http://xenbits.xen.org/xsa/).
 
-Older Xen had a python-based management tool called xm; this has long
-since been replaced by xl and is not discussed further.
+Extremely old Xen had a python-based management tool called xm; this
+has long since been replaced by xl and is not discussed further.
 
 ## NetBSD versions
 
@@ -144,9 +146,9 @@
 multiple CPUs if provided.  The XEN3_DOMU kernel is built
 with "options MULITPROCESSOR".
 
-Note that while Xen 4.15 is current, the kernel support is still
-called XEN3, because the hypercall interface has not changed
-significantly.
+Note that while the current version of Xen is 4.X, the kernel support
+is still called XEN3, because the hypercall interface has not changed
+significantly and because renaming it would not be useful.
 
 # Creating a NetBSD dom0
 

security/cgdroot: note obsolescence of miniroot.kmod
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- wikisrc/security/cgdroot.mdwn	24 Mar 2019 20:00:04 -0000	1.19
+++ wikisrc/security/cgdroot.mdwn	27 Nov 2023 18:40:04 -0000	1.20
@@ -1,5 +1,7 @@
 [[!meta title="Root Filesystem Encryption"]]
 
+**NOTE:** This page is outdated -- it should use the `fs cgdroot.fs` directive in [[!template id=man name="boot.cfg" section="5"]], rather than a custom-built miniroot kernel module with the ramdisk embedded.  Please update me to do that!
+
 It is possible to run NetBSD with [complete root filesystem encryption][1], thanks to the `cgdroot.kmod` kernel module. It really is a memory disk (also knows as RAM disk) that is expected to be loaded in the kernel while booting. It is named after CGD, the "cryptographic device driver", which implements encryption for storage in the NetBSD kernel.
 
 The mechanism described here still requires one unencrypted partition to boot from (typically `wd0a`). Full disk encryption would make it more difficult for an attacker to modify the unencrypted part of the disk to plant a backdoor. With only partial encryption, the original [[!template id=man name="cgdconfig" section="8"]] binary may be modified to send the passphrase away, allowing an attacker with a disk dump to recover the data.

Update 2023/2024 events
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.136
retrieving revision 1.137
diff -u -r1.136 -r1.137
--- wikisrc/users/jun.mdwn	10 Nov 2023 15:16:02 -0000	1.136
+++ wikisrc/users/jun.mdwn	27 Nov 2023 04:06:16 -0000	1.137
@@ -4,12 +4,40 @@
 
 # 2023
 
-## Kansai Open Forum 2023
+## Open Source Conference 2023 Fukuoka NetBSD Booth&BoF
+- 2023 Dec.9 Sat 10:00-18:00 JST (UTC+9) 
+- Fukuoka Soft Research Park [[https://www.fukuoka-srp.co.jp/]]
+- [[https://event.ospn.jp/osc2023-fukuoka/]]
+- Tour Guide [[]]
+- togetter [[]]
+
+# Nagoya *BSD Users' Group monthly meeting
+- [[http://nagoya.bug.gr.jp/]]
+
+#2024
+
+## Open Source Conference 2024 Osaka NetBSD Booth&BoF
+- 2024 Jan.27 Sat 10:00-18:00 JST (UTC+9) 
+- Osaka Sangyo Sozoukan  [[https://www.sansokan.jp/map/]]
+- [[https://event.ospn.jp/osc2024-osaka/]]
+- Tour Guide [[]]
+- togetter [[]]
+
+## Kansai Open Forum 2024
 - [[https://www.k-of.jp/]]
-- 2023 Nov.10 Fri. - Nov.11 Sat.
+- 2024 Nov.8 Fri. - Nov.9 Sat.
 - Booth and BSD BoF
-- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/KOF2023.pdf]]
-- togetter [[https://togetter.com/li/2254094]]
+- Tour Guide [[]]
+- togetter [[]]
+
+# Past Events in 2023
+
+## Open Source Conference 2023 Niigata NetBSD Booth&BoF
+- 2022 Nov.12 Sun 10:00-18:00 JST (UTC+9) 
+- Niigata City Public Library [[https://www.niigatacitylib.jp/?page_id=166]]
+- [[https://event.ospn.jp/osc2023-niigata/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023niigata.pdf]]
+- togetter [[https://togetter.com/li/2260623]]
 
 ## Open Source Conference 2023 Hiroshima NetBSD Booth&BoF
 - 2022 Nov.12 Sun 10:00-18:00 JST (UTC+9) 
@@ -17,11 +45,16 @@
 - [[https://event.ospn.jp/osc2023-hiroshima/]]
 - Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023hiroshima.pdf]]
 - togetter [[https://togetter.com/li/2254094]]
+- [[https://speakerdeck.com/tsutsui/kof2023]]
+- [[http://www.pastel-flower.jp/~isaki/NetBSD/osc23hi/]]
 
-# Nagoya *BSD Users' Group monthly meeting
-- [[http://nagoya.bug.gr.jp/]]
-
-# Past Events in 2023
+## Kansai Open Forum 2023
+- [[https://www.k-of.jp/]]
+- 2023 Nov.10 Fri. - Nov.11 Sat.
+- Booth and BSD BoF
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/KOF2023.pdf]]
+- togetter [[https://togetter.com/li/2254094]]
+- [[https://speakerdeck.com/tsutsui/kof2023]]
 
 ## Open Source Conference 2023 Shimane NetBSD Booth
 - 2023 Oct.28 Sat 10:00-17:30 JST (UTC+9)

Update test results, state and timeline
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.98
retrieving revision 1.99
diff -u -r1.98 -r1.99
--- wikisrc/releng/netbsd-10.mdwn	21 Oct 2023 09:12:07 -0000	1.98
+++ wikisrc/releng/netbsd-10.mdwn	11 Nov 2023 11:28:31 -0000	1.99
@@ -99,7 +99,7 @@
 
 ## Ongoing projects and unmerged branches
 
-* [Wifi renewal on hg](/Wifi_renewal_on_hg) - will not make it into mainline before the branch, but is planned to be merged into -current shortly after branching for netbsd-10
+* [Wifi renewal on hg](/Wifi_renewal_on_hg) - will not make it into mainline before the branch, but is planned to be merged into -current soon.
 * ~~[Updating drmkms to Linux 5.6](https://github.com/riastradh/netbsd-src/tree/redrm56) - has been merged to HEAD~~
 * [Removing PF](http://mail-index.netbsd.org/tech-kern/2019/04/04/msg024986.html) - will not happen before the branch
 	- pf was deprecated in 9 so it could be removed in 10.
@@ -122,9 +122,8 @@
 
 ## Current status and timeline
 
-* we seem to be close to what we realistically can get for 10.0
-* we plan switching to release candidate state in the last week of september
-* if all goes well, this could result in a 10.0 release mid october
+* 10.0 release candidate 1 is available
+* the 10.0 release is planed for the last week of november if nothing bad happens and we would need another RC
 
 ## Last netbsd-10 Test Results overview
 For all tests, see [releng's tests page](//releng.netbsd.org/test-results.html).
@@ -136,19 +135,19 @@
   <tbody>
     <tr>
         <td><a href="//www.netbsd.org/~martin/aarch64-atf-netbsd10/">aarch64</a>, real hardware</td>
-        <td>2023-09-08</td><td>3</td><td> </td>
+        <td>2023-11-03</td><td>0</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/sparc64-atf-netbsd10/">sparc64</a>, real hardware</td>
-        <td>2023-09-08</td><td>7</td><td> </td>
+        <td>2023-11-03</td><td>4</td><td> </td>
     </tr>
     <tr>
         <td><a href="//www-soc.lip6.fr/~bouyer/NetBSD-tests/xen/netbsd-10/">xen</a></td>
-        <td>2023-09-05</td> <td>8</td><td></td>
+        <td>2023-11-07</td> <td>3</td><td></td>
     </tr>
     <tr>
         <td><a href="//www.netbsd.org/~martin/evbarm-atf-netbsd10/">evbarm</a>, real hardware</td>
-        <td>2023-09-08</td><td>77</td><td></td>
+        <td>2023-11-03</td><td>75</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
     </tr>
   </tbody>
 </table>

Update KOF2023&OSC2023hiroshima
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.135
retrieving revision 1.136
diff -u -r1.135 -r1.136
--- wikisrc/users/jun.mdwn	10 Nov 2023 15:11:58 -0000	1.135
+++ wikisrc/users/jun.mdwn	10 Nov 2023 15:16:02 -0000	1.136
@@ -8,15 +8,15 @@
 - [[https://www.k-of.jp/]]
 - 2023 Nov.10 Fri. - Nov.11 Sat.
 - Booth and BSD BoF
-- Tour Guide [[]]
-- togetter [[]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/KOF2023.pdf]]
+- togetter [[https://togetter.com/li/2254094]]
 
 ## Open Source Conference 2023 Hiroshima NetBSD Booth&BoF
 - 2022 Nov.12 Sun 10:00-18:00 JST (UTC+9) 
 - Satellite Campus Hiroshima [[https://www.pu-hiroshima.ac.jp/site/satellite/accessmap.html]]
 - [[https://event.ospn.jp/osc2023-hiroshima/]]
-- Tour Guide [[]]
-- togetter [[]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023hiroshima.pdf]]
+- togetter [[https://togetter.com/li/2254094]]
 
 # Nagoya *BSD Users' Group monthly meeting
 - [[http://nagoya.bug.gr.jp/]]

move past: Open Source Conference 2023 Shimane
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.134
retrieving revision 1.135
diff -u -r1.134 -r1.135
--- wikisrc/users/jun.mdwn	23 Oct 2023 02:47:40 -0000	1.134
+++ wikisrc/users/jun.mdwn	10 Nov 2023 15:11:58 -0000	1.135
@@ -4,13 +4,6 @@
 
 # 2023
 
-## Open Source Conference 2023 Shimane NetBSD Booth
-- 2023 Oct.28 Sat 10:00-17:30 JST (UTC+9)
-- Matsue Terrsa 4f, Shimane ,Japan
-- [[https://event.ospn.jp/osc2023-shimane/]]
-- Tour Guide [[]]
-- togetter [[]]
-
 ## Kansai Open Forum 2023
 - [[https://www.k-of.jp/]]
 - 2023 Nov.10 Fri. - Nov.11 Sat.
@@ -30,6 +23,13 @@
 
 # Past Events in 2023
 
+## Open Source Conference 2023 Shimane NetBSD Booth
+- 2023 Oct.28 Sat 10:00-17:30 JST (UTC+9)
+- Matsue Terrsa 4f, Shimane ,Japan
+- [[https://event.ospn.jp/osc2023-shimane/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023shimane.pdf]]
+- togetter [[https://togetter.com/li/2247549]]
+
 ## Open Source Conference 2023 Tokyo/Fall NetBSD Booth
 - 2023 Oct.21 Sat 10:00-16:00 JST (UTC+9)
 - Ota City Industrial Plaza (PiO) [[https://www.pio-ota.net/english-access/]]

Open Source Conference 2023 Shimane
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.133
retrieving revision 1.134
diff -u -r1.133 -r1.134
--- wikisrc/users/jun.mdwn	3 Oct 2023 01:30:21 -0000	1.133
+++ wikisrc/users/jun.mdwn	23 Oct 2023 02:47:40 -0000	1.134
@@ -4,11 +4,10 @@
 
 # 2023
 
-## Open Source Conference 2023 Tokyo/Fall NetBSD Booth
-- 2023 Oct.21 Sat 10:00-16:00 JST (UTC+9)
-- Ota City Industrial Plaza (PiO) [[https://www.pio-ota.net/english-access/]]
-- [[https://event.ospn.jp/osc2023-fall/]]
-- [[https://ospn.connpass.com/event/295184]]
+## Open Source Conference 2023 Shimane NetBSD Booth
+- 2023 Oct.28 Sat 10:00-17:30 JST (UTC+9)
+- Matsue Terrsa 4f, Shimane ,Japan
+- [[https://event.ospn.jp/osc2023-shimane/]]
 - Tour Guide [[]]
 - togetter [[]]
 
@@ -31,6 +30,14 @@
 
 # Past Events in 2023
 
+## Open Source Conference 2023 Tokyo/Fall NetBSD Booth
+- 2023 Oct.21 Sat 10:00-16:00 JST (UTC+9)
+- Ota City Industrial Plaza (PiO) [[https://www.pio-ota.net/english-access/]]
+- [[https://event.ospn.jp/osc2023-fall/]]
+- [[https://ospn.connpass.com/event/295184]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyofall.pdf]]
+- togetter [[https://togetter.com/li/2240886]]
+
 ## Open Source Conference 2023 Online/Fall BSD BoF
 - 2022 Sep.30 Sat 14:00-14:45 JST (UTC+9) 
 - [[https://event.ospn.jp/osc2023-online-fall/session/1098479]]

Ring test bug fixed
Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.97
retrieving revision 1.98
diff -u -r1.97 -r1.98
--- wikisrc/releng/netbsd-10.mdwn	14 Sep 2023 10:55:15 -0000	1.97
+++ wikisrc/releng/netbsd-10.mdwn	21 Oct 2023 09:12:07 -0000	1.98
@@ -40,7 +40,7 @@
 * [[!template id=pr number=56815]]: Lenovo ThinkCentre with i915drmkms graphics fails to boot
 * [[!template id=pr number=56901]]: i915: Asynchronous wait on fence timed out (slowly dying X server)
 * [[!template id=pr number=56997]]: i915 framebuffer only shows a few dotted lines at the top
-* [[!template id=pr number=57059]]: amdgpu graphics ring test failing
+* ~~[[!template id=pr number=57059]]: amdgpu graphics ring test failing~~
 * [[!template id=pr number=57142]]: firefox-107.0.1 crashes on startup sometimes crashing 10.0_BETA along with it
 * [[!template id=pr number=57143]]: Screen rotation causes loss of acceleration on i915
 * [[!template id=pr number=57182]]: nouveau doesn't switches LVDS on

misc updates
Index: wikisrc/ports/sparc64/sparc64sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/sparc64sun4v.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/ports/sparc64/sparc64sun4v.mdwn	12 Oct 2023 17:37:27 -0000	1.9
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	12 Oct 2023 17:40:58 -0000	1.10
@@ -19,7 +19,9 @@
 ### Network
 Setup a boot environment with TFTP, DHCP and NFS as described in <https://www.netbsd.org/docs/network/netboot/>.  
 Note that the instruction might be a bit outdated, so some notes are present here: <https://mail-index.netbsd.org/netbsd-docs/2020/10/29/msg000560.html> and <https://mail-index.netbsd.org/netbsd-docs/2020/10/31/msg000561.html>.  
-The root filesystem served by the NFS server can be populated by extracting the sets from the sparc64/binary/sets directory.
+The root filesystem served by the NFS server can be populated by extracting the sets from the sparc64/binary/sets directory.  
+Issue a 'boot net:dhcp' command to boot from the network.
+
 ## On emulated hardware
 ### QEMU
 Can be used for basic verification of the kernel.  

misc updates
Index: wikisrc/ports/sparc64/sparc64sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/sparc64sun4v.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 18:44:27 -0000	1.8
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	12 Oct 2023 17:37:27 -0000	1.9
@@ -1,5 +1,5 @@
 # Goal
-Make NetBSD/sparc64 run on all sun4v-based systems.
+Make NetBSD/sparc64 run on sun4v-based systems.
 
 # Status
 Currently (as of 2023-10-10) the kernel boots fine using a single CPU (ignoring any additional available CPUs).  
@@ -17,7 +17,7 @@
 Oracle documentation for the logical domain is here: <https://docs.oracle.com/en/virtualization/oracle-vm-server-sparc/index.html>  
 OpenBSD has some notes on using the logical domain feature here: <https://undeadly.org/cgi?action=article;sid=20121214153413> and <https://flak.tedunangst.com/post/OpenBSD-on-a-Sun-T5120>
 ### Network
-Setup a boot environment with RARP, TFTP, DHCP and NFS as described in <https://www.netbsd.org/docs/network/netboot/>.  
+Setup a boot environment with TFTP, DHCP and NFS as described in <https://www.netbsd.org/docs/network/netboot/>.  
 Note that the instruction might be a bit outdated, so some notes are present here: <https://mail-index.netbsd.org/netbsd-docs/2020/10/29/msg000560.html> and <https://mail-index.netbsd.org/netbsd-docs/2020/10/31/msg000561.html>.  
 The root filesystem served by the NFS server can be populated by extracting the sets from the sparc64/binary/sets directory.
 ## On emulated hardware
@@ -25,7 +25,7 @@
 Can be used for basic verification of the kernel.  
 Information is available here: <https://wiki.qemu.org/Documentation/Platforms/SPARC> and <http://tyom.blogspot.com/search?q=niagara>.  
 Note that the 'niagara' is required machine type.  
-Use the NetBSD miniroot filesystem to replace the Solaris 10 image from the opensparc distribution.
+Use the NetBSD miniroot filesystem to replace the Solaris 10 image from the opensparc distribution <https://www.oracle.com/servers/technologies/opensparc-overview.html>.
 
 
 

add link to sun4v
Index: wikisrc/ports/sparc64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64.mdwn,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -r1.36 -r1.37
--- wikisrc/ports/sparc64.mdwn	10 Oct 2023 17:55:40 -0000	1.36
+++ wikisrc/ports/sparc64.mdwn	11 Oct 2023 18:56:37 -0000	1.37
@@ -69,7 +69,7 @@
 """
 unsupported_hardware="""
 * Systems with an UltraSPARC IV CPU (unknown; may work)
-* Systems based on the sun4v architecture (CPUs: T1, T2, T3, T4, T5, M5, M6, M7, M8, S7) (in-progress)
+* Systems based on the sun4v architecture (CPUs: T1, T2, T3, T4, T5, M5, M6, M7, M8, S7) (in-progress - see <https://wiki.netbsd.org/ports/sparc64/sparc64sun4v/>)
 * Systems with a Fujitsu SPARC64 CPU (in-progress)
 * Smart card readers
 """

provide link to sun4v
Index: wikisrc/projects/project/sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/sun4v.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/projects/project/sun4v.mdwn	27 Feb 2014 08:23:21 -0000	1.3
+++ wikisrc/projects/project/sun4v.mdwn	11 Oct 2023 18:53:55 -0000	1.4
@@ -14,7 +14,7 @@
 It would be nice to support these newer highly SMP processors from Sun.  A Linux
 port already exists, and Sun has contributed code to the FOSS community.
 
-(Some work has already been done and committed.)
+(Some work has already been done and committed - see <https://wiki.netbsd.org/ports/sparc64/sparc64sun4v/>
 
 """
 ]]

more updates
Index: wikisrc/ports/sparc64/sparc64sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/sparc64sun4v.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 18:42:15 -0000	1.7
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 18:44:27 -0000	1.8
@@ -25,6 +25,7 @@
 Can be used for basic verification of the kernel.  
 Information is available here: <https://wiki.qemu.org/Documentation/Platforms/SPARC> and <http://tyom.blogspot.com/search?q=niagara>.  
 Note that the 'niagara' is required machine type.  
+Use the NetBSD miniroot filesystem to replace the Solaris 10 image from the opensparc distribution.
 
 
 

more updates
Index: wikisrc/ports/sparc64/sparc64sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/sparc64sun4v.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 18:15:38 -0000	1.6
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 18:42:15 -0000	1.7
@@ -22,7 +22,11 @@
 The root filesystem served by the NFS server can be populated by extracting the sets from the sparc64/binary/sets directory.
 ## On emulated hardware
 ### QEMU
-TBD
+Can be used for basic verification of the kernel.  
+Information is available here: <https://wiki.qemu.org/Documentation/Platforms/SPARC> and <http://tyom.blogspot.com/search?q=niagara>.  
+Note that the 'niagara' is required machine type.  
+
+
 
 
 

misc updates
Index: wikisrc/ports/sparc64/sparc64sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/sparc64sun4v.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 17:35:43 -0000	1.5
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 18:15:38 -0000	1.6
@@ -9,7 +9,7 @@
 
 # Running
 ## On real hardware
-### CD-ROM/DVD
+### CD-ROM
 Create an install disc from the official ISO image and issue a 'boot cdrom' command from OpenBoot,
 ### Miniroot
 If the sun4v system has more than one logical domain configured, a secondary logical domain can use the 'miniroot' image as a virtual disk to boot from.  
@@ -17,7 +17,9 @@
 Oracle documentation for the logical domain is here: <https://docs.oracle.com/en/virtualization/oracle-vm-server-sparc/index.html>  
 OpenBSD has some notes on using the logical domain feature here: <https://undeadly.org/cgi?action=article;sid=20121214153413> and <https://flak.tedunangst.com/post/OpenBSD-on-a-Sun-T5120>
 ### Network
-TBD
+Setup a boot environment with RARP, TFTP, DHCP and NFS as described in <https://www.netbsd.org/docs/network/netboot/>.  
+Note that the instruction might be a bit outdated, so some notes are present here: <https://mail-index.netbsd.org/netbsd-docs/2020/10/29/msg000560.html> and <https://mail-index.netbsd.org/netbsd-docs/2020/10/31/msg000561.html>.  
+The root filesystem served by the NFS server can be populated by extracting the sets from the sparc64/binary/sets directory.
 ## On emulated hardware
 ### QEMU
 TBD

misc updates
Index: wikisrc/ports/sparc64/sparc64sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/sparc64sun4v.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 17:33:41 -0000	1.4
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 17:35:43 -0000	1.5
@@ -22,3 +22,6 @@
 ### QEMU
 TBD
 
+
+
+

misc updates
Index: wikisrc/ports/sparc64/sparc64sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/sparc64sun4v.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 17:31:14 -0000	1.3
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 17:33:41 -0000	1.4
@@ -13,7 +13,7 @@
 Create an install disc from the official ISO image and issue a 'boot cdrom' command from OpenBoot,
 ### Miniroot
 If the sun4v system has more than one logical domain configured, a secondary logical domain can use the 'miniroot' image as a virtual disk to boot from.  
-Configuration of secondary virtual domain can be done by running e.g. Solaris 11.3/11.4 or OpenBSD as the primary logical machine.  
+Configuration of secondary virtual domain can be done by running e.g. Solaris 11.3/11.4 or OpenBSD as the primary logical domain.  
 Oracle documentation for the logical domain is here: <https://docs.oracle.com/en/virtualization/oracle-vm-server-sparc/index.html>  
 OpenBSD has some notes on using the logical domain feature here: <https://undeadly.org/cgi?action=article;sid=20121214153413> and <https://flak.tedunangst.com/post/OpenBSD-on-a-Sun-T5120>
 ### Network

misc updates
Index: wikisrc/ports/sparc64/sparc64sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/sparc64sun4v.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/sparc64/sparc64sun4v.mdwn	10 Oct 2023 19:31:21 -0000	1.2
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	11 Oct 2023 17:31:14 -0000	1.3
@@ -1,5 +1,5 @@
 # Goal
-Make NetBSD/sparc64 run on all sun4v based systems.
+Make NetBSD/sparc64 run on all sun4v-based systems.
 
 # Status
 Currently (as of 2023-10-10) the kernel boots fine using a single CPU (ignoring any additional available CPUs).  
@@ -9,11 +9,13 @@
 
 # Running
 ## On real hardware
-### CDROM/DVD
-Create a install disc from the official ISO image and issue a 'boot cdrom' command from OpenBoot,
+### CD-ROM/DVD
+Create an install disc from the official ISO image and issue a 'boot cdrom' command from OpenBoot,
 ### Miniroot
-If the sun4v system has more than one logical machine configured, a secondary logical machine can use the 'miniroot' image as a virtual disk to boot from.  
-Configuration of secondary virtual machine can be done by running e.g. Solaris 11.3/11.4 or OpenBSD as the primary logical machine.
+If the sun4v system has more than one logical domain configured, a secondary logical domain can use the 'miniroot' image as a virtual disk to boot from.  
+Configuration of secondary virtual domain can be done by running e.g. Solaris 11.3/11.4 or OpenBSD as the primary logical machine.  
+Oracle documentation for the logical domain is here: <https://docs.oracle.com/en/virtualization/oracle-vm-server-sparc/index.html>  
+OpenBSD has some notes on using the logical domain feature here: <https://undeadly.org/cgi?action=article;sid=20121214153413> and <https://flak.tedunangst.com/post/OpenBSD-on-a-Sun-T5120>
 ### Network
 TBD
 ## On emulated hardware

More instructions for running
Index: wikisrc/ports/sparc64/sparc64sun4v.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/sparc64sun4v.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/ports/sparc64/sparc64sun4v.mdwn	10 Oct 2023 19:03:42 -0000	1.1
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	10 Oct 2023 19:31:21 -0000	1.2
@@ -2,8 +2,21 @@
 Make NetBSD/sparc64 run on all sun4v based systems.
 
 # Status
-Currently (as of 2023-10-10) the kernel boots fine using a single CPU (ignoring any additional available CPUs). 
-The only two systems known to boot the kernel so far are T2000 (T1 CPU) and S7-2 (S7 CPU).
-On T2000 the initial userland process (init) crashes after returning from a system call (access()) where an instruction MMU trap causes the register window to be incorrectly filled. On S7-S the intial userland process (init) runs fine and starts the installation program (sysinst), but hangs during the extraction of the sets.
+Currently (as of 2023-10-10) the kernel boots fine using a single CPU (ignoring any additional available CPUs).  
+The only two systems known to boot the kernel so far are T2000 (T1 CPU) and S7-2 (S7 CPU).  
+* On T2000 the initial userland process (init) crashes after returning from a system call (access()) where an instruction MMU trap causes the register window to be incorrectly filled.  
+* On S7-S the intial userland process (init) runs fine and starts the installation program (sysinst), but hangs during the extraction of the sets.  
 
+# Running
+## On real hardware
+### CDROM/DVD
+Create a install disc from the official ISO image and issue a 'boot cdrom' command from OpenBoot,
+### Miniroot
+If the sun4v system has more than one logical machine configured, a secondary logical machine can use the 'miniroot' image as a virtual disk to boot from.  
+Configuration of secondary virtual machine can be done by running e.g. Solaris 11.3/11.4 or OpenBSD as the primary logical machine.
+### Network
+TBD
+## On emulated hardware
+### QEMU
+TBD
 

Update sun4v
Index: wikisrc/ports/sparc64/projects.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/projects.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/ports/sparc64/projects.mdwn	10 Oct 2023 18:32:47 -0000	1.3
+++ wikisrc/ports/sparc64/projects.mdwn	10 Oct 2023 19:10:45 -0000	1.4
@@ -4,7 +4,7 @@
 
 ### Kernel
 
-* sun4v: Support for the successor to the sun4u architecture  is being worked on [[sparc64sun4v]]
+* sun4v: Support for the successor to the sun4u architecture  is being worked on ([[sparc64sun4v]])
 * Make sure registers %g6 and %g7 are free in all kernel asm code and use them for curlwp/curcpu
 * Cleanup locore.s: Locore.s needs a cleanup.
 * KGDB: The code for kgdb needs to be fixed back up.

Populate page with sun4v status
--- /dev/null	2023-10-10 19:04:02.935034811 +0000
+++ wikisrc/ports/sparc64/sparc64sun4v.mdwn	2023-10-10 19:04:14.438258611 +0000
@@ -0,0 +1,9 @@
+# Goal
+Make NetBSD/sparc64 run on all sun4v based systems.
+
+# Status
+Currently (as of 2023-10-10) the kernel boots fine using a single CPU (ignoring any additional available CPUs). 
+The only two systems known to boot the kernel so far are T2000 (T1 CPU) and S7-2 (S7 CPU).
+On T2000 the initial userland process (init) crashes after returning from a system call (access()) where an instruction MMU trap causes the register window to be incorrectly filled. On S7-S the intial userland process (init) runs fine and starts the installation program (sysinst), but hangs during the extraction of the sets.
+
+

Update sun4v information - create link to sub page
Index: wikisrc/ports/sparc64/projects.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64/projects.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/ports/sparc64/projects.mdwn	1 Jul 2015 09:31:10 -0000	1.2
+++ wikisrc/ports/sparc64/projects.mdwn	10 Oct 2023 18:32:47 -0000	1.3
@@ -4,7 +4,7 @@
 
 ### Kernel
 
-* Sun4v: Support for T1000 - T5000 is beeing worked on
+* sun4v: Support for the successor to the sun4u architecture  is being worked on [[sparc64sun4v]]
 * Make sure registers %g6 and %g7 are free in all kernel asm code and use them for curlwp/curcpu
 * Cleanup locore.s: Locore.s needs a cleanup.
 * KGDB: The code for kgdb needs to be fixed back up.

Index: wikisrc/ports/sparc64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/sparc64.mdwn,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- wikisrc/ports/sparc64.mdwn	8 Nov 2022 22:35:56 -0000	1.35
+++ wikisrc/ports/sparc64.mdwn	10 Oct 2023 17:55:40 -0000	1.36
@@ -69,7 +69,7 @@
 """
 unsupported_hardware="""
 * Systems with an UltraSPARC IV CPU (unknown; may work)
-* Systems with an UltraSPARC T1-T5 CPU (in-progress)
+* Systems based on the sun4v architecture (CPUs: T1, T2, T3, T4, T5, M5, M6, M7, M8, S7) (in-progress)
 * Systems with a Fujitsu SPARC64 CPU (in-progress)
 * Smart card readers
 """

tutorials/kerberos_realm: Fix typo in example.
Need an @ in a principal.
Members: 
	tutorials/kerberos_realm.mdwn:1.4->1.5 

Index: wikisrc/tutorials/kerberos_realm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/kerberos_realm.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/kerberos_realm.mdwn	23 Aug 2023 12:46:41 -0000	1.4
+++ wikisrc/tutorials/kerberos_realm.mdwn	8 Oct 2023 18:55:59 -0000	1.5
@@ -77,7 +77,7 @@
        jruser/admin@EXAMPLE.COM's Password: 
        Verifying - jruser/admin@EXAMPLE.COM's Password: 
 
-   The admin principal `jruser/adminEXAMPLE.COM` has no intrinsic
+   The admin principal `jruser/admin@EXAMPLE.COM` has no intrinsic
    connection to `jruser@EXAMPLE.COM` but by convention is chosen to be
    authorized like a [[!template id=man name="su" section="1"]]-style
    superuser version of `jruser` for administrative tasks with the help

Add Video: Open Source Conference 2023 Online/Fall BSD BoF, move past
Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.132
retrieving revision 1.133
diff -u -r1.132 -r1.133
--- wikisrc/users/jun.mdwn	4 Sep 2023 05:24:26 -0000	1.132
+++ wikisrc/users/jun.mdwn	3 Oct 2023 01:30:21 -0000	1.133
@@ -4,15 +4,6 @@
 
 # 2023
 
-## Open Source Conference 2023 Online/Fall BSD BoF
-- 2022 Sep.30 Sat 14:00-14:45 JST (UTC+9) 
-- [[https://event.ospn.jp/osc2023-online-fall/session/1098479]]
-- [[https://event.ospn.jp/osc2023-online-fall/]]
-- Join meeting via Youtube video [[https://www.youtube.com/c/OSPNjp]]
-- Join meeting via ZOOM [[https://ospn.connpass.com/event/295182]]
-- Tour Guide [[]]
-- togetter [[]]
-
 ## Open Source Conference 2023 Tokyo/Fall NetBSD Booth
 - 2023 Oct.21 Sat 10:00-16:00 JST (UTC+9)
 - Ota City Industrial Plaza (PiO) [[https://www.pio-ota.net/english-access/]]
@@ -40,6 +31,14 @@
 
 # Past Events in 2023
 
+## Open Source Conference 2023 Online/Fall BSD BoF
+- 2022 Sep.30 Sat 14:00-14:45 JST (UTC+9) 
+- [[https://event.ospn.jp/osc2023-online-fall/session/1098479]]
+- [[https://event.ospn.jp/osc2023-online-fall/]]
+- Youtube video [[https://youtu.be/ACcbr-JRNyk]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2023tokyofall.pdf]]
+- togetter [[https://togetter.com/li/2231931]]
+
 ## Open Developers Conference 2023 NetBSD BoF
 - 2023 Aug.26 Sat 12:00-12:45 JST (UTC+9)
 - docomo R&D OPEN LAB ODAIBA [[https://docomo-openlab.jp/about/#access]]

project/rfc5927: Link to IPv4 countermeasure implementation commit.
Index: wikisrc/projects/project/rfc5927.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/rfc5927.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/rfc5927.mdwn	1 Oct 2023 13:42:41 -0000	1.1
+++ wikisrc/projects/project/rfc5927.mdwn	1 Oct 2023 14:25:00 -0000	1.2
@@ -18,6 +18,9 @@
 
 This project will close
  [PR kern/35392](https://gnats.netbsd.org/35392).
+
+The IPv4 countermeasures were previously implemented here:
+<https://mail-index.NetBSD.org/source-changes/2005/07/19/msg166102.html>
 """
 ]]
 

project/rfc5927: new project to close PR kern/35392
--- /dev/null	2023-10-01 13:40:01.389936106 +0000
+++ wikisrc/projects/project/rfc5927.mdwn	2023-10-01 13:44:02.555399928 +0000
@@ -0,0 +1,24 @@
+[[!template id=project
+
+title="RFC 5927 countermeasures against IPv6 ICMP attacks on TCP"
+
+contact="""
+[tech-kern](mailto:tech-net@NetBSD.org)
+"""
+
+category="kernel"
+difficulty="medium"
+duration="1 month"
+
+description="""
+Assess and, if appropriate, implement RFC 5927 countermeasures against
+ IPv6 ICMP attacks on TCP.
+Write ATF tests for any countermeasures implemented, as well as ATF
+ tests for the existing IPv4 countermeasures.
+
+This project will close
+ [PR kern/35392](https://gnats.netbsd.org/35392).
+"""
+]]
+
+[[!tag gsoc]]

Fix "optionnal" typo
Index: wikisrc/tutorials/pkgsrc/pbulk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/pkgsrc/pbulk.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/tutorials/pkgsrc/pbulk.mdwn	10 Jun 2020 14:30:19 -0000	1.17
+++ wikisrc/tutorials/pkgsrc/pbulk.mdwn	29 Sep 2023 10:44:58 -0000	1.18
@@ -34,7 +34,7 @@
 Fortunately, a tool called *mksandbox* will simplify this process. *mksandbox*
 is located in the *pkgtools/mksandbox* package, and it is called like this:
 
-	# mksandbox [optionnal flags] /path/to/sandbox
+	# mksandbox [optional flags] /path/to/sandbox
 
 For example, to create a sandbox in */home/bulk* without the X11 system, run: