From owner-freebsd-stable Thu Oct 23 15:46:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA03592 for stable-outgoing; Thu, 23 Oct 1997 15:46:51 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from andrsn.stanford.edu (andrsn@andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA03587 for ; Thu, 23 Oct 1997 15:46:49 -0700 (PDT) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.8.7/8.6.12) with SMTP id PAA13778; Thu, 23 Oct 1997 15:44:43 -0700 (PDT) Date: Thu, 23 Oct 1997 15:44:42 -0700 (PDT) From: Annelise Anderson To: Gary Schrock cc: freebsd-stable@FreeBSD.ORG Subject: Re: upgrading from 2.1-stable to 2.2-stable remotely? In-Reply-To: <199710232245.SAA26861@eyelab.psy.msu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 23 Oct 1997, Gary Schrock wrote: > 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 Yes--get the sources, do make world without going to single-user mode, rebuild the kernel, reboot the machine. Somewhere along the line you'd want to merge the new stuff in etc with the old. Guess you would want to make sure there's no floppy in the A drive and a cd in the cdrom drive if /cdrom if mentioned in /etc/fstab. I've done this fairly often, but I'm only 10 minutes from the computer :) I try to be careful about changes to config files. Annelise