Date: Fri, 20 Sep 2002 02:13:23 -0700 From: Doug Hardie <bc979@lafn.org> To: Gunnar Flygt <flygt@sr.se> Cc: FreeBSD Stable <freebsd-stable@FreeBSD.ORG> Subject: Re: Updating 4.6.2.-RELEASE machines Message-ID: <f05111b2eb9b096318546@[10.0.1.90]> In-Reply-To: <20020920090555.B90048@sr.se> References: <20020920081512.A90176@sr.se> <20020920090555.B90048@sr.se>
next in thread | previous in thread | raw e-mail | index | archive | help
At 0905 +0200 9/20/2002, Gunnar Flygt wrote: > > Is there an easier and quicker way to get these systems up to date, or >> do I have to run the whole buildworld, make kernel ....-> mergemaster >> line? Most of the system are not so time critical for updating, but two > > of them are handling bind and named, and can not be down so long. I have a similar situation where down time is very undesirable. I found the following approach somewhere in the handbook. It reduces down time for major updates. I keep all the source on one non-critical machine. The kernels and makeworld are done on that machine. I also test everything out there. When its time to update the critical machines, I stop the server processes, NFS mount /usr/src, /usr/obj, and /usr/ports from the source machine and run installworld, installkernel and mergemaster. I have previously done a mergemaster on the source machine and keep notes so that most of the files which require no local customization can be quickly installed. Only a couple require any real action. This keeps the downtime to about 30 minutes per machine. -- -- Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f05111b2eb9b096318546>