RECONFIG(1M)
Series 300 Only
NAME
reconfig − configure an HP-UX system
SYNOPSIS
/etc/reconfig [−m]
Remarks:
reconfig is implemented on the Series 300 only.
DESCRIPTION
Reconfig provides a means for system upgrade in the following areas:
User Configurations:
• Adding new users to the system
• Deleting existing users from the system
• Setting up user access to the system
Workstation Configurations:
• Adding support for terminals and modems
• Adding line printer support to the system
• Building and customizing new operating systems
Cluster Configurations (see DEPENDENCIES below for details):
• Setting up a cluster environment
• Adding a diskless cluster node
• Removing a diskless cluster node
Reconfig provides a useful, easy-to-use tool for upgrading and customizing HP-UX systems to match particular needs. Thus, upgrading an existing system to add new users, add line printers, or set up a cluster becomes a simple task.
Reconfig is a menu-driven command that is easy to use, even with little knowledge. Once a menu is displayed, the following rules apply:
Softkey Label Definition or Use
HELP Displays information describing your currently available options.
PREVMENU Immediately exits the current menu and returns to the previous menu. No configuration information associated with the current menu is processed, and any modified values are destroyed.
NEXT / PREVIOUS Moves cursor to next or previous choice on multiple-choice action menu or field.
QUIT Exits reconfig.
RESTORE restores all fields in the current menu to their original (default) values before any values were changed.
SELECT Initiates the configuration action associated with the current cursor position (highlighted field).
Many menus also prompt for inputs. Each input is terminated by pressing [RETURN] or by pressing one of the displayed softkeys. To select a displayed default value from the field associated with a given prompt, press [RETURN] without typing an entry.
Some fields offer multiple choices where all valid choices are displayed simultaneously and the default choice is displayed following the input prompt. Type the preferred choice and press [RETURN] or use the NEXT or PREVIOUS softkey to display the next/previous choice then press SELECT or [RETURN] when the correct option is reached.
When responding to prompts that expect a yes/no answer, use y or n or yes or no in any combination of uppercase or lowercase letters followed by [RETURN].
Some menus (such as adding users) cycle repeatedly so you can perform the operation more than once in succession. To exit such menus, press PREVMENU. Any completed configurations associated with the cycling menu are left intact. If PREVMENU is pressed before a cycle is completed, any partial configurations are abandoned without altering system configuration.
If the −m option is used, a special mode is used that does not produce escape-code sequences. This option is useful when using terminals that do not support standard HP terminal escape-code sequences; that is, terminals that are not officially supported by HP-UX.
This mode of operation is the same as normal operation with the following exceptions:
Menus offering a choice of actions to perform identify each action with an associated number or letter. To choose an option, press the number or letter (uppercase or lowercase), then press [RETURN].
The QUIT, RESTORE, PREVMENU, and HELP softkeys are replaced with the letters q, r, p, and h, respectively. To select one, press the correct letter followed by [RETURN].
When prompted for a choice in a multiple-choice field, type the corresponding number or letter or type in the choice itself, then press [RETURN].
When a new user is added to the system, the password file /etc/passwd and the group file /etc/group are both updated to reflect the addition of the new user. At the same time, a home directory is created in the /users directory.
When an existing user is deleted from the system, the password file /etc/passwd and the group file /etc/group will both be updated to reflect the fact that the user no longer has access privileges to the system. The users home directory, and all files contained therein, will be deleted if that option is specified.
When setting up user access to the system, you can choose whether or not a user login is required. If login is required, the system must operate in init state 2 (multi-user state) and each user must be known to the system (use the reconfig option for adding new users). If login is not required, the system must operate in init state 1 (single-user state), and the system starts running in a the selected shell (default is PAM -- Personal Applications Manager) after power-up.
When remote terminal support is added for a new port, the /etc/inittab file will be updated so that the next time the system is powered up a getty will automatically be started for the specified port. Any required device files will be created, if necessary. Only one getty is permitted to run on any particular port.
When a new printer is added to the system, all required device files will automatically be made, and the line printer spooler will be notified that a new printer is now available for use.
When the user wishes to modify his operating system, three options are supplied:
1. Generate a fully loaded operating system.
2. Generate a minimally loaded operating system.
3. Generate a custom kernel.
If a user is not concerned with the size of the operating system, or if the user needs to support a multitude of devices and I/O cards, then option (1) is a logical choice. If the user does not plan to support many optional devices on the system, then the minimal system, option (2), should work well. However, the majority of the users will be supporting a wide variety of devices and I/O cards on their systems. For these users, option (3) makes the most sense. This option allows the user to build a version of the operating system which supports only those devices and I/O cards specified; thus, this is the most space efficient of the three options.
DEPENDENCIES
Series 300 Diskless
When setting up a clustered environment, the /etc/clusterconf file is created with the appropriate entry for the root server. In addition all the needed Context Dependent Files (CDFs) are formed, a fully loaded kernel is configured, and the basic NS-ARPA files are created. After this process completes, the system will be set up as the root server of the cluster. Additional diskless cluster nodes can now be added.
When adding a diskless cluster node to an existing cluster environment, the /etc/clusterconf file is updated to reflect the new cluster node, additional Context Dependent Files (CDFs) are created, a kernel is configured, and the necessary NS-ARPA files are updated. To save on disk space, the kernel is linked to an existing diskless cluster node’s kernel if possible. This process is allowed only from the cluster’s root server
When removing an existing diskless cluster node from the cluster, the /etc/clusterconf file and NS-ARPA files are updated to reflect the fact that the cluster node no longer has access to the cluster. The cluster node’s Context Dependent Files (CDFs) will be deleted, if that option is specified. This process is allowed only from the cluster’s root server.
SEE ALSO
clusterconf(4), cdf(4), hosts(4), hosts.equiv(4).
FILES
/etc/master master device table
/etc/conf/dfile description file for current operating system
/hp-ux current operating system
/etc/inittab system initialization tables
/etc/passwd system password file
/etc/group system groups identification file
/users system users identification file
/etc/clusterconf system cluster configuration file
/etc/hosts NS-ARPA file containing internet addresses of remote hosts on the network
/etc/hosts.equiv NS-ARPA file which lists equivalent hosts on the network
\.rhosts NS-ARPA security file which sets up equivalent remote login names on the network
SEE ALSO
Hewlett-Packard Company — May 11, 2021