From owner-freebsd-alpha@FreeBSD.ORG Fri Aug 20 16:16:01 2004 Return-Path: Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A8AE16A4CF; Fri, 20 Aug 2004 16:16:01 +0000 (GMT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA1DB43D5C; Fri, 20 Aug 2004 16:16:00 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id i7KGFvpM002429; Fri, 20 Aug 2004 12:15:58 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040820144638.GA92603@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> <20040820144638.GA92603@ip.net.ua> Date: Fri, 20 Aug 2004 12:15:57 -0400 To: Ruslan Ermilov From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: alpha@freebsd.org Subject: Re: Alpha is seriously broken X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Aug 2004 16:16:01 -0000 At 5:46 PM +0300 8/20/04, Ruslan Ermilov wrote: >Garance, > >Did you read this thread before replying? :-) I did read all the emails that I had received before I wrote what I wrote. You may have written other emails by then, but I had not received them so I did not read them. From the emails I had read, I thought you were hoping someone could suggest some alternative ideas. I was just trying to be helpful. I'm not sure why you had to respond with some smart-ass sarcasm. > > If that does not work, and would a cross-compile work well-enough to >> generate a new library (if the problem is a library), or a new kernel >> (if the error is in the kernel). Or maybe just generate dynamically- >> linked versions of make & cc. Even if cross-builds are not good >> enough to do a complete buildworld, might they work well enough to > > recover from this with less work than a complete reinstall? > >All static binaries on these two systems crash. Log in to beast >and give it a try. I thought most of the system was dynamically linked these days. In any case, I still think my suggestion *might* work out, but if you are sure it is a waste of time to even try then I guess a full install is the only way out. If I can login, then I assume slogin/scp must be working, and I assume beast still has some filesystems nfs-mounted from other machines. If it were *me* with my lone sparc64 machine, I would try to create a "dry spot to stand on" by scp-ing some fixed-binaries into the box, and then nfs-mount a successful buildworld done on some other machine, and see how far that got me. I admit that some times my attempts to avoid a re-install have probably taken me more time than the re-install would have, but other times it has been well worth the attempt. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu