From owner-freebsd-stable Sun Sep 19 22:52:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3a123.neo.rr.com [24.93.180.123]) by hub.freebsd.org (Postfix) with ESMTP id 450521573C for ; Sun, 19 Sep 1999 22:52:54 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA19537; Mon, 20 Sep 1999 01:52:06 -0400 Date: Mon, 20 Sep 1999 01:52:06 -0400 (EDT) From: Mike Nowlin To: "Chad R. Larson" Cc: Tony , stable@FreeBSD.ORG Subject: Re: Make World Time In-Reply-To: <199909200218.TAA20106@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 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. One time (ONE, out of hundreds), something got outta sync on one of the machines I run doing a "make installworld" -- don't remember the exact situation, but it was something like a binary getting installed & executed before the library that it required was installed... Not a big deal, but my phone started ringing when a user wanted to know why his job didn't work correctly. Doing a "make buildworld" is (almost) absoultely safe while running multiuser, and that's the part that takes so long... If you want to be extremely careful about it (and also a little anal), you can do the "make installworld" in single-user after it's built in multiuser.... --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message