From owner-freebsd-bugs  Thu Mar 27 15:10:05 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA01433
          for bugs-outgoing; Thu, 27 Mar 1997 15:10:05 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id PAA01425;
          Thu, 27 Mar 1997 15:10:02 -0800 (PST)
Date: Thu, 27 Mar 1997 15:10:02 -0800 (PST)
Message-Id: <199703272310.PAA01425@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: conf/3123: /stand/sysintstall does not perform to upgrade to 2.2 
Reply-To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR conf/3123; it has been noted by GNATS.

From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
To: wayne@barnes1.wustl.edu
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: conf/3123: /stand/sysintstall does not perform to upgrade to 2.2 
Date: Thu, 27 Mar 1997 15:00:16 -0800

 > I tried both the menu system and I tried the following command to start it:
 > 
 > /stand/sysinstall nfs=wuarchive.wustl.edu:/archive/systems/unix/FreeBSD\
 >  releaseName=2.2.1-RELEASE distSetDeveloper installUpgrade mediaSetNFS 
 
 Yikes!
 
 I never thought anyone would actually try to run it from multi-user
 mode like this. :-)
 
 It really expects to be run off the boot floppy, where it can
 carefully mount portions of the system and know that they're not
 *active* during the update/upgrade process.  I should probably disable
 upgrade entirely in multiuser mode - whoops.