From owner-freebsd-stable@FreeBSD.ORG Wed Dec 29 20:30:42 2004 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 5498C16A4CF for ; Wed, 29 Dec 2004 20:30:42 +0000 (GMT) Received: from melon.pingpong.net (82.milagro.bahnhof.net [195.178.168.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 836F643D49 for ; Wed, 29 Dec 2004 20:30:39 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost.pingpong.net [127.0.0.1]) by melon.pingpong.net (Postfix) with ESMTP id 345444AC2F for ; Wed, 29 Dec 2004 21:30:38 +0100 (CET) Received: from melon.pingpong.net ([127.0.0.1]) by localhost (melon.pingpong.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 70200-05-2 for ; Wed, 29 Dec 2004 21:30:38 +0100 (CET) Received: from palle.girgensohn.se (1-2-8-5a.asp.sth.bostream.se [82.182.157.66]) by melon.pingpong.net (Postfix) with ESMTP id 05DE04AC2E for ; Wed, 29 Dec 2004 21:30:38 +0100 (CET) Date: Wed, 29 Dec 2004 21:30:37 +0100 From: Palle Girgensohn To: stable@freebsd.org Message-ID: <05F0F09DEB66858D9B452FB8@palle.girgensohn.se> X-Mailer: Mulberry/3.1.6 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at pingpong.net Subject: how to remote update 4.10 -> 5.3? 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: Wed, 29 Dec 2004 20:30:42 -0000 Hi! Has anyone managed to update a 4.10 system to 5.3 remotely, i.e. without console access, and without spare disk partitions? I have a bunch of 4.10 machines that are too far away for me to actually do the update hands on. I've tried it on a test machine, it fails half way through installworld, and really needs single user mode to succeed. The install procedure fails since it starts using the newly installed stuff, things like sh(1) and test(1), and they cannot find their libc.so.5, I guess... One idea I have is copying / and /usr to some other place and set ldconfig and PATH=some/other/place and when building and installing. Haven't tried it yet, thought I'd hear anyone on this list has a better suggestion? Optimally, there would a couple of gigs on a separate spare disk partition so I could just install everything there and use it upon reboot. Problem is, there is no such space. :( Thanks Palle