Scripting sysinstall

Jeff Gold at
Fri Feb 15 23:06:32 UTC 2008

On Fri, Feb 15, 2008 at 12:14 PM, Jeff Gold < at> wrote:
>  When I invoke this sysinstall certainly seems busy -- it claims to be unpacking the
>  distribution set I specified -- but it doesn't actually accomplish
>  anything.  No boot loader is installed and no changes are made to the
>  partition table.

I'm still trying to figure this out, but I've got a few more details
that might be revealing for someone who understands FreeBSD and
sysinstall better than I do.  First, I'm not sure where the
distributions are being placed.  They don't appear to end up in the
live CD file system, as those have older time stamps and /usr/ports
doesn't exist before or after. There are no error messages, which
either means it "worked" in some strange way or the errors are
ignored.  There's nothing informative in /var/log/messages.  What

Second, I've added a packageAdd statement just to see what would
happen.  It fails with errors on md1 which I believe is mounted on
/var.  I think this means the package is being installed on the
current file system rather than the new system root.  I haven't yet
found any command in the sysinstall man page to redirect that.  Is
there one?

Finally, after the install (just like before) I see /dev/ad0, but
nothing resembling /dev/ad0s1a and friends.  And of course when I
attempt to boot afterward there is no boot loader, just a BIOS error
message.  Shouldn't the appropriate device nodes get added, either by
sysinstall or some deeper mechanism?

I'm still puzzled.  Has anyone else attempted this sort of thing or do
custom FreeBSD installations primarily use the network instead?


More information about the freebsd-questions mailing list