From owner-freebsd-stable Thu Aug 26 23: 5:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 61ACF154B9 for ; Thu, 26 Aug 1999 23:05:46 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from localhost (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA06969; Thu, 26 Aug 1999 23:05:20 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Andy Farkas Cc: freebsd-stable@FreeBSD.ORG Subject: Re: In-reply-to: Your message of "Fri, 27 Aug 1999 15:48:11 +1000." Date: Thu, 26 Aug 1999 23:05:20 -0700 Message-ID: <6965.935733920@localhost> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What is the definitive answer to doing a 'make upgrade' on a production > system running an older 2.2.x - is it ok to do it at the multiuser level, > or must one bring the system to single-user mode, hence denying services > during the duration of this rather long process?? I wouldn't use make upgrade on a production server at all, to be honest. I'd back up the user files and reinstall, or install onto a 2nd box, migrate the files, then switch over. This is how I do all production boxes. The upgrade target is by no means guaranteed to do anything more than turn a production box into hash. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message