From owner-freebsd-hardware@FreeBSD.ORG Tue May 30 08:18:00 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9FA0216A436 for ; Tue, 30 May 2006 08:18:00 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [64.39.75.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55DE643D46 for ; Tue, 30 May 2006 08:17:59 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 4A02F3DB; Tue, 30 May 2006 03:17:59 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 700CC61C2B; Tue, 30 May 2006 03:17:58 -0500 (CDT) Date: Tue, 30 May 2006 03:17:58 -0500 From: "Matthew D. Fuller" To: Rob Garbutt Message-ID: <20060530081758.GL5226@over-yonder.net> References: <003901c68348$27afbb70$0202a8c0@bmbpc733> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003901c68348$27afbb70$0202a8c0@bmbpc733> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.11-fullermd.3 Cc: freebsd-hardware@freebsd.org Subject: Re: root password recovery X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 May 2006 08:18:04 -0000 On Mon, May 29, 2006 at 06:48:54PM +0100 I heard the voice of Rob Garbutt, and lo! it spake thus: > > I'm getting the following when I try and sudo su - into my FreeBSD 5.1 box:- > > /usr/libexec/ld-elf.so.1: Shared object "libintl.so.4" not found Well, to be simple about it, sudo isn't linked to libintl (at least on my box), so I presume the problem is actually from a shell. So just `sudo /bin/sh` or something instead of calling su (I've never run sudo su anyway) and go from there. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.