Date: Thu, 21 Feb 2013 19:25:29 +0100 From: Fleuriot Damien <ml@my.gd> To: Bernt Hansson <bah@bananmonarki.se> Cc: questions FreeBSD <FreeBSD-questions@freebsd.org>, Devin Teske <Devin.Teske@fisglobal.com> Subject: Re: I made a mess. libc Message-ID: <8F43928B-7313-48C3-9C1B-FA89577D0CDE@my.gd> In-Reply-To: <13CA24D6AB415D428143D44749F57D7201EAC4FD@ltcfiswmsgmb21> References: <51263091.1080507@bananmonarki.se> <2E4C6324-D93A-46EF-82C4-D7C8F9D06894@my.gd>, <51264295.1040902@bananmonarki.se> <13CA24D6AB415D428143D44749F57D7201EAC464@ltcfiswmsgmb21>, <512657E7.90404@bananmonarki.se> <13CA24D6AB415D428143D44749F57D7201EAC4FD@ltcfiswmsgmb21>
next in thread | previous in thread | raw e-mail | index | archive | help
As per Devin's suggestion, I just set up a RCP server from which you'll = be able to grab libc.so.7 using /rescue/rcp I'm gonna need, in private, your IP address so I can add you both to = .rhosts and firewall rules. I'm leaving work now so I may not answer again before 2-3 hours. On Feb 21, 2013, at 6:46 PM, "Teske, Devin" <Devin.Teske@fisglobal.com> = wrote: > Can you specify perhaps "/rescue/sh" as the single-user shell? >=20 > That should get you in. >=20 > Then you have to stick to static executables like /rescue/rcp to = remotely transfer files. >=20 > Perhaps someone can host a file on a machine that can be reached via = /rescue/rcp for you. > --=20 > Devin >=20 >=20 > ________________________________________ > From: Bernt Hansson [bah@bananmonarki.se] > Sent: Thursday, February 21, 2013 9:22 AM > To: Teske, Devin > Cc: Fleuriot Damien; questions FreeBSD > Subject: Re: I made a mess. libc >=20 > 2013-02-21 18:01, Teske, Devin skrev: >> Is it the base machine that won't boot? I got this ... >=20 > That is correct. So no cd burning no nothing...Well it want to drop in > to a single shell bla bla bla press enter for /bin/sh >=20 > <enter> > libexec* libc.so.7: invalid file format >=20 > I do not want to reinstall, have 4 encrypted disks. >=20 >=20 >> My latest version of Druid has a very sophisticated "Interactive Disk = Repair" script that will assemble your system "humpty-dumpty style" = while booted from a CD or Thumb drive (you said you couldn't burn a CD, = but it wasn't clear whether you could master a thumb drive). >>=20 >> = https://urldefense.proofpoint.com/v1/url?u=3Dhttp://sourceforge.net/projec= ts/druidbsd/files/FreeBSD-8.3_Druid-1.0b60.iso/download&k=3D%2FbkpAUdJWZui= TILCq%2FFnQg%3D%3D%0A&r=3DLTzUWWrRnz2iN3PtHDubWRSAh9itVJ%2BMUcNBCQ4tyeo%3D= %0A&m=3D07piZUd2tTTVmRt2abbbhXwBr9OUC7olyXwRy6BdjoM%3D%0A&s=3Da0b244b57abd= 48f38a1cd817513b96950f4c6f2f035b3d33ddee2a27938b2f04 >>=20 >> When you run the "Interactive Disk Repair (IDR) Shell" option, it = presents you with a few questions (like, "I've found a saved network = interface in rc.conf(5) -- would you like me to activate it for you?"), = and ultimately mounts your system to present a working shell to fix your = problems. >>=20 >> Important: when it asks you if you want to chroot into the mounted = filesystem, say NO (you're libc isn't working, so that would be a bad = idea) -- rather, run from the LiveFS environment where /mnt is your = mounted system. There's even a copy of libc in the LiveFS environment = that you can copy over your old one... >>=20 >> cp /cdrom/freebsd/rescue/lib/libc.so.7 /mnt/lib/libc.so.7 >>=20 >> (if I recall correctly) >>=20 >=20 > _____________ > The information contained in this message is proprietary and/or = confidential. If you are not the intended recipient, please: (i) delete = the message and all copies; (ii) do not disclose, distribute or use the = message in any manner; and (iii) notify the sender immediately. In = addition, please be aware that any message addressed to our domain is = subject to archiving and review by persons other than the intended = recipient. Thank you.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8F43928B-7313-48C3-9C1B-FA89577D0CDE>