From owner-freebsd-stable  Thu Oct 23 14:51:49 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA00371
          for stable-outgoing; Thu, 23 Oct 1997 14:51:49 -0700 (PDT)
          (envelope-from owner-freebsd-stable)
Received: from eyelab.psy.msu.edu (eyelab.psy.msu.edu [35.8.64.179])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA00362
          for <freebsd-stable@freebsd.org>; Thu, 23 Oct 1997 14:51:44 -0700 (PDT)
          (envelope-from root@eyelab.psy.msu.edu)
Received: from eyelab3.psy.msu.edu (eyelab3.psy.msu.edu [35.8.64.180])
	by eyelab.psy.msu.edu (8.8.6/8.8.5) with SMTP id SAA26861
	for <freebsd-stable@freebsd.org>; Thu, 23 Oct 1997 18:45:03 -0400 (EDT)
Message-Id: <199710232245.SAA26861@eyelab.psy.msu.edu>
X-Sender: root@eyelab.msu.edu
X-Mailer: QUALCOMM Windows Eudora Pro 4.0 Beta 1 (build 175)
Date: Thu, 23 Oct 1997 17:48:04 -0400
To: freebsd-stable@freebsd.org
From: Gary Schrock <root@eyelab.psy.msu.edu>
Subject: upgrading from 2.1-stable to 2.2-stable remotely?
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Is there any good way of upgrading a system from 2.1-stable to 2.2-stable
when you don't have console access to the machine?  I've got a machine that
would definitely see some benefits in upgrading, but which I don't really
have access to (the machine's in california, I'm in michigan), and unless
we want to pay someone on site exorbiant fees to do the upgrade for us it
would be difficult to do unless it was done remotely.

Any thoughts?
Gary Schrock
root@eyelab.msu.edu