Installing OpenServer Release 5.0.6

This guide applies to OSR 5.0.6 ONLY

See also:

  • Installing OSR 5.0.0
  • Installing OSR 5.0.2
  • Installing OSR 5.0.4
  • Installing OSR 5.0.5
  • Install Problems and Gotcha's

    Installing OSR 5 is very straight forward and should not cause any major problems. These notes are aimed at Premvet Technical Staff and not the end user. If you are an end-user and are attempting the install then this should make sense - if not don't try it.

    These notes should be used in association with the OSR 5 release notes supplied with the system. There are many ways to setup and configure an OpenServer system, this page refer to our prefered method.


    All the OSR 5.0.6 documentaion is available on the CD and can be read with a browser PRIOR to starting the install. For example, insert the CD on a Windows PC and wander to:

    CDROM:\info\doc\ and bring up dochome.html

    It is a good idea to check out the Release notes and Features and Limitations prior to the install to check for important information.

    Another must before the install is to check out:


    This page contains up-to-date information that never made it onto the CD.

    Additionally, check out under the info sub-directory on the install CDrom as this has various text files with other helpfull tips and notes.

    Note: If there are ANY errors during the load START AGAIN, try switching OFF Internal and External cache in the BIOS during the load. If you cut corners here you may well get stuck later on.

    With release 5.0.6 you can, if your system supports it, install directly from the CD rom which is by far the better option. You will need to alter the BIOS so the bootable CD is active.

    If your system will not boot from the CD you will need to generate a boot floppy. On the CD (in the images sub-directory you will find dos utilities, unix disk images and readme's for generating the boot floopy disk.

    Make sure you have:

  • OSR 5 Boot disk (if not using the bootable CD option)
  • CD Rom
  • Serial numbers
  • User Licences (if needed)
  • SCSI Tapes should be set with an ID of 2
    SCSI CD's should be set with an ID of 5

    Insert the CD/Floppy and reset the machine - You should see:

    Press return

    Check hardware listing and if Ok press return to continue

    If you see: WARNING: hd: No root controller was found then the chances are the hard disk controller was not recognised and you may need to use a BTLD (Boot Time Loadable Driver) or a boot string.

    The 'common' hard disk controller are:

    Note: This is NOT a full list of the driver, see the features list on the cd.

    DriverHost Adapter
    ad Adaptec 154x, 164x, 174x (in Standard mode)
    fdhb Adaptec 292x, Future Domain 16x0, 600, 700 (18x0 Chip)
    ad160 Adaptec 2916x 3916x (7892, 7899 Chip)
    This is only available if booting from the CD. See the gotcha's
    alad Adaptec 294x 394x 494x (785X 7860 7870 7880 7895 Chip)
    blad Adaptec 2940U2W 2950U2W 3940U2W 3950U2 3950U2B (7890 7897 Chip)
    chaCompaq Fast-SCSI-2 Adapter
    cladCompaq Array Controller
    dptr DPT SCSI & RAID Host Adapters
    wd Enhanced IDE, ATAPI Interface (for tapes and CD-ROMs)
    wdha Future Domain (formerly Western Digital) 7000
    wdex Future Domain (formerly Western Digital) 7000EX

    For example, the DPT Century RAID controller is not currently supported so you would use a BTLD.

    Generally check ftp.sco.com/pub/drivers/OSR506/ for up-to-date drivers and use the SCO provided one rather than the one supplied with the card.

    At the boot prompt type: defbootstr link=dpti5 Sdsk=dpti(0,0,0,0)
    (Details of the exact string to use will be included either in the .ltr or readme file that comes with the BTLD).

    Or with a Mylex controller, you won't need a BTLD but may need to tell OSR 5 where it is connected e.g.

    At the boot prompt type: defbootstr link=mdac Sdsk=dpti(0,0,1)

    Once the hardware screen correctly identifies your hardware continue.

    After the licence screens you will be asked to select the install media e.g.

    SCSI CD Rom

    Installation from a SCSI CD-ROM is easiest.

    Install from SCSI CD
    Media Device to be used SCSI CD Rom
    Adapter Type alad, Adaptec 294x 394x
    SCSI Host adapter 0
    SCSI ID 5
    SCSI LUN 0
    SCSI BUS 0

    If you have a different SCSI host adapter, use the appropriate driver name from the above table instead of alad.

    IDE CD Rom

    Only fully ATAPI complient IDE CD's will work.
    Install from IDE CD
    Media Type IDE CD ROM
    Controller primary
    Master/Slave slave

    Determining your system configuration for ATAPI (EIDE) CD-ROM

    If you are uncertain of the hardware configuration of your system, but you know that the primary hard disk is attached to an IDE controller, the following information will allow you to determine the most likely configuration.

    Entries for the ATAPI CD-ROM will appear in system hardware report that is onscreen after booting. Look for lines of the following form, and especially a line with the string: type=wd:

    %adapter 0x01f0-0x01f7 14 - type=wd ha=0 id=7 bus=0 fts=d

    Here, ha=0 indicates that the ATAPI CD-ROM drive is attached to the Primary IDE controller.

    %adapter 0x0170-0x0177 15 - type=wd ha=1 id=7 bus=0 fts=d

    Here, ha=1 indicates that the ATAPI CD-ROM drive is attached to the Secondary IDE controller.

    If there is another device attached to the IDE controler, the effective SCSI ID of the CD-ROM drive is 0 if it is configured as a Master device or 1 if it is configured as a Slave device. If the other device is the primary hard disk drive, the CD-ROM drive will normally be configured as a Slave device. If your system has a primary SCSI hard disk, the CD-ROM drive may be configured as a Master device.

    If there is no other device attached to the IDE controller, the CD-ROM drive should have been configured as a Master device with an effective SCSI ID of 0.

    NOTE: The base I/O addresses and interrupt vectors shown on your system might differ from the examples shown above.

    Problems with UDMA drives

    If you are installing on a UDMA drive and the install hangs try

    defbootstr wd.udma=debug

    and see if it shows up any problems, or disable it completly with defbootstr wd.udma=off ..... .

    Once the media has been verified you will be asked:

    Keyboard Selection US English

    Licence Details See COLA

    Install Type Fresh

    System Name: Name of the machine
    Domain: uucp
    Security: Traditional
    Time Zone Europe / GMT with Daylight Saving
    Language: Standard C (English)

    Note: The computer Name, IP address and domain will be on the configuration form. DO NOT just pick something off the top of your head.

    Standard Enterprise configuration Yes
    Lightweight No
    Database services No

    Configure the hard disk to suit your need. Do not use the entire disk for root, as the root partitions is usually the first to fail. You have three options on how to configure the disk(s) The 'Customise' option is by far the easiest to use.

    Swap Minimum 64Mb, about 2 x installed RAM
    Root Minimum 700Mb, no more than 1.5Gb
    u Split the rest of the disk into as many areas as required.
    Generally make the /u filesystem about 2Gb the others use your common sense.

  • Bad Tracking: If you want but will add time, not normally needed for modern disks.

  • Select the software that you will install.

  • Configuring Optional Software

    Network Card : If you are using a supported type use Autodetect, If in doubt just select Defer and configure it later using netconfig.

    Note: To save a lot of time and effort, use only supported network cards, certainly NOT NE2000 clones.

    If this computer is going to be part of a network, then you will need to assign it an IP address.

    There are 3 IP address ranges available for use in a Private Network: to to to

    Given that 192.168.x.0 is the Network Address and 192.168.x.255 is the Broadcast Address.

    Network Address
    IP Address:
    Net Mask
    Gateway Address  
    Primary N.S.  
    Secondary N.S.  
    IPX Number : Accept default
    IPX network: Accept default
    IPX Framing: Accept default

    Use a supported video card, failing that use the generic VESA SVGA driver. Performance is not great but better than nothing.

    Card: If using a supported card select it otherwise use VESA SVGA
    Video mode: Accept default
    Monitor: Accept default
    Graphical login: Set to OFF

    Leave the resolution set at default at present, this can be reconfigured once the install has finished.

    The load of the software is automatic from this point on. If any errors occur, try a 'retry' otherwise start again.

    Once installed re-boot as advised.

    If there are any additional user licences, install them via: scoadmin -> licence manager

    You will still need to register but this can be done at a later point. It may be easier to continue with the rest and register when install finished.

    Register Enterprise/User licences by visiting www.sco.com.

    Install the Premvet Utility CD and any patches that may be required.

    Possible Problems or Gotcha's


    With OSR 5.0.6 /usr/local is a sym-link down into the /var/opt/K... tree - this does give you problems if you load your own applications into /usr/local and want to keep them separate from the operating system.

    Some pointers

    How Can I stop OpenServer 5.0.6 creating /usr/local as a sym-link.

    1. After the install remove /usr/local and re-create as required. BUT - if you do this and then at some point in the future you run custom verify and let it fix the discrepencies then your /usr/local will be moved to /usr/local# and the sys-link will be re-created.

    2. Edit the Custom+ database to stop custom complaining.

      WARNING - Incorrect Editing the Custom+ database WILL give you problems - be carefull.

      You need to comment out one line in the file


      The line is:

      EXPORT r ./usr/local /usr/local

      You can use a script similar to:

      ----- Cut Here ---------
      sed -e 's/^EXPORT r .*local$/#&/' < ${DIR}/${FILE} >${DIR}/$$
      mv ${DIR}/$$ ${DIR}/${FILE}
      ----- Cut Here ---------

      To do it for you.


    This only applies to an IPU, normally all users will be allowed to submit cron jobs - however, the IPU will automatically populate the cron.allow file. This will limit access to cron only to those users, after the IPU just remove /usr/lib/cron/cron.allow

    Adaptec Ultra160

    First off there is NO support for the 19160, this is a low end card not suitable for a server.

    The 29160 is fully supported, however, this will only be recognised if you boot from the CD. There was not enough room on the boot floppy to include the ad160 driver.

    The CD does hold a copy of the driver as a BTLD - mount the CD and have a look at .../images/boot/readme.txt.


    The uucp binary /usr/bin/uucp is broken. You should until an SLS is produced use the uucp binary from a 5.0.5 system


    If doing an IPU then there are a couple of duplicated lines in /etc/inetd.conf. You should check and edit as required. In my case it was pop3 and imap

    Comments on routing deamon

    In 5.0.6, the route daemon (routed or gated) will not start unless the variable ROUTER_DAEMON is set. A default route will not be established if the variable GATEWAY is not set. Thus, if neither variable is set, neither route daemon and default gateway are used.

    The way the /etc/tcp script is now coded, the route daemon will start regardless of the default route. If you have both configured, both will start.

    During the Initial System Load (ISL), there is no way to set the route daemon (I believe). You can only set the default route. If you leave the default route field blank, you won't get a default route either.

    I think this covers the bases.

    As for the default route, you set it by editing /etc/default/tcp and supplying the IP address of the router in the GATEWAY variable. If you want to start a route daemon too, use the ROUTER_DAEMON and ROUTER_DAEMON_ARGS variables in /etc/default/tcp.

    check out the late breaking news at this URL:


    You can still use /etc/rc2.d/S99route if you wish, but not for the default route. The code to start the default route is in /etc/tcp (/etc/rc2.d/S85tcp). Leaving it in S99route will result in a warning message on system startup.

    So we now have:

    Comments and suggestions always welcome - tom@tkrh.demon.co.uk