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 am running Fedora Core 4 x86_64 on an ASUS laptop.
Everything was fine, HAL ran fine before, but a yum update I did last week must have changed something, as now the haldaemon fails on startup. I don't know how to find out more about the problem, so I'll need help in that too. Thanks ahead of time!
So far I have found the same type of problem.
Hald and dbus-daemon do not start properly from the init scripts.
I can start dbus-daemon manualy (using --system) and then
start hald manualy. This is prbably not what the system realy wants.
I am thinking there may be a problem in selinux-policy-targeted-1.27.1-2.3
I am running FC4 and update nightly via yum.
Anyone know of what in selinux may be blocking the normal behavor of
dbus-daemon or hald?