Should build.sh install=/foo generate a "complete" installation?

Chris Hanson <[email protected]> Sat, 5 Jul 2025 19:12:39 -0700
Newsgroups gmane.os.netbsd.devel.installation
Message-ID <[email protected]>
--Apple-Mail=_66A6B1EC-87D1-44DB-A4A5-96D5A1599AB8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I=E2=80=99ve just used =E2=80=9Cbuild.sh install=E2=80=9D for the first =
time in quite a while=E2=80=94the last time was when 9.0 was =
current=E2=80=94to set up an NFS root directory for a 64-bit SPARC =
system. I remember it working in the past to set up a =
full-but-not-yet-configured installation of NetBSD; today, however, it =
didn=E2=80=99t put things in place like the default /etc/passwd, =
/etc/groups, or /etc/rc.conf so actually setting up and configuring the =
system from a newly-built NetBSD seems like it=E2=80=99ll be difficult.

Specifically, I used

    ./build/sh \
        -m sparc64 \
        -T /usr/tools-10/sparc64 \
        -O /usr/obj-10/sparc64 \
        -x -U -u \
        ${command}

three times to build (my local branch of) netbsd-10, with ${command} =
producing in order:

    tools
    kernel=3DGENERIC distribution
    install=3D/export/NetBSD/10.1/root/ultra60

to build tools for sparc64, to build a kernel for sparc64, and then to =
install it to the NFS-exported root directory that I want to use for my =
Sun Ultra 60.

Upon doing the install to an empty directory, I get failures in the =
following post-install checks:

  atf autofsconfig bluetooth ddbonpanic defaults dhcpcd envsys =
fontconfig
  gid gpio iscsi makedev mtree named opensslcertsconf opensslcertsrehash
  pam periodic pf pwd_mkdb rc ssh uid

This=E2=80=A6 doesn=E2=80=99t seem right? Is there a different way that =
I should set up such a directory? I don=E2=80=99t want to go through =
sysinst for every single system.

  -- Chris


--Apple-Mail=_66A6B1EC-87D1-44DB-A4A5-96D5A1599AB8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;">I=E2=80=99ve =
just used =E2=80=9Cbuild.sh install=E2=80=9D for the first time in quite =
a while=E2=80=94the last time was when 9.0 was current=E2=80=94to set up =
an NFS root directory for a 64-bit SPARC system. I remember it working =
in the past to set up a full-but-not-yet-configured installation of =
NetBSD; today, however, it didn=E2=80=99t put things in place like the =
default <font face=3D"Courier New"><span style=3D"text-shadow: =
none;">/etc/passwd</span></font>, <font face=3D"Courier New"><span =
style=3D"text-shadow: none;">/etc/groups</span></font>, <font =
face=3D"Courier New"><span style=3D"text-shadow: none;">or =
/etc/rc.conf</span></font>&nbsp;so actually setting up and configuring =
the system from a newly-built NetBSD seems like it=E2=80=99ll be =
difficult.<div><br></div><div>Specifically, I =
used</div><div><br></div><div><font face=3D"Courier New">&nbsp; &nbsp; =
./build/sh \</font></div><div><font face=3D"Courier New">&nbsp; &nbsp; =
&nbsp; &nbsp; -m sparc64 \</font></div><div><font face=3D"Courier =
New">&nbsp; &nbsp; &nbsp; &nbsp; -T /usr/tools-10/sparc64 =
\</font></div><div><font face=3D"Courier New">&nbsp; &nbsp; &nbsp; =
&nbsp; -O /usr/obj-10/sparc64 \</font></div><div><font face=3D"Courier =
New">&nbsp; &nbsp; &nbsp; &nbsp; -x -U -u \</font></div><div><font =
face=3D"Courier New">&nbsp; &nbsp; &nbsp; &nbsp; =
${command}</font></div><div><br></div><div>three times to build (my =
local branch of) <font face=3D"Courier New">netbsd-10</font>, with <font =
face=3D"Courier New">${command}</font> producing in =
order:</div><div><br></div><div><font face=3D"Courier New">&nbsp; &nbsp; =
tools</font></div><div><font face=3D"Courier New">&nbsp; &nbsp; =
kernel=3DGENERIC distribution</font></div><div><font face=3D"Courier =
New">&nbsp; &nbsp; =
install=3D/export/NetBSD/10.1/root/ultra60</font></div><div><br></div><div=
>to build tools for <font face=3D"Courier New"><span style=3D"text-shadow:=
 none;">sparc64</span></font>, to build a kernel for <font face=3D"Courier=
 New"><span style=3D"text-shadow: none;">sparc64</span></font>, and then =
to install it to the NFS-exported root directory that I want to use for =
my Sun Ultra 60.</div><div><br></div><div>Upon doing the install to an =
empty directory, I get failures in the following post-install =
checks:</div><div><br></div><div><font face=3D"Courier New">&nbsp; atf =
autofsconfig bluetooth ddbonpanic defaults dhcpcd envsys =
fontconfig</font></div><div><font face=3D"Courier New">&nbsp; gid gpio =
iscsi makedev mtree named opensslcertsconf =
opensslcertsrehash</font></div><div><font face=3D"Courier New">&nbsp; =
pam periodic pf pwd_mkdb rc ssh =
uid</font></div><div><br></div><div>This=E2=80=A6 doesn=E2=80=99t seem =
right? Is there a different way that I should set up such a directory? I =
don=E2=80=99t want to go through <font face=3D"Courier New"><span =
style=3D"text-shadow: none;">sysinst</span></font>&nbsp;for every single =
system.</div><div><br></div><div>&nbsp; -- =
Chris</div><div><br></div></body></html>=

--Apple-Mail=_66A6B1EC-87D1-44DB-A4A5-96D5A1599AB8--