On Tuesday 18 November 2008 10:26:26 Peter Steele wrote:
Is this something that can be done via sysinstall? If not, what's the
best alternative? This whole process is targeted to be on a PXE boot
server so we can configure our systems in a completely automated
hands-off manner. We have 200+
On Mon, Nov 17, 2008 at 03:56:26PM -0800, Peter Steele typed:
I'll have to check this out. I'm not getting anywhere with trying to
customize mfsroot with my current approach...
The goal we are trying to achieve btw is to make gmirror available
during an install so that the file systems are
I believe you modify /usr/src/release/${ARCH}/boot_crunch.conf to do
this.
I haven't actually tried though...
I think it would be possible to have a 'GEOM' menu that you can run
prior to fdisk, label, etc that would allow you to
do some basic stuff like this.
While the sysinstall code is a bit
What I've done in the past is skip sysinstall alltogether and just boot
of an NFS root. Then use custom scripts for the slicing/partitioning/
mirroring, copy a minimal system to disk and pkg_add the rest.
Would be nice to do all this with install.cfg though. Please let me
know
when you get this
On Wednesday 19 November 2008 02:25:12 Peter Steele wrote:
I believe you modify /usr/src/release/${ARCH}/boot_crunch.conf to do
this.
I haven't actually tried though...
I think it would be possible to have a 'GEOM' menu that you can run
prior to fdisk, label, etc that would allow you to
You wouldn't have to do so - you could just run a shell script from
sysinstall and do what you want.
That brings me back to my original problem. Yes, I can run a shell
script from sysinstall, but gmirror isn't available in mfsroot, and
adding gmirror to mfsroot isn't straightforward because it
On Sun, 16 Nov 2008 14:59:29 -0800
Peter Steele [EMAIL PROTECTED] mentioned:
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
I'm not sure, but probably the installation CD doesn't carry shared
libraries at all? All binaries in /stand are
static-linked ones.
Yeah, that is absolutely the problem--no shared libraries are available
when sysinstall is running.
You could also try scripts from mfsbsd project:
I'll have to check this out. I'm not getting anywhere with trying to
customize mfsroot with my current approach...
The goal we are trying to achieve btw is to make gmirror available
during an install so that the file systems are mirrored right from the
get-go, so that we can avoid having to go
I'll have to check this out. I'm not getting anywhere with trying to
customize mfsroot with my current approach...
The goal we are trying to achieve btw is to make gmirror available
during an install so that the file systems are mirrored right from the
get-go, so that we can avoid having to go
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
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
How does it fail?
There doesn't seem to be any error generated. Or at least I tried to
capture stderr and got nothing.
Is the binary you added statically linked?
The command I'm doing most of my testing with is gmirror. I pulled it
from one of our operation FreeBSD boxes, and it appears to be
13 matches
Mail list logo