******************************************************************************
1) IBM R/6000 users wishing to upgrade to OS 3.1.7 should know that there
are problems with UUCP:

> Are you running 3.1.7 of the OS, or 3.1.5? What is the nature of problems
> with UUCP?
> 
> Thanks,
> Tasos
> 
	3.1.7 is the version I'm on under the AIX.  When I refer to 2007,
it breaks down as :

			2 - Update to most current previous version
			00 - ???
			7 - New version number.

When you refer to a 3005 tape, it means

			3 - Replacement for a previous version, totally.
			00 - ???
			5 - New version number.

So, when I went from 3.1.0 to 3.1.5, I got a 3005 tape.  When I went from
3.1.5 to 3.1.6 I got a 2006 tape, and from 3.1.6 to 3.1.7 I got a 2007
tape.  When they come out with 3.2, it'll probably be a 2010 tape.  Also,
you can not go from 3.1.5 to 3.1.7 with a 2007 tape, you MUST be on the 
x-1 gen (3.1.6).  The problems are that it does not spawn the polling 
processes in /usr/spool/cron/crontabs/uucp.

******************************************************************************
2) Systems running under AIX 3.1.7 have yet another problem with cron. This
can be fixed by APAR #a21036

******************************************************************************
3) "BTW: PLEASE inform whoever runs the AIX
that you use to do debug work there that he MAY have gotten SCSI update
code on disk recently, and NOT to install it!  There is a good chance his
system won't come back up."

******************************************************************************
4) Problems migrating from SUN OS 4.1.1 to SUN OS 4.1.2:
Got it.  The problem is on SunOs 4.1.2.  I had rebuilt libc.so so the
machine could be a resolver w/out needing to run DNS and only needing
resolv.conf and a route to the gateway.  Anyway, If one does this
(or a few other things as well) ld gets sick like I described before.

The answer is to get a jumbo patch from Sun support.  The patch reference
is: 100532 (International) or 100531 (Security).  It also corrects the
Makefile in /usr/lib/shlib.etc by putting a -ldl switch on ld.
This switch can probably be used in other makes as a possible
workaround.  I'll try it tomorrow.
******************************************************************************
5) Article 15006 (36 more) in comp.unix.aix:
From: lubkt@synergy.CC.Lehigh.EDU (Binod Taterway)
Subject: C routine realloc() seems broken in AIX 3.2.2...
Message-ID: <LUBKT.92Aug17113728@synergy.CC.Lehigh.EDU>
Date: 17 Aug 92 16:37:28 GMT
Sender: usenet@chili.cc.lehigh.edu
Distribution: comp.unix.aix
Organization: Lehigh University, Bethlehem, PA
Lines: 16
Nntp-Posting-Host: synergy.cc.lehigh.edu


FYI -

AIX 3.2.2 has broken all my realloc() calls. The code that worked on
AIX 3.1.8 (and all previous releases) now gives core dump after I
upgraded AIX. I get -

        Catastrophe in realloc: invalid storage ptr
        IOT/Abort trap(coredump)

******************************************************************************
6) malloc() under 3.2 may cause bur errors:

From the malloc man page:

Note:   AIX Version 3.2 allocates memory using a different method than in
previous releases.  Some applications may fail due to this new method.
Therefore, AIX Version 3.2 supports both the old and new memory
management strategies.  The MALLOCTYPE environment variable can be set
to access the older version.  To use the old memory allocation method
instead of the new, enter:

MALLOCTYPE=3.1; export MALLOCTYPE
setenv MALLOCTYPE 3.1

