Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ admkernel(1M) — DG/UX 5.4R3.00

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

cc(1)

config(1M)

ld(1)

probedev(1M)

sysadm(1M)

system(4)



admkernel(1M)                  DG/UX 5.4R3.00                  admkernel(1M)


NAME
       admkernel - manipulate the system's kernel

SYNOPSIS
       admkernel -o autoconfigure [ -C ] [ -B client-boot-device ] [ -d
                 build-directory ] system-name

       admkernel -o build system-name

       admkernel -o install [ -Cr ] [ -d build-directory ] system-name

       admkernel -o link [ -c client-list ] system-name

       admkernel -o list [ -qv ] [ -d build-directory ] [ system-name ...  ]

DESCRIPTION
       admkernel builds and installs system kernels.

       A system's kernel is the image which is loaded into memory when
       booting the system.  The admkernel command manages this system's
       kernel and may also manage the kernels of any operating system
       clients of this system.

   Operations
       autoconfigure
                 Create a system file in the build-directory which lists the
                 hardware devices currently attached to the system, as well
                 as the pseudo-devices and configuration variables of any
                 loaded packages.  The resulting system file, system.system-
                 name, can be used to build a custom kernel for the system.

       build     Build a new system kernel from an existing system file in
                 the build-directory.  This includes running the config(1M)
                 program on a system file and compiling the resulting file
                 (with cc(1) and ld(1)) with the kernel libraries into a
                 bootable kernel image, called dgux.system-name.  Note that
                 kernels can only be built for the PRIMARY release area.

       install   Copy a kernel from the build-directory into some other
                 directory where it can be booted as the system's kernel.
                 If the operation is successful, the kernel is deleted from
                 the build directory.

       link      Link a kernel to the default kernel (/dgux) for this host
                 or for clients of this host.

       list      Display information about system-names.  If there is no
                 system-name or the system-name is all, the list of valid
                 system-names is displayed.

   Options
       -B client-boot-device
                 Configure the OS client kernel to boot from the client-
                 boot-device device.  This option is meaningful only when



Licensed material--property of copyright holder(s)                         1




admkernel(1M)                  DG/UX 5.4R3.00                  admkernel(1M)


                 used with -C.  The default is dgen().

       -C        Perform the operation for an operating system client.  For
                 the autoconfigure operation, this option indicates that the
                 kernel will be used by an operating system client.  For the
                 install operation, this option indicates that the kernel
                 will be installed for an operating system client of this
                 host.

       -c client-list
                 Link a kernel as the default kernel for each client in
                 client-list.  client-list is either a comma-separated list
                 of clients, or may be "all" to indicate that the kernel
                 should be linked for all clients of this host.

       -d build-directory
                 The directory in which system files and new kernels reside.
                 The default is /usr/src/uts/aviion/Build.

       -r        Remove the old kernel ( dgux.system-name ), if it exists.
                 Without this option, the old kernel is saved to
                 dgux.system-name.old before the new kernel is installed.

       -q        Quiet.  Omit header lines from the output of the list
                 operation.

       -v        Verbose.  Include header lines in the output of the list
                 operation.  This option is enabled by default.

EXAMPLES
       To generate a system file based on the system's current
       configuration, use

            admkernel -o autoconfigure aviion

       To build, install, and link a kernel based on the "aviion" system
       file, use

            admkernel -o build aviion
            admkernel -o install aviion
            admkernel -o link aviion

       which builds dgux.aviion and links it to /dgux.

       To build, install, and link a kernel for two diskless clients of this
       host, first create /usr/src/uts/aviion/Build/system.diskless with the
       appropriate parameters, then use these command lines

            admkernel -o build diskless
            admkernel -o install -C diskless
            admkernel -o link -c myclient,yourclient diskless






Licensed material--property of copyright holder(s)                         2




admkernel(1M)                  DG/UX 5.4R3.00                  admkernel(1M)


ENVIRONMENT VARIABLES
       Several environment variables are used to control which tools are
       used for building new kernels.  Some of the more useful variables are
       listed below.

       CC        Name of the compiler, with its options, to use when
                 compiling the configuration file into an object file.  The
                 default is "/usr/bin/gcc -mno-underscores".

       LD        Name of the linker, with its options, to use when linking
                 the kernel libraries to form the kernel image.  The default
                 is "/usr/bin/ld -x -F 0555".

       LIB_DIR   Directory where kernel libraries are found.  Define this
                 variable to build with a non-default set of libraries.  The
                 default is "/usr/src/uts/aviion/lb".

       You should exercise great care when defining these variables in your
       environment, because some combinations of settings may cause the
       resulting kernel image to be unbootable.

FILES
       /usr/src/uts/aviion/Build
                 Build directory.

       /usr/src/uts/aviion/cf
                 Directory containing prototype system files.

       /dgux.system-name
                 Name of the installed kernel for this host.

       /srv/release/PRIMARY/_Kernels/dgux.system-name
                 Name of the installed kernel for operating system clients
                 of this host.

OUTPUT
       The list operation displays the system name and date of last
       modification for each of the system-names.

DIAGNOSTICS
   Warnings
        -  The file system.system-name does not exist.  It will be created
           from the prototype files in /usr/src/uts/aviion/cf.

   Errors
        -  There is no C compiler on the system.

        -  One of the necessary directories under /usr/src/uts/aviion is
           missing or incomplete.

        -  The kernel failed to configure (with config(1M)) or failed to
           link (with ld(1)).

        -  One of the clients in the client-list does not exist.



Licensed material--property of copyright holder(s)                         3




admkernel(1M)                  DG/UX 5.4R3.00                  admkernel(1M)


   Exit Codes
        0     The operation was successful.

        1     The operation was unsuccessful.

        2     The operation failed due to access restrictions.

        3     There was an error in the command line.

SEE ALSO
       cc(1), config(1M), ld(1), probedev(1M), sysadm(1M), system(4).

NOTES
       The autoconfigure operation uses probedev(1M) to determine which
       hardware devices to include in the system file.

       The autoconfigure and build operations require write permission in
       the build-directory1.  The install and link operations require write
       permission in the target root directory.  Normally, these four
       operations require superuser privilege.





































Licensed material--property of copyright holder(s)                         4


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