From owner-freebsd-stable Sun Sep 19 19:18:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id B870015370 for ; Sun, 19 Sep 1999 19:18:50 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id TAA20106; Sun, 19 Sep 1999 19:18:46 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199909200218.TAA20106@freeway.dcfinc.com> Subject: Re: Make World Time In-Reply-To: <199909200216.VAA15799@cyberosity.com> from Tony at "Sep 19, 99 09:09:48 pm" To: tony@cyberosity.com (Tony) Date: Sun, 19 Sep 1999 19:18:46 -0700 (MST) Cc: stable@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Tony wrote: > My customers would freak out if I had them down for 6 hours just to > update the os. Is there a safe way to do this so you dont have your > boxes down until they are updated? I know there has been some paranoia on this list about doing the updates in single user mode, but I've never had any problem doing either a "make world" or a "make installworld" with the system in its normal operating mode. So, I'd recommend you do "make buildworld >& Make.out &" in normal run mode. Examine the output file for warnings or crashes. If it looks ok, then run "make installworld". I doubt your users will even notice. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message