Drop the leading H1 from every page
GitHub renders the page name as a heading on every wiki page, so a file
that also opens with "# Page Name" prints its title twice. All eleven
pages did.
Home's H1 read "NextBSD" rather than "Home", so it was not a literal
duplicate, but it goes too -- eleven pages with one convention beats ten
plus an exception, and the bold opening sentence works as the lead.
Section headings inside the pages are untouched.
Hardware: arm64 ships kexts too; drop Nmdm, which ships nowhere
NextBSD-kernel-extensions publishes for both arches -- verified by unpacking
today's packages from the continuous-<arch> release tags rather than reading
the pkg README, which still carries the stale amd64-only table.
arm64 7 kexts: VirtIOGraphics, IOGraphics, IOGraphicsExtras,
IOGraphicsShmem, TTM, DMABuf, LinuxVirtIO
amd64 17 kexts: the above plus BochsGraphics, VBoxGraphics,
IntelGraphics, AMDGraphics, RadeonGraphics,
NVIDIAGraphics595 + NVIDIACore595 + NVIDIAModeset595,
IntelWiFi, IntelEthernet
So arm64 has the complete virtio-gpu stack, which is the driver that
matters there -- UTM and QEMU give an arm64 guest virtio-gpu.
Also corrected from the same evidence: TTM and DMABuf were missing from
the shared-helpers table, NVIDIA is three kexts rather than one, and the
per-arch columns on the virtual-GPU table were guesswork.
Nmdm.kext is gone entirely. It appears in the CI workflow's kext PoC boot
test, which is where I originally read it, but it is in neither shipped
package -- zero matching entries in the amd64 archive.
Installing-Packages carried the same amd64-only claim in its package table.
Installing-Packages: the repo config already ships, stop telling users to write it
build.sh:183 writes /usr/local/etc/pkg/repos/NextBSD.conf into the shipped
rootfs, alongside FreeBSD.conf and a pkg.conf pinning the ABI -- so both
repositories are live on first boot of any published .img or .iso.
The page led with "drop a config file into ...", which invented a setup step
that does not exist and implied pkg would not work until you did it. It now
leads with the three files that are already there, and puts the config text
in a "Recreating the config" section for the case where someone is
bootstrapping onto a system that did not come from a published image.
Build out the wiki as user-facing documentation
Adds nine pages and a sidebar, drawn from the repo READMEs, PORTING notes,
the shipped man pages and the userland source tree.
Home welcome, navigation, the three surprises
Getting-Started download, verify, boot under QEMU, log in
Installing-NextBSD nextbsd-installer walkthrough
Installing-Packages pkg repo config, NextBSD-everything
Command-Reference Darwin commands with their man sections
Service-Management-with-launchd plists, launchctl, the foreground trap
Filesystem-Layout four-domain model, empty /boot/kernel
How-NextBSD-Differs the BSD comparison table, boot diagram
Project-Repositories build chain and who owns what
The existing UTM guide keeps its content and gains a title, an intro and
cross-links. Its page name contains parentheses, so links to it use
angle-bracket destinations -- a bare ](Apple-Silicon-Mac-(UTM)-Guide)
terminates at the first close paren and renders broken.