From owner-freebsd-stable@FreeBSD.ORG Mon Nov 29 02:56:35 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B33116A4CE for ; Mon, 29 Nov 2004 02:56:35 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7028043D5A for ; Mon, 29 Nov 2004 02:56:34 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAT2tcop023264; Sun, 28 Nov 2004 19:55:38 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 28 Nov 2004 19:56:35 -0700 (MST) Message-Id: <20041128.195635.44431739.imp@bsdimp.com> To: stephen@math.missouri.edu From: "M. Warner Losh" In-Reply-To: <41AA745E.3070400@math.missouri.edu> References: <20041128.174946.105188774.imp@bsdimp.com> <41AA745E.3070400@math.missouri.edu> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: stable@freebsd.org Subject: Re: 5.2 -> 5.3 without single mode? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Nov 2004 02:56:35 -0000 In message: <41AA745E.3070400@math.missouri.edu> Stephen Montgomery-Smith writes: : M. Warner Losh wrote: : > In message: : > dima <_pppp@mail.ru> writes: : > : > Is it possible to cvsup from 5.2 to 5.3 without booting in single mode? : > : > I have a remote machine and want update it, but it is no console access, : > : > only SSH. : > : You don't actually need to reboot in single-user mode. Just make sure your users wouldn't use the server hard during the : > : # mergemaster -p : > : # make installworld : > : # mergemaster : > : cycle. You can basically disable all the services but sshd for that task & enable them again after the second reboot. : > : > While you don't NEED to go into single user (I do the above all the : > time), you are setting yourself up to get screwed the first time that : > a new, common system call is introudced... : > : : So if there is a new common system call introduced, will it arrive with : a nice entry in UPDATING plus a HEADS UP? Maybe, maybe not. All I'm saying is that often you can get away with short cuts, but unless you really know what's going on there are a number of different things that can mess you up trying to do the shortcut. Some of which can be a 'restore from backup' mistake. Warner