NAME

doconfig − a program to aid system configuration

SYNOPSIS

/usr/sbin/doconfig [-c config_file] [-dn] [ ∗L-e ed_script]

FLAGS

The doconfig program supports the following flags:

−cThe name of the existing configuration file (config_file) must be supplied without specifying the pathname.  The name of the configuration file is usually the system name.  A new kernel is built using the existing config_file file and config_file.list file.  If there is no config_file.list file and a .product.list file exists, doconfig will copy the .product.list file to the config_file.list file.  These files must exist in the /sys/conf directory. 

−dSpecifies that only device special files are created. 

−eWhen specified, the configuration file is edited by the ed script before building the new kernel. 

−nThis option builds a network bootable kernel for Dataless Management Services (DMS) clients.  When specified, the -n option invokes pmerge(8) which builds a stripped network bootable kernel called .vmunix.  The dataless management utility, dmu(8), invokes this option when the configuration phase is run on a DMS environment. 

DESCRIPTION

The doconfig shell script creates a new or modifies an existing system configuration file for a new system kernel.  The script prompts you for the configuration file name. 

Whether the configuration file is built or not, the script then allows you to edit, configure, and build until both the configuration and the kernel build run without errors.  Additional runs of doconfig can be made to tune the configuration further. 

When new hardware is added to a system, the configuration file should be updated to reflect the new system configuration.  When updating an existing configuration file or creating a new configuration file with doconfig, the system must be operating the generic kernel or new hardware might not be found.  To successfully complete the doconfig process, follow these steps:

     1.Log on as root or become superuser. You must be superuser to execute the doconfig script. 

     2.Save a copy of the running kernel. If there are disk space constraints, you can save the kernel in a file system other than root. For example to copy the kernel to the /usr directory, issue the following command:

# cp /vmunix /usr/vmunix.save

     3.Install the generic kernel as the running kernel and reboot the system by using the cp and shutdown commands as follows:

# cp /genvmunix /vmunix
# /usr/sbin/shutdown -r +5 "Shutting down to build new kernel"

     4.Log on as root and shutdown the system to single-user mode as follows:

# /usr/sbin/shutdown +1

     5.Mount the /usr file system:

# mount /usr

     6.Run the doconfig script as follows:

# /usr/sbin/doconfig

The doconfig program then prompts you for information about your system configuration. 

     7.Type yes when the doconfig program asks if you want to edit the configuration file only if you need to make additional changes. The doconfig program then invokes the editor specified by the EDITOR environment variable. 

     8.The doconfig program builds the new kernel.  When the doconfig program finishes, it prints a message showing the path and location of the new vmunix kernel. 

     9.Move the new vmunix (from the message noted above) to /vmunix as follows:

# mv /sys/DECOSF/vmunix /vmunix

If you used the -n option, you must move .vmunix as well. 

     10.Reboot the system as follows:

# /usr/sbin/shutdown -r now

If the new vmunix fails to boot, you can recover by using the following procedure:

     1.Boot the generic kernel (/genvmunix) to single-user mode using the appropriate boot command for your system. If you are unsure of the command syntax, System Administration provides information on booting your system. 

     2.Check all local file systems using the fsck command with the -p option as follows:

# fsck -p

     3.Write-enable the root file system using the mount command with the -u option as follows:

# mount -u /

     4.If you want to revert to the vmunix kernel saved in step 2, mount the /usr file system, copy the saved kernel to the root file system, and reboot as follows:

# mount /usr
# cp /usr/vmunix.save /vmunix
# shutdown -r now

If you want to continue trying to build a bootable kernel, bring the system up to multiuser mode by issuing a CTRL/D as follows:

# CTRL/D

Proceed to step 4. 

FILES

/sys/conf/config_file

Specifies the system configuration file, where config_file is usually the name of the system. 

/sys/conf/config_file.list

Specifies the optional configuration file that is used by kernel layered products to extend the system configuration file.  This file can be modified to remove kernel layered product entries by deleting or commenting out (#) specific entries. 

/sys/conf/.product.list

Specifies the optional configuration file that is used by kernel layered products to register their configuration file requirements.  This file is used as the basis for the config_file.list file and should not be modified. 

/sys/system_name/.vmunix

Specifies the name of the network bootable kernel for DMS clients. 

RELATED INFORMATION

Commands: ed(1), config(8), pmerge(8), dmu(8)
Installation Guide
System Administration
Sharing Software on a Local Area Network