Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!ames!ucbcad!ucbvax!ucbarpa.Berkeley.EDU!jordan
From: jordan@ucbarpa.Berkeley.EDU.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Bringing up 4.3BSD, a half-step at a time
Message-ID: <17058@ucbvax.BERKELEY.EDU>
Date: Mon, 26-Jan-87 19:27:38 EST
Article-I.D.: ucbvax.17058
Posted: Mon Jan 26 19:27:38 1987
Date-Received: Tue, 27-Jan-87 06:30:03 EST
References: <864@sdcc7.ucsd.EDU>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: jordan@ucbarpa.Berkeley.EDU (Jordan Hayes)
Organization: University of California, Berkeley
Lines: 23

Keith Muller <muller@sdcc7.ucsd.EDU> writes:

	One trick I tired and it worked was I used 4.3 rdist to upgrade
	4.2 machines.  I moved rdist to the 4.2 machine, made a kernel
	for the 4.2 machine on the 4.3 machine moved the kernel to the
	4.2 machine and let rdist fix the binaries for the 4.2
	machine.  (I just made sure that /etc was the LAST thing rdist
	updated).

Two things:

	1) The original poster was working from *no* 4.3 machines, so
	   although this is nice for propagating 4.3 around the net, it
	   doesn't solve his problem of getting it up from the tape.

	2) I have had no problems with rdist'ing /etc first, rebooting
	   and then bringing over the rest ... my big problem (the first
	   time ... *sigh*) was that I rdist'ed /bin/csh which doesn't
	   run too well under 4.2 which rdist needed ... luckilly, the
	   4.2 csh works under 4.3, so do /etc first (so the network will
	   come up correctly after the reboot, and then get the rest.

/jordan