Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
tar -xzvf filename
If you have any problems, you'll need to check the scripts and see if you can edit anything - such as your libraries being in a weird place when the script expects them somewhere else, but that's rare and you should be okay in Slack.
Of course, you may not have the libraries and whatnot needed, but then just download them and start the process over again. Good luck.
- Sorry. Dain bramage. Somebody in a thread I was just reading was using Slack. Duh.
It's a really good thread on installing from source. BTW, any package that ends with .tgz is a package designed for Slackware and they are also known as Slackpacks. Oh, and I've yet to see a *.zip file in Linux, so I can't tell you anything about them. Hope this helps you out.
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Originally posted by tcaptain Just so the newbies don't get confused, that should be change the x to a j if the file is tar.bz2 instead of tar.gz
This is precisely why you need to read the man page. The "x" is for
extract, which is always needed if you are extracting data from a
If you have a file that has been gziped and would like to gunzip it,
you use the "z" option. For differing versions of tar, the bzip2
option is either "y" or "j".
READ THE MAN PAGE!!!
Now could someone please discuss the best methods of dealing with missing libraries.
I'm trying to install a package that complained that libz was missing when I did ./configure, fair enough, I installed the zlib package and then it can't find zlib.h (I think, I'm not at my computer right now) which I'm pretty sure is included in the zlib package I installed.
So would be very grateful if someone would explain how to deal with situations like these in general terms. How do I find the libs if they are on my system? How do I tell configure where to find them, symlinks? command line options? edit the configure script?
you are most likely having problems installing because of missing dependencies... make sure you have all the progs that the application you are trying to install requires.....i usually download from freshmeat.net and they list all the dependencies for the softwares...
usually configure scripts are best left alone since they will make sure that the software you are trying to install will run without fail all the time....but IF YOU REALLY KNOW WHAT YOU ARE DOING or a risk taker (like me)...then i guess you could always change the configure script and remake it using autoconf command...
mrg: Another bit of advice about the dependencies is that when you compile from source, check to see if you have the development packages for those dependencies...
For example, if a certain app needs the XDelta libraries or something...make sure you also have the XDelta-devel package installed or it will say "not found" when you configure...
This isn't ALWAYS the case...but whenever I try and compile something and it says it can't find something I KNOW is installed, the first thing I check is if I have the -devel package installed. Usually that's it...
The second thing I check is ld.so.conf in /etc for the paths to the libraries (just google around for more on that)
Another tip....sometimes ./configure --help or -h will give you some interesting info.
This what I do....I download the file into my ~/dlds folder. Then i go into my /usr/src and run the tar command
tar -zxf /home/me/file.tar.gz
About the install part. There are two kinds of installs (that i know off). First is just a regular where the binaries go into the binary folder/s, the man pages go into the man pages folder/s, etc. To uninstall the program you go back into the source directory and run a 'make uninstall' (That is IF that program has that). If not you can just run a 'make install' again and look where everything went a manually delete it.
Then there is a directory install where everything goes into one folder. To uninstall the program you just delete the folder.
Most times its the first one, but you can choose a directory install every time (again, that was a "i think") by doing.
Yeah - you can delete the zip and keep the source if you're going to do some hacking or delete the source and keep the zip if you need room - or delete both or keep both.
I'm not sure what you mean by install any package in any directory. You can put the tar.gz anywhere and the scripts will send the stuff to their places. And you can change that by modifying the scripts, but there's generally no reason to.
I think maybe you *are* supposed to use /opt or something but /usr/local's still by far the most common thing. I'm not sure if /usr/local meets the File System Hierarchy specs or not.