Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!haven!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: comp.sys.next
Subject: Re: Upgrade problem
Message-ID: <1990Dec25.142157.2465@ni.umd.edu>
Date: 25 Dec 90 14:21:57 GMT
References: <4927@idunno.Princeton.EDU> <1990Dec22.064311.29759@agate.berkeley.edu>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland, College Park
Lines: 26

In article <1990Dec22.064311.29759@agate.berkeley.edu> izumi@fugitive.berkeley.edu (Izumi Ohzawa) writes:

>Oh, no!  I was afraid of this, since I am in the same boat.
>You mean, they wrote this nice Upgrade2.0.app and it allows
>you to upgrade only from release 1.0 or 1.0a, but not from
>beta versions of 2.0?

This is the price you pay for beta testing software.  I suppose that
if you wanted turnkey operation, you should wait for the released
versions of the software.  I'm just pleased that the two beta releases
of 2.0 that I tested didn't hose the disk, and actually worked; never
mind how easy it is to upgrade.

On that that I found was that you could invoke the shell script that
BuildDisk invokes manually in such a was that I didn't format the
entire disk.  I have a 660MB drive in my machine, with all the "user"
files that need to be preserved on the /clients partition.  By
invoking the script manually, it just rebuilt the root partition, and
left the other one alone.  Look at /usr/etc/builddisk.

You have to make sure that you preseve your /private directory to
recover aliases, printcap, NetInfo, sendmail.cf and other files.

*Still* waiting for my NeXTstation to arrive...

louie