From: probreak@matt.ksu.ksu.edu (James Michael Chacon) Subject: Re: /bin files should not be linked with shared libs! Date: 10 Mar 1993 22:25:05 -0600
eric@tantalus.nrl.navy.mil (Eric Youngdale) writes:
> How would you boot if [init, getty, bash, login] were corrupted? What
>if you put something stupid in your rc, rc.local, or inittab which prevented
>you from getting in to your system? Basically you cannot get away from the
>fact that there are certain files which must be present and uncorrupt for the
>system to come up. The bootable rootdisk is designed to recover from these
>types of problems.
> I do not think that this is really called for. Those of us in the
>shared library building business always keep a staticly linked ln lying around
>just for the problem you described, but if you staticly linked every binary
>there would be a *very* significant increase in disk usage.
After building the latest version of the shared libs and getting the
ln statement wrong, I always appreciate that boot/root combo H.J made.
I don't keep anything linked static anymore (including init, which makes
booting impossible then :-), but just keep those 2 disks handy. If my
system were going to be used by more than me, than yes I would keep
certain things linked statically like init, sh, and mount. But, until
that day comes I really don't see the point.
James