Quickly move an executable between systems with ELF Statifier


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Quickly move an executable between systems with ELF Statifier
# 1  
Old 10-23-2008
Quickly move an executable between systems with ELF Statifier

10-23-2008 01:00 AM
Shared libraries that are dynamically linked make more efficient use of disk space than those that are statically linked, and more importantly allow you to perform security updates in a more efficient manner, but executables compiled against a particular version of a dynamic library expect that version of the shared library to be available on the machine they run on. If you are running machines with both Fedora 9 and openSUSE 11, the versions of some shared libraries are likely to be slightly different, and if you copy an executable between the machines, the file might fail to execute because of these version differences. With ELF Statifier you can create a statically linked version of an executable, so the executable includes the shared libraries instead of seeking them at run time. A staticly linked executable is much more likely to run on a different Linux distribution or a different version of the same distribution.



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Joing Linux systems to AD and move to OU

Hi, We have joined Linux systems ( RHEL 6.3 ) to Windows AD ( 2008 R2 ). System has been placed in the deafault location 'Computers' in AD. Then we manually move the systems to the respective OU. Is there any option to specify OU location at the time of domain joining ? We are using... (1 Reply)
Discussion started by: snjksh
1 Replies

2. UNIX for Dummies Questions & Answers

Run executable in one directory and then move to another successively

Hello, I have several hundred subdirectories which contain input files for a binary executable. I need to get into each of the subdirectories, run the executable and then move to the next one and repeat the process. What is the best way to do this? Arbitrarily my file structures look like... (3 Replies)
Discussion started by: Gussifinknottle
3 Replies

3. What is on Your Mind?

From Systems Admin to Systems Eng.

I have been wondering how do Systems Administrators do the jump into Systems Engineering? Is it only a matter of time and experience or could I actually help myself get there? Opinions? Books I could read? Thanks a lot for your help! (0 Replies)
Discussion started by: svalenciatech
0 Replies

4. UNIX for Dummies Questions & Answers

move files between file systems with privileges, time stamp

Hi I have to move files between file systems but files in new file system must have the same attributes as in old one (privileges, time stamp etc). Which tool is best : - ufsdump / ufsrestore - tar - cpio - pax - dd - mv Or maybe there is sth else, you suggest to use. Thx for help (5 Replies)
Discussion started by: presul
5 Replies

5. Shell Programming and Scripting

Linux Script to move executable to quarantine

Please help! I am preparing a Linux Script to move windows executable files from samba directory to quarantine directory. For safety, will use "file" command to determine if its executable. Anyone can help? Below is my trial script, but it just move everything, including non-executable.. any wrong... (2 Replies)
Discussion started by: gavintam
2 Replies

6. UNIX for Advanced & Expert Users

How can i read a non text file in unix - ELF-64 executable object file - IA64

The binary file is ELF-64 executable object file - IA64. How i know that the source is Is there any comamnd in unix i can read these kind of files or use a thirty party software? Thanks for your help (8 Replies)
Discussion started by: alexcol
8 Replies

7. UNIX for Dummies Questions & Answers

need solution for this quickly. please quickly.

Write a nawk script that will produce the following report: ***FIRST QUARTERLY REPORT*** ***CAMPAIGN 2004 CONTRIBUTIONS*** ------------------------------------------------------------------------- NAME PHONE Jan | ... (5 Replies)
Discussion started by: p.palakj.shah
5 Replies
Login or Register to Ask a Question
crt0_ia(3)						     Library Functions Manual							crt0_ia(3)

NAME
crt0_ia: crt0.o - execution startup routines for Integrity systems SYNOPSIS
Remarks This manpage describes for Integrity systems. For on PA-RISC systems, see crt0_pa(3). DESCRIPTION
The C, aC++, and FORTRAN compilers link in the object file for statically-bound programs to provide startup capabilities and environments for program execution. It contains startup code that must be linked using to every statically-bound program. In a dynamically linked program (the default method), the object file is not used, and all actions normally associated with it are instead done by the dynamic loader dld.so(5). processes initializers and terminators. Initializers are routines that are called before the program entry point and terminators are rou- tines that are called when the program terminates via the routine. Initializers are invoked in reverse order of the link line so that dependent libraries are initialized before the libraries that depend on them. Terminators, on the other hand, are invoked in the forward order. does not define any variables. It, however, sets the following global variables: A variable of type long containing the number of arguments. An array of character pointers to the arguments themselves. An array of character pointers to the environment in which the program will run. This array is terminated by a null pointer. A variable of type long containing the system id value for an executable program. A variable of type long containing the requested thread local storage size. This variable is initialized with data from the ker- nel. A variable of type void * containing load information passed from the kernel. A variable of type void * whose value equals to the global pointer. A symbol named is also declared in as an enumeration constant, and is incompatible with the declaration in In order to include both header files, it is necessary to define the macro before including This will force the header file to omit the conflicting definition of The enumeration constant is equivalent to in that context, and may be used instead. See ttrace(2). AUTHOR
The features described in this entry originated from AT&T UNIX System III. FILES
SEE ALSO
System Tools aCC(1) invoke the HP-UX aC++ compiler cc(1) invoke the HP-UX C compiler dld.so(5) the dynamic loader exec(2) execute a file f90(1) invoke the HP-UX FORTRAN compiler ld(1) invoke the link editor Miscellaneous end(3C) symbol of the last locations in program Integrity Systems Only crt0_ia(3)