Very Computer

Hello All,

I am attempting to implement a jumpstart config.  The basic jumpstart
installation that I have works for installing the OS and slicing the
disks as defined.  I am trying to get some finish scripts to work to
install solstice disk suite and to copy some patches to the server
(not install them just copy).  I have the scripts written and they
work if I run them on my local machine. They are pretty basic scripts
(as my scripting abilities are also basic :) ), Ideally I would like
to have both scripts called from one script. But for now I will just
deal with getting one to work from the jumpstart load.  Here is the
script.

#!/bin/ksh

touch /a/noautoshutdown

BASEDIR=/a
SLASHMNT=${BASEDIR}/mnt
SD=/export/home/Jumpstart/Packages/SDS

mount -F nfs <jumpstart server>:${SD} ${SLASHMNT}

if [ $? != 0 ]; then
        exit 1
fi

#perform package add

echo "Installing package SUNWmdg.."
pkgadd -a ${SI_CONFIG_DIR}/noask_pkg -d ${SLASHMNT} -R ${BASEDIR}
SUNWmdg

...
...
etc...

When the finish script is getting called I get the following.

Executing JumpStart postinstall phase...
Executing finish script "Finish/pkg.add.fin".
nfs mount: <jumpstart server> : RPC: Rpcbind failure - RPC: Success
nfs mount: retrying: /a/mnt
nfs mount: <jumpstart server> : RPC: Rpcbind failure - RPC: Success
...
...

The mount point is shared out on the jumpstart server. Can anyone
point me in the right direction ?

Thanks in Advance

 > nfs mount: <jumpstart server> : RPC: Rpcbind failure - RPC: Success
 > nfs mount: retrying: /a/mnt
 > nfs mount: <jumpstart server> : RPC: Rpcbind failure - RPC: Success

Seems that the jump start server is unknown to the machine.

Use the IP address for <jumpstart server> .

To test you may create a finish script with only the command  "/sin/sh +e "

Than you'll get a shell (on the console) after the installation and you
can manually do the commands from your script and test them.

regards

Bernd