From owner-freebsd-questions@FreeBSD.ORG Sat Jun 21 03:14:28 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 02C28615 for ; Sat, 21 Jun 2014 03:14:28 +0000 (UTC) Received: from relay2.tomsk.ru (mail.sibptus.tomsk.ru [212.73.124.5]) by mx1.freebsd.org (Postfix) with ESMTP id 614AF2778 for ; Sat, 21 Jun 2014 03:14:26 +0000 (UTC) X-Virus-Scanned: by clamd daemon 0.98.1 for FreeBSD at relay2.tomsk.ru Received: from admin.sibptus.tomsk.ru (account sudakov@sibptus.tomsk.ru [212.73.125.240] verified) by relay2.tomsk.ru (CommuniGate Pro SMTP 5.1.16) with ESMTPSA id 35776346 for freebsd-questions@freebsd.org; Sat, 21 Jun 2014 10:14:23 +0700 Received: from admin.sibptus.tomsk.ru (sudakov@localhost [127.0.0.1]) by admin.sibptus.tomsk.ru (8.14.7/8.14.7) with ESMTP id s5L3EMYH037696 for ; Sat, 21 Jun 2014 10:14:23 +0700 (NOVT) (envelope-from vas@mpeks.tomsk.su) Received: (from sudakov@localhost) by admin.sibptus.tomsk.ru (8.14.7/8.14.7/Submit) id s5L3EMIh037695 for freebsd-questions@freebsd.org; Sat, 21 Jun 2014 10:14:22 +0700 (NOVT) (envelope-from vas@mpeks.tomsk.su) X-Authentication-Warning: admin.sibptus.tomsk.ru: sudakov set sender to vas@mpeks.tomsk.su using -f Date: Sat, 21 Jun 2014 10:14:22 +0700 From: Victor Sudakov To: freebsd-questions@freebsd.org Subject: Re: binary upgrade of a remote box Message-ID: <20140621031422.GA37667@admin.sibptus.tomsk.ru> References: <20140620122400.GA26444@admin.sibptus.tomsk.ru> <0049E329-310A-4BE9-829B-FE22AC54490F@lafn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0049E329-310A-4BE9-829B-FE22AC54490F@lafn.org> Organization: AO "Svyaztransneft", SibPTUS X-PGP-Key: http://www.dreamwidth.org/pubkey?user=victor_sudakov X-PGP-Fingerprint: 10E3 1171 1273 E007 C2E9 3532 0DA4 F259 9B5E C634 User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jun 2014 03:14:28 -0000 Doug Hardie wrote: > > > > > I have some remote boxes running outdated versions of FreeBSD like > > 8.2-RELEASE-p6 or even 7.4-RELEASE-p5 > > > > What's the least painful way of updating those systems to something > > like RELENG_9_2 ? > > > > I am comfortable with the "make world" method and have done this > > remotely before, but those boxes are too weak to compile their own > > world, and the disks are too small. Mounting /usr/{src,obj} from a > > remote host is not an option because of relatively slow and unreliable > > WAN links. > > > > I am very uncomfortable with "freebsd-update upgrade", at least it's > > not something I would risk remotely. > > > > Any more ideas of a way to perform a smooth binary upgrade? > > Here is the approach I use: > > I keep one system that is purely for development/test. Its large > enough to hold and build the entire system. Note, these machines > are all remote. I use freebsd-update to keep it up to date. I then > rebuild kernels and userland on it since I need to have non-defaults > in the kernel and changes to sendmail to support STARTTLS. That > machine is also configured as a NFS server. > > On the actual production machines, I mount /usr/src, /usr/obj, and > /usr/ports via NFS and then to an install kernel and installworld. > Once that is done, I use mergemaster and then reboot the machine. Doug, That's an excellent method, but as I have already written above, mounting /usr/{src,obj} from a remote host is not an option because of relatively slow and unreliable WAN links. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru