Re: Ldconfig mistake renders system unbootable?

From: Brooks Davis <brooks_at_one-eyed-alien.net>
Date: Tue, 15 Aug 2006 16:02:27 -0500
On Tue, Aug 15, 2006 at 03:58:59PM -0500, Michael Gardner wrote:
> I was trying to get a Linux binary to run
> (http://filter24.org/seq24/), and was having problems with linking, so
> I messed around with ldconfig a bit and somehow ended up breaking my
> system completely. The command I ran before everything broke was
> "ldconfig -elf /usr/compat/linux/lib", which I now realize was not at
> all what I wanted to do. Now when I try to boot FreeBSD, even in
> single user mode, I get the folowing:
> 
> libexec/ld-elf.so.1: Undefined symbol "__stdoutp" referenced from COPY
> relocation in -sh
> libexec/ld-elf.so.1: Undefined symbol "__stdoutp" referenced from COPY
> relocation in sh
> 
> It then asks me for the location of my shell, but keeps giving the
> errors above no matter which shell I choose (/bin/sh being the obvious
> one).
> 
> I'm running FreeBSD 6.1 (and have been since it came out, so this
> shouldn't have anything to do with upgrading). I know I did something
> monumentally dumb, but how can I fix things?

Use /rescue/sh as your shell (it's statically linked) and then use
/rescue/ldconfig to fix the databases.

-- Brooks

Received on Tue Aug 15 2006 - 19:02:37 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:59 UTC