My original question was:
On Digital UNIX 3.2C /usr/bin/ksh is 136 MB
On Digital UNIX 4.0B /usr/bin/ksh is 132 MB.
Some on my scripts that calls subscripts within the main scripts would
not work with korn shell provided with 4.0B, the temporary workaround
was to copy ksh from 3.2C system.
My recommendation: If you are planning upgrade to 4.0B, save your 3.2C
or 3.2G korn shell --you will need it.
I have logged a call with Digital regarding this problem. I will
update you when I hear from them.
I would like to hear if anyone else ran into this problem.
----------------------------------------------------------------------
I got many replies stating that they have similar type of problem.
Digital Support ask me to reproduce the problem in a smaller script
and ship the code so they can diagnose it further.
Thanks to Richard L Jackson Jr <rjackson_at_gmu.edu> for being one step
ahead of Digital and pointing out the following patch, which sounds
like going to fix the broken korn shell shipped with Digital UNIX 4.0B
I also informed Digital Software Support about existance of this patch
so in future they can provide quick resolution to other customer
having similar problem with korn shell on 4.0B.
Thanks,
Ronny
The Walt Disney Company
Disney Studios, Burbank California
======================= << START OF PATCH >>=========================
New PatchID: 98.00
PATCH ID: OSF410-057 SUBSET(s): OSFBASE410
*********************************************************************
SUPERSEDED PATCHES: OSF410-400118 (17.00), OSF410-400169 (54.00)
PROBLEM: (UVO104297) (Patch ID: OSF410-400118) ********
This patch fixes a problem that occurs when using the Korn shell
(ksh).
Keyboard input is not echoed when a user exits via a trap, after
editor options have been set in ksh.
To restore the tty modes, enter the following command:
<newline> stty sane <newline>
To reproduce the problem execute the following:
/usr/bin/ksh
/usr/bin/ksh
set -o emacs
touch /tmp/foo
trap 'rm -f /tmp/foo' EXIT
TMOUT=1
Now wait 60 seconds. When ksh exits, the keyboard should echo
characters. If it does not, then this bug has occurred.
PROBLEM: (QAR 50297) (Patch ID: OSF410-400169) ********
The ksh shell program prevents a command, which runs in a sub-process,
from writing to a tape device.
For example:
$ /usr/bin/ksh -c "/bin/echo foo | /bin/cat > /dev/rmt0h"
/usr/bin/ksh: /dev/rmt0h: cannot create
PROBLEM: (QAR 51086) (Patch ID: OSF410-057) ********
Set old-obreak = 0 breaks ksh will be fixed by this patch.
FILE(s):
/usr/bin/ksh subset OSFBASE410 CHECKSUM: 39000 264
/usr/bin/posix/sh subset OSFBASE410 CHECKSUM: 12456 264
-----------------------------------------------------------------
Received on Fri Jun 20 1997 - 23:10:33 NZST