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
EXECVE(2)						     Linux Programmer's Manual							 EXECVE(2)

NAME
execve - execute program SYNOPSIS
#include <unistd.h> int execve(const char *filename, char *const argv [], char *const envp[]); DESCRIPTION
execve() executes the program pointed to by filename. filename must be either a binary executable, or a script starting with a line of the form "#! interpreter [arg]". In the latter case, the interpreter must be a valid pathname for an executable which is not itself a script, which will be invoked as interpreter [arg] filename. argv is an array of argument strings passed to the new program. envp is an array of strings, conventionally of the form key=value, which are passed as environment to the new program. Both, argv and envp must be terminated by a null pointer. The argument vector and environ- ment can be accessed by the called program's main function, when it is defined as int main(int argc, char *argv[], char *envp[]). execve() does not return on success, and the text, data, bss, and stack of the calling process are overwritten by that of the program loaded. The program invoked inherits the calling process's PID, and any open file descriptors that are not set to close on exec. Signals pending on the calling process are cleared. Any signals set to be caught by the calling process are reset to their default behaviour. The SIGCHLD signal (when set to SIG_IGN) may or may not be reset to SIG_DFL. If the current program is being ptraced, a SIGTRAP is sent to it after a successful execve(). If the set-uid bit is set on the program file pointed to by filename the effective user ID of the calling process is changed to that of the owner of the program file. Similarly, when the set-gid bit of the program file is set the effective group ID of the calling process is set to the group of the program file. If the executable is an a.out dynamically-linked binary executable containing shared-library stubs, the Linux dynamic linker ld.so(8) is called at the start of execution to bring needed shared libraries into core and link the executable with them. If the executable is a dynamically-linked ELF executable, the interpreter named in the PT_INTERP segment is used to load the needed shared libraries. This interpreter is typically /lib/ld-linux.so.1 for binaries linked with the Linux libc version 5, or /lib/ld-linux.so.2 for binaries linked with the GNU libc version 2. RETURN VALUE
On success, execve() does not return, on error -1 is returned, and errno is set appropriately. ERRORS
EACCES The file or a script interpreter is not a regular file. EACCES Execute permission is denied for the file or a script or ELF interpreter. EACCES The file system is mounted noexec. EPERM The file system is mounted nosuid, the user is not the superuser, and the file has an SUID or SGID bit set. EPERM The process is being traced, the user is not the superuser and the file has an SUID or SGID bit set. E2BIG The argument list is too big. ENOEXEC An executable is not in a recognised format, is for the wrong architecture, or has some other format error that means it cannot be executed. EFAULT filename points outside your accessible address space. ENAMETOOLONG filename is too long. ENOENT The file filename or a script or ELF interpreter does not exist, or a shared library needed for file or interpreter cannot be found. ENOMEM Insufficient kernel memory was available. ENOTDIR A component of the path prefix of filename or a script or ELF interpreter is not a directory. EACCES Search permission is denied on a component of the path prefix of filename or the name of a script interpreter. ELOOP Too many symbolic links were encountered in resolving filename or the name of a script or ELF interpreter. ETXTBSY Executable was open for writing by one or more processes. EIO An I/O error occurred. ENFILE The limit on the total number of files open on the system has been reached. EMFILE The process has the maximum number of files open. EINVAL An ELF executable had more than one PT_INTERP segment (i.e., tried to name more than one interpreter). EISDIR An ELF interpreter was a directory. ELIBBAD An ELF interpreter was not in a recognised format. CONFORMING TO
SVr4, SVID, X/OPEN, BSD 4.3. POSIX does not document the #! behavior but is otherwise compatible. SVr4 documents additional error condi- tions EAGAIN, EINTR, ELIBACC, ENOLINK, EMULTIHOP; POSIX does not document ETXTBSY, EPERM, EFAULT, ELOOP, EIO, ENFILE, EMFILE, EINVAL, EIS- DIR or ELIBBAD error conditions. NOTES
SUID and SGID processes can not be ptrace()d. Linux ignores the SUID and SGID bits on scripts. The result of mounting a filesystem nosuid vary between Linux kernel versions: some will refuse execution of SUID/SGID executables when this would give the user powers she did not have already (and return EPERM), some will just ignore the SUID/SGID bits and exec success- fully. A maximum line length of 127 characters is allowed for the first line in a #! executable shell script. SEE ALSO
chmod(2), fork(2), execl(3), environ(5), ld.so(8) Linux 2.0.30 1997-09-03 EXECVE(2)