This chapter describes steps that should be completed after installing software through ptx/INSTALL. Refer to the product release notes and administration documentation for information about setting up and configuring the software.
Remove the newfiles.<date-time> and oldfiles.<date-time> directories from each /usr/options subdirectory. These directories use large amounts of disk space and are no longer needed after the installation is complete.
This optional procedure applies only to INIT ALT DISK DELTA and ALT DISK DELTA installations.
The Alternate Disk Compare menu option locates any file modifications that were made on the original root disk after the image of the operating system was created on an alternate disk. This comparison should be done after booting on the alternate disk.
The Alternate Disk Compare menu option does a three-way comparison among the following files:
The files that were present on the alternate disk after the root filesystem was copied to the disk.
The files that are now present on the original root disk.
The files that are now present on the alternate disk.
The comparison creates three files: NewFiles, ClobberFiles, and ConflictFiles. The files are located in the directory /usr/options/base/altdelta.
NewFiles lists files that were added to the original root filesystem after the filesystem was copied to the alternate disk. The Alternate Disk Compare procedure can copy these files to the alternate disk.
ClobberFiles lists files that were changed on the original root filesystem after the filesystem was copied to the alternate disk. The Alternate Disk Compare procedure can copy these files to the alternate disk.
ConflictFiles specifies files that are in conflict; the version of the file currently on the alternate disk does not match either the version that is currently on the original root disk or the version that was copied to the alternate disk. You will need to examine the files and make any changes to the file on the alternate disk by hand.
To perform the Alternate Disk Compare, complete the following steps:
Mount the original root filesystem under another name such as /mnt:
# /etc/devbuild vtoc /dev/rdsk/sd0
# /etc/mount /dev/dsk/s0s0 /mnt
Start the menu system and select the Alternate Disk Compare option from the Software Management menu.
Get Files That Changed During Alternate Disk Delta Enter mountpoint for the root filesystem ___________ on the original root disk (e.g., /mnt). If the corresponding /usr directory is on a separate partition, that partition must be mounted. The alternate-disk mountpoint must be in the root directory (/mnt is valid;/a/mnt is not). Enter <y> if you want to overwrite ____________ current root disk files with New and Changed files from the original root disk after reviewing the lists. No files are saved. Conflict files must be resolved by hand. Enter <n> to only generate a list of New, Changed, and Conflict files; no files are overwritten.
The first prompt asks for the mount point for the root filesystem on the original root disk. Enter the mountpoint that you specified in step 1. (The original root filesystem must be mounted.)
The second prompt allows you to specify whether you want files on the new root filesystem (the filesystem on the alternate disk) to be automatically overwritten by the revised files from the original root filesystem.
When you select Run to execute the form, the system will generate the files NewFiles, ClobberFiles, and ConflictFiles.
If you answered N to the second prompt on the form, the files specified in NewFiles, ClobberFiles, and ConflictFiles will not be copied to the new root disk. If you want to copy the files manually, use the following commands.
$ cd /mnt
$ cpio -pdmau / < /usr/options/base/altdelta/NewFiles
$ cpio -pdmau / < /usr/options/base/altdelta/ClobberFiles
$ cpio -pdmau / < /usr/options/base/altdelta/ConflictFiles
If you answered Y to the second prompt on the form, you can view or edit the contents ofNewFiles and ClobberFiles before any files are copied. You will be prompted to press any key; when you do this, the vi editor is invoked on the files. When you exit vi, the following prompt appears:
Do you still wish to overwrite / files with the /mnt file list (y/n)?
If you answer Y, the Alternate Disk Compare procedure will copy the files specified inNewFiles and ClobberFiles to the new root disk, overwriting the files currently on the disk. Files in conflict must be viewed or copied manually. Use the cpio command shown above to copy the files.
If you answer N, you will need to view or copy the files manually. Use the cpio commands shown earlier to copy the files.
After all software is installed on your system, we strongly recommend that you create a custom miniroot. You will need to use this miniroot if it should become necessary to restore the root filesystem. See the DYNIX/ptx System Recovery and Troubleshooting Guide for information about creating a miniroot.
To ensure that problems can be diagnosed quickly, we recommend that you synchronize all time clocks on your system. If you do not do this, diagnosing certain problems can take longer because time skew between the clocks can make it difficult to correlate event entries in the system logs.
To synchronize the clocks on hosts running DYNIX/ptx, configure either timed or xntpd as described in the ptx/TCP/IP Administration Guide.
By default, EES records older than 30 days are now deleted at midnight everyday. If necessary, you can change both the number of days and the time at which the deletion takes place. To do this, use the ptx/ADMIN "EES Management" submenu. We recommend that you modify these parameters immediately after installing EES.
A new policy has been added to purge messages having the severity INFO/DEBUG/WARN from syslog. If you want to modify this policy, use the following EES command:
ees_logmgr -policy [change|delete] policy_id,...
ptx/CLUSTERS and ptx/CTC should always be installed together. If an updated version of ptx/CLUSTERS is installed and ptx/CTC is not reinstalled, the ptx/CTC menus in ptx/ADMIN will be removed. To correct this problem, reinstall ptx/CTC from the distribution CD and the menus will reappear.
ptx/LAE requires certain Red Hat® Linux V6.2 components to enable Linux binaries to run with the DYNIX/ptx kernel. The Red Hat Linux components required by ptx/LAE are installed from the CD produced by Red Hat.
The Red Hat Linux CD is not provided by IBM. Obtain it directly from any retailer of your choosing. You can use any one of the Red Hat V6.2 releases; that is, the Standard, Deluxe, and Professional releases will all work with ptx/LAE. Note that Red Hat Linux itself is not installed; only the components required by ptx/LAE.
ATTENTION Before the Red Hat Linux components can be installed, DYNIX/ptx V4.6.1 must be booted, ptx/LAE must be installed, and the new kernel recompiled and rebooted.
ptx/LAE includes a script, /etc/install_rh, that installs the necessary Red Hat Linux components (individual RPMTM packages) from the Red Hat Linux CD. The script installs the Red Hat Linux components under the directory /linux/root. The script lists the names of the components as they are installed and records an entry in /etc/versionlog for each individual RPM package. You must be root to run the script.
The install_rh script is interactive by default; however, you can use the -b option to run the script non-interactively. For information on running this script with command line options, refer to the install_rh(1LAE) man page.
You can choose to install the Red Hat Linux components directly from the distribution CD or from a filesystem to which you have already copied the full contents of the Red Hat Linux CD.
To install the necessary Red Hat Linux components, complete the following steps:
Start the install_rh script:
# /etc/install_rh
At any time during the installation, you can cancel it by pressing Ctrl-C.
Specify whether you are installing the Red Hat Linux components from the distribution CD or a filesystem:
Do you wish to install from CD or from a filesystem [CD]?
Specify the device node for the CD drive:
What is the device node for the CD-ROM drive [/dev/dsk/cd0]?
If you are installing from the distribution CD, you are prompted to install the CD in the CD drive and press Enter.
Several lines of output are displayed as install_rh prepares for and installs the Red Hat Linux components. Errors are printed when any rpm packages fail to install correctly. Additionally, a log file containing warnings is created in /usr/options. Log file names start with the string laelog. and end with a numeric string. For example, the file laelog.4537 represents a log file created by install_rh.
Remove the Red Hat distribution CD from the CD drive.
Once the Red Hat Linux components are installed, you can install and run Linux applications on DYNIX/ptx. For details, refer to the ptx/LAE Release Notes.
Once installed, ptx/NFS cannot be deinstalled.
The Licensed Internal Code (LIC) microcode needed for the Disk Array Storage System (DASS) is installed with ptx/RAID. Refer to the ptx/RAID Release Notes for information about downloading the LIC.
Also verify that the scsidisk_standard_timeout parameter is set correctly. The parameter is in the /usr/conf/uts/io/scsidisk/scsidisk_space.c file and should be set as follows:
int scsidisk_standard_timeout = 150; /* seconds (was 35) */
When using media changer devices, you should use the mcbuild utility to associate tape drives with each media changer or library device. You can create or update these associations at any time-a system reboot is not required.
When mcbuild is not used, a media changer driver tries to determine the names of its connected tape drives the first time the media changer device is opened. The media changer driver then keeps those tape drive names until the system is rebooted. This method works most of the time, especially when there is only one media changer on the host and all the tape drives connected to the host are in the media changer. However, because the media changer device cannot return unique identifiers for the tape drives connected to it, the media changer driver has no way to positively associate a tape drive with that media changer device. Also, if you rename a tape device with the devctl command, the output from the mc command does not reflect the current device configuration until the system is rebooted.
To prevent these problems, you should use the mcbuild utility to explicitly associate tape drives with every media changer on the host. Even if you only have one media changer on the host, it is a good system administration practice to use the mcbuild utility.
To use the mcbuild utility to associate tape drives to media changer devices, complete the following steps:
Create or edit the /etc/mctab file to contain one line for each media changer device and its associated tape drives.
ATTENTION Any time you add, remove, or rename media changers or the tape drives in these media changers, you must update the /etc/mctab file to reflect the current device configuration. Otherwise, the output from the mc command will not reflect the changes.
Each line in the /etc/mctab file should have this format:
mc_device_name drive1 drive2 drive3 ...
For example, to associate the tape drives tl0 through tl3 with the HP DLT4000 library /dev/mch/ml0 and to associate the tape drives tl4 through tl8 with the STK 9710 library /dev/mch/mw0, add the following lines to the /etc/mctab file:
/dev/mch/ml0 tl0 tl1 tl2 tl3 tl4
/dev/mch/mw0 tl5 tl6 tl7 tl8 tl9
If you do not know which tape drives belong to which library, you can determine this information as follows:
To determine a tape drive that belongs to a specific DDS-2 or DDS-3 library, identify the SCSI bus ID for the library (ms device) and then locate the tape drives (td devices) that are located on the same SCSI bus.
Use the same method to determine the first two tape drives that belong to a specific HP DLT4000 library. Identify the SCSI bus ID for the library (ml device) and then locate the two tape drives (tl devices) that are located on the same SCSI bus. If the HP DLT4000 library contains four tape drives, the third and fourth tape drives will be the next two tl devices, typically located on the next SCSI bus.
For a STK 9710 or STK 9730 library, first identify the SCSI bus ID for the library (mw device). If drives were installed according to the recommended procedure, they will be in the following locations:
On a STK 9710 library, DLT4000 drives (tl devices) will be at SCSI IDs 0-4. DLT7000 drives (tl devices) will be at SCSI IDs 0-4 and 10-15. If the library contains both DLT4000 and DLT7000 drives, the DLT4000 drives will be at the lower SCSI IDs.
For the STK9730 library, DLT4000 and DLT7000 drives will be at SCSI IDs 0-4.
The lowest ID is typically in the lowest position in the library. For example, drive tl5 will be at SCSI ID 0. In dumpconf output, the unit number corresponds to the SCSI ID.
Run the mcbuild utility to associate the tape drives and media changers that are defined in the /etc/mctab file.
# mcbuild
After installing ptx/SPDRIVERS software and appropriate hardware, you can verify that the software is properly detecting the hardware. Complete the following steps:
Use the dumpconf command to verify that the appropriate devices were found at system boot. Following is sample output for td devices:
# /etc/dumpconf -d | grep td
td0 td 0 0x00000000 S scsi scsibus2
td1 td 1 0x00000010 S scsi scsibus2
td2 td 2 0x00000010 S scsi scsibus17
td3 td 3 0x00000020 S scsi scsibus17
td4 td 4 0x00000030 S scsi scsibus17
td5 td 5 0x00000040 S scsi scsibus17
Use the dumpconf command to verify that the appropriate media changers (libraries) were found at system boot. The following output is for ml and mx devices:
# /etc/dumpconf -d | egrep "ml | mx"
mx0 mx 0 0x00000040 S scsi scsibus3
ml0 ml 0 0x00000050 S scsi scsibus9
Run the infodev -a command on each device to verify that the output returned from the SCSI inquiry command is as expected. (There must be a tape in the drive when you run this command.) For example, to display information for /dev/rmt/tl0, enter the following command:
# infodev -a /dev/rmt/tl0
At this point, you may want to verify the operation of each library or tape drive. To do this, load a tape into each drive, write data to the tape, read data from the tape back to the system, and verify the write/read operation. You should use tar or cpio to perform these basic operational tests.
To complete the installation, follow the procedure entitled "Start the ptx/SVM Configuration Daemon" in Chapter 2 of the ptx/SVM Administration Guide. Then read the ptx/SVM Administration Guide for information about laying out your ptx/SVM system, placing disks under ptx/SVM control, and creating disk groups and objects.
To complete the installation, refer to the ptx/SYNC Release Notes and continue with the procedure corresponding to your system's architecture.
Ensure that you have your original version of the /etc/inetd.conf file. You may also need to make the following change to this file.
The version of reshd distributed with this release requires a service type of stream. Locate the entry for shell in the /etc/inetd.conf file. If the entry specifies the tli service type, as in the following example, you will need to change it to stream.
shell tli tcp nowait root /usr/etc/reshd reshd -R
The corrected entry is as follows:
shell stream tcp nowait root /usr/etc/reshd reshd -R
If you do not make this change, remote resh services will not function.
If you saved your previous ptx/X.25 configuration, complete the following steps to restore that configuration.
ATTENTION The configuration files supplied with the newly installed version of ptx/X.25 will be overwritten by the saved configuration files. If you want to save the new configuration files before they are overwritten, follow the procedure in the section "Updates of ptx/X.25" in Chapter 2.
As root, enter the following command, where directory is the directory in which you saved the configuration.
# /usr/lib/x25/rstx25conf directory
When the following message appears, answer y to confirm that you want to restore the saved X.25 configuration.
WARNING WARNING WARNING Restoring X.25 configuration will overwrite existing files. It will overwrite some files even if you are not using them currently. Are you sure you want to restore X.25 configuration? (y/n)
If your /usr/lib/x25/x25d.action file contains a reference to xlogind, the following message appears:
Please edit the file /usr/lib/x25/x25d.action to change
/usr/etc/xlogind to /bin/login
You may want to edit this file, because the xlogind program is no longer used in the ptx/X.25 product.
When the X.25 configuration files have been restored, the following message appears:
Saved X.25 configuration has been restored
If the HDLC Baud Rate parameter is set to a non-zero value in any of the restored configuration files, the following message appears:
The Level II parameter HDLC Baud Rate MUST be set to 0 if clock is provided by an external source. This parameter must be set correctly for the X.25 network to operate The following parameter files have this parameter set to a non-zero value. If you use them, be sure to check this parameter's value.
List of files
A non-zero HDLC baud rate indicates that clocking will be provided by an internal source. Internal clocking is supported only on the SCC-I board. If you are using ptx/X.25 with an SCC-V or DCP 8804 board, the HDLC baud rate must be set to 0. You can change this parameter on the Other Level 2 Parameters form during ptx/X.25 configuration.
When the following prompt appears, press Return, then y and Return:
The format of parameter files has changed for this release of ptx/X.25. The following parameter files are not valid
List of files
.
.
EOF (Press <Return> here)
Would you like me to fix ALL of them? (y/n)
This will convert the restored configuration files to the new format. Note that if you do not convert these files, you cannot use them with this release of ptx/X.25.
Ignore error messages with the following form:
/usr/lib/x25/x25fixfile: error in file filename for parameter use_d_bit
After the saved configuration files have been restored, you can remove the saved directory structure. Before removing the directory, ensure that there are no files in the directory that you wish to save. Then enter the following command, where directory is the directory in which you saved the configuration.
# rm -r directory
If you rebooted the operating system after installing ptx/XWM, the system will restart xdm automatically. If you did not reboot, the previous version of xdm will still be running. To start the new version of xdm, complete the following steps:
ATTENTION The name of the font server binary was changed from fs to xfs in ptx/XWM.
If you plan to use the font server, change the following line in the /usr/lib/X11/fs/config file as necessary so that the ordered list of font path elements can be accessed from the host running xfs.
catalogue =
This font path is often the same as the font path used by X terminals at your site. For more information, refer to the xfs(1) man page and to the font server information in O'Reilly, X Window System Administrator's Guide, Volume 8.
The X11R5 libraries must be linked dynamically. If you have an application that must link with the X11R5 libraries in the directory /usr/X11R5/lib, and must also link statically (using the compiler option -Bstatic) with other libraries, you will need to specify -Bdynamic to link the X11R5 libraries.
To link the X11R5 libraries, you must either specify a cc command line option (-L/usr/X11R5/lib) or set an environment variable as described in the ptx/XWM Release Notes. In addition, either allow the dynamic libraries to be linked by default, or, if any other libraries are linked statically with -Bstatic, use -Bdynamic before linking the Motif and X11 libraries. Following are some examples.
Link all libraries dynamically by default:
cc ... -luserlib1 ... -L/usr/X11R5/lib -lMrm
-lXm -lXt -lXext -lX11 ...
Link initial libraries statically and the remaining libraries dynamically:
cc ... -Bstatic -luserlib1 ... -Bdynamic -L/usr/X11R5/lib
-lMrm -lXm -lXt -lXext -lX11 ...
Link libraries before and after the X11R5 libraries statically; link the X11R5 libraries dynamically:
cc ... -Bstatic -luserlib1 ... -Bdynamic -L/usr/X11R5/lib
-lMrm -lXm -lXt -lXext -lX11 -Bstatic ...
To create an executable version of emacs, first become superuser; then complete the following steps.
Go to the /usr/local/gnu/emacs directory:
# cd /usr/local/gnu/emacs
If you want to build an X-windows version of emacs and ptx/XWM is currently installed on your system, edit src/config.h and remove the comment characters from this line:
/* #define HAVE_X_WINDOWS */
The line should look like this:
#define HAVE_X_WINDOWS
You must also modify the following line in src/m-ptx4-0.h:
#define LIBX11_SYSTEM -linet -lnsl -lsocket
#define LIBX11_SYSTEM -lsocket -lnsl
If you did not edit the config.h file as described in step 2, set the modification date on the file by typing the following command:
# touch src/config.h
If the public software was previously installed on your system and emacs was set up, run the following commands:
# cd /usr/local/gnu/emacs
# make clean
Run make and put the process in the background:
# make > make.out 2>&1 &
To view the make output, enter the following command:
# tail -f make.out
When the build is complete, an executable version of emacs will be in /usr/local/gnu/emacs/src/emacs-18.57.<number>, which is linked to /usr/local/gnu/emacs/src/xemacs. The value of <number> increases by one each time you recompile emacs.
Install emacs on your system. Typically, you should enter the following commands to install emacs:
# cd /usr/local/gnu/emacs
# cp src/xemacs /usr/local/bin/emacs
# chmod 755 /usr/local/bin/emacs
For the movemail program to function properly, its group-ID must be set to mail. Otherwise, many mail readers for emacs will not work properly. Enter the following commands:
# cd /usr/local/gnu/emacs/etc
# chgrp mail movemail
# chmod 2755 movemail
To prevent writing collisions, which can occur if two users attempt to write to the same file at the same time, enter the following commands:
# cd /usr/local/gnu/emacs
# mkdir lock
# chmod 1777 lock
The installation is now complete. For more information about emacs, refer to the README and INSTALL files in /usr/local/gnu/emacs.
The README file in /usr/local/less tells how to install less on your system. For less to work properly, you must include /usr/local/bin in your path.
After running sh linstall as described in the README file, you will need to modify the makefile. Locate the following line:
LIBS = -lcurses -lPW
Add -lseq to the end of the line:
LIBS = -lcurses -lPW -lseq
The mkisofs utility can be used to create a binary image of an IS0 9660 filesystem (with Rock Ridge extensions). You can then use cdrecord to copy the image to a compact disc. You will need to build mkisofs as described in the mkisofs.mk makefile. Refer to the mkisofs man page for information about using the utility. For information about cdrecord, see DYNIX/ptx System Administration.