From owner-freebsd-questions@FreeBSD.ORG Wed May 4 02:50:53 2005 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 6DF5416A4CE for ; Wed, 4 May 2005 02:50:53 +0000 (GMT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C9B443D66 for ; Wed, 4 May 2005 02:50:53 +0000 (GMT) (envelope-from pergesu@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so96512nzk for ; Tue, 03 May 2005 19:50:47 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SWNvcU6C0SwP/JeLCQ2R2/HlM/BX+lgE3io8eB8qPbnWGnYJ2fcJcn5tGq8UBggj2erHQplr07yWKRiTy/hOz4C5zTizWC6/rhuUM8BEh5ode6XTBgqSwMWMvaJUtqaCwRD4EY4J9NT2H76l1W9lrO6hCl2Nu9PbQXB1P2z5PRw= Received: by 10.36.81.11 with SMTP id e11mr29992nzb; Tue, 03 May 2005 19:50:47 -0700 (PDT) Received: by 10.36.48.9 with HTTP; Tue, 3 May 2005 19:50:47 -0700 (PDT) Message-ID: <810a540e0505031950920bc63@mail.gmail.com> Date: Tue, 3 May 2005 20:50:47 -0600 From: Pat Maddox To: FreeBSD Questions In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: Subject: Re: make installworld (remotely) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pat Maddox List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 May 2005 02:50:53 -0000 Huh? How about the many many production machines located at remote datacenters? How do people upgrade those? I've personally done hundreds of remote upgrades without ever rendering a machine unrecoverable. In fact, the only problems I've run into are with a noexec /tmp, but that's easily fixable when doing an upgrade. On 5/3/05, bob@a1poweruser.com wrote: > Doing a remote buildworld is just too dangerous for an production > box and expensive in backups because you have all the source files > to deal with. The more popular method of updating a remote system is > to have an local development box that has same components and do a > fresh install to a empty ata hard drive and them ship new HD to > remote site and swap for old one. If needed, you recover by swapping > old one back in. Or another popular way is after populating new HD, > build an bootable system on a cdrom then ship cdrom to remote site > and swap that. >=20 >=20 > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Lauri > Anteploon / ctrl-L > Sent: Tuesday, May 03, 2005 5:30 PM > To: freebsd-questions@freebsd.org > Subject: make installworld (remotely) >=20 > Hi. > Im running FreeBSD 5.3-Release #0 and would like to do buildworld > and > buildkernel. > The problem is that the machine is a remote one. > Handbook states that to run "mergemaster" and "make installworld" I > should > boot into single user mode. > That would mean that I can't access the machine remotely anymore am > I > correct? >=20 > Would it be okey to run make installworld when running in multiuser > mode and > being the only person whos logged on and maby shutting down most of > the > network services (leaving my sshd running though) ? >=20 > Lauri Anteploon > HYPERLINK "mailto:lauri@bitifarm.ee"lauri@bitifarm.ee > 5056999 >=20 > HYPERLINK "http://www.bitifarm.ee/" >=20 > -- > No virus found in this outgoing message. > Checked by AVG Anti-Virus. > Version: 7.0.308 / Virus Database: 266.11.2 - Release Date: > 2.05.2005 >=20 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" >