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.
If the file doesn't live under your /home/<username>
root should be the only one with write access to it.
If it 's one of your personal configuration files (under
/home/<username>, and you can't write to it, check
who's the owner. If it's you, change the permissions
using chmod u+w <file>. If you're not the owner,
become root, and then chown <username>:users <file>.
However, I can't emphasisze enough that if it's a system
wide file, you should become root to edit it!!!
OK, you DEFINITELY don't want that one to be
writable by anyone else than root.
If you don't want to log-out, log back in as root
so you can use a graphical editor, learn to use one
of the abundantly available command-line ones
so you can do system administration tasks from
a console using su -
E.g. vi, emacs, pico, mc, joe, ....
The previous posters are correct, you don't want to change the permissions on that file. That would weaken the overall integrity and security of the system. Instead, try editing the file by using su like the previous poster said. It will temporarily "change" you into root, who can edit any file on the system.
For added peace of mind you can execute exactly one command as root using su by typing:
su -c "<command"
This'll run just that command so you might type 'su -c "vi /etc/ld.so.conf"' or 'su -c "pico /etc/ld.so.conf"'
You can even use a GUI editor in place of vi or pico above the editor will simply be run as a different user than the rest of your desktop.
sudo's even better, but takes a little setting up.