Index: wikisrc/users/wiz/pkgsrc-migration.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/wiz/pkgsrc-migration.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/users/wiz/pkgsrc-migration.mdwn	22 Apr 2024 07:15:15 -0000	1.7
+++ wikisrc/users/wiz/pkgsrc-migration.mdwn	24 Apr 2024 12:53:40 -0000	1.8
@@ -5,26 +5,27 @@
 Repositories
 ===
 
-Either use the existing conversion, or make a new one using
-`cvs2fossil` is preferred, packaged in wip/cvs2fossil and then convert
-via something like wip/cvs2hg, but for git.
+Either use the existing conversion, or make a new one using `wip/cvs2git`.
+
+(DONE in this section refers to the test repository.)
 
 - pkgsrc
   - conversion exists, but joerg wants to do a cleaned up version
-  - update branch-cutting instructions
-  - update releng instructions
-  - `doc/CHANGES-*`: add a `.gitattributes` file in `doc` with
+    - asked joerg if he's still interested in doing that
+  - DONE `doc/CHANGES-*`: add a `.gitattributes` file in `doc` with
 
     CHANGES-* merge=union
 
+  - DONE authormap (mapping CVS Unix users to name and email)
+  - DONE authormap needs to be applied
+  - DONE rename trunk to main
+
 
 git server
 ===
 
 - software
   - use git: ssh + git like for wip
-  - authormap exists (mapping CVS Unix users to name and email) but needs updating
-  - authormap needs to be applied
 - new hardware?
   - no; use cvs and anoncvs machines
 - new DNS entry
@@ -36,15 +37,17 @@
 
 - DONE email notifications: use hook script from pkgsrc-wip
 - DONE linear history: use hook script from pkgsrc-wip
-- TODO warning about merge conflict in commits
-- TODO warning about work directories included in commits
-- TODO emails to GNATS when commits include magic pattern relating to a PR
+- warning about merge conflict in commits
+- warning about work directories included in commits
+- emails to GNATS when commits include magic pattern relating to a PR
 - DONE `pkg_add p5-MIME-Lite` for notifications
 - DONE branch support
 
 Documentation
 ===
-- TODO pkgsrc-specific documentation for developers and git
+- pkgsrc-specific documentation for developers and git
+- update branch-cutting instructions
+- update releng instructions
 
 Updating Repository Contents & Deployment
 ===
@@ -57,13 +60,12 @@
 - developer activity script for admins/membership-exec needs to be adapted
 - update bulk build machines to get their sources from git
 
-Switch from CVS to git
+Switching from CVS to git
 ===
 - make git repository available to all developers
 - make pkgsrc CVS read-only
 - github
   - after final conversion happens, either force-push or make a new repository and deprecate the old one
-- rename trunk to main
 
 Post-Conversion
 ===

Index: wikisrc/users/wiz/pkgsrc-migration.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/wiz/pkgsrc-migration.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/users/wiz/pkgsrc-migration.mdwn	21 Apr 2024 16:23:38 -0000	1.6
+++ wikisrc/users/wiz/pkgsrc-migration.mdwn	22 Apr 2024 07:15:15 -0000	1.7
@@ -39,7 +39,8 @@
 - TODO warning about merge conflict in commits
 - TODO warning about work directories included in commits
 - TODO emails to GNATS when commits include magic pattern relating to a PR
-- TODO `pkg_add p5-MIME-Lite` for notifications
+- DONE `pkg_add p5-MIME-Lite` for notifications
+- DONE branch support
 
 Documentation
 ===

Index: wikisrc/users/wiz/pkgsrc-migration.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/wiz/pkgsrc-migration.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/wiz/pkgsrc-migration.mdwn	20 Apr 2024 15:22:20 -0000	1.5
+++ wikisrc/users/wiz/pkgsrc-migration.mdwn	21 Apr 2024 16:23:38 -0000	1.6
@@ -13,7 +13,7 @@
   - conversion exists, but joerg wants to do a cleaned up version
   - update branch-cutting instructions
   - update releng instructions
-  - DONE `doc/CHANGES-*`: add a `.gitattributes` file in `doc` with
+  - `doc/CHANGES-*`: add a `.gitattributes` file in `doc` with
 
     CHANGES-* merge=union
 
@@ -39,6 +39,7 @@
 - TODO warning about merge conflict in commits
 - TODO warning about work directories included in commits
 - TODO emails to GNATS when commits include magic pattern relating to a PR
+- TODO `pkg_add p5-MIME-Lite` for notifications
 
 Documentation
 ===

Index: wikisrc/users/wiz/pkgsrc-migration.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/wiz/pkgsrc-migration.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/wiz/pkgsrc-migration.mdwn	20 Apr 2024 15:11:47 -0000	1.4
+++ wikisrc/users/wiz/pkgsrc-migration.mdwn	20 Apr 2024 15:22:20 -0000	1.5
@@ -61,6 +61,7 @@
 - make pkgsrc CVS read-only
 - github
   - after final conversion happens, either force-push or make a new repository and deprecate the old one
+- rename trunk to main
 
 Post-Conversion
 ===

Index: wikisrc/users/wiz/pkgsrc-migration.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/wiz/pkgsrc-migration.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/wiz/pkgsrc-migration.mdwn	17 Apr 2024 10:24:05 -0000	1.3
+++ wikisrc/users/wiz/pkgsrc-migration.mdwn	20 Apr 2024 15:11:47 -0000	1.4
@@ -13,7 +13,10 @@
   - conversion exists, but joerg wants to do a cleaned up version
   - update branch-cutting instructions
   - update releng instructions
-  - expect lots of merge problems in doc/CHANGES* - write a [[custom merge tool|https://gregmicek.com/software-coding/2020/01/13/how-to-write-a-custom-git-merge-driver/]] [[second link|https://blog.beardhatcode.be/2018/03/your-own-git-mergetool.html]]
+  - DONE `doc/CHANGES-*`: add a `.gitattributes` file in `doc` with
+
+    CHANGES-* merge=union
+
 
 git server
 ===
@@ -21,6 +24,7 @@
 - software
   - use git: ssh + git like for wip
   - authormap exists (mapping CVS Unix users to name and email) but needs updating
+  - authormap needs to be applied
 - new hardware?
   - no; use cvs and anoncvs machines
 - new DNS entry
@@ -49,6 +53,7 @@
   - all the pkgsrc automation (requires an unpacked updated tree of the right branch, doesn't care how it came into being)
   - backups of the repo(s)
 - developer activity script for admins/membership-exec needs to be adapted
+- update bulk build machines to get their sources from git
 
 Switch from CVS to git
 ===

Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.110
retrieving revision 1.111
diff -u -r1.110 -r1.111
--- wikisrc/ports/evbarm.mdwn	30 Mar 2024 19:27:00 -0000	1.110
+++ wikisrc/ports/evbarm.mdwn	19 Apr 2024 08:55:10 -0000	1.111
@@ -5,9 +5,9 @@
 port_var2="earmv7hf"
 port_var3="earmv7hfeb"
 port_var4="aarch64"
-port_var_install_notes="evbarm-earm"
+port_var_install_notes="evbarm-earmv5"
 iso_image="true"
-pkg_rel="9.0"
+pkg_rel="10.0"
 cur_rel="10.0"
 future_rel="11.0"
 changes_cur="10.0"
@@ -66,6 +66,11 @@
 [32-bit](https://github.com/NetBSD/src/blob/netbsd-9/sys/arch/evbarm/conf/GENERIC#L18) and
 [64-bit](https://github.com/NetBSD/src/blob/netbsd-9/sys/arch/evbarm/conf/GENERIC64#L20) device trees.
 
+### Bootable Install Images
+
+We provide [ready-to-install / boot images](https://armbsd.org)
+for many of the supported boards.
+
 ### QEMU
 
 See the [[NetBSD/evbarm under QEMU|qemu_arm]] page for instructions on how to get started with QEMU.

Index: wikisrc/users/wiz/pkgsrc-migration.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/wiz/pkgsrc-migration.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/wiz/pkgsrc-migration.mdwn	16 Apr 2024 22:04:29 -0000	1.2
+++ wikisrc/users/wiz/pkgsrc-migration.mdwn	17 Apr 2024 10:24:05 -0000	1.3
@@ -27,6 +27,15 @@
 - public access:
   - provide [[read-only git|https://github.com/netbsd/]] that's not on github
 
+git server hooks
+===
+
+- DONE email notifications: use hook script from pkgsrc-wip
+- DONE linear history: use hook script from pkgsrc-wip
+- TODO warning about merge conflict in commits
+- TODO warning about work directories included in commits
+- TODO emails to GNATS when commits include magic pattern relating to a PR
+
 Documentation
 ===
 - TODO pkgsrc-specific documentation for developers and git

Index: wikisrc/users/wiz/pkgsrc-migration.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/wiz/pkgsrc-migration.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/wiz/pkgsrc-migration.mdwn	16 Apr 2024 22:02:07 -0000	1.1
+++ wikisrc/users/wiz/pkgsrc-migration.mdwn	16 Apr 2024 22:04:29 -0000	1.2
@@ -13,7 +13,7 @@
   - conversion exists, but joerg wants to do a cleaned up version
   - update branch-cutting instructions
   - update releng instructions
-  - expect lots of merge problems in doc/CHANGES* - write a [[custom merge tool|https://gregmicek.com/software-coding/2020/01/13/how-to-write-a-custom-git-merge-driver/]]
+  - expect lots of merge problems in doc/CHANGES* - write a [[custom merge tool|https://gregmicek.com/software-coding/2020/01/13/how-to-write-a-custom-git-merge-driver/]] [[second link|https://blog.beardhatcode.be/2018/03/your-own-git-mergetool.html]]
 
 git server
 ===

--- /dev/null	2024-04-16 22:02:02.030160082 +0000
+++ wikisrc/users/wiz/pkgsrc-migration.mdwn	2024-04-16 22:02:47.339058587 +0000
@@ -0,0 +1,58 @@
+This is the list of open issues for the migration of pkgsrc to git.
+
+There are at least the following topics:
+
+Repositories
+===
+
+Either use the existing conversion, or make a new one using
+`cvs2fossil` is preferred, packaged in wip/cvs2fossil and then convert
+via something like wip/cvs2hg, but for git.
+
+- pkgsrc
+  - conversion exists, but joerg wants to do a cleaned up version
+  - update branch-cutting instructions
+  - update releng instructions
+  - expect lots of merge problems in doc/CHANGES* - write a [[custom merge tool|https://gregmicek.com/software-coding/2020/01/13/how-to-write-a-custom-git-merge-driver/]]
+
+git server
+===
+
+- software
+  - use git: ssh + git like for wip
+  - authormap exists (mapping CVS Unix users to name and email) but needs updating
+- new hardware?
+  - no; use cvs and anoncvs machines
+- new DNS entry
+- public access:
+  - provide [[read-only git|https://github.com/netbsd/]] that's not on github
+
+Documentation
+===
+- TODO pkgsrc-specific documentation for developers and git
+
+Updating Repository Contents & Deployment
+===
+- Daily/weekly jobs:
+  - daily publishing jobs for tar balls
+    - with .git or without? or both?
+  - updated extracted sources? where?
+  - all the pkgsrc automation (requires an unpacked updated tree of the right branch, doesn't care how it came into being)
+  - backups of the repo(s)
+- developer activity script for admins/membership-exec needs to be adapted
+
+Switch from CVS to git
+===
+- make git repository available to all developers
+- make pkgsrc CVS read-only
+- github
+  - after final conversion happens, either force-push or make a new repository and deprecate the old one
+
+Post-Conversion
+===
+Cleanups after conversions are final (these can only be done once the
+CVS-to-git step is finalized, because they are manual work and would
+get lost otherwise)
+
+- nothing known right now?
+- turn off CVS/anoncvs server

--- /dev/null	2024-04-03 20:20:02.801975502 +0000
+++ wikisrc/tag/gsoc90h.mdwn	2024-04-03 20:20:54.931339339 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged gsoc90h"]]
+
+[[!inline pages="tagged(gsoc90h)" actions="no" archive="yes"
+feedshow=10]]

Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- wikisrc/ports.mdwn	6 Aug 2022 12:18:49 -0000	1.29
+++ wikisrc/ports.mdwn	30 Mar 2024 19:26:59 -0000	1.30
@@ -20,15 +20,15 @@
 
 [[!table data="""
 Port		|CPU		|Machines						|Latest Release
-[[aarch64]]	|aarch64	|64-bit ARM CPUs					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[evbarm]]	|arm		|ARM evaluation boards					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[evbmips]]	|mips		|MIPS-based evaluation boards				|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[evbppc]]	|powerpc	|PowerPC-based evaluation boards			|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[hpcarm]]	|arm		|StrongARM based Windows CE PDA machines		|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[i386]]	|i386		|32-bit x86-family generic machines ("PC clones")	|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[sparc64]]	|sparc		|Sun UltraSPARC (64-bit)				|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[xen]]		|i386, x86_64	|Xen Virtual Machine Monitor				|[9.3](http://www.netbsd.org/releases/formal-9/)
+[[aarch64]]	|aarch64	|64-bit ARM CPUs					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[evbarm]]	|arm		|ARM evaluation boards					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[evbmips]]	|mips		|MIPS-based evaluation boards				|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[evbppc]]	|powerpc	|PowerPC-based evaluation boards			|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[hpcarm]]	|arm		|StrongARM based Windows CE PDA machines		|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[i386]]	|i386		|32-bit x86-family generic machines ("PC clones")	|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[sparc64]]	|sparc		|Sun UltraSPARC (64-bit)				|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[xen]]		|i386, x86_64	|Xen Virtual Machine Monitor				|[10.0](http://www.netbsd.org/releases/formal-9/)
 """]]
 
 
@@ -46,55 +46,55 @@
 [[!table data="""
 Port		|CPU		|Machines								|Latest Release
 [[acorn32]]	|arm		|Acorn RiscPC/A7000/NC and compatibles					|[8.1](http://www.netbsd.org/releases/formal-8/)
-[[algor]]	|mips		|Algorithmics MIPS evaluation boards					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[alpha]]	|alpha		|Digital Alpha (64-bit)							|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[amiga]]	|m68k		|Commodore Amiga, MacroSystem DraCo					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[amigappc]]	|powerpc	|PowerPC-based Amiga boards						|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[arc]]		|mips		|Machines following the Advanced RISC Computing spec			|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[atari]]	|m68k		|Atari TT030, Falcon, Hades						|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[bebox]]	|powerpc	|Be Inc's BeBox								|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[cats]]	|arm		|Chalice Technology's Strong Arm evaluation board			|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[cesfic]]	|m68k		|CES's FIC8234 VME processor board					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[cobalt]]	|mips		|Cobalt Networks' Microservers						|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[dreamcast]]	|[[sh3]]	|Sega Dreamcast game console						|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[epoc32]]	|arm		|32bit PSION EPOC PDA							|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[emips]]	|mips		|Machines based on "Extensible MIPS"					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[evbsh3]]	|[[sh3]]	|Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs	|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[ews4800mips]]	|mips		|NEC's MIPS based EWS4800 workstations					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[hp300]]	|m68k		|Hewlett-Packard 9000/300 and 400 series				|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[hppa]]	|hppa		|Hewlett-Packard 9000/700 series					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[hpcmips]]	|mips		|MIPS based Windows CE PDA machines					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[hpcsh]]	|[[sh3]]	|Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines		|[9.3](http://www.netbsd.org/releases/formal-9/)
+[[algor]]	|mips		|Algorithmics MIPS evaluation boards					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[alpha]]	|alpha		|Digital Alpha (64-bit)							|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[amiga]]	|m68k		|Commodore Amiga, MacroSystem DraCo					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[amigappc]]	|powerpc	|PowerPC-based Amiga boards						|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[arc]]		|mips		|Machines following the Advanced RISC Computing spec			|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[atari]]	|m68k		|Atari TT030, Falcon, Hades						|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[bebox]]	|powerpc	|Be Inc's BeBox								|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[cats]]	|arm		|Chalice Technology's Strong Arm evaluation board			|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[cesfic]]	|m68k		|CES's FIC8234 VME processor board					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[cobalt]]	|mips		|Cobalt Networks' Microservers						|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[dreamcast]]	|[[sh3]]	|Sega Dreamcast game console						|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[epoc32]]	|arm		|32bit PSION EPOC PDA							|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[emips]]	|mips		|Machines based on "Extensible MIPS"					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[evbsh3]]	|[[sh3]]	|Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs	|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[ews4800mips]]	|mips		|NEC's MIPS based EWS4800 workstations					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[hp300]]	|m68k		|Hewlett-Packard 9000/300 and 400 series				|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[hppa]]	|hppa		|Hewlett-Packard 9000/700 series					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[hpcmips]]	|mips		|MIPS based Windows CE PDA machines					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[hpcsh]]	|[[sh3]]	|Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines		|[10.0](http://www.netbsd.org/releases/formal-9/)
 [[ia64]]	|itanium	|Itanium family of processors						|none
-[[ibmnws]]	|powerpc	|IBM Network Station Series 1000					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[iyonix]]	|arm		|Iyonix ARM pc								|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[landisk]]	|[[sh3]]	|SH4 based NAS appliances by I-O DATA					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[luna68k]]	|m68k		|OMRON Tateisi Electronics' LUNA series					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[mac68k]]	|m68k		|Apple Macintosh							|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[macppc]]	|powerpc	|Apple Power Macintosh and clones					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[mipsco]]	|mips		|Mips family of workstations and servers				|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[mmeye]]	|[[sh3]]	|Brains' mmEye Multi Media Server					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[mvme68k]]	|m68k		|Motorola MVME 68k SBCs							|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[mvmeppc]]	|powerpc	|Motorola MVME PowerPC SBCs						|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[netwinder]]	|arm		|StrongARM based NetWinder machines					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[news68k]]	|m68k		|Sony's m68k based "NET WORK STATION" series				|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[newsmips]]	|mips		|Sony's MIPS based "NET WORK STATION" series				|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[next68k]]	|m68k		|NeXT 68k 'black' hardware						|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[ofppc]]	|powerpc	|Generic OpenFirmware compliant PowerPC machines			|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[pmax]]	|mips		|Digital MIPS-based DECstations and DECsystems				|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[prep]]	|powerpc	|PReP (PowerPC Reference Platform) and CHRP machines			|[9.3](http://www.netbsd.org/releases/formal-9/)
+[[ibmnws]]	|powerpc	|IBM Network Station Series 1000					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[iyonix]]	|arm		|Iyonix ARM pc								|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[landisk]]	|[[sh3]]	|SH4 based NAS appliances by I-O DATA					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[luna68k]]	|m68k		|OMRON Tateisi Electronics' LUNA series					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[mac68k]]	|m68k		|Apple Macintosh							|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[macppc]]	|powerpc	|Apple Power Macintosh and clones					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[mipsco]]	|mips		|Mips family of workstations and servers				|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[mmeye]]	|[[sh3]]	|Brains' mmEye Multi Media Server					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[mvme68k]]	|m68k		|Motorola MVME 68k SBCs							|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[mvmeppc]]	|powerpc	|Motorola MVME PowerPC SBCs						|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[netwinder]]	|arm		|StrongARM based NetWinder machines					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[news68k]]	|m68k		|Sony's m68k based "NET WORK STATION" series				|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[newsmips]]	|mips		|Sony's MIPS based "NET WORK STATION" series				|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[next68k]]	|m68k		|NeXT 68k 'black' hardware						|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[ofppc]]	|powerpc	|Generic OpenFirmware compliant PowerPC machines			|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[pmax]]	|mips		|Digital MIPS-based DECstations and DECsystems				|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[prep]]	|powerpc	|PReP (PowerPC Reference Platform) and CHRP machines			|[10.0](http://www.netbsd.org/releases/formal-9/)
 [[riscv]]	|riscv		|RISC-V									|none
-[[rs6000]]	|powerpc	|MCA-based IBM RS/6000 workstations					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[sandpoint]]	|powerpc	|Motorola Sandpoint reference platform					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[sbmips]]	|mips		|Broadcom SiByte evaluation boards					|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[sgimips]]	|mips		|Silicon Graphics' MIPS-based workstations				|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[shark]]	|arm		|Digital DNARD ("shark")						|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[sparc]]	|sparc		|Sun SPARC (32-bit)							|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[sun2]]	|m68k		|Sun 2									|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[sun3]]	|m68k		|Sun 3 and 3x								|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[vax]]		|vax		|Digital VAX								|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[x68k]]	|m68k		|Sharp X680x0 series							|[9.3](http://www.netbsd.org/releases/formal-9/)
-[[zaurus]]	|arm		|Sharp C7x0/C860/C1000/C3x00 series PDA					|[9.3](http://www.netbsd.org/releases/formal-9/)
+[[rs6000]]	|powerpc	|MCA-based IBM RS/6000 workstations					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[sandpoint]]	|powerpc	|Motorola Sandpoint reference platform					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[sbmips]]	|mips		|Broadcom SiByte evaluation boards					|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[sgimips]]	|mips		|Silicon Graphics' MIPS-based workstations				|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[shark]]	|arm		|Digital DNARD ("shark")						|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[sparc]]	|sparc		|Sun SPARC (32-bit)							|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[sun2]]	|m68k		|Sun 2									|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[sun3]]	|m68k		|Sun 3 and 3x								|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[vax]]		|vax		|Digital VAX								|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[x68k]]	|m68k		|Sharp X680x0 series							|[10.0](http://www.netbsd.org/releases/formal-9/)
+[[zaurus]]	|arm		|Sharp C7x0/C860/C1000/C3x00 series PDA					|[10.0](http://www.netbsd.org/releases/formal-9/)
 """]]
 
 
Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- wikisrc/releng.mdwn	15 May 2023 20:46:10 -0000	1.52
+++ wikisrc/releng.mdwn	30 Mar 2024 19:26:59 -0000	1.53
@@ -5,23 +5,26 @@
 This page contains various information about NetBSD Release Engineering, including status information about various branches, pointers to release engineering procedures and other documentation, and the status of various branches.
 
 ## Next Major Release
+The next major release will be NetBSD 11.0 (not branched yet)
 
-The next major release will be NetBSD 10.0 (no date for release set)
-
-* [[Pre release task list for NetBSD 10.0|netbsd-10]]
-* [Current pull-up queue for the netbsd-10 branch](http://releng.netbsd.org/cgi-bin/req-10.cgi)
 
 ## Active Major Releases
 
+### NetBSD 10.x
+
+* Next minor release: NetBSD 10.1 (no schedule)
+  + CVS branch tag: <code>netbsd-10</code>
+* [Current pull-up queue for the netbsd-10 branch](http://releng.netbsd.org/cgi-bin/req-10.cgi)
+
 ### NetBSD 9.x
 
-* Next minor release: NetBSD 9.4 (no schedule)
+* Next minor release: NetBSD 9.4 (scheduled for mid Apil 2024)
   + CVS branch tag: <code>netbsd-9</code>
 * [Current pull-up queue for the netbsd-9 branch](http://releng.netbsd.org/cgi-bin/req-9.cgi)
 
 ### NetBSD 8.x
 
-* Next minor release: NetBSD 8.3 (no schedule, will happen before the 10.0 release)
+* Next minor release: NetBSD 8.3 (scheduled for end of April 2024, which also is end of support for this branch)
   + CVS branch tag: <code>netbsd-8</code>
 * [Current pull-up queue for the netbsd-8 branch](http://releng.netbsd.org/cgi-bin/req-8.cgi)
 
Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/ports/aarch64.mdwn	8 Nov 2022 22:35:55 -0000	1.16
+++ wikisrc/ports/aarch64.mdwn	30 Mar 2024 19:27:00 -0000	1.17
@@ -3,10 +3,10 @@
 changes_port="evbarm64"
 port_alt="arm"
 iso_image="true"
-future_rel="10.0"
-changes_future="10.0"
-cur_rel="9.3"
-changes_cur="9.0"
+future_rel="11.0"
+changes_future="11.0"
+cur_rel="10.0"
+changes_cur="10.0"
 pkg_rel="9.0"
 about="""
 NetBSD/aarch64 is a port to Arm's 64-bit CPUs and other compatible

(Diff truncated)

Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.110
retrieving revision 1.111
diff -u -r1.110 -r1.111
--- wikisrc/releng/netbsd-10.mdwn	26 Mar 2024 18:24:34 -0000	1.110
+++ wikisrc/releng/netbsd-10.mdwn	30 Mar 2024 15:54:29 -0000	1.111
@@ -2,16 +2,14 @@
 
 ## Hard Release Blockers
 
-* __NONE__
+* __NONE__, 10.0 has been released.
 
 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 6](//www.netbsd.org/releases/formal-10/NetBSD-10.0.html) is available.
-* a few minor issues in that RC have been fixed already
-* The final 10.0 release is planned in the next few days (waiting for a few more test results)
+* The netbsd-10 branch is open for pullups, there is no timeline for the 10.1 release yet.
 
 
 ## Showstopper bugs and PRs

Index: wikisrc/releng/netbsd-10.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng/netbsd-10.mdwn,v
retrieving revision 1.109
retrieving revision 1.110
diff -u -r1.109 -r1.110
--- wikisrc/releng/netbsd-10.mdwn	13 Mar 2024 19:20:06 -0000	1.109
+++ wikisrc/releng/netbsd-10.mdwn	26 Mar 2024 18:24:34 -0000	1.110
@@ -10,7 +10,8 @@
 ## Current status and timeline
 
 * [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
+* a few minor issues in that RC have been fixed already
+* The final 10.0 release is planned in the next few days (waiting for a few more test results)
 
 
 ## 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-03-12</td><td>1</td><td> </td>
+        <td>2024-03-25</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-03-13</td><td>5</td><td> </td>
+        <td>2024-03-25</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-03-06</td> <td>4</td><td></td>
+        <td>2024-03-22</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-03-12</td><td>80</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
+        <td>2024-03-25</td><td>76</td><td><small>(similar to HEAD numbers, mostly caused by softfloat and specific evbarm issues)</small></td>
     </tr>
   </tbody>
 </table>

Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -r1.32 -r1.33
--- wikisrc/templates/port.mdwn	23 Mar 2024 18:33:22 -0000	1.32
+++ wikisrc/templates/port.mdwn	23 Mar 2024 22:24:16 -0000	1.33
@@ -1,5 +1,4 @@
 [[!templatebody <<ENDBODY
-<TMPL_IF NAME="port">
 [[!meta title="NetBSD/<TMPL_VAR port>"]]
 
 # <TMPL_IF thumbnail><img src=<TMPL_VAR thumbnail> alt="<TMPL_VAR port> thumbnail image"/></TMPL_IF>

Index: wikisrc/templates/project.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/project.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/templates/project.mdwn	23 Mar 2024 18:33:22 -0000	1.7
+++ wikisrc/templates/project.mdwn	23 Mar 2024 18:42:05 -0000	1.8
@@ -1,5 +1,4 @@
 [[!templatebody <<ENDBODY
-<TMPL_IF NAME="title">
 [[!meta title="<TMPL_VAR NAME=raw_title>"]]
 
 * Contact: <TMPL_VAR NAME="raw_contact"> <TMPL_IF NAME="mentors">

Index: wikisrc/root_on_zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/root_on_zfs.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/root_on_zfs.mdwn	23 Mar 2024 18:27:57 -0000	1.3
+++ wikisrc/root_on_zfs.mdwn	23 Mar 2024 18:40:14 -0000	1.4
@@ -1,6 +1,8 @@
 [[!meta title="Root On ZFS"]]
 
-[[!template id=needs-update reason="the `fs ramdisk-zfsroot.fs` in [[!template id=man name="boot.cfg" section="5"]] obviates the need for a custom kernel module with the ramdisk embedded"]]
+[[!template id=needs-update reason="""
+the `fs ramdisk-zfsroot.fs` in [[!template id=man name="boot.cfg" section="5"]] obviates the need for a custom kernel module with the ramdisk embedded
+"""]]
 
 NetBSD-9 gained much improved ZFS support.
 However, one feature it's still missing is the ability to have your system
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/security/cgdroot.mdwn	23 Mar 2024 18:27:57 -0000	1.21
+++ wikisrc/security/cgdroot.mdwn	23 Mar 2024 18:40:14 -0000	1.22
@@ -1,6 +1,8 @@
 [[!meta title="Root Filesystem Encryption"]]
 
-[[!template id=needs-update reason="the `fs ramdisk-cgdroot.fs` in [[!template id=man name="boot.cfg" section="5"]] obviates the need for a custom kernel module with the ramdisk embedded"]]
+[[!template id=needs-update reason="""
+the `fs ramdisk-cgdroot.fs` in [[!template id=man name="boot.cfg" section="5"]] obviates the need for a custom kernel module with the ramdisk embedded
+"""]]
 
 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.
 

--- wikisrc/tag/NAME.mdwn	2024-03-23 18:45:28.286682613 +0000
+++ /dev/null	2024-03-23 18:45:27.719863631 +0000
@@ -1,4 +0,0 @@
-[[!meta title="pages tagged NAME"]]
-
-[[!inline pages="tagged(NAME)" actions="no" archive="yes"
-feedshow=10]]
--- wikisrc/tag/__60__TMPL_VAR.mdwn	2024-03-23 18:45:28.324087190 +0000
+++ /dev/null	2024-03-23 18:45:27.719863631 +0000
@@ -1,4 +0,0 @@
-[[!meta title="pages tagged <TMPL VAR"]]
-
-[[!inline pages="tagged(__60__TMPL_VAR)" actions="no" archive="yes"
-feedshow=10]]
Index: wikisrc/templates/filecontent.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/filecontent.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/templates/filecontent.mdwn	4 Feb 2011 00:46:01 -0000	1.2
+++ wikisrc/templates/filecontent.mdwn	23 Mar 2024 18:33:22 -0000	1.3
@@ -1,10 +1,11 @@
+[[!templatebody <<ENDBODY
 <fieldset>
 <legend><TMPL_VAR raw_name></legend>
 <pre>
 <TMPL_VAR raw_text>
 </pre>
 </fieldset>
-<TMPL_UNLESS NAME="text">
+ENDBODY]]
 
 ## Description
 
@@ -36,4 +37,3 @@
     procfs      /proc     procfs   rw
     /dev/cd0a   /cdrom    cd9660   ro,noauto
     """]]
-</TMPL_UNLESS>
Index: wikisrc/templates/new_page.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/new_page.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/templates/new_page.mdwn	3 Jul 2010 21:25:34 -0000	1.1
+++ wikisrc/templates/new_page.mdwn	23 Mar 2024 18:33:22 -0000	1.2
@@ -1,2 +1,4 @@
+[[!templatebody <<ENDBODY
 [[!meta title="Foo Bar, or, A Nice-Looking Title"]]
 
+ENDBODY]]
Index: wikisrc/templates/note.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/note.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/templates/note.mdwn	9 Nov 2009 01:35:01 -0000	1.1
+++ wikisrc/templates/note.mdwn	23 Mar 2024 18:33:22 -0000	1.2
@@ -1,7 +1,9 @@
+[[!templatebody <<ENDBODY
 <div class="notebox">
 <TMPL_VAR text>
 </div>
-<TMPL_UNLESS NAME="text">
+ENDBODY]]
+
 ## Description
 
 Use this template to insert a note into a page. The note will be styled to float to the right of other text on the page. This template has one parameter:
@@ -19,4 +21,3 @@
         \[[!template id=note text="""
         <img src="http://www.netbsd.org/images/NetBSD-smaller.png" /><br />
         The official NetBSD Foundation Logo."""]]
-</TMPL_UNLESS>
Index: wikisrc/templates/popup.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/popup.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/templates/popup.mdwn	10 Nov 2009 00:29:02 -0000	1.1
+++ wikisrc/templates/popup.mdwn	23 Mar 2024 18:33:22 -0000	1.2
@@ -1,4 +1,9 @@
-<TMPL_UNLESS NAME="mouseover">
+[[!templatebody <<ENDBODY
+<span class="popup"><TMPL_VAR mouseover>
+<span class="paren">[</span><span class="balloon"><TMPL_VAR popup></span><span class="paren">]</span>
+</span>
+ENDBODY]]
+
 ## Description
 
 Use this template to create a popup window that is displayed when the mouse
@@ -14,8 +19,3 @@
 Trigger a popup when [[!template id=popup mouseover="hovering this text" popup="Here comes the content of the popup."]]:
 
         \[[!template id=popup mouseover="hovering this text" popup="Here comes the content of the popup."]]
-
-</TMPL_UNLESS>
-<span class="popup"><TMPL_VAR mouseover>
-<span class="paren">[</span><span class="balloon"><TMPL_VAR popup></span><span class="paren">]</span>
-</span>
Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- wikisrc/templates/port.mdwn	8 Nov 2022 22:35:56 -0000	1.31
+++ wikisrc/templates/port.mdwn	23 Mar 2024 18:33:22 -0000	1.32
@@ -1,3 +1,4 @@
+[[!templatebody <<ENDBODY
 <TMPL_IF NAME="port">
 [[!meta title="NetBSD/<TMPL_VAR port>"]]
 
@@ -268,8 +269,8 @@
 ## Additional Info
 <TMPL_VAR additional>
 </TMPL_IF>
+ENDBODY]]
 
-<TMPL_ELSE>
 # Ports page template
 
 The *port* template is used to make the ports pages very easy
@@ -293,5 +294,3 @@
 - unsupported_hardware (optional)
 - no_install_notes (optional)
 - additional (optional)
-
-</TMPL_IF>
Index: wikisrc/templates/programlisting.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/programlisting.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/templates/programlisting.mdwn	12 May 2010 16:41:24 -0000	1.7
+++ wikisrc/templates/programlisting.mdwn	23 Mar 2024 18:33:22 -0000	1.8
@@ -1,5 +1,6 @@
+[[!templatebody <<ENDBODY
 <pre class="programlisting"><TMPL_VAR raw_text></pre>
-<TMPL_UNLESS NAME="text">
+ENDBODY]]
 
 ## Description
 
@@ -39,5 +40,3 @@
     chmod      dd         expr       ls         ps         rmdir      tar
     cp         df         hostname   mkdir      pwd        sh         test
     """]]
-
-</TMPL_UNLESS>
--- wikisrc/templates/project-test.mdwn	2024-03-23 18:45:28.726208595 +0000
+++ /dev/null	2024-03-23 18:45:27.719863631 +0000
@@ -1,44 +0,0 @@
-<TMPL_IF NAME="title">
-## <TMPL_VAR NAME="title">
-
-* contact: <TMPL_VAR NAME="contact">
-* mentors: <TMPL_VAR NAME="mentors">
-
-<i><TMPL_VAR NAME="description"></i>
-
-### requirements<br />
-<TMPL_VAR NAME="requirements">
-
-### deliverables<br />
-<TMPL_VAR NAME="deliverables">
-
-### expected duration<br />
-<TMPL_VAR NAME="duration">
-
-
-[[!tag <TMPL_VAR NAME="skills">]]
-[[!tag <TMPL_VAR NAME="difficulty">]]
-[[!tag <TMPL_VAR NAME="funded">]]
-
-<TMPL_ELSE>
-
-## Description
-
-This template will make a standard project proposal page.  It takes many parameters:
-
-- title
-- requirements
-- deliverables
-- duration
-- contact
-- mentors
-- schedule
-- description
-
-*standard tags
-- funded
-- difficulty
-- skills

(Diff truncated)

Index: wikisrc/root_on_zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/root_on_zfs.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/root_on_zfs.mdwn	30 May 2023 15:06:31 -0000	1.2
+++ wikisrc/root_on_zfs.mdwn	23 Mar 2024 18:27:57 -0000	1.3
@@ -1,5 +1,7 @@
 [[!meta title="Root On ZFS"]]
 
+[[!template id=needs-update reason="the `fs ramdisk-zfsroot.fs` in [[!template id=man name="boot.cfg" section="5"]] obviates the need for a custom kernel module with the ramdisk embedded"]]
+
 NetBSD-9 gained much improved ZFS support.
 However, one feature it's still missing is the ability to have your system
 root on ZFS.
Index: wikisrc/security/cgdroot.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/cgdroot.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/security/cgdroot.mdwn	27 Nov 2023 18:40:04 -0000	1.20
+++ wikisrc/security/cgdroot.mdwn	23 Mar 2024 18:27:57 -0000	1.21
@@ -1,6 +1,6 @@
 [[!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!
+[[!template id=needs-update reason="the `fs ramdisk-cgdroot.fs` in [[!template id=man name="boot.cfg" section="5"]] obviates the need for a custom kernel module with the ramdisk embedded"]]
 
 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.
 

Index: wikisrc/security/meltdown_spectre.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/security/meltdown_spectre.mdwn,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- wikisrc/security/meltdown_spectre.mdwn	22 Dec 2018 08:20:01 -0000	1.38
+++ wikisrc/security/meltdown_spectre.mdwn	23 Mar 2024 18:25:51 -0000	1.39
@@ -1,5 +1,7 @@
 [[!meta title="Meltdown and Spectre Status Page"]]
 
+[[!template id=needs-update reason="netbsd-9 and netbsd-10 aren't catalogued and more recent Spectre-class vulnerabilities are probably missing"]]
+
 Status of the Fixes
 -------------------
 

Index: wikisrc/set-up_raidframe.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/set-up_raidframe.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/set-up_raidframe.mdwn	30 Nov 2013 16:36:58 -0000	1.9
+++ wikisrc/set-up_raidframe.mdwn	23 Mar 2024 18:16:46 -0000	1.10
@@ -1,5 +1,7 @@
 [[!meta  title="Setting up raidframe(4) on NetBSD"]]
 
+[[!template id=needs-update reason="netbsd-10 has new raidctl create operation to make this easier"]]
+
 After posting lots of questions, and getting lots of expert help, I finally got my new server up and running with raid!  Since I asked so many questions, it was suggested that I recap the process so that someone else might be able to make it work without having to ask!
 
 So ...

Index: wikisrc/examples.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/examples.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/examples.mdwn	17 Apr 2010 17:03:16 -0000	1.2
+++ wikisrc/examples.mdwn	23 Mar 2024 18:09:47 -0000	1.3
@@ -1,4 +1,3 @@
 Example usage of various NetBSD APIs.
 
-- [[examples/drvctlio]]
-- [[examples/proplib]]
+[[!map pages="examples/*"]]

Index: wikisrc/tutorials.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials.mdwn,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- wikisrc/tutorials.mdwn	1 Aug 2023 09:35:39 -0000	1.49
+++ wikisrc/tutorials.mdwn	23 Mar 2024 18:09:10 -0000	1.50
@@ -8,7 +8,7 @@
 * [Enabling or disabling extended attributes and ACLs on FFS](acls_and_extended_attributes_on_ffs)
 
 ## Guide and HOWTOs
-* [Root on ZFS](../wiki/RootOnZFS/)
+* [Root on ZFS](../root_on_zfs/)
 * [[set-up raidframe]]
 * [[LaTeX in NetBSD]]
 * [[How to use snapshots]]

Index: wikisrc/tutorials/how_to_use_encrypted_swap_over_nfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_encrypted_swap_over_nfs.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/tutorials/how_to_use_encrypted_swap_over_nfs.mdwn	9 Sep 2020 14:28:56 -0000	1.4
+++ wikisrc/tutorials/how_to_use_encrypted_swap_over_nfs.mdwn	23 Mar 2024 17:54:38 -0000	1.5
@@ -2,6 +2,8 @@
 
 [[!toc levels=3]]
 
+[[!template id=needs-update reason="netbsd-10 vm.swap_encrypt=1, default on most platforms today, obsoletes swapping to cgd"]]
+
 #  Summary 
 
 It's getting more and more popular to use encrypted swap. This is however not a trivial task with nfs-swap. Swap over nfs is supported like this: 

Index: wikisrc/examples/drvctlio.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/examples/drvctlio.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/examples/drvctlio.mdwn	25 Apr 2010 21:21:05 -0000	1.2
+++ wikisrc/examples/drvctlio.mdwn	23 Mar 2024 17:50:16 -0000	1.3
@@ -1,54 +1,52 @@
-This and other code examples really want the [[wiki/todo/highlight_plugin]]. --[[schmonz]]
+[[!format c """
+#include <sys/ioctl.h>
+#include <sys/drvctlio.h>
 
------
+#include <err.h>
+#include <string.h>
+#include <stdlib.h>
+#include <fcntl.h>
 
-    #include <sys/ioctl.h>
-    #include <sys/drvctlio.h>
-    
-    #include <err.h>
-    #include <string.h>
-    #include <stdlib.h>
-    #include <fcntl.h>
-    
-    int
-    main(int argc, char *argv[])
-    {
-            struct devlistargs l;
-            unsigned int i, children;
-            int drvfd;
-    
-            if (argc != 2)
-                    err(1, "args");
-    
-            if ((drvfd = open(DRVCTLDEV, O_RDONLY, 0)) < 0)
-                    err(1, "can't open " DRVCTLDEV);
-    
-            strlcpy(l.l_devname, argv[1], sizeof(l.l_devname));
-            l.l_childname = NULL;
-            l.l_children = 0;
-    
-            if (ioctl(drvfd, DRVLISTDEV, &l) == -1)
-                    err(1, "DRVLISTDEV");
-    
-            children = l.l_children;
-            l.l_childname = malloc(sizeof(l.l_childname[0]) * children);
-    
-            if (ioctl(drvfd, DRVLISTDEV, &l) == -1)
-                    err(1, "DRVLISTDEV");
-    
-            if (l.l_children != children)
-                    err(1, "number of children changed between ioctls");
-    
-            if (l.l_childname == NULL) {
-                    puts("No children.");
-                    return 0;
-            }
-    
-            for (i = 0; i < l.l_children; i++) {
-                    puts(l.l_childname[i]);
-            }
-    
-            close(drvfd);
-    
-            return 0;
-    }
+int
+main(int argc, char *argv[])
+{
+        struct devlistargs l;
+        unsigned int i, children;
+        int drvfd;
+
+        if (argc != 2)
+                err(1, "args");
+
+        if ((drvfd = open(DRVCTLDEV, O_RDONLY, 0)) < 0)
+                err(1, "can't open " DRVCTLDEV);
+
+        strlcpy(l.l_devname, argv[1], sizeof(l.l_devname));
+        l.l_childname = NULL;
+        l.l_children = 0;
+
+        if (ioctl(drvfd, DRVLISTDEV, &l) == -1)
+                err(1, "DRVLISTDEV");
+
+        children = l.l_children;
+        l.l_childname = malloc(sizeof(l.l_childname[0]) * children);
+
+        if (ioctl(drvfd, DRVLISTDEV, &l) == -1)
+                err(1, "DRVLISTDEV");
+
+        if (l.l_children != children)
+                err(1, "number of children changed between ioctls");
+
+        if (l.l_childname == NULL) {
+                puts("No children.");
+                return 0;
+        }
+
+        for (i = 0; i < l.l_children; i++) {
+                puts(l.l_childname[i]);
+        }
+
+        close(drvfd);
+
+        return 0;
+}
+"""]]
Index: wikisrc/examples/proplib.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/examples/proplib.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/examples/proplib.mdwn	13 May 2011 08:47:34 -0000	1.2
+++ wikisrc/examples/proplib.mdwn	23 Mar 2024 17:50:16 -0000	1.3
@@ -4,61 +4,65 @@
 
 This will create a dictionary and store it as an xml file on the disk:
 
-    int
-    main(void)
-    {
-        prop_dictionary_t d;
-        bool r;
-
-        d = prop_dictionary_create();
-
-        if (d == NULL)
-            goto error;
-
-        r = prop_dictionary_set_cstring(d, "name", "Adam");
-        if (!r)
-            goto error;
-        r = prop_dictionary_set_uint32(d, "year", 1986);
-        if (!r)
-            goto error;
-
-        r = prop_dictionary_externalize_to_file(d, "test.plist");
-        if (!r)
-            goto error;
-
-        return EXIT_SUCCESS;
-
-        error :
-            fprintf(stderr, "error\n");
-            return EXIT_FAILURE;
-    }
+[[!format c """
+int
+main(void)
+{
+    prop_dictionary_t d;
+    bool r;
+
+    d = prop_dictionary_create();
+
+    if (d == NULL)
+        goto error;
+
+    r = prop_dictionary_set_cstring(d, "name", "Adam");
+    if (!r)
+        goto error;
+    r = prop_dictionary_set_uint32(d, "year", 1986);
+    if (!r)
+        goto error;
+
+    r = prop_dictionary_externalize_to_file(d, "test.plist");
+    if (!r)
+        goto error;
+
+    return EXIT_SUCCESS;
+
+    error :
+        fprintf(stderr, "error\n");
+        return EXIT_FAILURE;
+}
+"""]]
 
 And this will read it and display the values:
 
-    int
-    main(void)
-    {
-        prop_dictionary_t d;
-        uint32_t year;
-        char *name;
-        bool r;
-
-        d = prop_dictionary_internalize_from_file("test.plist");
-        if (d == NULL)
-            goto error;
-
-        r = prop_dictionary_get_cstring(d, "name", &name);
-        if (!r)

(Diff truncated)

--- /dev/null	2024-03-23 18:45:31.295931200 +0000
+++ wikisrc/tag/status:active.mdwn	2024-03-23 18:45:32.273620156 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged status:active"]]
+
+[[!inline pages="tagged(status:active)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:31.295931200 +0000
+++ wikisrc/tag/__60__TMPL_VAR.mdwn	2024-03-23 18:45:32.674007668 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged <TMPL VAR"]]
+
+[[!inline pages="tagged(__60__TMPL_VAR)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:31.295931200 +0000
+++ wikisrc/tag/releng.mdwn	2024-03-23 18:45:33.075389266 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged releng"]]
+
+[[!inline pages="tagged(releng)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:31.295931200 +0000
+++ wikisrc/tag/blog.mdwn	2024-03-23 18:45:33.452320676 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged blog"]]
+
+[[!inline pages="tagged(blog)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/NAME.mdwn	2024-03-23 18:45:33.839768004 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged NAME"]]
+
+[[!inline pages="tagged(NAME)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/category:pkgsrc.mdwn	2024-03-23 18:45:34.241862449 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:pkgsrc"]]
+
+[[!inline pages="tagged(category:pkgsrc)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/kerberos.mdwn	2024-03-23 18:45:34.643898777 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged kerberos"]]
+
+[[!inline pages="tagged(kerberos)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/difficulty:hard.mdwn	2024-03-23 18:45:35.039862445 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged difficulty:hard"]]
+
+[[!inline pages="tagged(difficulty:hard)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/category:languages.mdwn	2024-03-23 18:45:35.430230922 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:languages"]]
+
+[[!inline pages="tagged(category:languages)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/howto.mdwn	2024-03-23 18:45:35.861525442 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged howto"]]
+
+[[!inline pages="tagged(howto)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/easy.mdwn	2024-03-23 18:45:36.265448099 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged easy"]]
+
+[[!inline pages="tagged(easy)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/gsoc175h.mdwn	2024-03-23 18:45:36.686433200 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged gsoc175h"]]
+
+[[!inline pages="tagged(gsoc175h)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/difficulty:unknown.mdwn	2024-03-23 18:45:37.070513070 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged difficulty:unknown"]]
+
+[[!inline pages="tagged(difficulty:unknown)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/category:networking.mdwn	2024-03-23 18:45:37.498226215 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:networking"]]
+
+[[!inline pages="tagged(category:networking)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/gsoc350h.mdwn	2024-03-23 18:45:37.908150429 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged gsoc350h"]]
+
+[[!inline pages="tagged(gsoc350h)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/tier3port.mdwn	2024-03-23 18:45:38.322732984 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged tier3port"]]
+
+[[!inline pages="tagged(tier3port)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:33.645533833 +0000
+++ wikisrc/tag/category:misc.mdwn	2024-03-23 18:45:38.760952486 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:misc"]]
+
+[[!inline pages="tagged(category:misc)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:38.983949990 +0000
+++ wikisrc/tag/status:done.mdwn	2024-03-23 18:45:39.166687263 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged status:done"]]
+
+[[!inline pages="tagged(status:done)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:38.983949990 +0000
+++ wikisrc/tag/tier2port.mdwn	2024-03-23 18:45:39.564993089 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged tier2port"]]
+
+[[!inline pages="tagged(tier2port)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:38.983949990 +0000
+++ wikisrc/tag/pkgsrc.mdwn	2024-03-23 18:45:39.959948108 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged pkgsrc"]]
+
+[[!inline pages="tagged(pkgsrc)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:38.983949990 +0000
+++ wikisrc/tag/category:userland.mdwn	2024-03-23 18:45:40.361632673 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:userland"]]
+
+[[!inline pages="tagged(category:userland)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:38.983949990 +0000
+++ wikisrc/tag/smp_networking.mdwn	2024-03-23 18:45:40.760376405 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged smp networking"]]
+
+[[!inline pages="tagged(smp_networking)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:38.983949990 +0000
+++ wikisrc/tag/needs-update.mdwn	2024-03-23 18:45:41.159101134 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged needs-update"]]
+
+[[!inline pages="tagged(needs-update)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:38.983949990 +0000
+++ wikisrc/tag/schmonz.mdwn	2024-03-23 18:45:41.578452438 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged schmonz"]]
+
+[[!inline pages="tagged(schmonz)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/gsoc.mdwn	2024-03-23 18:45:41.994139496 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged gsoc"]]
+
+[[!inline pages="tagged(gsoc)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/difficulty:easy.mdwn	2024-03-23 18:45:42.384194476 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged difficulty:easy"]]
+
+[[!inline pages="tagged(difficulty:easy)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/tier1port.mdwn	2024-03-23 18:45:42.790644895 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged tier1port"]]
+
+[[!inline pages="tagged(tier1port)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/category:ports.mdwn	2024-03-23 18:45:43.201398482 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:ports"]]
+
+[[!inline pages="tagged(category:ports)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/kern.mdwn	2024-03-23 18:45:43.593214206 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged kern"]]
+
+[[!inline pages="tagged(kern)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/difficulty:__60__TMPL_VAR.mdwn	2024-03-23 18:45:44.008816683 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged difficulty:<TMPL VAR"]]
+
+[[!inline pages="tagged(difficulty:__60__TMPL_VAR)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/funded.mdwn	2024-03-23 18:45:44.398304674 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged funded"]]
+
+[[!inline pages="tagged(funded)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/difficulty:medium.mdwn	2024-03-23 18:45:44.802706567 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged difficulty:medium"]]
+
+[[!inline pages="tagged(difficulty:medium)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/category:kernel.mdwn	2024-03-23 18:45:45.194118725 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:kernel"]]
+
+[[!inline pages="tagged(category:kernel)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/category:__60__TMPL_VAR.mdwn	2024-03-23 18:45:45.622755764 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:<TMPL VAR"]]
+
+[[!inline pages="tagged(category:__60__TMPL_VAR)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/category:filesystems.mdwn	2024-03-23 18:45:46.016955592 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:filesystems"]]
+
+[[!inline pages="tagged(category:filesystems)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/project.mdwn	2024-03-23 18:45:46.407824833 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged project"]]
+
+[[!inline pages="tagged(project)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/category:desktop.mdwn	2024-03-23 18:45:46.826339395 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:desktop"]]
+
+[[!inline pages="tagged(category:desktop)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tag/category:analyzers.mdwn	2024-03-23 18:45:47.219767846 +0000
@@ -0,0 +1,4 @@
+[[!meta title="pages tagged category:analyzers"]]
+
+[[!inline pages="tagged(category:analyzers)" actions="no" archive="yes"
+feedshow=10]]

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/templates/needs-update.mdwn	2024-03-23 18:45:47.635743729 +0000
@@ -0,0 +1,17 @@
+[[!templatebody <<ENDBODY
+[[!tag needs-update]]
+THIS PAGE NEEDS AN UPDATE BECAUSE <TMPL_VAR NAME="reason">
+ENDBODY]]
+
+## Description
+
+Use this template to indicate the content of a wiki page needs attention from someone who knows better.
+The template uses one parameter:
+
+* *reason* - [required] What's wrong with the current content and/or what would be better
+
+## Examples
+
+Link to [[!template id=needs-update reason="uvm now does swap encryption natively, cgd not needed"]]:
+
+        \[[!template id=needs-update reason="uvm now does swap encryption natively, cgd not needed"]]
Index: wikisrc/users/schmonz.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/schmonz.mdwn,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- wikisrc/users/schmonz.mdwn	30 May 2023 15:22:10 -0000	1.45
+++ wikisrc/users/schmonz.mdwn	23 Mar 2024 17:38:18 -0000	1.46
@@ -1,5 +1,7 @@
 [[schmonz_73x73.jpg]]
 
+[[!template id=needs-update reason="been a while since he looked like that"]]
+
 ## This site
 
 You can mostly point a finger at me for how `wiki.netbsd.org` works (or sometimes doesn't).

Index: wikisrc/users/schmonz/pkgsrccon2014.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/schmonz/pkgsrccon2014.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/users/schmonz/pkgsrccon2014.mdwn	14 Mar 2023 23:00:55 -0000	1.17
+++ wikisrc/users/schmonz/pkgsrccon2014.mdwn	23 Mar 2024 17:21:23 -0000	1.18
@@ -40,7 +40,7 @@
 
 ## Benny Siegert: "BulkTracker"
 
-* [BulkTracker](http://bulktracker.appspot.com) is WIP to parse
+* [BulkTracker](https://releng.netbsd.org/bulktracker/) is WIP to parse
   `pkgsrc-bulk` reports and present them in an organized way
 * Uses lots of trendy stuff:
     * Google App Engine

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

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>

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/]]

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)

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>

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

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

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"

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
 

--- /dev/null	2024-03-23 18:45:41.702424587 +0000
+++ wikisrc/tutorials/pkgsrc/build_ccache_distcc/comment_2_6f170c154512e0bba26a2dd5729c0b7d._comment	2024-03-23 18:45:52.152435290 +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`
+"""]]

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

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

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
+

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

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]`

Members: 
	tutorials/setting_up_blocklistd.mdwn:INITIAL->1.1 

--- /dev/null	2024-03-23 18:45:53.478893439 +0000
+++ wikisrc/tutorials/setting_up_blocklistd.mdwn	2024-03-23 18:45:55.043909506 +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

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.

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
 

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)

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
 

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:
 

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)

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
 

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
 

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

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

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

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.

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
 
 """

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.
+
 """
 ]]

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="""
 

--- /dev/null	2024-03-23 18:46:01.237771445 +0000
+++ wikisrc/projects/project/fullfs.mdwn	2024-03-23 18:46:01.502251171 +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.
+
+"""
+]]

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)

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: 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]]