Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -r1.17 -r1.18
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	10 Sep 2026 22:55:32 -0000	1.17
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	11 Sep 2026 08:44:44 -0000	1.18
@@ -9,6 +9,8 @@
 
 The devsummit will take place on September 11 (the day before the main conference) in room D.0.07.
 
+The presentations (see the schedule below) will be streamed and recorded, but there will be no audio recording/streaming during the discussions.
+
 ### NetBSD Dinner
 
 September 11, evening: Le Saint-Hubert, Place des Chasseurs Ardennais -- FOSDEM regulars will recognize the place :)

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	10 Sep 2026 22:50:26 -0000	1.16
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	10 Sep 2026 22:55:32 -0000	1.17
@@ -38,6 +38,7 @@
 ?? - 10:45 | Everybody | Hacking, discussions, ...
 10:45 - 11:00 | Harold Gutch/Everybody | Welcome, introductions, ...
 11:00 - 12:00 | Leonardo Taccari (`leot@`) | Google Summer of Code: introduction, quick report of 2026 projects and moreâ„¢!
+12:00 - 13:00 | | lunch break
 13:00 - 14:00 | Benny Siegert (`bsiegert@`) | Using `jj` for version control (with demo)
 14:00 - 15:00 | Harold Gutch (`hgutch@`) | Running NetBSD on the Wii U (with demo)
 15:00 - ?? | Everybody | Discussions

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	10 Sep 2026 12:08:31 -0000	1.15
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	10 Sep 2026 22:50:26 -0000	1.16
@@ -7,7 +7,7 @@
 
 Additional details about the conference can be found at the official website: <https://2026.eurobsdcon.org/>
 
-The devsummit will take place on September 11 (the day before the main conference).  The exact room at the conference venue will be announced in time.
+The devsummit will take place on September 11 (the day before the main conference) in room D.0.07.
 
 ### NetBSD Dinner
 
@@ -31,17 +31,27 @@
 Benny | `bsiegert@` | yes |
 """]]
 
-## Planning to present something?
+## Schedule
 
 [[!table data="""
-Speaker | Title
-Leonardo Taccari (`leot@`) | Google Summer of Code: introduction, quick report of 2026 projects and moreâ„¢!
-Benny Siegert (`bsiegert@`) | Using `jj` for version control (with demo)
-Harold Gutch (`hgutch@`) | Running NetBSD on the Wii U (with demo)
+Time | Speaker | Title
+?? - 10:45 | Everybody | Hacking, discussions, ...
+10:45 - 11:00 | Harold Gutch/Everybody | Welcome, introductions, ...
+11:00 - 12:00 | Leonardo Taccari (`leot@`) | Google Summer of Code: introduction, quick report of 2026 projects and moreâ„¢!
+13:00 - 14:00 | Benny Siegert (`bsiegert@`) | Using `jj` for version control (with demo)
+14:00 - 15:00 | Harold Gutch (`hgutch@`) | Running NetBSD on the Wii U (with demo)
+15:00 - ?? | Everybody | Discussions
 """]]
 
 ## Discussions
 
+Potential discussion topics:
+
+* LLM/AI use (for things not covered by the commit guidelines)
+* Repo conversion
+* Multimedia/gaming with NetBSD
+* ...
+
 ### NetBSD 11
 
 * ...

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	7 Sep 2026 21:29:29 -0000	1.14
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	10 Sep 2026 12:08:31 -0000	1.15
@@ -37,6 +37,7 @@
 Speaker | Title
 Leonardo Taccari (`leot@`) | Google Summer of Code: introduction, quick report of 2026 projects and moreâ„¢!
 Benny Siegert (`bsiegert@`) | Using `jj` for version control (with demo)
+Harold Gutch (`hgutch@`) | Running NetBSD on the Wii U (with demo)
 """]]
 
 ## Discussions

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	7 Sep 2026 21:21:53 -0000	1.13
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	7 Sep 2026 21:29:29 -0000	1.14
@@ -25,7 +25,7 @@
 Stephen | `sborrill@` | yes | 10th or 11th, please
 Adrian | `ast@` | yes | n/a
 Yuri | `yurix@` | yes | n/a
-Leonardo | `leot@` | yes | vegetarian
+Leonardo | `leot@` | yes | vegetarian + 2 guests (count me x3!, probably the two guests without any dietary restrictions)
 Pierre | `khorben@` | TBD | tentative
 Reinoud | `reinoud@` | yes | n/a
 Benny | `bsiegert@` | yes |

Members: 
	summits/eurobsdcon_2026_netbsd_summit.mdwn:1.12->1.13 

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	30 Aug 2026 18:40:58 -0000	1.12
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	7 Sep 2026 21:21:53 -0000	1.13
@@ -35,7 +35,7 @@
 
 [[!table data="""
 Speaker | Title
-Leonardo Taccari (`leot@`) | Google Summer of Code: introduction and report of 2026 projects
+Leonardo Taccari (`leot@`) | Google Summer of Code: introduction, quick report of 2026 projects and moreâ„¢!
 Benny Siegert (`bsiegert@`) | Using `jj` for version control (with demo)
 """]]
 

Members: 
	ports/aarch64.mdwn:1.21->1.22 

Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- wikisrc/ports/aarch64.mdwn	1 Aug 2026 17:43:48 -0000	1.21
+++ wikisrc/ports/aarch64.mdwn	7 Sep 2026 20:27:16 -0000	1.22
@@ -29,7 +29,13 @@
 The port is fully functional. It has been tested on single-CPU and
 multiprocessor configurations, including big.LITTLE asymmetric multiprocessing.
 
-The lists of supported boards, SoCs and CPUs is likely incomplete.
+"""
+supported_hardware="""
+
+### Bootable Install Images
+
+We provide [ready-to-install / boot images](https://armbsd.org)
+for many of the supported boards.
 
 ### SoC specific information
 
@@ -63,6 +69,8 @@
  * Marvell ThunderX
  * NVIDIA Denver2
 
+**NOTE**: The list of supported boards, SoCs and CPUs is likely incomplete.
+
 [//]: ### Unknown CPUs list:
 [//]: * Arm Cortex-A32
 [//]: * Arm Cortex-A35

Point to dtb lists instead of NetBSD 9 kernel configs for supported device
trees.

Add link to aarch64 port.

PR misc/60686.

Members: 
	ports/evbarm.mdwn:1.117->1.118 

Index: wikisrc/ports/evbarm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/evbarm.mdwn,v
retrieving revision 1.117
retrieving revision 1.118
diff -u -r1.117 -r1.118
--- wikisrc/ports/evbarm.mdwn	1 Aug 2026 17:43:48 -0000	1.117
+++ wikisrc/ports/evbarm.mdwn	7 Sep 2026 20:25:46 -0000	1.118
@@ -4,10 +4,10 @@
 port_var1="earmv6hf"
 port_var2="earmv7hf"
 port_var3="earmv7hfeb"
+port_var3_no_packages="true"
 port_var4="aarch64"
 port_var5="aarch64eb"
 port_var_install_notes="evbarm-earmv5"
-iso_image="true"
 pkg_rel="11.0"
 cur_rel="11.0"
 future_rel="12.0"
@@ -26,6 +26,11 @@
 """
 supported_hardware="""
 
+### Bootable Install Images
+
+We provide [ready-to-install / boot images](https://armbsd.org)
+for many of the supported boards.
+
 ### CPU types
 
 Various CPU variants are supported, e.g:
@@ -36,7 +41,7 @@
   most recent and common 32-bit ARM boards. Supports up to 8 CPUs.
 - earmv7hfeb - Same as the above, but with the CPU running in
   big endian mode.
-- aarch64 - 64-bit ARMv8-A boards, e.g. all 64-bit hardware.
+- [[aarch64|ports/aarch64]] - 64-bit ARMv8-A boards, e.g. all 64-bit hardware.
   Fully 64-bit kernel and userland. Running 32-bit binaries is supported
   with `compat32`.
 - aarch64eb - Same as the above, but with the CPU running in
@@ -63,14 +68,9 @@
  - [[Terasic DE0 Nano-SoC|Cyclone5]]
 
 **NOTE**: This list is incomplete. For a full list of supported device tree
-based boards, please see the list of
-[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.
+based boards, please see the 
+[dtb](https://github.com/NetBSD/src/tree/netbsd-11/distrib/sets/lists/dtb)
+list for the corresponding port.
 
 ### QEMU
 

Should not affect currect articles. It is needed for evbarm at least.

Members: 
	templates/port.mdwn:1.35->1.36 

Index: wikisrc/templates/port.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/templates/port.mdwn,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- wikisrc/templates/port.mdwn	20 Jul 2026 12:49:19 -0000	1.35
+++ wikisrc/templates/port.mdwn	7 Sep 2026 20:00:55 -0000	1.36
@@ -149,59 +149,75 @@
   </TMPL_UNLESS>
   <TMPL_IF pkg_rel>
     <TMPL_IF port_var1>
-      <li>
-        <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var1> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var1>/<TMPL_VAR pkg_rel>/">
-          NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var1> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
-        </a>
-      </li>
+      <TMPL_UNLESS port_var1_no_packages>
+        <li>
+          <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var1> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var1>/<TMPL_VAR pkg_rel>/">
+            NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var1> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
+          </a>
+        </li>
+      </TMPL_UNLESS>
     <TMPL_IF port_var2>
-      <li>
-        <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var2> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var2>/<TMPL_VAR pkg_rel>/">
-          NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var2> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
-        </a>
+      <TMPL_UNLESS port_var2_no_packages>
+        <li>
+          <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var2> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var2>/<TMPL_VAR pkg_rel>/">
+            NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var2> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
+          </a>
       </li>
+      </TMPL_UNLESS>
     </TMPL_IF>
     <TMPL_IF port_var3>
-      <li>
-        <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var3> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var3>/<TMPL_VAR pkg_rel>/">
-          NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var3> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
-        </a>
-      </li>
+      <TMPL_UNLESS port_var3_no_packages>
+        <li>
+          <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var3> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var3>/<TMPL_VAR pkg_rel>/">
+            NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var3> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
+          </a>
+        </li>
+      </TMPL_UNLESS>
     </TMPL_IF>
     <TMPL_IF port_var4>
-      <li>
-        <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var4> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var4>/<TMPL_VAR pkg_rel>/">
-          NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var4> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
-        </a>
-      </li>
+      <TMPL_UNLESS port_var4_no_packages>
+        <li>
+          <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var4> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var4>/<TMPL_VAR pkg_rel>/">
+            NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var4> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
+          </a>
+        </li>
+      </TMPL_UNLESS>
     </TMPL_IF>
     <TMPL_IF port_var5>
-      <li>
-        <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var5> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var5>/<TMPL_VAR pkg_rel>/">
-          NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var5> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
-        </a>
-      </li>
+      <TMPL_UNLESS port_var5_no_packages>
+        <li>
+          <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var5> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var5>/<TMPL_VAR pkg_rel>/">
+            NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var5> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
+          </a>
+        </li>
+      </TMPL_UNLESS>
     </TMPL_IF>
     <TMPL_IF port_var6>
-      <li>
-        <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var6> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var6>/<TMPL_VAR pkg_rel>/">
-          NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var6> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
-        </a>
-      </li>
+      <TMPL_UNLESS port_var6_no_packages>
+        <li>
+          <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var6> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var6>/<TMPL_VAR pkg_rel>/">
+            NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var6> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
+          </a>
+        </li>
+      </TMPL_UNLESS>
     </TMPL_IF>
     <TMPL_IF port_var7>
-      <li>
-        <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var7> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var7>/<TMPL_VAR pkg_rel>/">
-          NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var7> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
-        </a>
-      </li>
+      <TMPL_UNLESS port_var7_no_packages>
+        <li>
+          <a title="NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var7> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port_var7>/<TMPL_VAR pkg_rel>/">
+            NetBSD/<TMPL_VAR port>-<TMPL_VAR port_var7> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
+          </a>
+        </li>
+      </TMPL_UNLESS>
     </TMPL_IF>
     <TMPL_ELSE>
-      <li>
-        <a title="NetBSD/<TMPL_VAR port> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port>/<TMPL_VAR pkg_rel>/">
-          NetBSD/<TMPL_VAR port> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
-        </a>
-      </li>
+      <TMPL_UNLESS port_no_packages>
+        <li>
+          <a title="NetBSD/<TMPL_VAR port> pkgsrc binary packages" href="https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/<TMPL_VAR port>/<TMPL_VAR pkg_rel>/">
+            NetBSD/<TMPL_VAR port> <TMPL_VAR pkg_rel> pre-built binary packages from pkgsrc
+          </a>
+        </li>
+      </TMPL_UNLESS>
     </TMPL_IF>
   </TMPL_IF>
   <TMPL_IF changes_cur>
@@ -279,7 +295,9 @@
 - port (required)
 - port_suffix (optional)
 - port_alt (optional)
+- port_no_packages (optional)
 - port_var[1-7] (optional)
+- port_var[1-7]_no_packages (optional)
 - install_image (optional)
 - port_var_install_notes (optional)
 - about (required)

Index: wikisrc/gaming.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/gaming.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/gaming.mdwn	5 Sep 2026 02:18:10 -0000	1.2
+++ wikisrc/gaming.mdwn	6 Sep 2026 00:59:13 -0000	1.3
@@ -1,5 +1,9 @@
 [[!meta title="Gaming"]]
 
+## General Info
+
+* [[Installing Games from GOG|gaming/installing_games_from_gog]]
+
 ## Games
 
 * [[CrossCode|gaming/crosscode]]

--- /dev/null	2026-09-06 00:58:59.627596522 +0000
+++ wikisrc/gaming/installing_games_from_gog.mdwn	2026-09-06 00:59:51.178540949 +0000
@@ -0,0 +1,82 @@
+[[!meta title="Installing Games from GOG"]]
+
+When you purchase a game from [GOG](https://www.gog.com/), you can download
+the offline backup installer for it. Unfortunately, there's no "NetBSD"
+option; you must instead download the installer intended for Linux or
+Windows.
+
+This page shows the different ways you could extract the files. You may have
+to use several different strategies across your GOG library -- no single
+strategy works for every game.
+
+
+## Linux Executables
+
+### Unzipping the shell archive
+
+GOG's installers for Linux games look like shell scripts, but amazingly,
+embedded in each one is a zip archive! Hence, you can (counterintuitively)
+unzip the file directly.
+
+```
+$ unzip ./ftl_advanced_edition_1_6_12_2_35269.sh
+```
+
+### Using the GUI installer with `compat_linux`
+
+NetBSD's Linux compatibility layer permits the Linux installers to run as
+intended, with a nice GUI. This is the most attractive way to install
+software from GOG, but it requires setup.
+
+You must have the Linux emulation packages installed:
+
+```
+# pkgin install suse
+```
+
+You must load the Linux compatibility kernel module:
+
+```
+# modload compat_linux
+
+    - or -
+
+# echo compat_linux >> /etc/modules.conf
+# service modules restart
+```
+
+Make the installer executable and run it!
+
+```
+$ chmod +x ./ftl_advanced_edition_1_6_12_2_35269.sh
+$ /emul/linux/bin/bash ./ftl_advanced_edition_1_6_12_2_35269.sh
+```
+
+If you encounter unreadable or garbagey text, you might need to initialize
+the Pango modules file. Run the following command as root and try again.
+
+```
+# /emul/linux/usr/bin/pango-querymodules-64 > /emul/linux/etc/pango/pango.modules
+```
+
+
+## Windows Executables
+
+## Using `innoextract`
+
+`innoextract` is a command-line tool that can extract files from certain
+install wizards, including the ones prepared by GOG.
+
+```
+# pkgin install innoextract
+```
+
+Put the installer (the `.exe` file) and all of the data parts (the `.bin`
+files) in the same directory. When you use `innoextract`, be sure to enable
+the program's `--gog` flag, like so:
+
+```
+$ mkdir morrowind
+$ cd morrowind
+$ innoextract --gog setup_the_elder_scrolls_iii_morrowind_goty_1.6.0.1820_gog_0.1_(77582).exe
+```

Index: wikisrc/gaming.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/gaming.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/gaming.mdwn	5 Sep 2026 01:58:40 -0000	1.1
+++ wikisrc/gaming.mdwn	5 Sep 2026 02:18:10 -0000	1.2
@@ -3,3 +3,4 @@
 ## Games
 
 * [[CrossCode|gaming/crosscode]]
+* [[Red Eclipse|gaming/redeclipse]]

--- /dev/null	2026-09-05 02:18:03.671732715 +0000
+++ wikisrc/gaming/redeclipse.mdwn	2026-09-05 02:18:34.415554139 +0000
@@ -0,0 +1,14 @@
+[[!meta title="Red Eclipse"]]
+
+Two versions of [Red Eclipse][] are provided in pkgsrc:
+
+- `games/redeclipse`, which provides the newest version of the game, and
+- `games/redeclipse16`, which provides version 1.6. This is the older
+  version of the game with all the older maps.
+
+[Red Eclipse]: https://www.redeclipse.net/
+
+It is possible to install both versions of the game on the same system. The
+newer package provides the executables `redeclipse` and `redeclipse-server`;
+the older package has renamed the executables to `redeclipse16` and
+`redeclipse16-server`.

Index: wikisrc/index.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/index.mdwn,v
retrieving revision 1.78
retrieving revision 1.79
diff -u -r1.78 -r1.79
--- wikisrc/index.mdwn	15 Jan 2024 00:29:27 -0000	1.78
+++ wikisrc/index.mdwn	5 Sep 2026 01:59:24 -0000	1.79
@@ -10,6 +10,7 @@
 * [[Security]]
 * [[GitHub]]
 * [[Amazon EC2]]
+* [[Gaming]]
 * [[pkgsrc]]
 * [[releng]]
 

--- /dev/null	2026-09-05 01:58:48.363430992 +0000
+++ wikisrc/gaming.mdwn	2026-09-05 01:59:29.423561309 +0000
@@ -0,0 +1,5 @@
+[[!meta title="Gaming"]]
+
+## Games
+
+* [[CrossCode|gaming/crosscode]]

--- /dev/null	2026-09-05 01:58:03.623270630 +0000
+++ wikisrc/gaming/crosscode.mdwn	2026-09-05 01:58:42.807604099 +0000
@@ -0,0 +1,120 @@
+[[!meta title="CrossCode"]]
+
+[CrossCode][] is a retro-inspired 2D action RPG that takes place in the
+distant future, developed by [Radical Fish Games][].
+
+Amazingly, the game is written entirely in HTML and JavaScript. That means
+with just a few tweaks, it's possible to play this wonderful game natively
+on NetBSD with Firefox!
+
+Most of the information here comes from [Solene Rapenne][] and Thomas
+Frohwein (thanks!), but this page shows some NetBSD-specific tricks.
+
+[CrossCode]: https://www.cross-code.com/en/home
+[Radical Fish Games]: https://www.radicalfishgames.com/
+[Solene Rapenne]: https://dataswamp.org/~solene/2019-12-09-crosscode-instructions-playing.html
+
+
+## Where to buy
+
+[GOG](https://www.gog.com/en/game/crosscode) is the best place to purchase
+CrossCode for playing on NetBSD due to ease of installation (see below).
+
+
+## Installation and setup
+
+### Obtain and extract the game files
+
+Download GOG's Windows offline backup game installer for CrossCode. (It
+shouldn't matter whether you get the 64-bit or 32-bit version.)
+
+Download `innoextract` from pkgsrc:
+
+```
+# pkgin install innoextract
+```
+
+Create a new directory, change into it, and extract the game files from the
+installer:
+
+```
+$ mkdir crosscode
+$ cd crosscode
+$ innoextract --gog setup_crosscode_1.4.2-3_(32bit)_(65218).exe
+```
+
+(Alternatively, you could download the Linux installer and unzip it, [as
+Solene explains][Solene Rapenne].)
+
+### Apply a patch
+
+Find the file called `node-webkit.html` inside the `assets` folder. You need
+to comment out (or delete) the indicated block of code; it's toward the
+bottom of the file. (Patch courtesy of Solene Rapenne.)
+
+```
+--- node-webkit.html.orig	Mon Dec  9 17:27:17 2019
++++ node-webkit.html	Mon Dec  9 17:27:39 2019
+@@ -51,12 +51,12 @@
+ <script type="text/javascript">
+     // make sure we don't let node-webkit show it's error page
+     // TODO for release mode, there should be an option to write to a file or something.
+-    window['process'].once('uncaughtException', function() {
++/*    window['process'].once('uncaughtException', function() {
+         var win = require('nw.gui').Window.get();
+         if(!(win.isDevToolsOpen && win.isDevToolsOpen())) {
+             win.showDevTools && win.showDevTools();
+         }
+-    });
++    });*/
+     
+     function doStartCrossCodePlz(){
+       if(window.startCrossCode){
+```
+
+### Configure `bozohttpd`
+
+The next step is to make CrossCode available on a local web server.
+Fortunately, NetBSD comes with [bozohttpd][] out of the box, and it is easy
+to set up. Just add a line like the following to [inetd.conf(5)][]:
+
+```
+9000 stream tcp nowait:1200 _httpd /usr/libexec/httpd httpd -X /path/to/crosscode/assets
+```
+
+[inetd.conf(5)]: https://man.netbsd.org/inetd.conf.5
+[bozohttpd]: https://man.netbsd.org/bozohttpd.8
+
+**NOTE.** The first number is the port number. 9000 is just an example.
+Please pick a number that won't be used for any other applications on your
+system. _Your game progress will be lost_ if you host the game from a
+different port, so choose a number that will be reserved for CrossCode!
+
+**NOTE.** The "1200" `nowait:1200` represents bozohttpd's _maximum spawn
+rate_. It's important for this number to be high enough, otherwise the game
+may crash. The default value of 40 is not suitable for CrossCode. 1200 works
+in my testing, but in case of failure, try raising this number and
+restarting `inetd`.
+
+To start bozohttpd, add `inetd=YES` to `/etc/rc.conf` and then start (or
+restart) the inetd service:
+
+```
+# service inetd start   # or 'restart'
+```
+
+## Play on!
+
+Point Firefox to `http://localhost:9000/node-webkit.html`. The game should
+load now. Have fun, and try not to lower the difficulty setting!
+
+
+## What works
+
+- Sound, video
+- Saving and loading progress
+
+
+## What doesn't work
+
+- Controller support 

Index: wikisrc/languages.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/languages.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/languages.mdwn	15 Dec 2024 21:39:09 -0000	1.10
+++ wikisrc/languages.mdwn	5 Sep 2026 00:24:58 -0000	1.11
@@ -10,6 +10,7 @@
 Go       | yes   | yes     | yes  | yes   | no      | no      | no    | no   | no
 Guile    | yes   | yes     | yes  | yes   | yes     | yes     | yes   | yes  | yes
 Haskell  | yes   | no      | no   | no    | no      | no      | no    | no   | no
+Janet    | yes   | yes     | yes  | yes   | no      | no      | yes   | no   | no
 Java 8   | yes   | yes     | yes  | yes   | yes     | no      | no    | no   | no
 Java 11  | yes   | no      | yes  | no    | no      | no      | no    | no   | no
 NodeJS   | yes   | yes     | yes  | yes   | no      | no      | no    | no   | no

Index: wikisrc/users/charlotte.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/charlotte.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/charlotte.mdwn	5 Sep 2026 00:01:33 -0000	1.3
+++ wikisrc/users/charlotte.mdwn	5 Sep 2026 00:05:23 -0000	1.4
@@ -1,5 +1,6 @@
-[[!meta  title="Charlotte's Spot"]]
+[[!meta  title="Charlotte Koch (charlotte)"]]
 
-Hola, this is Charlotte's spot.
+Hola, this is Charlotte's page.
 
 - [My NetBSD www page](https://www.netbsd.org/~charlotte/)
+- [My personal website](https://dressupgeekout.com)

Index: wikisrc/users/charlotte.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/charlotte.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/charlotte.mdwn	6 Aug 2025 04:34:40 -0000	1.2
+++ wikisrc/users/charlotte.mdwn	5 Sep 2026 00:01:33 -0000	1.3
@@ -1,3 +1,5 @@
+[[!meta  title="Charlotte's Spot"]]
+
 Hola, this is Charlotte's spot.
 
 - [My NetBSD www page](https://www.netbsd.org/~charlotte/)

Index: wikisrc/users/drixter/ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter/ec2.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/users/drixter/ec2.mdwn	12 Aug 2026 08:06:59 -0000	1.8
+++ wikisrc/users/drixter/ec2.mdwn	3 Sep 2026 18:26:23 -0000	1.9
@@ -1,6 +1,6 @@
 # NetBSD EC2 AMI 11.0 #
 
-There aren't many of them in the AWS environment; some are broken and some are old, so I decided to use the information: [here](https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html) and [here](https://www.netmeister.org/blog/netbsd-amd64-ami.html here)
+There aren't many of them in the AWS environment; some are broken and some are old, so I decided to use the information: [here](https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html) and [here](https://www.netmeister.org/blog/netbsd-amd64-ami.html [here])
 
 After minor tweaks, I compiled and publicly released the following AMIs.
 These aren't official images, but I'd appreciate feedback from anyone using AWS on whether everything is OK or if something is wrong.

Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.64
retrieving revision 1.65
diff -u -r1.64 -r1.65
--- wikisrc/releng.mdwn	10 Aug 2026 12:21:43 -0000	1.64
+++ wikisrc/releng.mdwn	3 Sep 2026 16:37:30 -0000	1.65
@@ -27,10 +27,8 @@
 
 ### NetBSD 9.x
 
-* Next minor release will be NetBSD 9.5 (ETA end of August 2026)
-  + 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)
-* end of support for netbsd-9 end of August 2026 (with the 9.5 release)
+* NetBSD 9.5 has been released
+* the netbsd-9 branch will not receive any further security updates and is out of support
 
 
 ## Automated Status Information

Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.157
retrieving revision 1.158
diff -u -r1.157 -r1.158
--- wikisrc/users/jun.mdwn	19 Aug 2026 01:23:39 -0000	1.157
+++ wikisrc/users/jun.mdwn	2 Sep 2026 02:56:29 -0000	1.158
@@ -9,12 +9,6 @@
 ## Event Updates [[https://www.facebook.com/NetBSD.jp]]
 
 #2026
-## Open Developers Conference 2026 NetBSD BoF
-- 2026 Aug.29 Sat 11:00-11:45 JST (UTC+9)
-- [[https://event.ospn.jp/odc2026/]]
-- Nihon Kogakuin Kamata Campus [[https://www.neec.ac.jp/portal/access/kamata/]]
-- Tour Guide [[]]
-- togetter [[]]
 
 ## Open Source Conference 2026 Hiroshima NetBSD Booth&BoF
 - 2026 Sep.12 Sun 10:00-18:00 JST (UTC+9)
@@ -68,6 +62,15 @@
 - togetter [[]]
 
 # Past in 2026
+
+## Open Developers Conference 2026 NetBSD BoF
+- 2026 Aug.29 Sat 11:00-11:45 JST (UTC+9)
+- [[https://event.ospn.jp/odc2026/]]
+- Nihon Kogakuin Kamata Campus [[https://www.neec.ac.jp/portal/access/kamata/]]
+- NetBSD BoF [[https://youtu.be/gXOL7oveHI0]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/ODC2026.pdf]]
+- togetter [[https://posfie.com/@ebijun/p/Mb7ktHu]]
+
 ## Open Source Conference 2026 Kyoto NetBSD Booth & NetBSD BoF
 - 2025 Aug.1 Sat 10:00-16:00 JST (UTC+9) 
 - 2025 Aug.1 Sat 16:00-16:45 JST (UTC+9) NetBSD BoF at Room2B [[https://event.ospn.jp/osc2026-kyoto/session/2329485]]

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	28 Aug 2026 21:07:24 -0000	1.11
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	30 Aug 2026 18:40:58 -0000	1.12
@@ -11,7 +11,7 @@
 
 ### NetBSD Dinner
 
-TODO
+September 11, evening: Le Saint-Hubert, Place des Chasseurs Ardennais -- FOSDEM regulars will recognize the place :)
 
 ## Planning to attend?
 
@@ -28,6 +28,7 @@
 Leonardo | `leot@` | yes | vegetarian
 Pierre | `khorben@` | TBD | tentative
 Reinoud | `reinoud@` | yes | n/a
+Benny | `bsiegert@` | yes |
 """]]
 
 ## Planning to present something?
@@ -35,6 +36,7 @@
 [[!table data="""
 Speaker | Title
 Leonardo Taccari (`leot@`) | Google Summer of Code: introduction and report of 2026 projects
+Benny Siegert (`bsiegert@`) | Using `jj` for version control (with demo)
 """]]
 
 ## Discussions

Members: 
	projects/project/update-webkit-gtk.mdwn:1.1->1.2 

Index: wikisrc/projects/project/update-webkit-gtk.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/projects/project/update-webkit-gtk.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/projects/project/update-webkit-gtk.mdwn	20 Jan 2026 16:52:00 -0000	1.1
+++ wikisrc/projects/project/update-webkit-gtk.mdwn	30 Aug 2026 15:07:41 -0000	1.2
@@ -11,6 +11,8 @@
 [Thomas Klausner](mailto:wiz@NetBSD.org)
 """
 
+done_by="Thomas Klausner"
+
 category="pkgsrc"
 difficulty="hard"
 duration="175 hours"

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	27 Aug 2026 10:21:22 -0000	1.10
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	28 Aug 2026 21:07:24 -0000	1.11
@@ -27,6 +27,7 @@
 Yuri | `yurix@` | yes | n/a
 Leonardo | `leot@` | yes | vegetarian
 Pierre | `khorben@` | TBD | tentative
+Reinoud | `reinoud@` | yes | n/a
 """]]
 
 ## Planning to present something?

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	11 Aug 2026 10:01:35 -0000	1.9
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	27 Aug 2026 10:21:22 -0000	1.10
@@ -26,6 +26,7 @@
 Adrian | `ast@` | yes | n/a
 Yuri | `yurix@` | yes | n/a
 Leonardo | `leot@` | yes | vegetarian
+Pierre | `khorben@` | TBD | tentative
 """]]
 
 ## Planning to present something?

Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.30
retrieving revision 1.31
diff -u -r1.30 -r1.31
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	24 Aug 2026 22:19:48 -0000	1.30
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	24 Aug 2026 22:22:13 -0000	1.31
@@ -27,7 +27,7 @@
 
 ##  Building DTrace 
 
-For recent NetBSD (Since NetBSD 8.0 for `i386`/`amd64`/`earm*`, and since NetBSD 9.1 for `aarch64`), DTrace doesn't require special building for GENERIC kernels on the supported architectures. (`i386`, `amd64`, `earm*` and `aarch64`)
+For recent NetBSD (Since NetBSD 8.0 for `i386`/`amd64`/`earm*`, and since NetBSD 9.1 for `aarch64`), **DTrace doesn't require special building for GENERIC kernels on the supported architectures.** (`i386`, `amd64`, `earm*` and `aarch64`)
 
 For custom kernels, you need the following options in your kernel: 
     

Index: wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	30 Mar 2020 15:45:00 -0000	1.29
+++ wikisrc/tutorials/how_to_enable_and_run_dtrace.mdwn	24 Aug 2026 22:19:48 -0000	1.30
@@ -8,7 +8,7 @@
 DTrace is a work-in-progress effort and it is for x86 systems and some arm boards.
 
 * i386 and amd64
-* earm* (evbarm and armv4 based ports)
+* earm* (evbarm and armv4 based ports, including aarch64)
 
 ## Supported providers
 
@@ -23,17 +23,13 @@
 * Syscall Linux (32bit & 64 bit): System calls via the Linux binary emulation layer
 * VFS: Filesystem operations (confined to namecache events at time of writing - 8.99.22)
 
-## TODO for netbsd-7
-
-* Measure effect of `options KDTRACE_HOOKS` on system performance.
-* Determine whether the profile module works and list it here.
-* Integrate [[riz|users/riz]]'s syscall provider patch.
-
 # How to use
 
 ##  Building DTrace 
 
-You need the following options in your kernel: 
+For recent NetBSD (Since NetBSD 8.0 for `i386`/`amd64`/`earm*`, and since NetBSD 9.1 for `aarch64`), DTrace doesn't require special building for GENERIC kernels on the supported architectures. (`i386`, `amd64`, `earm*` and `aarch64`)
+
+For custom kernels, you need the following options in your kernel: 
     
     options         KDTRACE_HOOKS   # kernel DTrace hooks
     options         MODULAR
@@ -45,6 +41,7 @@
 A Distribution needs to be built with the options `MKDTRACE=yes` and `MKCTF=yes`, this is taken care of automatically and doesn't need to be specified manually. The list of platforms it is applied to automatically is set in `src/share/mk/bsd.own.mk`
 
 Set the system to load the solaris and dtrace related modules in `/etc/modules.conf`, for a list of available modules, see `/stand/$MACHINE/$VERSION/modules/`
+**Note: you will get permission errors on non-x86 platforms if you neglect this step!**
 
 For example, add the following to `/etc/modules.conf` (the file may not exist already on a system):
     
@@ -55,11 +52,11 @@
 - `dtrace_profile`
 - `dtrace_sdt`
 - `dtrace_syscall`
-- `dtrace_syscall_linux`
+- `dtrace_syscall_linux` (**NOTE:** not available on `earm*`/`aarch64`)
     
 A `dtrace` device node is created automatically in `/dev/dtrace` when the modules are loaded into place.
     
-List the dtrace probes 
+## List the dtrace probes 
     
     dtrace -l
     

Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.156
retrieving revision 1.157
diff -u -r1.156 -r1.157
--- wikisrc/users/jun.mdwn	12 Aug 2026 09:39:21 -0000	1.156
+++ wikisrc/users/jun.mdwn	19 Aug 2026 01:23:39 -0000	1.157
@@ -30,7 +30,7 @@
 - Tour Guide [[]]
 - togetter [[]]
 
-## Open Source Conference 2025 Tokyo/Fall NetBSD Booth
+## Open Source Conference 2026 Tokyo/Fall NetBSD Booth
 - Booth: 2026 Oct.17 Sat 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/osc2026-fall/]]
@@ -46,6 +46,19 @@
 - togetter [[]]
 - youtube[[]]
 
+## Open Source Conference 2026 Nagaoka NetBSD Booth
+- Booth: 2026 Nov.21 Sat 10:30-17:00 JST (UTC+9)
+- Miraie Nagaoka [[https://miraie-nagaoka.jp/user-guide/]]
+- [[https://ospn.connpass.com/event/398562/]]
+- Tour Guide [[]]
+- togetter [[]]
+
+## Open Source Conference 2026 Yamaguchi NetBSD Booth
+- Booth: 2026 Nov.22 Sat 10:00-16:00 JST (UTC+9)
+- [[https://event.ospn.jp/]]
+- Tour Guide [[]]
+- togetter [[]]
+
 ## Open Source Conference 2025 Fukuoka NetBSD Booth
 - Booth: 2025 Dec.12 Sat 10:00-16:00 JST (UTC+9)
 - NetBSD BoF Dec.12 Sat XX:00-XX:45 JST (UTC+9)

Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -r1.35 -r1.36
--- wikisrc/ports.mdwn	17 Aug 2026 19:17:10 -0000	1.35
+++ wikisrc/ports.mdwn	17 Aug 2026 19:47:00 -0000	1.36
@@ -41,7 +41,7 @@
 * MI architecture decisions may penalize organic ports if there is a benefit for focus ports.
 * If the port is not working at release time, a release is done without the port and the port is moved down to the life support tier.
 
-Currently there are 49 ports with Tier II status. They are:
+Currently there are 52 ports with Tier II status. They are:
 
 [[!table data="""
 Port		|CPU		|Machines								|Latest Release
@@ -62,6 +62,7 @@
 [[evbsh3]]	|[[sh3]]	|Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs	|[11.0](http://www.NetBSD.org/releases/formal-11/)
 [[ews4800mips]]	|mips		|NEC's MIPS based EWS4800 workstations					|[11.0](http://www.NetBSD.org/releases/formal-11/)
 [[hp300]]	|m68k		|Hewlett-Packard 9000/300 and 400 series				|[11.0](http://www.NetBSD.org/releases/formal-11/)
+hb68k		|m68k		|m68k port oriented towards home-brew m68k machines			|none
 [[hppa]]	|hppa		|Hewlett-Packard 9000/700 series					|[11.0](http://www.NetBSD.org/releases/formal-11/)
 [[hpcmips]]	|mips		|MIPS based Windows CE PDA machines					|[11.0](http://www.NetBSD.org/releases/formal-11/)
 [[hpcsh]]	|[[sh3]]	|Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines		|[11.0](http://www.NetBSD.org/releases/formal-11/)
@@ -93,6 +94,7 @@
 [[sun2]]	|m68k		|Sun 2									|[11.0](http://www.NetBSD.org/releases/formal-11/)
 [[sun3]]	|m68k		|Sun 3 and 3x								|[11.0](http://www.NetBSD.org/releases/formal-11/)
 [[vax]]		|vax		|Digital VAX								|[11.0](http://www.NetBSD.org/releases/formal-11/)
+virt68k		|m68k		|QEMU m68k "virt" platform						|[11.0](http://www.NetBSD.org/releases/formal-11/)
 [[x68k]]	|m68k		|Sharp X680x0 series							|[11.0](http://www.NetBSD.org/releases/formal-11/)
 [[zaurus]]	|arm		|Sharp C7x0/C860/C1000/C3x00 series PDA					|[11.0](http://www.NetBSD.org/releases/formal-11/)
 """]]
@@ -128,11 +130,12 @@
 arm		|I, II		|[[acorn32]] [[cats]] [[epoc32]] [[evbarm]] [[hpcarm]] [[iyonix]] [[netwinder]] [[shark]] [[zaurus]]
 hppa		|II		|[[hppa]]
 i386		|I		|[[i386]] [[xen]]
-m68010		|II		|[[sun2]]
-m68k		|II		|[[amiga]] [[atari]] [[cesfic]] [[hp300]] [[luna68k]] [[mac68k]] [[mvme68k]] [[news68k]] [[next68k]] [[sun3]] [[x68k]]
+m68010		|II		|hb68k [[sun2]]
+m68k		|II		|[[amiga]] [[atari]] [[cesfic]] hb68k [[hp300]] [[luna68k]] [[mac68k]] [[mvme68k]] [[news68k]] [[next68k]] [[sun3]] virt68k [[x68k]]
 mipseb		|I, II		|[[emips]] [[evbmips]] [[ews4800mips]] [[mipsco]] [[newsmips]] [[sbmips]] [[sgimips]]
 mipsel		|I, II		|[[algor]] [[arc]] [[cobalt]] [[evbmips]] [[hpcmips]] [[pmax]] [[sbmips]]
 powerpc		|I, II		|[[amigappc]] [[bebox]] [[evbppc]] [[ibmnws]] [[macppc]] [[mvmeppc]] [[ofppc]] [[prep]] [[rs6000]] [[sandpoint]]
+riscv		|II		|[[riscv]]
 [[sh3eb|sh3]]	|II		|[[evbsh3]] [[mmeye]]
 [[sh3el|sh3]]	|II		|[[dreamcast]] [[evbsh3]] [[landisk]] [[hpcsh]]
 sparc		|II		|[[sparc]]

Index: wikisrc/ports.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports.mdwn,v
retrieving revision 1.34
retrieving revision 1.35
diff -u -r1.34 -r1.35
--- wikisrc/ports.mdwn	21 Dec 2024 21:16:40 -0000	1.34
+++ wikisrc/ports.mdwn	17 Aug 2026 19:17:10 -0000	1.35
@@ -20,15 +20,15 @@
 
 [[!table data="""
 Port		|CPU		|Machines						|Latest Release
-[[aarch64]]	|aarch64	|64-bit ARM CPUs					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[evbarm]]	|arm		|ARM evaluation boards					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[evbmips]]	|mips		|MIPS-based evaluation boards				|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[evbppc]]	|powerpc	|PowerPC-based evaluation boards			|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[hpcarm]]	|arm		|StrongARM based Windows CE PDA machines		|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[i386]]	|i386		|32-bit x86-family generic machines ("PC clones")	|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[sparc64]]	|sparc		|Sun UltraSPARC (64-bit)				|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[xen]]		|i386, x86_64	|Xen Virtual Machine Monitor				|[10.1](http://www.NetBSD.org/releases/formal-10/)
+[[aarch64]]	|aarch64	|64-bit ARM CPUs					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[amd64]]	|x86_64		|64-bit x86-family machines with AMD and Intel CPUs	|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[evbarm]]	|arm		|ARM evaluation boards					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[evbmips]]	|mips		|MIPS-based evaluation boards				|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[evbppc]]	|powerpc	|PowerPC-based evaluation boards			|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[hpcarm]]	|arm		|StrongARM based Windows CE PDA machines		|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[i386]]	|i386		|32-bit x86-family generic machines ("PC clones")	|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[sparc64]]	|sparc		|Sun UltraSPARC (64-bit)				|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[xen]]		|i386, x86_64	|Xen Virtual Machine Monitor				|[11.0](http://www.NetBSD.org/releases/formal-11/)
 """]]
 
 
@@ -45,56 +45,56 @@
 
 [[!table data="""
 Port		|CPU		|Machines								|Latest Release
-[[acorn32]]	|arm		|Acorn RiscPC/A7000/NC and compatibles					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[algor]]	|mips		|Algorithmics MIPS evaluation boards					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[alpha]]	|alpha		|Digital Alpha (64-bit)							|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[amiga]]	|m68k		|Commodore Amiga, MacroSystem DraCo					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[amigappc]]	|powerpc	|PowerPC-based Amiga boards						|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[arc]]		|mips		|Machines following the Advanced RISC Computing spec			|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[atari]]	|m68k		|Atari TT030, Falcon, Hades						|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[bebox]]	|powerpc	|Be Inc's BeBox								|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[cats]]	|arm		|Chalice Technology's Strong Arm evaluation board			|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[cesfic]]	|m68k		|CES's FIC8234 VME processor board					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[cobalt]]	|mips		|Cobalt Networks' Microservers						|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[dreamcast]]	|[[sh3]]	|Sega Dreamcast game console						|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[epoc32]]	|arm		|32bit PSION EPOC PDA							|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[emips]]	|mips		|Machines based on "Extensible MIPS"					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[evbsh3]]	|[[sh3]]	|Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs	|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[ews4800mips]]	|mips		|NEC's MIPS based EWS4800 workstations					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[hp300]]	|m68k		|Hewlett-Packard 9000/300 and 400 series				|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[hppa]]	|hppa		|Hewlett-Packard 9000/700 series					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[hpcmips]]	|mips		|MIPS based Windows CE PDA machines					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[hpcsh]]	|[[sh3]]	|Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines		|[10.1](http://www.NetBSD.org/releases/formal-10/)
+[[acorn32]]	|arm		|Acorn RiscPC/A7000/NC and compatibles					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[algor]]	|mips		|Algorithmics MIPS evaluation boards					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[alpha]]	|alpha		|Digital Alpha (64-bit)							|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[amiga]]	|m68k		|Commodore Amiga, MacroSystem DraCo					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[amigappc]]	|powerpc	|PowerPC-based Amiga boards						|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[arc]]		|mips		|Machines following the Advanced RISC Computing spec			|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[atari]]	|m68k		|Atari TT030, Falcon, Hades						|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[bebox]]	|powerpc	|Be Inc's BeBox								|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[cats]]	|arm		|Chalice Technology's Strong Arm evaluation board			|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[cesfic]]	|m68k		|CES's FIC8234 VME processor board					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[cobalt]]	|mips		|Cobalt Networks' Microservers						|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[dreamcast]]	|[[sh3]]	|Sega Dreamcast game console						|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[epoc32]]	|arm		|32bit PSION EPOC PDA							|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[emips]]	|mips		|Machines based on "Extensible MIPS"					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[evbsh3]]	|[[sh3]]	|Evaluation boards with Renesas (Hitachi) Super-H SH3 and SH4 CPUs	|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[ews4800mips]]	|mips		|NEC's MIPS based EWS4800 workstations					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[hp300]]	|m68k		|Hewlett-Packard 9000/300 and 400 series				|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[hppa]]	|hppa		|Hewlett-Packard 9000/700 series					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[hpcmips]]	|mips		|MIPS based Windows CE PDA machines					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[hpcsh]]	|[[sh3]]	|Renesas (Hitachi) SH3 and SH4 based Windows CE PDA machines		|[11.0](http://www.NetBSD.org/releases/formal-11/)
 [[ia64]]	|itanium	|Itanium family of processors						|none
-[[ibmnws]]	|powerpc	|IBM Network Station Series 1000					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[iyonix]]	|arm		|Iyonix ARM pc								|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[landisk]]	|[[sh3]]	|SH4 based NAS appliances by I-O DATA					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[luna68k]]	|m68k		|OMRON Tateisi Electronics' LUNA series					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[mac68k]]	|m68k		|Apple Macintosh							|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[macppc]]	|powerpc	|Apple Power Macintosh and clones					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[mipsco]]	|mips		|Mips family of workstations and servers				|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[mmeye]]	|[[sh3]]	|Brains' mmEye Multi Media Server					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[mvme68k]]	|m68k		|Motorola MVME 68k SBCs							|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[mvmeppc]]	|powerpc	|Motorola MVME PowerPC SBCs						|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[netwinder]]	|arm		|StrongARM based NetWinder machines					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[news68k]]	|m68k		|Sony's m68k based "NET WORK STATION" series				|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[newsmips]]	|mips		|Sony's MIPS based "NET WORK STATION" series				|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[next68k]]	|m68k		|NeXT 68k 'black' hardware						|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[ofppc]]	|powerpc	|Generic OpenFirmware compliant PowerPC machines			|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[pmax]]	|mips		|Digital MIPS-based DECstations and DECsystems				|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[prep]]	|powerpc	|PReP (PowerPC Reference Platform) and CHRP machines			|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[riscv]]	|riscv		|RISC-V									|none
-[[rs6000]]	|powerpc	|MCA-based IBM RS/6000 workstations					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[sandpoint]]	|powerpc	|Motorola Sandpoint reference platform					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[sbmips]]	|mips		|Broadcom SiByte evaluation boards					|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[sgimips]]	|mips		|Silicon Graphics' MIPS-based workstations				|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[shark]]	|arm		|Digital DNARD ("shark")						|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[sparc]]	|sparc		|Sun SPARC (32-bit)							|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[sun2]]	|m68k		|Sun 2									|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[sun3]]	|m68k		|Sun 3 and 3x								|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[vax]]		|vax		|Digital VAX								|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[x68k]]	|m68k		|Sharp X680x0 series							|[10.1](http://www.NetBSD.org/releases/formal-10/)
-[[zaurus]]	|arm		|Sharp C7x0/C860/C1000/C3x00 series PDA					|[10.1](http://www.NetBSD.org/releases/formal-10/)
+[[ibmnws]]	|powerpc	|IBM Network Station Series 1000					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[iyonix]]	|arm		|Iyonix ARM pc								|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[landisk]]	|[[sh3]]	|SH4 based NAS appliances by I-O DATA					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[luna68k]]	|m68k		|OMRON Tateisi Electronics' LUNA series					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[mac68k]]	|m68k		|Apple Macintosh							|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[macppc]]	|powerpc	|Apple Power Macintosh and clones					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[mipsco]]	|mips		|Mips family of workstations and servers				|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[mmeye]]	|[[sh3]]	|Brains' mmEye Multi Media Server					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[mvme68k]]	|m68k		|Motorola MVME 68k SBCs							|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[mvmeppc]]	|powerpc	|Motorola MVME PowerPC SBCs						|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[netwinder]]	|arm		|StrongARM based NetWinder machines					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[news68k]]	|m68k		|Sony's m68k based "NET WORK STATION" series				|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[newsmips]]	|mips		|Sony's MIPS based "NET WORK STATION" series				|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[next68k]]	|m68k		|NeXT 68k 'black' hardware						|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[ofppc]]	|powerpc	|Generic OpenFirmware compliant PowerPC machines			|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[pmax]]	|mips		|Digital MIPS-based DECstations and DECsystems				|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[prep]]	|powerpc	|PReP (PowerPC Reference Platform) and CHRP machines			|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[riscv]]	|riscv		|RISC-V									|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[rs6000]]	|powerpc	|MCA-based IBM RS/6000 workstations					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[sandpoint]]	|powerpc	|Motorola Sandpoint reference platform					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[sbmips]]	|mips		|Broadcom SiByte evaluation boards					|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[sgimips]]	|mips		|Silicon Graphics' MIPS-based workstations				|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[shark]]	|arm		|Digital DNARD ("shark")						|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[sparc]]	|sparc		|Sun SPARC (32-bit)							|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[sun2]]	|m68k		|Sun 2									|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[sun3]]	|m68k		|Sun 3 and 3x								|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[vax]]		|vax		|Digital VAX								|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[x68k]]	|m68k		|Sharp X680x0 series							|[11.0](http://www.NetBSD.org/releases/formal-11/)
+[[zaurus]]	|arm		|Sharp C7x0/C860/C1000/C3x00 series PDA					|[11.0](http://www.NetBSD.org/releases/formal-11/)
 """]]
 
 

Index: wikisrc/users/jun.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/jun.mdwn,v
retrieving revision 1.155
retrieving revision 1.156
diff -u -r1.155 -r1.156
--- wikisrc/users/jun.mdwn	23 Jul 2026 02:58:46 -0000	1.155
+++ wikisrc/users/jun.mdwn	12 Aug 2026 09:39:21 -0000	1.156
@@ -9,14 +9,6 @@
 ## Event Updates [[https://www.facebook.com/NetBSD.jp]]
 
 #2026
-## Open Source Conference 2026 Kyoto NetBSD Booth & NetBSD BoF
-- 2025 Aug.1 Sat 10:00-16:00 JST (UTC+9) 
-- 2025 Aug.1 Sat 16:00-16:45 JST (UTC+9) NetBSD BoF at Room2B [[https://event.ospn.jp/osc2026-kyoto/session/2329485]]
-- Kyoto Research Park [[https://www.krp.co.jp/access/map.html]]
-- [[https://event.ospn.jp/osc2026-kyoto/]]
-- Tour Guide [[]]
-- togetter [[https://posfie.com/@ebijun/p/k4thRpd]]
-
 ## Open Developers Conference 2026 NetBSD BoF
 - 2026 Aug.29 Sat 11:00-11:45 JST (UTC+9)
 - [[https://event.ospn.jp/odc2026/]]
@@ -24,9 +16,9 @@
 - Tour Guide [[]]
 - togetter [[]]
 
-
 ## Open Source Conference 2026 Hiroshima NetBSD Booth&BoF
 - 2026 Sep.12 Sun 10:00-18:00 JST (UTC+9)
+- NetBSD Bof: 2026 Sep.12 Sun 11:00-11:45 JST (UTC+9)
 - https://event.ospn.jp/osc2026-hiroshima/
 - Tour Guide [[]]
 - togetter [[]]
@@ -63,6 +55,15 @@
 - togetter [[]]
 
 # Past in 2026
+## Open Source Conference 2026 Kyoto NetBSD Booth & NetBSD BoF
+- 2025 Aug.1 Sat 10:00-16:00 JST (UTC+9) 
+- 2025 Aug.1 Sat 16:00-16:45 JST (UTC+9) NetBSD BoF at Room2B [[https://event.ospn.jp/osc2026-kyoto/session/2329485]]
+- Kyoto Research Park [[https://www.krp.co.jp/access/map.html]]
+- [[https://event.ospn.jp/osc2026-kyoto/]]
+- Tour Guide [[https://cdn.netbsd.org/pub/NetBSD/misc/jun/OSC/OSC2026kyoto.pdf]]
+- togetter [[https://posfie.com/@ebijun/p/k4thRpd]]
+- [[https://speakerdeck.com/tsutsui/osc2026kyoto]] LUNA68K+animationGIF
+
 ## Open Source Conference 2026 Shimane NetBSD Booth
 - Booth: 2026 Jul.11 Sat 10:00-17:00 JST (UTC+9)
 - Matsue Terusa,near by JR Matsue station

Index: wikisrc/amazon_ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/amazon_ec2.mdwn,v
retrieving revision 1.57
retrieving revision 1.58
diff -u -r1.57 -r1.58
--- wikisrc/amazon_ec2.mdwn	9 Jan 2024 13:03:33 -0000	1.57
+++ wikisrc/amazon_ec2.mdwn	12 Aug 2026 08:14:47 -0000	1.58
@@ -7,3 +7,4 @@
 * [Build instructions for NetBSD AMI with ENA support - HVM](http://www.netbsd.org/~ryoon/ena/how-to-create-ami-for-aws-c5.txt)
 * [NetBSD AMIs identifiers, by region](amis)
 * [Using bsdec2-image-upload to create an AMI](bsdec2_image_upload)
+* [NetBSD EC2 AMI 11.0 - Non-official](ec2-11)

--- /dev/null	2026-08-12 08:14:02.894126844 +0000
+++ wikisrc/amazon_ec2/ec2-11.mdwn	2026-08-12 08:14:41.286163769 +0000
@@ -0,0 +1,48 @@
+# NetBSD EC2 AMI 11.0 #
+
+There aren't many of them in the AWS environment; some are broken and some are old, so I decided to use the information: [here](https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html) and [here](https://www.netmeister.org/blog/netbsd-amd64-ami.html here)
+
+After minor tweaks, I compiled and publicly released the following AMIs.
+These aren't official images, but I'd appreciate feedback from anyone using AWS on whether everything is OK or if something is wrong.
+You might be using AWS and didn't know the latest images were available. Now you know :-)
+
+For me personally, NetBSD works very well as a small instance with AWS Graviton2 Processor which is quite cheap after good cost optimization in AWS.
+
+## Non-official NetBSD 11.0 AMI Images ##
+
+Login details: ec2-user
+
+<table class="center">
+<tr>
+  <th>NetBSD version</th>
+  <th>eu-north-1<br />(Stockholm)</th>
+  <th>eu-central-1<br />(Frankfurt)</th>
+  <th>us-east-1<br />(Virginia)</th>
+</tr>
+<tr>
+  <th>NetBSD 11.0 AMD64</th>
+  <td>ami-0145cddb5cf345869</td><!-- eu-north-1 -->
+  <td>ami-0cf4a39aa5be88c2f</td><!-- eu-central-1 -->
+  <td>ami-04b3fd43f30b85024</td><!-- us-eest-1 -->
+</tr>
+<tr>
+  <th>NetBSD 11.0 ARM64</th>
+  <td>ami-02b0c6989549cef7b</td><!-- eu-north-1 -->
+  <td>ami-0d74af44a2f94f069</td><!-- eu-central-1 -->
+  <td>ami-0f9369fa3f85b9845</td><!-- us-eest-1 -->
+</tr>
+<tr>
+  <th>NetBSD 10.1 AMD64</th>
+  <td>ami-06e42a9707a64d92b</td><!-- eu-north-1 -->
+  <td>ami-0461e97d4fc700c6c</td><!-- eu-central-1 -->
+  <td>ami-0a04013eb378f1d1f</td><!-- us-eest-1 -->
+</tr>
+<tr>
+  <th>NetBSD 10.1 ARM64</th>
+  <td>ami-07cd7639672404936</td><!-- eu-north-1 -->
+  <td>ami-008a0557d7ac250fb</td><!-- eu-central-1 -->
+  <td>ami-0f85e38a4af745890</td><!-- us-eest-1 -->
+</tr>
+</table>
+
+In case of problems, gaps, let me know drixter(AT)NetBSD.org or drixter(AT)e-utp.net.

Index: wikisrc/users/drixter/ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter/ec2.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:50:43 -0000	1.7
+++ wikisrc/users/drixter/ec2.mdwn	12 Aug 2026 08:06:59 -0000	1.8
@@ -45,4 +45,4 @@
 </tr>
 </table>
 
-In case of problems, gaps, let me know.
+In case of problems, gaps, let me know drixter(AT)NetBSD.org or drixter(AT)e-utp.net.

Index: wikisrc/root_on_zfs.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/root_on_zfs.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/root_on_zfs.mdwn	27 Nov 2024 02:04:56 -0000	1.5
+++ wikisrc/root_on_zfs.mdwn	11 Aug 2026 16:24:23 -0000	1.6
@@ -33,7 +33,7 @@
 
 Until the NetBSD installer can be updated, here are the manual steps from fresh:
 
-  *  Build the ramdisk (`cd src/distrib/amd64/ramdisks/ramdisk-zfsroot; nbmake-amd64`)
+  *  Build the ramdisk (`cd src/distrib/amd64/ramdisks/ramdisk-zfsroot; nbmake-amd64`) or fetch it from a release, e.g. [NetBSD/amd64 11.0 ramdisk-zfsroot.fs](https://cdn.NetBSD.org/pub/NetBSD/NetBSD-11.0/amd64/installation/ramdisk/ramdisk-zfsroot.fs)
   *  Boot the NetBSD installer
   *  Create a small (I used 2G) FFS partition and a normal swap partition
   *  Create a partition for ZFS

Members: 
	summits/eurobsdcon_2026_netbsd_summit.mdwn:1.8->1.9 

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	2 Aug 2026 17:22:24 -0000	1.8
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	11 Aug 2026 10:01:35 -0000	1.9
@@ -32,7 +32,7 @@
 
 [[!table data="""
 Speaker | Title
-... | ...
+Leonardo Taccari (`leot@`) | Google Summer of Code: introduction and report of 2026 projects
 """]]
 
 ## Discussions

Members: 
	tutorials/how_to_use_snapshots.mdwn:1.51->1.52 

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -r1.51 -r1.52
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	10 Aug 2026 13:52:22 -0000	1.51
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	10 Aug 2026 13:54:39 -0000	1.52
@@ -386,9 +386,9 @@
 back it up with tarsnap:
 
 [[!template id=programlisting text="""
+# touch /tmp/20260706
 # fssconfig fss3 /var /var/
 # mount /dev/fss3 /mnt
-# touch /tmp/20260706
 # tarsnap -C /mnt -cf var-20260706 --snaptime /tmp/20260706 .
 # rm /tmp/20260706
 # umount /mnt

Members: 
	tutorials/how_to_use_snapshots.mdwn:1.50->1.51 

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.50
retrieving revision 1.51
diff -u -r1.50 -r1.51
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	1 Aug 2026 16:03:36 -0000	1.50
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	10 Aug 2026 13:52:22 -0000	1.51
@@ -432,7 +432,7 @@
 # fssconfig fss1 /data /var/tmp/
 # mount /dev/fss1 /mnt
 # ssh rsynchost mkdir /backups/$(hostname)/data/20260706
-# rsync -aHc --link-dest=../latest/. \
+# rsync -aHcz --link-dest=../latest/. \
     /mnt/. rsynchost:/backups/$(hostname)/data/20260706/.
 # ssh rsynchost ln -sfn 20260706 /backups/$(hostname)/latest
 # umount /mnt

Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.63
retrieving revision 1.64
diff -u -r1.63 -r1.64
--- wikisrc/releng.mdwn	10 Aug 2026 12:19:27 -0000	1.63
+++ wikisrc/releng.mdwn	10 Aug 2026 12:21:43 -0000	1.64
@@ -27,7 +27,7 @@
 
 ### NetBSD 9.x
 
-* Next minor release will be NetBSD 9.5, ETA end of August 2026.
+* Next minor release will be NetBSD 9.5 (ETA end of August 2026)
   + 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)
 * end of support for netbsd-9 end of August 2026 (with the 9.5 release)

Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.62
retrieving revision 1.63
diff -u -r1.62 -r1.63
--- wikisrc/releng.mdwn	1 Aug 2026 17:43:48 -0000	1.62
+++ wikisrc/releng.mdwn	10 Aug 2026 12:19:27 -0000	1.63
@@ -21,16 +21,16 @@
 
 ### NetBSD 10.x
 
-* Next minor release: NetBSD 10.2 (ETA end of August 2026)
+* Next minor release: NetBSD 10.2 (ETA early September 2026)
   + 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 would be NetBSD 9.5, but is unlikely to happen.
+* Next minor release will be NetBSD 9.5, ETA end of August 2026.
   + 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)
-* end of support for netbsd-9 end of August 2026
+* end of support for netbsd-9 end of August 2026 (with the 9.5 release)
 
 
 ## Automated Status Information

Index: wikisrc/users/drixter.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/drixter.mdwn	8 Aug 2026 07:19:10 -0000	1.3
+++ wikisrc/users/drixter.mdwn	8 Aug 2026 07:23:31 -0000	1.4
@@ -1,3 +1,3 @@
 My corner of the NetBSD wiki
 
-- [[AWI AMI EC2|ec2]]
+- [[AWS AMI EC2|ec2]]

Index: wikisrc/users/drixter.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/drixter.mdwn	8 Aug 2026 07:06:42 -0000	1.2
+++ wikisrc/users/drixter.mdwn	8 Aug 2026 07:19:10 -0000	1.3
@@ -1,3 +1,3 @@
 My corner of the NetBSD wiki
 
-*[[AWI AMI EC2|ec2]]
+- [[AWI AMI EC2|ec2]]

Index: wikisrc/users/drixter.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/drixter.mdwn	7 Aug 2026 20:09:41 -0000	1.1
+++ wikisrc/users/drixter.mdwn	8 Aug 2026 07:06:42 -0000	1.2
@@ -1,2 +1,3 @@
 My corner of the NetBSD wiki
 
+*[[AWI AMI EC2|ec2]]

Index: wikisrc/users/drixter/ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter/ec2.mdwn,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:46:12 -0000	1.6
+++ wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:50:43 -0000	1.7
@@ -1,6 +1,6 @@
 # NetBSD EC2 AMI 11.0 #
 
-There aren't many of them in the AWS environment; some are broken and some are old, so I decided to use the information below: [here](https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html) and [here](https://www.netmeister.org/blog/netbsd-amd64-ami.html here)
+There aren't many of them in the AWS environment; some are broken and some are old, so I decided to use the information: [here](https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html) and [here](https://www.netmeister.org/blog/netbsd-amd64-ami.html here)
 
 After minor tweaks, I compiled and publicly released the following AMIs.
 These aren't official images, but I'd appreciate feedback from anyone using AWS on whether everything is OK or if something is wrong.
@@ -45,3 +45,4 @@
 </tr>
 </table>
 
+In case of problems, gaps, let me know.

Index: wikisrc/users/drixter/ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter/ec2.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:37:25 -0000	1.5
+++ wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:46:12 -0000	1.6
@@ -10,45 +10,38 @@
 
 ## Non-official NetBSD 11.0 AMI Images ##
 
-### 11.0: ###
 Login details: ec2-user
 
-** eu-north-1 (Stockholm) **
-
-- amd64: ami-0145cddb5cf345869
-
-- arm64: ami-02b0c6989549cef7b
-
-** eu-central-1 (Frankfurt) **
-
-- amd64: ami-0cf4a39aa5be88c2f
-
-- arm64: ami-0d74af44a2f94f069
-
-**  us-east-1 (N. Virginia) **
-
-- amd64: ami-04b3fd43f30b85024
-
-- arm64: ami-0f9369fa3f85b9845
-
-### 10.1 ###
-Login details: ec2-user
-
-** eu-north-1 (Stockholm) **
-
-- amd64: ami-06e42a9707a64d92b
-
-- arm64: ami-07cd7639672404936
-
-** eu-central-1 (Frankfurt) **
-
-- amd64: ami-0461e97d4fc700c6c
-
-- arm64: ami-008a0557d7ac250fb
-
-** us-east-1 (N. Virginia) **
-
-- amd64: ami-0a04013eb378f1d1f
-
-- arm64: ami-0f85e38a4af745890
+<table class="center">
+<tr>
+  <th>NetBSD version</th>
+  <th>eu-north-1<br />(Stockholm)</th>
+  <th>eu-central-1<br />(Frankfurt)</th>
+  <th>us-east-1<br />(Virginia)</th>
+</tr>
+<tr>
+  <th>NetBSD 11.0 AMD64</th>
+  <td>ami-0145cddb5cf345869</td><!-- eu-north-1 -->
+  <td>ami-0cf4a39aa5be88c2f</td><!-- eu-central-1 -->
+  <td>ami-04b3fd43f30b85024</td><!-- us-eest-1 -->
+</tr>
+<tr>
+  <th>NetBSD 11.0 ARM64</th>
+  <td>ami-02b0c6989549cef7b</td><!-- eu-north-1 -->
+  <td>ami-0d74af44a2f94f069</td><!-- eu-central-1 -->
+  <td>ami-0f9369fa3f85b9845</td><!-- us-eest-1 -->
+</tr>
+<tr>
+  <th>NetBSD 10.1 AMD64</th>
+  <td>ami-06e42a9707a64d92b</td><!-- eu-north-1 -->
+  <td>ami-0461e97d4fc700c6c</td><!-- eu-central-1 -->
+  <td>ami-0a04013eb378f1d1f</td><!-- us-eest-1 -->
+</tr>
+<tr>
+  <th>NetBSD 10.1 ARM64</th>
+  <td>ami-07cd7639672404936</td><!-- eu-north-1 -->
+  <td>ami-008a0557d7ac250fb</td><!-- eu-central-1 -->
+  <td>ami-0f85e38a4af745890</td><!-- us-eest-1 -->
+</tr>
+</table>
 

Index: wikisrc/users/drixter/ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter/ec2.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:36:00 -0000	1.4
+++ wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:37:25 -0000	1.5
@@ -14,29 +14,41 @@
 Login details: ec2-user
 
 ** eu-north-1 (Stockholm) **
+
 - amd64: ami-0145cddb5cf345869
+
 - arm64: ami-02b0c6989549cef7b
 
 ** eu-central-1 (Frankfurt) **
+
 - amd64: ami-0cf4a39aa5be88c2f
+
 - arm64: ami-0d74af44a2f94f069
 
 **  us-east-1 (N. Virginia) **
+
 - amd64: ami-04b3fd43f30b85024
+
 - arm64: ami-0f9369fa3f85b9845
 
 ### 10.1 ###
 Login details: ec2-user
 
 ** eu-north-1 (Stockholm) **
+
 - amd64: ami-06e42a9707a64d92b
+
 - arm64: ami-07cd7639672404936
 
 ** eu-central-1 (Frankfurt) **
+
 - amd64: ami-0461e97d4fc700c6c
+
 - arm64: ami-008a0557d7ac250fb
 
 ** us-east-1 (N. Virginia) **
+
 - amd64: ami-0a04013eb378f1d1f
+
 - arm64: ami-0f85e38a4af745890
 

Index: wikisrc/users/drixter/ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter/ec2.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:30:46 -0000	1.3
+++ wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:36:00 -0000	1.4
@@ -1,9 +1,6 @@
 # NetBSD EC2 AMI 11.0 #
 
-There aren't many of them in the AWS environment; some are broken and some are old, so I decided to use the information below:
-
-[here](https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html) and
-[here](https://www.netmeister.org/blog/netbsd-amd64-ami.html here)
+There aren't many of them in the AWS environment; some are broken and some are old, so I decided to use the information below: [here](https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html) and [here](https://www.netmeister.org/blog/netbsd-amd64-ami.html here)
 
 After minor tweaks, I compiled and publicly released the following AMIs.
 These aren't official images, but I'd appreciate feedback from anyone using AWS on whether everything is OK or if something is wrong.
@@ -17,29 +14,29 @@
 Login details: ec2-user
 
 ** eu-north-1 (Stockholm) **
-* amd64: ami-0145cddb5cf345869
-* arm64: ami-02b0c6989549cef7b
+- amd64: ami-0145cddb5cf345869
+- arm64: ami-02b0c6989549cef7b
 
 ** eu-central-1 (Frankfurt) **
-* amd64: ami-0cf4a39aa5be88c2f
-* arm64: ami-0d74af44a2f94f069
+- amd64: ami-0cf4a39aa5be88c2f
+- arm64: ami-0d74af44a2f94f069
 
 **  us-east-1 (N. Virginia) **
-* amd64: ami-04b3fd43f30b85024
-* arm64: ami-0f9369fa3f85b9845
+- amd64: ami-04b3fd43f30b85024
+- arm64: ami-0f9369fa3f85b9845
 
 ### 10.1 ###
 Login details: ec2-user
 
 ** eu-north-1 (Stockholm) **
-* amd64: ami-06e42a9707a64d92b
-* arm64: ami-07cd7639672404936
+- amd64: ami-06e42a9707a64d92b
+- arm64: ami-07cd7639672404936
 
 ** eu-central-1 (Frankfurt) **
-* amd64: ami-0461e97d4fc700c6c
-* arm64: ami-008a0557d7ac250fb
+- amd64: ami-0461e97d4fc700c6c
+- arm64: ami-008a0557d7ac250fb
 
 ** us-east-1 (N. Virginia) **
-* amd64: ami-0a04013eb378f1d1f
-* arm64: ami-0f85e38a4af745890
+- amd64: ami-0a04013eb378f1d1f
+- arm64: ami-0f85e38a4af745890
 

Index: wikisrc/users/drixter/ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter/ec2.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:24:06 -0000	1.2
+++ wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:30:46 -0000	1.3
@@ -1,9 +1,9 @@
-== NetBSD EC2 AMI 11.0 ==
+# NetBSD EC2 AMI 11.0 #
 
 There aren't many of them in the AWS environment; some are broken and some are old, so I decided to use the information below:
 
-[https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html here] and
-[https://www.netmeister.org/blog/netbsd-amd64-ami.html here]
+[here](https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html) and
+[here](https://www.netmeister.org/blog/netbsd-amd64-ami.html here)
 
 After minor tweaks, I compiled and publicly released the following AMIs.
 These aren't official images, but I'd appreciate feedback from anyone using AWS on whether everything is OK or if something is wrong.
@@ -11,35 +11,35 @@
 
 For me personally, NetBSD works very well as a small instance with AWS Graviton2 Processor which is quite cheap after good cost optimization in AWS.
 
-'''Non-official NetBSD 11.0 AMI Images'''
+## Non-official NetBSD 11.0 AMI Images ##
 
-=== 11.0: ===
+### 11.0: ###
 Login details: ec2-user
 
-'''eu-north-1 (Stockholm)'''
+** eu-north-1 (Stockholm) **
 * amd64: ami-0145cddb5cf345869
 * arm64: ami-02b0c6989549cef7b
 
-'''eu-central-1 (Frankfurt)'''
+** eu-central-1 (Frankfurt) **
 * amd64: ami-0cf4a39aa5be88c2f
 * arm64: ami-0d74af44a2f94f069
 
-'''us-east-1 (N. Virginia)'''
+**  us-east-1 (N. Virginia) **
 * amd64: ami-04b3fd43f30b85024
 * arm64: ami-0f9369fa3f85b9845
 
-=== 10.1 ===
+### 10.1 ###
 Login details: ec2-user
 
-'''eu-north-1 (Stockholm)'''
+** eu-north-1 (Stockholm) **
 * amd64: ami-06e42a9707a64d92b
 * arm64: ami-07cd7639672404936
 
-'''eu-central-1 (Frankfurt)'''
+** eu-central-1 (Frankfurt) **
 * amd64: ami-0461e97d4fc700c6c
 * arm64: ami-008a0557d7ac250fb
 
-'''us-east-1 (N. Virginia)'''
+** us-east-1 (N. Virginia) **
 * amd64: ami-0a04013eb378f1d1f
 * arm64: ami-0f85e38a4af745890
 

Index: wikisrc/users/drixter/ec2.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/drixter/ec2.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:15:37 -0000	1.1
+++ wikisrc/users/drixter/ec2.mdwn	7 Aug 2026 20:24:06 -0000	1.2
@@ -1,15 +1,45 @@
-# Non-official NetBSD 11.0 AMI Images (made by drixter@e-utp.net)
-# Login details: ec2-user
+== NetBSD EC2 AMI 11.0 ==
 
-eu-north-1 (Stockholm)
-amd64: ami-0145cddb5cf345869
-arm64: ami-02b0c6989549cef7b
-
-eu-central-1 (Frankfurt)
-amd64: ami-0cf4a39aa5be88c2f
-arm64: ami-0d74af44a2f94f069
-
-us-east-1 (N. Virginia)
-amd64: ami-04b3fd43f30b85024
-arm64: ami-0f9369fa3f85b9845
+There aren't many of them in the AWS environment; some are broken and some are old, so I decided to use the information below:
+
+[https://www.netmeister.org/blog/creating-netbsd-ec2-amis.html here] and
+[https://www.netmeister.org/blog/netbsd-amd64-ami.html here]
+
+After minor tweaks, I compiled and publicly released the following AMIs.
+These aren't official images, but I'd appreciate feedback from anyone using AWS on whether everything is OK or if something is wrong.
+You might be using AWS and didn't know the latest images were available. Now you know :-)
+
+For me personally, NetBSD works very well as a small instance with AWS Graviton2 Processor which is quite cheap after good cost optimization in AWS.
+
+'''Non-official NetBSD 11.0 AMI Images'''
+
+=== 11.0: ===
+Login details: ec2-user
+
+'''eu-north-1 (Stockholm)'''
+* amd64: ami-0145cddb5cf345869
+* arm64: ami-02b0c6989549cef7b
+
+'''eu-central-1 (Frankfurt)'''
+* amd64: ami-0cf4a39aa5be88c2f
+* arm64: ami-0d74af44a2f94f069
+
+'''us-east-1 (N. Virginia)'''
+* amd64: ami-04b3fd43f30b85024
+* arm64: ami-0f9369fa3f85b9845
+
+=== 10.1 ===
+Login details: ec2-user
+
+'''eu-north-1 (Stockholm)'''
+* amd64: ami-06e42a9707a64d92b
+* arm64: ami-07cd7639672404936
+
+'''eu-central-1 (Frankfurt)'''
+* amd64: ami-0461e97d4fc700c6c
+* arm64: ami-008a0557d7ac250fb
+
+'''us-east-1 (N. Virginia)'''
+* amd64: ami-0a04013eb378f1d1f
+* arm64: ami-0f85e38a4af745890
 

--- /dev/null	2026-08-07 20:16:00.139345112 +0000
+++ wikisrc/users/drixter/ec2.mdwn	2026-08-07 20:16:23.767890205 +0000
@@ -0,0 +1,15 @@
+# Non-official NetBSD 11.0 AMI Images (made by drixter@e-utp.net)
+# Login details: ec2-user
+
+eu-north-1 (Stockholm)
+amd64: ami-0145cddb5cf345869
+arm64: ami-02b0c6989549cef7b
+
+eu-central-1 (Frankfurt)
+amd64: ami-0cf4a39aa5be88c2f
+arm64: ami-0d74af44a2f94f069
+
+us-east-1 (N. Virginia)
+amd64: ami-04b3fd43f30b85024
+arm64: ami-0f9369fa3f85b9845
+

--- /dev/null	2026-08-07 20:10:01.726360377 +0000
+++ wikisrc/users/drixter.mdwn	2026-08-07 20:10:31.060588880 +0000
@@ -0,0 +1,2 @@
+My corner of the NetBSD wiki
+

Index: wikisrc/users/spz/amiga060.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/amiga060.mdwn,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 13:19:12 -0000	1.5
+++ wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 13:22:46 -0000	1.6
@@ -4,7 +4,7 @@
 
 #### /etc/mk.conf:
     .if ${MACHINE} == "amiga"
-    CPUFLAGS+=-m68020-60
+    CPUFLAGS+=-m68020-60 -mhard-float
     # kernel
     CMACHFLAGS=-m68020-60
     .endif

Index: wikisrc/users/spz/amiga060.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/amiga060.mdwn,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 11:29:55 -0000	1.4
+++ wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 13:19:12 -0000	1.5
@@ -75,3 +75,17 @@
     _double.S, _float.S and _floatex.S
 
 derivates without -m68020-60 was insufficient. Building the entire libgcc_s without (but the rest of the build with -m68020-60) also works.
+
+After consultation with someone who knows assembler (mlelstv@) the following change helped:
+
+    --- external/gpl3/gcc/dist/libgcc/config/m68k/lb1sf68.S 30 Jul 2023 05:51:37 -0000      1.10
+    +++ external/gpl3/gcc/dist/libgcc/config/m68k/lb1sf68.S 7 Aug 2026 13:16:23 -0000
+    @@ -215,7 +215,7 @@
+            lea     \addr-.-8,a0
+            jmp     pc@(a0)
+     #else
+    -       bra     \addr@PLTPC
+    +       bral    \addr@PLTPC
+     #endif
+            .endm
+

Index: wikisrc/users/spz/amiga060.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/amiga060.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 11:25:16 -0000	1.3
+++ wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 11:29:55 -0000	1.4
@@ -55,6 +55,7 @@
 
 #### when building distribution
 the build fails with:
+
 	#     build  libgcc_s/libgcc_s.so.1.0
 	rm -f libgcc_s.so.1.0
 	/home/netbsd/11/arch/amiga/tools/bin/m68k--netbsdelf-gcc -nodefaultlibs -shared -Wl,-soname,libgcc_s.so.1  -Wl,--warn-shared-textrel -Wl,-Map=libgcc_s.so.1.map   --sysroot=/home/netbsd/11/arch/amiga/destdir -nodefaultlibs -Wl,-z -Wl,nodelete -Wl,--version-script=/home/netbsd/11/arch/amiga/obj/external/gpl3/gcc/lib/libgcc/libgcc_s/libgcc.map  -o libgcc_s.so.1.0.tmp  -Wl,-rpath,/lib  -L=/lib -Wl,-x  -Wl,--whole-archive libgcc_s_pic.a  -Wl,--no-whole-archive -L/home/netbsd/11/arch/amiga/obj/external/gpl3/gcc/lib/libgcc/libgcc -lgcc 
@@ -69,6 +70,8 @@
 
 this builds when not using CPUFLAGS (surprise :/ )
 
-building just _double.S, _float.S and _floatex.S derivates without
--m68020-60 was insufficient. Building the entire libgcc_s without
-(but the rest of the build with -m68020-60) also works.
+building just
+
+    _double.S, _float.S and _floatex.S
+
+derivates without -m68020-60 was insufficient. Building the entire libgcc_s without (but the rest of the build with -m68020-60) also works.

Index: wikisrc/users/spz/amiga060.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/amiga060.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 11:16:24 -0000	1.2
+++ wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 11:25:16 -0000	1.3
@@ -68,3 +68,7 @@
 	collect2: error: ld returned 1 exit status
 
 this builds when not using CPUFLAGS (surprise :/ )
+
+building just _double.S, _float.S and _floatex.S derivates without
+-m68020-60 was insufficient. Building the entire libgcc_s without
+(but the rest of the build with -m68020-60) also works.

Index: wikisrc/users/spz/amiga060.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz/amiga060.mdwn,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 06:58:33 -0000	1.1
+++ wikisrc/users/spz/amiga060.mdwn	7 Aug 2026 11:16:24 -0000	1.2
@@ -1,5 +1,5 @@
 note: the recipies here are not necessarily the right thing to do.
-Some adjustments surely break building for other archs or CPUs.
+Some adjustments may break building for other archs or CPUs.
 It's a log of what was needed so I don't forget, and hopefully get to do it correctly eventually.
 
 #### /etc/mk.conf:
@@ -52,3 +52,19 @@
 
 #### when compiling the kernel
 locore.s needs -Wa,-m68030 and netbsd060sp.c needs pure -m68060 to build. When hitting these compile them with the -m68020-60 replaced by what they need and normally would use, and continue the kernel build with -u (very crude solution)
+
+#### when building distribution
+the build fails with:
+	#     build  libgcc_s/libgcc_s.so.1.0
+	rm -f libgcc_s.so.1.0
+	/home/netbsd/11/arch/amiga/tools/bin/m68k--netbsdelf-gcc -nodefaultlibs -shared -Wl,-soname,libgcc_s.so.1  -Wl,--warn-shared-textrel -Wl,-Map=libgcc_s.so.1.map   --sysroot=/home/netbsd/11/arch/amiga/destdir -nodefaultlibs -Wl,-z -Wl,nodelete -Wl,--version-script=/home/netbsd/11/arch/amiga/obj/external/gpl3/gcc/lib/libgcc/libgcc_s/libgcc.map  -o libgcc_s.so.1.0.tmp  -Wl,-rpath,/lib  -L=/lib -Wl,-x  -Wl,--whole-archive libgcc_s_pic.a  -Wl,--no-whole-archive -L/home/netbsd/11/arch/amiga/obj/external/gpl3/gcc/lib/libgcc/libgcc -lgcc 
+	libgcc_s_pic.a(_float.pico):(.text+0x8): relocation truncated to fit: R_68K_PLT16 against symbol `$_exception_handler' defined in .text section in libgcc_s_pic.a(_floatex.pico)
+	libgcc_s_pic.a(_float.pico):(.text+0x18): relocation truncated to fit: R_68K_PLT16 against symbol `$_exception_handler' defined in .text section in libgcc_s_pic.a(_floatex.pico)
+	libgcc_s_pic.a(_float.pico):(.text+0x22): relocation truncated to fit: R_68K_PLT16 against symbol `$_exception_handler' defined in .text section in libgcc_s_pic.a(_floatex.pico)
+	libgcc_s_pic.a(_float.pico):(.text+0x2c): relocation truncated to fit: R_68K_PLT16 against symbol `$_exception_handler' defined in .text section in libgcc_s_pic.a(_floatex.pico)
+	libgcc_s_pic.a(_float.pico):(.text+0x3c): relocation truncated to fit: R_68K_PLT16 against symbol `$_exception_handler' defined in .text section in libgcc_s_pic.a(_floatex.pico)
+	libgcc_s_pic.a(_float.pico): in function `__cmpsf2_internal':
+	(.text+0x726): relocation truncated to fit: R_68K_PLT16 against symbol `$_exception_handler' defined in .text section in libgcc_s_pic.a(_floatex.pico)
+	collect2: error: ld returned 1 exit status
+
+this builds when not using CPUFLAGS (surprise :/ )

--- /dev/null	2026-08-07 11:25:16.327681666 +0000
+++ wikisrc/users/spz/amiga060.mdwn	2026-08-07 11:26:02.275630540 +0000
@@ -0,0 +1,54 @@
+note: the recipies here are not necessarily the right thing to do.
+Some adjustments surely break building for other archs or CPUs.
+It's a log of what was needed so I don't forget, and hopefully get to do it correctly eventually.
+
+#### /etc/mk.conf:
+    .if ${MACHINE} == "amiga"
+    CPUFLAGS+=-m68020-60
+    # kernel
+    CMACHFLAGS=-m68020-60
+    .endif
+
+
+#### changes to source files:
+m68020 - m68060 doesn't need strict alignment and not aligning strictly should give more efficient code
+
+    --- external/gpl3/gcc/dist/gcc/config/m68k/m68k.cc      2 Feb 2026 20:18:21 -0000       1.1.1.1.4.1
+    +++ external/gpl3/gcc/dist/gcc/config/m68k/m68k.cc      7 Aug 2026 06:29:04 -0000
+    @@ -550,7 +550,7 @@
+       target_mask = 0;
+     
+       /* ColdFire is lenient about alignment.  */
+    -  if (!TARGET_COLDFIRE)
+    +  if (!TARGET_68020 && !TARGET_COLDFIRE)
+         target_mask |= MASK_STRICT_ALIGNMENT;
+     
+       if ((m68k_cpu_flags & FL_BITFIELD) != 0)
+
+the bootblocks are 68030 assembler code and -m68020-60 -march=68030 -mcpu=68030 won't compile. Setting AFLAGS with '=' instead of with '+=' loses assembler flags that aren't CPUFLAGS, this needs a better solution
+
+    --- sys/arch/amiga/stand/bootblock/boot/Makefile        8 Jun 2024 06:39:57 -0000       1.63
+    +++ sys/arch/amiga/stand/bootblock/boot/Makefile        7 Aug 2026 06:40:05 -0000
+    @@ -85,7 +85,7 @@ INCPATH += -I${.CURDIR}
+     INCPATH += -I${.CURDIR}/../../.. -I${.OBJDIR}
+     INCPATH += -I${.CURDIR}/../elf2bb
+ 
+    -AFLAGS += -march=68030 -mcpu=68030
+    +AFLAGS = -march=68030 -mcpu=68030
+     CAFLAGS += -Wa,-march=68030 -Wa,-mcpu=68030 ${INCPATH}
+     
+     COPTIM= -Os -fomit-frame-pointer -fcse-follow-jumps -fcse-skip-blocks
+    --- sys/arch/amiga/stand/bootblock/bootxx_ffs/Makefile  29 Apr 2022 07:45:20 -0000      1.28
+    +++ sys/arch/amiga/stand/bootblock/bootxx_ffs/Makefile  7 Aug 2026 06:40:58 -0000
+    @@ -70,7 +70,7 @@
+     INCPATH += -I${.CURDIR}/../boot -I${.CURDIR}/../../..
+     INCPATH += -I${.CURDIR}/../elf2bb -I${.OBJDIR}
+     
+    -AFLAGS += -m68030 -l
+    +AFLAGS = -m68030 -l
+     CAFLAGS += -Wa,-l -Wa,-march=68030 -Wa,-mcpu=68030 ${INCPATH} -D_PRIMARY_BOOT
+     
+     COPTIM= -Os -fomit-frame-pointer -fcse-follow-jumps -fcse-skip-blocks
+
+#### when compiling the kernel
+locore.s needs -Wa,-m68030 and netbsd060sp.c needs pure -m68060 to build. When hitting these compile them with the -m68020-60 replaced by what they need and normally would use, and continue the kernel build with -u (very crude solution)

Index: wikisrc/users/spz.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/users/spz.mdwn,v
retrieving revision 1.22
retrieving revision 1.23
diff -u -r1.22 -r1.23
--- wikisrc/users/spz.mdwn	1 Mar 2020 16:55:27 -0000	1.22
+++ wikisrc/users/spz.mdwn	7 Aug 2026 06:35:29 -0000	1.23
@@ -7,3 +7,5 @@
 *[[sandbox|spz/sandbox]]
 
 *[[(old) Security Reference List|spz/secref2]]
+
+*[[compiling NetBSD-11/amiga for -m68060-20 notes|spz/amiga060]]

Index: wikisrc/tutorials/cpu_frequency_scaling.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/cpu_frequency_scaling.mdwn,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- wikisrc/tutorials/cpu_frequency_scaling.mdwn	5 Aug 2026 07:18:34 -0000	1.3
+++ wikisrc/tutorials/cpu_frequency_scaling.mdwn	5 Aug 2026 07:23:14 -0000	1.4
@@ -1,4 +1,9 @@
-Support is enabled in GENERIC kernels by default. sysctl and sysutils/estd do the rest. 
+Support for throttling the CPU is enabled in GENERIC kernels by
+default, and available on a range of architectures, including
+evbarm, amd64, macppc, and i386. CPU speed can be changed by
+adjusting the [sysctl](//man.NetBSD.org/sysctl.8) variable
+or using sysutils/estd to do so dynamically depending on
+system load.
 
 Please refer to the relevant
 [power management](//www.NetBSD.org/docs/guide/en/chap-power.html#chap-power-adjusting-cpu-freq)

Index: wikisrc/tutorials/cpu_frequency_scaling.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/cpu_frequency_scaling.mdwn,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- wikisrc/tutorials/cpu_frequency_scaling.mdwn	5 Feb 2012 07:14:36 -0000	1.2
+++ wikisrc/tutorials/cpu_frequency_scaling.mdwn	5 Aug 2026 07:18:34 -0000	1.3
@@ -1,136 +1,5 @@
-How to throttle your CPU 
-
-Basic support is in generic kernels by default. sysctl and sysutils/estd do the rest. 
-
-**Contents**
-
-[[!toc levels=3]]
-
-#  i386 
-
-##  AMD PowerNow! 
-    
-      options 	POWERNOW_K7
-    
-
-or 
-    
-      options 	POWERNOW_K8
-    
-
-accessible through e.g. 
-    
-      sysctl machdep.powernow.frequency.current
-      sysctl machdep.powernow.frequency.available 
-      sysctl -w machdep.powernow.frequency.target=600
-    
-
-##  Intel Speedstep 
-    
-      options 	ENHANCED_SPEEDSTEP
-    
-
-accessible through e.g. 
-    
-      sysctl machdep.est.frequency.current
-      sysctl machdep.est.frequency.available
-      sysctl -w machdep.est.frequency.target=600
-    
-
-##  speedstep-ich 
-
-  * Available since NetBSD 2.0 
-    
-      ichlpcib* at pci? dev ? function ?
-      isa0 at ichlpcib?
-    
-
-accessible through 
-    
-      sysctl -w machdep.speedstep_state=[0/1]
-    
-
-where 0 is a low state and 1 is a high state. 
-
-##  speedstep-smi 
-
-  * Available since NetBSD 4.0 
-    
-      piixpcib* at pci? dev ? function ?
-      isa0 at piixpcib?
-    
-
-also accessible through 
-    
-      sysctl -w machdep.speedstep_state=[0/1]
-    
-
-##  Transmeta longrun 
-
-  * Should be activated by default 
-
-accessible through 
-    
-      machdep.tm_longrun_mode
-      machdep.tm_longrun_frequency
-      machdep.tm_longrun_voltage
-      machdep.tm_percentage
-    
-
-#  amd64 
-
-##  Cool'n'Quiet 
-
-Same procedure as with PowerNow!: 
-    
-      options 	POWERNOW_K8
-    
-
-accessible through e.g. 
-    
-      sysctl machdep.powernow.frequency.current
-      sysctl machdep.powernow.frequency.available 
-      sysctl -w machdep.powernow.frequency.target=600
-    
-
-#  Setting up estd for automatic scaling 
-
-The estd daemon dynamically sets the frequency on SpeedStep and PowerNow!-enabled CPUs depending on current CPU-utilization. It is written for systems running NetBSD or DragonFly. 
-    
-      cd /usr/pkgsrc/sysutils/estd
-      make install clean
-    
-
-To make it start at boot-time 
-    
-      cp /usr/pkg/share/examples/rc.d/estd /etc/rc.d/
-      chmod +x /etc/rc.d/estd
-    
-
-and add to /etc/rc.conf 
-    
-      estd="yes"
-      estd_flags=""
-    
-
-then as root 
-    
-      /etc/rc.d/estd restart
-    
-
-  * Examples 
-
-Maximize battery lifetime by limiting CPU-frequency to 1000 MHz and switching to lower speeds fast: 
-    
-      estd_flags="-d -b -M 1000"
-    
-
-Maximize performance by running at least at 1400MHz and switching to higher speeds real fast: 
-    
-      estd_flags="-d -a -m 1400"
-    
-
-Alternatively, you can start estd directly from /etc/rc.local instead of rc.conf/rc.d. 
-
-More in the manual. 
+Support is enabled in GENERIC kernels by default. sysctl and sysutils/estd do the rest. 
 
+Please refer to the relevant
+[power management](//www.NetBSD.org/docs/guide/en/chap-power.html#chap-power-adjusting-cpu-freq)
+section in the NetBSD Guide.

Index: wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	27 Jul 2026 18:56:40 -0000	1.7
+++ wikisrc/summits/eurobsdcon_2026_netbsd_summit.mdwn	2 Aug 2026 17:22:24 -0000	1.8
@@ -25,6 +25,7 @@
 Stephen | `sborrill@` | yes | 10th or 11th, please
 Adrian | `ast@` | yes | n/a
 Yuri | `yurix@` | yes | n/a
+Leonardo | `leot@` | yes | vegetarian
 """]]
 
 ## Planning to present something?

Index: wikisrc/ports/cats/gxemul_cats.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/cats/gxemul_cats.mdwn,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- wikisrc/ports/cats/gxemul_cats.mdwn	5 Oct 2025 12:29:48 -0000	1.7
+++ wikisrc/ports/cats/gxemul_cats.mdwn	2 Aug 2026 13:55:10 -0000	1.8
@@ -1,10 +1,10 @@
 [[!meta title="NetBSD/cats in GXemul"]]
 
-As of October 2024, GXemul runs all versions of NetBSD/cats, including all releases and -current.  Note that at the time of this writing, the latest GXemul release (0.7.0) has a bug that prevents builds compiled with GCC 10 (NetBSD 10.0 and later releases and -current after June 2021 and) from booting.  To run such a release either install GXemul from pkgsrc or apply the patch linked below.
+As of October 2024, GXemul runs all versions of NetBSD/cats, including all releases and -current.  Note that at the time of this writing, the latest GXemul release (0.7.0) has a bug that prevents builds compiled with GCC >= 10 (NetBSD 10.0 and later releases and -current after June 2021) from booting.  To run such a release either install GXemul from pkgsrc or apply the patch linked below.
 
 # Requirements
 * GXemul from pkgsrc (otherwise make sure it contains [this patch](https://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/emulators/gxemul/patches/patch-src_cpus_cpu__arm__instr__dpi.c?rev=1.1;content-type=text%2Fplain))
-* an installation .iso, e.g., [NetBSD-10.1-cats.iso](https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.1/iso/NetBSD-10.1-cats.iso) and corresponding [kernel](https://cdn.netbsd.org/pub/NetBSD/NetBSD-10.1/cats/binary/kernel/netbsd-GENERIC.gz)
+* an installation .iso, e.g., [NetBSD-11.0-cats.iso](https://cdn.netbsd.org/pub/NetBSD/NetBSD-11.0/iso/NetBSD-11.0-cats.iso) and corresponding [kernel](https://cdn.netbsd.org/pub/NetBSD/NetBSD-11.0/cats/binary/kernel/netbsd-GENERIC.gz)
 
 # Creating a disk image
 
@@ -12,7 +12,7 @@
 
 # Installing NetBSD/cats in GXemul
 
-    $ gxemul -E cats -q -d c:NetBSD-10.1-cats.iso -d d:hdd.img -j 'NETBSD.;1'
+    $ gxemul -E cats -q -d c:NetBSD-11.0-cats.iso -d d:hdd.img -j 'NETBSD.;1'
 
 Go through a standard NetBSD installation.  At the end, when configuring the networking, use the following settings:
 

Index: wikisrc/laptops.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/laptops.mdwn,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- wikisrc/laptops.mdwn	2 Aug 2026 09:50:52 -0000	1.41
+++ wikisrc/laptops.mdwn	2 Aug 2026 10:41:53 -0000	1.42
@@ -62,13 +62,9 @@
 [[!template id=man name="iwn" section="4"]] for older models.
 Atheros 11n miniPCIe cards are supported by the
 [[!template id=man name="athn" section="4"]] driver.
-Since December 2025, iwm(4) is more stable and faster in the
--current kernel for most users. These changes have not yet
-made it to a stable branch.
-
-See the
-[[!template id=man name="afterboot" section="8"]] man page for details
-on connecting to WiFi networks.
+Since December 2025, iwm(4) is more stable and performant in the
+-current kernel (for most users). These changes have not yet
+been pulled to a stable branch.
 
 USB 11n WiFi adapters such as
 [[!template id=man name="urtwn" section="4"]] and
@@ -82,6 +78,10 @@
 with NetBSD over USB using
 [[!template id=man name="urndis" section="4"]].
 
+See the
+[[!template id=man name="afterboot" section="8"]] man page for details
+on connecting to WiFi networks.
+
 Unfortunately, WiFi hardware is not particularly standardized compared
 to most other aspects of modern laptops.
 

Index: wikisrc/laptops.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/laptops.mdwn,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- wikisrc/laptops.mdwn	2 Aug 2026 09:47:37 -0000	1.40
+++ wikisrc/laptops.mdwn	2 Aug 2026 09:50:52 -0000	1.41
@@ -62,6 +62,9 @@
 [[!template id=man name="iwn" section="4"]] for older models.
 Atheros 11n miniPCIe cards are supported by the
 [[!template id=man name="athn" section="4"]] driver.
+Since December 2025, iwm(4) is more stable and faster in the
+-current kernel for most users. These changes have not yet
+made it to a stable branch.
 
 See the
 [[!template id=man name="afterboot" section="8"]] man page for details
@@ -71,8 +74,13 @@
 [[!template id=man name="urtwn" section="4"]] and
 [[!template id=man name="run" section="4"]] can also be used,
 and most/all generic USB ethernet adapters are also well supported.
+USB adapters generally have the most mature drivers and are
+the best way to get wireless networking out of your NetBSD machine.
 For a fairly complete list, see 
 [[!template id=man name="usb" section="4"]].
+Most modern smartphones can also share their internet connection
+with NetBSD over USB using
+[[!template id=man name="urndis" section="4"]].
 
 Unfortunately, WiFi hardware is not particularly standardized compared
 to most other aspects of modern laptops.

Index: wikisrc/laptops.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/laptops.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/laptops.mdwn	2 Aug 2026 09:39:23 -0000	1.39
+++ wikisrc/laptops.mdwn	2 Aug 2026 09:47:37 -0000	1.40
@@ -13,17 +13,18 @@
 
 ## Graphics
 
-NetBSD 10.0 supports Intel integrated graphics up to Tiger Lake, Nvidia
-graphics up to Pascal,, and AMD graphics up to GCNv1 (with radeon).
-The amdgpu driver for post-GCNv1 GPUs is experimental.
+NetBSD 10.0 has full acceleration with Intel integrated graphics up to
+Tiger Lake, Nvidia graphics up to Pascal, and AMD graphics up to
+GCNv1 (with radeon). The amdgpu driver for post-GCNv1 GPUs is
+experimental. The support includes connecting external monitors
+over HDMI, DisplayPort, and DisplayPort over USB-C.
 There is no change in the supported GPUs in 11.0.
 
 Anything newer than this will work, but will use `llvmpipe`
-instead of hardware acceleration for OpenGL. See
-[using wsfb with unsupported GPUs](../tutorials/x11/how_to_use_wsfb_uefi_bios_framebuffer).
-
-The support includes connecting external monitors over HDMI,
-DisplayPort, and DisplayPort over USB-C.
+instead of hardware acceleration for OpenGL, and the video
+mode will be fixed at boot. See
+[using wsfb with unsupported GPUs](../tutorials/x11/how_to_use_wsfb_uefi_bios_framebuffer) for details on how to change the video mode
+and configure X.Org.
 
 For the Intel driver, there may be slight graphical corruptions
 when using X11 without a compositor. Xfce/MATE include their own

Index: wikisrc/laptops.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/laptops.mdwn,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- wikisrc/laptops.mdwn	6 Aug 2024 18:35:28 -0000	1.38
+++ wikisrc/laptops.mdwn	2 Aug 2026 09:39:23 -0000	1.39
@@ -13,13 +13,14 @@
 
 ## Graphics
 
-NetBSD 9.0 supports Intel integrated graphics up to (including)
-Kaby Lake, Nvidia graphics up to Maxwell, and AMD graphics up to GCNv1.
-NetBSD 10.0 supports Intel integrated graphics up to Tiger Lake
-and Nvidia graphics up to Pascal.
+NetBSD 10.0 supports Intel integrated graphics up to Tiger Lake, Nvidia
+graphics up to Pascal,, and AMD graphics up to GCNv1 (with radeon).
+The amdgpu driver for post-GCNv1 GPUs is experimental.
+There is no change in the supported GPUs in 11.0.
 
 Anything newer than this will work, but will use `llvmpipe`
-instead of hardware acceleration for OpenGL.
+instead of hardware acceleration for OpenGL. See
+[using wsfb with unsupported GPUs](../tutorials/x11/how_to_use_wsfb_uefi_bios_framebuffer).
 
 The support includes connecting external monitors over HDMI,
 DisplayPort, and DisplayPort over USB-C.

Index: wikisrc/releng.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/releng.mdwn,v
retrieving revision 1.61
retrieving revision 1.62
diff -u -r1.61 -r1.62
--- wikisrc/releng.mdwn	26 Jul 2026 08:36:40 -0000	1.61
+++ wikisrc/releng.mdwn	1 Aug 2026 17:43:48 -0000	1.62
@@ -6,19 +6,22 @@
 
 ## Next Major Release
 
-The next major release will be NetBSD 11.0.
+The next major release will be NetBSD 12.0.
 
-* currently in RC1 state, 11.0 release expected before the end of february 2026.
-  + CVS branch tag: <code>netbsd-11</code>
-* [Current pull-up queue for the netbsd-11 branch](http://releng.netbsd.org/cgi-bin/req-11.cgi)
-* open issues to solve [before the 11.0 release](netbsd-11)
+* not branched yet, no timeline.
 
 
 ## Active Major Releases
 
+### NetBSD 11.x
+
+* Next minor release: NetBSD 11.1 (ETA end of September 2026)
+  + CVS branch tag: <code>netbsd-11</code>
+* [Current pull-up queue for the netbsd-11 branch](http://releng.netbsd.org/cgi-bin/req-11.cgi)
+
 ### NetBSD 10.x
 
-* Next minor release: NetBSD 10.2 (early in 2026, about a month after the 11.0 release)
+* Next minor release: NetBSD 10.2 (ETA end of August 2026)
   + 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)
 
@@ -27,7 +30,7 @@
 * Next minor release would be NetBSD 9.5, but is unlikely to happen.
   + 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)
-* end of support for netbsd-9 in first quarter 2026
+* end of support for netbsd-9 end of August 2026
 
 
 ## Automated Status Information
Index: wikisrc/ports/aarch64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/aarch64.mdwn,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- wikisrc/ports/aarch64.mdwn	15 Jan 2025 23:25:30 -0000	1.20
+++ wikisrc/ports/aarch64.mdwn	1 Aug 2026 17:43:48 -0000	1.21
@@ -8,11 +8,11 @@
 changes_port="evbarm64"
 port_alt="arm"
 iso_image="true"
-future_rel="11.0"
-changes_future="11.0"
-cur_rel="10.1"
-changes_cur="10.0"
-pkg_rel="10.0"
+future_rel="12.0"
+changes_future="12.0"
+cur_rel="11.0"
+changes_cur="11.0"
+pkg_rel="11.0"
 about="""
 NetBSD/aarch64 is a port to Arm's 64-bit CPUs and other compatible
 machines.
Index: wikisrc/ports/acorn26.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn26.mdwn,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- wikisrc/ports/acorn26.mdwn	2 Jun 2019 13:32:38 -0000	1.18
+++ wikisrc/ports/acorn26.mdwn	1 Aug 2026 17:43:48 -0000	1.19
@@ -1,8 +1,8 @@
 [[!template id=port
 port="acorn26"
-cur_rel="8.1"
-pkg_rel="6.1"
-changes_cur="8.1"
+cur_rel="11.0"
+pkg_rel="11.0"
+changes_cur="11.0"
 thumbnail="//www.netbsd.org/images/ports/arm26/arch310.gif"
 about="""
 NetBSD/acorn26 was the port of NetBSD to ARMv2 and ARMv2a machines, primarily the
Index: wikisrc/ports/acorn32.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/acorn32.mdwn,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- wikisrc/ports/acorn32.mdwn	15 Jan 2025 23:25:30 -0000	1.23
+++ wikisrc/ports/acorn32.mdwn	1 Aug 2026 17:43:48 -0000	1.24
@@ -1,10 +1,10 @@
 [[!template id=port
 port="acorn32"
 iso_image="true"
-cur_rel="10.1"
-future_rel="11.0"
-changes_cur="10.0"
-changes_future="11.0"
+cur_rel="11.0"
+future_rel="12.0"
+changes_cur="11.0"
+changes_future="12.0"
 thumbnail="//www.netbsd.org/images/ports/acorn32/riscpc.gif"
 about="""
 NetBSD/acorn32 is a port to ARM- and StrongARM-powered Acorn RiscPC compatible
Index: wikisrc/ports/algor.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/algor.mdwn,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- wikisrc/ports/algor.mdwn	15 Jan 2025 23:25:30 -0000	1.28
+++ wikisrc/ports/algor.mdwn	1 Aug 2026 17:43:48 -0000	1.29
@@ -1,10 +1,10 @@
 [[!template id=port
 port="algor"
-cur_rel="10.1"
-future_rel="11.0"
-pkg_rel="9.4"
-changes_cur="10.0"
-changes_future="11.0"
+cur_rel="11.0"
+future_rel="12.0"
+pkg_rel="11.0"
+changes_cur="11.0"
+changes_future="12.0"
 thumbnail="//www.netbsd.org/images/ports/algor/alogo2.gif"
 no_install_notes="defined"
 about="""
Index: wikisrc/ports/alpha.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/alpha.mdwn,v
retrieving revision 1.28
retrieving revision 1.29
diff -u -r1.28 -r1.29
--- wikisrc/ports/alpha.mdwn	15 Jan 2025 23:25:30 -0000	1.28
+++ wikisrc/ports/alpha.mdwn	1 Aug 2026 17:43:48 -0000	1.29
@@ -1,11 +1,11 @@
 [[!template id=port
 port="alpha"
 iso_image="true"
-cur_rel="10.1"
-pkg_rel="10.0"
-future_rel="11.0"
-changes_cur="10.0"
-changes_future="11.0"
+cur_rel="11.0"
+pkg_rel="11.0"
+future_rel="12.0"
+changes_cur="11.0"
+changes_future="12.0"
 thumbnail="//www.netbsd.org/images/ports/alpha/au-1000.gif"
 about="""
 NetBSD/alpha is a true 64-bit system that fully implements the LP64 architecture,
Index: wikisrc/ports/amd64.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amd64.mdwn,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- wikisrc/ports/amd64.mdwn	15 Jan 2025 23:25:30 -0000	1.43
+++ wikisrc/ports/amd64.mdwn	1 Aug 2026 17:43:48 -0000	1.44
@@ -2,11 +2,11 @@
 port="amd64"
 iso_image="true"
 install_image="install"
-cur_rel="10.1"
-future_rel="11.0"
-pkg_rel="10.0"
-changes_cur="10.0"
-changes_future="11.0"
+cur_rel="11.0"
+future_rel="12.0"
+pkg_rel="11.0"
+changes_cur="11.0"
+changes_future="12.0"
 thumbnail="//www.netbsd.org/images/ports/amd64/AMD_Opteron.gif"
 about="""
 NetBSD/amd64 is a port to the AMD64 family of processors; it
Index: wikisrc/ports/amiga.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/amiga.mdwn,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- wikisrc/ports/amiga.mdwn	15 Jan 2025 23:25:30 -0000	1.41
+++ wikisrc/ports/amiga.mdwn	1 Aug 2026 17:43:48 -0000	1.42
@@ -1,11 +1,11 @@
 [[!template id=port
 port="amiga"
 iso_image="true"

(Diff truncated)

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 20:23:20 -0000	1.49
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	1 Aug 2026 16:03:36 -0000	1.50
@@ -8,24 +8,38 @@
 in time.  If you take a snapshot of a file system, and later create a
 new file or modify an existing one or make any other changes to the
 file system, the snapshot will still have the old version of the file
-system without the changes.
+system without the changes.  A snapshot can be mounted as a file system
+to give a read-only view of a past state of the file system it's a
+snapshot of.
 
 Unlike copies, snapshots use space on disk only for data that have been
 overwritten since the snapshot was taken, and can be taken for a whole
 file system at once without any cooperation from applications to
 suspend their activity.
 
-Snapshots are often used to take backups.  For example, the
-[[!template id=man name="dump" section="8"]] tool for taking a backup
-of an ffs file system will use a snapshot with the “`-X`”
-or &ldquo;`-x <snapstore>`&rdquo; options to ensure that files such as
-sqlite3 databases aren't concurrently modified while it is trying to
-read them; without snapshots, such files can be backed up reliably only
-with application-specific cooperation like [sqlite3
-backup](https://sqlite.org/backup.html).  Snapshots can also be mounted
-like regular file systems to give read-only views of past states of
-file systems.  (See [caveat about incremental backups and
-mtimes](#caveat-mtime), though.)
+Snapshots are often used to [take backups](#snap-backups).  This
+ensures that files such as sqlite3 databases aren't concurrently
+modified while the backup is being taken.  Without snapshots, such
+files can be backed up reliably only with application-specific
+cooperation like [sqlite3 backup](https://sqlite.org/backup.html), or
+while applications are not running.  Caveats:
+
+- Snapshots don't magically make application data consistent.  If
+  interrupting an application suddenly, e.g. with SIGKILL or a
+  spontaneous system reboot, would leave corrupt application data in
+  the file system, then a snapshot taken at the same moment will also
+  have corrupt application data.
+
+  But for live applications that are resilient to interruption, such as
+  [sqlite3](https://sqlite.org/atomiccommit.html), a backup taken
+  without a snapshot may *still* corrupt their data, while a backup
+  taken with a snapshot will not.  (Taking a backup without a snapshot
+  is a [standard technique for corrupting sqlite3
+  databases](https://sqlite.org/howtocorrupt.html#_backup_or_restore_while_a_transaction_is_active)!)
+
+- Incremental backup tools that try to avoid reprocessing unchanged
+  files the next time around must [handle mtimes
+  carefully](#caveat-mtime).
 
 On some file systems&mdash;ffs and zfs&mdash;snapshots can be
 **persistent**: you can take a snapshot, stored in the file system
@@ -296,6 +310,7 @@
 # zfs destroy -r rpool/home@20260706
 """]]
 
+<a name="snap-backups"></a>
 ### Taking backups with snapshots
 
 A snapshot of a file system won't help you recover if the disk it is

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 15:56:00 -0000	1.48
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 20:23:20 -0000	1.49
@@ -212,7 +212,8 @@
 `<pool>/<datasetpath>@<snapname>`, and can be listed with
 &ldquo;`zfs list -t snap <pool>/<datasetpath>`&rdquo;.  Datasets can be
 rolled back to a snapshot with &ldquo;`zfs rollback`&rdquo;, or cloned
-from a snapshot with &ldquo;`zfs clone`&rdquo;.
+from a snapshot with &ldquo;`zfs clone`&rdquo;.  All snapshots in zfs
+are persistent until deleted with &ldquo;`zfs destroy`&rdquo;.
 
 The snapshots of a file system are automounted on demand as
 subdirectories of its `.zfs/snapshot/` directory, at the root of the
@@ -249,7 +250,7 @@
 # zfs rollback rpool/home/jruser@20260706
 """]]
 
-#### Discarding a persistent snapshot
+#### Discarding a snapshot
 
 When done with a snapshot, you can destroy it with
 &ldquo;`zfs destroy`&rdquo;:

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -r1.47 -r1.48
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 14:57:26 -0000	1.47
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 15:56:00 -0000	1.48
@@ -438,9 +438,9 @@
 unchanged files the next time around.  Although backing up a snapshot
 rather than the live file system avoids writing corrupted live
 application data into the backup (at least from applications that can
-recover from interruption), mtime-based incremental backups may have a
-subtle race condition that can lead to data loss if you are not
-careful.
+recover from interruption), **mtime-based incremental backups may have
+a subtle race condition that can lead to data loss if you are not
+careful.**
 
 Suppose:
 
@@ -460,11 +460,11 @@
 
 The tarsnap
 &ldquo;[`--snaptime <reference>`](https://www.tarsnap.com/snaptime.html)&rdquo;
-option avoids this problem by treating any file with an mtime equal
-to or newer than the ctime *t* of `<reference>` as if it had an mtime
-of *t* &minus; 1 when comparing mtimes on the next run.  Other backup
-tools may have&mdash;or may not have, but may need!&mdash;similar
-options to reliably take incremental backups.
+option avoids this problem by treating any file with an mtime equal to
+or newer than the ctime *t* of `<reference>` *as if* it had an mtime of
+*t* &minus; 1 in this run when comparing mtimes on the next run.  Other
+backup tools may have&mdash;or may not have, but may
+need!&mdash;similar options to reliably take incremental backups.
 
 The [[!template id=man name="dump" section="8"]] options
 &ldquo;`-X`&rdquo; and &ldquo;`-x <snapstore>`&rdquo; also avoid this

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -r1.46 -r1.47
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 14:54:11 -0000	1.46
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 14:57:26 -0000	1.47
@@ -31,13 +31,13 @@
 **persistent**: you can take a snapshot, stored in the file system
 itself, and it will persist until it is explicitly deleted, even if the
 system is rebooted.  All disk-backed file systems in NetBSD, such as
-msdos and ext2fs, also support external but non-persistent snapshots.
+ext2fs and msdosfs, also support external but non-persistent snapshots.
 
 ### Persistent snapshots in ffs
 
-*Persistent snapshots are currently supported for ffs file systems
-only—not to be confused with the fss file system snapshot
-device used to manage them.*
+*Persistent snapshots with [[!template id=man name=fss section=4]] are
+currently supported for ffs file systems only—not to be confused
+with the fss file system snapshot device used to manage them.*
 
 A persistent snapshot of a file system is represented by a file inside
 the file system (with a special flag so it can't be read or written
@@ -148,24 +148,21 @@
 
 ### External snapshots with any disk-backed file system
 
-Any file system mounted from a disk device, such as ext2fs and msdosfs,
-supports snapshots with [[!template id=man name="fss" section="4"]].
-
-An external (non-persistent)
-[[!template id=man name="fss" section="4"]] snapshot of a file system
-requires a backing store *outside* the file system, where any existing
-data in the file system will be saved if later overwritten while the
-snapshot is active.  The backing store can be either a raw character
-disk device or a regular file in another file system.  Active snapshots
-are managed with the [[!template id=man name=fssconfig section=8]]
-command.
+**Any file system mounted from a disk device, such as ext2fs and
+msdosfs, supports external (non-persistent) snapshots with
+[[!template id=man name="fss" section="4"]].**  This requires a backing
+store *outside* the file system, where any existing data in the file
+system will be saved if later overwritten while the snapshot is active.
+The backing store can be either a raw character disk device or a
+regular file in another file system.  Active snapshots are managed with
+the [[!template id=man name=fssconfig section=8]] command.
 
 [[!template id=man name="fss" section="4"]] only supports file systems
 mounted from disk devices, so it does not support, for example:
 
 - memory-backed file systems such as tmpfs
 - virtual file systems such as procfs, ptyfs, or nullfs
-- zfs
+- zfs (which manages disk devices differently through zpools of vdevs)
 - nfs
 - fuse/puffs
 

Members: 
	tutorials/how_to_use_snapshots.mdwn:1.45->1.46 

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 13:18:26 -0000	1.45
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 14:54:11 -0000	1.46
@@ -33,7 +33,7 @@
 system is rebooted.  All disk-backed file systems in NetBSD, such as
 msdos and ext2fs, also support external but non-persistent snapshots.
 
-### Persistent snapshots with [[!template id=man name="fss" section="4"]]
+### Persistent snapshots in ffs
 
 *Persistent snapshots are currently supported for ffs file systems
 only—not to be confused with the fss file system snapshot
@@ -146,7 +146,7 @@
 # rm /home/.snap/20260706.store
 """]]
 
-### External snapshots with [[!template id=man name="fss" section="4"]]
+### External snapshots with any disk-backed file system
 
 Any file system mounted from a disk device, such as ext2fs and msdosfs,
 supports snapshots with [[!template id=man name="fss" section="4"]].

Members: 
	ports/xen/howto.mdwn:1.299->1.300 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.299
retrieving revision 1.300
diff -u -r1.299 -r1.300
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 14:06:07 -0000	1.299
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 14:50:30 -0000	1.300
@@ -1,5 +1,7 @@
 [[!meta title="Xen Status and HowTo"]]
 
+[[!template id=note text="[[!toc levels=2]]"]]
+
 Xen is a Type 1 hypervisor which supports running multiple guest operating
 systems on a single physical machine. One uses the Xen kernel to control the
 CPU, memory and console, a dom0 operating system which mediates access to
@@ -24,8 +26,6 @@
 See also an [earlier Xen tutorial](http://wiki.netbsd.org/tutorials/how_to_set_up_a_guest_os_using_xen3/)
 which should perhaps be folded into this HOWTO.
 
-[[!toc]]
-
 # Overview
 
 The basic concept of Xen is that the hypervisor (xenkernel) runs on
@@ -202,8 +202,6 @@
 [scripts to run the tests](https://ftp.netbsd.org/pub/NetBSD/misc/bouyer/nbsd-tests/)
 as a source of configuration hints.
 
-[[!template id=note text="[[!toc startlevel=2]]"]]
-
 # Creating a NetBSD dom0
 
 In order to install a NetBSD as a dom0, one first installs a normal

Members: 
	ports/xen/howto.mdwn:1.298->1.299 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.298
retrieving revision 1.299
diff -u -r1.298 -r1.299
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 14:04:11 -0000	1.298
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 14:06:07 -0000	1.299
@@ -24,7 +24,7 @@
 See also an [earlier Xen tutorial](http://wiki.netbsd.org/tutorials/how_to_set_up_a_guest_os_using_xen3/)
 which should perhaps be folded into this HOWTO.
 
-[[!template id=note text="[[!toc]]"]]
+[[!toc]]
 
 # Overview
 

Members: 
	ports/xen/howto.mdwn:1.297->1.298 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.297
retrieving revision 1.298
diff -u -r1.297 -r1.298
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 14:00:04 -0000	1.297
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 14:04:11 -0000	1.298
@@ -1,7 +1,5 @@
 [[!meta title="Xen Status and HowTo"]]
 
-[[!template id=note text="[[!toc startlevel=1 levels=1]]"]]
-
 Xen is a Type 1 hypervisor which supports running multiple guest operating
 systems on a single physical machine. One uses the Xen kernel to control the
 CPU, memory and console, a dom0 operating system which mediates access to
@@ -26,6 +24,8 @@
 See also an [earlier Xen tutorial](http://wiki.netbsd.org/tutorials/how_to_set_up_a_guest_os_using_xen3/)
 which should perhaps be folded into this HOWTO.
 
+[[!template id=note text="[[!toc]]"]]
+
 # Overview
 
 The basic concept of Xen is that the hypervisor (xenkernel) runs on

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.296
retrieving revision 1.297
diff -u -r1.296 -r1.297
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:32:49 -0000	1.296
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 14:00:04 -0000	1.297
@@ -1,6 +1,6 @@
 [[!meta title="Xen Status and HowTo"]]
 
-[[!template id=note text="[[!toc startlevel=1]]"]]
+[[!template id=note text="[[!toc startlevel=1 levels=1]]"]]
 
 Xen is a Type 1 hypervisor which supports running multiple guest operating
 systems on a single physical machine. One uses the Xen kernel to control the

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.295
retrieving revision 1.296
diff -u -r1.295 -r1.296
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:26:36 -0000	1.295
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:32:49 -0000	1.296
@@ -1,6 +1,6 @@
 [[!meta title="Xen Status and HowTo"]]
 
-[[!template id=note text="[[!toc]]"]]
+[[!template id=note text="[[!toc startlevel=1]]"]]
 
 Xen is a Type 1 hypervisor which supports running multiple guest operating
 systems on a single physical machine. One uses the Xen kernel to control the

Members: 
	ports/xen/howto.mdwn:1.294->1.295 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.294
retrieving revision 1.295
diff -u -r1.294 -r1.295
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:22:44 -0000	1.294
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:26:36 -0000	1.295
@@ -1,6 +1,6 @@
 [[!meta title="Xen Status and HowTo"]]
 
-[[!template id=note text="[[!toc startlevel=0 levels=3]]"]]
+[[!template id=note text="[[!toc]]"]]
 
 Xen is a Type 1 hypervisor which supports running multiple guest operating
 systems on a single physical machine. One uses the Xen kernel to control the

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.293
retrieving revision 1.294
diff -u -r1.293 -r1.294
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:19:43 -0000	1.293
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:22:44 -0000	1.294
@@ -1,6 +1,6 @@
 [[!meta title="Xen Status and HowTo"]]
 
-[[!template id=note text="[[!toc startlevel=1 levels=2]]"]]
+[[!template id=note text="[[!toc startlevel=0 levels=3]]"]]
 
 Xen is a Type 1 hypervisor which supports running multiple guest operating
 systems on a single physical machine. One uses the Xen kernel to control the

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.292
retrieving revision 1.293
diff -u -r1.292 -r1.293
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:14:03 -0000	1.292
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:19:43 -0000	1.293
@@ -1,6 +1,6 @@
 [[!meta title="Xen Status and HowTo"]]
 
-[[!template id=note text="[[!toc levels=2]]"]]
+[[!template id=note text="[[!toc startlevel=1 levels=2]]"]]
 
 Xen is a Type 1 hypervisor which supports running multiple guest operating
 systems on a single physical machine. One uses the Xen kernel to control the

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.44
retrieving revision 1.45
diff -u -r1.44 -r1.45
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 05:27:39 -0000	1.44
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 13:18:26 -0000	1.45
@@ -1,3 +1,5 @@
+[[!meta title="How to use file system snapshots in NetBSD"]]
+
 [[!template id=note text="[[!toc startlevel=3 levels=2]]"]]
 
 ### Overview

Members: 
	tutorials/kerberos_client.mdwn:1.13->1.14 
	tutorials/kerberos_realm.mdwn:1.16->1.17 
	tutorials/kerberos_services.mdwn:1.15->1.16 

Index: wikisrc/tutorials/kerberos_client.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/kerberos_client.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/tutorials/kerberos_client.mdwn	31 Jul 2026 04:28:49 -0000	1.13
+++ wikisrc/tutorials/kerberos_client.mdwn	31 Jul 2026 13:17:56 -0000	1.14
@@ -1,6 +1,6 @@
-[[!template id=note text="[[!toc startlevel=3 levels=2]]"]]
+[[!meta title="How to use Kerberos for single sign-on in a NetBSD client"]]
 
-## How to use Kerberos for single sign-on in a NetBSD client
+[[!template id=note text="[[!toc startlevel=3 levels=2]]"]]
 
 Your organization has a [[Kerberos|kerberos]] realm EXAMPLE.COM.
 You have a login password for the principal jruser@EXAMPLE.COM.
Index: wikisrc/tutorials/kerberos_realm.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/kerberos_realm.mdwn,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- wikisrc/tutorials/kerberos_realm.mdwn	31 Jul 2026 04:23:56 -0000	1.16
+++ wikisrc/tutorials/kerberos_realm.mdwn	31 Jul 2026 13:17:56 -0000	1.17
@@ -1,4 +1,4 @@
-## How to create a Kerberos realm for single sign-on running on NetBSD
+[[!meta title="How to create a Kerberos realm for single sign-on running on NetBSD"]]
 
 You want to organize your users and services into a
 [[Kerberos|kerberos]] realm to enable
Index: wikisrc/tutorials/kerberos_services.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/kerberos_services.mdwn,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -r1.15 -r1.16
--- wikisrc/tutorials/kerberos_services.mdwn	31 Jul 2026 12:56:39 -0000	1.15
+++ wikisrc/tutorials/kerberos_services.mdwn	31 Jul 2026 13:17:56 -0000	1.16
@@ -1,6 +1,6 @@
-[[!template id=note text="[[!toc startlevel=3 levels=1]]"]]
+[[!meta title="How to set up Kerberos authentication in network services"]]
 
-## How to set up Kerberos authentication in network services
+[[!template id=note text="[[!toc startlevel=3 levels=1]]"]]
 
 Your organization has a [[Kerberos|kerberos]] realm EXAMPLE.COM, or you
 [[set one up|tutorials/kerberos_realm]].

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.291
retrieving revision 1.292
diff -u -r1.291 -r1.292
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:11:51 -0000	1.291
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:14:03 -0000	1.292
@@ -1,5 +1,7 @@
 [[!meta title="Xen Status and HowTo"]]
 
+[[!template id=note text="[[!toc levels=2]]"]]
+
 Xen is a Type 1 hypervisor which supports running multiple guest operating
 systems on a single physical machine. One uses the Xen kernel to control the
 CPU, memory and console, a dom0 operating system which mediates access to
@@ -24,8 +26,6 @@
 See also an [earlier Xen tutorial](http://wiki.netbsd.org/tutorials/how_to_set_up_a_guest_os_using_xen3/)
 which should perhaps be folded into this HOWTO.
 
-[[!toc]]
-
 # Overview
 
 The basic concept of Xen is that the hypervisor (xenkernel) runs on
@@ -202,6 +202,8 @@
 [scripts to run the tests](https://ftp.netbsd.org/pub/NetBSD/misc/bouyer/nbsd-tests/)
 as a source of configuration hints.
 
+[[!template id=note text="[[!toc startlevel=2]]"]]
+
 # Creating a NetBSD dom0
 
 In order to install a NetBSD as a dom0, one first installs a normal

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.290
retrieving revision 1.291
diff -u -r1.290 -r1.291
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:10:53 -0000	1.290
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:11:51 -0000	1.291
@@ -1283,7 +1283,8 @@
 \# USB Mass Storage
 umass\*  at uhub? port ? configuration ? interface ?
 wd\*     at umass?
-# SCSI controllers
+<span></span>
+\# SCSI controllers
 ahc\*    at pci? dev ? function ?        # Adaptec [23]94x, aic78x0 SCSI
 <span></span>
 \# SCSI bus support (for both ahc and umass)

Members: 
	ports/xen/howto.mdwn:1.289->1.290 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.289
retrieving revision 1.290
diff -u -r1.289 -r1.290
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:09:32 -0000	1.289
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:10:53 -0000	1.290
@@ -339,15 +339,16 @@
 
 ### Selecting the console for the boot blocks
 
-See [[!template id=man name=boot_console section=8]].  Understand that
-you should start from a place of having the console setup correct for
-booting GENERIC before trying to configure Xen.
-
-Generally, one sets the console in bootxx_ffsv1 or equivalent, and
-this is passed on to `/boot` (where one typically does not set the
-console).  This configuration should also be in place for Xen systems,
-to allow seeing messages and typing to `/boot`.  It is necessary for
-proper booting of GENERIC as a rescue/fallback.
+See [[!template id=man name="x86/boot_console" section=8]].  Understand
+that you should start from a place of having the console setup correct
+for booting GENERIC before trying to configure Xen.
+
+Generally, one sets the console in bootxx_ffsv1 or equivalent with
+[[!template id=man name=installboot section=8]], and this is passed on
+to `/boot` (where one typically does not set the console).  This
+configuration should also be in place for Xen systems, to allow seeing
+messages and typing to `/boot`.  It is necessary for proper booting of
+GENERIC as a rescue/fallback.
 
 ### Selecting the console for Xen
 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.288
retrieving revision 1.289
diff -u -r1.288 -r1.289
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:06:51 -0000	1.288
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:09:32 -0000	1.289
@@ -304,13 +304,13 @@
 pseudo-device	xenevt
 pseudo-device	xvif
 pseudo-device	xbdback
-&newline;
+<span></span>
 \# Likely only necessary if you have these devices and booting with them crashes.
 no i915drmkms\*     at pci?
 no radeon\*         at pci?
 no nouveau\*        at pci?
 no options      DRM_LEGACY
-&newline;
+<span></span>
 no options DDB_COMMANDONENTER
 \#options DDB_COMMANDONENTER="trace"
 """]]
@@ -333,7 +333,7 @@
 (because it's faster), and thus:
 
 - DOM00PS and xenevt, xvif, and xbdback will be in GENERIC
-- XEN3_DOM* kernels will be non-preferred and perhaps not used much
+- XEN3_DOM\* kernels will be non-preferred and perhaps not used much
 
 \todo Validate that these instructions are correct, and that they work.
 
@@ -642,7 +642,7 @@
 
 ## Config files
 
-See /usr/pkg/share/examples/xen/xlexample* for a very small number of
+See /usr/pkg/share/examples/xen/xlexample\* for a very small number of
 examples for running GNU/Linux.
 
 The following is an example minimal domain configuration file.  The
@@ -692,7 +692,7 @@
 
 ## Logs
 
-Look in /var/log/xen/* for logs written at creation time.
+Look in /var/log/xen/\* for logs written at creation time.
 
 ## CPU and memory
 
@@ -1198,13 +1198,13 @@
            target=/dev/zvol/rdsk/tank/foo',
           'format=raw, vdev=hdc, access=ro,
            target=/n0/xen/iso/SW_DVD9_Win_Server_STD_CORE_2022_2108.6_64Bit_English_DC_STD_MLF_X23-03231.ISO' ]
-&newline;
+<span></span>
 vncdisplay=0
 vncpasswd="secret"
 vnclisten="0.0.0.0"
 keymap="en-gb"
 usbdevice = "tablet"
-&newline;
+<span></span>
 boot = "d"
 """]]
 
@@ -1268,26 +1268,26 @@
 # Add support for PCI buses to the XEN3_DOMU kernel
 xpci\* at xenbus ?
 pci\* at xpci ?
-&newline;
+<span></span>
 \# PCI USB controllers
 uhci\*   at pci? dev ? function ?        # Universal Host Controller (Intel)
-&newline;
+<span></span>
 \# USB bus support
 usb\*    at uhci?
-&newline;
+<span></span>
 \# USB Hubs
 uhub\*   at usb?
 uhub\*   at uhub? port ? configuration ? interface ?
-&newline;
+<span></span>
 \# USB Mass Storage
 umass\*  at uhub? port ? configuration ? interface ?
 wd\*     at umass?
 # SCSI controllers
 ahc\*    at pci? dev ? function ?        # Adaptec [23]94x, aic78x0 SCSI
-&newline;
+<span></span>
 \# SCSI bus support (for both ahc and umass)
 scsibus\* at scsi?
-&newline;
+<span></span>
 \# SCSI devices
 sd\*     at scsibus? target ? lun ?      # SCSI disk drives
 cd\*     at scsibus? target ? lun ?      # SCSI CD-ROM drives

`<' -> `&lt;'
`*' -> `\*'

Members: 
	ports/xen/howto.mdwn:1.287->1.288 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.287
retrieving revision 1.288
diff -u -r1.287 -r1.288
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:01:03 -0000	1.287
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:06:51 -0000	1.288
@@ -304,22 +304,22 @@
 pseudo-device	xenevt
 pseudo-device	xvif
 pseudo-device	xbdback
-&#32;
+&newline;
 \# Likely only necessary if you have these devices and booting with them crashes.
-no i915drmkms*     at pci?
-no radeon*         at pci?
-no nouveau*        at pci?
+no i915drmkms\*     at pci?
+no radeon\*         at pci?
+no nouveau\*        at pci?
 no options      DRM_LEGACY
-&#32;
+&newline;
 no options DDB_COMMANDONENTER
 \#options DDB_COMMANDONENTER="trace"
 """]]
 
 As an alternative to disabling graphic devices in the kernel, add to /boot.cfg:
 [[!template id=filecontent name="/boot.cfg" text="""
-userconf=disable i915drmkms*
-userconf=disable nouveau*
-userconf=disable radeon*
+userconf=disable i915drmkms\*
+userconf=disable nouveau\*
+userconf=disable radeon\*
 """]]
 
 Then, create a copy of the boot line, adding `dom0=pvh` near
@@ -366,7 +366,7 @@
 
 When Xen uses a serial console, it manages the serial port and, after
 booting, forwards it it to the dom0's xencons(4) device.  An exception
-is that when Xen receives the "comswitch" character (<CTRL-A> by
+is that when Xen receives the "comswitch" character (&lt;CTRL-A> by
 default) three times in quick succession, it will take over serial I/O
 until three more presses.  Xen console interactions can be used for
 various debugging features which are not usually present in the
@@ -1083,7 +1083,7 @@
 wdc1 at isa0 port 0x170-0x177 irq 15
 atabus0 at wdc1 channel 0
 atapibus0 at atabus0: 2 targets
-cd0 at atapibus0 drive 0: <QEMU DVD-ROM, QM00003, 2.5+> cdrom removable
+cd0 at atapibus0 drive 0: &lt;QEMU DVD-ROM, QM00003, 2.5+> cdrom removable
 cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
 """]]
 
@@ -1091,7 +1091,7 @@
 wdc0 at isa0 port 0x1f0-0x1f7 irq 14
 atabus0 at wdc0 channel 0
 wd0 at atabus0 drive 0
-wd0: <ST506>
+wd0: &lt;ST506>
 wd0: drive supports 1-sector PIO transfers, chs addressing
 wd0: 69632 KB, 1024 cyl, 8 head, 17 sec, 512 bytes/sect x 139264 sectors
 """]]
@@ -1147,7 +1147,7 @@
 """]]
 
 does matter to Linux. It wants a Linux device number here (e.g. 0x300
-for hda).  Linux builds device numbers as: (major << 8 + minor).
+for hda).  Linux builds device numbers as: (major &lt;&lt; 8 + minor).
 So, hda1 which has major 3 and minor 1 on a Linux system will have
 device number 0x301.  Alternatively, devices names can be used (hda,
 hdb, ...)  as xentools has a table to map these names to devices
@@ -1198,13 +1198,13 @@
            target=/dev/zvol/rdsk/tank/foo',
           'format=raw, vdev=hdc, access=ro,
            target=/n0/xen/iso/SW_DVD9_Win_Server_STD_CORE_2022_2108.6_64Bit_English_DC_STD_MLF_X23-03231.ISO' ]
-&#32;
+&newline;
 vncdisplay=0
 vncpasswd="secret"
 vnclisten="0.0.0.0"
 keymap="en-gb"
 usbdevice = "tablet"
-&#32;
+&newline;
 boot = "d"
 """]]
 
@@ -1266,31 +1266,31 @@
 
 [[!template id=filecontent name="XEN3_DOMU.local" text="""
 # Add support for PCI buses to the XEN3_DOMU kernel
-xpci* at xenbus ?
-pci* at xpci ?
-&#32;
+xpci\* at xenbus ?
+pci\* at xpci ?
+&newline;
 \# PCI USB controllers
-uhci*   at pci? dev ? function ?        # Universal Host Controller (Intel)
-&#32;
+uhci\*   at pci? dev ? function ?        # Universal Host Controller (Intel)
+&newline;
 \# USB bus support
-usb*    at uhci?
-&#32;
+usb\*    at uhci?
+&newline;
 \# USB Hubs
-uhub*   at usb?
-uhub*   at uhub? port ? configuration ? interface ?
-&#32;
+uhub\*   at usb?
+uhub\*   at uhub? port ? configuration ? interface ?
+&newline;
 \# USB Mass Storage
-umass*  at uhub? port ? configuration ? interface ?
-wd*     at umass?
+umass\*  at uhub? port ? configuration ? interface ?
+wd\*     at umass?
 # SCSI controllers
-ahc*    at pci? dev ? function ?        # Adaptec [23]94x, aic78x0 SCSI
-&#32;
+ahc\*    at pci? dev ? function ?        # Adaptec [23]94x, aic78x0 SCSI
+&newline;
 \# SCSI bus support (for both ahc and umass)
-scsibus* at scsi?
-&#32;
+scsibus\* at scsi?
+&newline;
 \# SCSI devices
-sd*     at scsibus? target ? lun ?      # SCSI disk drives
-cd*     at scsibus? target ? lun ?      # SCSI CD-ROM drives
+sd\*     at scsibus? target ? lun ?      # SCSI disk drives
+cd\*     at scsibus? target ? lun ?      # SCSI CD-ROM drives
 """]]
 
 # Miscellaneous Information

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.286
retrieving revision 1.287
diff -u -r1.286 -r1.287
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 12:50:18 -0000	1.286
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 13:01:03 -0000	1.287
@@ -304,13 +304,13 @@
 pseudo-device	xenevt
 pseudo-device	xvif
 pseudo-device	xbdback
- 
+ 
 \# Likely only necessary if you have these devices and booting with them crashes.
 no i915drmkms*     at pci?
 no radeon*         at pci?
 no nouveau*        at pci?
 no options      DRM_LEGACY
- 
+ 
 no options DDB_COMMANDONENTER
 \#options DDB_COMMANDONENTER="trace"
 """]]
@@ -1198,13 +1198,13 @@
            target=/dev/zvol/rdsk/tank/foo',
           'format=raw, vdev=hdc, access=ro,
            target=/n0/xen/iso/SW_DVD9_Win_Server_STD_CORE_2022_2108.6_64Bit_English_DC_STD_MLF_X23-03231.ISO' ]
-\ 
+ 
 vncdisplay=0
 vncpasswd="secret"
 vnclisten="0.0.0.0"
 keymap="en-gb"
 usbdevice = "tablet"
-\ 
+ 
 boot = "d"
 """]]
 
@@ -1268,26 +1268,26 @@
 # Add support for PCI buses to the XEN3_DOMU kernel
 xpci* at xenbus ?
 pci* at xpci ?
-\ 
+ 
 \# PCI USB controllers
 uhci*   at pci? dev ? function ?        # Universal Host Controller (Intel)
-\ 
+ 
 \# USB bus support
 usb*    at uhci?
-\ 
+ 
 \# USB Hubs
 uhub*   at usb?
 uhub*   at uhub? port ? configuration ? interface ?
-\ 
+ 
 \# USB Mass Storage
 umass*  at uhub? port ? configuration ? interface ?
 wd*     at umass?
 # SCSI controllers
 ahc*    at pci? dev ? function ?        # Adaptec [23]94x, aic78x0 SCSI
-\ 
+ 
 \# SCSI bus support (for both ahc and umass)
 scsibus* at scsi?
-\ 
+ 
 \# SCSI devices
 sd*     at scsibus? target ? lun ?      # SCSI disk drives
 cd*     at scsibus? target ? lun ?      # SCSI CD-ROM drives

Members: 
	tutorials/kerberos_services.mdwn:1.14->1.15 

Index: wikisrc/tutorials/kerberos_services.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/kerberos_services.mdwn,v
retrieving revision 1.14
retrieving revision 1.15
diff -u -r1.14 -r1.15
--- wikisrc/tutorials/kerberos_services.mdwn	31 Jul 2026 04:28:49 -0000	1.14
+++ wikisrc/tutorials/kerberos_services.mdwn	31 Jul 2026 12:56:39 -0000	1.15
@@ -24,9 +24,9 @@
    realm name).
 
 2. **Get a keytab for the service principal** from the Kerberos KDC
-   using [[!template id=man name="kadmin" section="8"]]:
-   first `kadmin add` to generate a key for the service principal in
-   the KDC database, and then `kadmin ext` to extract it into a keytab.
+   using [[!template id=man name="kadmin" section="8"]] commands:
+   first “`add`” to generate a key for the service principal in the KDC
+   database, and then “`ext`” to extract it into a keytab.
 
    The key is a secret shared between the service and the KDC.
    Anyone who knows the key can spoof the service, so you must keep
@@ -34,8 +34,8 @@
 
    You can run
    [[!template id=man name="kadmin" section="8"]]
-   on the KDC itself with `kadmin -l` (`kadmin --local`), or you can
-   configure
+   on the KDC itself with “`kadmin -l`”
+   (“`kadmin --local`”), or you can configure
    [[!template id=man name="kadmind" section="8"]]
    on the KDC and run
    [[!template id=man name="kadmin" section="8"]]
@@ -78,20 +78,16 @@
    keytab:
 
    [[!template id=programlisting text="""
-# kadmin add --random-key --max-ticket-life=unlimited \
-       --max-renewable-life=unlimited --use-defaults \
-       imap/imap.example.com
-# kadmin add --random-key --max-ticket-life=unlimited \
-       --max-renewable-life=unlimited --use-defaults \
-       pop/pop.example.com
-# kadmin add --random-key --max-ticket-life=unlimited \
-       --max-renewable-life=unlimited --use-defaults \
-       smtp/mail.example.com
 # mkdir -m 0700 /usr/pkg/etc/dovecot/private
 # cd /usr/pkg/etc/dovecot/private
-# kadmin ext -k keytab imap/imap.example.com
-# kadmin ext -k keytab pop/pop.example.com
-# kadmin ext -k keytab smtp/mail.example.com
+# kadmin
+kadmin> add --random-key --max-ticket-life=unlimited --max-renewable-life=unlimited --use-defaults imap/imap.example.com
+kadmin> add --random-key --max-ticket-life=unlimited --max-renewable-life=unlimited --use-defaults pop/pop.example.com
+kadmin> add --random-key --max-ticket-life=unlimited --max-renewable-life=unlimited --use-defaults smtp/mail.example.com
+kadmin> ext -k keytab imap/imap.example.com
+kadmin> ext -k keytab pop/pop.example.com
+kadmin> ext -k keytab smtp/mail.example.com
+kadmin> ^D
 # chown dovecot:dovecot . keytab
 """]]
 
@@ -129,7 +125,7 @@
 [[!template id=filecontent name="/usr/pkg/etc/dovecot/local.conf" text="""
 protocols =
 service auth {
-    unix_listener /var/spool/postfix/private/auth {
+    unix_listener /var/spool/postfix/private/dovecot-auth {
         mode = 0660
         user = postfix
         group = postfix
@@ -147,7 +143,7 @@
    ([[!template id=man name="postconf" section="5"]]):
 
    [[!template id=filecontent name="/etc/postfix/main.cf" text="""
-smtpd_sasl_path = private/auth
+smtpd_sasl_path = private/dovecot-auth
 smtpd_sasl_type = dovecot
 """]]
 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.285
retrieving revision 1.286
diff -u -r1.285 -r1.286
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 12:46:29 -0000	1.285
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 12:50:18 -0000	1.286
@@ -304,15 +304,15 @@
 pseudo-device	xenevt
 pseudo-device	xvif
 pseudo-device	xbdback
-
-# Likely only necessary if you have these devices and booting with them crashes.
+ 
+\# Likely only necessary if you have these devices and booting with them crashes.
 no i915drmkms*     at pci?
 no radeon*         at pci?
 no nouveau*        at pci?
 no options      DRM_LEGACY
-
+ 
 no options DDB_COMMANDONENTER
-#options DDB_COMMANDONENTER="trace"
+\#options DDB_COMMANDONENTER="trace"
 """]]
 
 As an alternative to disabling graphic devices in the kernel, add to /boot.cfg:
@@ -1198,13 +1198,13 @@
            target=/dev/zvol/rdsk/tank/foo',
           'format=raw, vdev=hdc, access=ro,
            target=/n0/xen/iso/SW_DVD9_Win_Server_STD_CORE_2022_2108.6_64Bit_English_DC_STD_MLF_X23-03231.ISO' ]
- 
+\ 
 vncdisplay=0
 vncpasswd="secret"
 vnclisten="0.0.0.0"
 keymap="en-gb"
 usbdevice = "tablet"
- 
+\ 
 boot = "d"
 """]]
 
@@ -1268,26 +1268,26 @@
 # Add support for PCI buses to the XEN3_DOMU kernel
 xpci* at xenbus ?
 pci* at xpci ?
- 
+\ 
 \# PCI USB controllers
 uhci*   at pci? dev ? function ?        # Universal Host Controller (Intel)
- 
+\ 
 \# USB bus support
 usb*    at uhci?
- 
+\ 
 \# USB Hubs
 uhub*   at usb?
 uhub*   at uhub? port ? configuration ? interface ?
- 
+\ 
 \# USB Mass Storage
 umass*  at uhub? port ? configuration ? interface ?
 wd*     at umass?
 # SCSI controllers
 ahc*    at pci? dev ? function ?        # Adaptec [23]94x, aic78x0 SCSI
- 
+\ 
 \# SCSI bus support (for both ahc and umass)
 scsibus* at scsi?
- 
+\ 
 \# SCSI devices
 sd*     at scsibus? target ? lun ?      # SCSI disk drives
 cd*     at scsibus? target ? lun ?      # SCSI CD-ROM drives

Members: 
	ports/xen/howto.mdwn:1.284->1.285 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.284
retrieving revision 1.285
diff -u -r1.284 -r1.285
--- wikisrc/ports/xen/howto.mdwn	31 Jul 2026 12:40:31 -0000	1.284
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 12:46:29 -0000	1.285
@@ -782,7 +782,7 @@
 [[!template id=filecontent name="/usr/pkg/etc/xen/foo" text="""
 # Newer key/value format:
 disk = [ 'format=raw, vdev=hdc, devtype=cdrom, access=ro, target=/n0/xen/iso/NetBSD-10.1_STABLE-amd64.iso' ]
-# Older positional format:
+\# Older positional format:
 disk = [ 'file:/n0/xen/iso/NetBSD-10.1_STABLE-amd64.iso,hdc:cdrom,r' ]
 """]]
 
@@ -1198,13 +1198,13 @@
            target=/dev/zvol/rdsk/tank/foo',
           'format=raw, vdev=hdc, access=ro,
            target=/n0/xen/iso/SW_DVD9_Win_Server_STD_CORE_2022_2108.6_64Bit_English_DC_STD_MLF_X23-03231.ISO' ]
-
+ 
 vncdisplay=0
 vncpasswd="secret"
 vnclisten="0.0.0.0"
 keymap="en-gb"
 usbdevice = "tablet"
-
+ 
 boot = "d"
 """]]
 
@@ -1268,27 +1268,27 @@
 # Add support for PCI buses to the XEN3_DOMU kernel
 xpci* at xenbus ?
 pci* at xpci ?
-
-# PCI USB controllers
+ 
+\# PCI USB controllers
 uhci*   at pci? dev ? function ?        # Universal Host Controller (Intel)
-
-# USB bus support
+ 
+\# USB bus support
 usb*    at uhci?
-
-# USB Hubs
+ 
+\# USB Hubs
 uhub*   at usb?
 uhub*   at uhub? port ? configuration ? interface ?
-
-# USB Mass Storage
+ 
+\# USB Mass Storage
 umass*  at uhub? port ? configuration ? interface ?
 wd*     at umass?
 # SCSI controllers
 ahc*    at pci? dev ? function ?        # Adaptec [23]94x, aic78x0 SCSI
-
-# SCSI bus support (for both ahc and umass)
+ 
+\# SCSI bus support (for both ahc and umass)
 scsibus* at scsi?
-
-# SCSI devices
+ 
+\# SCSI devices
 sd*     at scsibus? target ? lun ?      # SCSI disk drives
 cd*     at scsibus? target ? lun ?      # SCSI CD-ROM drives
 """]]

Members: 
	ports/xen/howto.mdwn:1.283->1.284 

Index: wikisrc/ports/xen/howto.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/ports/xen/howto.mdwn,v
retrieving revision 1.283
retrieving revision 1.284
diff -u -r1.283 -r1.284
--- wikisrc/ports/xen/howto.mdwn	22 Jul 2026 11:32:05 -0000	1.283
+++ wikisrc/ports/xen/howto.mdwn	31 Jul 2026 12:40:31 -0000	1.284
@@ -246,9 +246,10 @@
 options](https://xenbits.xenproject.org/docs/4.18-testing/misc/xen-command-line.html)
 documentation.
 
-Read boot.cfg(8) carefully.  Add lines to /boot.cfg to boot Xen,
-adjusting for your root filesystem (if you installed with GPT partitioning,
-your root filesystem is likely to be /dev/dk0):
+Read [[!template id=man name="boot.cfg" section=8]] carefully.  Add
+lines to `/boot.cfg` to boot Xen, adjusting for your root filesystem
+(if you installed with GPT partitioning, your root filesystem is likely
+to be `/dev/dk0`):
 
 [[!template id=filecontent name="/boot.cfg" text="""
 menu=Xen:load /netbsd-XEN3_DOM0.gz rndseed=/var/db/entropy-file bootdev=wd0a console=pc;multiboot /xen.gz dom0_mem=1024M
@@ -282,8 +283,8 @@
 
 A PVH dom0 is currently experimental, as of Xen 4.18.  For 4.19 and
 later, not yet in pkgsrc, it is
-[supported](https://xenbits.xen.org/docs/unstable/support-matrix.html
-) with
+[supported](https://xenbits.xen.org/docs/unstable/support-matrix.html)
+with
 [caveats](https://xenbits.xen.org/docs/4.19-testing/SUPPORT.html#x86pvh),
 notably that SR-IOV is missing and PCI passthrough does not work.
 
@@ -298,7 +299,7 @@
 Prepare a GENERIC kernel with the additions necessary to be a DOM0,
 which consists of code to deal with DOM0 requests, and PV drivers for
 the dom0 part of events, network interfaces, and disks.
-[[!template id=programlisting text="""
+[[!template id=filecontent name="GENERIC.local" text="""
 options		DOM0OPS
 pseudo-device	xenevt
 pseudo-device	xvif
@@ -315,7 +316,7 @@
 """]]
 
 As an alternative to disabling graphic devices in the kernel, add to /boot.cfg:
-[[!template id=programlisting text="""
+[[!template id=filecontent name="/boot.cfg" text="""
 userconf=disable i915drmkms*
 userconf=disable nouveau*
 userconf=disable radeon*
@@ -329,22 +330,23 @@
 fine on bare metal and, if not, it's a bug -- but so far we have no
 reports either way.  In the glorious future, it will be normal to run
 a dom0 as PVH (because it's faster), and to run a domU as PVH or PVHVM
-(because it's faster), and thus: - DOM00PS and xenevt, xvif, and
-xbdback will be in GENERIC - XEN3_DOM* kernels will be non-preferred
-and perhaps not used much
+(because it's faster), and thus:
+
+- DOM00PS and xenevt, xvif, and xbdback will be in GENERIC
+- XEN3_DOM* kernels will be non-preferred and perhaps not used much
 
 \todo Validate that these instructions are correct, and that they work.
 
 ### Selecting the console for the boot blocks
 
-See boot_console(8).  Understand that you should start from a place of
-having the console setup correct for booting GENERIC before trying to
-configure Xen.
+See [[!template id=man name=boot_console section=8]].  Understand that
+you should start from a place of having the console setup correct for
+booting GENERIC before trying to configure Xen.
 
 Generally, one sets the console in bootxx_ffsv1 or equivalent, and
-this is passed on to /boot (where one typically does not set the
+this is passed on to `/boot` (where one typically does not set the
 console).  This configuration should also be in place for Xen systems,
-to allow seeing messages and typing to /boot.  It is necessary for
+to allow seeing messages and typing to `/boot`.  It is necessary for
 proper booting of GENERIC as a rescue/fallback.
 
 ### Selecting the console for Xen
@@ -368,7 +370,7 @@
 default) three times in quick succession, it will take over serial I/O
 until three more presses.  Xen console interactions can be used for
 various debugging features which are not usually present in the
-default /xen kernel (the xenkernel package also includes a xen-debug kernel).
+default `/xen` kernel (the xenkernel package also includes a xen-debug kernel).
 
 When Xen uses vga as a console, the vga console is relinquished at the
 conclusion of hypervisor boot, before the dom0 is started.  See also
@@ -380,16 +382,17 @@
 menu=Xen:load /netbsd-XEN3_DOM0.gz rndseed=/var/db/entropy-file bootdev=sd0; multiboot /xen.gz dom0_mem=1024M console=com1
 """]]
 
-On Xen's console, one can type the escape character (default ^A) three
-times to switch input from Xen to the dom0.  (See ddb(4) for how to
-get into DDB, which differs from non-Xen amd64.)
+On Xen's console, one can type the escape character (default `^A`)
+three times to switch input from Xen to the dom0.  (See
+[[!template id=man name=ddb section=4]] for how to get into DDB, which
+differs from non-Xen amd64.)
 \todo Xen's vga console is probably output only, but this needs clarifying.
 
 The default serial console speed may depend on whether the whether the
 bootloader or earlier firmware has already set it up. To be certain,
 the desired speed can be specified with the com1= boot command. For example,
 the following configures use of serial console with the speed explicitly
-set to 115200
+set to 115200:
 [[!template id=filecontent name="/boot.cfg" text="""
 menu=Xen:load /netbsd-XEN3_DOM0.gz rndseed=/var/db/entropy-file bootdev=sd0; multiboot /xen.gz dom0_mem=1024M console=com1 com1=115200,8n1
 """]]
@@ -659,9 +662,10 @@
 various domUs independently.  The `vif` line causes an interface to be
 provided, with a specific mac address (do not reuse MAC addresses!),
 in bridge mode.  Two disks are provided, and they are both writable;
-the bits are stored in files and Xen attaches them to a vnd(4) device
-in the dom0 on domain creation.  The system treats xbd0 as the boot
-device without needing explicit configuration.
+the bits are stored in files and Xen attaches them to a
+[[!template id=man name=vnd section=4]] device in the dom0 on domain
+creation.  The system treats xbd0 as the boot device without needing
+explicit configuration.
 
 There is not a type line; that implicitly defines a pv domU.
 Otherwise, one sets type to the lower-case version of the domU type in
@@ -735,7 +739,7 @@
 """]]
 
 The vdev field can be 0x0 in PV mode but must be something like
-hda in HVM mode. Leaving as 0x0 will generate a warning such as 
+hda in HVM mode. Leaving as 0x0 will generate a warning such as
 'unable to determine disk number for 0x0'
 
 For key-value pairs:
@@ -866,9 +870,9 @@
 See [Xen's Booting Overview](https://wiki.xenproject.org/wiki/Booting_Overview).
 and the more detailed [pvgrub2 page](https://wiki.xenproject.org/wiki/PvGrub2).
 
-See [Debian's pvgrub page](https://wiki.debian.org/PvGrub). 
+See [Debian's pvgrub page](https://wiki.debian.org/PvGrub).
 
-For information about how specific provider's address booting,  
+For information about how specific provider's address booting,
 see the sections below about Panix and Tornado VPS.
 See also [Bitfolk's Booting page](https://tools.bitfolk.com/wiki/Booting).
 
@@ -903,8 +907,8 @@
 The kernel must be specifically built for Xen, to use PV interfaces as
 a domU.  NetBSD release builds provide the following kernels:
 
-        i386 XEN3PAE_DOMU
-        amd64 XEN3_DOMU
+- i386: XEN3PAE_DOMU
+- amd64: XEN3_DOMU
 
 This will boot NetBSD, but this is not that useful if the disk is
 empty.  One approach is to unpack sets onto the disk outside of Xen
@@ -915,14 +919,18 @@
 and can load sets from the network.  To do this, copy the INSTALL
 kernel to / and change the kernel line in the config file to:
 
-        kernel = "/netbsd-INSTALL_XEN3_DOMU"
+[[!template id=filecontent name="/usr/pkg/etc/xen/foo" text="""
+kernel = "/netbsd-INSTALL_XEN3_DOMU"
+"""]]
 
-Then, start the domain as "xl create -c configfile".
+Then, start the domain as "xl create -c foo".
 
 Alternatively, if you want to install NetBSD/Xen with a physical
 CDROM, the following line should be used in the config file.
 
-    disk = [ 'phy:/dev/wd0e,0x1,w', 'phy:/dev/cd0a,0x2,r' ]
+[[!template id=filecontent name="/usr/pkg/etc/xen/foo" text="""
+disk = [ 'phy:/dev/wd0e,0x1,w', 'phy:/dev/cd0a,0x2,r' ]
+"""]]
 
 After booting the domain, the option to install via CDROM may be
 selected.  The CDROM device should be changed to `xbd1d`.
@@ -939,11 +947,13 @@
 `/etc/ttys` and `/etc/wscons.conf`. You must disable all terminals in
 `/etc/ttys`, except *console*, like this:
 
-    console "/usr/libexec/getty Pc"         vt100   on secure
-    ttyE0   "/usr/libexec/getty Pc"         vt220   off secure
-    ttyE1   "/usr/libexec/getty Pc"         vt220   off secure
-    ttyE2   "/usr/libexec/getty Pc"         vt220   off secure
-    ttyE3   "/usr/libexec/getty Pc"         vt220   off secure
+[[!template id=filecontent name="/etc/ttys" text="""
+console "/usr/libexec/getty Pc"         vt100   on secure
+ttyE0   "/usr/libexec/getty Pc"         vt220   off secure
+ttyE1   "/usr/libexec/getty Pc"         vt220   off secure
+ttyE2   "/usr/libexec/getty Pc"         vt220   off secure
+ttyE3   "/usr/libexec/getty Pc"         vt220   off secure

(Diff truncated)

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.43
retrieving revision 1.44
diff -u -r1.43 -r1.44
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 05:22:47 -0000	1.43
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 05:27:39 -0000	1.44
@@ -308,19 +308,6 @@
   content of the snapshot.  The content can later be restored with the
   [[!template id=man name=restore section=8]] tool.
 
-  By default, any user in the “`operator`” group (see
-  [[!template id=man name=groups]]) can configure snapshots, read disk
-  devices, and write to tape devices to take backups—this way
-  backups can be taken without root privileges.  However, since
-  “`dump -X ... /fs`” requires creating a snapshot backing
-  store at `/fs/<tempfile>`, running command such as
-  &ldquo;`dump -X ... /`&rdquo; or &ldquo;`dump -X ... /usr`&rdquo;
-  unprivileged will fail because `/` and `/usr` are writable only by
-  root.  Instead, you can create a directory `/operator` that group
-  &ldquo;`operator`&rdquo; can write to, and use
-  &ldquo;`dump -x /operator/ ... /`&rdquo; to create the snapshot file
-  for `/` at `/operator/<tempfile>`.
-
 - **For lfs**, the [[!template id=man name=dump_lfs section=8]] tool
   supports an option &ldquo;`-X`&rdquo; to dump a snapshot of the file
   system.  (However, lfs does not support persistent snapshots, nor
@@ -347,6 +334,24 @@
 
 These tools can be used on any mounted snapshot.
 
+#### Unprivileged snapshots and backups
+
+By default, any user in the &ldquo;`operator`&rdquo; group (see
+[[!template id=man name=groups section=7]]) can configure
+[[!template id=man name=fss section=4]] snapshots, read disk devices,
+and write to tape devices to take backups&mdash;this way backups can be
+taken without root privileges, at least for some file systems like ffs
+and lfs.
+
+However, since &ldquo;`dump -X ... /fs`&rdquo; requires creating a
+snapshot backing store at `/fs/<tempfile>`, running commands such as
+&ldquo;`dump -X ... /`&rdquo; or &ldquo;`dump -X ... /usr`&rdquo;
+unprivileged will fail because `/` and `/usr` are writable only by
+root.  Instead, you can create a directory `/operator` that group
+&ldquo;`operator`&rdquo; can write to, and use
+&ldquo;`dump -x /operator/ ... /`&rdquo; to create the snapshot file
+for `/` at `/operator/<tempfile>`.
+
 #### Example: tar
 
 Mount a persistent snapshot of `/home` and back it up with

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -r1.42 -r1.43
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 04:53:58 -0000	1.42
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 05:22:47 -0000	1.43
@@ -18,9 +18,12 @@
 of an ffs file system will use a snapshot with the “`-X`”
 or &ldquo;`-x <snapstore>`&rdquo; options to ensure that files such as
 sqlite3 databases aren't concurrently modified while it is trying to
-read them.  Snapshots can also be mounted like regular file systems to
-give read-only views of past states of file systems.  (See [caveat
-about incremental backups and mtimes](#caveat-mtime), though.)
+read them; without snapshots, such files can be backed up reliably only
+with application-specific cooperation like [sqlite3
+backup](https://sqlite.org/backup.html).  Snapshots can also be mounted
+like regular file systems to give read-only views of past states of
+file systems.  (See [caveat about incremental backups and
+mtimes](#caveat-mtime), though.)
 
 On some file systems&mdash;ffs and zfs&mdash;snapshots can be
 **persistent**: you can take a snapshot, stored in the file system
@@ -383,7 +386,7 @@
 haven't changed the last time.  The &ldquo;`--snaptime`&rdquo; argument
 gives a file whose ctime must predate the snapshot; see
 [caveat about mtime](#caveat-mtime) below for why this is necessary to
-avoid losing data in later incremental backups.
+avoid data loss in later incremental backups.
 
 #### Example: borgbackup
 
@@ -397,7 +400,7 @@
 """]]
 
 **WARNING: If used to take incremental backups, this may be vulnerable
-to a race condition with mtime checks; see
+to data loss with naive mtime checks; see
 [caveat about mtime](#caveat-mtime) below.**
 
 #### Example: rsync
@@ -420,35 +423,44 @@
 while the snapshot is active, and then discard it as soon as it is
 unconfigured.
 
-**WARNING: If used to take incremental backups, this may be vulnerable
-to a race condition with mtime checks; see
-[caveat about mtime](#caveat-mtime) below.**
+**WARNING: This may be vulnerable to data loss with naive mtime checks;
+see [caveat about mtime](#caveat-mtime) below.**
 
 <a name="caveat-mtime"></a>
 ### Caveat: Incremental backups and mtimes
 
-An incremental backup tool such as tarsnap, borg, or rsync which backs
-up the snapshot and records mtimes to avoid reprocessing unchanged
-files the next time around may have a subtle race condition that can
-lead to data loss if you are not careful.  Suppose:
+Some incremental backup tools such as tarsnap, borg, or rsync will
+record the mtimes of files they have backed up to avoid reprocessing
+unchanged files the next time around.  Although backing up a snapshot
+rather than the live file system avoids writing corrupted live
+application data into the backup (at least from applications that can
+recover from interruption), mtime-based incremental backups may have a
+subtle race condition that can lead to data loss if you are not
+careful.
+
+Suppose:
 
 1. A file is modified at time *t* + 0.1sec.
-2. The snapshot is taken at time *t* + 0.2sec and backed up.
+2. A snapshot is taken at time *t* + 0.2sec and backed up.
 3. The file is modified again at time *t* + 0.3sec.
 
 In this case, the file's mtime before the snapshot and after the
-snapshot may both be rounded down by the tool to just a number of
-seconds *t* since the epoch.  **The next time the tool runs, it may
-conclude the file was unchanged since the last run, and *lose the second
-modification*.**
+snapshot may both be rounded down&mdash;whether by the file system, by
+the backup tool, or by the backup archive format&mdash;to just a number
+of seconds *t* since the epoch.  **The next time the tool runs, it may
+conclude the file was unchanged since the last run, and *lose the
+second modification*.**  (Of course, in this scenario, trying to back
+up the live file system instead of a snapshot may lead to the even
+worse outcome of storing a corrupted file with some garbled mixture of
+the modifications instead!)
 
 The tarsnap
 &ldquo;[`--snaptime <reference>`](https://www.tarsnap.com/snaptime.html)&rdquo;
 option avoids this problem by treating any file with an mtime equal
 to or newer than the ctime *t* of `<reference>` as if it had an mtime
 of *t* &minus; 1 when comparing mtimes on the next run.  Other backup
-tools may have&mdash;or may need&mdash;similar options to reliably take
-incremental backups with snapshots.
+tools may have&mdash;or may not have, but may need!&mdash;similar
+options to reliably take incremental backups.
 
 The [[!template id=man name="dump" section="8"]] options
 &ldquo;`-X`&rdquo; and &ldquo;`-x <snapstore>`&rdquo; also avoid this

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 04:49:58 -0000	1.41
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 04:53:58 -0000	1.42
@@ -19,8 +19,8 @@
 or &ldquo;`-x <snapstore>`&rdquo; options to ensure that files such as
 sqlite3 databases aren't concurrently modified while it is trying to
 read them.  Snapshots can also be mounted like regular file systems to
-give read-only views of past states of file systems.  (See [caveats
-about taking incremental backups and mtimes](#caveat-mtime), though.)
+give read-only views of past states of file systems.  (See [caveat
+about incremental backups and mtimes](#caveat-mtime), though.)
 
 On some file systems&mdash;ffs and zfs&mdash;snapshots can be
 **persistent**: you can take a snapshot, stored in the file system
@@ -381,8 +381,9 @@
 Tarsnap takes incremental backups and caches the mtimes of files each
 time it runs in order to avoid spending time processing files that
 haven't changed the last time.  The &ldquo;`--snaptime`&rdquo; argument
-gives a file whose ctime must predate the snapshot; see below for why
-this is necessary to avoid losing data in later incremental backups.
+gives a file whose ctime must predate the snapshot; see
+[caveat about mtime](#caveat-mtime) below for why this is necessary to
+avoid losing data in later incremental backups.
 
 #### Example: borgbackup
 
@@ -396,7 +397,8 @@
 """]]
 
 **WARNING: If used to take incremental backups, this may be vulnerable
-to a race condition with mtime checks; see below.**
+to a race condition with mtime checks; see
+[caveat about mtime](#caveat-mtime) below.**
 
 #### Example: rsync
 
@@ -419,14 +421,16 @@
 unconfigured.
 
 **WARNING: If used to take incremental backups, this may be vulnerable
-to a race condition with mtime checks; see below.**
+to a race condition with mtime checks; see
+[caveat about mtime](#caveat-mtime) below.**
 
 <a name="caveat-mtime"></a>
 ### Caveat: Incremental backups and mtimes
 
 An incremental backup tool such as tarsnap, borg, or rsync which backs
 up the snapshot and records mtimes to avoid reprocessing unchanged
-files the next time around may have a subtle race condition.  Suppose:
+files the next time around may have a subtle race condition that can
+lead to data loss if you are not careful.  Suppose:
 
 1. A file is modified at time *t* + 0.1sec.
 2. The snapshot is taken at time *t* + 0.2sec and backed up.

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 04:46:42 -0000	1.40
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 04:49:58 -0000	1.41
@@ -266,8 +266,9 @@
 **WARNING: If you enter the command before you finished typing, you
 might accidentally destroy the file system instead of just a
 snapshot!**
-[[!template id=man name=zfs section=8]] uses the same “`zfs
-destroy`” for destroying file systems, zvols, and snapshots.
+[[!template id=man name=zfs section=8]] uses the same
+“`zfs destroy`” command for destroying file systems, zvols,
+and snapshots.
 
 One technique to avoid this mistake is to start by typing
 “`xxxzfs`” instead of “`zfs`” so if you enter
@@ -280,7 +281,7 @@
 -sh: xxxzfs: not found
 """]]
 
-Or start by typing “`echo zfs`&rdqou; instead of
+Or start by typing “`echo zfs`” instead of
 “`zfs`”, or use “`zfs destroy -n`”, especially
 if you are running a loop over many different snapshot names, to review
 what you *would* do.

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -r1.39 -r1.40
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 04:43:42 -0000	1.39
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 04:46:42 -0000	1.40
@@ -65,10 +65,10 @@
 # mount /dev/fss0 /home/.snap/20260706
 """]]
 
-Users can then browse their home directories in `/home/.snap` as they
-existed at the time the snapshot was taken.  There's nothing special
-about the directory name `.snap`; you can store snapshots anywhere in
-the file system.
+Users can then browse their home directories in `/home/.snap/20260706`
+as they existed at the time the snapshot was taken.  There's nothing
+special about the directory name `.snap`; you can store snapshots
+anywhere inside the file system, and mount them anywhere at all.
 
 Snapshots appear as files with the `snap` (`SF_SNAPSHOT`) flag, visible
 with the [[!template id=man name=ls section=1]] option

- Explain how to destroy a zfs snapshot, and suggest ways to make
  sure mistakes in the command don't destroy your whole zfs file
  system.

Members: 
	tutorials/how_to_use_snapshots.mdwn:1.38->1.39 

Index: wikisrc/tutorials/how_to_use_snapshots.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/how_to_use_snapshots.mdwn,v
retrieving revision 1.38
retrieving revision 1.39
diff -u -r1.38 -r1.39
--- wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 04:12:16 -0000	1.38
+++ wikisrc/tutorials/how_to_use_snapshots.mdwn	31 Jul 2026 04:43:42 -0000	1.39
@@ -19,7 +19,8 @@
 or &ldquo;`-x <snapstore>`&rdquo; options to ensure that files such as
 sqlite3 databases aren't concurrently modified while it is trying to
 read them.  Snapshots can also be mounted like regular file systems to
-give read-only views of past states of file systems.
+give read-only views of past states of file systems.  (See [caveats
+about taking incremental backups and mtimes](#caveat-mtime), though.)
 
 On some file systems&mdash;ffs and zfs&mdash;snapshots can be
 **persistent**: you can take a snapshot, stored in the file system
@@ -246,6 +247,51 @@
 # zfs rollback rpool/home/jruser@20260706
 """]]
 
+#### Discarding a persistent snapshot
+
+When done with a snapshot, you can destroy it with
+&ldquo;`zfs destroy`&rdquo;:
+
+[[!template id=programlisting text="""
+# zfs destroy rpool/home/jruser@20260706
+"""]]
+
+You can also recursively destroy all snapshots of the same name on
+datasets under a path:
+
+[[!template id=programlisting text="""
+# zfs destroy -r rpool/home/jruser@20260706
+"""]]
+
+**WARNING: If you enter the command before you finished typing, you
+might accidentally destroy the file system instead of just a
+snapshot!**
+[[!template id=man name=zfs section=8]] uses the same &ldquo;`zfs
+destroy`&rdquo; for destroying file systems, zvols, and snapshots.
+
+One technique to avoid this mistake is to start by typing
+&ldquo;`xxxzfs`&rdquo; instead of &ldquo;`zfs`&rdquo; so if you enter
+the command too early, it will fail harmlessly:
+
+[[!template id=programlisting text="""
+# xxxzfs destroy -r rpool/home
+-sh: xxxzfs: not found
+# xxxzfs destroy -r rpool/home@20260706
+-sh: xxxzfs: not found
+"""]]
+
+Or start by typing &ldquo;`echo zfs`&rdqou; instead of
+&ldquo;`zfs`&rdquo;, or use &ldquo;`zfs destroy -n`&rdquo;, especially
+if you are running a loop over many different snapshot names, to review
+what you *would* do.
+
+Then, once you have finished typing the whole command, go back to the
+beginning of the line and remove the `xxx`:
+
+[[!template id=programlisting text="""
+# zfs destroy -r rpool/home@20260706
+"""]]
+
 ### Taking backups with snapshots
 
 A snapshot of a file system won't help you recover if the disk it is
@@ -374,6 +420,7 @@
 **WARNING: If used to take incremental backups, this may be vulnerable
 to a race condition with mtime checks; see below.**
 
+<a name="caveat-mtime"></a>
 ### Caveat: Incremental backups and mtimes
 
 An incremental backup tool such as tarsnap, borg, or rsync which backs

Index: wikisrc/tutorials/kerberos_client.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/kerberos_client.mdwn,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- wikisrc/tutorials/kerberos_client.mdwn	31 Jul 2026 04:22:37 -0000	1.12
+++ wikisrc/tutorials/kerberos_client.mdwn	31 Jul 2026 04:28:49 -0000	1.13
@@ -1,4 +1,4 @@
-[[!template id=note text="[[!toc startlevel=3 levels=1]]"]]
+[[!template id=note text="[[!toc startlevel=3 levels=2]]"]]
 
 ## How to use Kerberos for single sign-on in a NetBSD client
 
@@ -6,6 +6,8 @@
 You have a login password for the principal jruser@EXAMPLE.COM.
 How do you log in and authenticate to services?
 
+### Set up Kerberos and get a ticket
+
 1. Create a directory ~/.krb5 and a file ~/.krb5/config with the
    following content to enable Kerberos on the client side:
 
@@ -82,7 +84,9 @@
      Make sure to set `[libdefaults] dns_lookup_realm = false` in each
      config file too in this case.
 
-### ssh
+### Applications
+
+#### ssh
 
 To enable [[!template id=man name="ssh" section="1"]] to use Kerberos
 authentication when logging into any host under *.example.com, add the
@@ -109,7 +113,7 @@
 Now run kerberized applications on foo.example.com through ssh without
 a password!
 
-### Firefox
+#### Firefox
 
 To log into kerberized web sites at `https://*.example.com/`:
 
@@ -131,7 +135,7 @@
 
 - This is restricted to HTTPS, and will not work with HTTP sites.
 
-### Kerberos for local login
+#### Kerberos for local login
 
 To use Kerberos for local logins, e.g. at the console or in a display
 manager such as [[!template id=man name="xdm" section="8"]], when your
Index: wikisrc/tutorials/kerberos_services.mdwn
===================================================================
RCS file: /cvsroot/wikisrc/tutorials/kerberos_services.mdwn,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- wikisrc/tutorials/kerberos_services.mdwn	31 Jul 2026 04:23:56 -0000	1.13
+++ wikisrc/tutorials/kerberos_services.mdwn	31 Jul 2026 04:28:49 -0000	1.14
@@ -55,8 +55,6 @@
    by creating “\_kerberos._host_” TXT records with the realm name in
    the DNS.
 
-[[!toc startlevel=2 levels=1]]
-
 ### sshd
 
 [[!template id=man name="sshd" section="8"]] uses service principal