From owner-freebsd-current@FreeBSD.ORG Fri Aug 20 16:46:12 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 261B516A4CE; Fri, 20 Aug 2004 16:46:12 +0000 (GMT) Received: from mail.qubesoft.com (gate.qubesoft.com [217.169.36.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35CDC43D39; Fri, 20 Aug 2004 16:46:11 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from bluebottle.qubesoft.com (bluebottle.qubesoft.com [192.168.1.2]) by mail.qubesoft.com (8.12.9/8.12.9) with ESMTP id i7KGk9GR010046; Fri, 20 Aug 2004 17:46:10 +0100 (BST) (envelope-from dfr@nlsystems.com) Received: from builder02.qubesoft.com (builder02.qubesoft.com [192.168.1.8]) i7KGk9JV031538; Fri, 20 Aug 2004 17:46:09 +0100 (BST) (envelope-from dfr@nlsystems.com) From: Doug Rabson To: Ruslan Ermilov In-Reply-To: <20040820151503.GC92603@ip.net.ua> References: <20040820101817.GE27931@ip.net.ua> <1092999187.9863.2.camel@builder02.qubesoft.com> <20040820105915.GA29178@ip.net.ua> <1093000460.9863.4.camel@builder02.qubesoft.com> <20040820120757.GC29568@ip.net.ua> <20040820135844.GA76070@ip.net.ua> <1093012873.9863.11.camel@builder02.qubesoft.com> <20040820151503.GC92603@ip.net.ua> Content-Type: text/plain Message-Id: <1093020367.9863.13.camel@builder02.qubesoft.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Fri, 20 Aug 2004 17:46:08 +0100 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 'clamd / ClamAV version 0.65', clamav-milter version '0.60p' cc: Wilko Bulte cc: alpha@FreeBSD.org cc: current@FreeBSD.org cc: Ken Smith Subject: Re: Alpha is seriously broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Aug 2004 16:46:12 -0000 On Fri, 2004-08-20 at 16:15, Ruslan Ermilov wrote: > On Fri, Aug 20, 2004 at 03:41:13PM +0100, Doug Rabson wrote: > > On Fri, 2004-08-20 at 14:58, Ruslan Ermilov wrote: > > > On Fri, Aug 20, 2004 at 03:24:52PM +0200, Dag-Erling Sm?rgrav wrote: > > > > Ruslan Ermilov writes: > > > > > I think there's no emergency plan other than to reinstall "base" > > > > > on these systems from some older snapshot? > > > > > > > > cross-compile on a different machine in the cluster, copy over the new > > > > make(1), then use it to installworld over NFS. > > > > > > > Only if this machine is also Alpha. To tell you the truth, some bits > > > produced by cross-compiles on different architectures are not ready > > > for use on a native architecture. This includes binary files such as > > > fortune(6) .dat files, NLS catalogs, etc. I haven't identified them > > > all yet. > > > > > > Once I get my "modern" Alpha box, I will start working on a project > > > that will eventually address this, so cross- builds and releases > > > will produce the same binary files as on native platforms. NetBSD > > > achieved a great success in this direction, so it shouldn't be too > > > hard to fix. > > > > It might be quicker to extract various critical static binaries (init, > > make, cc, ld etc.) from an unbroken bindist. Oh and hope that beast > > doesn't crash before you replace init :-) > > > Hmm, but init(8) is also a statically linked binary. Heh, and I know > why beast is still alive -- it's due to the way the /root script that > automatically updates the world and kernel on beast works. The script > does, in this risky sequence: buildworld, installworld, and the "old > way" kernel build/install, then reboots in five minutes. At this time, > after it made installworld and attempted to build a kernel, it failed > to do so (the /boot/kernel/kernel is still old). Installworld was > fine because it saves tools that it uses (including "sh" and "make" > into WORLDTMP). > > So Ken, if you want to attempt to revive this machine, don't reboot > it yet, it won't boot up with the new init(8). Of course, we have > /sbin/init.bak saved, but... ;) Another idea - if the obj tree is still around on beast, you might be able to re-run 'make everything' if you can find a working make binary.