idbuild(1M) — Reliant UNIX 5.44c4

idbuild(1M)                                                     idbuild(1M)

NAME
     idbuild - build new system kernel

SYNOPSIS
     /etc/conf/bin/idbuild [-M | -S | -L | -MK | -KM | -SK | -KS | -LK |
     -KL]

DESCRIPTION
     This script builds a new Reliant UNIX system kernel using the current
     system configuration in etc/conf/. The script uses the shell variable
     $ROOT from the user's environment as its starting path. $ROOT should
     always be set to null, except for the special case of kernel develop-
     ment in a non-root source tree.

     Building a new Reliant UNIX system image consists of generating new
     system configuration files, then link-editing the kernel and device
     driver object modules in the etc/conf/pack.d object tree. To do this,
     idbuild calls idconfig(1M), which builds kernel configuration files,
     and idmkunix(1M), which processes the configuration files and link-
     edits a new Reliant UNIX system image.

     The system configuration files are built by processing the Master and
     System files representing device driver and tunable parameter specifi-
     cations. For the Reliant UNIX system the files etc/conf/cf.d/mdevice,
     and etc/conf/cf.d/mtune represent the Master information. The files
     etc/conf/cf.d/stune, and the files specified in etc/conf/sdevice.d/*
     represent the System information. The kernel also has file system type
     information defined in the files specified by etc/conf/sfsys.d/* and
     etc/conf/mfsys.d/*.

     Once configured, a lock file is set in etc/.newunix causing the new
     kernel to replace /unix on the next system shutdown (i.e. entry to the
     init 0 state). The new kernel will be executed on next system reboot.

OPTIONS
     -M      causes idbuild to produce a multiprocessor kernel.

     -S      causes idbuild to produce a single processor kernel.

             Warning: Only multiprocessor kernels can be created on an
             RM600.

     -L      causes idbuild to produce a multiprocessor debug kernel.

     -MK or -KM
             causes idbuild to retain configuration files conf.c, config.h,
             vector.c, fsconf.c, direct, and ifile files after a multipro-
             cessor kernel build.

     -SK or -KS
             causes idbuild to retain configuration files conf.c, config.h,
             vector.c, fsconf.c, direct, and ifile files after a single



Page 1                       Reliant UNIX 5.44                Printed 11/98

idbuild(1M)                                                     idbuild(1M)

             processor kernel build.

     -LK or -KL
             causes idbuild to retain configuration files conf.c, config.h,
             vector.c, fsconf.c, direct, and ifile files after a debug ker-
             nel build.

     Only one of these options can be specified at a time.

DIAGNOSTICS
     Since idbuild calls other system commands to accomplish system recon-
     figuration and link editing, it will report all errors encountered by
     those commands, then clean up intermediate files created in the pro-
     cess. In general, the exit value 1 indicates an error was encountered
     by idbuild.

     The errors encountered fall into the following categories:

          -  Master file error messages.

          -  System file error messages.

          -  Tunable file error messages.

          -  Compiler and Link editor error messages.

     All error messages are designed to be self-explanatory.

NOTE
     The command idbuild can only be called in multiuser mode on an RM600.

SEE ALSO
     uname(1), idinstall(1M), idtune(1M), mdevice(4), mfsys(4), mtune(4),
     sdevice(4), sfsys(4), stune(4).




















Page 2                       Reliant UNIX 5.44                Printed 11/98

Museum

Related Articles