Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

comp.unix.sco Technical FAQ (2/7)

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Houses ]
Archive-Name: comp.unix.sco Technical FAQ 2/7
Posting-Frequency: Monthly (mid month)
Last-modified: Oct 12



comp.unix.sco Technical FAQ 2/7

See reader questions & answers on this topic! - Help others by sharing your knowledge
   Questions and Answers Specific to OpenServer Release 5
   
   FAQ Starting Page http://aplawrence.com/SCOFAQ/index.html
   
   These FAQS were developed and maintained for years by
   steved@ussinc.com (Stephen M. Dunn). Steve no longer has the time to
   maintain them, and has asked me to take them over. Please remember the
   debt all of us owe to Steve for his efforts- I myself spent many hours
   learning from these very documents, and I'm sure many of us can say
   similar things.
   
   Because Steve has not been able to maintain these for a while now,
   some of the information herein is outdated. I am working to correct
   that, but it's a lot to catch up on, so if you spot something, please
   let me know. For the moment, I'm just marking some of it as probably
   being useless; as I have time, I'll check further to be certain before
   I remove anything.
   
   Suggestion: Use my Search to find what you are looking for.
   
   NOTE: There are also many questions which apply not only to OSR5 but
   also to other Unix (and possibly Xenix) versions. If you don't see the
   answer to your question here, please check the other sections of this
   FAQ, as your question may be answered there.
   
   Graphical characters don't work

   OSR5 uses the IBM characters set by default. Try mapchan -n. If that
   cures the problem, comment out the appropriate line in
   /etc/rc.d/6/kinit - and make sure you make a note of this change so
   that you can remake it, if necessary, after a future upgrade.
   
   Bela Lubkin offered a slightly longer explanation:
   
   (as explained by Bela)
   SCO added a new alias for the console terminal emulation. The old one,
   "ansi", is still recognized. However, the new one, "scoansi", is used
   by default. There is no difference in the two terminal descriptions as
   long as your application uses the standard sources of terminal
   information: termcap (/etc/termcap) and terminfo
   (/usr/lib/terminfo/?/terminalname).
   However, many older applications are shipped with their own private
   terminal files. For instance, SCO FoxPlus comes with
   /usr/lib/foxplus/termcap. These private terminal descriptions are
   usually a superset of the normal information, plus other stuff that
   the application may use for its own purposes.
   Your problem is probably happening because your application provides
   its own termcap file with added information about line drawing. When
   the console terminal was called "ansi", the app looked up "ansi" in
   its private termcap and found out how to draw nice lines. Now that the
   console is called "scoansi", it looks that up and doesn't find it, so
   it falls back to the OS's public terminal description. That
   description actually *does* say how to draw nice boxes, but perhaps
   not in the same language that the application is expecting.
   Solution: the easiest one is to just call your console terminals
   "ansi". You can do that by editing the console entries in
   /etc/ttytype. Next easiest: find the app's private terminal database
   and teach it that "scoansi" is the same as "ansi".
   
   [Table of Contents]
     _________________________________________________________________
   
   sar doesn't work

   First off - did you run sar_enable? This is a new command in OSR5
   which sets everything up so that sar runs as it did previously. If sar
   isn't enabled, it simply won't run. Run /usr/lib/sa/sar_enable -y for
   starters. You will also need to edit root's and sys' crontab files if
   you wish data to be collected 24 hours a day, seven days a week. Also,
   if you wish to keep sar data for more than seven days, remove the
   'find' command in the last line of /usr/lib/sar/sa2.
   
   The file /etc/ps/booted.kernel gives the name of the booted kernel,
   and sar needs this to work properly. This file gets created each time
   the system is rebooted. In case it's messed up, try running kernel -uv
   and see if that cures it.
   
   There is another problem, though, which may not be cured by the above.
   There is a bug in the code in /boot. If the inode number of the kernel
   is greater than 32767, /boot improperly sign-extends it as a signed
   short integer rather than an unsigned one, and the end result is a
   completely wacky inode number. This should only happen on systems
   without a separate boot filesystem, which generally means those which
   were upgraded from an earlier release in place. The following is a
   patch to /boot which should cure the problem in 5.0.0; the TA from
   which it was derived (482688) states that this problem is for 5.0.0,
   but it also exists in 5.0.2. Be VERY careful, as always, applying
   patches; this one in particular may disable your system entirely if
   not done correctly.
   

   # cp -p /boot /boot.orig
   # what /boot
   /boot:
        SCO boot 23 Apr 95
   # sum -r /boot
   00357   134 /boot

   If either the results of what, or the results of sum -r, don't match
   exactly what you see above, stop! Do not apply this patch unless these
   are identical to the results you see.
   

   # echo 3f:feb?h 90 | _fst -w /boot -
   * 3f:feb?h 90
   0x3f:0xfeb:     0x99    =       0x90
   # sum -r /boot
   09082   134 boot

   Again, if the results of sum -r don't match exactly what you see,
   something did not work correctly. You should copy /boot.orig back to
   /boot.
   
   [Table of Contents]
     _________________________________________________________________
   
   My emergency floppies don't have enough inodes

   The simplest change to this is to edit /usr/lib/mkdev/fd and increase
   the number of inodes created from the default. This may cause
   problems, though, as HTFS inodes consume 128 bytes each and a
   significant increase in the number of inodes would result in a
   significant drop in the number of data blocks available on the floppy.
   
   A better change would be to eliminate unnecessary device nodes from
   your emergency floppy. Look for a line in /usr/lib/mkdev/fd which sets
   a variable called NOTREQ (which, roughly, is a list of device drivers
   not required on an emergency diskette). Add to that list
   merge mpm spm svdsp svkbd vdsp vkbd mouse
   If you don't need pseudottys on your emergency diskettes, you might
   also want to add spt mpt. There is also a bug in this file; change the
   item ptspwr to pts pwr (by adding a space), and you will cut out a few
   more unnecessary devices.
   
   When editing /usr/lib/mkdev/fd, you should actually make a new copy
   (e.g. /usr/lib/mkdev/fd.new) and edit, and later use, that rather than
   /usr/lib/mkdev/fd. Otherwise, you may find your changes vanish at some
   time in the future.
   
   [Table of Contents]
     _________________________________________________________________
   
   I'm having trouble with licensing and registration

   First off, you may have up to three difference license
   number/activation key combinations to use. Please read the
   documentation and the COLA (Certificate Of License and Authenticity)
   card(s) carefully. If you are upgrading from an old release of an SCO
   product, you will be asked not only to type in your new SNAK (Serial
   Number and Activation Key), but also the old SNAK from your old
   release. Additionally, if you are upgrading to the Enterprise system,
   you must first install and license the Host system, and then perform
   an upgrade to Enterprise.
   
   Licensing and registration is a two-step process. The first step
   involves licensing, and this takes place when you enter the SNAK from
   your COLA. You then fill in a form, included with your software, and
   send it to SCO in any of a number of ways. SCO sends you a
   registration key, which you enter to complete the registration
   process. The registration key is dependent both on your serial number
   and on a number generated by the system when you install it; this
   latter half means that should you have to reinstall, you will need to
   re-register your system.
   
   One big problem many people have had is that in the case of an
   Enterprise upgrade, you must register the Host system before you can
   register the Enterprise system. If you do not, then you may end up
   with a system which will appear to accept your registration but which
   will subsequently complain that it has not been registered, and there
   is no elegant way out of this situation; SCO recommends reinstalling
   to cure this. SCO is working on a cure for this but it is not ready
   yet and it will probably not be able to rescue systems which have
   already experienced this problem.
   
   If you need to do an upgrade or install and cannot wait for the
   registration information to be sent back to you, there is a procedure
   you can follow to avoid this problem. Install the Host system, and
   then install the Enterprise system. Send SCO the registration
   information for _both_ systems. When you receive your registration
   keys, perform the following steps:
   
    1. Take the system to single-user (maintenance) mode
    2. Remove the Enterprise license. This does not mean removing the
       software - just the license.
    3. Register the Host system license.
    4. Register the Enterprise system license.
    5. Shut the system down (haltsys) - do not bring it back up to
       multi-user mode without shutting down first
       
   If you find yourself unregistering/unlicensing parts of your system
   and you have a PANIC, it's possible that you may have upset the kernel
   streams linker module. Try booting with the boot string defbootstr
   ksl.disable; if that gets the system running, finish up your licensing
   and registration work and then reboot with your usual boot string.
   
   [Table of Contents]
     _________________________________________________________________
   
   sysadmsh is missing

   OSR5 includes sysadmsh, but it's not installed by default. If you wish
   to use it, you will need to use custom (or SCOAdmin Software) to
   install it.
   
   [Table of Contents]
     _________________________________________________________________
   
   Will Release 5 run my older binaries?

   In general, yes; binaries from previous versions of SCO Unix or SCO
   Xenix will run on OSR5. The exceptions tend to be those which probe
   system internals, where such internals may have changed, or those
   coded with certain assumptions (e.g. "an inode number is always a
   16-bit quantity") which are not necessarily true on OSR5. Examples
   include programs which read directories from disk rather than using OS
   directory access routines, or those which look for kernel structures
   and variables.
   
   [Table of Contents]
     _________________________________________________________________
   
   I loaded a patch but it didn't take effect

   Loading/unloading and applying patches only applies through 5.0.2-
   thanks to Dirk Hart for spotting this. 
   
   You probably forgot to apply it. Loading a patch places the contents
   of the patch on the hard drive, but does not activate the patch.
   Applying the patch does the necessary replacement of system files and
   whatever other adjustments are required to make the patch take effect.
   For more detailed information on the actual procedures, consult your
   manuals.
   
   You may wish to load a patch, but not apply it, for several reasons.
   Another machine on the network can apply a patch directly from your
   machine's hard drive if you've loaded the patch. Also, you may find
   that you will have to roll back several patches to replace or remove
   an earlier one, and then reapply the ones you rolled back; having
   loaded the patches first saves you from having to use the diskettes
   again.
   
   [Table of Contents]
     _________________________________________________________________
   
   What patches should I use?

   There is information in the file
   ftp://ftp.sco.com/README.OSR5.Supplements, including a list of
   currently applicable patches, and some quick summary information on
   which patches should not be used in conjunction with each other. For
   more detailed information, read the documentation files accompanying
   each specific patch.
   
   There's also a Web page,
   http://www.sco.com/support/toolbox/patch.html, with a minimum patch
   list.
   
   [Table of Contents]
     _________________________________________________________________
   
   What patches are on my system?

   To see which patches have been loaded, start SCOAdmin Software or
   custom and pick Software -> Patch Management -> View Loaded Patches
   
   Checking the list of patches which have been applied may be more of a
   problem; there is no simple way of doing this with SCOAdmin. You can
   pick Software -> Examine -> Applied Patches, and then pick each
   component in turn to see what patches have been applied to it. Yes,
   SCO is aware that this is a pain, so hopefully there will be a better
   way in a future release.
   
   If you are running OSR5.0.0 with the rs500d release supplement
   applied, or OSR5.0.2 or later, there is a command-line method,
   customquery listpatches, which will list what patches have been
   applied. This option to customquery did not exist prior to rs500d; if
   you do not have rs500d applied to your system, you should.
   
   [Table of Contents]
     _________________________________________________________________
   
   What's this free copy of SCO Unix I keep hearing about?

   On 19 August 1996, SCO announced that the single-user (desktop)
   configuration of OpenServer Release 5 would be available free of
   charge for noncommercial use. The package includes OSR5 Desktop, the
   development system (C/C++ compilers), SCO Doctor Lite, and SCO
   ARCserve/Open Lite.
   
   Since then, SCO has also released a free version of SCO UnixWare.
   
   For full details, including the license terms and on-line ordering
   information, see http://www.sco.com/offers/.
   
   [Table of Contents]
     _________________________________________________________________
   
   I'm having trouble using my ATAPI CD-ROM

   The two most common problems are that your "IDE" CD-ROM drive may not
   follow the ATAPI spec, or that you are unsure of what parameters to
   enter when asked for the configuration of your drive. Check the
   drive's documentation, or consult the manufacturer, for the first
   problem.
   
   The support for ATAPI CD-ROMs in OSR5 is done by using a driver which
   makes the drive appear to be a SCSI drive, and so you need to enter
   the same information as for a SCSI drive. The correct answers are as
   follows:
   
     * Host Adapter Number (HA): 0 if your drive is connected to your
       primary IDE host adapter, and 1 if it's connected to a secondary.
     * SCSI ID: 0 if your drive is a master, and 1 if it's a slave
     * Logical Unit Number (LUN): Always 0
     * Bus number: Always 0
       
   If all of these have been done correctly and the drive still does not
   work, try changing its configuration. If it's the master on the
   secondary host adapter, try making it a slave on the primary, or vice
   versa.
   
   Also, on some systems there is a conflict with the driver for the
   Western Digital/Future Domain 7000. If you don't have such a card, and
   your machine hangs at a line including wdhainit, boot with defbootstr
   disable=wdha to disable the wdha driver. There have also been reports
   of conflicts with the dptr and ncr drivers. For more information on
   disabling drivers, see the section entitled "My kernel locks up at
   boot time" in section 3.
   
   [Table of Contents]
     _________________________________________________________________
   
   My >2GB ATA hard drive doesn't work with OSR5

   See the documentation for oss451b to see if it applies to you. The two
   most commonly reported problems which are fixed by this patch are the
   system being unable to find the root filesystem, or aborting during
   installtion with a message similar to "NOTICE: ram: No space on device
   31/50", but there are other problems also fixed by it.
   
   [Table of Contents]
     _________________________________________________________________
   
   My floppy drive doesn't work reliably

   First things first - it may be a bad diskette, a bad floppy drive, or
   the cable connecting your floppy drive to its controller may be loose.
   
   However, if the problem gets worse if the system is under load
   (particularly, when anything is doing DMA - and that usually means a
   SCSI host adapter) and is particularly bad when trying to format a
   floppy, you may be running into a problem with the FIFO on the floppy
   controller.
   
   Briefly, older floppy controllers have a one-byte buffer, and the
   system must grab that byte before the next byte is read from the drive
   or else you have a problem. If the DMA controller (floppies use DMA)
   is blocked long enough, usually by a SCSI host adapter, the buffer
   gets overwritten. Newer controllers generally have a 16-byte buffer,
   but it may or may not be turned on by your BIOS. SCO Unix doesn't
   program the buffer by default, but the floppy driver in OSR5 can be
   set to use the buffer if you wish.
   
   Make a backup of /etc/conf/pack.d/fd/space.c (just in case). Now edit
   the file. At the bottom you will see
   
   int fd_enable_FIFO = 0;
   int fd_FIFOthresh = 0;

   Change them to
   
   int fd_enable_FIFO = 1;
   int fd_FIFOthresh = 15;

   The first one simply enables or disables programming of the FIFO; the
   second one sets the FIFO's size if you've enabled it. There's probably
   no reason to set it to anything other than 15.
   
   Relink and reboot to activate the change.
   
   Making this change can actually be counterproductive if your system is
   working properly. Some floppy drive controllers will not work properly
   if you try enabling the FIFO, and you will end up with a system with
   floppy drives which do not work. Trust me on this one.
   
   [Table of Contents]
     _________________________________________________________________
   
   People log out but still show up in who

   This information is logged in /etc/utmp and /etc/utmpx. In 5.0.4, this
   information is cleared when the system reboots. For earlier releases,
   edit /etc/bcheckrc as follows. You will see the first of the following
   three lines already there; add the other two below it.
   
   /bin/su bin -c "/etc/devnm / 2>/dev/null" | /etc/setmnt
   [ -w /etc/utmp ] && > /etc/utmp
   [ -w /etc/utmpx ] && > /etc/utmpx

   Also, "cwtmp" ftp://ftp.armory.com/pub/scobins/cwtmp is a freely
   available utility that clears stale logins.
   
   [Table of Contents]
     _________________________________________________________________
   
   Can I perform an in-place upgrade?

   If you already have your package, consult the documentation (in
   particular, installation guide and release notes).
   
  5.0.4
  
     * Can IPU from: 5.0.0 and 5.0.2
     * Cannot IPU from: Internet Faststart or ODT 3/Unix 3.2v4.2 or
       earlier
     * Caveats: If you IPU, you cannot install Internet Manager; you must
       do a fresh install if you ever want it.
       
  5.0.2
  
     * Can IPU from: ODT3/Unix 3.2v4.2
     * Cannot IPU from: 5.0.0, Internet Faststart, older Unix versions
       
  5.0.0
  
     * Can IPU from: ODT3/Unix 3.2v4.2
     * Cannot IPU from: Older Unix versions
       
   Note that if you are doing an in-place upgrade from ODT3/Unix 3.2v4.2
   to OSR5, you will not get a separate boot filesystem, and you cannot
   upgrade your root filesystem to HTFS.
   
   For an article that explains why you wouldn't do an IPU, see
   http://aplawrence.com/Unixart/upgrades.html.
   
   Bela Lubkin supplied the following chart; it's out of date and
   probably of little interest with regard to the older parts, but I've
   included it anyway:

   SCO Unix/Open Desktop/OpenServer release-to-release upgrade chart 97/10/07
   ================================================================= ========

  SCO Unix 3.2.0                 -IPU-> 3.2v2.0
  SCO Unix 3.2v2.0               -IPU-> 3.2v4.0
  SCO Unix 3.2v4.0               -SUP-> 3.2v4.1  (use MSv4.1)
  SCO Unix 3.2v4.0               -SUP-> 3.2v4.2  (use MSv4.2)
  SCO Unix 3.2v4.1               -SUP-> 3.2v4.2  (use MSv4.2)
 [SCO Unix 3.2v4.1 or earlier    ~N/A~> OpenServer Release 5.0.0 or later]
  SCO Unix 3.2v4.2               -IPU-> OpenServer Release 5.0.0
  SCO Unix 3.2v4.2               -IPU-> OpenServer Release 5.0.2
  SCO Open Desktop family 1.0    -IPU-> 1.1
  SCO Open Desktop family 1.1    -IPU-> 2.0
  SCO Open Desktop family 1.1    -IPU-> 3.0
  SCO Open Desktop family 2.0    -IPU-> 3.0
 [SCO Open Desktop family <= 2.0 ~N/A~> OpenServer Release 5.0.0 or later]
  SCO Open Desktop family 3.0    -IPU-> OpenServer Release 5.0.0
  SCO Open Desktop family 3.0    -IPU-> OpenServer Release 5.0.2
  SCO OpenServer Release 5.0.0   -IPU-> OpenServer Release 5.0.4
  SCO OpenServer Release 5.0.2   -IPU-> OpenServer Release 5.0.4
 [SCO OpenServer Release 5.0.x   ~N/A~> Internet FastStart 1.x.0]
  SCO Internet FastStart 1.0.0   -SUP-> 1.1.0  (use IFS 1.1.0 Supplement)
 [SCO Internet FastStart 1.x.0   ~N/A~> OpenServer Release 5.0.4]

   -IPU-> In-place upgrade possible (start full OS install of target
       release, by booting N1 or N00 floppy; it will prompt you whether
       you want to upgrade)

   -SUP-> In-place upgrade by installing supplement (named at end of line)

   ~N/A~> Upgrade not possible in a single step (may be possible via
       intermediate steps; but as in-place upgrades are always a little
       shaky, you probably don't want to compound then -- better to do
       fresh-install and migrate applications & data)

   "Open Desktop family" = Open Desktop, Open Desktop Lite, Open Desktop
       with Server Supplement, Open Server Network System, and/or Open
       Server Enterprise System (different titles available at
       different release levels).

   "OpenServer" = OpenServer Host, Desktop, Enterprise Systems.  A license
       is required to do an upgrade, and must be purchased for the
       specific upgrade path (e.g. SCO Unix 3.2v4.2 -> OpenServer Host
       System 5.0.2 would require a different license than SCO Unix
       3.2v4.2 -> OpenServer Enterprise System 5.0.2)

   >Bela<

   Jean-Pierre Radley reported that the 5.06 from 5.0.5 IPU was "almost
   to my liking".
   
   [Table of Contents]
     _________________________________________________________________
   
   How do I access online docs from a browser?

   Point your browser at port 457, and ask for document dochome.html. For
   example, if your server is server.foo.com, use the URL
   http://server.foo.com:457/dochome.html
   
   You don't have access to the search tools this way, but you can
   simulate that with the following cgi-bin script.
                    ___________________________________
   
   #!/bin/sh
   # @(#) nftpsearch - wrapper for simple form access to scohelp search engine
   # call without QUERY_STRING set html form, with QUERY_STRING for search
   # relies on single Form search field called query
   #
   # Install as:  /var/scohttp/cgi-bin/nftsearch.sh  on OSR5.0.[024] systems.
   # Access via:  URL:<http://localhost:457/cgi-bin/nftsearch.sh> (any browser)

   if [ -z "$QUERY_STRING" ] ; then

   HELP_SVR="http://localhost:457"            # YOUR HELP SERVER system
   SCRIPT="$HELP_SVR/cgi-bin/nftsearch.sh"    # cgi-bin path of this script

   cat <<EOF
    <HEAD>
    <TITLE> ScoHelp Search </TITLE>
    <LINK REV="made" HREF="mailto:hops@sco.com">
    </HEAD>

    <BODY BGCOLOR="#FFFFF0" TEXT="#000000">
    <H1>ScoHelp Search </H1>

    For scohelp searching from a non ScoHelp Browser <BR>
    <HR>
    <STRONG>Enter single word search term in search field Below</STRONG>
    <P>
    <FORM METHOD=GET ACTION=$SCRIPT>
    <INPUT NAME="query" SIZE=30>
    <INPUT TYPE="submit" VALUE="Search">
    <INPUT TYPE="reset" VALUE="Clear">
    </FORM>
    <HR>

    <A HREF="$HELP_SVR/dochome.html">ScoHelp DocHome </A>

    </BODY>
    </HTML>
   EOF

   exit 0
   fi


   eval $QUERY_STRING
   QUERY_STRING=$query
   export QUERY_STRING

   PATH_TRANSLATED=/usr/lib/scohelp/library.stz
   PATH_INFO=/library.stz

   export QUERY_STRING PATH_TRANSLATED PATH_INFO

   #export  GATEWAY_INTERFACE HTTP_ACCEPT HTTP_CONNECTION HTTP_HOST
   #export HTTP_REFERER HTTP_USER_AGENT PATH REMOTE_ADDR REMOTE_HOST REQUEST_METHO
   D
   #export SCRIPT_NAME SERVER_NAME SERVER_PORT SERVER_PROTOCOL SERVER_SOFTWARE

   exec /var/scohttp/cgi-bin/ftsearch
                    ___________________________________
   
   [Table of Contents]
     _________________________________________________________________
   
   Can I use the scohelp server as a Web server?

   Yes, although you'd probably be wiser to consider something like
   Apache (http://www.apache.org/; it's also available as part of
   Skunkware). If you wish to use the scohelp server, follow the
   instructions in TA 482609 or at
   http://www.sco.com/Technology/internet/servers/scohttp80.html.
   
   [Table of Contents]
     _________________________________________________________________
   
   Is there a packet sniffer (tcpdump) available?

   A collection of network tools, including the tcpdump packet sniffer,
   can be found at http://www.sco.com/skunkware/osr5/net/nettools/. Pay
   particular attention to the requirements mentioned in the README file.
   For example, you will need a dedicated NIC to make this work.
   
   [Table of Contents]
     _________________________________________________________________
   
   What can I do about function keys not working?

   A new "recon" command in Open Server 5.0.6 can help solve the problem
   of escape sequences (function keys, line drawing characters, etc.)
   getting messed up because of timing issues- what happens is that the
   application gets confused if the sequences don't arrive together. The
   "recon" command watches for escape sequence and buffers them until
   they are complete, then sends them along. See
   http://osr5doc.sco.com:457/cgi-bin/man/man?recon+C
   
   [Table of Contents]
     _________________________________________________________________
   
   Can I have both IDE and SCSI Drives?

   Mixing SCSI and IDE drives can be a problem if you want the root disk
   to be scsi. The short answer is that you can if your BIOS lets you
   select which drive to boot (if not, you would have to boot from a
   floppy). Assuming everything else is in place, "defbootstr hd=Sdsk"
   should work. See SCSI for a full discussion of this.
   
   [Table of Contents]
     _________________________________________________________________
   
   Is there a DHCP client for OSR5?

   SCO doesn't currently have a DHCP client for OSR5 (modern releases do
   have a DHCP server) built in, but it's available as TLS711
   ftp://ftp.sco.com/TLS/tls711.tar.Z
   
   [Table of Contents]
     _________________________________________________________________
   
   Can OSR5 do NAT or ip filtering (function as a firewall)?

   Yes, with "ipfilter"- it's built into 5.0.6 and is available as a
   supplement for 5.0.4 and 5.0.5- TLS709 ftp://ftp.sco.com/TLS/. But
   note this Sept 14 2000 post from Kamal Mostafa:
   
   The 'ip' driver included in TLS709 needs the routine bcmp(), which
   didn't appear in the kernel until 5.0.4. After I discovered this
   problem, I fixed the 'ip' driver so that it no longer needs bcmp(). So
   the latest version of the 'ip' driver (e.g. from a 5.0.6 system) will
   work on 5.0.x systems. Eventually, I will update TLS709 with the newer
   version. In the meantime, replace the /etc/conf/pack.d/ip/Driver.o
   that TLS709 put there with a newer version. If anyone else is getting
   this problem, you can either lift the 'ip' driver from a 5.0.6 system,
   or contact me directly and I'll email you a replacement binary as
   well. Kamal A. Mostafa SCO Engineering
   
   Kamal has given me permission to put this driver on my ftp site; you
   can download it from ftp://ftp.aplawrence.com/pub/ip-Driver.o. Copy it
   to /etc/conf/pack.d/ip/Driver.o and relink your kernel (make a safe
   copy of your ip/Driver.o first).
   
   You'll also need netstat: ftp://ftp.aplawrence.com/pub/netstat. Copy
   that to /usr/bin and

   chown bin:mem /usr/bin/netstat
   chmod 2711 /usr/bin/netstat

   Again, be sure to save a copy of your original netstat!
   
   See also IPFILTER firewalls for OSR5
   http://aplawrence.com/Security/ipfilter.html, ip sharing ipnat
   ipfilter
   
   [Table of Contents]
     _________________________________________________________________
   
   How can I find my Activation Key?

   On modern releases, look in /var/adm/ISL/iqm_file.
   
   [Table of Contents]
     _________________________________________________________________
   
   Can OSR5 and Unixware run Linux binaries?

   Yes. The "lxrun" may already be installed; if not, get it from
   Skunkware.
   
   [Table of Contents]
     _________________________________________________________________
   
   Can Linux run OSR5 binaries?

   Generally, yes. It requires the ibcs2 module. Aside from library
   problems, you are apt to find directory structure problems (usually
   easy enough to fix with symbolic links) and, if the application calls
   OS commands, you may need to make appropriate links for some of those,
   too.
   
   [Table of Contents]
     _________________________________________________________________
   
   A Xenix or ODT application corrupts the screen

   Try
   oldapp | cat -
   or
   oldapp | tee /dev/null

   See also the "mapchan" entry above.
   
   [Table of Contents]
     _________________________________________________________________
   
   How can I recreate my install floppy?

   The floppy image is available on the CDROM in the "images" directory.
   A "readme" file is also there that explains how to create the floppy.
   
   [Table of Contents]
     _________________________________________________________________
   
   I've added more ram, do I need to increase swap?

   Not necessarily. There is a detailed discussion of this at
   http://aplawrence.com/Boot/swap.html, but the main points are:
     * If you have enough RAM, you don't need ANY swap.
     * However, if you are concerned with saving panic dump information,
       you WILL need sufficient dump space.
     * You can add swap space without resizing divisions by using the
       "swap" command to swap to a file; see "man swap" and :
       
     How much swap space do I need?
   
     Can I add more swap space?
   
   [Table of Contents]
     _________________________________________________________________
   
   Why do I get "dynamic linker" errors or load failures?

   If you get an error like the following.
   dynamic linker: svrmgrl: error opening libprogram.so
   Killed

   install_driver(program) failed: Can't load

   PERL_MODULE::program: dynamic linker: perl: relocation error: symbol not
   found: getrusage at....

   These messages all mean that you do not or have not setup
   LD_LIBRARY_PATH variable or Your Program isn't setting up
   LD_LIBRARY_PATH correctly, or your install of the program was faulty.
   
   This can be solved by adding the shell variable LD_LIBRARY_PATH or
   LIBPATH with the proper search path. For example if you are using
   bourne or korn shell

   LD_LIBRARY_PATH=/usr/lib:/lib:/usr/local/lib:/usr/ccs/lib:/usr/local/mysql/lib:
   /usr/local/BerkeleyDB.3.1/lib
   LIBPATH=/usr/lib:/lib:/usr/local/lib:/usr/ccs/lib:
   export LD_LIBRARY_PATH LIBPATH

   From the man page on ld:
   LD_LIBRARY_PATH is also used to specify library search directories to the
   dynamic linker at run time. That is, if LD_LIBRARY_PATH exists in the
   environment, the dynamic linker will search the directories it names
   before its default directory for shared objects to be linked with the program
   at execution.

   --
   Boyd Gerber
   ZENEZ   3748 Valley Forge Road, Magna Utah  84044
   Office 801-250-0795 FAX 801-250-7975

   Thanks to: Boyd Lynn Gerber 
   
   [Table of Contents]
     _________________________________________________________________
   
   Why do I get "cronsched: no response from server" messages ?

   This is related to the Calendar server- see "man calendar" and "man
   scocalendar". Usually this means that something is broken, so if you
   aren't using calendar, and therefor don't care that it is broken, you
   can just comment out the "cronsched" entries from root's crontab.
   
   If you do care, see http://www.sco.com/cgi-bin/ssl_reference?102995.
   
   [Table of Contents]
     _________________________________________________________________
   
   How do I change the system's name or IP address?

   Start by running "netconfig". But, you may have a lot more work to do:
   see http://aplawrence.com/Jeffl/new_name.html
   
   [Table of Contents]
     _________________________________________________________________
   
   What does "ifor_pmd, failed to initialize policy manager" mean?

   The license manager is failing for some reason. There are a number of
   reasons why that could be, including having an incorrect date in your
   computer's BIOS or simply not having a /pmd directory. See
   http://www.sco.com/cgi-bin/ssl_reference?104851 for more detailed
   reasons and fixes.
   
   [Table of Contents]
     _________________________________________________________________
   
   What causes "No utmp entry, must login from lowest level shell"

   Probably corruption in one of the log files /etc/utmp, /etc/wtmp,
   /etc/utmpx, or /etc/wtmpx. You can zero them out by:

   > /etc/utmp
   > /etc/utmpx
   > /etc/wtmp
   > /etc/wtmpx

   and then rebooting. i
   
   Robert Bailin says that he's seen the corruption caused by
   /etc/cleanup being run by cron; see I need information from "last",
   but most of it is gone!
   
   [Table of Contents]
     _________________________________________________________________
   
   What is the procedure for performing replicated OS5 installs ?

   http://www.sco.com/cgi-bin/ssl_reference?105212
   
   Roberto Zini
   
   [Table of Contents]
     _________________________________________________________________
   
   Does SCO OpenServer5 support the 'undelete' feature?

   Yes, it does but unfortunately it's not active by default (see the
   online manual pages for details). To activate it: pre> - scoadmin ->
   Hardware/Kernel Manager - MAXVDEPTH = max number of versioned files -
   MINVTIME = seconds after which files get versioned relink+reboot To
   activate file versioning on a directory: - undelete -s
   
   Roberto Zini
   
   [Table of Contents]
     _________________________________________________________________
   
   Why do I have to relink after just changing an ip address?

   The kernel knows its own ip address, even in single user mode where
   TCP/IP is obviously not running. A machine in init state 1 will still
   respond to pings, for example.
   
   So you'd think perhaps that's why you need to relink, but a little
   experimentation shows that even without relinking, a single user
   machine still responds to the address put in with netconfig.
   
   Apparently, then, there is no reason to relink if you are just
   changing IP addresses- it works fine without it.
   
   [Table of Contents]
     _________________________________________________________________
   
   Why does the installation bomb out with a "Signal 8" error ?

   Contributed by Roberto Zini
   
   Under SCO OpenServer 5.0.5 this is mainly a symptom of a memory
   problem. In the "SCO OpenServer 5.0.5 Release Notes" booklet, SCO
   states that your system must have at least 32MB of RAM to succesfully
   install OpenServer. If you have less, the following message is likely
   to appear on the screen:
   
 Reading from install source 10 Kb/ramFs/extractProd/extractAll
 terminated by signal 8


   To solve this problem on a 16MB system, you can restart the
   installation and type the "notebook" strings while at the boot prompt.
   Alternatively, reinstall the system by typing the following at the
   boot prompt:
   
 defbootstr nbuf=100


   [Table of Contents]
     _________________________________________________________________
   
   How Can I stop OpenServer 5.0.6 creating /usr/local as a sym-link?

   a) 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.
   
   b) 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
   
      /var/opt/K/SCO/Unix/5.0.6Ga/.softmgmt/RTS.fl


   The line is:

       EXPORT r ./usr/local /usr/local



   You can use a script similar to:
 ----- Cut Here ---------
 DIR=/var/opt/K/SCO/Unix/5.0.6Ga/.softmgmt
 FILE=RTS.fl
 sed -e 's/^EXPORT r .*local$/#&/' < ${DIR}/${FILE} >${DIR}/$$
 mv ${DIR}/$$ ${DIR}/${FILE}
 ----- Cut Here ---------


   to do it for you.
   
   Contributed by Tom Melvin
   tom@bdsl.com
   http://www.tkrh.demon.co.uk
   
   [Table of Contents]
     _________________________________________________________________
   
   Is it possible to have more than one instance of custom running ?

   John Boland posted the following a while ago (please change the
   reference to SCO OS 5.0.2 (5.0.2Dp) with the one related to the 5.0.x
   version you're using) :

 === cut here ===

 The lock file is:

 /var/opt/K/SCO/Unix/5.0.2Dp/custom/client.lock

 Move this file aside and you can run as many Software Managers (custom)
 as you like.

 === cut here ===


   Contributed by Roberto Zini
   
   [Table of Contents]
     _________________________________________________________________
   
   How can I access the documentation on the install CD if I don't yet have a SCO
   system installed?

   The install CD can be read from a Windows machine, and the
   documentation is in html format. There are also Windows tools included
   to make boot disks etc.
   
   [Table of Contents]
     _________________________________________________________________
   
   I need information from "last", but most of it is gone!

   The default root crontab cleans out /usr/adm/sulog, /etc/wtmp and
   /etc/wtmpx on Sunday mornings. The script that does this is
   /etc/cleanup.
   
   If your machine is used at the time this script is run, you will want
   to change the time in crontab. If you want more than 1 week's
   information in these files, you need to change its frequency or take
   it out all together.
   
   [Table of Contents]
     _________________________________________________________________
   
   How can I assign a user process to a specific pseudo tty?

   A new "recon" command in OpenServer 5.0.6 allows this. See
   http://osr5doc.sco.com:457/cgi-bin/man/man?recon+C
   
   [Table of Contents]
     _________________________________________________________________
   
   How can I get pci bus information?

   First, you probably don't need to. This usually comes up because a
   network card isn't working and you think that you must have the wrong
   pci information. More likely, you just don't have the most current
   driver- for example, Intel Pro100 cards are very apt to need a new
   driver(check ftp://ftp.sco.com/pub/drivers ).
   
   However, if you really do need this information "hw -r pci" will tell
   you everything you need to know and more. The "hw" command was not
   included with 5.00 and 5.0.2, but can be obtained from ftp.jpr.com. It
   will also work on 3.2v4.2. 
   
   [Table of Contents]
     _________________________________________________________________
   
   Why do I get "can't find user in protected password database" in syslog?

   These simply mean that someone telneted to the box and logged in
   incorrectly.
   
   [Table of Contents]
     _________________________________________________________________
   
   Why doesn't "man" work?

   Possibly the scohttp server is not running. Try
 /etc/scohttp stop
 /etc/scohttp start


   [Table of Contents]
     _________________________________________________________________
   
   I upgraded Merge and now cannot access my floppy drive

   David Peet explains:
   
   New to Merge 4.1.1 for OpenServer, the floppy is now accessed in the
   same way as it is on Merge for Unixware (via the UNIX floppy driver)
   instead of "direct attached" as it had been done. This change is
   because on faster machines the direct attach of the floppy often has
   problems because of timing.
   
   For a Win95 that was installed when direct attach floppy was being
   used, the registry needs to be updated so that Windows can use the new
   accesss method.
   
   The problem is that Merge is supposed to update your existing Windows
   registry when you upgrade to 4.1.1, and this update must have failed
   insome way. (Any new installation of Windows after the upgrade will
   not have the problem. It is only an issue of changing the hardware
   setup for an existing Windows installation.)
   
   What is supposed to happen is that the program
    /usr/lib/merge/bin/upgrade_flop.sh


   is supposed to be run the first time you use Merge after upgrading.
   This is supposed to update the registry.
   
   Either this did not get run automatically or it failed someway. You
   can retry this by running it. Just running it (with no parameters)
   will upgrade your regular Windows installation as specified by your
   "win" personal configuration. If you have other personal windows95
   configurations, you need to run this script for each one, using as a
   parameter the name of the configuration.
   
   If this does not work you have two choices:
    1. Reinstall Windows so the new installation will work with the new
       floppy access method.
    2. Change Merge to use direct attach floppy access so old
       installations of Windows will work as is.
          + Change the MERGE_DIRECT_FLOPPY_ENABLE switch in
            /etc/default/merge from off to on.
          + Edit /etc/conf/pack.d/merge/space.c and change the value of
            _M_direct_attach_floppy from 0 to 1 and rebuild a kernel
            (/etc/conf/cf.d/link_unix -y) and then reboot.
       
   [Table of Contents]
     _________________________________________________________________
     _________________________________________________________________

User Contributions:

Comment about this article, ask questions, or add new information about this topic:

CAPTCHA




Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
apl@world.std.com (Tony Lawrence)





Last Update March 27 2014 @ 02:12 PM