Date: Sun, 16 Nov 2008 15:41:06 -0800 (PST) From: Nate Eldredge <neldredge@math.ucsd.edu> To: Peter Steele <psteele@maxiscale.com> Cc: freebsd-hackers@freebsd.org Subject: Re: How can I add new binaries to the mfsroot image? Message-ID: <Pine.GSO.4.64.0811161539450.1597@zeno.ucsd.edu> In-Reply-To: <2ACA3DE8F9758A48B8BE2C7A847F91F23B502B@polaris.maxiscale.com> References: <2ACA3DE8F9758A48B8BE2C7A847F91F23B502B@polaris.maxiscale.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 16 Nov 2008, Peter Steele wrote: > I want to make a custom FreeBSD install CD-ROM with additional commands > available in the mfsroot image. Adding the new commands to the image is > easy enough, and I've made an install.cfg file on the CD-ROM as well so > that when the CD runs the commands in install.cfg are automatically > executed. This all works, except none of the new binaries I add to the > mfsroot image run during the automated sysinstall session. If I > reference one of the default commands (the ones stored in /stand) they > run fine, but if I add a new FreeBSD binary to the /stand directory > (e.g. gmirror), the command fails. How does it fail? Is the binary you added statically linked? > What's weird is that I can open a fixit shell after the install.cfg > script fails and then run the same commands interactively and they work > fine. Why would work these commands work in an interactive fixit shell > but not during the automated sysinstall session? Wild guess: the shared libraries are present somewhere else on the CD, which perhaps is either not mounted or not pointed to by LD_LIBRARY_PATH or similar until the fixit shell is run. -- Nate Eldredge neldredge@math.ucsd.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0811161539450.1597>