SETUP_EXEC(8) — MAINTENANCE COMMANDS
NAME
setup_exec − install and export a client’s executables on a file server
SYNOPSIS
/usr/etc/install/script/setup_exec arch execpath kvmpath
DESCRIPTION
setup_exec is used to install a client’s executables on a file server. It installs both application and kernel architecture executables. It can be used to convert a standalone system into a file server. setup_exec is a forms-based utility that can be invoked directly, but it is also used by suninstall(8). It can only be executed by the super-user.
setup_exec can be used with a local tape drive attached to the server it is being run on, a remote tape drive attached to a machine on a net that the server has access to, or with the local floppy drive in the server. It cannot use a floppy drive on a machine on a net it has access to.
setup_exec also updates the /etc/exports file (see exportfs(8)) to include the execpath and kvmpath directories it has installed. It adds entries that export these directories with read-write permissions to all machines. If you wish to restrict access to these directories, you must edit the /etc/exports file. It then executes a ‘exportfs −a’ command. Note: this command will export all directories in the /etc/exports, you will have to run a ‘exportfs −u’ command to unexport the appropriate directories.
setup_exec keeps track of the software that is installed for architecture arch. If it is run again for the same architecture, setup_exec will prompt with:
Do you want to use existing software list [y/n]?
Answer with a y if you want to install the same software that was installed last time or a n if you want to change the software that will be installed.
The arch argument specifies the kernel architecture of the client whose executables are being installed. to install (for instance, sun3x, sun4, sun4c...). See arch(1) for further explanation of kernel and application architecture and examples of valid application architectures. When run with no arguments, setup_exec displays a usage line that includes the proper format of the arch argument for each supported application architecture.
execpath is the full pathname of the application architecture executables directory. When the client’s application architecture is the same as the server’s, this path is /usr and /export/exec/appl_arch is a symbolic link to /usr.
kvmpath is the full pathname of the kernel architecture executables directory. When the client’s kernel architecture is the same as the server’s, this path is /usr/kvm and /export/exec/kvm/kernel_arch is a symbolic link to /usr/kvm.
EXAMPLE
This example shows how to install a Sun-4 clients.
example# setup_exec sun4 /export/exec/sun4 /export/exec/kvm/sun4
FILES
/etc/hosts hosts database
/etc/ethers database of hostnames and Ethernet addresses
/etc/exports database of exported file systems
/usr/etc/install/files/extractlist.arch
record of extracted categories for application architecture arch
/usr/etc/install/files/suninstall.log
history of systems installed/extracted after initial installation
SEE ALSO
exports(5), exportfs(8), setup_client(8), suninstall(8)
Installing the SunOS
DIAGNOSTICS
All paths must start with /.
execpathand kvmpath must be full paths starting with a ‘/’.
invalid architecture type “arch”.
An unsupported value for arch was supplied.
Unable to open /etc/exports.
The file /etc/exports could not be opened. Check to make sure it exists.
WARNING: run /usr/etc/exportfs if this is 4.0 SunOS.
/usr/etc/exportfs could not be found to export the directories it added to /etc/exports. /usr/etc/exportfs must be run before the directories are available to any clients.
Do you want to use existing software list [y/n]?
Do you want to install the software that was installed the last time setup_exec was run for this kernel architecture? Type y if you do, n if you do not.
Load release tape n for architecture arch and press <RETURN>:
Load the specified tape and press RETURN to continue.
insert suninstall diskette n for “arch”, then press <return>:
Load the specified diskette and press RETURN to continue.
Sun Release 4.0 — Last change: 2 May 1989