Cray Open Software Release Overview and Installation Guide

S–2350–40

© 2001–2007 Cray Inc. All Rights Reserved. This manual or parts thereof may not be reproduced in any form unless permitted by contract or by written permission of Cray Inc. U.S. GOVERNMENT RESTRICTED RIGHTS NOTICE The Computer Software is delivered as "Commercial Computer Software" as defined in DFARS 48 CFR 252.227-7014. All Computer Software and Computer Software Documentation acquired by or for the U.S. Government is provided with Restricted Rights. Use, duplication or disclosure by the U.S. Government is subject to the restrictions described in FAR 48 CFR 52.227-14 or DFARS 48 CFR 252.227-7014, as applicable. Technical Data acquired by or for the U.S. Government, if any, is provided with Limited Rights. Use, duplication or disclosure by the U.S. Government is subject to the restrictions described in FAR 48 CFR 52.227-14 or DFARS 48 CFR 252.227-7013, as applicable. Cray, LibSci, UNICOS and UNICOS/mk are federally registered trademarks and Active Manager, Cray Apprentice2, Cray C++ Compiling System, Cray Fortran Compiler, Cray SeaStar, Cray SeaStar2, Cray SHMEM, Cray Threadstorm, Cray X1, Cray X1E, Cray XD1, Cray XMT, Cray XT, Cray XT3, Cray XT4, CrayDoc, CRInform, Libsci, RapidArray, UNICOS/lc, and UNICOS/mp are trademarks of Cray Inc. Acrobat Reader and PostScript are trademarks of Adobe Systems, Inc. Apache is a trademark of The Apache Software Foundation. GNU is a trademark of The Free Software Foundation. Kerberos is a trademark of Massachusetts Institute of Techology. Linux is a trademark of Linus Torvalds. Mac OS is a trademark of Apple Computer, Inc. Platform is a trademark of Platform Computing Corporation. Windows is a trademark of Microsoft Corporation. UNIX, the “X device,” X Window System, and X/Open are trademarks of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners. The UNICOS, UNICOS/mk, and UNICOS/mp operating systems are derived from UNIX System V. These operating systems are also based in part on the Fourth Berkeley Software Distribution (BSD) under license from The Regents of the University of California.

Contents

Page

Preface
Accessing Product Documentation Conventions . . . . . . . . . . . . . . . . . Reader Comments Cray User Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

v v vi vii vii 1 . . . . . . . . . . . . . . . . . . . 1 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3 4 5 5 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7 8 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11
i

Introduction [1]
Emphasis for the COS 4.0 Release

Software Enhancements [2]
New Fully Supported Components Existing Components Updated to a New Version Packages Removed in the COS 4.0 Release SPRs Addressed Since the Last Release

COS Field Notices (FNs) Since the Last Release

Compatibilities and Differences [3]
The prngd and sshd Daemon Starting Order Separate coreutils Module . . . .

Cray J90, Cray SV1, and Cray T3E System Binaries Removed

Limitations [4]
Problems with All OpenSSH Versions Limitations for COS Components

Documentation [5]
CrayDoc Documentation Delivery System Accessing Product Documentation
S–2350–40

.

Cray Open Software Release Overview and Installation Guide
Page

Manuals Provided with This Release Ordering Documentation . . .

. .

. .

. .

. .

. .

. .

. . .

. . .

. . .

. . .

. . .

. . .

. . .

. . .

. . .

. . .

. . .

. . .

. . .

12 12 13 15

Related Documentation Not Provided with This Release

Release Package [6]
Hardware and Software Requirements Contents of the Release Package Fully Supported Components bash — GNU Version 3.2 bc — GNU Version 1.06 bison — GNU Version 2.3 coreutils — GNU Version 6.4 CVS — GNU Version 1.11.21 diffutils — GNU Version 2.8.1 emacs — GNU Version 21.4 flex — GNU Version 2.5.33 fsplit — Version 12.5.00 GMP — GNU Version 4.1.4 gnuplot — GNU Version 3.7.3 grep — GNU Version 2.5.1a gzip — GNU Version 1.3.3 less — GNU Version 394 make — GNU Version 3.81 netperf — Version 2.4.2 OpenSSH — Version 4.5p1 OpenSSL — Version 0.9.7l patch — GNU Version 2.5.4 Perl — Version 5.8.8
ii

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . .

15 15 15 15 16 16 16 17 17 18 18 18 18 18 19 19 19 20 20 20 21 21 21 22 22 22
S–2350–40

. . . . . .

. .

.

findutils — GNU Version 4.2.25 . . . . . . . . . . . . . . .

gawk — GNU Version 3.1.5

pe-version — Version 20040303 . .

Contents
Page

prngd — Version 0.9.29 sed — GNU Version 4.1.4 sudo — Version 1.6.8p12 tar — GNU Version 1.16 tcl — Version 8.4.14 tk — Version 8.4.14 top — Version 3.5 zlib — Version 1.2.3 . . . . .

.

. . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . .

22 23 23 23 24 24 24 24 25 25 25 26 26 26 26 27 27 27 27 28 28 28 29 31

rsync — GNU Version 2.6.8 . . . . . .

Lightly Supported Components autoconf — GNU Version 2.60 automake — GNU Version 1.10 expect — Version 5.43 groff — GNU version 1.19 m4 — GNU Version 1.4.4 Python — Version 2.3.3 ruby — Version 1.8.5 vim — Version 7.0 . . . . . . . . . . . . . . . . . .

. . . . . . . . . . .

TeXinfo — GNU Version 4.8 Unsupported Components Licensing . . . . . . . . .

gdb — GNU Version 50-1.10 Ordering Software

Customer Services [7]
Technical Assistance with Software Problems CRInform System Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31 31 32 33 33

Cray Service Bulletin (CRSB) Cray Public Website

S–2350–40

iii

Cray Open Software Release Overview and Installation Guide
Page

Installation of Cray Open Software [8]
Preinstallation Setup on the Cray Mainframe Installing the Precompiled Binaries Installation Using CIT Non-CIT Installation Source Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35 35 35 35 36 37 37 38 38 40 40 40 41 41 42 42 43

Preparation for Installation of Precompiled Binaries

Preparation for Source Installation Source Installation Procedures Installing Module Files . .

Making 40 the Default open Package

Loading Modules and Accessing Packages After Installation Instructions for UNICOS/mp Systems Only Verification of Security Files and Related Daemons Changes for Relative and Absolute Path Names

Using Cray Open Software in an Cray X1 Compile Environment

Index Tables
Table 1. Manuals Provided with This Release . . . . . . . . . . . . . . .

12

iv

S–2350–40

Preface

The information in this preface is common to Cray documentation provided with this software release.

Accessing Product Documentation
With each software release, Cray provides books and man pages, and in some cases, third-party documentation. These documents are provided in the following ways: CrayDoc The Cray documentation delivery system that allows you to quickly access and search Cray books, man pages, and in some cases, third-party documentation. Access this HTML and PDF documentation via CrayDoc at the following locations: • The local network location defined by your system administrator • The CrayDoc public website: docs.cray.com Man pages Access man pages by entering the man command followed by the name of the man page. For more information about man pages, see the man(1) man page by entering:
% man man

Third-party documentation Access third-party documentation not provided through CrayDoc according to the information provided with the product.

S–2350–40

v

Cray Open Software Release Overview and Installation Guide

Conventions
These conventions are used throughout Cray documentation: Convention command Meaning This fixed-space font denotes literal items, such as file names, pathnames, man page names, command names, and programming language elements. Italic typeface indicates an element that you will replace with a specific value. For instance, you may replace filename with the name datafile in your program. It also denotes a word or concept being defined. This bold, fixed-space font denotes literal items that the user enters in interactive sessions. Output is shown in nonbold, fixed-space font. Brackets enclose optional portions of a syntax representation for a command, library routine, system call, and so on. Ellipses indicate that a preceding element can be repeated. Denotes man pages that provide system and programming reference information. Each man page is referred to by its name followed by a section number in parentheses. Enter:
% man man

variable

user input

[] ... name(N)

to see the meaning of each section number for your particular system.

vi

S–2350–40

Preface

Reader Comments
Contact us with any comments that will help us to improve the accuracy and usability of this document. Be sure to include the title and number of the document with your comments. We value your comments and will respond to them promptly. Contact us in any of the following ways: E-mail: docs@cray.com Telephone (inside U.S., Canada): 1–800–950–2729 (Cray Customer Support Center) Telephone (outside U.S., Canada): +1–715–726–4993 (Cray Customer Support Center) Mail: Customer Documentation Cray Inc. 1340 Mendota Heights Road Mendota Heights, MN 55120–1128 USA

Cray User Group
The Cray User Group (CUG) is an independent, volunteer-organized international corporation of member organizations that own or use Cray Inc. computer systems. CUG facilitates information exchange among users of Cray systems through technical papers, platform-specific e-mail lists, workshops, and conferences. CUG memberships are by site and include a significant percentage of Cray computer installations worldwide. For more information, contact your Cray site analyst or visit the CUG website at www.cug.org.

S–2350–40

vii

Introduction [1]

This document describes the Cray Open Software (COS) 4.0 release. Cray Open Software consists of source packages of publicly available software and precompiled binaries for Cray X1 systems, and the complete source and product licenses for each included package. Note: The COS 3.6 release was the last release containing Cray J90, Cray SV1, and Cray T3E binaries. Sites may still submit SPRs against the binaries for Cray J90, Cray SV1 and Cray T3E systems. Source code, containing Cray updates, is still provided so that sites can compile their own utilities. For a description of the many different open source packages that comprise the COS 4.0 release, categorized by the level of Cray support available for those packages, see Section 6.2.1, page 15 (fully supported), Section 6.2.2, page 25 (lightly supported), and Section 6.2.3, page 28 (unsupported). Many of the utility programs in Cray Open Software are similar to those provided in UNICOS/mp programs but provide options that are either not available in or behave differently than their UNICOS/mp counterparts. Adding these widely available, public-domain programs to your Cray system eases the transition path for programs that already use these utilities.

1.1 Emphasis for the COS 4.0 Release
Cray Open Software was updated from COS 3.6 to COS 4.0 to add the emacs and rysnc packages and provide updates to autoconf, automake, bash, bison, coreutils, CVS, findutils, flex, gawk, GMP, gnuplot, grep, less, m4, make, netperf, OpenSSH, OpenSSL, Perl, prngd, ruby, sed, sudo, tar, Tcl, Tk, vim, and zlib packages. The pstree package has been removed. Non-CIT installation is now supported.

S–2350–40

1

Cray Open Software Release Overview and Installation Guide

2

S–2350–40

Software Enhancements [2]

The COS 4.0 release contains new and updated features described in the following sections. Note: For a description of the many different open source packages that comprise the COS 4.0 release, categorized by the level of Cray support available for those packages, see Section 6.2.1, page 15 (fully supported), Section 6.2.2, page 25 (lightly supported), and Section 6.2.3, page 28 (unsupported).

2.1 New Fully Supported Components
The following fully supported COS components are new for the COS 4.0 release: Note: For the definition of "fully supported" and a description of these and all the fully supported components in this COS release, see Section 6.2.1, page 15. • emacs — GNU version 21.4 • rsync — GNU version 2.6.8

2.2 Existing Components Updated to a New Version
The following existing COS components had version updates for this release: • autoconf was updated to version 2.60 • automake was updated to version 1.10 • bash was updated to version 3.2 • bison was updated to version 2.3 • coreutils was updated to version 6.4 • CVS was updated to version 1.11.21 • findutils was updated to version 4.2.25 • flex was updated to version 2.5.33 • gawk was updated to version 3.1.5

S–2350–40

3

Cray Open Software Release Overview and Installation Guide

• GMP was updated to version 4.1.4 • gnuplot was updated to version 3.7.3 • grep was updated to version 2.5.1a • less was updated to version 394 • m4 was updated to version 1.4.4 • make was updated to version 3.81 • netperf was updated to version 2.4.2 • OpenSSH was updated to version 4.5p1 • OpenSSL was updated to version 0.9.7l • Perl was updated to version 5.8.8 • prngd was updated to version 0.9.29 • ruby was updated to version 1.8.5 • sed was updated to version 4.1.4 • sudo was updated to version 1.6.8p12 • tar was updated to version 1.16 • Tcl was updated to version 8.4.14 • Tk was updated to version 8.4.14 • vim was updated to version 7.0 • zlib was updated to version 1.2.3

2.3 Packages Removed in the COS 4.0 Release
The following package was removed in the COS 4.0 release: • pstree — 19.3

4

S–2350–40

Software Enhancements [2]

2.4 SPRs Addressed Since the Last Release
The following SPRs were addressed since the COS 3.6 release, with fixes included in the COS 4.0 release: 725960 728283 729656 729967 730250 730346 730454 730696 731650 733319 733693 733902 MINIPERL ABORTS WITH EXCEPTION CODE: 9, ADDRESS ERROR GMAKE SHOULD USE 'FTN' INSTEAD OF 'CF77' WHEN COMPILING FORTRAN FILES CRAY OPEN SW NEEDS NO-CIT INSTALLATION METHOD COREUTILS 3.6 SORT IGNORES -R OPTION UPDATE OPENSSH TO VERSION 3.9 OPENSSH INSTALLATION DOES NOT MENTION LOOKING AT NEW CONFIG FILES UPDATE OPENSSL TO 0.9.7E SSH HANGS IN PRNGD COS 3.6 FIND ABORTS WHEN GIVEN -LS OPTION OPENSSL GENERATES MEMORY FAULT SSHD MEMORY LEAK ON KEY_READ DECODE ERRORS OPEN MODULE PROVIDES INCORRECT LIBRARY AND INCLUDE PATHS

2.5 COS Field Notices (FNs) Since the Last Release
Listed here are the FNs were addressed since the COS 3.6 release, with fixes included in the COS 4.0 release: • 5232 — COS 3.6 OpenSSH user limit problem

S–2350–40

5

Cray Open Software Release Overview and Installation Guide

6

S–2350–40

Compatibilities and Differences [3]

This chapter describes compatibility issues and functionality changes to be aware of when using this software after upgrading from the previous release of this software.

3.1 The prngd and sshd Daemon Starting Order
The prngd pseudo-random number generator daemon package is included in the COS release for better gathering of random (entropy) data for the OpenSSH daemon (sshd). Therefore, the prngd daemon must be started before the sshd daemon will start. If you want to modify the commands that the prngd daemon uses to gather the random data, modify the /opt/open/40/etc/prngd.conf file and restart the prngd daemon (only). If you do not want to use the prngd daemon, you must rebuild the OpenSSH package. Then, if you want to modify the commands that the sshd daemon (without prngd) uses to gather the random data, modify the /opt/open/40/etc/ssh_prng_cmds.conf and restart the sshd daemon. For more information about the prngd and OpenSSH packages in COS, see Section 6.2.1.24, page 22 and Section 6.2.1.19, page 21, respectively.

3.2 Separate coreutils Module
In COS 3.6, the separate coreutils package was split out into its own coreutils module to reduce some of the confusion between the COS version and the Cray mainframe operating system version of the coreutils utilities. To access the utilities in the coreutils module instead of those versions in the Cray mainframe operating system, you need to specifically run the module load coreutils command. For more information about coreutils package in COS, see Section 6.2.1.4, page 16.

S–2350–40

7

Cray Open Software Release Overview and Installation Guide

3.3 Cray J90, Cray SV1, and Cray T3E System Binaries Removed
The COS 3.6 release was the last release containing Cray J90, Cray SV1, and Cray T3E binaries. Sites may still submit SPRs against the binaries for Cray J90, Cray SV1 and Cray T3E systems. Source code, containing Cray updates, is still provided so that sites can compile their own utilities.

8

S–2350–40

Limitations [4]

This chapter describes significant limitations or problems related to using Cray Open Software.

4.1 Problems with All OpenSSH Versions
Any OpenSSH program started in the background (that is, started as a shepherd daemon by the master sshd to control the individual logging in) that does not redirect stdin, stdout, and stderr will cause that particular shepherd daemon to exist until the process closes its file descriptors (either by normal function or by death of the process). Using Compression with PrivilegeSeparation is now allowed. It is recommended that Compression be set to "Delayed" in sshd_config. For more information about OpenSSH, see: http://www.openssh.org

4.2 Limitations for COS Components
The Cray Open Software 4.0 release is UNICOS/mp only.

S–2350–40

9

Cray Open Software Release Overview and Installation Guide

10

S–2350–40

Documentation [5]

This chapter describes the documentation that supports the COS 4.0 release. Note: If a COS 4.0 Errata is required, it is provided in printed form with the product release package. It includes changes identified after the documentation for this release was packaged. Contact your Cray Service representative for problems published in Field Notices (FNs).

5.1 CrayDoc Documentation Delivery System
The CrayDoc documentation delivery system, along with product documentation, is provided with each Cray software release. The CrayDoc software runs on any operating system based on UNIX systems or systems like UNIX including Mac OS X, Linux, BSD, and anywhere else that Perl and Apache can be compiled from source code with freely available (GNU) tools. The installation and administration of the CrayDoc server software and Cray documentation are described in CrayDoc Installation and Administration Guide.

5.2 Accessing Product Documentation
With each software release, Cray provides books and man pages, and in some cases, third-party documentation. These documents are provided in the following ways: CrayDoc The Cray documentation delivery system that allows you to quickly access and search Cray books, man pages, and in some cases, third-party documentation. Access this HTML and PDF documentation via CrayDoc at the following locations: • The local network location defined by your system administrator • The CrayDoc public website: docs.cray.com Man pages Access man pages by entering the man command followed by the name of the man page. For more information about man pages, see the man(1) man page by entering:
% man man

S–2350–40

11

Cray Open Software Release Overview and Installation Guide

Third-party documentation Access third-party documentation not provided through CrayDoc according to the information provided with the product.

5.3 Manuals Provided with This Release
The manuals provided with this release are listed in Table 1, which also notes whether each manual was updated and whether it is also provided in hard copy. Most manuals are provided in HTML and all are provided in PDF.

Table 1. Manuals Provided with This Release Manual Title Cray Open Software Release Overview and Installation Guide1 Common Installation Tool (CIT) Reference Card CrayDoc Installation and Administration Guide1 Publication S–2350–40 S–2218–20 S–2340–40 Updated? Yes No Yes

5.4 Related Documentation Not Provided with This Release
The following documents are not provided with this release but might contain helpful information: • SSH, The Secure Shell: The Definitive Guide, Daniel J. Barret & Richard Silverman, O'Reilly & Associates: Sebastool, 2001. • Web pages for each of the utilities in the COS release package (refer to each utility listed in Section 6.2.1, page 15, Section 6.2.2, page 25, and Section 6.2.3, page 28).

1 12

Cray also provides this document in printed form.
S–2350–40

Documentation [5]

5.5 Ordering Documentation
To order Cray software documentation, contact your Cray representative or contact the Cray Software Distribution Center in any of the following ways: E-mail: orderdsk@cray.com Telephone (inside U.S., Canada): 1–800–284–2729 (BUG CRAY), then 605–9100 Telephone (outside U.S., Canada): +1–651–605–9100 Fax: +1–651–605–9001 Mail: Software Distribution Center Cray Inc. 1340 Mendota Heights Road Mendota Heights, MN 55120–1128 USA

S–2350–40

13

Cray Open Software Release Overview and Installation Guide

14

S–2350–40

Release Package [6]

This chapter describes the release package content, hardware and software requirements for using this release, licensing information, and ordering information. Sites using earlier release of COS are encouraged to upgrade to the latest available release.

6.1 Hardware and Software Requirements
The Cray J90, Cray SV1, and Cray T3E binaries were last released with COS 3.6. The Cray Open Software 4.0 release is UNICOS/mp only. Source code is available on the COS software release distribution CD for sites that want to build or modify their installation. These supported Cray systems must be running supported releases of the UNICOS/mp operating system.

6.2 Contents of the Release Package
The release package includes: • Product software as described in Section 6.2.1, Section 6.2.2, page 25, and Section 6.2.3, page 28 • CrayDoc software suite and the documentation, described in Chapter 5, page 11 • Cray Software License, as described in Section 6.3, page 28 6.2.1 Fully Supported Components The COS 4.0 release fully supported components, which means that Cray accepts Software Problem Reports (SPRs) submitted against them, are as follows: 6.2.1.1 bash — GNU Version 3.2 The bash utility is an sh-compatible GNU shell for both interactive and programming use. This utility is supported only on UNICOS/mp systems. The COS bash package includes bash and bashbug.

S–2350–40

15

Cray Open Software Release Overview and Installation Guide

For more information about bash, see: http://www.gnu.org/directory/all/bash.html 6.2.1.2 bc — GNU Version 1.06 The bc utility is a calculator. The COS bc package includes bc and dc. For more information about bc, see: http://www.gnu.org/directory/all/bc.html 6.2.1.3 bison — GNU Version 2.3 The bison utility, which is upwardly compatible with the yacc command, is a general-purpose parser generator that converts a grammar description for a context-free grammar into a C program that parses that grammar. The COS bison package includes bison and yacc. For more information about bison, see: http://www.gnu.org/directory/bison.html 6.2.1.4 coreutils — GNU Version 6.4 The coreutils package is a collection of basic file, shell, and text manipulation utilities many of which are duplicated in the Cray mainframe operating system. The coreutils package combines the sh-utils, textutils, and fileutils packages.

!

Caution: The chroot command is installed by default, it can be removed if you have concerns about it. However, because su does not write properly to the syslog, it has been removed from the package. The COS coreutils package includes basename, cat, chgrp, chmod, chown, chroot, cksum, comm, cp, csplit, cut, date, dd, df, dir, dircolors, dirname, du, echo, env, expand, expr, factor, false, fmt, fold, groups, head, hostid, hostname, id, install, join, kill, link, ln, logname, ls, md5sum, mkdir, mkfifo, mknod, mv, nice, nl, nohup, od, paste, pathchk, pinky, pr, printenv, printf, ptx, pwd, readlink, rm, rmdir, seq, sha1sum, shred, sleep, sort, split, stat, stty, sum, sync, tac, tail, tee, test, touch, tr, true, tsort, tty, uname, unexpand, uniq, unlink, uptime, users, vdir, wc, who, whoami, and yes. The buffer size used for this package has been increased from 2 MB to 8 MB.

16

S–2350–40

Release Package [6]

In COS 3.6, the coreutils package was split out into its own coreutils module. Now there are two modules, open and coreutils. This was done to reduce some of the confusion between the commands in coreutils and the commands released with the Cray mainframe's base operating system. Because of the duplication of commands, you might not want to load coreutils automatically. The coreutils package is installed in /opt/open/XX/coreutils where XX is the release number. To access the utilities included in the COS coreutils module, instead of those versions in the Cray mainframe operating system, load the new coreutils module, for example:
cray# module load coreutils

For more information coreutils, see: http://www.gnu.org/directory/all/coreutils.html 6.2.1.5 CVS — GNU Version 1.11.21 Concurrent Version System (CVS) is a GNU version control system that allows recording the history of source files and documents, similar to the GNU Revision Control System (RCS). The COS CVS package includes cvs, cvsbug, and rcs2log. For more information about CVS, see: http://www.gnu.org/directory/cvs.html 6.2.1.6 diffutils — GNU Version 2.8.1 The diff, diff3, and cmp commands compare files showing line-by-line changes in several flexible formats. The COS diffutils package includes cmp, diff, diff3, and sdiff. For more information about diffutils, see: http://www.gnu.org/directory/diffutils.html

S–2350–40

17

Cray Open Software Release Overview and Installation Guide

6.2.1.7 emacs — GNU Version 21.4 Emacs is a powerful text editor with additional features including content sensitive major modes with complete online documentation. The COS emacs package includes: emacs, ebrowse, ctags, etags, and emacs client. For more information about emacs, see http://www.gnu.org/software/emacs/emacs.html. 6.2.1.8 findutils — GNU Version 4.2.25 The find command searches files that match certain criteria and performs arbitrary operations on them. The COS findutils package includes find, locate, updatedb, and xargs. For more information about findutils, see: http://www.gnu.org/directory/findutils.html 6.2.1.9 flex — GNU Version 2.5.33 The flex utility is a tool for generating programs that perform pattern-matching on text; it is a fast lexical analyzer generator. It features a lex compatibility mode. In conjunction with the bison utility, it can be used to write compilers. The COS flex package includes flex and flex++. For more information flex, see: http://www.gnu.org/software/flex/flex.html 6.2.1.10 fsplit — Version 12.5.00 The fsplit utility breaks Fortran modules into separate files. The COS fsplit package includes only fsplit. For more information about fsplit, see: http://www.psc.edu/~burkardt/src/fsplit/fsplit.c 6.2.1.11 gawk — GNU Version 3.1.5 The gawk utility interprets a special-purpose programming language that makes it possible to handle simple data-reformatting jobs with just a few lines of code.

18

S–2350–40

Release Package [6]

The GNU gawk utility provided allows several actions that are not available in the UNICOS or UNICOS/mk awk utilities. The binary gawk utility is available as an individual package, but it is also built into the automake binary package (Section 6.2.2.1, page 25). The COS gawk package includes awk, gawk, igawk, and pgawk. For more information about gawk, see: http://www.gnu.org/directory/gawk.html 6.2.1.12 GMP — GNU Version 4.1.4 GMP is the GNU Multiple Precision arithmetic library. This package is supported only on UNICOS/mp systems. The COS GMP package includes libgmp.a and libgmp.la. For more information about GMP, see: http://www.swox.com/gmp 6.2.1.13 gnuplot — GNU Version 3.7.3 The gnuplot graph plotting utility is used to plot 2-D and 3-D graphs from a data file or by a formula. Interactive and noninteractive modes are available. The COS gnuplot package includes gnuplot. For more information about gnuplot, see: http://www.gnuplot.info/ 6.2.1.14 grep — GNU Version 2.5.1a The grep utilities finds lines that match entered patterns. The COS grep package includes the GNU grep, egrep, and fgrep utilities. For more information grep, see: http://www.gnu.org/directory/grep.html

S–2350–40

19

Cray Open Software Release Overview and Installation Guide

6.2.1.15 gzip — GNU Version 1.3.3 The gzip (GNU zip) utility is a compression and decompression program replacement for the compress program. This version of gzip contains a patch for the buffer overflow vulnerability bug. The COS gzip package includes gunzip, gzexe, gzip, zcat, zcmp, zdiff, zegrep, zfgrep, zforce, zgrep, zless, zmore, and znew. For more information about gzip, see: http://www.gzip.org 6.2.1.16 less — GNU Version 394 The less utility allows backward movement in the file as well as forward movement. The less program does not have to read the entire input file before starting, so it starts large files faster than text editors like vi. The COS less package includes less, lessecho, and lesskey. For more information about less, see: http://www.gnu.org/directory/less.html 6.2.1.17 make — GNU Version 3.81 The make program automatically determines which pieces of a large program need to be recompiled and issues commands to recompile them. The COS make package includes make and gmake, which is a symbolic link for make. For more information about make, see: http://www.gnu.org/directory/make.html

20

S–2350–40

Release Package [6]

6.2.1.18 netperf — Version 2.4.2 The netperf utility measures the performance of many different types of networking. This package is supported only on UNICOS/mp systems. The COS netperf package includes netperf, netserver, snapshot_script, tcp_range_script, tcp_rr_script tcp_stream_script, udp_rr_script, and udp_stream_script. For more information about netperf, see: http://www.netperf.org 6.2.1.19 OpenSSH — Version 4.5p1 OpenSSH is a secure communications protocol that implements both SSH-1 and SSH-2 protocols. The COS OpenSSH package includes scp, slogin, sftp, ssh, sshd, ssh-add, ssh-agent, ssh-keygen, and ssh-keyscan. Note: The prngd pseudo-random number generator daemon package is included in the COS release for better gathering of random (entropy) data for the OpenSSH daemon (sshd). Therefore, the prngd daemon must be started before the sshd daemon will start. If you want to modify the commands that the prngd daemon uses to gather the random data, modify the /opt/open/40/etc/prngd.conf file and restart the prngd daemon (only). If you do not want to use the prngd daemon, you must rebuild the OpenSSH package. Then, if you want to modify the commands that the sshd daemon (without prngd) uses to gather the random data, modify the /opt/open/40/etc/ssh_prng_cmds.conf and restart the sshd daemon. For more information about prngd, see Section 6.2.1.24, page 22. For more information about OpenSSH, see: http://www.openssh.org 6.2.1.20 OpenSSL — Version 0.9.7l The OpenSSL library contains the cryptography systems that encrypt the communications channel.

S–2350–40

21

Cray Open Software Release Overview and Installation Guide

The Secure Socket Layer (SSL) protocol is an authentication and encryption technique that provides security services to TCP clients. Binary OpenSSL is available only within the OpenSSH binary package. The COS OpenSSL package includes c_rehash, openssl, libcrypto.a, and libssl.a. For more information about OpenSSL, see: http://www.openssl.org 6.2.1.21 patch — GNU Version 2.5.4 The patch tool applies output from the diff command to the original file to generate a modified version of that file. The COS patch package includes only patch. For more information about patch, see: http://www.gnu.org/directory/patch.html 6.2.1.22 pe-version — Version 20040303 The pe-version utility, which was written by Cray, returns information describing the Programming Environment, such as which modules are loaded and which versions are current. If you suspect possible compiler bugs, it is useful to send the output of pe-version to Cray when submitting an SPR. 6.2.1.23 Perl — Version 5.8.8 Perl is a high-level, general-purpose scripting language. The COS Perl package includes a2p, find2perl, perl5.6.1, pl2pm, pod2text, pstruct, c2ph, h2ph, perlbug, pod2html, pod2usage, s2p, cppstdin, h2xs, perlcc, pod2latex, podchecker, splain, dprofpp, perl, perldoc, pod2man, and podselect. For more information about Perl, see: http://www.perl.org 6.2.1.24 prngd — Version 0.9.29 The prngd utility is a psuedo-random number generator daemon for use with the OpenSSH daemon (sshd), described in Section 6.2.1.19, page 21. The prngd daemon must be started up before starting sshd.
22 S–2350–40

Release Package [6]

The COS prngd package includes only prngd. For more information about prngd, see:
http://www.aet.tu-cottbus.de/personen/jaenicke/postfix_tls/prngd.html

6.2.1.25 rsync — GNU Version 2.6.8 rsync is a very fast method for bringing remote files into sync by sending just the differences in the files across the link, without requiring that both sets of files are present at one of the ends of the link beforehand. The COS rsync package includes only rsync. For more information about rsync, see http://samba.anu.edu.au/rsync/. 6.2.1.26 sed — GNU Version 4.1.4 The sed utility is a stream editor. A stream editor is used to perform basic text transformations on an input stream (a file or input from a pipeline). While in some ways similar to an editor that permits scripted edits (such as ed), sed works by making only one pass over the input, so it is more efficient. However, it is the ability to filter text in a pipeline that distinguishes sed from other types of editors. The COS sed package includes only sed. For more information about sed, see: http://www.gnu.org/directory/sed.html 6.2.1.27 sudo — Version 1.6.8p12 The sudo (superuser do) utility is similar to a logged and restricted superuser. This allows a system administrator to maintain a list of which groups or users are allowed to switch to another user to run some (or all) commands as root or another user while logging the commands and arguments. The users who are allowed to run the sudo command should be in a file in /etc/sudoers. An example of the format of this file is available in /opt/open/40/etc/sudoers if you install the binary packages, and it is automatically put into /etc when you install from source.

!

Caution: If you have security concerns, do not install the sudo package. The COS sudo package includes sudo and visudo.

S–2350–40

23

Cray Open Software Release Overview and Installation Guide

For more information about sudo, see: http://www.sudo.ws/sudo/ 6.2.1.28 tar — GNU Version 1.16 The tar utility manages archive files and devices. The GNU tar command allows several options that are not available in the UNICOS tar command, especially the -z option, which allows compression and decompression. The COS tar package includes only tar. For more information about tar, see: http://www.gnu.org/directory/tar.html 6.2.1.29 tcl — Version 8.4.14 The tcl scripting language is a tools command language. The COS tcl package includes tclsh8.4, wish8.4, libtcl8.4.a, libtclstub8.4.a, tclsh, which is a link to tclsh8.4, and wish, which is a link to wish8.4. The tk and expect binaries are also included in the tcl binary package. For more information tcl, see: http://www.tcl.tk 6.2.1.30 tk — Version 8.4.14 The tk tool kit is used to create a graphical user interface. The COS tk package includes libtk8.4.a and libtkstub8.4.a. The binary tk package is available only in the tcl binary package. For more information about tk, see: http://www.tcl.tk 6.2.1.31 top — Version 3.5 The top utility provides a rolling display of top CPU-using processes. This utility is supported only on UNICOS/mp systems. The COS top package includes only top.
24 S–2350–40

Release Package [6]

For more information about top, see: http://www.groupsys.com/top/ 6.2.1.32 zlib — Version 1.2.3 The zlib library contains compression and decompression routines. The binary zlib library is available only with the OpenSSH binary package. The COS zlib package includes only libz.a. For more information about zlib, see: http://www.zlib.org 6.2.2 Lightly Supported Components As a service to our customers, in addition to providing packages that have been well tested and are fully supported in the traditional SPR manner, Cray provides additional packages that may be useful but are only lightly supported. This means that the product passes most of its own self-tests (if it has any) and works well as it is used by Cray. However, it has not been exhaustively tested by Cray. Cray accepts SPRs for the component but may handle them with a lower priority than SPRs for fully supported components. The lightly supported components of the COS 4.0 release are as follows: 6.2.2.1 autoconf — GNU Version 2.60 The autoconf utility produces shell scripts that automatically configure source code packages. The COS autoconf package includes autoconf, autoheader, autom4te, autoreconf, autoscan, autoupdate, and ifnames. The binary autoconf utility is included in the automake binary package. For more information about autoconf, see: http://www.gnu.org/directory/autoconf.html

S–2350–40

25

Cray Open Software Release Overview and Installation Guide

6.2.2.2 automake — GNU Version 1.10 The automake utilities are Perl scripts that generate make files (Makefile.in) that are compliant with the GNU coding standards. automake requires the autoconf and perl packages. The COS automake package includes aclocal and automake. The binary gawk and binary m4 utilities are available as individual packages, but they are also built into the automake binary package. The binary autoconf utility is available only within the automake binary package. For more information about automake, see: http://www.gnu.org/directory/automake.html 6.2.2.3 expect — Version 5.43 The expect tool is used for automating interactive applications. The expect binary is included in the tcl binary package in COS. The COS expect package includes autoexpect, expect, and expectk. For more information about expect, see: http://expect.nist.gov/ 6.2.2.4 groff — GNU version 1.19 The groff package contains typesetting utilities which read plain text and formatting instructions, producing formatted output. The COS groff package includes groff, grog, grops, grotty, mmroff, nroff, tbl and troff. For more information about groff, see: http://www.gnu.org/software/groff/groff.html 6.2.2.5 m4 — GNU Version 1.4.4 The m4 utility is an implementation of the traditional UNIX macro processor. The binary m4 utility is available as an individual package, but it is also built into the automake binary package. The COS m4 package includes m4, libm4.a, and libm4.la.

26

S–2350–40

Release Package [6]

For more information about m4, see: http://www.gnu.org/directory/GNU/gnum4.html 6.2.2.6 Python — Version 2.3.3 Python is an interpreted, interactive object-oriented programming language. This package is supported only on UNICOS/mp systems. Note: Only the NumPy array extension is ported at this time. The COS Python package includes only Python. For more information about Python, see: http://www.python.org 6.2.2.7 ruby — Version 1.8.5 ruby is a simple and powerful object-oriented programming language. This package is supported only on UNICOS/mp systems. The COS ruby package includes ruby, libruby-static.a, erb, irb, rdoc, ri, and testrb. For more information about ruby, see: http://www.ruby-lang.org 6.2.2.8 TeXinfo — GNU Version 4.8 The TeXinfo set of utilities can be used to generate printed manuals, plain ASCII text, and online hypertext documentation (called info). They can also be used to read online info documents. The COS TeXinfo package includes info, install-info, texi2dvi, infokey, makeinfo, and texindex. For more information about TeXinfo, see: http://www.gnu.org/directory/texinfo.html 6.2.2.9 vim — Version 7.0 The vim utility is an improved version of the vi editor. It includes unlimited undo, split windows, visual selection, graphical user interface (such as menus, mouse control, scroll bars, text selection), and much more.
S–2350–40 27

Cray Open Software Release Overview and Installation Guide

The COS vim package includes ex, rvim, vim, vimtutor, rview, view, vimdiff, and xxd. For more information about vim, see: http://www.vim.org 6.2.3 Unsupported Components Unsupported components are included in the COS 4.0 release, may even contain enhancements, but are not supported by Cray. 6.2.3.1 gdb — GNU Version 50-1.10 The gdb command and gdb(1) man page for the gdb GNU version 50-1.10 debugger utility have been modified and are included in the COS package. Although the gdb package has some Cray enhancements, it is not supported by Cray. The source code and binary for this utility are provided for UNICOS/mp systems only. For more information about the basic GNU gdb version, see: http://www.gnu.org/software/gdb/gdb.html

6.3 Licensing
COS 4.0 release package is distributed to customers by order only. The customer need not add this product to the terms and conditions of their standard license agreement signed with Cray. Upgrades to this product are provided only when a software support agreement for this Cray software is in place. Customers outside the United States and Canada must sign a Letter of Assurance before software can be shipped to them. For questions about whether you have signed this agreement, or questions about which software requires this letter, send e-mail to crayinfo@cray.com.

28

S–2350–40

Release Package [6]

6.4 Ordering Software
This release package is distributed by order only to customers who have signed a license agreement for the Cray software that includes this product. The most current revision of the release package is supplied. To receive any upgrades to a given Cray product, the customer must also have a signed support agreement for this Cray software. You can order the release package from the Cray Software Distribution Center in any of the following ways: E-mail: orderdsk@cray.com CRInform (for subscribers): crinform.cray.com Click on the Order Cray Software link. Telephone (inside U.S., Canada): 1–800–284–2729 (BUG CRAY), then 605–9100 Telephone (outside U.S., Canada): +1–651–605–9100 Fax: +1–651–605–9001 Mail: Software Distribution Center Cray Inc. 1340 Mendota Heights Road Mendota Heights, MN 55120–1128 USA Software will be shipped by ground service or 5-day international service.

S–2350–40

29

Cray Open Software Release Overview and Installation Guide

30

S–2350–40

Customer Services [7]

This chapter describes the customer services that support this release.

7.1 Technical Assistance with Software Problems
If you experience problems with Cray software, contact your Cray service representative. Your service representative will work with you to resolve the problem. If you choose to have full- or part-time support on site, your on-site personnel are your primary contacts for service. If you have elected not to have on-site support, please call or send e-mail to the Cray Customer Support Center: E-mail: support@cray.com Telephone (inside U.S., Canada): 1–800–950–2729 (CRAY) Telephone (outside U.S., Canada): +1–715–726–4993 CRInform (for subscribers): crinform.cray.com You can also create a Request for Technical Assistance (RTA) and track and search RTAs and Software Problem Reports (SPRs) online if you are a CRInform subscriber, as described in Section 7.2.

7.2 CRInform System
The CRInform system is the information and problem-reporting system for Cray customers who are CRInform subscribers. You are a CRInform subscriber if your site has a software license agreement and software support agreement. Access CRInform at: crinform.cray.com Ask your system administrator for your password. Some of the things a subscriber to CRInform can do include: • Report software problems (SPRs)
S–2350–40 31

Cray Open Software Release Overview and Installation Guide

• Request technical assistance (RTAs) • Communicate with other Cray system users • Read about software problems reported at other sites • Learn about solutions to various problems • Order Cray software • View Cray Service Bulletin The CRInform program automatically logs events pertinent to your Cray system site as news items, so you do not have to search through the system for new information. The logged events include Software Problem Report (SPR) or Request for Technical Assistance (RTA) activity, new orderable software, new issues of the Cray Service Bulletin, new field notices (FNs), new software release documents, new software problem fix information, new marketing information, and new CRInform program information. You can also get automatic e-mail notification of any or all of the news items.

7.3 Training
To find out more about Cray training, contact your Cray representative or contact us in any of the following ways: E-mail: wwwtng@cray.com Web: www.cray.com/training/ Fax: +1–715–726–4991 Mail: Technical Training Cray Inc. P.O. Box 6000 Chippewa Falls, WI 54729–0080 USA

32

S–2350–40

Customer Services [7]

7.4 Cray Service Bulletin (CRSB)
The CRInform site provides access to the online Cray Service Bulletin, also called CRSB, which contains descriptions of software problems, information about service procedures or agreements, and announcements of product upgrades and future products for the private use of Cray customers.

7.5 Cray Public Website
The Cray public website offers information about a variety of topics and is located at: www.cray.com

S–2350–40

33

Cray Open Software Release Overview and Installation Guide

34

S–2350–40

Installation of Cray Open Software [8]

This chapter provides instructions for installing the Cray Open Software (COS 4.0) release software on UNICOS/mp systems. Note: If you are upgrading from a version of COS that is older than COS 3.0, remove the older version and install COS 3.6 as an initial installation. Cray Open Software contains precompiled binaries and source packages. The Common Installation Tool (CIT) is used to install the precompiled system-specific binary packages. However, you may choose to install manually by loading the desired packages onto the Cray, then running install.manually on the Cray itself or you may choose to load the one generic source package and run commands to compile and install the binary for each individual package. Installation using CIT or directly from the command line requires you to be the root (superuser) user on the supported Cray system.

8.1 Preinstallation Setup on the Cray Mainframe
Ensure that there is enough disk space to install the release (see Section 8.2.1, page 35, step 2 for installation of the precompiled binaries using CIT and Section 8.3.1, page 38, step 2 for installation using source).

8.2 Installing the Precompiled Binaries
This section describes the preparation and installation of the precompiled binaries in Cray Open Software using CIT or manual installation. The methods are recommended over the source installation that is described in Section 8.3, page 37. 8.2.1 Preparation for Installation of Precompiled Binaries 1. Get superuser, security, and network privileges. The /opt/open/40 disk space requirements for full binary installation are 840 1K blocks on Cray X1 systems.

S–2350–40

35

Cray Open Software Release Overview and Installation Guide

8.2.2 Installation Using CIT 1. Insert the Cray Open Software CD-ROM into the system's workstation. It might be necessary to mount the CD manually if the automounter is disabled. You can do this by entering the following command at the system's workstation (an SWS is used in this example):
sws# mount -t hsfs -r /dev/sr0 /cdrom_path

where cdrom_path is the path to the CD-ROM. 2. Log in to the system workstation (SWS) as crayadm. 3. Verify that the workstation account's .rhosts file is set up to allow a login from root on the Cray mainframe system to the workstation without a password, for example:
CrayHostName root

Note: For more information about setting up the communication paths between the workstation and the Cray system, see the Common Installation Tool (CIT) Reference Card, which can be printed from the /cdrom_path/CYRIinstall/2218.ps PostScript file. You may also select the Help button from the graphical user interface (GUI), or at the interactive prompt, enter:
cit> help all

4. Execute the following commands to start Cray Open Software installation:
workstation# cd /cdrom_path workstation# ./setup -c CrayHostName -l root

a. b. c.

Select the appropriate CrayOpenSoftware product for your specific system hardware architecture. Select the desired packages and start the installation. CIT installs the software in /opt/open/40. Quit CIT when the Cray Open Software is loaded.

5. Unmount and eject the CD by entering:
workstation# cd / workstation# umount /cdrom_path workstation# eject cd

36

S–2350–40

Installation of Cray Open Software [8]

6. Remove the entries made to the .rhosts and /.rhosts files for the workstation account on the Cray mainframe system. 7. Proceed to Section 8.4, page 40. 8.2.3 Non-CIT Installation A new script has been provided allowing installation without using CIT. 1. Insert the Cray Open Software CD-ROM into the system's workstation. It might be necessary to mount the CD manually if the automounter is disabled. This can be done by entering:
workstation# mount -t hsfs -r /dev/sr0 /cdrom_path

where cdrom_path is the path to the CD-ROM. 2. Log in to the system workstation (SWS) as crayadm. 3. Transfer the appropriate files to /tmp/.crayopen in the Cray system:
scp /CDROM/cray-x1/* CrayHostName:/tmp/.crayopen

Note: You may choose any or all of the package bin.bgz files, but you MUST include install.manually and the module files or the installation will fail. 4. Unmount and eject the CD by entering:
workstation# cd / workstation# umount /cdrom_path workstation# eject cd

5. Log in to the Cray system as the root user. 6. Change to /tmp/.crayopen and install COS manually:
cray# ./install.manually

8.3 Source Installation
This section describes the installation of Cray Open Software source.

S–2350–40

37

Cray Open Software Release Overview and Installation Guide

8.3.1 Preparation for Source Installation 1. Get superuser, security, and network privileges. Quite often, the root user umask is set such that no other access is permitted. This causes problems for users trying to use the Cray Open Software code, so set the umask to 022 during this installation process. 2. Allocate disk space for the installation and build of Cray Open Software. Manually installing and building the complete COS package uses 1500 1K blocks of disk space on UNICOS/mp systems. Individually building, installing, and cleaning each package (before going on to the next package) uses 200 1K blocks of disk space on UNICOS/mp systems. The largest package is 175 1K blocks for coreutils on UNICOS/mp systems. 8.3.2 Source Installation Procedures The installation process for all packages follows a similar basic routine of gzip, cpio, make, make test or make check, make install, and make clean. However, not all packages have a make test or make check, or they have them but the tests do not run properly, so they are skipped. Note: When installing COS on a Cray X1 system, the following environment variable must be set prior to running configure on any package. This requirement is not necessary when you use the install scripts provided with the COS package.
setenv CRI_cc_OPTIONS -hcommand

1. Insert the Cray Open Software CD-ROM into the system's workstation. It might be necessary to mount the CD manually if the automounter is disabled. This can be done by entering:
workstation# mount -t hsfs -r /dev/sr0 /cdrom_path

where cdrom_path is the path to the CD-ROM. 2. Log in to the system as crayadm or cri.

38

S–2350–40

Installation of Cray Open Software [8]

3. Transfer the appropriate file path from the following list according to your specific Cray system hardware architecture to /tmp/.crayopen in the Cray system: Cray X1 systems /CDROM/cray-x1/source.bgz 4. Log in to the Cray system as the root user. 5. Change to the directory containing the source code, then unpack the source file by entering:
cray# gzip -dc source.bgz | /bin/cpio -Bimdcu cray# cd 40/src

6. The following packages have dependencies, otherwise, you can install the software packages in any order: • OpenSSL, prngd, Perl, and zlib packages must be installed prior to installing the OpenSSH package. • The gawk and m4 packages must be installed prior to installing the autoconf package. • The autoconf and Perl packages must be installed prior to installing the automake package. • The autoconf, diffutils, findutils, m4, make, and tar utilities use the info command from the TeXinfo package to read the info pages but do not require that TeXinfo be installed before installing their packages. For each individual package in the Cray Open Software product, the Cray Open Software CD-ROM contains a script named install.packagename, so that you can individually install each package. These scripts contain the configuration used to create the Cray Open Software product package. Enter this command for each package that you want to individually install:
$ install.packagename

where packagename is the name of the individual package in the Cray Open Software product package. For example, the install.autoconf command installs the autoconf package.

S–2350–40

39

Cray Open Software Release Overview and Installation Guide

8.3.3 Installing Module Files To install Cray Open Software module files, enter:
cray# cp module.open 40 /opt/modulefiles/open40 cray# cp module.coreutils40 /opt/modulefiles/coreutils40

The module files install themselves when using either CIT or install.manually. 8.3.4 Making 40 the Default open Package Make 40 the default open package as follows. To use the script, enter:
cray# ./install.makedefault

You can also remove existing /opt/open symbolic links and replace them with the /opt/open/40 symbolic link using individual commands by entering:
cray# cd /opt/open cray# ln -s 40 open

8.4 Loading Modules and Accessing Packages After Installation
After Cray Open Software is installed, to access the COS packages, load the open module by entering:
cray# module load open

You can also load the coreutils module by entering:
cray# module load coreutils

Note: The prngd pseudo-random number generator daemon package is included in the COS release for better gathering of random (entropy) data for the OpenSSH daemon (sshd). Therefore, the prngd daemon must be started before the sshd daemon will start. If you want to modify the commands that the prngd daemon uses to gather the random data, modify the /opt/open/40/etc/prngd.conf file and restart the prngd daemon (only).

40

S–2350–40

Installation of Cray Open Software [8]

Note: OpenSSH sets PrivilegeSeparation to yes. This requires that an sshd user be created. This user should be a non-login user, with any UID, any home directory, and any groups, but it should have as little privilege as possible. Most sites set the home directory as /opt/open/open/var/empty. Using Compression with PrivilegeSeparation is now allowed. It is recommended that Compression be set to "Delayed" in sshd_config. Note: The default port used for all the secure shell protocols is port 22. Other ports may be used by using the -p option for sshd and ssh or by modifying the sshd_config file. You can run multiple OpenSSH daemons as long as each uses a different port. 8.4.1 Instructions for UNICOS/mp Systems Only Perform the following items to complete access to the COS packages on UNICOS/mp systems only. 8.4.1.1 Verification of Security Files and Related Daemons Ensure that the /etc/init.d/prngd, /etc/inet.d/sshd, /etc/rc2.d/S80prngd, and /etc/rc2.d/S80sshd files are all in place and that the prngd daemon will start before the OpenSSH daemon (sshd) starts during a system reboot. Several OpenSSH and prngd configuration files may be modified anytime OpenSSH or prngd issues a new release. The configuration files are in /opt/open/40/etc and consist of prngd.conf, ssh_config, sshd_config, and the recommended startup files are prngd.rc and sshd.rc. The install process compares the new files to the current /opt/open/open/etc files, and if there's a change, the new files are installed with a ".new" suffix. After installation and prior to restarting sshd, the old files should be compared to the .new files and modifications made. Note: The COS 4.0 version of sshd will not run over IPv6. Sites running IPv6 MUST start sshd with the -4 option. Sites not running IPv6 may start sshd with the -4 option with no ill effects. An updated /etc/init.d/sshd start up file has been provided in /opt/open/40/etc/sshd.rc.new and it's recommended that all sites use it.

S–2350–40

41

Cray Open Software Release Overview and Installation Guide

8.4.1.2 Changes for Relative and Absolute Path Names The sample cshrc file shipped with the Cray X1 systems uses relative, not absolute pathnames. You need to edit the /skl/etc/stdcshrc file and change hostname to /bin/hostname. Also, change any .cshrc files or /etc/cshrc files that you based on this sample. With relative pathnames, there is a danger that the wrong program will be run. This is especially dangerous for root. The current stdcshrc file uses hostname -s to set the prompt. If root has the Cray Open Software module loaded and then runs this .cshrc, it is possible that the machine name will be changed to -s. This is due to the hostname command in the Cray Open Software package not recognizing the -s option. 8.4.1.3 Using Cray Open Software in an Cray X1 Compile Environment The Cray Open Software release package is released asynchronously to both the Cray Programming Environment Server (CPES) software release and the Cray Programming Environment releases. If you choose to incorporate Cray Open Software into the software you are compiling for your Cray X1 system, refer to the instructions in the Cray Programming Environment Server Software Installation and Administration manual, Section 6.1.4 CPES Configuration Files.

42

S–2350–40

Index

A Accessing Cray documentation, autoconf, 25 automake, 26 B bash, 15 bc, 16 bison, 16 Books accessing,

11

11

C CIT documentation, 12 Common Installation Tool (CIT), 35 Compatibilities, 7 Compiling Cray Open Software, 42 Compression, 9, 41 Contact information Customer Support Center, 31 Software Distribution Center, 13 Training, 32 coreutils, 16 COS See Cray Open Software Cray Open Software, 1 compiling, 42 component packages, 3 installation, 35 release contents, 1 release overview, 1 release package, 15 upgrades, 35 Cray Open Software component packages autoconf, 25 automake, 26 bash, 15
S–2350–40

bc, 16 bison, 16 coreutils, 3, 16 CVS, 17 diffutils, 17 expect, 26 findutils, 18 flex, 18 fsplit, 3, 18 fully supported, 15 gawk, 18 GMP, 3, 19 gnuplot, 19 grep, 19 groff, 26 gzip, 20 less, 20 lightly supported, 25 m4, 26 make, 20 netperf, 3, 21 new fully supported, 3 OpenSSH, 21 OpenSSL, 21 patch, 22 pe-version, 22 Perl, 22 prngd, 22 Python, 27 ruby, 27 sed, 23 sudo, 23 tar, 24 tcl, 24 TeXinfo, 27 tk, 24 top, 24 unsupported, 28

43

Cray Open Software Release Overview and Installation Guide

updated, 3 vim, 27 zlib, 25 Cray Service Bulletin, 32–33 Cray websites, 33 CRInform, 31 publications, 11 support, 31 training, 32 CRInform, 31 CRSB, 33 cshrc file, 42 Customer services, 31 Customer Support Center, 31 Customs, 28 CVS, 17 D debugger, 28 Differences, 7 diffutils, 17 Disk space source installation, 38 Distribution Center, 13, 29 Documentation, 11–12 accessing, 11 E /etc/inet.d/sshd, 41 /etc/init.d/prngd, 41 /etc/rc2.d/580sshd, 41 /etc/rc2.d/S80prngd, 41 expect, 26 Export license, 28 F Field notices (FNs), 5, 32 findutils, 18 flex, 18 fsplit, 18 Fully supported components, 15

G gawk, 18 gdb, 28 gdb command, 28 GMP, 19 gnuplot, 19 grep, 19 groff, 26 gzip, 20 H Hard copy, 12 HTML, 12 I Installation, 35 instructions, 35 mainframe setup, 35 post installation instructions all systems, 40 UNICOS/mp systems, 41 source procedures, 37–38 using CIT, 35–36 L less, 20 Letter of assurance, 28 Lightly supported components, Limitations product, 9 M m4, 26 make, 20 Man pages accessing, 11 Manuals, 12 N netperf, 21

25

44

S–2350–40

Index

O OpenSSH running multiple daemons, 41 version and description, 21 OpenSSL, 21 Ordering documentation, 13 software, 29 Overview, 1 P patch, 22 PDF, 12 pe-version, 22 Perl, 22 PrivilegeSeparation, 9, 41 prngd, 22 Problems, 31 OpenSSH, 9 Publications, 11–12 accessing, 11 Python, 27 R Release package, 15 Request for Technical Assistance (RTA), 31–32 Requirements, 15 .rhosts, 36–37 ruby, 27 S Secure shell protocols

default port, 41 Secure Socket Layer (SSL), description, 22 sed, 23 Shipping, 29 Software Problem Report (SPR), 31–32 Software Problem Reports (SPRs) addressed, 5 Subscriber, CRInform, 31 sudo, 23 Support agreement, 28–29, 31 Support Center, 31 T tar, 24 tcl, 24 Technical support, 31 TeXinfo, 27 tk, 24 top, 24 Training, 32 U Unsupported components, 28 Upgrades, 28 installation, 35 V vim, 27 Z zlib,

25

S–2350–40

45

Sign up to vote on this title
UsefulNot useful