Section 2 - Installing the Server Software
Chapter 4 - Using the Kernel Configuration Utility
Chapter 5 - Continuing the Server Installation
Chapter 6 - Configuring the Communication Cards
Chapter 7 - Entering Time and Date Information
Chapter 8 - Entering Server Start-Up Information
Chapter 4 - Using the Kernel Configuration Utility
This chapter covers the beginning of the software installation and the part of the installation when the system builds the server's kernel. The kernel is the core of a server's operating system and contains the most basic components of your server's software. In earlier versions of VINES, a complete, unalterable kernel was provided with the installation media. With VINES 7.00, you can use the Kernel Configuration Utility to customize your server's kernel by selecting which drivers you want built into the kernel. You can also configure certain kernel parameters.
This chapter covers the following topics:
![]()
Starting the installation ![]()
Understanding kernel configuration ![]()
Building the system kernel ![]()
Running the Kernel Configuration Utility, which includes: - Viewing drivers on the system
- Loading third-party drivers onto the system
- Adding and removing drivers from the kernel
- Building the server's kernel
You received two sets of installation diskettes, each consisting of five diskettes. One set is labeled for AT-bus servers, and the other is labeled for MCA-bus servers. If you are installing on a MCA-bus server, use the MCA-bus diskettes. If you are installing on any other type of server, use the AT-bus diskettes. Make sure you use the correct set for your server.
Selecting the OS/2 and EBR Options
During this phase of the installation, you also have the option of installing the Enterprise Backup and Restore (EBR) product. EBR requires 19 MB on /disk1.
Note: You must purchase an Option Code to use EBR. If you will not be using EBR, you will save disk space by not installing it.
You also have the option of loading OS/2 versions of the Banyan client programs onto the server. Omitting OS/2 client files gives you more disk space on /disk1, but prevents OS/2 workstations from connecting to drive Z of the server. If you do not load OS/2 client files now, you can load them later from the Backup/Restore menu by selecting Reload VINES Files from Release Media.
1. Insert Install Disk 1 into drive A of the server.
2. Boot the server either by powering it on or by using CTRL-ALT-DELETE. If this is an existing Banyan server, shut down the server software from the Operator Menu and do an automatic reboot.
3. When prompted, insert Install Disk 2 into drive A and press ENTER. The Installation and Utility menu appears.
4. Select Full Installation of Banyan Server software on fixed disk.
5. The system prompts you to perform a surface analysis of the server's fixed disk (disk1):
- Enter Y if you are installing on a WD1003 fixed disk (ST506, ESDI, or IDE) or you question the integrity of your server's fixed disk. To continue the installation, go to "Entering Bad Block Information" in Chapter 10.
- Enter N if you are installing on a SCSI or RAID fixed disk subsystem. Go to step 6.
6. The system prompts you to install EBR on your server:
- Enter Y to load EBR.
- Enter N to skip loading EBR.
If you do not install EBR at this time, you can install it when the system is running.
7. The system prompts you to install OS/2 client files on the server.
- Enter Y to load OS/2 client files.
- Enter N to skip loading OS/2 client files.
As the message indicates, you can also load the OS/2 files after the server is running.
1. The system checks the condition of the root file system.
- If this is an installation on a new server, the system builds large root and swap partitions. Go to step 3.
- If this is an installation on an existing Banyan server, the following displays:
The installation process has detected the existence of a Banyan file system on the boot disk. Please choose one of the following options:
1.) Check available space in existing /disk1 file system for a full system backup restoration.
2.) Create large root (50 MB) and large swap (32 MB) partitions.
Enter your choice:Table 4-1 shows the existing and the new root file system and swap partition sizes. If you want the new root and swap partitions, determine that you have enough space left on your disk to create your existing /disk1 if you intend to reload a backup. The new root and swap use about 72 MB more than the previous versions.
Partition | New | Existing |
root | 50 MB | 12 K blocks (5.85 MB) |
swap | 32 MB | 8 K blocks (3.90 MB) |
2. Enter your choice.
- If you select choice 1, the system checks that it can restore a full system backup. The system creates the root and swap partitions at the existing sizes.
- If you select choice 2, the system creates large root and swap partitions only.
3. The system displays a message similar to the following:
New root and /disk1 file system must
be constructed on the Banyan partition.
Invoking the File System Configuration Utility...
The full installation process requires only a single file system to be created at this time. Creation of the other file systems will be deferred until later in the installation process.
A full installation requires a minimum file system size of 200 MB to be allocated at this time.
Logical disk 1 has a total capacity
of 16380 MB.
The following file systems will be created on logical disk 1:
File System Size
first 16380MB
Do you wish to override these defaults and specify your file
system sizes? (y/n):
At this point, enter Y to partition the remaining space on logical disk 1 later after creating /disk1. Enter N to use all the remaining space for /disk1. Use a minimum of 250 MB with the large root partition, or 200 MB with the existing root partition, for the software, including space for patches and upgrades. If you will use EBR, you need an additional 19 MB.
4. Answer the prompt:
- Enter N if you do not want to override the default size for /disk1. Do this if you plan to restore a full system backup and are not sure that less than the default size will accommodate the backup.
- Enter Y if you do want to override the default size for /disk1 and create other file systems. Do this if you plan to restore a full system backup and the default size is much larger than the backup. You can then build other file systems on this disk. At the next prompt, enter the size of the /disk1 file system.
You see these messages, and the process creates the root and /disk1 file systems:
Creating first S5 file system ...
Creating first S10 file system ...
If this is a new server, the process creates large root and swap partitions.
Continue with "To Load the Release Diskettes," which follows.
Note: The following error messages indicate that you have inserted the wrong Release Diskette during the installation. If you see either of these messages, insert the correct diskette and press ENTER.
Error: mount of diskette #1 failed
Error: Invalid sequence # found1. Insert Release Disk 1 and press ENTER. The following message appears:
Loading...Done
Load Release Diskette #2. Press <Enter> when ready:2. Insert Release Disk 2 and press ENTER. The following message appears:
Loading...Done
Load Release Diskette #3. Press <Enter> when ready:3. Insert Release Disk 3 and press ENTER.
The process installs kernel files, file systems, and Banyan drivers.
To continue with the installation, go to "Building the System Kernel" later in this chapter.
Understanding the Kernel Configuration Utility
In earlier versions of VINES, a complete system kernel was shipped with the server software and included all of the peripheral adapter drivers that Banyan produced. Because of this, your server's kernel included many drivers that your server did not use. In addition, if Banyan did not produce a driver for a specific peripheral device, you were unable to use that device with a Banyan server.
Banyan server software now includes a Kernel Configuration Utility that allows you to select peripheral adapter drivers and build a customized kernel for your server. This utility also includes a feature that lets you install new drivers produced by peripheral adapter manufacturers.
Note: Use the Kernel Configuration Utility to load peripheral adapter drivers (tape/disk/CD drive controllers, SCSI adapters, and so on) only. Load communication drivers (LAN/WAN cards, serial cards, and so on) later in the server installation (refer to Chapter 6).
The Kernel Configuration Utility is automatically accessed during the installation. In addition, after your server is running, use the Kernel Configuration Utility to reconfigure your server's kernel by adding or removing device drivers, or by configuring certain kernel parameters (refer to the Banyan Server Operations Guide). You can also save a copy of your server's kernel to diskette. After your server is installed, you access the utility by selecting Configure Kernel from the Banyan Server Configuration menu.
By using the Kernel Configuration Utility, you can either build a kernel from the standard default configuration that includes all the Banyan drivers, or create your own customized kernel configuration. For more information on the Kernel Configuration Utility, refer to the Banyan Server Operations Guide.
When you install the software, the system prompts you to build the default kernel or a customized kernel.
Default Configuration - This configuration includes all of the drivers shipped with the Banyan server software. All of the drivers are built into the kernel and are available for use. For a list of the drivers included in the default configuration, refer to "Banyan Peripheral Adapter Drivers," which follows.
Customized Configuration - You create this configuration through the Kernel Configuration Utility. You select which drivers to include in your server's kernel and build the kernel with only these drivers. The advantages of creating a customized kernel are that it:
![]()
Provides a smaller kernel thus easing memory requirements ![]()
Allows loading of third-party drivers for peripheral adapters
If, after you install your server, you purchase a peripheral device that uses a third-party driver, you can install the driver and rebuild your server's kernel.
Banyan Peripheral Adapter Drivers
Table 4-2 lists the Banyan peripheral adapter drivers that are included in the default kernel configuration for AT servers (ISA- and EISA-bus servers) and MCA-bus servers.
Drivers for AT Servers | Drivers for MCA Servers |
Diskette driver | Diskette driver |
ST506/ESDI/IDE-compatible disk driver | ST506/ESDI/IDE-compatible disk driver |
Adaptec 1510/1520 Adapter driver: 6x60 chipset | Adaptec 1640 MCA-Bus SCSI Adapter driver |
Adaptec 2740 Adapter Family driver: 7770 chipset | IBM PS/2 MCA-Bus ESDI Adapter driver |
Adaptec 1540/1542/1740 AT-Bus/EISA SCSI Adapter Family driver | IBM PS/2 MCA-Bus SCSI/SCSI-2 Adapter Family driver |
Compaq AT-BUS SCSI Tape Adapter/Compression Adapter driver | IBM MCA-Bus RAID Adapter driver |
Compaq SCSI-2 Options EISA driver | NCR 53C700/86C71 MCA SCSI Adapter driver |
Compaq Fast-SCSI-2 / 53C710 EISA SCSI driver | NCR 53C710 MCA-Bus SCSI Adapter driver |
Compaq Fast-Wide SCSI-2/EISA 53C825 driver | NCR 53C94 MCA-Bus SCSI Adapter driver |
Compaq IDA, IDA-2, IAES & Smart SCSI Array Adapter driver | |
Compaq Server Manager R Adapter driver | |
Dell Disk Array/SCSI Array driver | |
DPT 2021 AT-Bus SCSI Adapter driver | |
DPT 2012/2022/2122 EISA-Bus SCSI Adapter Family driver | |
DPT PM2x24/PM3224 PCI SCSI Adapter driver | |
Future Domain TMC-7000EX AT-Bus SCSI Adapter driver | |
Future Domain TMC-7000 FASST AT-Bus SCSI Adapter driver | |
Hewlett-Packard ECC memory driver | |
Mylex DAC960 EISA-Bus SCSI Array Adapter Family driver | |
NCR 53C810 PCI-SCSI (Fast SCSI-2) driver | |
NCR 53C825 PCI-SCSI (Fast-Wide SCSI-2) driver | |
Olivetti EFP-2 EISA-Bus SCSI Adapter driver | |
Olivetti ESC-1/ESC-2 EISA SCSI Adapter driver |
After you load the Release Diskettes, an informational message about the system kernel appears and you are prompted to:
Enter D to specify Default
Enter C to specify Customized
Your choice [D]:
At this point, you can either:
![]()
Build a kernel from the default configuration that includes all of the Banyan peripheral adapter drivers. For information on the default kernel, refer to "Understanding the Kernel Configuration Utility" earlier in this chapter. If you accept the default configuration, you can still modify the kernel after the server installation is complete. ![]()
Access the Kernel Configuration Utility and build a customized kernel. This option allows you to load third-party drivers and remove any Banyan drivers that you do not need.
When the system prompts you to select the default kernel or a customized kernel:
1. Enter D (the default) or press ENTER. The system builds the new kernel and copies /unix (the kernel) to /unix.orig.
2. The system prompts you to save the new kernel to a diskette:
- If you enter N, the server reboots.
- If you enter Y, you are prompted to insert a blank diskette in the diskette drive. The system then compresses and copies the kernel to diskette. When the copy is complete, the system prompts you to press ENTER to continue, and then prompts you to remove the diskette and press ENTER. The server then reboots.
To continue the installation, go to "Selecting Enhanced UNIX Access" in Chapter 5.
When the system prompts you to build a default kernel or a customized kernel:
1. Enter C. The Kernel Configuration Main Menu appears. Refer to "Running the Kernel Configuration Utility" later in this chapter for information on how to use the Kernel Configuration Utility.
2. Later, if you decide to build a default kernel, select Build Banyan default configuration (from the Build Kernel menu), and then exit the utility. You must build a kernel before you continue the server installation. If you try to exit the utility without building a kernel, the following message appears:
You have not built a kernel. If you exit the Kernel Configuration Utility without building a kernel, the installation cannot continue. Do you want to build a kernel now (Y or N) [Y]?
3. Do one of the following:
- Enter Y for the system to build the kernel with whatever configuration you have set (if you have not configured the kernel, the system uses the default configuration).
- Enter N to return to the Kernel Configuration Utility.
Running the Kernel Configuration Utility
From the Kernel Configuration Main menu, you can perform the following actions:
![]()
List drivers that are loaded onto the system ![]()
List drivers that are installed in the kernel ![]()
Add and remove drivers from the kernel ![]()
Build a new kernel ![]()
Load third-party drivers onto the system ![]()
Restore a previous kernel that you saved to diskette ![]()
Configure general kernel parameters ![]()
Exit from the utility
The Kernel Configuration Utility is described fully in Appendix C of the Banyan Server Operations Guide.
Through the Kernel Configuration Utility, you can view available drivers and installed drivers.
Available drivers are drivers that are loaded onto your system. When you first install the server software, the only available drivers are the standard Banyan adapter drivers. To build third-party drivers into the kernel, you must load the third-party driver package onto the system. See "To Load a Third-Party Driver Package" later in this chapter for instructions on loading third-party drivers.
Installed drivers are drivers that are configured into the kernel. Installed drivers are included in the kernel and available for use only after the kernel has been built. When you first install the server software, the Banyan adapter drivers are automatically installed. You can remove these drivers by configuring the kernel and removing the drivers. See "To Remove a Driver" later in this chapter for instructions. To include third-party drivers in the kernel, you must first load them onto the system, and then rebuild the kernel.
To List Available Drivers
1. From the Kernel Configuration Main menu, select List available drivers. The List Available Drivers screen appears.
This screen lists of all the Banyan and third-party drivers loaded onto the system. The drivers that are already installed in the kernel are marked with an asterisk (*).
2. When you finish viewing the drivers, press ESC to return to the main menu.
To List Installed Drivers
1. From the Kernel Configuration Main menu, select List installed drivers. The List Installed Drivers screen appears.
This screen lists of all the Banyan and third-party drivers that are installed in the kernel.
2. When you are finished viewing the drivers, press ESC to return to the main menu.
To build a customized kernel, first install (add) the drivers you want built into the kernel; if you have an existing kernel, you may also want to remove some drivers that are currently in the kernel.
Any changes you make to the kernel, whether adding or removing drivers, are not final until you build the kernel. For example, to include a specific driver in your server's kernel, you must install the driver and then build the kernel - the installed drivers are not accessible to the server until they are built into the kernel and the server is rebooted.
Note: If you configure a customized kernel, ensure that you include the driver for your server's boot device in the configuration.
To build a third-party driver into your server's kernel, you must load the driver from diskette. See "To Load a Third-Party Driver Package" later in this chapter for instructions on loading a third-party driver.
To Add a Driver
1. From the Kernel Configuration Main menu, select Add/Remove Drivers. The Add/Remove drivers screen appears.
2. Select Add driver. The Add Drivers screen appears.
This screen lists all the drivers that are available but not installed in the kernel. View additional drivers by pressing Pg-Dn and Pg-Up, or by using the arrow keys.
3. Enter the number of the driver you want to add.
4. When you are done adding a driver, press ESC to return to the Add/Remove drivers menu. To cancel any changes you made and retain the previous kernel configuration, select Discard changes.
5. Select Return to previous menu to return to the Kernel Configuration Main menu.
To access a driver that you have installed, you must rebuild the server's kernel. See "To Build the Kernel" later in this chapter.
1. From the Kernel Configuration Main menu, select Add/Remove drivers. The Add/Remove Drivers menu appears.
2. Select Remove driver. The Remove Drivers screen appears.
This screen lists all the drivers currently installed in the kernel. You can view additional drivers by pressing Pg-Dn and Pg-Up or using the arrow keys.
3. Enter the number of the driver you want to remove from the kernel.
Note: When you remove a driver, the driver is not deleted from the disk; it is deconfigured (changed from the installed state to the available state).
4. When you finish removing a driver, press ESC to return to the Add/Remove Drivers menu. To cancel any changes you made and retain the previous kernel configuration, select Discard changes.
5. Select Return to previous menu to return to the Kernel Configuration Main menu.
You must rebuild the server's kernel to actually remove a driver. Refer to the following section, "To Build the Kernel."
1. From the Kernel Configuration Main menu, select Build kernel. The Build Kernel menu appears.
2. Select the appropriate menu option:
- To build the kernel with the standard default configuration (includes all the Banyan drivers), select Build Banyan default configuration.
Note: This does not reset configurable kernel parameters to their default settings.
- To build the kernel with any driver changes you made, select Build current configuration. Table 4-3 lists three situations where you may have to take further action.
If your kernel configuration contains... | The system... | You must... |
Third-party fixed disk monolithic drivers and Banyan drivers | Prompts you to select a driver to control the boot device |
Select one of the third-party monolithic drivers or Press ESC to have one of the Banyan drivers control the boot device |
Third-party fixed disk monolithic drivers only | Prompts you to select a driver to control the boot device | Select one of the third-party monolithic drivers |
No fixed disk driver | Displays the message "No boot drive selected." |
1. Press ENTER to redisplay the Build Kernel
menu 2. Add a fixed disk driver to the kernel configuration. 3. Rebuild the kernel |
3. The system builds the new kernel and prompts you to save the new kernel to diskette:
- Enter N to skip saving a copy of the new kernel. Go to step 6 to continue.
- Enter Y to save a copy of the new kernel. The system prompts you to insert a blank diskette. Go to step 4 to continue.
4. Insert a 1.44 MB double-sided diskette into drive A and press ENTER. The system copies the kernel to the diskette and displays the following message:
Kernel has been copied successfully. Press <Enter> to continue.
5. Press ENTER. The Build Kernel menu appears.
6. Select Return to the previous menu. The Kernel Configuration Main menu appears.
7. Select Exit. The system prompts you to remove the diskette.
8. Remove the diskette from drive A and press ENTER. The system reboots. Go to "Selecting Enhanced UNIX Access" in Chapter 5 to continue the installation.
To build third-party drivers into your server's kernel, you must load the driver package provided by the device manufacturer. A driver package may contain more than one device driver.
To Load a Third-Party Driver Package
1. From the Kernel Configuration Main menu, select Load driver package. The following message appears:
Load package diskette. Press <Enter> when ready.
2. Insert a driver package diskette into drive A and press ENTER. The drivers are loaded onto the system and are automatically installed in the kernel. To use the new third-party drivers, you must rebuild the kernel.
Note: If a driver package with the same name and revision number is already installed, the system may prompt you to overwrite the existing driver package. To load the new driver package, follow the on-screen instructions.
3. Press ESC to return to the Kernel Configuration Main menu.
Overwriting the /unix.orig File
Your server's kernel is stored in a file called /unix. An additional file, called /unix.orig, contains a backup copy of your server's kernel. During installation or during a rebuild of a kernel, you are also prompted to save a copy of /unix to diskette. If your server's kernel ever becomes corrupted and you are unable to boot the server, you can boot the server from the kernel contained in /unix.orig or from the kernel you saved to diskette.
When you try to build a new kernel and your server already has an existing kernel, the following message appears:
The new kernel is built. Before the
new kernel becomes the default kernel, you have the opportunity
to save the default kernel as unix.orig.
Would you like to save the current default kernel as unix.orig?
(y/n):
If you enter Y, the system moves
the current default kernel to /unix.orig (thereby overwriting
the original /unix.orig), and stores the new kernel in /unix.
If you enter N, the system retains the original /unix.orig,
deletes the current default kernel (/unix), and stores the new
kernel as /unix.
To Boot the Server from /unix.orig
1. Power on the server.
2. Hold down SHIFT - A when the word Loading... appears in the upper left hand corner of the console screen.
Loading... will change to boot:
3. Enter unix.orig and press ENTER.
To Boot the Server from /unix Saved on Diskette
1. Insert Install Disk 1 of 2 in the server diskette drive and boot the system.
2. At the prompt, insert Install Disk 2 of 2.
3. At the menu, select Fixed Disk Utilities.
4. Select Restore kernel from diskette.
5. Insert the diskette containing the saved /unix.
6. Enter N at the prompt to copy the existing /unix over /unix.orig.
The system copies and decompresses /unix from diskette.
7. Select Exit from Fixed Disk Utilities.
8. Select Exit at the next menu.
9. Reboot the server.