Safest option would be to run/build the software on a new system that is already
configured to use the new version of GLIBC. VMWare is your friend.
Another option (assuming that you have the complete source code) is to try
doing a static build (all library functions included as part of the
executable).
The executable will definitely be large since all dependencies are compiled
into
the binaries. May not work if your program uses some extensions that run on
other packages.
Lastly, some reasons why people still run old Linux/BSD/Unix systems.
1. Why change when everything is running well. Why risk upgrading to the
latest/greatest kernel when firewall/router/dns/email system is already secured
and running well. It may even be riskier migrating all the settings+data to a
new system.
2. You have a lot of data on your system. Ask yourself, do really want to take
the
risk of losing all the StarGate/StarTrek episodes stored in your RAID5 ReiserFS
disk system just because of a new RedHat release.
3. You have some major software (e.g. Oracle database) that specifically works
on that version of the distro.
Ambrosio
---------------------------------
Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on,
when. _________________________________________________
Philippine Linux Users' Group (PLUG) Mailing List
[email protected] (#PLUG @ irc.free.net.ph)
Read the Guidelines: http://linux.org.ph/lists
Searchable Archives: http://archives.free.net.ph
