From owner-freebsd-questions@FreeBSD.ORG Wed Jan 2 18:21:29 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 80A8D8C1 for ; Wed, 2 Jan 2013 18:21:29 +0000 (UTC) (envelope-from asv@inhio.eu) Received: from cz-prg-mx-01.inhio.eu (mail.inhio.eu [178.238.36.226]) by mx1.freebsd.org (Postfix) with ESMTP id 050811B48 for ; Wed, 2 Jan 2013 18:21:15 +0000 (UTC) Received: from [172.16.2.3] (93-45-216-171.ip104.fastwebnet.it [93.45.216.171]) by cz-prg-mx-01.inhio.eu (Postfix) with ESMTPSA id 838766240C; Tue, 1 Jan 2013 11:36:16 +0000 (UTC) Subject: Re: Newbie question about freebsd-update: single user mode is not needed anymore? From: ASV To: Jose Garcia Juanino In-Reply-To: <20121231155020.GA13656@banach> References: <20121231121350.GA5026@banach> <1356967664.2050.9.camel@blackfriar.inhio.eu> <20121231155020.GA13656@banach> Content-Type: text/plain; charset="ISO-8859-1" Date: Tue, 01 Jan 2013 12:36:15 +0100 Message-ID: <1357040175.2063.1.camel@blackfriar.inhio.eu> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jan 2013 18:21:29 -0000 For some reason my email hasn't apparently been delivered so I'm re-sending it. "From: ASV To: Jose Garcia Juanino Cc: freebsd-questions@freebsd.org Subject: Re: Newbie question about freebsd-update: single user mode is not needed anymore? Date: Mon, 31 Dec 2012 17:19:19 +0100|" Well, I understand your concern. I've been using the freebsd-update method since several years now and mostly remotely. I've never encounter a problem. I haven't recompiled everything many times as I didn't really found a tangible advantage in this method but I've never thought about this. I believe some developer around here can provide you a neat explanation about that (which is going to be interesting to know). Strictly about your concern I believe whatever way you use for your upgrade you CANNOT be 100% sure that your upgrade will go smoothly and things like loosing control of your remote box will not happen. Even though jumping from close releases 9.0 => 9.1 is a low risk upgrade, a console access to your remote server (via terminal server/KVM/other) is imperative in these cases to avoid the worst. On Mon, 2012-12-31 at 16:50 +0100, Jose Garcia Juanino wrote: > El lunes 31 de diciembre a las 16:27:44 CET, ASV escribió: > > Hi Jose, > > > > with the freebsd-update method you don't need to pass through the "make > > installworld" as it's a binary patch/upgrade system. > > Using "freebsd-update upgrade -r 9.1-RELEASE" for example allows you to > > get your system patched directly without recompiling the kernel and the > > userland but getting binary patches from the repo and applying these > > directly on your system. > > Check the following page for a more detailed explanation and be aware > > that upgrading your ports/packages is required every time you upgrade > > your kernel to a major version (which would be your case). > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html > > > > Happy new year. > > Thanks for your response. > > The freebsd-update upgrade method is: > 1- freebsd-update install # will install a new kernel and modules > 2- reboot in multi user > 3- freebsd-update install # will install new userland > 4- reboot in multi user > > The src upgrade method is: > 1- make installkernel # will install a new kernel > 2- reboot in single user > 3- make installworld # will install a new userland > 4- reboot in multiuser > > I think that the third step is essentially the same in both methods: it > will install a new userland. But the second one require to be ran in > single user, and the first one does not. Why? > > My unique concern is that step 2 in "freebsd-update" method goes > smootly: it will boot kernel in 9.1-RELEASE but userland in 9.0-RELEASE. > If the system hangs giving up the net or other essential service, I will > not be able to reach the computer via ssh. > > Regards