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.
I need to either stop my computer from entering sleep and suspend mode after idle time,
or vastly increase the default time. I have read the limited information available on acpi,
and found nothing about how to change these. I now know how to PUT my computer into
sleep mode with /proc, but still now clue how to change the darn things that's doing it after
I need a bash solution, this is causing me problems at run level 3. Here's more details:
-Boot up slackware to run level 3
-View LFS book with lynx
-<alt>-f2 to another shell and chroot to do LFS compiling
-Start a long compile. I try not to interfere with this, as I've had problems
using any other shells while this was going on.
-After 10 or so minutes, my screen goes blank, and my cpu enters sleep or suspend mode.
-I enter a key that wouldn't effect the compile (<alt>-f2 again or something)
-Screen comes back up, compiling is stopped dead in its tracks.
-A single tear rolls down my face.
(I didn't know which forum to put this, as it's more a Slackware issue than LFS, so I
threw it in newbie since it regards basic system setup)
Well, I ended up killing acpid and it didn't do the trick. It turns out that by compiling
acpid support into my kernel I was allowing it to also perform acpid tasks as well as
the daemon. The following line in my /etc/rc.d/rc.M is what was doing it.
This is set before acpid is even loaded, turns out it's bash talking directly to the kernel.
The -blank option is how you change the time in minutes. I guess acpid just allows another
way for programs to communicate with acpid through /proc.