From: pete@introl.com (Pete Ikusz) Subject: Re: /bin files should not be linked with shared libs! Date: 12 Mar 1993 08:25:11 -0600
In article <C3pC8D.Gun@ra.nrl.navy.mil> 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 believe that the bootable rootdisk currently on tsx-11 has all of
>these filesystems built into the kernel.
>
Eric,
You are right that the system can be made unbootable by many different
methods, such as the corruption of files, init, login, etc.
But the point I think here is that these files do not often get
removed, or updated, whereas the shared libs have been updated quite
often. (Which really shouldn't need to be done, normally) But that
is part of the basis of having shared libs, ie: being able to replace
the libraries without re-compiling everything.
I do think that there is a good arguement for having a few programs
like ln staticly linked. No, it won't alleviate all cases of making
a machine unbootable, but it will rescue those who have deleted a
library link. And as I said, because that is done much more often than
the upgrade of other programs.
I do not agree with having /bin staticly linked though. There are
too many programs in there that are unnecessary for 'fixing' a machine.
Btw: what is the easiest method of making a boot floppy with a file
system on the same disk?
Thanks,
-Pete
--
=======================================================
Pete Ikusz Introl Corporation pete@introl.com
Milwaukee, WI