Date: Wed, 9 Apr 2003 08:46:36 +0100 From: Wayne Pascoe <freebsd@penguinpowered.org.uk> To: Randy Schultz <schultz@sgi.com> Cc: freebsd-questions@freebsd.org Subject: Re: remote upgrades Message-ID: <20030409074636.GA83496@marvin.penguinpowered.org.uk> In-Reply-To: <Pine.LNX.4.44.0304082206300.1694-100000@cf-vpn-hw-schultz-3.americas.sgi.com> References: <Pine.LNX.4.44.0304082206300.1694-100000@cf-vpn-hw-schultz-3.americas.sgi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 08, 2003 at 10:47:40PM -0500, Randy Schultz wrote: > Hey all, > > What's the preferred method (or what are the methods, in case I missed any) > to remote upgrade a system? I've been looking into the 3 methods and it > seems doing it from source is about the only way no? The binary upgrade > would be good except ones needs to boot the new version from floppy. Just > for grins I tried the "sysinstall installUpgrade" on a testbed. Seemed to > work but /kernel was missing. Oops. Depends on your installation. We have quite a number of servers, so we usually do a make buildworld and make buildkernel on one server, then mount /usr/src and /usr/obj onto the other servers and do a make installworld and make installkernel on each of the machines that we're upgrading. This keeps all the expensive compile work on a single machine, and ensures that all of our boxen are identical. For certain boxes that mustn't have some software touched, we do a make world on that box with it's own make.conf HTH, -- Wayne Pascoe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030409074636.GA83496>