[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libc5 / libc6



> > It is not bad to have also a kit of static utilities, like ln, cp, mv, or
> > even statically linked shell, if one goes to play with libraries.
> 
> Let's start with having a statically linked INIT, LOGIN, GETTY and all
> that yes ? The static utils are about as useful as a shoe for a wooden
> foot without. See below:

Wrong. Let's suppose you play with libc and mess it up. It doesn't
work anymore. Let's now say you did back up the thing, in /tmp. You do cp
/tmp/libc* /lib and see: "Cannot load shared library" or what ld.so says
about it. Whoa, cp needs libc too! What you gonna do now? Boot from floppy
(G-d Almighty knows where is it and when it was updated last time), try
to think how to invent some trick with your current shell built-ins, or
just take static cp and use your backup right now? 

And Linux *can* work without working /lib/libc*, if it was there at
boot time. It won't boot smooth, that's right. But even then a static
shell will help you - just say init=/sbin/statsh and voila! you have at
least the minimum minimorum for you recovery works.

-- 
frodo@sharat.co.il	\/  There shall be counsels taken
Stanislav Malyshev	/\  Stronger than Morgul-spells
phone +972-2-6245112	/\  		JRRT LotR.
http://sharat.co.il/frodo/	whois:!SM8333