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.
Ok so this is probably the most stupid question in the world, but I am having huge problems executing downloaded files in Fedora Core 2. My most recent disaster has been with Kile-and IDE for latex. i have downloaded two different versions of it, but they will not start with ./filename at the command line, can anybody tell me what i am doing wrong?
If you downloaded 'kile', it was probably either an rpm package or a tarballed source directory that you downloaded. What was the exact file name that you downloaded? With a .rpm file you need to install it with a package manager or the 'rpm' command. If it was a tarball you need to extract the directory, and follow the instructions in the README and INST-LL files.
For kile, that would be the instruction sequence of
tar xvzf kile-<version>.gz
******* # root password
Read through the INSTALL and README file to make sure this sequence is correct.
A simpler program may just have a Makefile. I've run across some tarballs where there wasn't a 'configure' file buy there was a config.in file, and I needed to run the
command 'autoconf' to produce the 'configure' script.
A tarball installation will probably put the files in the /usr heirarchy. You can run the command 'find /usr -cmin -5' to find new files and directories produced in the last 5 minutes.
The executable will probably be copied into either /usr/bin or /usr/local/bin. There will more often than not also be man files installed, and sometimes library files. For a program like kile, also icons files in /usr/share. But you may need to install the k-menu entry yourself.
On occasion, I've needed to run the 'ldconfig' command as root, so that the new library paths would be registered.
Another type of installation will run an automated install script. NVidia drivers and the Firefox browser may use this type of installation method.