From owner-freebsd-current Sat Nov 25 15:35:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.san.rr.com (smtp2.san.rr.com [24.25.195.39]) by hub.freebsd.org (Postfix) with ESMTP id EBF0237B4CF for ; Sat, 25 Nov 2000 15:35:35 -0800 (PST) Received: from san.rr.com ([24.25.222.134]) by smtp2.san.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Sat, 25 Nov 2000 15:32:43 -0800 Message-ID: <3A204C98.CE92ADD0@san.rr.com> Date: Sat, 25 Nov 2000 15:34:49 -0800 From: Derek Schene' X-Mailer: Mozilla 4.75 [en] (Win95; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: current@freebsd.org Subject: Re: libc.so.4 not found References: <3A1F75E3.2E17FC43@san.rr.com> <20001125024407.O14080@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for everyone's input, I feel I'm getting closer and see where my previous thinking had gone wrong. I tried this- > I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible > should happen. and now when booting get- Local package initialization:fopen: No such file or directory So I copied libc.so.4 from the 4.0 livefile cd....This gave the same message (also had a core dump but may be unrelated). But the good news is now emacs, cvsup, etc. are working. I don't know if this matters but when looking at- implies that the -current packages on ftp.freebsd.org haven't been built since the bump and are thus slightly out dated. I'm thinking the snapshot came from current.freebsd.org? (SNAP5) And when it was mentioned- 2. a 4.1.1-RELEASE libc.so.4 was being used on a 4.0-RELEASE system. I thought I may have problems with using 4.0-RELEASE libc.so.4 on a 5.0-CURRENT system and may be better going with the symlink to libc.so.5? or look for a 4.2-RELEASE libc.so.4 up for people to download and put in /usr/lib/compat manually.? Thanks, Derek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message