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.
(Example Diagram Above)
***EDIT: Diagram came out a bit wrong... Hope you get the idea!***
What I'm trying to ask is, when you're trying to install (from source) the 'App To Install', why, in most cases, is it that you need to install several other dependencies, AS WELL AS dependencies for those dependencies, and so on... for some things the list seems endless! However It's pretty cool in a way because, as a developer (new to linux) it's nice to see how everything links and works together thanks to the GPL (FSF).
The next question is, once you finally process the following commands (say for example from your home directory '/home/username') using ./configure && make && make install, and the source is installed, where does the main binary end up, or is this entirely dependant upon the ./configure parameters?
Lastly, the function 'modprobe' doesn't work for me (I get 'bash: modprobe: command not found'), is this simply to do with the fact I dont have the kernel source or something? If so what do I need to do?
Sorry to be a complete pain and ask total beginner questions, but the responses on here seem excellent, and yeh I may be able to program a fully fledged .cpp application, but can't figure out the above!
Thanks in advance for any help at all!
P.S. I'm running Mandrake Linux 10.0, on a Laptop (also trying to get my ZyAIR B-120 PCMCIA wireless card to work but didn't wanna ask too many questions in one post!).
The dependency problem will improve with time because many programs will be using the same libraries that a previous installation needed. Sometimes the source requires the absolute newest library versions that are newer then the ones that your distro is based on. These tend to be the worst projects to install.
About where binaries go, usually in /usr/bin or /usr/local/bin. The /bin and /sbin directories contain the gnu baseutils, fileutils and other programs that thesystem needs to run. Normal applications go under the /usr hierarchy tree which you may have noticed has a similar structure as the main hierarchy. The library files for these programs will go in /usr/lib for example rather than the /lib directory.
The /usr/local directory is another similarly structured hierarchy that is untouched by the distro during upgrades.
I find that is where the simplicity of Slackware comes in. You install the base system that has essentially everything that you need. I have personally never had to compile in a dependcy. Of course I don't do anything spectacular with my box. Usually the maker of the software should present you a list, but it is true that this can be endless. I gues that's why package management is such a hot topic.
Distribution: windows xp home, windows 98, red hat 9, fedora core 3, redhat enterprise linux, win2000 pro/server
wait till your install of slack gets old, before they release a newer version of slack, thats when you run into problems, you upgrade software, but the dependencies need to be updated too, and your in the same boat
Yeah, I might install Slackware 10.0... I have both ISO's, and 2 source discs. I'm just after a linux box capable of developing many types of apps, (using such libs as GTK+ and QT) in C/C++, maybe other languages but those mainly.
Thanks for all your help, I have a good book WELL worth the read... O'Reilly's 'Linux in a nutshell'. Its 927 pages long, so maybe they should've named the book 'Linux in a treetrunk'.
In the meantime I'll keep thinking of questions to ask you...
P.S. I'm developing a new O/S similar to UNIX/Linux... feel free to join me!
***EDIT: Yes... a BIG task... but I have the will power, some O/S programming knowledge (believe it or not), and promise, promise I'll do it i swear***
Last edited by arpanet1969; 12-30-2004 at 07:25 PM.