Re: ramdisk-zfsroot: pool detection and configurable boot fs

On 17/08/2026 13:48, Martin Husemann wrote:
> In case you have already done the "build.sh build" (or simmilar) step:
> the nbmake-$arch file is created in the ${TOOLDIR}/bin path, where
> $TOOLDIR comes from the -T argument to build.sh (or is auto-generated
> from the $OBJDIR).
Thank you for this, I didn't know about build.sh so this got me a few
steps ahead.  However it isn't really clear to me what needs to be built
before I can build the ramdisk.  I needed `nbmake-amd64 includes` too,
but after that I didn't understand how to continue:

	$ nbmake-amd64
	[…]
	nbmake: don't know how to make ~/obj/destdir.amd64/usr/mdec/boot. Stop

In the end I just built the release target, of which these ramdisks are
a part.  This took nearly two days, but it worked.  However, after this
I attempted to replace src/distrib/common/zfsroot.rc with my modified 
version and rebuild, but the resulting ramdisk still had the original
file in it.  I had to replace it in src/distrib/amd64/ramdisks/ramdisk-
zfsroot/work/etc, and I can't figure out how to rebuild that directory.
I tried removing the whole work directory but that just made building
the ramdisk through nbmake-amd64 fail.

To me it seems that the Makefile in ramdisk-zfsroot assumes some things 
to be built already?

This would mean that I need to compile a fresh release every time I want 
to test a modification to the rc script.  At this point I gave up and 
returned to just using the prebuilt ramdisk and mounting it through a 
vnd device to replace the rc script in it.

--
Jørn Åne