From owner-freebsd-hackers  Sun Jun 25 10:20:35 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id KAA26859
          for hackers-outgoing; Sun, 25 Jun 1995 10:20:35 -0700
Received: from rover.village.org (rover.village.org [198.137.146.49])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA26851
          for <hackers@freebsd.org>; Sun, 25 Jun 1995 10:20:32 -0700
Received: from localhost (localhost [127.0.0.1]) by rover.village.org (8.6.11/8.6.6) with SMTP id LAA03360; Sun, 25 Jun 1995 11:20:15 -0600
Message-Id: <199506251720.LAA03360@rover.village.org>
To: Richard Toren <rpt@miles.sso.loral.com>
Subject: Re: Announcing 2.0.5-950622-SNAP 
Cc: hackers@freebsd.org
In-reply-to: Your message of Sun, 25 Jun 1995 12:28:30 EDT
Date: Sun, 25 Jun 1995 11:20:15 -0600
From: Warner Losh <imp@village.org>
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. 

You don't have to change your disk partitioning to upgrade, if you
ignore the warnings that are printed.  Desirable, yes.  Required, I
don't think so.

Upgrading could still happen fairly easily, if you had someplace to
stage the upgrade.

Warner