GNU TAR vs NATIVE AIX TAR Post: 302975619

Sponsored Content

Operating Systems AIX GNU TAR vs NATIVE AIX TAR Post 302975619 by bakunin on Thursday 16th of June 2016 05:56:27 AM

06-16-2016

Registered User

Quote:

Originally Posted by filosophizer

What could be the problem / issue ?

Taking the other threads you opened into account which all seem to pertain to the same problem it is quite clear: your system is - for unknown reasons (probably some problem during package installation, but not enough data to verify that) - missing some of the shared libraries the GNU-tar binary relies on. This is why it can't do what it is supposed to do and this is why it can't process your tar-file.

It works like this: GNU-tar calls upon a function "somefunction()", but doesn't contain the code for it. Instead it relies on this code being stored somewhere else on the system (a so-called "shared library", because such files usually contain not only the code for this one but for many such functions). The normal proceedings would now be for tar to load the code representing this function from the library and then execute it. But somehow, in your case, it can't - and because this "somefunction()" is vital to the function of tar - it doesn't get done anything.

So far the general analysis of your problem. Now we need to find out what exactly is holding tar from loading the code for the function from the shared lib. There are several possible reasons:

1 - tar doesn't know where the lib is: any program is guided to the place where it can find the libraries it needs by the variable "LIBPATH" and/or "LD_LIBRARY_PATH". The format is the same as the PATH variable: a list of directories separated by a colon: /some/dir1:/some/dir2:.....

2 - tar can't read the library: maybe the user tar is started with isn't allowed to read the library - check and make sure the "r"-flag is set for world for shared libraries.

3 - The library is really missing: in this case you need to install it somehow. tar itself doesn't care how the library gets there, so install a package or even just copy the file (for test purposes! You don't want that to be a lasting state.) All this means you have to find out which libaries are missing.

I hope this helps.

bakunin

bakunin

View Public Profile for bakunin

Find all posts by bakunin

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

gnu tar on Solaris 8

Here is how I got where I am: I tried untarring tomcat and at the end of the untar I get the following: So I downloaded GNU tar and did a pkgadd -d, which installed the package. But when I run /usr/local/bin/tar, I get this message:

2. Solaris

GNU tar on SUN 9

I downloaded GNUtar from sunfreeware.con and installed it on a sparc running sun 9. Performed pkgadd -d on the required lib and tar file and everything seemed to be ok. I tried to extract a file from a tar created using the sun version with no success. Tar ran for several hours working on the...

3. UNIX for Dummies Questions & Answers

Problems with GNU tar installation

Hi all, Need some help here. I've been trying to install GNU tar version 1.12 into my Solaris 9 machine. steps that I have done was: -untar the package file -run "./configure" -run "make" command (got stuck at this point) Got the following error messages after hitting the make...

4. UNIX for Dummies Questions & Answers

tar -cvf test.tar `find . -mtime -1 -type f` only tar 1 file

Hi all, 4 files are returned when i issue 'find . -mtime -1 -type f -ls'. ./ora_475244.aud ./ora_671958.aud ./ora_934052.aud ./ora_934050.aud However, when I issued the below command: tar -cvf test.tar `find . -mtime -1 -type f`, the tar file only contains the 1st file -...

5. AIX

GNU Tar with compression for AIX 4.2 already compiled ?

Is there a GNU Tar available with compression option available for AIX 4.2 that I can directly use (not having to compile anything, simple installation) ?

6. Shell Programming and Scripting

tar command to explore multiple layers of tar and tar.gz files

Hi all, I have a tar file and inside that tar file is a folder with additional tar.gz files. What I want to do is look inside the first tar file and then find the second tar file I'm looking for, look inside that tar.gz file to find a certain directory. I'm encountering issues by trying to...

LEARN ABOUT SUNOS

chroot

chroot(1M)						  System Administration Commands						chroot(1M)

NAME

       chroot - change root directory for a command

SYNOPSIS

       /usr/sbin/chroot newroot command

DESCRIPTION

       The  chroot  utility causes command to be executed relative to newroot. The meaning of any initial slashes (/) in the path names is changed
       to newroot for command and any of its child processes. Upon execution, the initial working directory is newroot.

       Notice that redirecting the output of command to a file,

       chroot newroot command >x

       will create the file x relative to the original root of command, not the new one.

       The new root path name is always relative to the current root. Even if a chroot is currently in effect, the newroot argument is relative to
       the current root of the running process.

       This command can be run only by the super-user.

RETURN VALUES

       The exit status of chroot is the return value of command.

EXAMPLES

       Example 1: Using the chroot Utility

       The  chroot  utility  provides an easy way to extract tar files (see tar(1)) written with absolute filenames to a different location. It is
       necessary to copy the shared libraries used by tar (see ldd(1)) to the newroot filesystem.

       example# mkdir /tmp/lib; cd /lib
       example# cp ld.so.1 libc.so.1 libcmd.so.1 libdl.so.1 libsec.so.1 /tmp/lib
       example# cp /usr/bin/tar /tmp
       example# dd if=/dev/rmt/0 | chroot /tmp tar xvf -

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       cd(1), tar(1), chroot(2), ttyname(3C), attributes(5)

NOTES

       Exercise extreme caution when referencing device files in the new root file system.

       References by routines such as ttyname(3C) to stdin, stdout, and stderr will find that the device associated with the  file  descriptor	is
       unknown after chroot is run.

SunOS 5.10							    15 Dec 2003 							chroot(1M)