Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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 bar normally is compress of source code for particular program, after extract it you need to build and install it manually (./configure, make, sudo make install). the tar ball can be small but the time to compile it maybe very long. For beginner I don't recommend you install software via tar ball. (It is painful some times.)
rpm is software package which has been compile and optimise by particular distro provider (redhat, suse, mandrake, fedora core and etc). Normally this kind of vendor will have a big repository which can solve all your software dependency issue. For beginner I would like to suggest you to use this method.
Except rpm, there is another alternative called deb (work similar with rpm).
If you are beginner, and you willing to learning more. I would recommend you to use ubuntu because it has huge repository of software(ubuntu use .deb).
Well, assuming by "Tar ball" you mean a program compressed in tar ball format, there are quite a few differences. RPMs usually install via a double-click, unless they fail. Sometimes the install can be messy, and have duplicate libraries. But it's a lot easier.
I think the term tarball preceded slackware. A slack tarball will have the extension .tgz. A compressed tar archive of source will normally use the extension .tar.gz. Sometimes bzip2 is used instead and has the extenstion .tar.bz.
In any case, the most important file in a source tarball will be the README file.
If your distro is RPM based, use that unless what you want is not available. Using your distro's packaging system will keep the rpm database up to date and allow security updates to occur in the future for that package. Also, the library versions will match up, and a Fedora Core or SuSE repository for example should have any requirements also available.
Tarball: An archive of files created with the Unix tar utility. Source-code distributions have been packaged as tarballs since the mid 1980s, even though the term's usage did not become commonplace until the late 1990s.
In the same Google search were found several references indicated that a .tar archive can be called a tarball---"with or without" compression.
Terms like this may have been popularized by Linux, but they existed before.