From owner-freebsd-stable Thu Aug 26 23:42:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dt011n65.san.rr.com (dt010nb9.san.rr.com [204.210.12.185]) by hub.freebsd.org (Postfix) with ESMTP id A37A715421 for ; Thu, 26 Aug 1999 23:42:09 -0700 (PDT) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt011n65.san.rr.com (8.9.3/8.8.8) with ESMTP id XAA66963; Thu, 26 Aug 1999 23:41:37 -0700 (PDT) (envelope-from Doug@gorean.org) Message-ID: <37C63323.F4FABC41@gorean.org> Date: Thu, 26 Aug 1999 23:41:39 -0700 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 4.0-CURRENT-0826 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: Andy Farkas , freebsd-stable@FreeBSD.ORG Subject: Re: make upgrade References: <6965.935733920@localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > > 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. I agree with Jordan here. If you have console access there are a lot of good reasons to use it and start clean. If console access is not an option, or if you are feeling adventurous, try http://freebsd.simplenet.com/make-upgrade.html. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message