On Sat, 18 Feb 2006 20:11:04 +0200, Ori Idan wrote:
>
> I have a source tree which some of the files are actually symbolic links
> to other files in the same tree.
>
> I compress the tree using tar cjf file.tar.bz2 dir
>
> When I extract the files to the same machine everything works fine.
>
> When
On Sat, Feb 18, 2006 at 08:11:04PM +0200, Ori Idan wrote:
> I have a source tree which some of the files are actually symbolic
> links to other files in the same tree.
> When I extract the files to the same machine everything works fine.
> When I extract the files to another machine with same di
Ori Idan <[EMAIL PROTECTED]> writes:
> I have a source tree which some of the files are actually symbolic links
> to other files in the same tree.
>
> I compress the tree using tar cjf file.tar.bz2 dir
>
> When I extract the files to the same machine everything works fine.
>
> When I extract the
find . -type l -exec ls -l {} \;
and check that no link begins with /home (or what ever absolute path).
You can run this command on /usr to see some examples:
[EMAIL PROTECTED]:/usr$ find . -type l -exec ls -l {} \;
lrwxrwxrwx 1 root root 12 2006-01-17 20:42 ./X11R6/lib/libXt.so.6 ->
libXt.so.6.0
Probably the problem that into symbolic link you have absolute and not relative
path?
Can you check this by "ls -l"?
Rgds,
Vitaly
> ---Original Message---
> From: Ori Idan <[EMAIL PROTECTED]>
> Subject: Symbolic links at tar file
> Sent: 18 Feb '06
What was the current working directory when you issued the tar command?
tar uses path names, which are relative to the current working directory
(`cwd`).
So to control path names in the tar archive, cd to the appropriate
directory and then tar from there.
I have a source tree which some of the files are actually symbolic links
to other files in the same tree.
I compress the tree using tar cjf file.tar.bz2 dir
When I extract the files to the same machine everything works fine.
When I extract the files to another machine with same directory
strucu
