branches: 1.2.4; 1.2.8;
merge more, and add an i386 image

Add preliminary support for creating x86 usb sticks with mkimage.
This is untested, and just a checkpoint of the work. Image looks
ok, but I have not tried if it boots.

Fix MKREPRO build (Jan-Benedict Glaw)

ec2_init: Add support for Oracle Cloud

Background dhcpcd if ec2_init is not enabled to speed up boot.

port-evbarm/56274: no network on ec2 arm64 9.99.85

Add -w to dhcpcd_flags when running on EC2, since we need to wait for the
network to come up before contacting the metadata service.

Create an "octeon.img.gz" bootable image for evbmips64-eb release builds.

Enable GPT support w/ hybrid MBR for Raspberry Pi compatibility.

Separate devicetree .dts -> .dtb building from kernel builds. They are now
part of a separate set, "dtb.tgz", and only built when MKDTB=yes. This
defaults to yes for earmv[67]* and aarch64, and no everywhere else.

RPi4 has a different root device, so use config.txt conditionals to load
an alternate cmdline txt file (cmdline-pi4.txt) on these boards.

Update to new RaspberryPi firware

commit 0c01dbefba45a08c47f8538d5a071a0fba6b7e83
Author: popcornmix <popcornmix@gmail.com>
Date: Wed Dec 11 15:30:08 2019 +0000

and include firmware for RPI4

Firmware has bee updated to support mainline linux kernels as described in
https://github.com/raspberrypi/linux/issues/3237

Fix whitespace in a comment

Add Amlogic dtb files to arm64.img

Add support for configuring Amazon.com EC2 SSH keys and hostnames. While
here, only set wscons=YES if a wsdisplay0 device is present.

Install ELF kernel to the FFS partition and boot it with bootaa64.efi
instead of loading kernel.img from the MSDOS partition with extlinux.conf

Move rk3399 dtb files to the correct location

branches: 1.2.2;
Install RK3328 .dtb files to the correct location

branches: 1.1.2;
Add initial support for ARMv8 (AARCH64) (by nisimura@ and ryo@)

- sys/arch/evbarm64 is gone and integrated into sys/arch/evbarm. (by skrll@)
- add support fdt. evbarm/conf/GENERIC64 fdt (bcm2837,sunxi,tegra) based generic 64bit kernel config. (by skrll@, jmcneill@)

Fix MKREPRO build (Jan-Benedict Glaw)

No need for ec2_init on arm64mbr

Create a separate Arm64 image that uses MBR partitioning. Amlogic SoCs
require the bootloader to be installed on SD cards at LBA1 which makes
them incompatible with GPT images.

Fix reproducible build (Jan-Benedict Glaw)

Install /boot/boot.cfg with EFI bootloaders.

On ARM ports, the EFI boot loader handles a boot.cfg file if it
exists, but one is not installed by default. In contrast, both the
i386 and amd64 ports do install boot.cfg by default. Bring these
ports into agreement by installing boot.cfg on ARM ports with EFI boot
loaders.

Update a few www.raspberrypi.com URLs

Move back to MBR based images for armv7 because Amlogic's bootloader (for
Amlogic S805 based boards) needs to be installed to sector 1, which
conflicts with the GPT header.

No need to rename netbsd-GENERIC.img to kernel7.img

Switch to GPT w/ hybrid MBR for armv7 images

Separate devicetree .dts -> .dtb building from kernel builds. They are now
part of a separate set, "dtb.tgz", and only built when MKDTB=yes. This
defaults to yes for earmv[67]* and aarch64, and no everywhere else.

Update to new RaspberryPi firware

commit 0c01dbefba45a08c47f8538d5a071a0fba6b7e83
Author: popcornmix <popcornmix@gmail.com>
Date: Wed Dec 11 15:30:08 2019 +0000

and include firmware for RPI4

Firmware has bee updated to support mainline linux kernels as described in
https://github.com/raspberrypi/linux/issues/3237

Move omap3 dtb files to /boot/dtb

Remove debug output, fix a progress message

Move a lot of *.dtb files to a dtb/ subdirectory on the FAT partition.
Mkimage (eroneously) creates a FAT16 partition (despite the configuration
asking for FAT32), and that has a root directory size limit.
Idea from Jared.

Switch to GENERIC kernels only.

branches: 1.35.2;
Fallback to non-EFI boot script if EFI bootloader is absent.

Note that we do not currently build EFI bootloader for earmv7hf-eb,
as it requires little-endian version of toolchain.

Switch the kernel7.img RaspberryPi kernel in the armv7 image to GENERIC
and thus reducing the number of kernels built in an evbarmv7 release.

Remove sun50i support from 32-bit GENERIC.

Install GENERIC ELF kernel as /netbsd for EFI booting

Install bootarm.efi to boot partition

No need to specify root and console bootargs on amlogic

Another kernel bites te dust.

Remove ODROID-C1 as it is now replaced by GENERIC. Thanks jmcneill.

Add support for configuring Amazon.com EC2 SSH keys and hostnames. While
here, only set wscons=YES if a wsdisplay0 device is present.

Make armv7.img boot on the DE0 Nano SoC. Requires u-boot from -current pkgsrc.

Use the GENERIC kernel where possible in armv7.img and remove the old
kernels from the bulid for SUNXI and TEGRA.

While I'm here disable *_INSTALL kernel builds for boards supported by
armv7.img

Whitespace

a bit of sorting

branches: 1.23.2; 1.23.4;
Add missing RPI FDT build goop, from nick.

On 64-bit boards, U-Boot expects to find .dtb files in an allwinner/ subdirectory

Remove legacy awin kernels from image

Be more precise about exactly what fails when something does.

Relying upon set -e to abort things is sort of OK (it is not
a recommended option to use in general - too many odd special cases),
but only if user can work out from the "build failed" what actually
went wrong.

Tested only on amd64 build (for this, i386 is the same) - if anyone
has problems on builds for other systems, please let me know. However
the changes affect only failure paths, the most likely problem would
be for a build to fail to halt on an error, and I hope I have avoided
that. There should be no difference at all to error-free builds.

Trailing whitespace

Don't install uEnv.txt for beagle; boot.scr handles this now.

Install a boot.scr on armv7.img that detects the running board and selects
the correct kernel and boot protocol. Should work on tegra, sunxi, and
am335x boards for now.

Create a config.txt for RPI and set 'enable_uart=1' and 'force_turbo=0'.
This config gives us a stable core_freq clock that is used to drive the
SD HOST and AUX UART devices.

More information on config.txt settings for the UART can be found here:

https://www.raspberrypi.org/documentation/configuration/uart.md

Add : to body of populate_sunxi to appease bash.

Test for kernel build directory before reading DTB list

Replace HUMMINGBIRD_A31 with SUNXI kernel on armv7.img and include .dtb
files for SUNXI and TEGRA kernels on the MSDOS partition.

branches: 1.12.4;
ODROID-C1: Now that the MBR partition table contains an entry for the BSD
partition, the disklabel no longer conflicts with the ODROID-C1 bootloader.
Root partition changes from ld0e to ld0a.

tegra: set loadaddr to 0x90000000 (the default kernel_addr_r overlaps
fdt_addr_r on TK1 + L4T 21.x), and set default root device to ld0a to
match new device probe order.

branches: 1.10.2; 1.10.4;
C&P of change in rpi.conf (maybe factor out)

By default, RPI firmware sets the max CPU frequency to 600MHz. This can be
overridden by setting arm_freq in config.txt, but the default freq at boot
is still 600MHz.

Add logic to rc.local to compare the current vs. max CPU frequency; if they
differ, set the target frequency to the maximum.

Remove JETSONTK1 and NYAN-BIG kernels, add a new unified kernel named TEGRA.

Cubieboard2 kernel is named netbsd-CUBIEBOARD.ub not netbsd-CUBIEBOARD2.ub

branches: 1.7.2;
install jetsontk1 boot script as boot.scr

Properly escape the $ when trying to pass the u-boot env var $kernel.
From Rin Okuyama.

Turn resize on

double quote police

add JETSONTK1 to armv7.img

Cleanup: make_filesystems is not used any longer, purge remains

Rename beagleboard.img to armv7.img. The new image includes the same
kernels as beagleboard.img plus support for Raspberry Pi 2, ODROID-C1,
Cubieboard2, Cubietruck, Hummingbird A31, and Banana Pi.

Rename beagleboard.img to armv7.img. The new image includes the same
kernels as beagleboard.img plus support for Raspberry Pi 2, ODROID-C1,
Cubieboard2, Cubietruck, Hummingbird A31, and Banana Pi.

escape $ in $board so this will boot on beaglebone too

branches: 1.17.4;
After discussions with cristos regarding the previous commit, he
convinced me it was sufficient to define GZIP_CMD only in
distrib/utils/embedded/mkimage and not again in the config files
beagleboard.conf, rpi.conf, and rpi_inst.conf similar to how the
other variables $src, $release, $mnt, ... are only defined there.

Fix build release of evbarm which had been failing in mkimage
beagleboard_smp with the elusive message:

"gzip: can't stat: gzip: No such file or directory"

This was due to GZIP=gzip being defined in mkimage; we now use:

GZIP_CMD=${TOOL_GZIP:-gzip} # ${GZIP} is special to gzip(1)

as distrib/sets/sets.subr already does in these files as well:

distrib/utils/embedded/mkimage
distrib/utils/embedded/conf/beagleboard.conf
distrib/utils/embedded/conf/rpi.conf
distrib/utils/embedded/conf/rpi_inst.conf

4th time's a charm (I hope). Make sure that we pick up the kernel path passed to
mkimage command line, and not the default.

Instead of trying to pass two kernels to beagleboard.conf, pass one and
derive the path to the second from the first.

Try to pick up the right location for BEAGLEBONE and BEAGLEBOARD kernels.

support beaglebone and beagleboard with the same image

branches: 1.11.4;
Use "gzip -dc" instead of "zcat" - some versions of zcat don't grok
gzip.

gzcat -> zcat

no objmachine by default.

remove trailing whitespace from EOF

make sure kernel is installed as netbsd.ub

keep beagleboard conf in sync with rpi

switch to makefs

Move mdnsd to beagleboard only. RPI doesn't like it at the moment.

branches: 1.3.2;
- Add support for xsets
- Factor out common evbarm code

set kerneldir= to the path used by build.sh

add mkimage config for generating beagleboard images

Recognize MKPOSTFIX=no in mkimage

Remove duplicated code, handle minwrites in _normal the same way we handle
it in _gpt. Initial patch from jmmv@.

branches: 1.42.2;
/etc/rc.d/cerctl_init: New script for certctl rehash in live images.

This is very limited -- it does not supplant postinstall to rehash
certificates on upgrade; it only runs certctl rehash if
/etc/openssl/certs is an empty directory, as you get in live images
not created with sysinst.

We could also have a more general-purpose way to run postinstall(8)
on first boot of an image, but that has a lot more moving parts to
think about, so let's start with this limited-scope low-risk
approach.

PR install/57629

XXX pullup-10

branches: 1.41.2;
Silence a warning when machdep.dmi.chassis-asset-tag is not present

ec2_init: Add support for Oracle Cloud

Disable kernfs on live images -- it is not required.

Fix fallout from mkimage rev 1.76.

For mkimage:

- Update "size" if auto-calculated.
- Use "dd bs=1" instead of non-portable "head -c".
- Some style nits.

For MD make_label() functions:

- Stop using "newsize" as image size in MB, use "size" instead.

Create an "octeon.img.gz" bootable image for evbmips64-eb release builds.

Allow config file to override hostname

Add GPT support to mkimage.

Remove the pretty much useless 128MB swap partition from the arm images.

branches: 1.33.2;
add a method to add user accounts or ssh keys to the embedded
(installable) images which may be run entirely headless and
have no current method to edit the installation without another
netbsd host to modify the root (FFS) partition.

creds_msdos reads the creds.txt file from the msdos boot
partition and provides 4 basic methods:

sshkeyfile <user> <path on msdos>
sshkey <user> <entry>
useraddhash <user> <passwd hash>
useradd <user> <passwd>

the first two create a user with ssh key(s), and the second
two create a user with a password. if the last method is used
and raw passwords are given, the creds.txt file will be
shredded and deleted by rm -P.


inspired by a request from a pine64 user. ok jmcneill@.

Fix variable escaping in dev_exists()

Add support for configuring Amazon.com EC2 SSH keys and hostnames. While
here, only set wscons=YES if a wsdisplay0 device is present.

Use special ROOT. prefix in fstab entries instead of assuming ld0

resize_disklabel: if disk and partition is not specified, use kern.root_device/kern.root_partition sysctls

branches: 1.28.2;
Increase reserved space at start of image from 4MB to 16MB to make room
for Rockchip bootloaders.

branches: 1.27.8;
minor cleanup in customize_evbarm():
keep handling of /etc/rc.conf in one place

branches: 1.26.2;
Slightly reduce the size of the MSDOS partition from 124M to 92M. With
the larger size, installing the ODROID-C1 bootloader causes the fs to
become unreadable. Not sure why..

Increase the size of the boot partition and remove the 'd' part from the
disklabel.

branches: 1.24.2; 1.24.4;
mount root partition with noatime

Align partitions to 64MB for the benefit of SD cards > 32GB

show resize_ffs progress bar when resizing root partition

Add support for auto-growing the root partition. Enable it for rpi.img.

Fix previous so that the new generated rc.conf is picked up and that
any new new mount points (e.g. /proc and /kern) are generated.

While here increate the fs size so that postfix can actually build
/etc/mail/aliases.db

add /var/shm tmpfs to fstab

PR/49596: mkimage: incorrect permissions on evbarm images

Use NetBSD.dist in our mtree specification to populate the top level
directories, etc.

For each generated file hand craft an mtree entry.

Remove specialdirs as NetBSD.dist creates /proc and /kern.

disable wapbl for evbarm images until stability issues are sorted out

turn on ntpd

branches: 1.15.4;
these changes produce a bootable system under qemu, but its root is trashed.

Add preliminary support for creating x86 usb sticks with mkimage.
This is untested, and just a checkpoint of the work. Image looks
ok, but I have not tried if it boots.

Fix /dev population of the evbarm images by using MAKEDEV -s and appending
to the mtree spec file passed to makefs.

Keep both c: and d: paritions so this can work with systems that have
RAW_PART as 2 or 3. Addresses PR/47688.

If minwrites is set:
- set noatime, nodevmtime for root
- use tmpfs for frequently written files
- use unix sockets instead of fifos for postfix
From:
http://rich-tbp.blogspot.com/2013/03/netbsd-on-rpi-minimizing-disk-writes.html

Disklabel need to use sectors, not bytes. Thanks to agc.

branches: 1.9.4;
Use HOST_SH to run scripts. Makes mkimage work on SunOS.

create /proc and /kern

set rc_configured=YES and a hostname

start with the original rc.conf

switch to makefs

Move mdnsd to beagleboard only. RPI doesn't like it at the moment.

Size for 512 byte sectors and base ffs partition size on totalsize minus
others.

branches: 1.2.2;
kernel.img is for rpi only

- Add support for xsets
- Factor out common evbarm code

Recognize MKPOSTFIX=no in mkimage

Remove duplicated code, handle minwrites in _normal the same way we handle
it in _gpt. Initial patch from jmmv@.

branches: 1.4.2;
/etc/rc.d/cerctl_init: New script for certctl rehash in live images.

This is very limited -- it does not supplant postinstall to rehash
certificates on upgrade; it only runs certctl rehash if
/etc/openssl/certs is an empty directory, as you get in live images
not created with sysinst.

We could also have a more general-purpose way to run postinstall(8)
on first boot of an image, but that has a lot more moving parts to
think about, so let's start with this limited-scope low-risk
approach.

PR install/57629

XXX pullup-10

branches: 1.3.2;
Disable kernfs on live images -- it is not required.

Fix fallout from mkimage rev 1.76.

For mkimage:

- Update "size" if auto-calculated.
- Use "dd bs=1" instead of non-portable "head -c".
- Some style nits.

For MD make_label() functions:

- Stop using "newsize" as image size in MB, use "size" instead.

Create an "octeon.img.gz" bootable image for evbmips64-eb release builds.

wii: Disable ntpd by default.

It takes up a lot of memory.

Recognize MKPOSTFIX=no in mkimage

Remove duplicated code, handle minwrites in _normal the same way we handle
it in _gpt. Initial patch from jmmv@.

branches: 1.1.2; 1.1.4;
evbppc: Add initial support for the Nintendo Wii

branches: 1.1.4; 1.1.8;
merge more, and add an i386 image

Create an "octeon.img.gz" bootable image for evbmips64-eb release builds.

Remove duplicated code, handle minwrites in _normal the same way we handle
it in _gpt. Initial patch from jmmv@.

branches: 1.2.2;
/etc/rc.d/cerctl_init: New script for certctl rehash in live images.

This is very limited -- it does not supplant postinstall to rehash
certificates on upgrade; it only runs certctl rehash if
/etc/openssl/certs is an empty directory, as you get in live images
not created with sysinst.

We could also have a more general-purpose way to run postinstall(8)
on first boot of an image, but that has a lot more moving parts to
think about, so let's start with this limited-scope low-risk
approach.

PR install/57629

XXX pullup-10

RISC-V support that works on QEMU with a single hart.

Thanks for Simon Burge for plic(4).

RISC-V support that works on QEMU with a single hart.

Thanks for Simon Burge for plic(4).

RISC-V support that works on QEMU with a single hart.

Thanks for Simon Burge for plic(4).

Update a few www.raspberrypi.com URLs

G/C unused.

Fix kernel= order, add pi0w conditional and comments

Conditionally boot kernel.img or kernel7.img depending on board

Separate devicetree .dts -> .dtb building from kernel builds. They are now
part of a separate set, "dtb.tgz", and only built when MKDTB=yes. This
defaults to yes for earmv[67]* and aarch64, and no everywhere else.

Update to new RaspberryPi firware

commit 0c01dbefba45a08c47f8538d5a071a0fba6b7e83
Author: popcornmix <popcornmix@gmail.com>
Date: Wed Dec 11 15:30:08 2019 +0000

and include firmware for RPI4

Firmware has bee updated to support mainline linux kernels as described in
https://github.com/raspberrypi/linux/issues/3237

branches: 1.34.4;
Fix spelling in error message

Add missing RPI FDT build goop, from nick.

Be more precise about exactly what fails when something does.

Relying upon set -e to abort things is sort of OK (it is not
a recommended option to use in general - too many odd special cases),
but only if user can work out from the "build failed" what actually
went wrong.

Tested only on amd64 build (for this, i386 is the same) - if anyone
has problems on builds for other systems, please let me know. However
the changes affect only failure paths, the most likely problem would
be for a build to fail to halt on an error, and I hope I have avoided
that. There should be no difference at all to error-free builds.

Trailing whitespace

Create a config.txt for RPI and set 'enable_uart=1' and 'force_turbo=0'.
This config gives us a stable core_freq clock that is used to drive the
SD HOST and AUX UART devices.

More information on config.txt settings for the UART can be found here:

https://www.raspberrypi.org/documentation/configuration/uart.md

Cleanup: make_filesystems is not used any longer, purge remains

Add support for auto-growing the root partition. Enable it for rpi.img.

Add RPI2 to kernels build for both earmv[67].

Use the earmv6 built kernels to create an image that can be used on both
RPI and RPI2

actually write cpufreq changes to ${mnt}/etc/rc.local instead of /tmp/a

By default, RPI firmware sets the max CPU frequency to 600MHz. This can be
overridden by setting arm_freq in config.txt, but the default freq at boot
is still 600MHz.

Add logic to rc.local to compare the current vs. max CPU frequency; if they
differ, set the target frequency to the maximum.

branches: 1.24.4;
Put console=fb back as autodetect is bunged up.

After discussions with cristos regarding the previous commit, he
convinced me it was sufficient to define GZIP_CMD only in
distrib/utils/embedded/mkimage and not again in the config files
beagleboard.conf, rpi.conf, and rpi_inst.conf similar to how the
other variables $src, $release, $mnt, ... are only defined there.

Fix build release of evbarm which had been failing in mkimage
beagleboard_smp with the elusive message:

"gzip: can't stat: gzip: No such file or directory"

This was due to GZIP=gzip being defined in mkimage; we now use:

GZIP_CMD=${TOOL_GZIP:-gzip} # ${GZIP} is special to gzip(1)

as distrib/sets/sets.subr already does in these files as well:

distrib/utils/embedded/mkimage
distrib/utils/embedded/conf/beagleboard.conf
distrib/utils/embedded/conf/rpi.conf
distrib/utils/embedded/conf/rpi_inst.conf

use console auto detection, ok nick

turn on devpubd

branches: 1.19.4;
Use "gzip -dc" instead of "zcat" - some versions of zcat don't grok
gzip.

gzcat -> zcat

dont use echo -n

handle renaming and uncompressing the kernel

add missing }

change to take the full kernel path

switch to makefs

cmdline needs to be a line! hi jak.

branches: 1.11.2;
Specify the root device in cmdline.txt, also, it's 'Pi', not 'PI'.

kernel.img is for rpi only

- Add support for xsets
- Factor out common evbarm code

now that we compute sizes correctly, reduce the extra to how much free space
we want.

make autosizing work (kind of)

first step at autosizing, still does not work.

append to rc.conf, don't overwrite

add the comp set

use variables for the fdisk command too

Autosize label

Adjust mkimage to handle RPI. From skrll@

Update a few www.raspberrypi.com URLs

Disable kernfs on live images -- it is not required.

rpi.img: Bump boot partition in a similar manner to other images.

Separate devicetree .dts -> .dtb building from kernel builds. They are now
part of a separate set, "dtb.tgz", and only built when MKDTB=yes. This
defaults to yes for earmv[67]* and aarch64, and no everywhere else.

Use fat16 as the partition is too small for fat32. from Harold Gutch

Use make_label_evbarm instead of home grown

upstream_kernel=1 is required with new firmware/kernel.

Update to new RaspberryPi firware

commit 0c01dbefba45a08c47f8538d5a071a0fba6b7e83
Author: popcornmix <popcornmix@gmail.com>
Date: Wed Dec 11 15:30:08 2019 +0000

and include firmware for RPI4

Firmware has bee updated to support mainline linux kernels as described in
https://github.com/raspberrypi/linux/issues/3237

branches: 1.11.4;
Build fix (really this time) from Harold Gutch

Be more precise about exactly what fails when something does.

Relying upon set -e to abort things is sort of OK (it is not
a recommended option to use in general - too many odd special cases),
but only if user can work out from the "build failed" what actually
went wrong.

Tested only on amd64 build (for this, i386 is the same) - if anyone
has problems on builds for other systems, please let me know. However
the changes affect only failure paths, the most likely problem would
be for a build to fail to halt on an error, and I hope I have avoided
that. There should be no difference at all to error-free builds.

Create a config.txt for RPI and set 'enable_uart=1' and 'force_turbo=0'.
This config gives us a stable core_freq clock that is used to drive the
SD HOST and AUX UART devices.

More information on config.txt settings for the UART can be found here:

https://www.raspberrypi.org/documentation/configuration/uart.md

More cleanup:
Instead of first overwriting the *_evbarm functions with own code,
and then calling them from the regular functions, directly put the
code into the regular functions.

No more functions from evbarm.conf are used now.
Some variables are still used!

Cleanup: make_filesystems is not used any longer, purge remains

PR/49596: mkimage: incorrect permissions on evbarm images

Use NetBSD.dist in our mtree specification to populate the top level
directories, etc.

For each generated file hand craft an mtree entry.

Remove specialdirs as NetBSD.dist creates /proc and /kern.

branches: 1.5.4; 1.5.6;
Include evbarm.conf as same as other conf files

evbarm.conf ensures ${mnt}/boot exists so that it avoids the error:
/home/builds/ab/HEAD/src/distrib/utils/embedded/mkimage: cannot create \
/tmp/mkimage.24444a/mnt/boot/cmdline.txt: directory nonexistent

After discussions with cristos regarding the previous commit, he
convinced me it was sufficient to define GZIP_CMD only in
distrib/utils/embedded/mkimage and not again in the config files
beagleboard.conf, rpi.conf, and rpi_inst.conf similar to how the
other variables $src, $release, $mnt, ... are only defined there.

Fix build release of evbarm which had been failing in mkimage
beagleboard_smp with the elusive message:

"gzip: can't stat: gzip: No such file or directory"

This was due to GZIP=gzip being defined in mkimage; we now use:

GZIP_CMD=${TOOL_GZIP:-gzip} # ${GZIP} is special to gzip(1)

as distrib/sets/sets.subr already does in these files as well:

distrib/utils/embedded/mkimage
distrib/utils/embedded/conf/beagleboard.conf
distrib/utils/embedded/conf/rpi.conf
distrib/utils/embedded/conf/rpi_inst.conf

branches: 1.2.6;
Fix an empty shell function here, per Greg Troxel. Apparently empty shell
functions are not 100% portable.

Add a new installer image for Raspberry PI to evbarm

Includes the following major changes:

1) Add new configmenu item to sysinst to allow creation of users at
post-install time.
2) Add an sshramdisk type to evbarm, which is a ramdisk with sshd
enabled, allowing users to install on a headless PI by sshing to the
device with the account "sysinst" password "netbsd" to begin the
installation. (Note, neither the account, nor the ssh setup are copied to
the finalized installation image)
3) Change mkimage to build a boot-only image, without the root filesystems.

Much of the sshramdisk code could be reused on other ports easily.

/etc/rc.d/cerctl_init: New script for certctl rehash in live images.

This is very limited -- it does not supplant postinstall to rehash
certificates on upgrade; it only runs certctl rehash if
/etc/openssl/certs is an empty directory, as you get in live images
not created with sysinst.

We could also have a more general-purpose way to run postinstall(8)
on first boot of an image, but that has a lot more moving parts to
think about, so let's start with this limited-scope low-risk
approach.

PR install/57629

XXX pullup-10

branches: 1.6.2;
Disable kernfs on live images -- it is not required.

Cleanup: make_filesystems is not used any longer, purge remains

PR/49596: mkimage: incorrect permissions on evbarm images

Use NetBSD.dist in our mtree specification to populate the top level
directories, etc.

For each generated file hand craft an mtree entry.

Remove specialdirs as NetBSD.dist creates /proc and /kern.

branches: 1.3.4; 1.3.12;
switch to makefs

branches: 1.2.2;
append to rc.conf, don't overwrite

Adjust mkimage to handle RPI. From skrll@

wii: Add standalone bootloader.

This adds "ppcboot.elf" to the Wii (evbppc) build, which can be placed on
the FAT partition of an SD card in the bootmii directory. The bootloader
doesn't have a user interface, it simply loads a kernel from the first
FFS partition it finds on the SD card.

Debug logs are printed to a USB Gecko device in either memory card slot
if present.

\\-__,------,___.
\\ __,---` NetBSD/evbppc Wii MINI boot
\\ `---,_. Revision 1.0 (Sun Nov 16 19:27:47 UTC 2025)
\\-,_____,.---`
\\
\\
\\

booting netbsd 7828064/-|+130520 [315696+305916]=0x82f350
[ 1.0000000] Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003,
[ 1.0000000] 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013,
[ 1.0000000] 2014, 2015, 2016, 2017, 2018, 2019, 2020, 2021, 2022, 2023,
[ 1.0000000] 2024, 2025
[ 1.0000000] The NetBSD Foundation, Inc. All rights reserved.
[ 1.0000000] Copyright (c) 1982, 1986, 1989, 1991, 1993
[ 1.0000000] The Regents of the University of California. All rights reserved.

[ 1.0000000] NetBSD 11.99.3 (WII) #207: Sun Nov 16 14:28:23 AST 2025
[ 1.0000000] jmcneill@berserk:/home/jmcneill/netbsd/obj/sys/arch/evbppc/compile/WII
[ 1.0000000] total memory = 90112 KB
[ 1.0000000] avail memory = 77008 KB
[ 1.0000000] mainbus0 (root): Nintendo Wii
...

wii: Start bluetooth by default

branches: 1.4.2;
wii: update wii.img ffs parameters

Use 4K block/frags and FFSv2 for Wii images.

branches: 1.3.2; 1.3.4;
wii: Add 128x48 icon to SD card image

build fix: use dd with count=1 for compat with NetBSD dd(1)

evbppc: Add initial support for the Nintendo Wii

Recognize MKPOSTFIX=no in mkimage

Remove duplicated code, handle minwrites in _normal the same way we handle
it in _gpt. Initial patch from jmmv@.

branches: 1.11.2;
/etc/rc.d/cerctl_init: New script for certctl rehash in live images.

This is very limited -- it does not supplant postinstall to rehash
certificates on upgrade; it only runs certctl rehash if
/etc/openssl/certs is an empty directory, as you get in live images
not created with sysinst.

We could also have a more general-purpose way to run postinstall(8)
on first boot of an image, but that has a lot more moving parts to
think about, so let's start with this limited-scope low-risk
approach.

PR install/57629

XXX pullup-10

branches: 1.10.2;
Disable kernfs on live images -- it is not required.

Fix fallout from mkimage rev 1.76.

For mkimage:

- Update "size" if auto-calculated.
- Use "dd bs=1" instead of non-portable "head -c".
- Some style nits.

For MD make_label() functions:

- Stop using "newsize" as image size in MB, use "size" instead.

Be more precise about exactly what fails when something does.

Relying upon set -e to abort things is sort of OK (it is not
a recommended option to use in general - too many odd special cases),
but only if user can work out from the "build failed" what actually
went wrong.

Tested only on amd64 build (for this, i386 is the same) - if anyone
has problems on builds for other systems, please let me know. However
the changes affect only failure paths, the most likely problem would
be for a build to fail to halt on an error, and I hope I have avoided
that. There should be no difference at all to error-free builds.

Fix previous so that the new generated rc.conf is picked up and that
any new new mount points (e.g. /proc and /kern) are generated.

While here increate the fs size so that postfix can actually build
/etc/mail/aliases.db

PR/49596: mkimage: incorrect permissions on evbarm images

Use NetBSD.dist in our mtree specification to populate the top level
directories, etc.

For each generated file hand craft an mtree entry.

Remove specialdirs as NetBSD.dist creates /proc and /kern.

fix image building:
- round up the total size of the disk image
- fix fdisk offset for netbsd ffs images

branches: 1.4.4; 1.4.6; 1.4.8;
merge more, and add an i386 image

remove swap; these days x86 machines don't need it.

these changes produce a bootable system under qemu, but its root is trashed.

Add preliminary support for creating x86 usb sticks with mkimage.
This is untested, and just a checkpoint of the work. Image looks
ok, but I have not tried if it boots.