HP−UX Installation UNIX Installation Procedures

Chapter 26: UNIX Installation

26.1 Introductory Notes

The first step in dealing with an UNIX system is to install the operating system itself. On a UNIX platform, delivered systems with the OS preinstalled is more an exception than the rule. In any case, among the administrative duties are the UNIX installation when we say UNIX installation we are thinking UNIX OS installation and the initial configuration of the installed UNIX system that will allow access for further upgrades. UNIX installation per se should not be a problem. There are two main reasons why: The installation procedure is usually well documented; the provided documentation usually covers all possible installation scenarios, as well as potential troubleshooting. 1. The system is not in an operational stage, and we are relaxed during the installation. It is easy to repeat an installation procedure if something is going wrong, we have started everything from scratch, so we can do the same again. 2. Nevertheless, any real installation example is always welcome and helpful. Different installation scenarios and options, and a general installation approach in the provided documentation can sometimes be confusing. Existing dilemmas can be quickly resolved if we have an appropriate installation case in front of us. This is the purpose of this chapter. A few installation examples for the currently most common UNIX flavors — Solaris, HP−UX, and Linux — could be very helpful in a number of real installation cases, and also very educational for the readers. OS installation is the first step in making a UNIX system workable. However, this is not the only step in accomplishing this task, as well as keeping a UNIX system compliant with unavoidable upgrades, updates, and patches. The second part of this chapter addresses these issues. For both parts it is assumed that we have workable hardware in front of us, that we have access to the system console, and that the CD drive is available.

26.2 UNIX Installation Procedures

In this part, the installation procedure examples for a few common UNIX flavors are documented. Despite the fact that they are sufficiently general and applicable for listed UNIX flavors, they are also site−specific. Please keep in mind that some differences in the installation procedures caused by different system hardware configurations andor operating system versions and releases are always possible. This is the reason why, in each of the examples that follow, the relevant initial information is always provided.

26.2.1 HP−UX Installation

The following text describes in detail steps performed in installing HP−UX 10.20 operating system on the Series 800 HP system — model E35; the host is named blue in this example. The described installation procedure also includes a mirroring of the root filesystem, which is realized as a single filesystem that also includes usr and var. Power−on the system. 1. Insert the HP−UX 10.20 Install and Core OS CD into the CD drive. 2. Follow messages on the console. Pay attention to the message: 3. 657 and hit any key. Respond to questions: Boot from primary boot path Y or N? n ♦ Boot from alternate boot path Y or N? n ♦ Enter boot path, command, or ? boot 5652.2 or corresponding CD hardware path ♦ Since the CD was selected hardware path 5652.2, respond to the question: Interact with IPL Y or N? n ♦ 4. The Install Program on the CD is started, and the Welcome Screen appears. Select Install HP−UX and continue dialogue. Would you like to enable networking now? y ♦ 5. The screen: HP−UX Install Utility — Network Configuration hostname blue ip address: XX.XX.XX.XX enter corresponding IP address router: XX.XX.XX.XX enter corresponding IP address netmask 255.255.255.0 or another netmask Select OK. 6. The screen: HP−UX Install Utility — Select System Root disk Select 5652.6.0 for the primary boot disk or corresponding disk hardware path. 7. The screen: HP−UX Install Utility — Select Whole System Configuration Select LVM Configuration with VxFS Journaled file system. Select OK. 8. The screen: HP−UX Install Utility — ViewModify Basic Configuration Primary swap size for example 1200, or accept offered value Secondary swap size none Software selection CDE Runtime Environment Software language English Locale setting default FS file name length Long home Configuration none How many disks in root group one Make volatile dirs separate true Create export volume false Select OK. 9. The screen: HP−UX Install Utility — Configure File System mount size volume disk directory MB usage group 1420 VxFS vg00 stand 48 HFS vg00 swap 560 swap vg00 Select OK. 10. 658 The screen: HP−UX Install Utility — Enter SD−UX swinstall information Do you want to interact with SD−UX swinstall? No ♦ Select OK. The swinstall procedure continues; it takes almost one hour. Once it is completed, log in to the system as root and set the password. 12. Once the HP−UX OS is installed, the system itself should be appropriately configured for its mission. The following text describes the most common needed administrative steps to customize the installed system. Of course, the described steps are not mandatory — they are very much site−dependent; please read them as appropriate. Also, HP−UX provides a menu−based tool, system administration manager SAM, to help in the system administration — it is available upon OS installation. In some of the following steps, SAM is used to accomplish specific tasks. Log in as root. 13. Using vi modify the file etcissue to reflect the hosts name blue. blue [HP Release B.10.20] 14. Createprepare configuration files for Automounter if needed. This step is site−specific and probably could be skipped in most installations. In this example Automounter is used to mount home and share filesystems exported by the NFS server; and NIS maps specify the configuration data. etcauto_direct: +auto_direct etcauto_master: − auto_direct −ro net −hosts −rw home auto_home −rw share auto_share −rw etcauto_home: +auto_home etcauto_share: +auto_share 15. Modifyprepare the following files for NIS: etcpasswd etcgroup Add NIS marker + as the last line in the file; it will be in effect until the etcnsswitch.conf file is created. Again this step probably could be skipped; in this example NIS is implemented. 16. For most of the network−related services that follow, it is easier to use the SAM tool than to modify configuration files from the command line. However, such an approach is also acceptable. Enter sam to start SAMfrom the command line. 17. Select Networking and Communications. Select Name Service Switch. For each displayed entry, select ActionConfigure Name Service Switch and provide the necessary data. 18. 659 Select ActionSet Domain Name and set to domain−name enter the name for your NIS domain if applicable at all. Select Networked File System. Select Mounted Remote File Systems. Select ActionEnable Automounter. Note If there are problems, please check the rc configuration file etcrc.config.dnamesvrs it includes configuration data for NIS and etcrc.config.dnfsconf for NFS client and Automounter. Return to the SAM Main Menu and select Time. Select NTP Network Time Resources. Select ActionAdd Remote Server or Peer… Enter Host Name: ntphostor the name of the time server. Select ActionStart NTP. 19. Return to the SAM Main Menu and select Printer and Plotters. Select LP Spooler. Select Printer and Plotters. Select ActionAdd Remote PrinterPlotter. Printer name: printer−name Remote system: system−name Remote printer name: remote−name for network printer LF1 Make the printer default one; select ActionSet as Default Destination. Return to the SAM Main Menu and exit. 20. Createprepare the file etcshells to include all shells that FTP users could use. Otherwise, the FTP access to the system would be restricted. 21. Modify the system−wide file etcprofile to reflect your login needs. 22. Build the whatis database. Execute catman −w— it takes a while. 23. At this point the basic system configuration is set and the system is ready for use.

26.2.2 Solaris Installation