Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!safn2!rey From: rey@safn2.UUCP (rey) Newsgroups: comp.sys.ncr Subject: Summary - migration of Tower 32/450 from NCR Unix 2.01.01 to 3.00.01. Keywords: migrate Message-ID: <959@safn2.UUCP> Date: 13 Feb 91 19:50:12 GMT Organization: Southern Aluminum Finishing, Atlanta, GA Lines: 108 A few months ago I asked the group for comments regarding migration of our NCR 32/450 from NCR Unix 2.01.01 to 3.00.01. I only got 2 responses - Both negative. One person had had difficulty because the data base he was using would not work on the new release. The other person was dissappointed with the compiler speed and really saw no advantages to the 3.00.01 for his system. Just a lot of work to migrate the system. Thanks to those who responded. Their cautions were heeded. I needed to install a larger disk; and really wanted the latest and greatest, so I proceeded in spite of the cautions of others. I got a unify upgrade 4.0 from Unify Corp. I ordered a new Uniplex (It never arrived). Century Software said TERM should migrate OK. Uniplex is office automation - spreadsheets and wordprocessing. Term is communications - calling mci and compuserve. Unify is database. The plan was to do it over a weekend. NCR field eng installed the new 380MB Wren IV (I got from SeaChange ) at 16:00 Fri. On Sat AM I started installation. First event of note was that the drive came up sdb1 not sda1. Second internal SCSI disk, not first. /dev/rdsk/42s0 not /dev/rdsk/38s0. I guess SeaChange jumpered the drive as a second disc and the FE did not know to change it. I decided this would not hurt anything, and I could link 42s? to 38s? if I needed to. A big concern was lpr to lp conversion. I did this in Jan on release 2, so it would not be a migration issue. Good decision! Try finding every print command on your system sometime. Another concern was the 5 yrs of menu.o shell scripts we had written, (The rel 3 uses VSAD menu system) would all have to be rewritten. I had no way of knowing until I got rel 3 up. I was never able to formulate the question in a way CODAR could understand. All I could get out of CODAR was that "all applications must be reinstalled". They did put me on to the VSAD tutorial (ST-2114-35) which said it would be on the system 3.00.00. It was not there. We have set up a menustart script in /etc/passwd that calls /menu/obj/menu.o. We migrated menustart.o from rel 2; it did not work. All the $HOME/appl stuff had migrated from my cpio from the old system. The rel 2 menu should be addressed in the migration info. It is not. The manuals say that if you tic the supplied .ti files in /usr/lib/terminfo the va (sysadm) system is guaranteed not to work. I set up my .ti files in /usr/lib/terminfo/local prior to migration, and set TERMINFO=/usr/lib/terminfo/local in profile. Somehow I managed to tic the files in local without TERMINFO being set. So I wrote over the supplied files. I was able to find a file from some of the non-local emulations that were not in terminfo/local and thus had not been overwritten. I need to restore this from the release tape sometime. I think this va stuff is really bad if tic is guaranteed to destroy your system. libcurses and .ti files that work should be supplied. Unify 4.0 worked fine; but all c progs had to be reloaded. I recompiled all unify c, just for good measure. Uniplex I am not sure about yet; whatever I am running is unsupported, since I never got an update. Term (Century) does not want to coexist with uucp. This worked fine on rel 2. Term works OK; but after it is thru with a tty; it cannot be opened (stty -a