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.
Of course, there should be drivers running with them and those drivers programs should be processes.
I thought drivers were part of the kernel, not user-mode processes…? (Linux uses a monolithic design where drivers are essentially compiled into kernel AFAIK).
In any case, you're right that the keyboard/mouse are just seen as devices. Try cat /dev/input/mouse0 as root, move the mouse around, and you should see what I mean. (/dev/input/mouse0 is, AFAIK, the default device node file for incoming character data from the mouse driver. )
Your correct! The OP should have looked at 'man top', within reference to 'ps'. Some leg work for the OP to understand the reasoning behind 'top' & 'ps'. Then references that were given to the OP that would provide good definition(s) to understand basic operations.
In checking '/dev' you will have either a block or character devices;
Hardware devices can generally be categorized into random access devices like disk and tape drives, and serial devices like mouse devices, sound cards, and terminals.
Random access devices are usually accessed in large contiguous blocks of data that are stored persistently. They are read from in discrete units (for most disks, 1024 bytes at a time). These are known as block devices. Running an ls -l /dev/hda shows a b on the far left of the listing, which means that your hard disk is a block device:
The manner in which the device is handled is up to the 'interrupt handler' or as some say 'interrupt service handler'. Device driver is triggered by the interrupt thus servicing the device. API will control the information from the driver via the scheduler (completely fair scheduler).
Distribution: Ubuntu 11.4,DD-WRT micro plus ssh,lfs-6.6,Fedora 15,Fedora 16
another command would be the 'ps' command, though it simply creates an output and exits, it doesn't run in real time like top does
keyboard/mouse however are devices that are used by processes, not processes themselves.