Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How do I open and install certain files. Tar.GZ and BIN
- Thread starter vfear
- Start date
if it's a tar.gz file
you hav eto do this
gunzip filename.tar.gz
tar -xf filename.tar
and it should create the directory, where you can comkpile and install.
standard installation have a makefile
you can do ./configure if there is a configure file
and do a make
and then a make install
please refer to the readme files for each installation, it's different sometimes. Emagine Solutions, Inc.
you hav eto do this
gunzip filename.tar.gz
tar -xf filename.tar
and it should create the directory, where you can comkpile and install.
standard installation have a makefile
you can do ./configure if there is a configure file
and do a make
and then a make install
please refer to the readme files for each installation, it's different sometimes. Emagine Solutions, Inc.
- Thread starter
- #3
.bin files are executables. Usually they do all the necessray install work for you.
chmod 755 whatever.bin and then
./whatever.bin
(assuming you trust wherever you got this from, of course). Tony Lawrence
SCO Unix/Linux Resources tony@pcunix.com
chmod 755 whatever.bin and then
./whatever.bin
(assuming you trust wherever you got this from, of course). Tony Lawrence
SCO Unix/Linux Resources tony@pcunix.com
Hi,
Actually, its difficult to say with tar.gz files - it could be source code or a binary distribution. Its also easier to use the 'z' flag with tar rather than running gunzip separately. For example :
$ tar zxvf whatever.tar.gz
you would then cd to the subdirectory created by tar ..
$ cd whatever
then list (ls -l) the files in the directory and you will invariably find some kind of instructions in a README or INSTALL file or suchlike. If its source code you'd have to have the gcc complier collection plus utilities installed but, as htin11 says, generally you just do :
$ ./configure
$ make
$ su (enter root password)
# make install (normally should be run as root)
# exit
$
If it were something like a binary package of apache you have to follow the instructions in the README or whatever. It might be as simple as :
# ./INSTALL.SH
... but maybe not.
If you ever get tar.bz2 files you can use the 'j' flag with tar - e.g.
$ tar jxvf whatever.tar.bz2
These normally are source tarballs - especially for larger 'projects' like the kernel itself.
Regards
Actually, its difficult to say with tar.gz files - it could be source code or a binary distribution. Its also easier to use the 'z' flag with tar rather than running gunzip separately. For example :
$ tar zxvf whatever.tar.gz
you would then cd to the subdirectory created by tar ..
$ cd whatever
then list (ls -l) the files in the directory and you will invariably find some kind of instructions in a README or INSTALL file or suchlike. If its source code you'd have to have the gcc complier collection plus utilities installed but, as htin11 says, generally you just do :
$ ./configure
$ make
$ su (enter root password)
# make install (normally should be run as root)
# exit
$
If it were something like a binary package of apache you have to follow the instructions in the README or whatever. It might be as simple as :
# ./INSTALL.SH
... but maybe not.
If you ever get tar.bz2 files you can use the 'j' flag with tar - e.g.
$ tar jxvf whatever.tar.bz2
These normally are source tarballs - especially for larger 'projects' like the kernel itself.
Regards
- Status
Similar threads
- Locked
- Question
- Locked
- Question
