From: ani0349@cs.rit.edu (Anatoly N Ivasyuk) Subject: Re: /bin files should not be linked with shared libs! Date: 11 Mar 1993 03:15:50 GMT
In article <C3oypC.27z@umassd.edu> benu@cis.umassd.edu (David Hassel) writes:
> I know there has already been a discussion on this issue but /bin
>file should not be linked with shared libs. A good example of this is how
>would you boot if libc.so.xx got corrupted? I made the silly mistake of
>removing the link to libc.so.4 and expected to re-ln it immediately.
>ln, cp, cat, etc all were linked against the [missing] shared library.
>
> I do have a boot floppy but not one that knows about extended Minix
>file systems. So I can't boot off of floppy and re-install the link
>until a get a better boot disk.
>
> Therefore I suggest any files in /bin should not be linked with
>shared libs!
>
I set aside a 3 meg partition on my hard drive and put everything in there
that I would need in order to boot in an emergency. There's a kernel, /bin,
/lib with just libc, /etc with no inet, and a small /usr/bin in there. I
use lilo to set up an option to boot that backup kernel using that small
partition as root. This scheme has worked quite well the last time I
screwed up my library links.
-Anatoly
--
| Anatoly Ivasyuk @ Rochester Institute of Technology |
|-----------------------------------------------------|
| anatoly@nick.csh.rit.edu | ani0349@cs.rit.edu |
| Computer Science House | Computer Science Dept. |