Aborted 3.0 upgrade...

Thread View: comp.sys.next.sysadmin

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Michael O'Henly Thu, 17 Dec 1992 17:54

#2153

Author: Michael O'Henly
Date: Thu, 17 Dec 1992 17:54

31 lines
1729 bytes

    Yesterday, I upgraded our '040 Turbo from 2.2 to 3.0 using a Mac
CD-ROM and the "automatic" upgrade method. 

    Things appeared to work as they should until the very end. Then
the install said it was running a "postprocessing script" and went off
into hyperspace for a couple of hours. 

    I had a spinning cursor at this point, so I wasn't able to click
on the "stop" button. When it became clear that this script was going
run until the end of time (or until NeXT delivers my back-ordered
CD-ROM drive -- whichever comes first), I tried killing the process
and finally just rebooted the system.

    It came up in 3.0 without any obvious ill effects. But I am
concerned that the "postprocessing script" was working on something
when I aborted and that there may be things I should take care of.
I'd be prepared to run the whole thing again, but the upgrade app
tells me that it should only be run on 2.x disks.

    Should I be concerned about this? Is there a way to rerun the
upgrade?

    Michael


    
-- 
           Michael O'Henly |     o   | 604-721-7623 (604-721-8215 fax)
    Library Systems Office |  --/--  | LUX@UVVM.BITNET
    University of Victoria |  __\    | lux@sol.UVic.CA
    Victoria, B.C., Canada |     \   | mohenly@malahat.Library.UVic.CA

Re: Aborted 3.0 upgrade...

#2156

Author: Larry Shupe
Date: Thu, 17 Dec 1992 20:44

29 lines
1771 bytes

In article <lux.724614890@sol.UVic.CA> lux@sol.UVic.CA (Michael O'Henly)  
writes:
>    Yesterday, I upgraded our '040 Turbo from 2.2 to 3.0 using a Mac
>CD-ROM and the "automatic" upgrade method. 
>
>    Things appeared to work as they should until the very end. Then
>the install said it was running a "postprocessing script" and went off
>into hyperspace for a couple of hours. 
>
> [The rest deleted for brevity]

The same thing happened to me on all three of our NeXTs.
The computer hung during the postprocessing script while
trying to add a net-info property.  Killing the subprocess
(the one trying to create the property) allowed the 3.0
installation to finish.  I haven't had any problems in the
last few months so I assume that the property either was
added correcty or isn't all that important.

I called NeXT about this but they had no clue.  They suggested
running the installation again, but the same thing happened.
I think it may have something to do with having modified
the net-info printcap stuff on each machine to allow remote
access to my NeXT printer in the generic unix manner.  NeXT
changed the format of some of the net-info printer information
and there may have been an incompatibility with one of my
modifications.
--
Larry Shupe

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads