Click to See Complete Forum and Search --> : UT2003 Server install problems
cdslaughter
11-18-2003, 09:55 PM
Ok, I know this is probably simple, but I still need the help. I am trying to install the dedicated 2003 server, but cant fugur out th correct command line to de comprss the .tar file. Anyone have an Idea? I am really green with linux. I installed redhat 7.3 for th first time about 2 weeks ago and am still lost, so please be kind. :rolleyes:
Icarus
11-18-2003, 11:34 PM
I was about to post the tar man page...but THAT would of been mean :)
if it's a .tar.gz do
tar zxvf filename.tar.gz
if it's just a .tar then
tar xvf filename.tar
cdslaughter
11-19-2003, 09:06 AM
ok, do I need to mov this to another forum?
Well somthing is off here. I downloaded the ddicated UT 2003 server from Epic games yesterday the file name is ut2003-lnxded-2225.tar.tar when I try to de-compress the file it telles me"
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Archive contains obsolscent base-64 headers
tar: Error exit delayed from previous errors
I have downloaded it twice ( 3 hours each time on 2 diffrent computers) with the same results on both archives. I have tried to rename the archives to just ut2003-lnxded-2225.tar but the same errors result.
Any clues?
Carl
bwkaz
11-19-2003, 07:58 PM
Originally posted by cdslaughter
the file name is ut2003-lnxded-2225.tar.tar You downloaded it with IE, and it's really a .tar.bz2 file. Retarded browser... :mad:
In the future, if you get strange stuff like this, you can run file ut2003-lnxded-2225.tar.tar to see what kind of file it really is. file would tell you, here, that it's "bzip2 compressed data" or something along those lines.
andysimmons
11-19-2003, 08:03 PM
If it's a tar.bz2, use "tar jxvf filename" to extract it.
cdslaughter
11-29-2003, 11:12 PM
Coolness, I will give that a shot.. I assume it is ran just like gzip? gzip -d "Filename"
Thanks
Carl
bwkaz
11-30-2003, 03:19 PM
bzip2 -d "filename", actually. That'll give you a .tar file (actually, you still might end up with a .tar.tar file, but at least then tar itself won't complain that it "doesn't seem to be a tar file").