This release provides enhancements to the full (default or custom) installation process and to the installation cloning process. Now, administrators can modify the configuration description file (CDF) to achieve an unattended installation cloning process. In addition, the installation process searches for and invokes user-supplied files to enable customizations on the system to be installed. Refer to Appendix C for more information. NOTE
By reading this chapter, you will ... |
---|
Respond to prompts for a cloned installation or use the text-based or graphical interface to enter all information required by the full installation procedure. |
Enter boot commands when requested by the installation procedure. |
Select kernel options for custom installations. |
Log in to the newly-installed system as the user root. |
Before beginning the installation, ensure that you have performed all prerequisite tasks as described in Section 1.4.
Welcome to the Digital UNIX Installation Procedure This procedure installs Digital UNIX onto your system. You will be asked a series of system configuration questions. Until you answer all questions, your system is not changed in any way. During the question and answer session, you can go back to any previous question and change your answer by entering: history You can get more information about a question by entering: help There are two types of installations: o The Default Installation installs a mandatory set of software subsets on a predetermined file system layout. o The Custom Installation installs a mandatory set of software subsets plus optional software subsets that you select. You can customize the file system layout. The UNIX Shell option puts your system in single-user mode with superuser privileges. This option is provided for experienced UNIX system administrators who want to perform file system or disk maintenance tasks before the installation. The Installation Guide contains more information about installing Digital UNIX. 1) Default Installation 2) Custom Installation 3) UNIX Shell Enter your choice:
You may want to refer to Section J.1 and Section J.2 in Appendix J to review sample text-based installations before you actually start your own text-based installation. Reviewing these sample installations gives you an idea of what to expect. You can also use these sample installations to follow the progress of your own system installation.
A Configuration Description File, was specified for use during the installation of this system. The Configuration Description File can be used by the installation to provide the information related to file system layout and software selection. If you choose to use the Configuration Description File, the installation will proceed and you will not have to answer any questions. If you decide not to use the Configuration Description File, the installation will continue interactively. Would you like to use the Configuration Description File? (y/n) [y]:
If the prompt variable in the CDF is set to no, then the system will use the CDF without prompting the user. The system displays the following:
A Configuration Description File, was specified for use during the installation of this system. The Configuration Description File will be used by the installation to provide the information related to file system layout and software selection.
For information on the prompt variable and other variables in a CDF, see Appendix C.
Later in the installation process, you will be required to boot from the newly installed disks, as shown in Section 5.18 and to enter a root password as shown in Section 5.5 (if a password is not already contained in the CDF).
*** Validating CDF prior to starting installation... *** Validation Error: The disk name "rz8" was not found on this system when attempting to validate the following filesystem(s): root usr
*** Validating CDF prior to starting installation... *** Validation Error: The rz25 disk type specified in the Configuration Description File does not match the name/type found on this system for the following device(s): rz3/rz26l
The previous validation errors are saved in the /var/tmp/install.log file for your reference until you reboot the system.
You may restart the cloned installation procedure by doing one of the following:
User Input | DefaultInstallation | CustomInstallation |
---|---|---|
Installation Type | X | X |
Host name ° | X | X |
Root password ° | X | X |
Root password verification° | X | X |
Date° | X | X |
Time° | X | X |
Location° | X | X |
Time zone° | X | X |
Disk for root file system | X | X |
File system type for root file system | X | |
Disk and partition for /usr file system | X | |
File system type for /usr | X | |
Disk and partition for first swap area | X | |
Disk and partition for optional second swap area | X | |
Disk and partition for /var file system | X | |
File system type for /var | X | |
Optional software subsets to install | X | |
Boot commands ° | X | X |
Kernel options | X | |
Log in as the user root | X | X |
Section 5.3 through Section 5.20 provide additional reference information for each piece of information required by the installation procedure.
Default Installation | Custom Installation |
---|---|
The root and /usr file systems and swap space will be on the same disk; /var is a directory under /usr. | The root, /usr, and /var file systems and swap space can be on any disk and each can be put on separate disks. |
Always uses the default partition table. | Option to use the default or custom partition table. |
Uses the default file system layout: root is on the a partition; /usr is on the g partition, and swap space is on the b partition. | Except for the root file system, which is always on the a partition, uses any disk partition on any disk for file systems and swap space. |
UFS (UNIX file system) is the file system type for all file systems. | Choice between UFS or the Advanced File System (AdvFS) as the file system type. ° |
Configures one swap area. | Option to configure two swap areas. |
Automatically installs mandatory software subsets only. | Installs mandatory software subsets automatically and then offers the option to install additional software subsets. |
You should perform a custom installation if any one of the statements shown in Table 5-4 is true.
Choose the custom installation if you want to... |
---|
Keep or modify the existing customized disk partition table. |
Allocate two swap areas. |
Use either the Advanced File System (AdvFS) or the UNIX File System (UFS) as the file system type for root, /usr, or /var. ° |
Customize the file system layout by choosing the disk and the disk partitions on which the root, /usr, and /var file systems and swap area will reside. |
Create a separate file system for /var. |
Customize the software on your system by installing additional optional software subsets. |
Customize kernel options. |
Use the system as a dataless management services (DMS) server. ° |
Use the system as a remote installation services (RIS) server. ° |
You should perform a default installation if all of the statements shown in Table 5-5 are true.
Choose the default installation if you want to ... |
---|
Use only one disk to contain the root and /usr file systems and swap space. |
Make the var area a directory under /usr. |
Make no decisions about which disk partitions are used for the root and /usr file systems. |
Use the UNIX file system (UFS) as the file system type for the root and /usr file systems. |
Use the default partition table. ° |
Allocate one swap area. |
Install only the mandatory software subsets; optional software can be installed after the default installation completes. |
Get your Digital UNIX operating system up and running with limited decision-making. The default installation may be more appropriate for users with no previous UNIX experience. |
The default installation is recommended for systems with limited disk space and less than 32 MB of memory.
For custom installations... |
---|
Make an entry in the text entry fields in the Installation Setup window. |
Optionally click on Partition Disks... if you want to use the Disk Configuration Utility to resize disk partitions. |
Optionally click on Select Software... to display the software selection window. When you are finished selecting optional software, click on OK to return to the Installation Setup window. |
Click on Setup Done. |
Click on OK to verify that you are ready to begin the installation procedure. |
Table 5-7 describes how to navigate through the Installation Setup window for default installations:
For default installations... |
---|
Make an entry in the text entry fields on the Installation Setup window. |
Optionally click on View Software to view the mandatory software that will be installed. You cannot change (add or delete) the software subsets on this list during default installations. Click on OK to return to the Installation Setup window. |
Click on Setup Done. |
Click on OK to verify that you are ready to begin the installation procedure. |
Following are examples of correct and incorrect host names:
Correct: | mysystem | mysystem.com | abc-university.edu |
Incorrect: | my_system | 1996.com | binary |
Do not use the words generic or binary for your host name because they have been reserved for use by the operating system. Note
You may want to consult your site system administrator before choosing your host name because site-specific restrictions (such as maximum length) may have been defined. You also do not want to choose a host name that is already being used by another system. If your system is already running a previous version of Digital UNIX and is connected to a network, you should keep the same host name because changing it would impact how your system is recognized on the network.
If you do not supply a host name, you are prompted for one during the installation configuration phase.
Passwords should contain a combination of upper and lower case letters and a minimum of six to a maximum of 16 characters. The Digital UNIX operating system verifies only the first eight characters. Digital suggests using numbers and special characters such as the dollar sign ($), the percent sign (%), the number sign (#), the period (.), the hyphen (-), the underscore (_), or the at sign (@) in your password.
When choosing a password, you should not use:
The following are examples of correct and incorrect root passwords:
Correct: | U8one2too | wht%IZ-dne | DL_wrks@9 | 9Pnt.99% |
Incorrect: | lowercase | nonumbers | Spot | 7-6-58 |
If you do not supply a root password, you will be prompted for one during the installation configuration phase.
If you do not supply a date and time, you are prompted to enter the date and time during the installation configuration phase.
Location Acronym | Description |
---|---|
CET | Central European Time |
EET | Eastern European Time |
Factory | Specifies No Time Zone |
GB-Eire | Great Britain/Ireland |
GMT | Greenwich Mean Time |
MET | Middle European Time |
NZ | New Zealand |
NZ-CHAT | New Zealand, Chatham Islands |
PRC | Peoples Republic of China |
ROC | Republic of China |
ROK | Republic of Korea |
SystemV | Specific to System V operating systems |
UCT | Greenwich Mean Time |
US | United States |
UTC | Greenwich Mean Time |
Universal | Greenwich Mean Time |
W-SU | Western Soviet Union ° |
WET | Western European Time |
Zulu | Coordinated Universal Time |
If you do not supply a geographic location and time zone, you are prompted for this information during the installation configuration phase.
There are two requirements for the disk that contains the root file system:
The following information is displayed for each disk connected and available to your system:
The unit number for the disk that contains the root file system must be in the range 0 to 255 for ra type devices, in the range 0 to 47 for re type devices (SCSI disks employing RAID technology), and in the range 0 to 511 for rz type devices. This information is pertinent if your system has, for example, more than 511 rz disks because the disks with unit numbers greater than 511 will not be displayed for selection during the installation. The installation procedure automatically displays the device name (with unit numbers) for each disk connected to your system.
This is not a problem during custom installations because you have the opportunity to select different disks and partitions. If you are performing a custom installation, you can, for example, use RZ55 and RZ24L disks to hold the root file system and allocate the /usr (and other) file system to other disks and disk partitions on your system. The default installation uses only default partitions and puts all file systems on a single disk. Therefore, disk types such as the RZ55 and RZ24L cannot be used for a default installation.
The disk you selected is too small for a Default installation. You may switch to a Custom installation to distribute the software on multiple disks, or you may select a larger disk to continue the Default installation. 1) Switch to Custom installation 2) Select a different disk Enter your choice:
If you select option 1, you can use the custom installation procedure to allocate partitions on other disks for the /usr and other file systems or spread the software across multiple disks. Review Chapter 1 and read Chapter 3 before you continue with the custom installation.
Option 2 lets you choose a different disk. You must choose a disk large enough to contain root file system, /usr file system, and swap1 area to continue the default installation or the same message is repeated. If your system has another disk and it is not marked with an asterisk, you can choose this option and continue with the installation. Refer to Appendix G and Appendix H to ensure that the disk you choose has enough space.
Before writing a new disk label, the disk is checked for a preexisting disk label. If none is found, which is typical for a disk that has never been used for Digital UNIX before, a disk label is written using the default partition information.
The following describes how disk labels are handled by the installation procedure:
If an existing disk label is selected, it is saved and rewritten to the disk with a valid bootstrap. The new disk label is identical to the previous disk label. If the default disk label is selected, a disk label containing the default partition information is used.
Assuming that the partitions to be preserved were undisturbed during the installation, the partitions can be used on the newly-installed system. If the partition contained a file system, it should be capable of being mounted and accessed. If the partition you are preserving were using the Advanced File System (AdvFS), make sure you select AdvFS as the file system type.
If the disk you choose to contain the root file system was previously used on an ULTRIX system, it will be formatted with ULTRIX partition tables. You will see a message similar to the following:
ULTRIX compatible partition data found. This data may be different than the standard partition layout information in /etc/disktab. ULTRIX partition table layout is: partition bottom top size overlap a 0 40959 40960 c,h b 40960 163839 122880 c c 0 832526 832527 a,b,d,e,f,g,h d 163840 386735 222896 c,g e 386736 609631 222896 c,g f 609632 832526 222895 c,g g 163840 832526 668687 c,d,e,f h 0 0 0 a,c Use the ULTRIX-style partition data? [y]:If you enter y to use the ULTRIX layout, a Digital UNIX disk label is created for the disk. This label will correspond to the existing ULTRIX partition table. If you enter n, the default partitions for Digital UNIX are created.
If you are using the text-based user interface to perform a custom installation and your system has nonstandard disk partitions on the disk that contains the root file system, you are prompted to keep the nonstandard partitions or replace them with the disk's default partitions.
If you have carefully planned your partition layout and you want to keep the partitions you have on the disk, choose the existing partition table. If neither the default nor existing partition tables are suitable, exit the installation procedure and use either the Disk Configuration application or the disklabel command to modify the partitions on the disk.
The following information is shown for each disk partition:
The rz3 disk has a non-default partition table. Partition Start Size End Overlaps Default a 0 131072 131071 c b 131072 262144 393215 c c 0 2050860 2050859 a b d e f g h d 393216 552548 945763 c g e 945764 552548 1498311 c g h f 1498312 552548 2050859 c h g 393216 819200 1212415 c d e h 1212416 838444 2050859 c e f Existing a 0 263340 263339 c b 263340 1787520 2050859 c d e f g h c 0 2050860 2050859 a b d e f g h d 393216 552548 945763 b c g h e 945764 552548 1498311 b c g h f 1498312 552548 2050859 b c h g 393216 819200 1212415 b c d e h h 263340 1787520 2050859 b c d e f g Choose which partition table to use. 1) Default table 2) Existing table Enter your choice:
The custom installation lets you choose between the UNIX file system (UFS) or the Advanced File System (AdvFS) as the file system type for the root, /usr, and /var file systems.
Unless you choose otherwise, UFS is the default file system on Digital UNIX systems. On systems with less than 32 MB of memory, you do not have the option to use AdvFS as the file system type; the UNIX file system (UFS) is chosen automatically.
UFS has a more rigid hierarchy than AdvFS. In a UFS file system, each disk (or disk partition) contains one separate file system. The UFS file system is characterized by a hierarchical structure, the ability to create and delete files, dynamic growth of files, the protection of file data, and the treatment of peripheral devices.
Refer to the System Administration guide for more information about UFS.
The POLYCENTER Advanced File System (AdvFS) is a journaled local file system that provides higher availability and greater flexibility than traditional UNIX file systems. Using transaction journaling, AdvFS recovers file domains in seconds rather than minutes after an unexpected restart such as a power failure. AdvFS journaling also provides increased file system integrity. AdvFS provides greater flexibility by allowing filesets (file systems) to share a single storage pool and enabling hard and soft fileset quotas in addition to user and group quotas. AdvFS supports a maximum file size of 128 GB.
If you chose not to use the default file system layout, you must choose a disk and partition on which the /usr file system will reside. You have the option to choose between UFS or AdvFS as the file system type for the /usr file system.
If you need more information about the contents of the /usr file system, refer to Section 3.7.
You can place the var area either as a directory under the /usr file system or create a separate var file system.
If the system you are installing is a Dataless Management Services (DMS) server, you should allocate a separate file system for /var because all dataless environments reside in /var/adm/dms on the server. Putting var under /usr could mean that your system will run out of disk space when you create dataless environments. Refer to Sharing Software on a Local Area Network for more information about allocating the var area and calculating disk space for DMS environments and RIS servers.
If you plan to set up your system as a RIS server, you should allocate a separate file system for /var because all RIS environment information is stored in the /var/adm/ris directory. In addition, if the RIS user chooses to extract the data for the RIS area from the distribution media rather than symbolically linking to the area, this data will also be stored in /var/adm/ris. Refer to Sharing Software on a Local Area Network for more information about allocating the var area and calculating disk space requirements for RIS servers.
If you need more information about the contents of the /var file system, refer to Section 3.8.
Although you cannot choose the swap strategy modes during the installation procedure, there are two strategies for swap allocation: immediate and over-commitment. The swap strategy mode for Digital UNIX systems with greater than 32 MB of memory is immediate mode which means that swap space is allocated when modifiable virtual address space is created. This mode requires more swap space than over-commitment mode because it guarantees that there will be enough swap space if every modifiable virtual page is modified.
Refer to System Administration for more information about swap allocation strategies and how to switch from one swap allocation mode to the other after the installation.
If you need more information about planning swap space, refer to Section 3.9.
You have the option to allocate a second swap area during a custom installation.
To optimize the performance of your swap space, spread out your swap space across multiple devices and use the fastest disks for swap devices. To ensure the best performance, place each swap area on a separate disk instead of placing multiple swap areas on the same disk.
Base System Base System - Hardware Support Base System Management Applications and Utilities Basic Networking Configuration Applications Basic Networking Services Compiler Back End Hardware Kernel Header and Common Files Hardware Kernel Modules Kernel Header and Common Files Keyboard Support NFS(tm) Configuration Application NFS(tm) Utilities Standard Kernel Modules Tcl Commands
Depending on your system's graphics options, either DECwindows 75dpi Fonts or DECwindows 100dpi Fonts is mandatory. The mandatory X Server software subset depends on whether your system has a TurboChannel bus, QVision graphics adapter, or PCI bus. If you system has graphic capability, the following windowing and graphical applications software subsets are installed as mandatory automatically:
Adobe Fonts Basic X Environment CDE Desktop Environment CDE Mail Interface CDE Minimum Runtime Environment DECwindows Fonts Graphical Base System Management Utilities Graphical Print Configuration Application Graphical System Administration Utilities Netscape Navigator Gold V3.0 Old X Environment Tk Toolkit Commands X Fonts X Servers Base X Servers
If Asynchronous Mode Transfer (ATM) hardware is detected during the installation process, the following software subsets are also installed as mandatory:
ATM Commands ATM Kernel Header and Common Files ATM Kernel Objects ATM Kernel Modules
The following POLYCENTER AdvFS software subsets are usually optional. They become mandatory during a custom installation if AdvFS is chosen as the file system type for root, /usr, or /var:
POLYCTR advfs POLYCTR advfs Kernel Modules
Refer to Appendix D for descriptions of the mandatory software subsets.
The amount of free space remaining in the root, /usr, and /var file systems is displayed to indicate if the disk partitions you chose for those file systems are large enough to hold the mandatory software subsets. Space remaining is shown in gigabytes (GB), megabytes (MB), or kilobytes (kB):
Free space remaining (root/usr/var): 18.4MB/176MB/192MB
When you select optional software subsets, the amount of free space remaining in the root, /usr, and /var file systems is displayed to indicate if the disk partitions you chose are large enough to hold the software you are selecting. Space remaining is shown in gigabytes (GB), megabytes (MB), or kilobytes (kB).
Free space remaining (root/usr/var): 18.4MB/176MB/192MBThe figures are updated after pressing the Return key as each optional software subset is selected.
If you select a software subset that has a dependency with another subset that is not yet selected, the other subset is selected automatically.
The chosen subset(s) require one or more additional subset(s) which will be loaded automatically: * Doc. Preparation Tools (OSFDCMT410)
Some optional software subsets are hardware specific; that is they are optional because you do not have the hardware or graphics capabilities which they support. The Windowing Environment category, which provides support for numerous keyboard types, is an example of this situation. Therefore, during text-based installations, it is not necessary to select ALL mandatory and all optional subsets, or during a graphical installation to click on Add All because you will install hardware-specific software that your system does not need.
Section J.2.1 in Appendix J provides a list of the optional software subsets that are available to install regardless of the interface you are using. Refer to Appendix D for descriptions of the optional software subsets.
If you want to change your selections, press the Return key until you reach the end of the software subset list. Select the option to CANCEL selections and redisplay menus to start the selection process again.
It may not be wise to select ALL software subsets because you will select hardware-specific software subsets that your system does not need (such as fonts, keyboard types, and Xservers).
When you are finished making optional software subset selections, press Return at the prompt displayed at the end of the software subset list:
You have the opportunity to confirm your selections before software subset loading begins.
.
.
.
The following choices override your previous selections: 77) ALL mandatory and all optional subsets 78) MANDATORY subsets only 79) CANCEL selections and redisplay menus Add to your choices, or press RETURN to confirm previous choices. Free space remaining (root/usr/var): 18.4MB/176MB/192MB Choices (for example, 1 2 4-6): 2 5 21-27 [Return]
It may not be wise to click on the Add All button because you will select hardware-specific software subsets that your system does not need. However, an alternative to selecting one software subset (or category) at a time is to Add All subsets in one step and then double-click on the subsets you do not want. Adding all subsets results in more software than your system needs, so remember to remove all of the hardware-specific subsets related to keyboard types, Xservers, and fonts. The user interface will not let you remove software subsets that are mandatory for your system's hardware configuration.
If you want to remove (or deselect) optional software selections, position the cursor in the Selected Software window and double click on the software subset or software subset category you want to remove. Another way is to click on the software subset or software subset category and then click on the Remove button to remove the software subset or software subset category from the list. The Remove button is enabled only if the selected software subset or software subset category is removable.
You have now answered all questions needed to install Digital UNIX on this system. Press CTRL/C to cancel the installation; or type "history" to modify your earlier answers; or press RETURN to proceed with installation:
The screen display looks similar to the following.
*** Creating the root file system on device rz1a *** *** Creating the usr file system on device rz1g *** *** Creating the swap1 file system on device rz1b ***
Checking file system space required to install specified subsets: File system space checked OK. *** Loading the operating system software subsets *** The installation procedure will now load the software on your disk partitions. This process will take from 45 to 120 minutes to complete depending on your distribution media and processor type. Loading 1 of 28 subset(s).... Base System Copying from system9 (inet) Working....Fri Dec 13 13:21:30 EDT 1996 Verifying Working....Fri Dec 13 13:23:31 EDT 1996 Loading 2 of 28 subset(s).... Base System - Hardware Support Copying from system9 (inet) Working....Fri Dec 13 13:24:18 EDT 1996 Verifying Loading 3 of 28 subset(s).... Compiler Back End Copying from system9 (inet) Working....Fri Dec 13 13:24:59 EDT 1996 Verifying
.
.
.
Loading 26 of 28 subset(s).... Graphical Base System Management Utilities Copying from system9 (inet) Verifying Loading 27 of 28 subset(s).... Graphical System Administration Utilities Copying from system9 (inet) Verifying Loading 28 of 28 subset(s).... Graphical Print Configuration Application Copying from system9 (inet) Verifying 28 of 28 subset(s) installed successfully.
If your system has a graphics device on its ISA bus that requires a kernel device driver, you must modify the isacfg entry to match the kernel device driver before rebooting the system. When you issue this command, let the input line wrap; do not press the Return key in the middle of the line. Note
>>> isacfg -mod -slot slot_number -dev device_number -handle vendor_handle -etyp 1 -enadev 1In the previous example, replace vendor_handle with the handle supplied in the vendor's installation documentation. If you performed a RIS installation from a RIS area that already has a kernel device graphics device driver installed and you already set the handle to the one specified in the vendor's installation documentation, you do not need to execute this command.
Issue the following console commands to set your default bootpath variable and to boot your system disk to multiuser: >>> set boot_osflags A >>> set bootdef_dev DKA0 >>> boot syncing disks... done CPU 0: Halting... (transferring to monitor) ?05 HLT INSTR PC= FFFFFC00.0044CA90 PSL= 00000000.00000005Enter the boot commands at the console mode prompt (>>>) as instructed:
>>> set boot_osflags A [Return] BOOT_OSFLAGS = A >>> set bootdef_dev DKA0 [Return] BOOTDEF_DEV = DKA0 >>> boot [Return]Write down the boot commands here in case you need them again: >>> >>> >>>
Software configuration begins after the system boots. Section 5.19.2 provides samples of system configuration screens. A kernel build procedure begins after software configuration.
This system requires a driver for its graphics card. Enter the device where the kit can be found (e.g. rz4c), or <return> to cancel:
** SYSTEM CONFIGURATION *** Configuring "Base System " (OSFBASE410) Configuring "Base System - Hardware Support " (OSFHWBASE410) Configuring "Compiler Back End " (OSFCMPLRS410)
.
.
.
Configuring "Graphical Base System Management Utilities" (OSFXSYSMAN410) Configuring "Graphical System Administration Utilities" (OSFXADMIN410) Configuring "Graphical Print Configuration Application" (OSFXPRINT410)
If you did not provide certain essential site-specific information (such as a root password, your system's host name, the date and time, and location and time zone) earlier in the installation procedure, you will be prompted to enter that information now.
What happens after software configuration completes depends on whether you performed a default, custom, or cloned installation. Proceed to Section 5.20 for more information.
If you performed
a default installation, the kernel is built automatically with the mandatory
kernel parameters for your system configuration. None of the options shown
in Section 5.20.1 will be included in the kernel.
After the kernel build, continue with Section 5.21, which shows
you how to log in to your system for the first time. If you want to build
a kernel with selected options after the default installation, refer to the doconfig
(8)
reference page.
If you performed a custom installation or invoked the update installation with the -i option, go to Section 5.20.1 to select kernel options.
If you performed a cloned installation, how the kernel build occurs is defined in the configuration description file (CDF). If the CDF was originally created during a default installation, the kernel is built automatically. If the CDF was originally created during a custom installation, you have the opportunity to select kernel options.
If you do not select the kernel option for the product, you will not be able to use that product. For example, if you do not select the Logical Storage Manager (LSM) kernel option, even though you installed the LSM software subsets, you will not be able to use LSM. When you select a kernel option, additional code to support the option is loaded into the kernel. Therefore, selecting All of the above kernel options significantly increases the size of the kernel.
The following kernel subsystems are mandatory on all systems except systems with less than 32 MB of memory:
If your system has less than 32 MB of memory, the kernel subsystems available for your system have been optimized and the selection of certain optional kernel subsystems has been disabled. If you choose any of these kernel options for systems with less than 32 MB system, you may negatively impact system performance.
The Kernel Option Selection menu has a Help option that displays online help about each kernel option.
The Kernel Option Selection menu is similar to the following:
*** KERNEL CONFIGURATION AND BUILD PROCEDURE *** *** KERNEL OPTION SELECTION *** Selection Kernel Option -------------------------------------------------------------- 1 LAN Emulation over ATM (LANE) 2 Classical IP over ATM (ATMIP) 3 ATM UNI 3.0/3.1 Signalling for SVCs 4 Asynchronous Transfer Mode (ATM) 5 Advanced File System (ADVFS) 6 System V Devices 7 Kernel Breakpoint Debugger (KDEBUG) 8 NTP V3 Kernel Phase Lock Loop (NTP_TIME) 9 Packetfilter driver (PACKETFILTER) 10 Point-to-Point Protocol (PPP) 11 STREAMS pckt module (PCKT) 12 X/Open Transport Interface (XTISO, TIMOD, TIRDWR) 13 File on File File System (FFM) 14 ISO 9660 Compact Disc File System (CDFS) 15 Audit Subsystem 16 ACL Subsystem 17 Logical Storage Manager (LSM) 18 All of the above 19 None of the above 20 Help 21 Display all options again -------------------------------------------------------------- Enter the selection number for each kernel option you want. For example, 1 3 [19]:The following is a description of each kernel option:
If you chose AdvFS as the file system type for root, /usr, or /var, the subset is mandatory will not be displayed in the menu; AdvFS will be configured automatically.
If the NTP_TIME kernel option is configured, a new system call is available to xntpd that uses a PLL algorithm in the kernel for improved accuracy when adjusting the system clock frequency. A detailed description of the PLL algorithm can be found in RFC 1589. Refer to Network Administration for more information about NTP.
The Digital UNIX packetfilter supports two filtering models: the original
CMU/Stanford model, as supported in ULTRIX, and the BSD Packet Filter (BPF),
which provides more flexible and efficient filtering. (BPF was developed by
the University of California, Lawrence Berkeley Laboratory.) Several public
domain applications that use the packetfilter are integrated in Digital UNIX,
including rarpd, tcpdump, tcpslice, nfswatch, and nfslogsum.
Refer to the packetfilter
(7) reference page for more information.
Refer to Network Administration for more information about PPP.
If you installed LAT, Data Link Bridge does not appear as a kernel option.
This functionality is mandatory on systems with greater than 24 MB of memory.
Refer to Network Administration for more information about SLIP.
This functionality is mandatory on systems with greater than 24 MB of memory. Disk quotas for AdvFS are configured into the kernel by default, on systems in which AdvFS is installed.
This functionality is mandatory on systems with greater than 24 MB of memory. The STREAMS framework is required by many of the personal computer protocols and DECnet.
Selecting this kernel option allows DECnet/OSI to load its kernel modules dynamically; you do not have to rebuild the kernel and reboot.
acl
(4), getacl
(1), and setacl
(1) reference pages for more information.
LAT software has the features required for a host to function as a service node so that requests for connections can be made by server users. LAT also permits host applications to initiate connections to the server's ports, designated as applications ports, to access remote devices such as printers. Digital UNIX supports 1500 logins using LAT.
If you chose the LAT subset when you made your subset selections, the option is not displayed in the kernel option menu and is configured automatically. If you add the LAT subset after the installation, you must reconfigure the kernel using the doconfig command.
Refer to Network Administration for more information about LAT.
This functionality is mandatory on systems with greater than 24 MB of memory.
Refer to Network Administration for more information about NFS.
You selected the following kernel options: Asynchronous Transfer Mode (ATM) System V Devices Logical Volume Manager (LVM) Kernel Breakpoint Debugger (KDEBUG) Packetfilter driver (PACKETFILTER) STREAMS pckt module (PCKT) Data Link Bridge (DLPI V2.0 Service Class 1) X/Open Transport Interface (XTISO, TIMOD, TIRDWR) File on File File System (FFM) ISO 9660 Compact Disc File System (CDFS) Audit Subsystem Local Area Transport Support Logical Storage Manager (LSM) Is that correct? (y/n) [y]:If the displayed kernel options are the ones you want, enter y or press Return to accept the default response. If the displayed kernel options are not the ones you want, enter n at the prompt. The Kernel Option Selection menu is redisplayed for you to select kernel options again.
After you select kernel options, you have the option to edit the configuration file. The configuration file is a text file that defines the components built into the kernel; it is located in the /usr/sys/conf/ SYSTEM_NAME file.
You may want to edit the configuration file to add devices, tune parameters, enable realtime preemption, or add third party layered product support. You may also want to recreate any customizations you may have made in a previous version of this file. Section 5.20.2.1 describes how to edit the configuration file to enable realtime preemption.
The Command and Shell User's Guide contains a tutorial that teaches you how to use the ed text editor (as well as the vi text editor). Refer to System Administration for information about the contents of the configuration file and the entries that you may want to edit.
You will see a prompt similar to the following:
Do you want to edit the configuration file? (y/n) [n]:
If you enter n or press Return (to enter the default response) to skip the edit of the configuration file, the kernel build process begins as shown in Section 5.20.3.
If you enter y to edit the configuration file, the following message displays:
Using 'ed' to edit the configuration file. Press return when ready, or type 'quit' to skip the editing session:Enter the word quit if you want to skip the editing session and start the kernel build process or press the Return key if you want to edit the configuration file.
The following example shows an editing session using the ed text editor where the value of maxusers is changed to a value of 64:
Using ed to edit the configuration file. Press return when ready, or type quit to skip the editing session: [Return] 1907 [1] /maxuser [2] maxusers 32 [3] s/32/64 [4] maxusers 64 [5] w [6] 1907 [7] q [8]
The kernel build begins when you write and quit the editing session.
The realtime kernel that supports kernel preemption was installed previously as an option during base system installation. Now, the POSIX 1003.lb portions are included in the kernel automatically and a separate kernel is not needed. Preemption capabilities are disabled by default, but can be selected and enabled when the kernel is configured and built.
To enable realtime preemption in the kernel during the installation procedure, edit the configuration file and set the rt-preempt-opt parameter equal to 1 as shown in the following example:
rt-preempt-opt=1
The system will now automatically build a kernel and then reboot. This will take approximately 15 minutes, depending on the processor type. When the login prompt appears after the system has rebooted, use 'root' as the login name and the SUPERUSER password that was entered during this procedure, to log into the system. *** PERFORMING KERNEL BUILD *** Working....Fri Dec 13 15:45:24 EST 1996 Working....Fri Dec 13 15:47:24 EST 1996 Working....Fri Dec 13 15:49:25 EST 1996 Working....Fri Dec 13 15:51:26 EST 1996
Your system may boot to single-user mode if the boot_osflags variable was not set as described in Section 5.18. The system reboots using the new kernel when doconfig completes. To bring the system to multiuser mode, press Ctrl/d at the root prompt (#). You are prompted to enter the run level. Four run levels are available:
init[0 | s | S | 2 | 3]
What happens when you log in for the first time depends upon whether you have a graphics workstation or a text-based terminal without graphics capabilities:
Refer to the CDE Companion guide for an introduction to CDE and for information about migrating from DECwindows Motif to CDE.