Subject: Standard Release (ABC Release of Linux .95a)

From: Alan B Clegg <[email-masked]>
Date: Mon, 6 Apr 92 10:08:27 EDT

With the advent of GCC 2.1 and shared libraries, here is a question:

Every program in /bin *WILL* be linked static.  I have already had to rebuild
from one "accidental" removal of the shared libraries with shared executables
in /bin (rm, cp, etc etc).

BUT:  Should there be a dynamic version of every program that currently lives
in /bin in /usr/bin?  If so, and users have /usr/bin in their path before
/bin, we allow the use of shared libraries for most programs, and we don't
blow off a *LOT* of disk space...

Just an idea....

			from the tormented mind of...

									-abc
-- 
[email-masked]				Alan Clegg - Network Programmer
KD4JML (just my luck!)			MCNC -- Center for Communications

---

From: David Engel <[email-masked]>
Date: Mon, 6 Apr 92 13:38:59 CDT

> in /bin (rm, cp, etc etc).

Well, I plan on putting shared binaries in /bin, but I also plan on putting
together my own "emergency" root disk with a backup copy of the shared library
and essential binaries in case I screw up.

I don't know the nature of your accidental removal but here a couple things
I've done to hopefully avoid doing so myself.  First, DO NOT put a symlink
in /lib to the shared library in /usr/shared/lib.  Copy it to /lib instead.
That way you can safely remove /usr/shared when the next update comes around.
Second, change the mode on your shared libs to 444.  Unless you do an rm -f,
the prompt for comfirmation should make you think twice about deleting it.

> blow off a *LOT* of disk space...

Huh?  Wouldn't keeping static versions in /bin and shared versions in /usr/bin
wast *more* disk space than just static versions in /bin (maybe with symlinks
in /usr/bin)?

-David
-- 
David Engel                        Optical Data Systems, Inc.
[email-masked]                      1101 E. Arapaho Road
(214) 234-6400                     Richardson, TX  75081