cunix(1M) MISC. REFERENCE MANUAL PAGES cunix(1M)
NAME
cunix - configure a new bootable operating system
SYNOPSIS
cunix [-a "ld_args"] [-b boot_dir] [-c config_dir] [-d] [-f
system] [-g]
[-i loader_directive_file] [-l link_ed] [-o outfile] [-r
raw_disk] [-v]
DESCRIPTION
The cunix command creates a new bootable operating system
file from the object files (drivers) specified in the given
system file. The configuration of a new bootable operating
system is usually done when new hardware or software is
added to or removed from the system; most frequently it is
done during a powerup or reboot of the system. The cunix
command allows this procedure to be performed at the user
level, without a powerdown or system reboot. The options to
cunix also allow the user to create customized input files
for the configuration process, and to choose the location
for the resulting bootable operating system. Both COFF and
ELF format object files can be used as input to cunix. The
options to cunix are as follows:
-a Pass the specified ld_args as arguments to the link
editor; the entire set of arguments must be enclosed
in double quotes, with each argument surrounded by
white space. By default (no -a specified), -x is
passed to the link editor as an argument for COFF for-
mat object files (directs the link editor to omit local
symbols from the output symbol table, saving some space
in the output file); if one or more object files is in
ELF format, then no loader arguments are passed by
default. The link editor ld is used by default, unless
another is specified with the -l option (see below).
-b boot_dir specifies the directory where driver object
files reside; the default is /boot.
-c config_dir specifies the directory that contains work-
ing files for cunix; the default is /config.
-d Build the operating system with debug mode on; the
default is debug mode off. Debug mode populates the
sys3bsym symbol table with symbols from the kernel
object file and drivers specified in the system file.
The -d option causes cunix to use more disk space and
time. The sys3bsym table is accessible through the
sys3b system call.
-f system specifies the file that contains configuration
information; the default is /stand/system.
Last change: Essential Utilities 1
cunix(1M) MISC. REFERENCE MANUAL PAGES cunix(1M)
-g Do not remove config_dir/conf.o file after the bootable
operating system has been created; the default is to
remove conf.o. The directory config_dir is either
/config or the directory specified by -c, above.
-i loader_directive_file to be used for configuration; a
loader_directive_file specifies memory locations for
loading the operating system at boot time. A
loader_directive_file for a COFF system is called an
ifile, while a loader_directive_file for an ELF system
is called a mapfile. Normally, it is not necessary to
specify a loader_directive_file. Only use the -i
option with a custom loader_directive_file.
-l Use the link_ed link editor to bind object files; the
link editor ld is used by default. See NOTES.
-o outfile specifies the output file name for the bootable
operating system; the default is /stand/unixtest.
-r The raw_disk where the root file system resides; the
default is /dev/rSA/disk1.
-v Verbose mode on; cunix displays all the modules and
drivers being linked. The default is verbose mode off.
NOTES
Do not execute a separate ld ... -o /stand/unix command for
the operating system; the output file is processed by cunix
after loading.
FILES
/boot_dir/* drivers to be configured into the operating
system
/config_dir/conf.o
object file created by cunix
/config_dir/ifile*
loader directive file(s) for COFF system
/config_dir/mapfile*
loader directive file(s) for ELF system
/stand/system system file
/stand/unix bootable operating system
/usr/bin/ld default link editor
/dev/rSA/disk1 default location of root file system
SEE ALSO
buildsys(1M), mkboot(1M), rc6(1M), system(4).
ld(1), sys3b(2) in the Programmer's Reference Manual.
System Administrator's Guide.
Last change: Essential Utilities 2