From owner-freebsd-questions@FreeBSD.ORG Mon May 24 07:34:54 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ACB5116A4CE for ; Mon, 24 May 2004 07:34:54 -0700 (PDT) Received: from md1.psixpress.com (md1.psixpress.com [154.32.105.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2275E43D31 for ; Mon, 24 May 2004 07:34:54 -0700 (PDT) (envelope-from danielby@ip48.ops.uk.psi.com) Received: from ip48.ops.uk.psi.com (ip48.ops.uk.psi.com [154.8.22.48]) by md1.psixpress.com (MOS 3.4.4-GR) with ESMTP id BCO50805 (AUTH via LOGINBEFORESMTP); Mon, 24 May 2004 15:34:20 +0100 (BST) Received: from danielby by ip48.ops.uk.psi.com with local (Exim 4.34; FreeBSD) id 1BSGXG-000Enf-S5 for freebsd-questions@freebsd.org; Mon, 24 May 2004 15:34:38 +0100 Date: Mon, 24 May 2004 15:34:38 +0100 From: Daniel Bye To: freebsd-questions@freebsd.org Message-ID: <20040524143438.GB44087@ip48.ops.uk.psi.com> Mail-Followup-To: freebsd-questions@freebsd.org References: <20040524144732.3aeaab7b@tarkhil.over.ru> <20040524113743.GA44087@ip48.ops.uk.psi.com> <20040524174821.7fe7a925@tarkhil.over.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wzJLGUyc3ArbnUjN" Content-Disposition: inline In-Reply-To: <20040524174821.7fe7a925@tarkhil.over.ru> User-Agent: Mutt/1.4.2.1i Subject: Re: sysinstall config question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2004 14:34:54 -0000 --wzJLGUyc3ArbnUjN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 24, 2004 at 05:48:21PM +0400, Alex Povolotsky wrote: > On Mon, 24 May 2004 12:37:43 +0100 > Daniel Bye wrote: >=20 >=20 > DB> My understanding from reading sysinstall(8) is that the sysinstall > DB> binary needs to have LOAD_CONFIG_FILE set in the environment, not > DB> the release build. > DB>=20 > DB> Try adding it to the Makefile for sysinstall, and see what > DB> happens... > DB>=20 > DB> However, I have recently set up a custom install script, which > DB> simply has the default name, install.cfg. As long as it is located > DB> in the root of your mfsroot file system, sysinstall will load it.=20 > DB> If you don't have a particular need to give it a different name, you > DB> might give it a go. >=20 > Thanks; will try it. >=20 > WHat is the correct way to add install.cfg? Should it jut be put into /us= r/src/release before build? >=20 Maybe that would work - but it's not how I'm doing it. I am building a custom mfsroot image, into which I install statically linked binaries etc, as well as a copy of my install.cfg. This has the advantage of being easy to modify - if you need to alter the install.cfg, you don't have to completely reblow your release build; you can just mount the mfsroot image, and edit the file like a normal file. Something like this should work for you: # gunzip /path/to/release/mfsroot.gz # mdconfig -a -t vnode -f /path/to/release/mfsroot -u 0 # mount /dev/md0 /mnt (copy your custom install.cfg to /mnt) # umount /mnt # mdconfig -d -u 0 Your imstall.cfg now resides in the root of the mfsroot image, and will be picked up by sysinstall when it starts at boot. HTH, Dan --wzJLGUyc3ArbnUjN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAsgf+31B8YuHL9ZwRAg8CAJ9ac6PKQOG28kKGC5TMXgGCmePhvACfT1NV qPGau9pqrHLpl+JCMXMd1Ys= =9KbQ -----END PGP SIGNATURE----- --wzJLGUyc3ArbnUjN--