Date: Fri, 22 Feb 2013 19:19:02 +1100 From: "Daniel O'Callaghan" <danny@clari.net.au> To: freebsd-questions@freebsd.org Subject: Re: I made a mess. libc Message-ID: <512729F6.10007@clari.net.au> In-Reply-To: <512705BB.1020801@ShaneWare.Biz> References: <51263091.1080507@bananmonarki.se> <2E4C6324-D93A-46EF-82C4-D7C8F9D06894@my.gd>, <51264295.1040902@bananmonarki.se> <13CA24D6AB415D428143D44749F57D7201EAC464@ltcfiswmsgmb21> <512657E7.90404@bananmonarki.se> <51268D52.5000906@gmail.com> <5126AFC3.8010802@bananmonarki.se> <512705BB.1020801@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
On 22/02/2013 4:44 PM, Shane Ambler wrote: > You missed the earlier suggestion - at the single user prompt for a > shell don't just hit enter - type in /rescue/sh This suggestion was gold for me, but in a different way. I have for years lamented the passing of static binaries in /bin and /sbin. I forget who mentioned that /rescue/* are statically linked - I had never known that. Today I have just built a 5.4-RELEASE jail on a 9.1-STABLE system, and being able to include a statically linked 9.1-STABLE 'ps' is very useful. The 5.4 version of ps is useless in this jail. And just in case the significance is lost on Bernt, /rescue/sh does not rely on libc, so it won't care if libc is broken. Danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?512729F6.10007>