Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Originally posted by Misteree Does it matter if I install an "...src.rpm", or just an rpm without the "src" in it?
are precompiled binaries, you don't need to compile them, just install. The i386,486,586 & 686 is an indication for what sort of cpu you have.
So, if you have a newer processor, get either the i586 or i686. If you're using a 386 or 486, get the i386 version.
The xx.src.rpm contains no precompiled binary but the source, if you download that you can compile the source inside the src.rpm to obtain an .rpm you can install on your system
The .src one contains the source code, which you can use to build the binaries yourself, by doing:
rpm --rebuild xxx.src.rpm
So it would be better if you build an rpm from a src.rpm 'cause it'll be optimized for your cpu, but if you have a 686 system and you happen to find a xxx.i686.rpm grab that as it's already built for your type cpu
Originally posted by Misteree
I have a P3, so it seems i586 is the best I can go for.
Compiling, building, binaries, etc... are things that are way over my head.
as in 'executable file' (an "exe" in windows terms)
as in building a source rpm (= RedHat package manager, think of a "self-extracting zip" in windows terms) to obtain an rpm (a package with binaries in it that you can install)
as in making an executable file from a source by translating the source to code the cpu understands (-> a compiler's work)
Double-clicking on the .rpm file is about as techno as I get.
You'll have to learn it sooner or later, better now imho
If I understand correctly, I should go for rpm's with i586 in the name, and no .src, right?
Yes, but if there aren't any i586's around, but you spot a src.rpm you can build it yourself.
And what about suse 8.1?
Can I install any rpm at all? or do they have to be specific to suse?