The department has an Silicon Graphics software server on a.chem to facilitate SGI software installation for the Chemistry Department.  Group system administrators can have round-the-clock access to nearly all SGI software CD's.  Installing over the network eliminates the need to change CD's which can be time-consuming to monitor.  It is sometimes faster to install over the network as opposed to a CD in a local CD-ROM drive.

    This server is restricted to the Chemistry department only for those who have paid for current varsity software support.  If you're in Chemistry, but are not current with it, you need to renew or sign up new for it with ISC's SGI renewal form.   The server is an organized directory tree on a.chem.upenn.edu comprised of copies of the CD-ROM's for the software covered, or where the software was not on CD, the de-tarred files.

Software available:

• IRIX 6.5 and the unsupported versions of IRIX: 5.3, 6.2, 6.3, and 6.4.
• IRIX 6.5 maintenance and feature stream updates.
• Recommended patches and security patches for IRIX 5.3, 6.2, 6.3, and 6.4.
• SGI Varsity Developer package CD's
• Gaussian 94 source and compiled version for 6.5
• Maple Vr4 UNIX CD

1. To check that you are allowed access into the server, change to root: "su - " or login as root. Then type "rlogin varsity@a.chem.upenn.edu".  It should let you in to the varsity account. If it says refused or some other kind of message, write help@chem.upenn.edu.  You won't be able to use it until you can do this step.
2. Check /etc/motd on a.chem to make sure a.chem will be up during the time you will be installing the software.  Be conservative in estimating how much time you'll need.
3. Make sure you have a recent backup.  While this probably isn't necessary for installing Maple, it's foolhardy not to have one for OS upgrades.
4. As root, start inst or Software Manager.
5. Determine the location of the software.  Enter "softserv" on a.chem to get the string.  You can alternatively develop it yourself from the directory tree listing below.
6. Proceed as you would to install the software as if you were using a local CD-ROM drive.  When it asks for the software distribution path, enter the string you've obtained.

1. Produce the string that will identify the software distribution you want: Start with:"varsity@a.chem:/" or, "guest@a.chem:/" if you are going to use any of the /os directories.
2. Append the subtree where the distribution resides. You need to start by selecting the type of software in the leftmost column, add a slash, and then continue by picking the name from the next column, appending a slash, and so on, until you can't go any further. I regret I don't have a description of what each piece offers right now.

os
        5.3
        6.2
                       part2
        6.3
        6.4
        6.5
                    found1
                    found2
                    6.5.5

patches    *
        5.3
                    indigo
                                                11-99
        6.2
                    crimson
                                                11-99
                    indy
                                                11-99
                    pchallenge
                                                11-99
        6.3
                     11-99
        6.4
                    origin
                                                11-99
                    octane
                                                11-99

        mipspro
                    7.2.1
                                                all
                                                                6-99
                    7.3
                                (not installed)

        secure (security patches organized by OS, includes all security patches, not broken up by month, last updated 1/99)
                    5.3
                    6.2
                    6.3
                    6.4
                    6.5    (none produced)
        other
                    (other patches by number)

varsity
        5.3
                    dpu
                    openinv2.1.1
                    performer2.0
                    webforce9-96
                    f77-4.0.2
                    pdw2.5.1
                    vdp5-95
        6.2
                    app8-96
                    auxapp8-97
                    devfound1.2
                     ido7.1
                    devlib
        6.3
                    app8-97
                    devfound1.2
                    devlib
                    ido7.1
        6.4
                    app2-97
                    devfound1.2
                    devlib
                    ido7.1.1
        6.5
                    app8-99
                    devfound
                    dvptlib
                    ivldo3.2.1

        all (usually for 6.2 and above)
                    cosmo8-98
                    freeware8-99
                    inventor2.1.5
                    mineset2.6
                    onc3nfs
                    performer2.2
                    scsl1.2
                    vau12-98
                    vup8-98
                    webforce11-98

       compilers
                    cee7.3
                    allcomp5-99
        other
                    (other varsity software)

You then need to add "/dist"at the end of the string for most distributions; exceptions would be for some security patch distribution directories and 5.3 varsity.  Enter this string in when it asks you for the software distribution to install from. You can change the default installation if needed. If there are no conflicts, you can start the installation. Once it is finished you may need to restart your system for the changes to take effect.

Booting miniroot:
    The machine you are booting from must be in Chemistry subnet for os booting to miniroot from PROM. This is because the machine can't communicate with hosts outside the subnet from the PROM. If the machine has an IP whose third field is a 64, 65, 66, or 67, it is in the Chemistry subnet. 112's are in IAST.  There is presently no NFS server to bridge this for IST, contact help@chem.upenn.edu if you'd still like to use this.
 

1. To boot to miniroot from this server, shut down to PROM ("/etc/shutdown -y -g0 -i0")
2. Ensure the PROM has the correct IP address for your system.  Select "Command Monitor" option at the PROM menu.

1. "setenv netaddr <your system's IP address>
2. Enter "quit" to return to the PROM menu.
3. Enter "2" install system software.
4. Select "remove install"
5. Enter hostname and then directory of remote install location:a.chem.upenn.edu and then /aux1/os/<version of IRIX>/dist", for IRIX 6.5, enter "/aux1/os/6.5/6.5.5/overlays1/dist".
6. It may prompt you for a.chem's IP address, enter "130.91.64.31" for the net address of a.chem. If it asks for the subnet mask, enter "0xfffffc00"
7. It should now boot normally to miniroot.

Upgrading to IRIX 6.5:
    You may experience trouble using this to upgrade to 6.5.  For one, the sash on your pre-IRIX 6.5 version may not be able to boot the 6.5 miniroot over the network.  In this case, you'd need to obtain the IRIX 6.5 CD's from the Computer Facility.  Email help@chem.upenn.edu.  Also, in some cases, the system's current OS loader(sash) may not be able to handle a long pathname like that above.  This is a bug with IRIX that I believe has not been fixed.  I've only noticed it on a few systems, particularly R8000's.   Otherwise, upgrading to IRIX 6.5 should go fine.
 

Important:

•  The speed of the install depends on the network traffic, a.chem load, and your own SGI.
•  Be warned about PROM code upgrades using the server. There shouldn't be any problem doing these. You should be aware that there is a rare chance that your network connection could be unexpectedly severed during a PROM upgrade the connection to the server is severed, your system may need to be replaced. If this isn't on hardware support this could cost a lot! PROM upgrades come with IRIX 6.5 updates and the recommended patch sets. I've only seen them for Origin systems, although other SGI's may be able to upgrade their PROM code this way.

last updated 2/28/00 by Martin McCormick, martinm@sas.upenn.edu