From owner-freebsd-hackers Sun Jun 25 14:30:14 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id OAA08319 for hackers-outgoing; Sun, 25 Jun 1995 14:30:14 -0700 Received: from mercury.unt.edu (mercury.unt.edu [129.120.1.1]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id OAA08313 for ; Sun, 25 Jun 1995 14:30:10 -0700 Received: from gab.unt.edu by mercury.unt.edu with SMTP id AA22210 (5.65c/IDA-1.4.4 for ); Sun, 25 Jun 1995 16:30:03 -0500 Received: from GAB/SpoolDir by gab.unt.edu (Mercury 1.13); Sun, 25 Jun 95 16:30:03 CST6CDT Received: from SpoolDir by GAB (Mercury 1.13); Sun, 25 Jun 95 16:29:52 CST6CDT From: "John Booth" Organization: University of North Texas To: Richard Toren Date: Sun, 25 Jun 1995 16:29:52 CST6CDT Subject: Re: Announcing 2.0.5-950622-SNAP Cc: hackers@freebsd.org Priority: normal X-Mailer: Pegasus Mail v3.22 Message-Id: <4DCFB26AED@gab.unt.edu> Sender: hackers-owner@freebsd.org Precedence: bulk > But in the current case of 2.0.5, possibly the biggest gotcha is the new > disk partitioning / slicing. Upgrading (which I would love to see) > requires that the underlying disk structure and partion sizes are correct > and large enough to hold the new upgrade. Well, this may be a "no no". But I upgraded my 3-22 2.0 Snap machine and upgraded it to 2.05R by booting into single user mode and extracting the binaries over the current setup (after backing up etc). Seems to be working ok. ---------------------------------------------------------------------- College of Arts & Sciences Computing Services John A. Booth, john@gab.unt.edu