Looking at my history, I did:
./build.sh -O ../obj -T ../tools tools distribution kernel=MYCONFIG modules
./build.sh -O ../obj -T ../tools installmodules=/
cp -p /netbsd /onetbsd
cp /usr/obj/sys/arch/amd64/compile/MYCONFIG/netbsd /
shutdown -r now
/stand still has modules for both versions listed. Went go to install
the new userland after the reboot and it never got that far since
things started crashing. Rebooting back into onetbsd seems to work,
so I'm fairly certain that it didn't upgrade the userland yet, but
I'll double check.
On a side note, it would be really nice if the modules stuff got added
to https://www.netbsd.org/docs/guide/en/chap-updating.html#updating-procedure
so I don't have to keep referring to my old notes every time :)
-Dustin
On Mon, Feb 10, 2020 at 6:57 PM Kamil Rytarowski <n54%gmx.com@localhost> wrote:
On 11.02.2020 01:49, Dustin Marquess wrote:
I'm trying to upgrade a VM from a 9.99.10 install that was built
around Sep 2th to a 9.99.46 install compiled yesterday.
I installed the new kernel and modules and rebooted into the new
kernel / old userland. Once done, almost everything crashes with Bad
system call. So far "su -", "ls" and even the configure instance the
a build.sh install kicked off died with one.
Is this a known issue? I don't believe I missed a step in the upgrade
instructions...
Thanks!
-Dustin
Make sure that you upgraded your kernel and kernel modules before
installing new userland. The otherway around upgrade is not supported
and can break like it (there was an ABI change in struct statvfs).