How to Install IRIX 6.5.26m Using Product Selections Files (for use with O2, Octane/Octane2, Fuel, Tezro, Onyx2, Origin, etc.) By Ian Mapleson Last Change: 18/Apr/2009 This document explains how to install IRIX 6.5.26m on a system which cannot be booted using the original IRIX 6.5 June 1998 boot CD. This includes systems such as R5200/300 O2, later Octanes with E-series graphics or VPro, R12K systems, etc., though the procedure given here will work for any SGI system that can use 6.5.26. Please read through this document _before_ commencing the installation; this will help avoid many unexpected or avoidable problems. Please also read the file warning.txt before proceeding. Since the installation this document describes results in a system that is already running a 6.5.x update, installing extra items requires one to read in both the base June 1998 CD for the item, plus the update to that item from the relevant 6.5.x CD. Thus, I have created product selections files to help make this process considerably easier. However, in order to use the devsw*.txt selections files, you must either have my combination CD that contains Inventor, NFS and CosmoSuite, or else have these items available on separate CDs. Otherwise, conflicts may appear which must be resolved prior to installation. In general, the selections files should work ok for most 6.5.x releases, but I've only tested them with 6.5.22 and 6.5.26. NOTE: this installation description *only* applies to the maintenance stream. I do not use the Feature stream. Preparation ^^^^^^^^^^^ To do the initial installation, you must have the following CDs (I call this the 'base set'): IRIX 6.5.26 Installation Tools and Overlays 1 of 3, November 2004 IRIX 6.5 Foundation 1, June 1998 IRIX 6.5 Foundation 2, June 1998 IRIX 6.5 Applications, June 1998 IRIX 6.5.26 Overlays 2 of 3, November 2004 IRIX 6.5.26 Overlays 3 of 3, November 2004 IRIX 6.5 Applications, November 2004 IRIX 6.5 Complimentary Applications, November 2004 Boot from the 6.5.26 Inst Tools CD in the normal way to fx the disk and prepare a blank file system. Full details on how to do this are on my web site at: http://www.sgidepot.co.uk/6.5inst.html As a quick summary though: start the system, press ESC for maintenance, press 5 to get into Command Monitor and then enter the relevant boot command, eg. for an O2 the command would be (assuming the use of the internal CDROM): boot -f dksc(0,4,8)sashARCS dksc(0,4,7)/stand/fx.ARCS --x while for an Octane it typically would be as follows (assuming an external CDROM on SCSI ID 4): boot -f dksc(1,4,8)sash64 dksc(1,4,7)/stand/fx.64 --x Note that some 64bit systems may refer to SCSI devices as scsi(a,b,c), eg. I think Origin200 is one such system, in which case the boot command would be something like this: boot -f scsi(1,4,8)sash64 scsi(1,4,7)/stand/fx.64 --x or whatever the appropriate controller and ID are. The output from hinv will confirm how a system labels the devices. Anyway, once at the fx prompt, select repartition, root drive option, confirm xfs, confirm, enter '..' to go up a menu level, then enter 'l', then 'sy' to write out the label information to disk, and finally enter '/exit' to quit fx. You would enter the following character sequence to achieve this: r ro yes .. l sy /exit Back at the maintenance menu again, press 2 for Install System Software, confirm the use of the CDROM and click Go. After the installation tools have been read in, the system may say the disk has no valid file system and offer the choice of a shell prompt. If so, then enter the shell and then enter this to create the file system: mkfs /dev/dsk/dks0d1s0 and then exit the shell with CTRL-D. Some systems will just offer the option of creating a new file system instead, in which case confirm this action and select a 4096 block size if your disk is 4GB or larger, or a 512 block size if your disk is less than 4GB. The system will try again to mount the root disk on /root. If the disk already has an old valid file system on it, the system will be able to mount the disk straight away. If this happens, wait until you are at the inst prompt and then use the admin menu option to clear the disk - full details on my web page, but essentially just enter '13' (admin), then '11' (mkfs), then confirm the operation and afterwards enter '..' to go back to the top level inst menu. In either case, when the README file appears on screen, press Q if necessary to stop reading any README file and then, when asked, select 1 for the Maintenance stream; sometimes you may be asked to choose a stream in the next step - either way, just select the Maintenance stream. Now at the Inst prompt, the base set CDs must all be read in. Enter 1 for the 'From' menu option, confirm /CDROM/dist, ignore the README file again and let it read the CD. When the inst prompt appears once more, eject the CD (using the CDROM's hardware eject button) and insert the Foundation 1 CD. When the CD is ready (spinning), press Enter to read from /CDROM/dist again. After it's been read, repeat the procedure for the Foundation 2 CD and all the other CDs listed above for the base set. When README files appear for the applications CDs, just press Q to quit out of the README and let it read the CD. Once the final CD has been read (Comp Apps Nov 2004), enter 'done' to quit the CD-reading process. Now back at the Inst prompt, enter: keep * install standard install prereqs You will likely see an apparent error message which says something like, "No matching prereqs were found". This is completely normal and can be safely ignored. Now enter 'conflicts' and you will see a list of conflicts. Repeatedly select the 'a' choice in each case (ie. 1a, 2a, 3a, etc.) to not install the offending items until there are no more conflicts. Infact, on most systems the following command sequence will results in inst reporting no conflicts remain: conflicts 1a 2a 3a 4a 5a 6a conflicts 1a Now enter: go This will begin the installation. As the installation progresses, you will be prompted to exchange the CDs so Inst can read from them. They will be requested in a slightly different order from the order in which they were first read, but don't worry about this. Also, Inst will want to read some CDs more than once as it both installs IRIX 6.5 and updates it to 6.5.26 at the same time. When you insert each CD, you don't need to press Enter or anything - the system detects automatically when the CD is ready to read from. Once the installation has finished, enter 'quit' to to exit Inst. This will begin the rqsall procedure (see the rqsall man page at a later time for details of what this does). While this is going on, you can still enter 'y' so that, when rqsall completes, the 'y' (yes) choice to restart the system is already in the keyboard buffer, ie. the action will occur without your having to be present. Thus, once you've entered 'quit' and 'y', eventually the system should reboot on its own and come up with a login screen. Indeed, if the installation is done from a hard disk containing dumps of the various CDs, one can begin the installation and enter 'quit' and 'y' straight away, leaving the system alone until it brings up the login screen, ie. no need to change CDs. When the system boots up for the first time, you may notice it appears to pause for a long time during the boot process on two occasions. Don't worry about this, I will explain later exactly why this happens and how to fix it - the delays are just caused by certain default system services timing out because they haven't yet been configured or turned off. Login as root. From the Toolchest, select: Desktop -> Customize -> Windows Select the 'Click to type' option for Keyboard Focus and confirm. This will restart the window manager so that the mouse focus policy is click-to-use rather than point-to-use. IMO, this is far more sensible than the default point-to-use configuration, but if you prefer the default mode then don't do this step. Close the Windows Settings panel. Bring up a shell window from the Toolchest: Desktop -> Open UNIX Shell Remove whatever CD is in the CDROM drive (enter 'eject' in the shell window, or click on the CDROM icon and use the mouse right button to select 'Eject CDROM') and insert the following CD: SGI Gifts April 2009, Part 1 of 2 Once the CDROM icon shows the CD is ready, enter the following in the shell window: cd /CDROM/BaseChange ./RUN After a short pause, you will be logged out. Don't worry, this is normal. The script changes a number of things about the default system setup which most users should find useful. Various unnecessary services are turned off, the root shell is changed to tcsh (change this later if you'd prefer a different shell for root), /usr/local/bin is created with a variety of useful commands and scripts, an enhanced .cshrc for root is copied over and an example desktop is created. The script logs you out in order to install and extract the desktop archive - wait at least 10 seconds and then log back in again as root; the script extracts the desktop archive ten seconds after logging out, so you should hear some noise from the disk when this happens, ie. login again when the noise stops. NOTE: sometimes the extraction of the example desktop doesn't work; if you login and find the desktop has not changed, then logout and do the following: - Login as guest - Start a UNIX shell from the Toolchest - Enter this: su - root rem -r .desktop-IRIS .desktophost Desktop tar -xvf desktop.tar then logout again and log back in as root. Usually though, the example desktop layout will be created just fine. When you login as root, a much better desktop will appear with many more icons, well-positioned shell windows, and after a few seconds a Netscape window will appear (along with two error boxes about creating the Netscape cache; just dismiss these). Close the Netscape window at this point; it won't be relevant until later. This is just an example desktop of course, but in my opinion it's much better and more practical than the default desktop layout. Feel free to change this. Note that the example desktop will show icons that are initially 'dead' (like a blue circle), but don't worry about this; as more software is installed, these icons will become valid and change appearance. Also note that my Gifts CD (1 of 2) has further example desktops in the misc/desktops subdirectory, eg. some example system- specific desktops, such as a desktop for O2 systems which has many of the O2 demos icons already on the desktop. Now enter the following in any shell to deactivate some other services which most users won't need ('chk' is one of the aliases defined in the replacement .cshrc file; it stands for 'chkconfig'). You can use the mouse to highlight these lines and paste them directly into a shell window with the middle mouse button. chk esp off chk webface_apache off chk sesdaemon off NOTE: if your system has FibreChannel and you intend to use it, then do not turn off sesdaemon. Next, before proceeding with further installations, I always change three system startup scripts to help speedup the system bootup time. This was mentioned earlier when I referred to the mysterious pauses that occur the first time the system boots. Enter the following in a shell: cd /etc/init.d j network Press CTRL-F (hold down CTRL and press F, to search the text). Type 'MSGT' and press Enter. The editor will jump to a line which shows this: MSGTIME=10 # number of seconds to display error message Change the number from 10 to 0, then save and exit jot. This prevents the system from pausing for 10 seconds on bootup just because, for example, the host name is still set to IRIS. WARNING: jot is an IrisGL application; unfortunately, it has a bug concerning the way in which jot exits. On newer systems with VPro graphics (Octane[2], Fuel and Tezro), if you use the Alt+Q method to exit, it can cause the system to bomb out the X server. Thus, to exit from jot on any VPro system, always hold down the right mouse button over the jot window and select Exit from the popup menu, or for absolute safety just use the kill command to terminate the jot window. Alternatively, you can use nedit to make the changes instead, or you can use vi (I often use vi for such tasks because it's very fast to use for making simple changes to files). Anyway, the next file to change is the mail configuration script, so enter: j mail Press CTRL-F. Enter 'newal'. The editor will jump to a line which looks something like this: newaliases >/dev/null If not already present, add a '&' symbol to the end of the line so that it looks like this: newaliases >/dev/null & though usually the line will already have the '&' symbol present. Save and exit jot. This change prevents Sendmail from stalling for 60 Seconds on bootup just because the system email domain hasn't yet been defined. In conjunction with turning off esp, these three changes decrease the system bootup time by more than 2 minutes!! On systems with later CPUs, this makes for a massively faster startup time. I have been told that, with these changes in place, an R12K/400 Octane will boot faster than many modern PCs. Of course, if you don't need sendmail at all, then you could turn off all of the sendmail daemons with: chk sendmail off chk sendmail_cf off Next, enter: j filesystems (note that you can just type 'j fi' and then press TAB to fill in the rest - the joys of tcsh! 8) Press CTRL-F. Enter 'p 5'. The editor will jump to a section which looks like this (I've snipped the first line a bit as it's rather long): lfmt -G 1 'Some filesystems failed to mount; may be (blah blah...) sleep 5 Change the sleep number from 5 to 0, then save and exit. This means that if ever the system reports a failure to mount a file system on startup (eg. an external disk wasn't turned on), the system will not pause for 5 seconds. Why bother pausing when, because verbose is on, the same error message is shown on the startup text screen anyway? These are simple changes to make, but they can make life a lot easier for some users, eg. those who often have to turn their systems on and off for security reasons, noise, power usage, component testing, etc. Turning off the esp service as shown earlier prevents one of the major startup delays: if left unconfigured, esp times out on bootup for 60 seconds. The easiest initial solution is just to turn it off. Most home/hobbyists don't need ESP anyway, but if you're in a company with a proper SGI support contract, then look into the use of ESP as you may find it useful. The next step is to remove some unwanted software items, which at last requires the use of the selections files from the first Gifts CD. Assuming the Gifts CD is still in the drive, enter the following to copy the selections files to /var/tmp (since CDs must be swapped to do further installations, the selections files must be copied to the local disk now in order to have access to them when needed later): cp /CDROM/Selections/6.5.26/* /var/tmp Note that with tcsh, you can use TAB to help complete the file names as you're typing. This action also copies the README file to disk, so feel free to load it into jot for reference as you're doing the installations. Run up swmgr, click on Manage Installed Software. Select Load Selections from the File menu and select this file: /var/tmp/delbits.txt This selects a number of items for removal which the vast majority of users won't need, eg. the MediaBase Client software. Customise the choices if desired and then click Start to begin the removal process; when finished, choose Continue. NOTE: if you have more than one CDROM attached to your system, always use the default CDROM for installing extra software with the selections files, ie. the unit which the system would regard as /CDROM. Thus, for an O2, this would always be the internal drive. Software Manager is not able to properly track the use of an alternate CDROM source such as /CDROM2, though note that alternate locations from a disk device work fine, eg. if you've copied any CDs to disk for speed and convenience. Now we are ready to begin installing extra software. Swap the CD in the drive for the 6.5.26 Inst Tools CD (either enter 'ej' in a shell, or click once on the CDROM icon once and use the right mouse button menu to eject the CD). Still in swmgr, select Open Distribution from the File menu and choose /CDROM/dist. Dismiss the README that appears and let it read the CD. A panel may appear afterwards asking you if you'd like to read further CDs - if this happens, then just use the option to eject the CD each time. If it doesn't ask about reading further CDs, click on Customize Installation. Once done, select 'Open Additional Distribution' from the File menu (or the panel may appear automatically as I say), click 'Eject CD', insert the Foundation 1 CD, wait for the CDROM icon to change, then click Add. Let it read the CD. Now repeatedly read the other base set CDs in the same way, clicking Add each time, but with the addition of the combined Cosmo/NFS/Inventor CD (or just use the separate original CDs if you don't have my custom combined version), ie. the list of CDs to read in is as follows: IRIX 6.5.26 Installation Tools and Overlays 1 of 3, November 2004 IRIX 6.5 Foundation 1, June 1998 IRIX 6.5 Foundation 2, June 1998 IRIX 6.5 Applications, June 1998 Network File System (NFS) V3, June 1998 (#) Open Inventor 2.1.5, October 1998 (#) Cosmo Suite, August 1998 (#) IRIX 6.5.26 Overlays 2 of 3, November 2004 IRIX 6.5.26 Overlays 3 of 3, November 2004 IRIX 6.5 Applications, November 2004 IRIX 6.5 Complimentary Applications, November 2004 (#) If you don't have these items by way of my combined NFS/Inventor/ Cosmo CD (which allows one to read in all 3 items in one go), then just use the separate original CDs. If the selection panel disappears at any stage, just choose Open Additional Distribution from the File menu to bring it up again and continue reading in further CDs. Once the last base set CD has been read (click Done if the Open Additional Distribution panel is still visible), and if swmgr hasn't done so already, choose Customize Installation. swmgr will tick various default items for installation; this will make the Conflicts button go red, but just ignore this. Choose Unmark All from the Selected menu (this is to clear the initial selections made by swmgr) and then choose Load Selections from the File menu; load the following selections file: /var/tmp/basesels.txt If you're using a system which uses a 64bit kernel (R8K/R10K Indigo2, Onyx, Octane, Fuel, Onyx2, Origin, etc.) then load this file instead: /var/tmp/basesels64.txt NOTE: O2 systems do NOT use a 64bit kernel. If you are using any O2 system, always load the basesels.txt file. The selections mark a whole range of very useful extras which the vast majority of users would wish to have installed if they knew they were present. Demo programs, examples, extra documentation, useful tools and applications, MIDI support, spell utilities, reference materials, N32 libraries, etc. On an N32 system such as O2, about 770MB of extra software is installed, while for an N64 system roughly an extra 940MB of data is installed. Click Start to begin the installation. swmgr will prompt for the CDs to be changed as and when appropriate, likely beginning with a request to insert the "Foundation 1" CD; a panel will appear which has an 'Eject CD' button you can use to eject the current CD. When you insert each CD, there is no need to click on anything - when the CD is ready to read, swmgr will detect this automatically and begin reading it (the panel will disappear again). When the installation has finished, select the option to restart the system; this will commence the rqsall procedure and then eventually reboot the system. Once the system is back up, login as root again. Eject whatever CD is in the drive - try the 'e' command to do this; a simple yet effective alias. Note that if the definition of the 'e' command in /.cshrc does not match the SCSI controller/ID of your CDROM, then just edit the .cshrc file so that it does match. By default, the 'e' command tries to act on controller 1, ID 4. Or you can enter 'ej', though 'e' is a better command to get used to using since it can eject the CD even if the system is having problems dealing with the current CD in the drive (the alias acts on the raw SCSI device). Next, if you don't intend to create or use disk volumes, stripes or RAID arrays, then turn off the xlv service: chk xlv off The system now has a full base 6.5.26 installation. Even at this stage, what has been installed is far more complete and useful than you'd ever find on any system purchased from eBay, or even from most dealers. Next comes the installation of all the development software. Insert the following CD into the drive: IRIS 6.5 Foundation 1, June 1998 Either double-click on the CDROM icon, or run up swmgr and choose Open Distribution, selecting /CDROM/dist as the source. Click on Customize Installation. Once read, repeatedly select Open Additional Distribution (OAD for short) from the File menu, ejecting CDs each time, to read in the following CDs in this order, using either a target source directory of /CDROM/dist or /CDROM/dist/dist6.5 as shown on the right for each item (use the Browse option if necessary to specify the appropriate location for each CD): CD Title Source Dir. ^^^^^^^^ ^^^^^^^^^^^ IRIS Performer 2.2 for IRIX 6.2 or later, Dec 1997 [1] IRIX 6.5 Development Libraries, June 1998 [1] IRIX 6.5 Development Foundation, June 1998 [2] MIPS Pro All-Compiler CD, May 1999 [2] Network File System (NFS) V3, June 1998 (#) [2] Open Inventor 2.1.5, October 1998 (#) [1] Cosmo Suite, August 1998 (#) [2] IRIX 6.5.26 Inst Tools and Overlays 1 of 3, Nov 2004 [1] IRIX 6.5.26 Overlays 2 of 3, November 2004 [1] IRIX 6.5.26 Overlays 3 of 3, November 2004 [1] SGI Gifts April 2009, Part 1 of 2 [1] [1] Select a target source directory of /CDROM/dist [2] Select a target source directory of /CDROM/dist/dist6.5 (#) Use my combined Open-Inventor/NFS/CosmoSuite CD, if you have it available, using a source of /CDROM/dist. All of these CDs with their respective sources must be read in, one after the other, using OAD (Open Additional Distribution) and clicking Add (with /CDROM/dist already selected) or by using Browse to choose the right directory first and then clicking Add. Once all the CDs have been read, click Done if the OAD panel is still visible. From the Selected menu, choose Unmark All to clear the default choices made by swmgr. Now use Load Selections from the File menu to load the file: /var/tmp/devsw.txt If you're using a system with a 64bit kernel then load this file instead: /var/tmp/devsw64.txt This selects a vast range of all the main development software for installation, with no conflicts. Remember that the file selects *everything* for installation. Don't worry if there are items selected that you don't need, just let it install everything first; if you want to remove something, do so after the whole full installation has been completed. Remember that, unless disk space is an issue, and unlike PCs, having unwanted or unnecessary software installed makes absolutely no difference to system performance whatsoever. On an N32 system, an extra 1410MB of data is installed, while on an N64 system an extra 1735MB of data is installed. Click Start. Swap CDs as requested. When the installation has finished (which will take quite a while), choose Exit - rqsall will be executed once more. When the swmgr window has gone, enter 'reboot' in a shell window to restart the system. Login as root again after the system has rebooted. Now enter the following to remove old unwanted configuration files, if they are present: cd /etc rm inetd.conf.O services.O Be careful not to remove the wrong files. It must be the .O versions. On some systems, the old files are not there to be deleted though. Now enter the following to turn off some other system services, unless you intend to use a particular service: chk tfxd off chk sendmail off chk sendmail_cf off chk grio off chk cluster off Use the man command to obtain information about a service, or consult the online help system (InfoSearch). SGI Gifts CDs ^^^^^^^^^^^^^ Insert the following CD into the drive: SGI Gifts April 2009, Part 1 of 2 Either double-click on the CDROM icon, or run up swmgr and choose Open Distribution, selecting /CDROM/dist as the source. Click on Customize Installation. Once read, from the Selected menu, choose Unmark All to clear the default choices made by swmgr. Now use Load Selections from the File menu to load the file: /var/tmp/gifts.txt Click Start to begin the installation. SGI Nekoware ^^^^^^^^^^^^ If you have my custom 8-CD split of the Nekoware software, then full installation instructions can be found in the README on the first Nekoware CD. Briefly though, the procedure is similar to installing the freeware: - read in the first two Neko CDs into swmgr using /CDROM/dist, - select Customize Installations and then Unmark All, - select Load Selections, - choose the file neko.txt, either from /var/tmp or from /CDROM/dist. This will select 1GB of software for installation, or roughly half the items from the first two CDs.. If you wish to install the extra items, which I would definitely recommend, then also load the selections file neko-extra.txt, which will combine the choices of both selections files, resulting in about 2GB of software selected for installation. Alternatively, just load the file neko-full.txt initially. Note that some Neko products do not contain complete dependency rules. Thus, it is much easier just to use my selections files as this will ensure that all prerequisite items for products are already installed. Also note that the normal Nekoware is compiled MIPS4; although swmgr will not stop you installing items onto a MIPS3 system (ie. any R4K system), the installed items will not run, unless - for example - they are installed onto an R4K Indy which is later upgraded to R5K, or an R4K Indigo2 which is upgraded to R8K/R10K. If you do install any Neko items, remember to add the /usr/nekoware locations to your .cshrc file in order to have access to the software, ie. add /usr/nekoware/lib to $LD_LIBRARY_PATH, add /usr/nekoware/man to $MANPATH, and add /usr/nekoware/bin to the main $PATH. Alternatively, run the INSTALL script on the first Gifts CD, which sets this up automatically and also installs a custom reference page with links to numerous online documents about the various Nekoware items. If you ran the RUN script from the BaseChange directory on the 1st Gifts CD though, then these changes have already been made for you. After the installation has completed, you may wish to turn off any extra chkconfig flags that have been created, for any service which is not yet going to be used, eg. samba. At this point in the installation process, it is likely that the various updates which have occurred to certain items will have resulted in the configuration files for the Apache web server being renamed, which prevents the server from starting up. You can tell if this has happened because Apache will report on bootup that it is unable to startup, with the lines: Starting SGI Web Server(s) /var/sgi_apache/httpd-outbox /var/sgi_apache/httpd-outbox/sbin/apachectl start: httpd could not be started Cannot start /var/sgi_apache/httpd-outbox. or just examine the directory: /var/sgi_apache/httpd-outbox/etc and see if the files inside look anything like this (with 'ls -l'): -r--r--r-- 1 root sys 0 Oct 9 01:08 access.conf -r--r--r-- 1 root sys 348 Oct 8 03:06 access.conf.bak24077 -r--r--r-- 1 root sys 0 Oct 9 01:08 httpd.conf -r--r--r-- 1 root sys 45501 Oct 8 03:06 httpd.conf.bak24077 -r--r--r-- 1 root sys 45649 Oct 8 02:41 httpd.conf.bak284 -r--r--r-- 1 root sys 12441 Oct 8 02:41 magic -r--r--r-- 1 root sys 15016 Oct 8 02:41 mime.types -r--r--r-- 1 root sys 0 Oct 9 01:08 srm.conf -r--r--r-- 1 root sys 357 Oct 8 03:06 srm.conf.bak24077 (there are some other files which are ssl.* links to files elsewhere, but those don't matter) As can be seen, the main configuration files have been renamed. To fix this, rename the most recently modified version of each file to its normal name and then delete any unwanted files. Thus, in the above example, the httpd.conf.bak24077 file is the most recently modified version of the httpd.conf file; the other affected files only have one modified version present, so they're the only file to rename. In this example, the commands would be as follows: IRIS# mv access.conf.bak24077 access.conf Overwrite access.conf? (yes/no)[no] : y IRIS# mv httpd.conf.bak24077 httpd.conf Overwrite httpd.conf? (yes/no)[no] : y IRIS# rem httpd.conf.bak284 IRIS# mv srm.conf.bak24077 srm.conf Overwrite srm.conf? (yes/no)[no] : y IRIS# ls -l total 176 -r--r--r-- 1 root sys 348 Oct 8 03:06 access.conf -r--r--r-- 1 root sys 45501 Oct 8 03:06 httpd.conf -r--r--r-- 1 root sys 12441 Oct 8 02:41 magic -r--r--r-- 1 root sys 15016 Oct 8 02:41 mime.types -r--r--r-- 1 root sys 357 Oct 8 03:06 srm.conf The Apache server can now be started successfully by: /etc/init.d/sgi_apache start which will now give the normal startup messages: Starting SGI Web Server(s) /var/sgi_apache/httpd-outbox /var/sgi_apache/httpd-outbox/sbin/apachectl start: httpd started It is quite easy to make these chanes by using the TAB key to auto- complete the file names as you type. SGI Gifts April 2009, Part 1 of 2 (non-swmgr items) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ For full details on using the SGI Gifts CD Part 1 of 2, please consult the main README file on the CD. Essentially though, insert the 1st Gifts CD and then enter: /CDROM/INSTALL Answer the questions which are presented. After installation, feel free to install anything else you want from the Gifts CD, eg. RealPlayer8, extras from the Unsorted directory, etc. Full details on each item are in the top-level main README file on the CD. SGI Gifts April 2009, Part 2 of 2 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This contains Quake/Quake2-related items, plus the FightGear flight simulator. If you want to install Quake and/or Quake2, consult the README file on the CD for installation instructions. SGI Gifts Extras, April 2009 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Insert the CD, double-click on the CDROM icon, choose Customize Installation, select Unmark All from the Selected menu and then select the items you'd like to install. NOTE: 6.5.26 already includes a newer version of Mozilla, but if you do install the version of Mozilla contained on the Gifts Extras CD, note that it has a wrapper script which causes the normal startup icon in /usr/freeware/bin not to function. It will startup fine if you enter 'mozilla' in a shell, but if you want a desktop icon to start Mozilla, then do this: Select 'File QuickFind' from the File menu of the Toolchest. Type the following into the box but do not press enter: /usr/freeware/mozilla/mozilla When the icon appears, drag it to your desktop. As for the Adobe software on the CD, full installation instructions are in the file /CDROM/adobe/crack/README. Instructions for installing the other items are in the main top-level README on the CD. O2 Demos 1.2 for IRIX 6.5 ^^^^^^^^^^^^^^^^^^^^^^^^^ If you have this CD and are using an O2 system, insert the CD and enter: swmgr -f /CDROM/install When swmgr appears, click on Customize Installation. Choose Unmark All from the Selected menu. Load the selections file called: /var/tmp/o2demos.txt Click Start. Exit swmgr when finished. The O2 demos use up 436MB of disk space. Obviously, don't bother with this CD if you're not using an O2 since most of the demos will only work on an O2; some do work ok though, eg. the 3D models of ChromeSkins O2, Underwater Camera and Huge Engine Model (I use these on my benchmarks page). Octane Demos 1.3 and Octane2 Demos 1.0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ If you have this CD and are using an Octane or Octane2 system, insert the CD and enter: swmgr -f /CDROM/install When swmgr appears, click on Customize Installation. Select whichever items you want to install and click Start. Exit swmgr when finished. Obviously, don't bother with this CD if you're not using an Octane or Octane2 since many of the demos will only work on the appropriate system; some of the Octane demos will work ok though and can be installed just fine on an IMPACT Indigo2. However, swmgr will only allow you to install the Octane2 demos on a system which has VPro graphics - indeed, if your system does not have VPro graphics, then the Octane2 demos are not even shown in the swmgr product listing. Similarly, on a system with VPro graphics, the earlier Octane demos will not be shown for installation, although some of the older demos will run fine on a VPro system. You can get round these swmgr restrictions by installing onto an appropriate system and then manually copying over the relevant demos subdirectory by using tar, though this is only worth doing for trying out the older demos on a VPro system - the later demos will definitely not run on an older MGRAS system. IRIS Performer Friends Demo CD, December 1997 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ This CD does not have installable products. Instead, the CD contains 3D models, demos and other example data files for IRIS Performer. Read the documentation on the CD for full details. For example, many of the models can be loaded using the perfly program. If you intend to use IRIS Performer to create your own 3D applications, or are just curious as to what Performer is capable of (often demonstrated via the perfly program) then this CD is a good source of examples. Now for one final essential task, namely updating the online help book system so that the books are fully accessible within InfoSearch. Do the following: - Turn on the system and login as root. Do this at a time when the system will not be needed for several hours, since this operation can take a long time, especially on a lower spec system such as an R5K/180 O2, eg. leave it running overnight. - Enter the following in a shell window: timex insightAdmin -c This examines every online book, converting any books in the old SGML format into the new format required for InfoSearch. The 'timex' part isn't strictly necessary, but I find it useful to know how long this procedure takes when doing installations, and at least you'll know how long it takes if you have to do it again in the future. And that's it! All done! When doing a disk installation for someone, there are various other things I do to enhance the installation even further, such as extra changes to the online web pages, adding other icons to the desktop layout, etc. Some of the files I use to make these extra changes are in the misc directory, though as yet there's no documentation about them, eg. a modified version of the RUN script for the HugeEngineModel demo from the Octane Demos CD (the default file does not work). Email if you have any questions! I have tested this installation procedure on an various configurations of O2, Octane, Octane2 and Fuel. The selections files allowed me to install *everything* without any conflicts (about 6GB of data), which is the goal of this document. Feedback on this help file is most welcome. If you would like the combo CD, Gifts CD(s) and/or Aug 2003 freeware CDs (my own split), feel free to email me. Cheers! :) Ian. SGI Depot: http://www.sgidepot.co.uk/sgidepot/ Email: mapesdhs@yahoo.com Tel: +44 (0)131 476 0796 CC all emails to: ian@sgidepot.co.uk and sgidepot@blueyonder.co.uk My Auctions: http://uk.ebid.net/perl/main.cgi?words=mapesdhs&mo=search&type=user Tired of eBay? Then try eBid! Safe, secure! Follow this link to register: http://uk.ebid.net/perl/normal.cgi?ref=mapesdhs&mo=register-main SGI/Future Technology/N64: http://www.sgidepot.co.uk/ Mirror (Holland): http://www.futuretech.blinkenlights.nl/ Mirror (USA): http://vintagecomputers.info/