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 have made my way through installing linux, but I still feel kind of lost when it comes to desktop environments stuff.
Installing/understanding (basics) Xorg is not a problem, but when I get to policykit, hal, udev, and similar, I don't have clear vision what works on top of what. I have read corresponding manuals, but yet I am still not fully comfortable with it.
For example, "what's policykit's relation to PAM?". I'd be very grateful, if you kicked me out with some links on documentation.
udev is a user-space application (as opposed to the old in-kernel methods) that dynamically generates entries in /dev. When the kernel detects a new piece of hardware, it tells udev, and udev creates a node for it.
Hal is a step above that, and abstracts the hardware layer events into ones that your user-level programs can deal with in a consistent way. It's what (theoretically, at least) makes things like plugging/unplugging your mouse and suspend buttons work properly.
Thanks for your answer,
your post helps me to make it more clear. Also, mind if I have another question? If I want to mount disk with nautilus, how can I determine the exact call it makes? I mean, mounting disks by gnome-related tools always fails with "Not authorized", so I would like to be able to trace call it makes to see where the problem is.
So far, I think I made it to the point that nautilus, through dbus calls policy kit, which mounts disks somehow. I don't know what call nautilus invokes, neither what does it have to do with pam_mount or pmount packages. Also, where console kit gets to the game is also not known for me, but that's fairly another question, so let's stick with original one.
I'd like to get better perspective on what happens here, but so far I haven't been much successful.
The "not authorized" problem is not the main problem, I mentioned it only because it could have something to do with the topic I am talking about.
edit: Actually, I was searching for some info about stuff I was posting about before (policykit,consolekit, dbus calls and maybe something more related to how it works, not how to work with it), not whole linux guides. (I already have read some of them).