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.
I've read many howto's and threads that state that you should configure and compile as a non-root user. Then to install, su to root and install. Why should i do this? I have ben configuring and compiling as root for a while and have had no problems? Thanks for the help!
well... it's all about security, I'm not sure, but in Linux philosophy, you should NEVER do ANYTHING at root, except things you are FORCED to do. So, since you can "configure" and "make" at user but need to be root to "make install" you should only be root to do make install. I suppose this way, you can avoid bad code, evil configure script or things like this.
Distribution: openSuSE 42.1_64+Tumbleweed-KDE, Mint 17.3
I should think that you are the owner, when you compile something -> the program inherits your rights and not root rights, which might be more secure if your machine is (ever) attacked. That right, security folks?
hum, no you're wrong there, since every progs should be protected against users, they should be "make installed" at root so there right will (habitually) be rwxr-xr-x (755) and owned by root:root, so no one will be able to mess with the progs, except root. Installing progs as users can result in disaster, since anyone can play in the progs executable and add an evil code.