From owner-freebsd-questions@FreeBSD.ORG Tue Dec 2 21:57:56 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA5B516A4CE for ; Tue, 2 Dec 2003 21:57:56 -0800 (PST) Received: from dsl-mail.kamp.net (mail.kamp-dsl.de [195.62.99.42]) by mx1.FreeBSD.org (Postfix) with SMTP id A382B43FAF for ; Tue, 2 Dec 2003 21:57:54 -0800 (PST) (envelope-from root@pukruppa.de) Received: (qmail 32682 invoked by uid 505); 3 Dec 2003 05:57:55 -0000 Received: from root@pukruppa.de by dsl-mail by uid 89 with qmail-scanner-1.14 (spamassassin: 2.43. Clear:SA:0(0.0/5.0):. Processed in 0.494509 secs); 03 Dec 2003 05:57:55 -0000 X-Spam-Status: No, hits=0.0 required=5.0 Received: from unknown (HELO reverse-213-146-114-24.dialin.kamp-dsl.de) (213.146.114.24) by dsl-mail.kamp.net with SMTP; 3 Dec 2003 05:57:54 -0000 Date: Wed, 3 Dec 2003 07:00:43 +0100 (CET) From: Peter Ulrich Kruppa X-X-Sender: root@pukruppa.net To: Alex de Kruijff In-Reply-To: <20031203021242.GB562@dds.nl> Message-ID: <20031203065356.X741@pukruppa.net> References: <3FCBF280.9060108@acm.org> <20031203021242.GB562@dds.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Denis Fortin cc: freebsd-questions@freebsd.org Subject: Re: Is there a guide to Upgrading a FreeBSD server remotely X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 05:57:56 -0000 On Wed, 3 Dec 2003, Alex de Kruijff wrote: > On Tue, Dec 02, 2003 at 03:01:36AM +0100, Denis Fortin wrote: > > Greetings, > > > > I've Google'd a bit, but I cannot find a "survival guide to upgrading > > a FreeBSD system remotely". > > > > The Handbook's procedure is excellent (cvsup to the RELENG branch and > > then make'ing world), but it requires going into single user mode and > > using the console, two things which may not be possible in the context > > of a server sitting unattended in a hosting center 10000 kilometers away. > > > > Has anyone written a quick guide on issues that can arise in this kind > > of situation? (For instance, one the the issues is that one might end > > up with a bad kernel: have people devised a way for the boot code to > > interact with "reboot -k xxx" to revert to the default kernel after an > > unsucessful boot, or after a specific time?) > > > Although its not recommended to do this, it can be done. It basicaly > comes down to following the manual (without rebooting into single > usermode) and be very very carefull. Read everything you need to read, > run every command you need to run and have someone sitting there in case > it goes wrong. > > Note: I've never done this on a busy system. That is the really important thing: there shouldn't be any other traffic on the system. Do everything step by step and keep a logfile to check if everything worked o.k. . Do something like # make buildworld > logfile & In case your connection breaks, buildworld will go on and you can check everything when it is up again. With # tail -f logfile you can check the advance anytime you whish. Uli. > -- > Alex > > Articles based on solutions that I use: > http://www.kruijff.org/alex/index.php?dir=docs/FreeBSD/ > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > +---------------------------+ | Peter Ulrich Kruppa | | Wuppertal | | Germany | +---------------------------+