Professional Documents
Culture Documents
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 v
Accessing Product Documentation . . . . . . . . . . . . . . . . . . . v
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . vi
Reader Comments . . . . . . . . . . . . . . . . . . . . . . . . vii
Cray User Group . . . . . . . . . . . . . . . . . . . . . . . . vii
Introduction [1] 1
Emphasis for the COS 4.0 Release . . . . . . . . . . . . . . . . . . . 1
Limitations [4] 9
Problems with All OpenSSH Versions . . . . . . . . . . . . . . . . . . 9
Limitations for COS Components . . . . . . . . . . . . . . . . . . . 9
Documentation [5] 11
CrayDoc Documentation Delivery System . . . . . . . . . . . . . . . . . 11
Accessing Product Documentation . . . . . . . . . . . . . . . . . . . 11
S–2350–40 i
Cray Open Software Release Overview and Installation Guide
Page
ii S–2350–40
Contents
Page
S–2350–40 iii
Cray Open Software Release Overview and Installation Guide
Page
Index 43
Tables
Table 1. Manuals Provided with This Release . . . . . . . . . . . . . . . 12
iv S–2350–40
Preface
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 Meaning
command This fixed-space font denotes literal items, such as file
names, pathnames, man page names, command names, and
programming language elements.
variable 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.
user input 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.
name(N) 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
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
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.
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).
S–2350–40 3
Cray Open Software Release Overview and Installation Guide
4 S–2350–40
Software Enhancements [2]
S–2350–40 5
Cray Open Software Release Overview and Installation Guide
6 S–2350–40
Compatibilities and Differences [3]
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]
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).
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.
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.
S–2350–40 15
Cray Open Software Release Overview and Installation Guide
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
S–2350–40 17
Cray Open Software Release Overview and Installation Guide
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
S–2350–40 19
Cray Open Software Release Overview and Installation Guide
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]
S–2350–40 21
Cray Open Software Release Overview and Installation Guide
22 S–2350–40
Release Package [6]
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
24 S–2350–40
Release Package [6]
S–2350–40 25
Cray Open Software Release Overview and Installation Guide
http://expect.nist.gov/
26 S–2350–40
Release Package [6]
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.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]
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.
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.
S–2350–40 31
Cray Open Software Release Overview and Installation Guide
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]
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.
S–2350–40 35
Cray Open Software Release Overview and Installation Guide
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.
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.
S–2350–40 37
Cray Open Software Release Overview and Installation Guide
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
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
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
40 S–2350–40
Installation of Cray Open Software [8]
S–2350–40 41
Cray Open Software Release Overview and Installation Guide
42 S–2350–40
Index
A bc, 16
Accessing Cray documentation, 11 bison, 16
autoconf, 25 coreutils, 3, 16
automake, 26 CVS, 17
diffutils, 17
B expect, 26
bash, 15 findutils, 18
bc, 16 flex, 18
bison, 16 fsplit, 3, 18
Books fully supported, 15
accessing, 11 gawk, 18
GMP, 3, 19
C gnuplot, 19
grep, 19
CIT
groff, 26
documentation, 12
gzip, 20
Common Installation Tool (CIT), 35
less, 20
Compatibilities, 7
lightly supported, 25
Compiling Cray Open Software, 42
m4, 26
Compression, 9, 41
make, 20
Contact information
netperf, 3, 21
Customer Support Center, 31
new fully supported, 3
Software Distribution Center, 13
OpenSSH, 21
Training, 32
OpenSSL, 21
coreutils, 16
patch, 22
COS
pe-version, 22
See Cray Open Software
Perl, 22
Cray Open Software, 1
prngd, 22
compiling, 42
Python, 27
component packages, 3
ruby, 27
installation, 35
sed, 23
release contents, 1
sudo, 23
release overview, 1
tar, 24
release package, 15
tcl, 24
upgrades, 35
TeXinfo, 27
Cray Open Software component packages
tk, 24
autoconf, 25
top, 24
automake, 26
unsupported, 28
bash, 15
S–2350–40 43
Cray Open Software Release Overview and Installation Guide
updated, 3 G
vim, 27 gawk, 18
zlib, 25 gdb, 28
Cray Service Bulletin, 32–33 gdb command, 28
Cray websites, 33 GMP, 19
CRInform, 31 gnuplot, 19
publications, 11 grep, 19
support, 31 groff, 26
training, 32 gzip, 20
CRInform, 31
CRSB, 33 H
cshrc file, 42 Hard copy, 12
Customer services, 31 HTML, 12
Customer Support Center, 31
Customs, 28 I
CVS, 17
Installation, 35
instructions, 35
D
mainframe setup, 35
debugger, 28 post installation instructions
Differences, 7 all systems, 40
diffutils, 17 UNICOS/mp systems, 41
Disk space source procedures, 37–38
source installation, 38 using CIT, 35–36
Distribution Center, 13, 29
Documentation, 11–12 L
accessing, 11
less, 20
Letter of assurance, 28
E
Lightly supported components, 25
/etc/inet.d/sshd, 41 Limitations
/etc/init.d/prngd, 41 product, 9
/etc/rc2.d/580sshd, 41
/etc/rc2.d/S80prngd, 41 M
expect, 26
m4, 26
Export license, 28
make, 20
Man pages
F
accessing, 11
Field notices (FNs), 5, 32 Manuals, 12
findutils, 18
flex, 18 N
fsplit, 18
netperf, 21
Fully supported components, 15
44 S–2350–40
Index
O default port, 41
OpenSSH Secure Socket Layer (SSL), description, 22
running multiple daemons, 41 sed, 23
version and description, 21 Shipping, 29
OpenSSL, 21 Software Problem Report (SPR), 31–32
Ordering Software Problem Reports (SPRs)
documentation, 13 addressed, 5
software, 29 Subscriber, CRInform, 31
Overview, 1 sudo, 23
Support agreement, 28–29, 31
P Support Center, 31
patch, 22
PDF, 12 T
pe-version, 22 tar, 24
Perl, 22 tcl, 24
PrivilegeSeparation, 9, 41 Technical support, 31
prngd, 22 TeXinfo, 27
Problems, 31 tk, 24
OpenSSH, 9 top, 24
Publications, 11–12 Training, 32
accessing, 11
Python, 27 U
Unsupported components, 28
R Upgrades, 28
Release package, 15 installation, 35
Request for Technical Assistance (RTA), 31–32
Requirements, 15 V
.rhosts, 36–37 vim, 27
ruby, 27
Z
S zlib, 25
Secure shell protocols
S–2350–40 45