Upgrading to the latest release of IRIX
 This procedure will most likely change soon, as we get the Chemistry AFS cell configured. All of these instructions will be done with a terminal for now, as I haven't yet had time to take screenshots. The instructions now include installing OpenSSH, but do not enable it by default to avoid conflict with other SSH servers you may have installed. See Enabling OpenSSH in IRIX for instructions on enabling it.
Getting the latest IRIXWe've currently got IRIX 6.5.23 and 6.5.22 loaded up on a workstation here. 6.5.22 was the last version available for SGI Indigo^2, Indy, and Challenge machines, while 6.5.23 is preferred otherwise. We're going to go ahead and attach the shared drive temporarily so we can install off of it. Perform the following as root:
# mkdir /mnt
# mount strongmad.chem.indiana.edu:/data/export /mnt
Installing IRIX Overlays
Start the installerYou can do this from the GUI Software Manager, but again, we'll do it the command line way for now. When you run inst, it will look like this:
# inst
Default distribution to install from: /tmp/pkgs
For help on inst commands, type "help overview".
Inst 4.1 Main Menu
1. from [source ...] Specify location of software to be installed
2. open [source ...] Specify additional software locations
...
Patching your install toolsSomewhere down the line in 6.5.x, they updated the installation tools. If you are running anything less than 6.5.21 currently, you will need to do this step. We'll tell inst to load from the patch directory we've created. The three commands we will use is "from /mnt/IRIX/inst", "go", and "quit"
Inst> from /mnt/IRIX/inst
Reading product descriptions .. 100% Done.
Inst> go
Reading fileset information .. 8%
Pre-installation check .. 16%
Checking space requirements .. 24%
Installing/removing files .. 24%
..
Installations and removals were successful.
You may continue with installations or quit now.
Inst> quit
Requickstarting ELF files (see rqsall(1)) .. 100% Done.
You're all set now. Lets go do this upgrade thing.
Loading your overlaysNow that we've got your installer fixed, we will quit inst, and then restart it. Afterwards, we select IRIX 6.5.23 to be installed.
Inst> from /mnt/IRIX/6.5.23
___________________________________________________________________________
IRIX 6.5.23 Installation Tools and Overlays, December 2003 README
Silicon Graphics, Inc.
---------------------------------------------------------------------------
The IRIX 6.5.23 Overlay CDs contain the miniroot and other components
necessary for booting the system into the basic installation environment.
...
If you have never upgraded your SGI before, it will ask if you would like to be placed on the (f)eature or (m)aintenance stream. We generally select feature, unless there is some real fragile peice of software on the machine. So far, I've never picked (m)aintenance. If while running the open command, you saw errors like this, you forgot to update your installation tools like we talked about above:
WARNING: Invalid filetype "X" at line 29 of desktop_eoe_6521m.idb
WARNING: Invalid filetype "X" at line 31 of desktop_eoe_6521m.idb
ERROR: No product corresponding to "" at line 31 of desktop_eoe_6521m.idb
Okay, we also have to point it to where the original version of IRIX 6.5 was located. For this we will use the "open" command.
Inst> open /mnt/IRIX/6.5
Reading product descriptions .. 100% Done.
Your all set now.
Installing the overlaysNow select what you want to upgrade. We're going to tell it to leave the base system alone (keep *), and just install the standard upgrade, as well as any prerequisites. Typically, there are no pre-reqs. Perform the following steps:
Inst> keep *
Inst> install standard
Inst> install openssh
Inst> install prereqs
No matches for "prereqs" were found
Inst> go
If your lucky, that's all you have to do. If not, you've got conflicts
Resolving conflicts when upgrading IRIXMost of the time, when you are upgrading IRIX, you will run into conflicts. This is kind of guesswork, to be honest. You pick what software not to install, or what to delete. This is the error message you will see:
ERROR: Conflicts must be resolved.
gnu.sw.textutils cannot be installed because of missing prerequisites:
1a. Do not install gnu.sw.textutils (1278600920)
1b. Also install fw_textutils.sw.textutils (1236376120 - 1289999900) from
an additional distribution -- insert another CD or specify another
software distribution.
1. Address these conflicts now (show them)
2. Postpone these conflicts until later (hide them)
Please enter a choice [1]:
I recommend selecting 1. You'll get a list of all the conflicts. You can get this list at any time by typing "conflicts". It will give you a list of choices, and to choose them you can type: "conflicts 1a 2b 3b 3b 1a", or something similar. Once you have resolved everything, you will see the magic words:
Inst> conflicts
No conflicts
You may now type "go" and get on with your life. For reference, Here are common conflicts we see:
The dmedia and eos conflictThis one looks similar to:
eoe.sw.base (1289214920) is incompatible with dmedia_dev.sw.base (1278316532)
eoe.sw.base (1289214920) is incompatible with dmedia_dev.man.relnotes (1278316532)
eoe.sw.base (1289214920) is incompatible with dmedia_dev.man.pages (1278316532)
etc.
It means you probably did not patch your installation tools before trying to install the new IRIX overlays.
The GNU conflictThis is typical if you've installed anything from http://www.freeware.com/
gnu.sw.textutils cannot be installed because of missing prerequisites:
1a. Do not install gnu.sw.textutils (1278600920)
1b. Also install fw_textutils.sw.textutils (1236376120 - 1289999900) from
an additional distribution -- insert another CD or specify another
software distribution.
If you see conflicts with gnu.sw.*, just choose not to install it. The solution is pretty simple, just type "remove gnu". Then type "conflicts" again.
File PermissionsWARNING: Error reading product descriptor: /mnt/IRIX/6.5/performer_eoe. WARNING: Error reading product descriptor: /mnt/IRIX/6.5/sgitcl_eoe. That means that the file permissions are probably too tight on those files.
Finishing upNow we need to reboot our machines. I usually just run /etc/reboot.
/etc/reboot
|
