Last night I downloaded and installed libc.so.4.3.3 into my Linux
system (originally installed from the latest SLS release but now
with the 0.99.p8 kernel).  I encountered the problem with df not
working any more, so I tried going back to the original
libc.so.4.0 that came with the SLS.  However, when I tried to go
back to libc.so.4.3.3, I made a typo in the symbolic link name,
and discovered that seemingly every damn executable uses the
shared libraries.

Fortunately, thanks to HJ Lu's bootable rootdisk, I was able to
restore the correct symlink and now have a functional system
again.  And thanks to some recent postings here I now know how to
fix the problem with df.

Is there some quick way to unwedge your system if you make the
mistake of destroying the symlink to the shared C library?  If
there isn't any way other than to use a bootable rootdisk to get
in to fix the problem, I would like to _strongly_ suggest that
'ln' be statically linked or that a statically linked version of
'ln' be made available in the distribution so that it is possible
to recover from this mistake the obvious way.

--
Steve VanDevender       stevev@greylady.uoregon.edu
"Bipedalism--an unrecognized disease affecting over 99% of the population.
Symptoms include lack of traffic sense, slow rate of travel, and the
classic, easily recognized behavior known as walking."