From owner-freebsd-current Thu May 9 04:26:56 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA26666 for current-outgoing; Thu, 9 May 1996 04:26:56 -0700 (PDT) Received: from kitten.mcs.com (Kitten.mcs.com [192.160.127.90]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id EAA26658 for ; Thu, 9 May 1996 04:26:54 -0700 (PDT) Received: from mailbox.mcs.com (Mailbox.mcs.com [192.160.127.87]) by kitten.mcs.com (8.7.5/8.6.9) with SMTP id GAA03763; Thu, 9 May 1996 06:26:49 -0500 (CDT) Received: by mailbox.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Thu, 9 May 96 06:26 CDT Received: by mercury.mcs.com (/\==/\ Smail3.1.28.1 #28.5) id ; Thu, 9 May 96 06:26 CDT Date: Thu, 9 May 1996 06:26:48 -0500 (CDT) From: Alex Nash X-Sender: nash@Mercury.mcs.com To: Bill Paul cc: Michael Smith , wollman@lcs.mit.edu, current@freebsd.org Subject: Re: Libc is broken! In-Reply-To: <199605090639.QAA03827@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I'd like nothing better than to dive in and debug this, but I need > to get 2.2-current running on my machine at work to do that, and I can't > get the damn snapshot installed because of some mysterious NFS breakage. I had the same problem with NFS (Mike: this was a 486 also) but managed to install using the 2.1.0-RELEASE boot disk. Jordan, do you see any problems with using a 2.1.0 boot disk to install a SNAP? Alex