Date: Thu, 16 Feb 2012 11:03:16 +0100 From: "O. Hartmann" <ohartman@mail.zedat.fu-berlin.de> To: Dimitry Andric <dim@FreeBSD.org> Cc: Current FreeBSD <freebsd-current@FreeBSD.org>, Lars Engels <lars.engels@0x20.net>, Andriy Gapon <avg@FreeBSD.org>, krassi@bulinfo.net Subject: Re: killed libc.so.7 somehow - help./ISO images of CURRENT Message-ID: <4F3CD464.6090507@mail.zedat.fu-berlin.de> In-Reply-To: <4F3BABDE.30908@FreeBSD.org> References: <4F3B89FC.4020802@mail.zedat.fu-berlin.de> <4F3B9B4C.5070508@FreeBSD.org> <20120215120130.GP93151@e-new.0x20.net> <4F3BA719.3060702@mail.zedat.fu-berlin.de> <4F3BABDE.30908@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4280B183EAC7EEC418616E2C Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 02/15/12 13:58, Dimitry Andric wrote: > On 2012-02-15 13:37, O. Hartmann wrote: >> ;-) Problem: I can not even login anymore, since I have "insecured" th= e >> console for security reasons and the shell is rejecting due to a symbo= l >> missing. I tried booting into single user mode, but that doesn't help >> much. >=20 > When booting in single user mode, use /rescue/sh as initial shell. Thi= s > is statically linked, so should always be able to run. Then use the > tools in /rescue to copy back a known good libc.so.7. Last night I did and tried with no success. First I booted from a boot-only cd. After copying libc.so.7, I still received on binaries of the local disc Symbol "_ThreadRuneLocal" not found. So I copied all libs from cd to /lib/ on disc. That helped - for short. I tried to build world again with no success, since cc was missing on the boot/rescue cd. So I booted the regular system again and tried building world. It failed, clang obviously suffered from the same missing symbol. The I did make clean cleandepend depend obj all install in folder /usr/src/lib. But after a reboot, I found myself confronted with the same initial situation when I started the thread. I guess I have "old" binaries and now too recent libs? I fear I'm missing one little specific point to repair the system. Regards, Oliver --------------enig4280B183EAC7EEC418616E2C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBAgAGBQJPPNRrAAoJEOgBcD7A/5N8DQIH/RIUJzGEzKhn6Zn4aIf5P3z4 Mbfe8qDsSvLex0fs6XmwXj/zI3Gqi49e/r4d1dHtlHCSD3Toa3V7PIT4WO1uIZlC tK7otrWm1nHjwv/SudMjT3gQ5FMPnYo4vlEip1YICNmpVKzxi17tqTDZIGLIITHu 6Q13dEcHtF61zn0ATPanU5GPmLL+UOuJgUxKqtjjcTWYHtujqUp/tsgRPqWmu5Ya 5r+MtaKZcTgKkPeXBP+Mv2IWn6uFOuH7lS0HXV/XO/HT6rau6B2WBAx9nLnXgvCE jL/STArTb7O0hm9Pex+MaLvtp4e7O/b8l34wJ4QsdWCEEUDmOiYuaa3364u5OIg= =5wfP -----END PGP SIGNATURE----- --------------enig4280B183EAC7EEC418616E2C--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F3CD464.6090507>