Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 May 2004 12:37:43 +0100
From:      Daniel Bye <daniel.bye@psineteurope.com>
To:        questions@freebsd.org
Subject:   Re: sysinstall config question
Message-ID:  <20040524113743.GA44087@ip48.ops.uk.psi.com>
In-Reply-To: <20040524144732.3aeaab7b@tarkhil.over.ru>
References:  <20040524144732.3aeaab7b@tarkhil.over.ru>

next in thread | previous in thread | raw e-mail | index | archive | help

--6TrnltStXW4iwmi0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, May 24, 2004 at 02:47:32PM +0400, Alex Povolotsky wrote:
> Hello!
>=20
> According to sysinstall(8),=20
>=20
>      LOAD_CONFIG_FILE
>        If sysinstall is compiled with LOAD_CONFIG_FILE set in the envi-
>        ronment (or in the Makefile) to some value, then that value will
>        be used as the filename to automatically look for and load when
>        sysinstall starts up and with no user interaction required.  This
>        option is aimed primarily at large sites who wish to create a
>        single prototype install for multiple machines with largely iden-
>        tical configurations and/or installation options.
>=20
> However, attempt to make release as follows
>=20
> make release BUILDNAME=3D5.2.1-RELEASE CHROOTDIR=3D/var/release CVSROOT=
=3D/home/ncvs RELEASETAG=3DRELENG_5_2_1_RELEASE LOAD_CONFIG_FILE=3D"gw.conf"
>=20
> result in the following error:
>=20
> =3D=3D=3D> bin
> =3D=3D=3D> bin/cat
> install -s -o root -g wheel -m 555   cat /var/release/bin
> install: cat: No such file or directory
> *** Error code 71
>=20
> Stop in /usr/src/bin/cat.
> *** Error code 1
>=20
> Stop in /usr/src/bin.
> *** Error code 1
>=20
> while building release without LOAD_CONFIG_FILE builds just fine.
>=20
> I do not have a 4.X box with enough resources to try the same there; maybe
> someone could enlighten me? Or I should ask in -current?


My understanding from reading sysinstall(8) is that the sysinstall binary
needs to have LOAD_CONFIG_FILE set in the environment, not the release
build.

Try adding it to the Makefile for sysinstall, and see what happens...

However, I have recently set up a custom install script, which simply has
the default name, install.cfg.  As long as it is located in the root of your
mfsroot file system, sysinstall will load it.  If you don't have a
particular need to give it a different name, you might give it a go.

Dan

--6TrnltStXW4iwmi0
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAsd6H31B8YuHL9ZwRAk6vAJ90a5Er/wv0Sj+mJwMKqCfIFZfU9QCcCWT2
329EpTaZ+3n44kOzvCHRFL8=
=6Tp3
-----END PGP SIGNATURE-----

--6TrnltStXW4iwmi0--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040524113743.GA44087>