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.
fexter@fexter-desktop:~/clamav-0.92rc2$ make install
At least here's a problem: make install (usually) copies files to directories you don't necessarily have write permissions, as a normal user, so for that reason 'make install' should be ran either as root, or with root privileges (trough sudo, for example). The dollar sign ($) above suggests that you're running 'make install' not as root, but as a regular user, and that doesn't work
EDIT: also "fexter@fexter-desktop" sounds like you're issuing the command as user 'fexter', whose rights aren't as high as 'root's.
Configuration step (./configure) and compiling step (make) can and should be done as a regular user, since they don't usually deal with things that require root privileges. But do the last step with root privileges.
Well, the file freshclam.conf (in /etc/ probably, but I'm not sure) is the configuration for the program. By default, if I'm right, there is a variable set that prevents the normal startup of the program and causes it to tell you to edit the file -- this is because the program maker wants that you don't just blindly run it, but read the configuration file trough and modify the options to suit your needs.
So, what you do, is open the file as root (using sudo) with your favourite text editor. Go trough the options; don't remove every comment mark (#) because that either makes the file unusable (wrong lines uncommented, like real comments), or causes things to be un/set that you really don't want to. Instead read the lines trough, and decide which options you want to be set on or off (or to some value), and which ones you want to have at their default values. You don't need to edit lines you think are ok for you, but you can and should edit those values you think are important.
When you've reviewed the configuration options (most of them may well be ok for you), then find the line that says something like "remove this line to allow the program run", and comment it - add # in front of the line (it could also be made so that you need to uncomment something, but you'll see when you read it).
That step is taken in some other programs as well, to make sure the user who installs the program does read the configuration trough and doesn't just jump into using it.
No, not in this forum (that would be awesome, depending on the users themselves), but if you happen to have one of those IM apps installed (Pidgin, Kopete etc..for ICQ for example), you are able to throw me a message.