From owner-freebsd-stable@FreeBSD.ORG Tue Apr 19 16:00:55 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B79CD16A4CE for ; Tue, 19 Apr 2005 16:00:55 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CB9443D46 for ; Tue, 19 Apr 2005 16:00:55 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from localhost (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id 7400F69A21; Tue, 19 Apr 2005 12:00:54 -0400 (EDT) Date: Tue, 19 Apr 2005 12:00:53 -0400 From: Bill Moran To: Matthias Buelow Message-Id: <20050419120053.6ad17df1.wmoran@potentialtech.com> In-Reply-To: <200504191317.j3JDH76H001458@drjekyll.mkbuelow.net> References: <426447F8.5090209@charter.net> <200504191317.j3JDH76H001458@drjekyll.mkbuelow.net> Organization: Potential Technologies X-Mailer: Sylpheed version 1.0.4 (GTK+ 1.2.10; i386-portbld-freebsd5.3) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-stable@freebsd.org cc: jim-c@charter.net Subject: Re: Newbie Question About System Update X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Apr 2005 16:00:55 -0000 Matthias Buelow wrote: > Jim Campbell writes: > > >After that, I ran into problems. It took me a little while to figure > >out how to do "boot -s". However, it appears that a lot of the > >directories aren't mounted and the next scripts aren't in the path. For > >example, I can't figure out how to do the "mergemaster -p". > > You don't have to do it in single user mode, I never did. I don't know > why it is recommended that one boots in single user in the Makefile, > perhaps to get a quiescent system without any users and services that > would interfere. But that can also be achieved by stopping the > high-volume services on the machine after booting, and on a personal > machine (workstation PC) it doesn't matter anyways. Often it's not even > possible to boot into single-user, for example if you don't have > physical control over the machine (like in a co-lo situation). This isn't really true. Fact is, trying to update a running system could result in silent failures. The system can not replace programs that are in use, so there's always the chance that something or other won't get updated (cron would be an excellent example ... do you always shut cron off when you update? How about syslogd?) That being said, I quite often do installworld on running systems because I have no way to go to single-user mode. It almost always works well enough for my purposes, but I don't want anyone to think that it's "OK" to do this, as it's not guaranteed to work, and will most likely result in some programs not being updated (such as the examples in the previous paragraphs). On a production system, you should have a serial terminal connected so you can go to single-user mode remotely to do updates. There are fairly inexpensive serial terminal boxes available from a number of vendors, and if you have a spare machine available, you can always hook it up as a serial terminal. -- Bill Moran Potential Technologies http://www.potentialtech.com