sysinstall config question
Hello! According to sysinstall(8), 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. However, attempt to make release as follows make release BUILDNAME=5.2.1-RELEASE CHROOTDIR=/var/release CVSROOT=/home/ncvs RELEASETAG=RELENG_5_2_1_RELEASE LOAD_CONFIG_FILE=gw.conf result in the following error: === bin === bin/cat install -s -o root -g wheel -m 555 cat /var/release/bin install: cat: No such file or directory *** Error code 71 Stop in /usr/src/bin/cat. *** Error code 1 Stop in /usr/src/bin. *** Error code 1 while building release without LOAD_CONFIG_FILE builds just fine. 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? -- Alex. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysinstall config question
On Mon, May 24, 2004 at 02:47:32PM +0400, Alex Povolotsky wrote: Hello! According to sysinstall(8), 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. However, attempt to make release as follows make release BUILDNAME=5.2.1-RELEASE CHROOTDIR=/var/release CVSROOT=/home/ncvs RELEASETAG=RELENG_5_2_1_RELEASE LOAD_CONFIG_FILE=gw.conf result in the following error: === bin === bin/cat install -s -o root -g wheel -m 555 cat /var/release/bin install: cat: No such file or directory *** Error code 71 Stop in /usr/src/bin/cat. *** Error code 1 Stop in /usr/src/bin. *** Error code 1 while building release without LOAD_CONFIG_FILE builds just fine. 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 pgpG2OeCMnaCg.pgp Description: PGP signature
Re: sysinstall config question
On Mon, 24 May 2004 12:37:43 +0100 Daniel Bye [EMAIL PROTECTED] wrote: 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 DB Try adding it to the Makefile for sysinstall, and see what DB happens... DB 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. DB If you don't have a particular need to give it a different name, you DB might give it a go. Thanks; will try it. WHat is the correct way to add install.cfg? Should it jut be put into /usr/src/release before build? -- Alex. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sysinstall config question
On Mon, May 24, 2004 at 05:48:21PM +0400, Alex Povolotsky wrote: On Mon, 24 May 2004 12:37:43 +0100 Daniel Bye [EMAIL PROTECTED] wrote: 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 DB Try adding it to the Makefile for sysinstall, and see what DB happens... DB 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. DB If you don't have a particular need to give it a different name, you DB might give it a go. Thanks; will try it. WHat is the correct way to add install.cfg? Should it jut be put into /usr/src/release before build? 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 pgpi3Ndp8E7Z3.pgp Description: PGP signature
