From: Tom Bjorkholm AT (tom@at8.abo.fi)
Date: 08/14/93


From: tom@at8.abo.fi (Tom Bjorkholm AT)
Subject: Re: oops, I broke the link for /lib/libc.so.4
Date: Sat, 14 Aug 1993 15:29:27 GMT


>: >I inadvertently changed the link for /lib/libc... to nowwhere. Now my machine
>: >is very unhappy. Every command I try complains about not finding this library.

First: When you are upgrading the libraries use "ln -sf" to make
the new link. If you anyhow manages to get the libraries AFU
sash is a good help. It might be a good idea to install sash
today, you never know what happens tomorrow :-)

sash is found on: sunsite.unc.edu:/pub/Linux/system/Shells/sash.tar.z

From the man page:

SASH(1) SASH(1)

NAME
       sash - stand-alone shell with built-in commands

SYNOPSYS
       sash

DESCRIPTION
       The sash program is a stand-alone shell which is useful
       for recovering from certain types of system failures. In
       particular, it was created in order to cope with the prob-
       lem of missing shared libraries. You can also use sash to
       safely upgrade to new versions of the shared libraries.

       Sash can execute external programs, as in any shell.
       There are no restrictions on these commands, as the stan-
       dard shell is used to execute them if there are any meta-
       characters in the command.

       More importantly, however, is that many of the standard
       system commands are built-in to sash. These built-in com-
       mands are:

            -chgrp, -chmod, -chown, -cmp, -cp, -dd, -echo,
            -ed, -grep, -kill, -ln, -ls, -mkdir, -mknod,
            -more, -mount, -mv, -printenv, -pwd, -rm, -rmdir,
            -sync, -tar, -touch, -umount
[pages of text deleted]

AUTHOR
       David I. Bell