DebianThis forum is for the discussion of Debian Linux.
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.
As far as a system info program, a task-manager like program is available for kde, just hit "ctrl-esc" - I don't remember what the program name is called, and I'm not in KDE right now. You can also get some good info from the command-line about memory / CPU usage / etc. by running "top".
For the startup programs, you can see what's run on bootup by looking at /etc/rc2.d. All of the scripts in there right now are probably there because of packages you have installed - things like the ssh daemon, cron, etc. The other numbers (besides 2 - e.g. /etc/rc1.d, /etc/rc3.d) mark different runlevels the system enters into, you can find information about the runlevels by typing "man init". Looks like 0 is shutdown, 1 is to get the system into single-user mode (early / emergency initialization), and I BELIEVE 2 is for multi-user startup and 6 is reboot, but I could be wrong. Anyways, placing a link to your own script in one of those folders (and making sure the execute bit is set on the appropriate script / program) will cause that script to be run on entering that runlevel. Make sure you name it like all the other scripts - Sxxscriptname, where "xx' is a number from 00 - 99 that signifies the order the scripts in that folder will be run in, and "scriptname" is whatever name you want.