Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

buildsys(1M)

mkboot(1M)

rc6(1M)

system(4)

ld(1)

sysm68k(2)

sysm88k(2)





   cunix(1M)                                                         cunix(1M)


   NAME
         cunix - configure a new bootable operating system

   SYNOPSIS
         cunix [-a "ld_args"] [-b boot_dir] [-c config_dir] [-d] [-e edtfile]
         [-f system] [-g] [-i loader_directive_file] [-j assembler] [-l
         link_ed]
         [-o outfile] [-r raw_disk] [-s script_file] [-v] [-z "as_args"] [-E]
         [-I]

   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.  The ICDDEV: field in the system(4) file
         directs cunix to incorporate an In-Core Disk (ICD) image within the
         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 format 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 working 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 sysm68ksym or
              sysm88ksym 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 sysm68ksym table is


   7/91                                                                 Page 1









   cunix(1M)                                                         cunix(1M)


              accessible through the sysm68k system call; the sysm88ksym table
              is accessible through the sysm88k system call.

         -e   Use the EDT data from edtfile rather than /stand/edt_data.

         -f   system specifies the file that contains configuration
              information;  the default is /stand/system.

         -g   Do not remove the config_dir/conf.o or config_dir/conf.s files
              after the bootable operating system has been created;  the
              default is to remove conf.o and conf.s.  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.

         -j   Use the assembler to assemble conf.s.  By default, as is invoked
              as if it had been typed as a command to the terminal.

         -l   Use the link_ed link editor to bind object files;  the link
              editor ld is used by default.  The PATH- variable is searched
              for the ld program.  See NOTES.

         -o   outfile specifies the output file name for the bootable
              operating system;  the default is /stand/unix_test.

         -r   The raw_disk where the root file system resides;  the default is
              /dev/rSA/disk1.

         -s   Run the script file after creating conf.s but before invoking
              the assembler.  Script_file may be a shell script or an
              executable object.  The script file may be used to massage
              conf.s before the assembler is invoked.  In this use,
              script_file must reference conf.s explicitly since cunix does
              not pass it as an argument to script_file.

         -v   Verbose mode on;  cunix displays all the modules and drivers
              being linked.  The default is verbose mode off.

         -z   Pass the specified "as_args" to the assembler.  The entire set
              of arguments must be enclosed in double quotes, with each
              argument surrounded by white space.  No flags are passed by
              default.




   Page 2                                                                 7/91









   cunix(1M)                                                         cunix(1M)


         -E   Use only the EDT data file.  Do not read the in-core EDT.
              Normally cunix reads the in-core EDT and then the EDT data file
              and combines them, ignoring entries in the data file that
              duplicate entries in the in-core EDT and replacing entries in
              the in-core EDT with corresponding entries from the data file,
              if they match on name and board fields, but differ otherwise.
              By default cunix reads /stand/edt_data for the data file.  Use
              the -e flag to change this.

         -I   Use only the in-core EDT.  Do not use the EDT data file.

   NOTES
         Do not execute a separate ld ... -o /stand/unix command for the
         operating system;  the output file is processed by cunix after
         loading. cunix calls the setrlimit system call to set the file size
         limit to infinity. It proceeds without complaint if setrlimit fails.

   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
         /dev/rSA/disk1 default location of root file system

   SEE ALSO
         buildsys(1M), mkboot(1M), rc6(1M), system(4).
         ld(1), sysm68k(2), sysm88k(2) in the Programmer's Reference Manual.
         System Administrator's Guide.




















   7/91                                                                 Page 3





Typewritten Software • bear@typewritten.org • Edmonds, WA 98026