From owner-freebsd-stable Sun May 13 13:36:45 2001 Delivered-To: freebsd-stable@freebsd.org Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by hub.freebsd.org (Postfix) with ESMTP id 3D19437B423; Sun, 13 May 2001 13:36:42 -0700 (PDT) (envelope-from juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 14z2bY-00021E-00; Mon, 14 May 2001 08:36:40 +1200 Date: Mon, 14 May 2001 08:36:40 +1200 (NZST) From: Juha Saarinen To: Mike Smith Cc: Hugh Blandford , "stable@freebsd.org" Subject: Re: Running Stable on remote production server In-Reply-To: <200105132035.f4DKXtB01042@mass.dis.org> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 May 2001, Mike Smith wrote: > It's entirely unnecessary to go single-user when updating a machine; just > rebuild the world, optionally run mergemaster, and reboot. > > Exceptions to this rule do occur, but they're *extremely* rare. Having rebuilt a number of machines remotely in the last couple of weeks, I have to concur... The most important thing is to pay attention to mergemaster, PLUS doing a final check of vital rc and other conf files in /etc BEFORE rebooting. On one site I had the local "admin" unplug the network cable after the box was shifted into the server room -- I was trying to figure out what I had done wrong until it occured to me to ask if the system was connected to the LAN. His answer was priceless... "why do you have to have a network connection? Can't you get at the box remotely?" ;-D -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message