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 have a little problem I was hoping would go away after I upgraded to Fedora Core 2 but it didn't, so I'll ask you guys...
If I try to kill a root process using gnome-system-monitor, it hangs after I enter the root password. I then have to open a terminal to kill gnome-system-monitor. If I launch the system monitor as root, everything works fine.
It's not a big deal to have to login as root to launch the system monitor or to use the terminal to kill processes, but I was wondering if there's another fix for this problem.
Speaking of "killing", I've been using the command "kill -KILLALL process" whenever I need to shut down a process that's not behaving. I picked up the habit a while ago and can't remember why I use it. Is it correct to always do this, or is there specific times when I shouldn't do it?
And lastly, while on a similar topic (I think), is there a "smart" way to use gnome-session-save? I do it manually whenever I make changes (I learnt the hard way by having it set to auto) but sometimes feel like I'm making mistakes. Nothing I can specifically explain, it's just a gut feeling I get cause of some weird stuff that sometimes happens every once and a while, like alsa not always remembering the volume settings and gaim sometimes loads and sometimes doesn't when I start my machine.
The reason I'm doing all of this, btw, is because I've been fiddling around with my machine, trying to make it run more efficiently. If I been a little vague about anything, please let me know. And thanks in advance!