Server Preview: publish the ISOs as plain .iso; keep the Pi image zipped
The live ISO's root is already compressed, so zipping saved ~13% (arm64:
233 MB raw, 203 MB zipped) and made users unzip before booting or
writing it. The release step unzips the ISOs; the build, its artifacts
and the boot tests are unchanged. The Raspberry Pi image stays .img.zip:
raw it's 2.4 GB of mostly empty filesystem, over GitHub's 2 GB per-file
limit, against ~190 MB zipped, and the usual Pi writers take .img.zip
directly. The README's quick start loses its unzip step.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
Publish the Server Preview to continuous-server: ISOs, the Pi image, SHA256SUMS (#679)
The rolling release becomes continuous-server and holds only what people
install: the amd64 and arm64 live ISOs and the Raspberry Pi 5 image,
named NextBSD-Server-<arch|rpi5>-<version>, with one SHA256SUMS. The
amd64/arm64 .img stay workflow artifacts for the boot test; a tests-only
run boots the last successful build's artifact instead of a release
asset. The README's quick start boots the live ISO in QEMU.
The old continuous release is left in place; it's deleted once
continuous-server has published.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
Publish the Server Preview to continuous-server: ISOs, the Pi image, SHA256SUMS
The rolling release becomes continuous-server and holds only what people
install: the amd64 and arm64 live ISOs and the Raspberry Pi 5 image,
named NextBSD-Server-<arch|rpi5>-<version>, with one SHA256SUMS. The
amd64/arm64 .img stay workflow artifacts for the boot test; a tests-only
run boots the last successful build's artifact instead of a release
asset. The README's quick start boots the live ISO in QEMU.
The old continuous release is left in place; it's deleted once
continuous-server has published.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
live ISO: hand launchd /dev/null stdio, not the console (#621)
The live ISO's /init wires stdout/stderr to /dev/console for its own
[init] progress and error lines, then execs launchd. launchd only opens
/dev/null for closed fds, so PID 1 and every job without StandardOutPath
or StandardErrorPath inherited the console, and their stderr reached the
screen on a normal boot.
Redirect stdio to /dev/null on the exec of launchd, matching a disk boot
where the kernel starts launchd with no fds open. /init's own output and
failure paths before that point still go to the console; the exec-failed
message now writes to /dev/console explicitly. Verbose boots keep
launchd's console logging, which launchd opens itself under -v.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
live ISO: hand launchd /dev/null stdio, not the console
The live ISO's /init wires stdout/stderr to /dev/console for its own
[init] progress and error lines, then execs launchd. launchd only opens
/dev/null for closed fds, so PID 1 and every job without StandardOutPath
or StandardErrorPath inherited the console, and their stderr reached the
screen on a normal boot.
Redirect stdio to /dev/null on the exec of launchd, matching a disk boot
where the kernel starts launchd with no fds open. /init's own output and
failure paths before that point still go to the console; the exec-failed
message now writes to /dev/console explicitly. Verbose boots keep
launchd's console logging, which launchd opens itself under -v.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
build: take the NextBSD version from SystemVersion.plist (#612)
nextbsd-version, /etc/os-release and the image names now come from the
installed NextBSD-everything's /System/Library/CoreServices/SystemVersion.plist,
which nextbsd-pkg writes (nextbsd/nextbsd#536), instead of the image's
IMG_DATE:
- /bin/nextbsd-version reads the plist each time it runs and prints
"NextBSD 27.0.0 (<build>)", so it follows pkg upgrade.
- /etc/os-release gets NAME, VERSION, VERSION_ID, BUILD_ID and
PRETTY_NAME from the plist. nextbsd-fetch, the login banner, prints
PRETTY_NAME, so the banner shows "NextBSD 27.0.0 (<build>)". On an
installed system NextBSD-everything's Lua post-install script writes
the same lines on every upgrade, so os-release is not left at the
version the image was built with.
- The disk image, ISO and rpi5 image are named
NextBSD-<arch>-27.0.0-<build>. The workflow reads the stamp off the
file build.sh wrote, and the continuous release notes name the
version and build.
[7 lines not shown]
build: take the NextBSD version from SystemVersion.plist
nextbsd-version, /etc/os-release and the image names now come from the
installed NextBSD-everything's /System/Library/CoreServices/SystemVersion.plist,
which nextbsd-pkg writes (nextbsd/nextbsd#536), instead of the image's
IMG_DATE:
- /bin/nextbsd-version reads the plist each time it runs and prints
"NextBSD 27.0.0 (<build>)", so it follows pkg upgrade.
- /etc/os-release gets NAME, VERSION, VERSION_ID, BUILD_ID and
PRETTY_NAME from the plist. nextbsd-fetch, the login banner, prints
PRETTY_NAME, so the banner shows "NextBSD 27.0.0 (<build>)". On an
installed system NextBSD-everything's Lua post-install script writes
the same lines on every upgrade, so os-release is not left at the
version the image was built with.
- The disk image, ISO and rpi5 image are named
NextBSD-<arch>-27.0.0-<build>. The workflow reads the stamp off the
file build.sh wrote, and the continuous release notes name the
version and build.
[8 lines not shown]
build: install NextBSD packages with NextBSD's pkg-static (#609)
The NextBSD repository now carries the NextBSD ABI (NextBSD:27:<arch>,
OSVERSION 2700000), and the build VM's stock pkg refuses it ("wrong
architecture: NextBSD:27:aarch64 instead of FreeBSD:15:aarch64").
Install NextBSD-everything, the pkglist.txt packages and the residue
clean with nextbsd-contrib's pkg-static, the same tool nextbsd-pkg uses,
with ABI=NextBSD:27:<arch> (aarch64 on arm64) and OSVERSION=2700000. The
workflow downloads the amd64 pkg-static from nextbsd-contrib's continuous
release for both build jobs (amd64/arm64 and rpi5); a hand run fetches
it. The FreeBSD:15 ABI pin and the VM's uname -K OSVERSION are gone, so
the image's package database carries the ABI its own pkg computes.
Refs nextbsd/nextbsd-kernel#376
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
build: install NextBSD packages with NextBSD's pkg-static
The NextBSD repository now carries the NextBSD ABI (NextBSD:27:<arch>,
OSVERSION 2700000), and the build VM's stock pkg refuses it ("wrong
architecture: NextBSD:27:aarch64 instead of FreeBSD:15:aarch64").
Install NextBSD-everything, the pkglist.txt packages and the residue
clean with nextbsd-contrib's pkg-static, the same tool nextbsd-pkg uses,
with ABI=NextBSD:27:<arch> (aarch64 on arm64) and OSVERSION=2700000. The
workflow downloads the amd64 pkg-static from nextbsd-contrib's continuous
release for both build jobs (amd64/arm64 and rpi5); a hand run fetches
it. The FreeBSD:15 ABI pin and the VM's uname -K OSVERSION are gone, so
the image's package database carries the ABI its own pkg computes.
Refs nextbsd/nextbsd-kernel#376
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
build: stop shipping FreeBSD's pkg repo config (#606)
NextBSD no longer ships or configures FreeBSD's package repo
(nextbsd/nextbsd-kernel#376). build.sh no longer writes
/usr/local/etc/pkg/repos/FreeBSD.conf and no longer creates
/usr/local/etc/pkg/repos; the image's only repo is NextBSD's own, from
nextbsd-overlays.
Nothing in the image build resolved from pkg.FreeBSD.org:
NextBSD-everything installs through the isolated NextBSD-only REPOS_DIR,
and pkglist.txt is empty. The pkglist.txt step now installs from that
same NextBSD-only repo config instead of the FreeBSD one, so it can never
reach pkg.FreeBSD.org. Comments in build.sh and pkglist.txt are updated
to match.
Refs nextbsd/nextbsd-kernel#376
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
build: stop shipping FreeBSD's pkg repo config
NextBSD no longer ships or configures FreeBSD's package repo
(nextbsd/nextbsd-kernel#376). build.sh no longer writes
/usr/local/etc/pkg/repos/FreeBSD.conf and no longer creates
/usr/local/etc/pkg/repos; the image's only repo is NextBSD's own, from
nextbsd-overlays.
Nothing in the image build resolved from pkg.FreeBSD.org:
NextBSD-everything installs through the isolated NextBSD-only REPOS_DIR,
and pkglist.txt is empty. The pkglist.txt step now installs from that
same NextBSD-only repo config instead of the FreeBSD one, so it can never
reach pkg.FreeBSD.org. Comments in build.sh and pkglist.txt are updated
to match.
Refs nextbsd/nextbsd-kernel#376
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
build: pin pkg's ABI per arch in the image's pkg.conf
NextBSD is moving __FreeBSD_version/kern.osreldate to 2700000 (NextBSD
kernel 27.0.0). pkg reads its ABI from /usr/bin/uname's ELF note, so
once the world is built at 27 it would ask repositories for
FreeBSD:27:<arch>. NextBSD's own packages (built by nextbsd-pkg on a
FreeBSD 15.1 VM) and pkg.FreeBSD.org/latest are FreeBSD:15:<arch>, and
NextBSD keeps the releng/15.1 kernel and libc API.
Step 5 now appends ABI = "FreeBSD:15:amd64" (or "FreeBSD:15:aarch64")
and OSVERSION = 1501000, an unquoted integer as pkg 2.8.4 requires, to
the overlay-seeded /private/etc/pkg.conf, and fails if the overlay
already sets them or the pin is missing afterwards. No ALTABI. At
1501000 this matches what pkg detects today.
Refs nextbsd/nextbsd-kernel#376
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
Fetch freebsd-kexts on arm64 too (#592)
nextbsd-kernel-extensions now publishes freebsd-kexts-<arch>.tar.gz for
both arches (autofs.kext is on arm64 too, nextbsd-kernel-extensions#7).
Fetch it per arch instead of on amd64 only, failing if it is missing.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
Fetch freebsd-kexts on arm64 too
nextbsd-kernel-extensions now publishes freebsd-kexts-<arch>.tar.gz for
both arches (autofs.kext is on arm64 too, nextbsd-kernel-extensions#7).
Fetch it per arch instead of on amd64 only, failing if it is missing.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
Take the FreeBSD kexts from nextbsd-kernel-extensions (#591)
IntelWiFi and IntelEthernet now build in the new nextbsd-kernel-extensions
and ship as freebsd-kexts-amd64.tar.gz (nextbsd/nextbsd#554); fetch that
instead of the two Intel tarballs from the graphics repo.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
Take the FreeBSD kexts from nextbsd-kernel-extensions
IntelWiFi and IntelEthernet now build in the new nextbsd-kernel-extensions
and ship as freebsd-kexts-amd64.tar.gz (nextbsd/nextbsd#554); fetch that
instead of the two Intel tarballs from the graphics repo.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
Use nextbsd-kernel-extensions-graphics, failing loudly (#590)
nextbsd-kernel-extensions is now nextbsd-kernel-extensions-graphics
(nextbsd/nextbsd#551). Fetch the kexts and the Raspberry Pi 5 overlays
from the new name before the old one is reused, and fail when any of
them is missing instead of shipping an image without it
(nextbsd/nextbsd#552). README and issue refs follow.
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
Use nextbsd-kernel-extensions-graphics, failing loudly
nextbsd-kernel-extensions is now nextbsd-kernel-extensions-graphics
(nextbsd/nextbsd#551). Fetch the kexts and the Raspberry Pi 5 overlays
from the new name before the old one is reused, and fail when any of
them is missing instead of shipping an image without it
(nextbsd/nextbsd#552). README and issue refs follow.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
Fetch NVIDIA kexts from nextbsd-kernel-extensions-nvidia (#589)
Take nvidia-kexts-amd64.tar.gz from the NVIDIA repo instead of
nvidia-kexts.tar.gz from nextbsd-kernel-extensions, and fail when it is
missing instead of shipping an image without it (nextbsd/nextbsd#548).
Co-authored-by: Claude Opus 5.5 <noreply at anthropic.com>
Fetch NVIDIA kexts from nextbsd-kernel-extensions-nvidia
Take nvidia-kexts-amd64.tar.gz from the NVIDIA repo instead of
nvidia-kexts.tar.gz from nextbsd-kernel-extensions, and fail when it is
missing instead of shipping an image without it (nextbsd/nextbsd#548).
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
build.sh: keep shipping the FreeBSD ports repo in /usr/local/etc/pkg/repos
The image still ships /usr/local/etc/pkg/repos/FreeBSD.conf
(pkg.FreeBSD.org/latest) so FreeBSD ports packages install out of the
box. It sits below the NextBSD repo (priority 0 vs 100); NextBSD's pkg
never takes pkg from it and keeps its packages in /usr/local/ and /var/.
No /usr/local/etc/pkg.conf is written. Step 5b uses the same file again.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
build.sh: ship no pkg config of its own and no FreeBSD repo; pkg from NextBSD
NextBSD's pkg reads /private/etc/pkg.conf and /private/etc/pkg/, and
nextbsd-overlays now ships /private/etc/pkg.conf (IGNORE_OSVERSION only;
pkg detects FreeBSD:15:<arch> from /usr/bin/uname's ELF note) and
/private/etc/pkg/NextBSD.conf (continuous-${MACHINE}, priority 100).
- Step 5 no longer writes /usr/local/etc/pkg.conf or
/usr/local/etc/pkg/repos/{FreeBSD,NextBSD}.conf; it checks that the
overlay seed provided both files.
- pkglist.txt drops pkg: it comes from the NextBSD repo through
NextBSD-everything (nextbsd-pkg#19). The list is now empty.
- When pkglist.txt is not empty, the FreeBSD repo it needs is a build-only
REPOS_DIR under $WORK, as $NBREPO is, and is never written into the
image.
- The residue-clean notes name the new config paths.
Closes #545
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
Merge pull request #544 from nextbsd/fix/pkg-db-private-var
build.sh: lay the /private symlinks before pkg installs, so the package database lands in /private/var
Merge pull request #544 from nextbsd/fix/pkg-db-private-var
build.sh: lay the /private symlinks before pkg installs, so the package database lands in /private/var
build.sh: empty the package cache directory after pkg clean
pkg clean's failure is ignored and it leaves files it does not recognise,
so delete whatever remains in private/var/cache/pkg before the image is
baked. No downloaded package ships in the IMG or ISO.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
build.sh: empty the package cache directory after pkg clean
pkg clean's failure is ignored and it leaves files it does not recognise,
so delete whatever remains in private/var/cache/pkg before the image is
baked. No downloaded package ships in the IMG or ISO.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
build.sh: lay the /private symlinks before pkg installs, so the package database lands in /private/var
Step 3 moved the installed var into private/ after NextBSD-everything was
installed. Since nextbsd-userland#375, NextBSD-userland ships
/private/var/log/com.apple.launchd, so private/var already existed and
mv nested var inside it as private/var/var. The package database and the
package cache were stranded there: the image's pkg info listed only pkg,
and the 101 MiB cache escaped step 5b's clean.
Create private/{etc,var,tmp} and the relative etc/var/tmp symlinks at the
start of the pkg branch instead, and drop the move.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>
build.sh: lay the /private symlinks before pkg installs, so the package database lands in /private/var
Step 3 moved the installed var into private/ after NextBSD-everything was
installed. Since nextbsd-userland#375, NextBSD-userland ships
/private/var/log/com.apple.launchd, so private/var already existed and
mv nested var inside it as private/var/var. The package database and the
package cache were stranded there: the image's pkg info listed only pkg,
and the 101 MiB cache escaped step 5b's clean.
Create private/{etc,var,tmp} and the relative etc/var/tmp symlinks at the
start of the pkg branch instead, and drop the move.
Co-Authored-By: Claude Opus 5.5 <noreply at anthropic.com>