:> It seems silly to move something that a huge number of executables
:> in / require to what is most likely a different partition on many
:> systems. So now you have to have two reliable partitions to do
:> anything instead of one? That's silly!
:There shouldn't be anything in the root partition that requires
:libm.so.x.y. If you refer to libc.so.x.y, it has not been removed
:from /lib. Only libm has been moved.
:> My root partition is much, much safer then any other partition
:> because virtually no files are created, written to, or otherwise
:> modified on it. I've been able to shift most of the volatile files
:> onto /var (with a partial mirror in the root to allow an emergency
:> boot without mounting /var), and what few remain are hardly ever
:> touched. From my point of view, putting the shared libs on the root
:> partition is the SAFEST thing you can possibly do with them.
:You only need one demand paged shared library on the root partition.
:That is /lib/libc.so.x.y. The safety of the root partition is not
:just a function of writing/creating/modifying, but also size. The
:larger the root partition is, the greater the chance for a random
:error to occur on it.
:There are other reasons to reduce the size of the root partition, such
:as allowing for diskless systems which can then mount /usr via NFS.
:There are 1.5 megs of demand paged shared libraries (.so files) on my
:system, not including libm.so.x.y and libc.so.x.y. Why would you want
:to increase the size of root by 1.5 megs for things which are not
:needed for anything on your root partition? It is much more sensible
:to move them all to /usr/lib (and /usr/X386/lib).
libc and libm have traditionally gone together, and just because
most CURRENT boot-related binaries don't use libm is no reason
to split them up. libm or its equivalent is already necessary for
booting on some machines (like the NeXT).
If you are looking for a diskless workstation config all you need
to do is make a few boot-related binaries static and put ALL your
libraries under NFS! That takes even less space.
Splitting libc and libm is a mistake, and if it's going to be done
I really, really, really would like a LIBPATH to be implemented and
the absolute nature of ld.so's current library paths made relative.
Sure I can put softlinks all over the place, but I'd rather have
a clean setup. LIBPATH would obviously default to /lib, /usr/lib,
That is a request :-) Then we can all go our merry way.
1005 Apollo Way
Incline Village, NV. 89451 ham: KC6LVW (no mail drop)
USA Sandel-Avery Engineering (702)831-8000
[always include a portion of the original email in any response!]