getting error during "tar -xvzf filename.tar.gz"

b0nd · 04-11-2005, 05:41 AM

Hello all,
i'm trying to untar a package.......but when i'm executing the following command
.........
tar -xvzf filename.tar.gz
.........
its giving the following error......( i'm just stating the last few lines )

john-1.6/README
tar: john-1.6/README: Cannot create symlink to `doc/README': Operation not permitted
tar: Error exit delayed from previous errors

i again downloaded its fresh copy........but still facing the same problem

any sort of help will be highly appriciated.
regards

ravee · 04-11-2005, 07:01 AM

Your error says

Quote:

Operation not permitted

. So try installing the package by logging in as root.

mjjzf · 04-11-2005, 07:14 AM

Exactly. It seems you are trying to create a symlink in a place you don't have write access to.

b0nd · 04-12-2005, 12:25 AM

pardon me..........but i'm the "root"..........i don't have any user on my system

regards

masand · 04-13-2005, 01:50 AM

hi there

there is some thing wrong with the installation script that it is running
post the link from where u got this package

regards

b0nd · 04-13-2005, 04:57 AM

www.openwall.com/john/

mugwump84 · 04-13-2005, 08:41 AM

You don't have a user account? Big security hole. easy to turn your system into somthing that looks like a computer, but doesn't act like one.

trscookie · 04-22-2005, 03:46 PM

i got that problem when trying to tar my stage in gentoo 2005. got that problem when trying to tar -xvjpf <mystage>.tar.bz2 and i havent got a clue how to sort it out

Raafi · 04-22-2005, 06:42 PM

i have found when using the various xvzf-type commands, what works for one, may not work for another

sometimes you have to put the negative (-) sign, sometimes not

i have always attributed it to the quirks of the system

(my one cent)

trscookie · 04-23-2005, 07:13 AM

thanks for the response but i still got the same error :'( you havent got any other ideas do you?? cheers

Raafi · 04-23-2005, 06:11 PM

post the tarball here

trscookie · 04-23-2005, 08:50 PM

cheers man tis ok ive sussed it!!! its because i had mounted the proc (mount -t proc none) before uncompressing the file(s) i think that it had tried to write a new file whilst i was using it, thanks for your help all the same though, cheers trscookie.